[BUG] - Running on MacOS fails installing Chrome

Describe the bug
Can install google-chrome-stable via docker build --tag my-cftools-discord-bot . or docker-compose up
❯ docker build --tag my-cftools-discord-bot .
[+] Building 4.4s (6/11)
 => [internal] load build definition from Dockerfile                                                          0.0s
 => => transferring dockerfile: 1.51kB                                                                        0.0s
 => [internal] load .dockerignore                                                                             0.0s
 => => transferring context: 536B                                                                             0.0s
 => [internal] load metadata for docker.io/library/node:19                                                    0.5s
 => CACHED [1/7] FROM docker.io/library/node:19@sha256:92f06fc13bcc09f1ddc51f6ebf1aa3d21a6532b74f076f224f188  0.0s
 => [internal] load build context                                                                             0.2s
 => => transferring context: 5.29MB                                                                           0.1s
 => ERROR [2/7] RUN apt-get update --no-install-recommends    && apt-get install -y --no-install-recommends   3.9s
------
 > [2/7] RUN apt-get update --no-install-recommends    && apt-get install -y --no-install-recommends wget gnupg     && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | gpg --dearmor -o /usr/share/keyrings/googlechrome-linux-keyring.gpg     && sh -c 'echo "deb [arch=amd64 signed-by=/usr/share/keyrings/googlechrome-linux-keyring.gpg] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list'     && apt-get update     && apt-get install -y google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-khmeros fonts-kacst fonts-freefont-ttf libxss1       --no-install-recommends     && rm -rf /var/lib/apt/lists/*:
#5 0.264 Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
#5 0.325 Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
#5 0.360 Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
#5 0.396 Get:4 http://deb.debian.org/debian bullseye/main arm64 Packages [8071 kB]
#5 1.390 Get:5 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages [248 kB]
#5 1.421 Get:6 http://deb.debian.org/debian bullseye-updates/main arm64 Packages [12.1 kB]
#5 2.045 Fetched 8539 kB in 2s (4608 kB/s)
#5 2.045 Reading package lists...
#5 2.322 Reading package lists...
#5 2.585 Building dependency tree...
#5 2.655 Reading state information...
#5 2.738 gnupg is already the newest version (2.2.27-2+deb11u2).
#5 2.738 wget is already the newest version (1.21-1+deb11u1).
#5 2.738 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
#5 2.984 Get:1 http://dl.google.com/linux/chrome/deb stable InRelease [1825 B]
#5 2.989 Hit:2 http://deb.debian.org/debian bullseye InRelease
#5 3.011 Hit:3 http://deb.debian.org/debian-security bullseye-security InRelease
#5 3.044 Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
#5 3.054 Get:5 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1078 B]
#5 3.200 Fetched 2903 B in 0s (10.5 kB/s)
#5 3.200 Reading package lists...
#5 3.480 Reading package lists...
#5 3.737 Building dependency tree...
#5 3.814 Reading state information...
#5 3.862 E: Unable to locate package google-chrome-stable
------
executor failed running [/bin/sh -c apt-get update --no-install-recommends    && apt-get install -y --no-install-recommends wget gnupg     && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | gpg --dearmor -o /usr/share/keyrings/googlechrome-linux-keyring.gpg     && sh -c 'echo "deb [arch=amd64 signed-by=/usr/share/keyrings/googlechrome-linux-keyring.gpg] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list'     && apt-get update     && apt-get install -y google-chrome-stable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-khmeros fonts-kacst fonts-freefont-ttf libxss1       --no-install-recommends     && rm -rf /var/lib/apt/lists/*]: exit code: 100

Desktop (please complete the following information):

OS: MacOS 13.4.x
Version: main branch

I assume it is due to the arch on the Mac being arm and the chrome package being only available as amd. The docs referenced that I could tell puppeteer the path to my local binary, any suggestions on how to do that?

@mszoernyi That's exactly right, we are currently experiencing this issue in #11 - let me get on this right away and allow users to overwrite the path pointing to the binary executable

this has been added in the latest release, please refer to the documentation
Feel free to re-open this issue if your problem isn't addressed


Map class and methods in NarratorOptionsScreen

Map class and methods in NarratorOptionsScreen
This PR maps the class class_5500, which is the base of AccessibilityOptionsScreen and ChatOptionsScreen.
The class simply contains code to handle updating the narrator button text when the mode is changed via the
keyboard shortcut.
It also maps two related functions in GameOptionsScreen and ButtonListWidget.

I've made the suggested changes, I totally forgot the use of parent for screens when I first did these 🙂


Merge prTesting_201904301041 branch to master branch

Docs Build status updates of commit 0d166b6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Grammatical edits to documentation

Made various grammatical edits to the documentation in an effort to improve clarity.

Excellent module! I'm looking forward to using it 👍

Awesome, thanks for the edits. Docs change so often that these mistakes often go missed


"Load on all tabs" has to be unchecked then checked again, after first install

Hi, thanks for this extension! I used "Back to close" a long time ago but it stopped working for me, so it's great to have it back again.
Just one thing, after I installed it, tabs opened from a New Tab wouldn't close, only from "Open in a new tab", even though "Load on all tabs" is checked by default. After a while, I figured out I had to uncheck it, then check it again.

Hmm.. thanks for this report. I'll look into what could be causing these issues. Note that I'm currently very busy, so progress might be a bit slow :)

@ElhemEnohpi Could you try with version v0.6.0? It should be public on AMO in a few minutes :)

Yes, it seems to be fixed in the new version, thanks!


Enhance "DEPRECATED" feature

Now it is only possible to add a "*DEPREACTED*" text within a keyword documentation for generating a warning. I would like to see it enhanced in those ways:

deprecate not only the keyword, but also keyword's argument(s)
deprecate library as well
a decorator to avoid modification of keyword's documentation

I am think about such usage of deprecated decarator for 1st point:
@deprecated(desc='Some description', arguments=[arg3], library_version='1.2.3')
def keyword(arg1, arg2, arg3=1):
    ...

desc: specifies a reason for deprecating; can be some default value if omitted.
arguments: if deprecated argument is not passed to keyword in .robot file, so default value is used - no warning, otherwise, warning is logged. May be arguments can be defined as pair: [desc, arg], so deprecation message associates with a particular argument.
library_version: specifies version of the library where keyword has been deprecated.

Not sure how to apply the same to user keywords though.

I agree using documentation for deprecation isn't always that nice and I have been thinking we could add other means for that. Having a dedicated decorator with all the proposed features sounds pretty complicated, though. I'm not sure is any of the configuration options really needed or at least worth the implementation effort:

Having a separate description about deprecation sounds strange when you could just use keyword documentation instead. Could you explain the benefits of a separate free text entry?

Being able to deprecate arguments would be helpful, but arguments can be changed in so many ways (renamed, removed, added, reorganized) that I'm afraid it gets too complicated to solve this in generic manner. If you have a concrete plan how it would work, please explain it in comments.

When something is deprecated could be just explained in keyword documentation (or in deprecation description if it was added). Or did you have some special use case for this?

A common problem with adding any of the above information is that we needed to add them to various model objects, Libdoc spec files, output.xml, log.html and report.html meaning that implementation work would be rather big. Especially with free description and library version I find it hard to see benefits when you can just use the keyword documentation instead.

I've been personally thinking that we could support a special keyword tag like robot:deprecated to mark a keyword deprecated. It would work both with library and user keywords and would also be very easy to implement. A drawback is that you would still need to update the documentation to tell more about deprecation, but at least this would allow dropping the *DEPRECATED* prefix from the doc.
We could also support deprecated=True argument with the existing @keyword decorator, but I'm not sure would it have real benefits compared to using tags=['robot:deprecated']. Implementing it so that it just adds that robot:deprected tag would be trivial, though.

It would be nice to have a clear way of deprecating a whole library, not just individual keywords. In that case it could be useful to have a decorator or is it possible in some way already?

There's no possibility to deprecate a library. That would need a separate issue.

Having a separate description about deprecation sounds strange when you could just use keyword documentation instead. Could you explain the benefits of a separate free text entry?

I like a warning message in the HTML log that pops up deprecation info. That's what I meant here. If description is defined, it can be used to as a source for a warning message. The only thing here is that number of such messages (even now) might be too high and the top of HTML log might be over populated with those messages.

Being able to deprecate arguments would be helpful, but arguments can be changed in so many ways (renamed, removed, added, reorganized) that I'm afraid it gets too complicated to solve this in generic manner. If you have a concrete plan how it would work, please explain it in comments

The most generic use case for us is that sometimes we don't want to deprecate a keyword, but only some argument. For example, arguments's behaviour changes or it is replaced by other argument. While we don't want to break existing tests, we support old behaviour for a while. And unfortunately this can take a long time (e.g. half year) as corresponding teams reponsible to support tests shall have planned work to do changes.
I see only 2 options for an existing argument:

agument's behaviour changes in some way
argument get replaced by another argument, or is going to be removed at some point of time

For both cases, might be good to issue a warning message (again, I meant it when added a description) so people take this into account. Only more though here is to have a tool similar to tidy, but with different purpose - it can be used to analyze test scripts for deprecated keywords/arguments/libraries, and, if found, the tool reports that so we know that it is safe now to stop supporting old behaviour. As we are having more and more test scripts in our environment, the problem of analysis them for deprecated stuff becomes more feasible.
Adding, removing, renaming and so on are not backward compatible changes in terms of API, so I agree it does not make sense to deprecate such changes.

When something is deprecated could be just explained in keyword documentation (or in deprecation description if it was added). Or did you have some special use case for this?

Agree. Read my proposal about description argument as a warning. So whatever written in warning pops up on top of HTML log.

There's no possibility to deprecate a library. That would need a separate issue.

I've added it: https://github.com/robotframework/robotframework/issues/3548

Quick comments after looking at this again:

I don't like adding a new decorator too much, but would be fine with enhancing the existing @keyword decorator. Perhaps it could be used like @keyword(deprecated='The message to show to user.').

Automatically deprecating arguments is really hard and I doubt that's worth the effort. Keywords can themselves log deprecation messages like logger.warn("Argument 'x' is deprecated and will be removed.") easily.

As I just commented #3548, I don't think deprecating a whole library has too much benefits. That can be discussed more in that issue, though.


Fix alter for partitions

Fix for https://github.com/vertica/dbt-vertica/issues/78

 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.Stanislav Lysikov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


added support for EPD2in13v2

Added support for the EPD2in13v2 display.
LUT values taken from:
https://github.com/waveshare/e-Paper/blob/master/RaspberryPi_JetsonNano/python/lib/waveshare_epd/epd2in13_V2.py

@googlebot I signed it!

@googlebot I signed it!

Hi! Thank you so much for the change. I'm trying to only scope improvements to the new version of the code that is Go modules compatible.
The announcement is https://periph.io/news/2020/a_new_start/
This would go in https://periph.io/news/2020/a_new_start/
As a nice side effect, the "experimental" bit is removed.

Hi! Thank you so much for the change. I'm trying to only scope improvements to the new version of the code that is Go modules compatible.
The announcement is https://periph.io/news/2020/a_new_start/
This would go in https://periph.io/news/2020/a_new_start/
As a nice side effect, the "experimental" bit is removed.

Ah, great news. So I will just make a new pull request to periph/devices, right?

Ah, great news. So I will just make a new pull request to periph/devices, right?

yep!

yep!


Allow volume control without having the app in foreground

Other Kodi remotes like Yatse allow for volume changes while media is being played back without having the app in foreground.
Solution: Register the playback with Android's media control API when showing a notification with controls and allow volume control this way.

I don't like this (assuming you're referring to controlling the volume through the physical volume buttons), not even as an option.
The volume buttons are too general, and Kore should only "hijack" them under strict conditions. Right now it's only when the remote panel is showing (and imo it should be kept that way), but i understand that it might also be useful on other screens, but never when Kore is not on the foreground.

I often times use Kore as a remote for music or videos running on my TV and think that it would be very convenient to quickly turn the volume up or down without having to unlock or turn on the device. I understand that there are people who do not like this, but having this as an option seems like a good idea to me. I don't see why this shouldn't at least be an option for people like me; maybe you could elaborate on why you think this is a bad idea.

Isn't it possible to add a custom volume slider to the general volume controls from the notification bar? I can't find any API that would allow us to do so. But that would really be awesome if we could simply register our volume control to the generic volume controls.

I'll try to explain my position: Kore is just one more app on your phone, and it's not even one of the most important (generally speaking. You might have an old phone dedicated to the remote, in which case this isn't true, but generally it is). Therefore it should behave as such and shouldn't takeover your phone in marginally related areas, even if it can handle requests in those areas, particularly when that can confuse users.
Regarding the "it could be an option" option, the problem is that we already have an option for that, which makes Kore handle the volume control buttons when it's on the foreground, and that should be kept. Extending that option to handling the volume buttons when in the background is a no go for me, and having another option specifically for that isn't something that i, personally, think should be done. It would be useful to some people, but on the whole i think would be detrimental to the experience.

Closing this, as i don't think that volume control without Kore being on the foreground is something that should be done.


Remove helper typedefs in favor of fixes

Now that developers don't have a choice to opt in to the helpers.dart members being available, I think these type definitions are detrimental to the developer experience. They increase the items in the global scope, introduce more choices, and increase inconsistency.
Let's help developers of existing packages/apps get to a consistent end-state sooner by leaning on data-driven fixes and help developers working on new packages/apps by having a more streamlined experience.

I'll let @srujzs (and @kevmoo and @sigmundch) speak to the desired API here, but do agree that the data-driven fixes give us more options in terms of migrating from dart:html => package:web. We can lean on data-driven fixes - which will patch up code with deprecation messages or missing type references - instead of having a transitory shim layer. Perhaps there's a use case for both? But it may be a clearer story to change the import statement and fix-up all code to the new package:web API.

Now that we have the dart fix, I don't see much value in this anymore. It'll lead to confusing conflicts, and it's better to deprecate them now before people start relying on them.


MapPoint does not select on first click.

Version:
0.4.0
I'm submitting a:

[X] bug report
[ ] feature request
Current behavior:
Clicking on map icons requires multiple clicks to select the element.
Expected behavior:
Clicking once on an icon should select an element.
Steps to reproduce:
Navigate to the directory and select a building with icons on the map.  Click once on an icon.  It will not be selected. Click on it once or twice more and it will be selected.
Additional information:
This is likely a bug in the ryersonlibrary/web-components library.

This was a problem with the ryersonlibrary/web-components library that was since resolved.


ROCm 2.4 cannot import tensorflow

System information

Ubuntu 18.04.1
kernel: 4.15.0-54-generic
ROCm 2.4-25
Python 3.6.8
tensorflow-rocm 1.13.3
miopen 1.8.1

Device

Radeon VII(vega20, 16G): VEGA20 0x1002:0x66AF 0x1002:0x081E 0xC1

Install

installed by pip3, not in virtualenv

pip3 install tensorflow-rocm

Describe the problem
Cannot import tensorflow,  which works when I played with ROCm 2.0, tensorlfow 1.12.0
import tensorflow as tf

Any other info / logs
Python 3.6.8 (default, Jan 14 2019, 11:02:34)
[GCC 8.0.1 20180414 (experimental) [trunk revision 259383]] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
Traceback (most recent call last):
  File "/home/zjunwei/.local/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "/home/zjunwei/.local/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "/home/zjunwei/.local/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
  File "/usr/lib/python3.6/imp.py", line 243, in load_module
    return load_dynamic(name, filename, file)
  File "/usr/lib/python3.6/imp.py", line 343, in load_dynamic
    return _load(spec)
ImportError: /opt/rocm/bin/../lib/librocfft-device.so.0: undefined symbol: _ZN8hip_impl13program_stateD1Ev

Hi @zjunweihit , can you provide the logs of the following command?
apt --installed list | grep rocfft

Hi @sunway513
apt --installed list | grep rocfft

rocfft/now <IP_ADDRESS> amd64 [installed,upgradable to: <IP_ADDRESS>]

upgrade ROCm to 2.6, since I get the notice today.
everything works well now :)

Thanks for the update :-)


fix(FloatingPanel): fix stuck during indetermine direction

iOS: if touch events triggered but touch direction not recognized by getDirection, then

FloatingPanel(FP) treat this touch as dragging and prevent it.
Until direction recognized and we try to scroll content, FP think it is not dragging then expectedly ignore
But the first touch move event is prevented, subsequent events are not active for content scrolling.

Reproduction:
https://react-vant-pr-627.surge.sh/~demo/components/floating-panel

Scroll panel to max anchor
Try scroll content
Get stuck sometimes.

好兄弟，我没时间review了，确定我明天就合完发版了

好兄弟，我没时间review了，确定我明天就合完发版了

辛苦了，draft 转 ready 通常表示ok
这条 PR 主要解决 touch 方向读不出来 ( useTouch 需要 MIN_DISTANCE )，而提前阻止了事件导致卡住的问题。

没人碰到FloatingPanel内的元素滚动失效了，滚动触发的是拖拽，

这两个属性开放很有必要的


Match request paths with wildcards

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #4265   👈

PR #4266

PR #4267

This comment was auto-generated by Graphite.

/retest

/retest


Re-add links to ApplicantTable

Acceptance Criteria

sample text

User Story

sample text

Story Points

sample text

Closed by #158


Use g value instead of f value to create sucessors in A*

This pull request fixes an error in the A* implementation and adds two separate test cases to prevent the issue I was facing in the future.
Fixes #267
Details
The A* implementation previously used these formulas to calculate the new g and f values for a node:
successor.g = previous.f + step_cost
successor.f = previous.f + step_cost + distance_to_end

The correct equations however use the previous.g value instead. See here, here, or here for reference.
g is the cost to reach the node from the start, f is g plus a heuristic for the remaining cost to reach the destination.
Using the cost + heuristic to calculate the cost for the next node does not make sense, the new f value would then contain the heuristic for the distance between the two nodes twice, resulting in a value that increases with the number of nodes in a path instead of the distance. This is why I added the more generic testcase.
I also changed the way the cost is passed to the add_successor function. Instead of passing q.g + step_cost, now only the step cost is passed. This is because q (and thus also q.g) is already passed to the function and the I think the new cost should conceptually be calculated inside add_successor instead of the call-site.

I'll try and get this merged this week. Thanks!


Instant Login

Hey, is there a way to add a way to type in your login data directly through the cmd-line?

We offer the -quickplay argument wich logs you in with previously entered credentials. See the generated json for that.
Currently we don't support login via arguments. PR is welcome if you can implement it :)


Changes to users API

We need to change the auth sidecar so it works as described in this: https://github.com/humio/cli/pull/54
We probably want to write the code in the auth sidecar in a way where we try using the new GraphQL query, but fall back to the old one. That way we can support both current and upcoming Humio versions with the same humio-operator release.

Not needed anyways.


Fix usage of hidden external node

Tree-sitter has had an update where hidden nodes consisting of just one terminal do not have the "absorption" feature that is silently present that you might have noticed. The problem is, with hidden nodes, this absorption does not allow the literal to be queried for, which was a pain point that was subtle but potentially inexplicable behavior. As such, we should just not have a node for this if we are concerned with a literal that is an anonymous node that is also an external - we can just directly reference this anonymous node if we want to hide it from the parse tree anyways (but still allow it to be queryable)

@stadelmanma the description does not make it clear, but without this change, generating the tree-sitter-fortran parse will FAIL on tree-sitter master (and thus the upcoming release).

Just looked up and read through the relevant PR on the main repo that prompted this change. Thanks for this!


VRTNU: "Unable to extract media element"

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.09.01 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
Belgium
Provide a description that is worded well enough to be understood
VRTNU (https://www.vrt.be/vrtnu/) changed its HTML & API and the current extractor doesn't work anymore.
I will create a PR with the fix ASAP.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--username', 'PRIVATE', '--password', 'PRIVATE', 'https://www.vrt.be/vrtnu/a-z/vrt-nws-journaal/2022/vrt-nws-journaal-vrt-nws-journaal-19u-20220913/']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.09.01 [5d7c7d6]
[debug] Python 3.10.7 (CPython 64bit) - Linux-5.19.7-arch1-1-x86_64-with-glibc2.36 (glibc 2.36)
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg 5.1.1 (setts), ffprobe 5.1.1
[debug] Optional libraries: Cryptodome-3.12.0, certifi-2021.10.08, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1670 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.09.01, Current version: 2022.09.01
yt-dlp is up to date (2022.09.01)
[VrtNU] Logging in
[VrtNU] Requesting XSRF Token
[VrtNU] Performing login
[debug] [VrtNU] Extracting URL: https://www.vrt.be/vrtnu/a-z/vrt-nws-journaal/2022/vrt-nws-journaal-vrt-nws-journaal-19u-20220913/
[VrtNU] vrt-nws-journaal-vrt-nws-journaal-19u-20220913: Downloading webpage
ERROR: [VrtNU] vrt-nws-journaal-vrt-nws-journaal-19u-20220913: Unable to extract media element; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/usr/lib/python3.10/site-packages/yt_dlp/extractor/common.py", line 670, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.10/site-packages/yt_dlp/extractor/canvas.py", line 317, in _real_extract
    attrs = extract_attributes(self._search_regex(
  File "/usr/lib/python3.10/site-packages/yt_dlp/extractor/common.py", line 1222, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)

In future, you don't need to open an issue if you are going to make a PR. Simply explaining the issue in the PR is sufficient


submit exercise 4

Most of the way there! Grouping by ward and summing units within each ward didn't make it into the function you wrote, though I see that you did experiment with it earlier in the notebook. You copied the function into the module, but then didn't call that version of the function in the notebook; there wasn't an import statement, so the function called in the notebook was the one you defined earlier in the notebook. Nearly there, just a few loose ends. And thanks for submitting it so nicely packaged up in a folder!


Update: KDE.Dolphin version 22.12.0 [FP-D]

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Dolphin
Dolphin

Version
22.12.0
22.12.0

Publisher
KDE e.V.
KDE e.V.

ProductCode

Dolphin

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 4731

This PR has no files.

PR removes YAMLCreate.ps1.

@stephengillie - ARP fields are incorrect; please approve https://github.com/microsoft/winget-pkgs/pull/92032 which fixes these ARP Entries.


Remove superfluous curly brace

Not sure where it came from or how no one noticed it :)

 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.

It's a duplicate of #1104.


Avoid unnecessary 301 redirects between pages in the Design System

What
Many of the links to other pages in the Design System omit the trailing slash.
When you omit the trailing slash from a URL in the Design System, the web server will redirect you to the version with the trailing slash – for example if you try to go to design-system.service.gov.uk/components you'll be redirected to design-system.service.gov.uk/components/.
This adds an extra round trip to the server which could otherwise be avoided if we ensure that all links include the trailing slash.
The broken link checker is currently configured to explicitly allow these redirects:
https://github.com/alphagov/govuk-design-system/blob/67ba57d6ae3816bdf57bcf273ad51ad2c6db57f8/lib/metalsmith.js#L287-L290
Disabling this would cause the link checker to flag links that redirect, causing builds to fail.
This would potentially mean more failing builds (and thus more back and forth before merging) whilst team members get in the habit of including the trailing slash, so we need to decide if that overhead is worth it for the performance gains.
Why
Avoiding the unnecessary redirect will improve performance, especially for users on slower connections.
For example, on a simulated slow 3G connection, the extra round trip for the 301 redirect takes approx 2 seconds, out of a total 5.77s (till DOMContentLoaded).

The performance impact is still relatively worthwhile but is objectively less noticeable for users on a fast connection – on a 120mb fibre connection the request takes 60ms out of a total 300ms (till DOMContentLoaded).
Who needs to know about this
Developers, anyone that regularly edits the content on the Design System
Done when

[ ] Decide if the overhead of needing to ensure all links include the trailing slash is worth the mild performance gain (for most users)
[ ] Redirects are disabled for the broken link checker
[ ] Redirects fixed throughout the site (by adding the trailing slashes) so the build passes

Given I (thought I…) had done most of the work, I've finished up the changes to get the tests passing and opened a PR… now we just have to decide if we actually want to do this or not!


[Clean up] Clean up some routing related classes

Codecov Report

Merging #8356 (d0aadf2) into master (aa44189) will decrease coverage by 34.80%.
The diff coverage is 63.46%.

@@              Coverage Diff              @@
##             master    #8356       +/-   ##
=============================================
- Coverage     70.91%   36.10%   -34.81%
+ Complexity     4253       81     -4172
=============================================
  Files          1637     1637
  Lines         85830    85796       -34
  Branches      12911    12909        -2
=============================================
- Hits          60864    30977    -29887
- Misses        20781    52302    +31521
+ Partials       4185     2517     -1668

Flag
Coverage Δ

integration1
?

integration2
27.56% <63.46%> (+0.04%)
:arrow_up:

unittests1
?

unittests2
14.19% <0.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...va/org/apache/pinot/spi/utils/CommonConstants.java
0.00% <ø> (-23.64%)
:arrow_down:

...rg/apache/pinot/core/transport/ServerInstance.java
38.29% <38.88%> (-9.92%)
:arrow_down:

.../pinot/server/starter/helix/BaseServerStarter.java
51.41% <69.56%> (-6.58%)
:arrow_down:

...a/org/apache/pinot/core/transport/QueryRouter.java
70.12% <80.00%> (-10.31%)
:arrow_down:

...roker/requesthandler/GrpcBrokerRequestHandler.java
75.67% <100.00%> (-2.90%)
:arrow_down:

...rg/apache/pinot/core/transport/ServerChannels.java
76.47% <100.00%> (-0.68%)
:arrow_down:

.../java/org/apache/pinot/spi/utils/BooleanUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/config/table/FSTType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/data/MetricFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...va/org/apache/pinot/spi/utils/BigDecimalUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1018 more

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 aa44189...d0aadf2. Read the comment docs.


Unable to create a custum worker name

Hello,
i Check this code and i unable adding a custum field
current : (%RANDOM%} |  (%COMPUTERNAME%}
how Add {%HWID%} ?
replace ( {%HWID%},HwId.Generate);
dll  used : https://github.com/saeidjoker/libc.hwid

The ETH current custom names are {RANDOM}, {COMPUTERNAME} and {USERNAME}. They are all currently replaced inside the miner itself so that it also works for the 'Remote Configuration' feature but if you want to add your own (and don't use the 'Remote Configuration' feature) then you could add that here outside the actual miner: https://github.com/UnamSanctam/SilentETHMiner/blob/1a76caea87796cd5e2dc6914ffedefb07a632d8f/SilentETHMiner/Resources/Program.cs#L207. Just make it replace {HWID} at RGetString("#ARGSTR").

thank you, that's exactly what i wanted, your the best X)


calico-node unexplained readiness/liveness probe fails

Hi,
Our calico-node pods on k8s suffer from Liveness/Readiness failed errors continuously. We can reproduce the case when scaling up or scaling down the deployments.
If we set the Liveness/Readiness timeouts to 60 seconds then we can prevent the fails. But we are trying to find the reason of the fails for Liveness/Readiness probe checks. When set timeout to 1 seconds we get too much fails. Also time to time this failed checks cause to restart of calico-node pods.
We have tried tried Debian 9, Ubuntu 20.04, Centos 7 as cluster OS but thought that is not related to OS. We also encounter the same fails rarely on the clusters which are installed to vmware infrastructure. The clusters which are located over vmware infrastructe also set 1 seconds for probe timeouts.

Current Behavior
There exist too much Liveness/Readiness probe fails.
Steps to Reproduce (for bugs)

Setup k8s cluster with kubespray on OpenStack environment.
Apply some deployments
Monitor the kubectl events.
There exist too much Liveness/Readiness probe fails.

Context
We got random connection errors from our pods and thought that is related this.
Your Environment

Infrastructure: OpenStack Victoria Release
Calico version: v3.20.2
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes v1.22.3 (installed via kubespray 2.17.1)
Operating System and version: Ubuntu 20.04.3 LTS (Kernel: 5.4.0-90-generic)
Container RunTime: containerd://1.4.11

In v3.20 we increased probe timeouts from 1s to 10s. Part of the reason is that in k8s 1.20, exec probe timeouts were fixed to actually respect the timeout values.
A 1s timeout is too low for loaded clusters: https://github.com/projectcalico/calico/pull/4788
What is the load like on your nodes? Can you try a value between 1s and 60s?

Hi @lmm thanks for your reply.
We also created another k8s cluster(s) with kubespray 2.17.1 [k8s version v1.22.3 and calico version: v3.20.2]
Setting timeouts to 1 second decrease the readiness/liveness probe fails but still exist.
We also tried to set timeout to 60 seconds but we still can reproduce the readiness/liveness probe fails when deploy ~400 pods at same time. (Scale 20 deployment from 1 pod to 30 pods)
We also have seen that the cpu resource is limited as below on default for calico-node ds:
        resources:
          limits:
            cpu: 300m
            memory: 500M
          requests:
            cpu: 150m
            memory: 64M

We have tried to set unlimited cpu-memory for calico-node pods and increase the master-worker nodes to 16 vCPU but still no chance.
 Can you share the kubectl describe output for a calico-node pod that has a failed probe? Is there anything in that calico-node's pod logs?

We have tried to set unlimited cpu-memory for calico-node pods and increase the master-worker nodes to 16 vCPU but still no chance.
If you remove both the requests/limits for calico-node, you'll get "best-effort" priority from the node.

Are your nodes simply overloaded?
Can you reserve some CPU for the system daemons?  https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/

Hi @lwr20 thanks for your response. We have also tried to remove both request-limits for calico-node but still same problem exist. The worker/master nodes are not fully loaded and we think it is not caused by cpu suffer.
We had to change the cni :(

We have also tried to remove both request-limits

This will most likely exacerbate the problem, but not reserving resources for calico/node (assuming it is a resource issue).
600 pods across 50+ nodes shouldn't be a problem though, unless they are all very resource hungry. As evidenced by your top output, it seems unlikely to be a node resource issue.

If we set the Liveness/Readiness timeouts to 60 seconds then we can prevent the fails. But we are trying to find the reason of the fails for Liveness/Readiness probe checks. When set timeout to 1 seconds we get too much fails.

Agree with the above. 1 second is way too short. 60 seconds should be more than enough, and it seems that with 60 seconds it passes, so that indicates it's not a totally broken node, just that things are moving slower than expected.

@caseydavenport @yusufgungor  I am observing something similar. Due to rapid autoscaling, my calico pods face probe failures because Bird is not able to connect to all its BGP peers.

my calico pods face probe failures because Bird is not able to connect to all its BGP peers.

Calico should eventually recover from this though, right? I believe the BGP check is more forgiving - it will eventually succeed so long as a single peer is established?

You said that if even a single peer is established, the probe should succeed. Why do you think so?

Because that's how the code works - we wait 30 seconds for all peers to establish, after which we reduce the requirement to a single node. it's explained a bit in the comment in the code here: https://github.com/projectcalico/calico/blob/master/node/pkg/health/health.go#L198-L201

Any thoughts on how I can debug further?

Looks like both readiness and liveness are failing - could you share what those probes look like in your cluster?
My best guess is that you just need to increase the cpu / memory limits on your calico/node pods for a cluster of your size, because increasing the timeout reduces the flakes suggesting resource starvation for the calico/node pods. (but not necessarily the entire node). Also, given you're running a cluster of 50+ nodes, you should make sure that you have Typha installed and that you're using either VXLAN or BGP with RR or peering to your top of rack (anything but full mesh, which performs poorly at around the 50-100 node mark).

@caseydavenport My resources are like this:
    Limits:       cpu:     2500m       memory:  2Gi     Requests:       cpu:      100m       memory:   1536Mi
This is my calico config
`calico_backend:
bird
cni_network_config:
{
"name": "k8s-pod-network",
"cniVersion": "0.3.1",
"plugins": [
{
"type": "calico",
"log_level": "info",
"datastore_type": "kubernetes",
"nodename": "KUBERNETES_NODE_NAME",
"mtu": CNI_MTU,
"ipam": {
"type": "calico-ipam"
},
"policy": {
"type": "k8s"
},
"kubernetes": {
"kubeconfig": "KUBECONFIG_FILEPATH"
}
},
{
"type": "portmap",
"snat": true,
"capabilities": {"portMappings": true}
},
{
"type": "bandwidth",
"capabilities": {"bandwidth": true}
}
]
}
typha_service_name:
none
veth_mtu:
1440`
Can you elaborate on your last point pls.

you should make sure that you have Typha installed

Typha is a scale component. You should install it for clusters over 50 nodes. Operator installs do this by default.

and that you're using either VXLAN or BGP with RR or peering to your top of rack (anything but full mesh, which performs poorly at around the 50-100 node mark).

Either use Calico in VXLAN mode (described in the docs) or disable the node mesh and configure explicit BGP peering with a route reflector (also described in the docs)

@tarun-asthana any update on this one?

Closing this issue due to inactivity.

@caseydavenport apologies I was away for a while. Need to reopen this thread.
My question is how do I track that the lack of typha is causing issues in my cluster right now.


[diag] Add new command to factory diags.

Commit adds new command to factory diag called radio.
- enable for enabling the interface to dfault mode,
- disable for disabling the interface

@abtink @zhanglongxia Thanks for review.


Added LavaSrc fields for yandex music tracks. Fixed getting links in …

Accidentally deleted the master branch :/

thanks


add al-rasheed university collage

just add my university domain

@devsadeq First stage of verification passed, official domain is alrasheedcol.edu.iq as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Pull request merged. Thank you!


⚠ Bofrost.at has degraded performance

In afbc8e8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1036 ms

Resolved: Bofrost.at performance has improved in 7bf1ba4.


File to import not found or unreadable: bourbon w/ npm scripts, node-sass`

Hey there,
I've got my deps set up as so:
  "devDependencies": {
    "eyeglass": "^0.8.2",
    "node-sass": "^3.4.2",
    "onchange": "^2.0.0"
  },
  "dependencies": {
    "bourbon": "^4.2.6"
  }

and I'm trying to use npm scripts to build this, though raw CLI fails as well,
  "scripts": {
    "sass": "node-sass --output-style compressed -o assets/css/ assets/css/src",
  },

and so far inside assets/css/src is my screen.scss file:
@import "bourbon";

// ...

When I run npm run sass, I get the following error:
{
  "formatted": "Error: File to import not found or unreadable: bourbon\n       Parent style sheet: /Users/giantrobotbee/Sites/giantrobotbee/content/themes/grb_theme/assets/css/src/screen.scss\n        on line 1 of assets/css/src/screen.scss\n>> @import \"bourbon\";\n   ^\n",
  "message": "File to import not found or unreadable: bourbon\nParent style sheet: /Users/giantrobotbee/Sites/giantrobotbee/content/themes/grb_theme/assets/css/src/screen.scss",
  "column": 1,
  "line": 1,
  "file": "/Users/giantrobotbee/Sites/giantrobotbee/content/themes/grb_theme/assets/css/src/screen.scss",
  "status": 1
}```

I'm running node 4.3.1. Any help is greatly appreciated.  Thanks!

@drmanitoba You likely need to add Bourbon to your node-sass includePaths. Have you read the section in our readme regarding Node-based asset pipelines?

Hey @tysongach, I was going off the line in your docs

If you’re using Eyeglass, skip to Step 3.

Which I took to mean "install Eyeglass, and that's it". Is this not so?

FWIW, I've updated the npm script to be the following
  "scripts": {
    "sass": "node-sass --import-path node_modules/bourbon/app/assets/stylesheets --output-style compressed -o assets/css/ assets/css/src",
}

but I'm still getting the same error when running npm run sass. I've tried running this same command from the CLI manually, and it produces the error as well.

@drmanitoba Ah, I didn’t see that you have eyeglass in there. I honestly haven’t had much experience with that yet, it’s new for us.
Perhaps @chriseppstein has some insight?

@drmanitoba: try --include-path

adding the path to your include paths in your plugin configuration did the trick for me
  plugins: {
    sass: {
      options: {
        mode: 'native'
        , includePaths: [
            'node_modules/bourbon/core'
        ]
      }
    }
  }
}

Closing this as we don’t have a response to the last two suggestions, but if this is still an active issue, please feel free to re-open.


Automatic residual criterion

This is a starting point for discussing solutions to #1222.
This PR adds a new stopping criterion AutomaticResidualNorm (name subject to change, perhaps Default...?), wrapping either ResidualNorm or ImplicitResidualNorm. Which of those two gets used depends on what is available by the solver. The aim is to by default reuse the already computed norms or dot products.

I won't work on that right now, so I will retire it for now.


MAINT: Fix CI/CD

Hi @rfahlberg , Changing the link in  contributing.rst  from https://dev.docs.pyansys.com/overview/contributing.html to https://dev.docs.pyansys.com/how-to/contributing.html will fix the error. It is causing because of the latest ansys/actions  link check.

 Hi @rfahlberg , Changing the link in contributing.rst from https://dev.docs.pyansys.com/overview/contributing.html to https://dev.docs.pyansys.com/how-to/contributing.html will fix the error. It is causing because of the latest ansys/actions link check.

@Revathyvenugopal162 Thanks for the hint, I also just figured this :).


[UI] Improvement: Keep Zoom Options Menu Open Until Explicitly Closed

Current Behavior
The zoom options menu (minimize, maximize, fit, full) automatically collapses after selecting any option. This requires users to reopen it for additional adjustments
Screencast from 29-12-24 10:58:13 PM IST.webm
Desired Behavior
The menu should remain open until the user explicitly clicks the "X" to close it.

Implementation

Acceptance Tests

Mockups

Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I'd like to work on this issue. Could it be assigned to me?


addIDTokenDidChangeListener not called when the ID token expires

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.5.1
Firebase SDK version: 7.8.0
Installation method: Swift Package Manager
Firebase Component: Auth

[REQUIRED] Step 2: Describe the problem
By reading these docs for addIDTokenDidChangeListener:

Registers a block as an "ID token did change" listener. To be invoked when:

The ID token of the current user has been refreshed

I understood that every time the ID token is expired, the callback will be executed and I can read the new ID token.
It doesn't seem to be the case. I am using only the callback to get the token and use in every back-end call. On launch, everything works as expected but if the app is running for a while (around 30 minutes or so), the app has only the expired token and this results in Error: Firebase ID token has expired. Get a fresh ID token from your client app and try again on the back-end.
I also read this bit (although it's pretty old and I am not sure if it's actual nowadays): https://github.com/firebase/firebase-ios-sdk/issues/245#issuecomment-328163934

Also, just in case you weren't already aware, all listeners are triggered by local events only. Even after  #249  is fixed, user linking account on one device won't directly trigger a listener in another app running on the same device, or a listener in any app running on another device.

And got a bit confused by the all listeners are triggered by local events only part. None of this is mentioned in the docs.
Steps to reproduce:

Use Auth.auth().addIDTokenDidChangeListener
Wait for the token to expire
There is no callback

Relevant Code:
Auth.auth().addIDTokenDidChangeListener { auth, user in
      if let user = user {
        user.getIDToken { idToken, error in
         /// store the token in memory to be sent with every HTTPS request

Hi @NeverwinterMoon, thanks for reaching out. The token will not automatically refresh itself on its own when it expires. (The exception is that it will automatically refresh if you're connected to another service like Cloud Firestore or the Realtime Database). Instead of using the change listener, I would suggest calling user.getIDToken every time you make a call to your back-end. This function will refresh the token behind the scenes if necessary.


Chrome 37 IndexedDB stores incorrect content type for blobs

Hello from PouchDB. :)
Just a heads up, in case you weren't aware of this bug: https://github.com/pouchdb/pouchdb/issues/2701 and https://code.google.com/p/chromium/issues/detail?id=408120.
From Chrome 38+, blobs will be stored just fine, exactly like IE and Firefox. In the meantime, 37 is out there in the wild, and it's got this bug. If you'd like to detect blob support, here's the code we use, which should work on Firefox, IE, and Chrome 36-38.

I came across the lack of Blob support in my own testing (see #380) on an Android 4.4.4 Samsung device (UA string claims "Chrome/28").  I worked around it in my vendored copy of localForage with a UA sniff marking IndexedDB as unsupported in any Chrome less than 38.  This effectively makes localForage use the WebSQL backend, which serializes blobs for storage.  I suppose an alternative would be to enable the serializer for the IndexedDB driver in this case (which would be effectively the same as to the PouchDB approach).
I didn't submit a PR as I'm not the UA sniff is the right approach (better approaches have already been listed), and I assume not everyone finds Blob support mission-critical as I do.

@sheppard Yeah sorry, I did not follow up with the localForage fix after reporting this. But basically our "blob support" check looks like this now: https://github.com/pouchdb/pouchdb/blob/1093c845bac9550baf8b0394d59fed3e14efe185/lib/adapters/idb/idb-blob-support.js
Reason being, there were actually more bugs that popped up since v38, and blobs are only reeeeaaally supported in v43 (see state of binary data in the browser for the gory details).

Found some time tonight, so here we go: https://github.com/mozilla/localForage/pull/382 :smiley:
In retrospect, I'm kind of flabbergasted at the number of hacks necessary to get blobs to work in IndexedDB. Might make more sense to just take that _checkBlobSupport() function and use it to downgrade to WebSQL... :expressionless:

Wow nice work, also amazed by the number of problems with blob in IndexedDB, a good read: https://github.com/nolanlawson/state-of-binary-data-in-the-browser

Yes, thanks for all your work in this area, @nolanlawson.

this has been fixed for awhile


LeoJS does not recognize multiple @language directives

One of my common outline patterns is:
@language rest
notes about an issue
@language python

followed by python child nodes relating to the issue.
Bug: LeoJS colorizes the children with @language rest.
Instead, ambiguous nodes (nodes containing multiple @language directives) should have no effect on the node's descendants.
This is a serious bug from my point of view. However, there are several easy and obvious workarounds.

Thanks for this report! :)
I will make a minimal Leo file with only 2 or 3 nodes and try to compare the behavior between Leo, LeoInteg and LeoJS for cases like this, or similar to this. (E.g. with an @other between the @language directives, etc... )
And I'll fix it and/or report here inconsistencies or further questions that may arise from my experiments.

@boltex Thanks for your comments. Imo, part 2 of this issue should be fixed for LeoJS 1.0.
Part 1: Desktop Leo can color individual lines with different language within the same body text. That feature might be difficult or impossible in vs-code.
Part 2: The logic that controls whether @language directives affect descendant nodes should have nothing to do with vs-code. I'm surprised that LeoJS has not already duplicated that logic.

@boltex There two workarounds for the pattern:
@language rest
notes about an issue
@language python

Workaround 1: Put the notes in a separate node, with a single @language rest directive.
Workaround 2: Eliminate both @language directives and convert the notes to Python comments.
In other words, this issue will not prevent me from using LeoJS :-)

Part 2: The logic that controls whether @language directives affect descendant nodes should have nothing to do with vs-code. I'm surprised that LeoJS has not already duplicated that logic.

You are right about this, perhaps I thought "vscode can only assign 1 language to an editor, so I might stop looking for @language when I reach the first @language directive in a body text". When in fact I should settle on the LAST @language directive in a node to decide it's language (so that it affects its descendants properly)
Thanks again for your insights !

@boltex I thought perhaps you had made such an invalid assumption. Restoring Leo's exact coloring code is likely the only way to fix this issue.

@edreamleo I just tested in Leo itself : Having multiple @languages in a node makes its descendant have no set language. (plain text)  Is that the intended behavior? (just want to make sure before I make it so in LeoJS)

@boltex The intended behavior is that an ambiguous node (a node with multiple @language directives) does not affect the syntax coloring of its descendant nodes. So whether descendant nodes are colorized depends on:
a) the first (moving up the tree) non-ambiguous ancestor node that contains an @language directive.
b) the default (target) language in effect for the outline.
Case a) is even more complex for cloned nodes. Imo, both LeoInteg and LeoJS should follow Leo's code as closely as possible, starting with the node BaseColorizer.updateSyntaxColorer & helpers.
Defaults
All outlines I use have a default coloring of either @language rest or @language python.
However, leoSettings.leo  has a node @string target-language = plain which looks like no default language is in effect, but my myLeoSettings.leo has @string target-language = python.
In short, it's complicated :-) Please feel free to ask more questions.

@edreamleo 😄 I just looked at leoColorizer.py to figure out the way Leo actually does it, and then easily fixed it in devel branch with commit 66fc45440ded9201db209f8df1f0b910037e5401
--> Thanks for beta-testing LeoJS and finding details like this !!

@edreamleo I'll fix it in leoserver too

@boltex I'm glad the fix was straightforward.


Strange behavior when setting AWS profile in sst.config.ts

Version: SST ❍ ion 0.0.296
I'm attempting to set the AWS profile as follows:
export default $config({
  app(input) {
    return {
      ...
      providers: {
        aws: {
          region: "us-east-1",
          profile: "PROFILE_NAME",
        },
      },
    };
...
});

As far as I can tell, this works with the exception of ACM / Route53 related operations.
The following works fine.
new sst.aws.Router("Router", {
    ...
});

The following fails and produces the subsequent error.
new sst.aws.Router("Router", {
    domain: {
        name: "DOMAIN_NAME",
        dns: sst.aws.dns({
            zone: "HOSTED_ZONE_ID"
        })
    },
    ...
});

|  Error       AwsProvider sst:us-east-1 pulumi:providers:aws resource 'AwsProvider.sst.us-east-1' has a problem: No valid credential sources found.
Please see https://www.pulumi.com/registry/packages/aws/installation-configuration/ for more information about providing credentials.
NEW: You can use Pulumi ESC to set up dynamic credentials with AWS OIDC to ensure the correct and valid credentials are used.
Learn more: https://www.pulumi.com/registry/packages/aws/installation-configuration/#dynamically-generate-credentials
j
×  Failed
   AwsProvider sst:us-east-1
   pulumi:providers:aws resource 'AwsProvider.sst.us-east-1' has a problem: No valid credential sources found.
Please see https://www.pulumi.com/registry/packages/aws/installation-configuration/ for more information about providing credentials.
NEW: You can use Pulumi ESC to set up dynamic credentials with AWS OIDC to ensure the correct and valid credentials are used.
Learn more: https://www.pulumi.com/registry/packages/aws/installation-configuration/#dynamically-generate-credentials

The issue goes away as soon as I set the profile name in the current shell session.
export AWS_PROFILE=PROFILE_NAME

Seeing this too after upgrading to 0.0.345


fix: disable keep alive

doesn't seem to matter
the envoy is simply slow to respond with 7.x+ firmware


Update GitHub Pages deploy guide

What kind of changes does this PR include?

[ ] Minor content fixes (broken links, typos, etc.)
[X] New or updated content
[ ] Translated content
[ ] Changes to the docs site code
[ ] Something else!

Description

Closes #108
Updates the GitHub Pages deploy guide — hopefully making it simpler!

This looks amazing, @delucis , thank you! (I mean, it doesn't start with a warning anymore 😅  , so already much friendlier forjust  that reason alone!)
And, we already have someone on the job testing out how well someone who doesn't already know this stuff can follow the instructions.
GO TEAM! 🎉

Trying and failing to follow my own instructions so revision of this guide in the works… 😅

OK, made a couple of tweaks based on my experiences and I think this should now work. I’d be curious to hear from anyone else who has a chance to try to follow these instructions.

OK, WHEW.... do I have UPDATES!
So thank you both @delucis @tony-sull ... I did get not one, but two repositories successfully deployed! 🥳
Yes, making a repository actually named sarah11918.github.io helped, but Chris' instructions for setting base worked for another repository too. (Didn't need to know about GH Actions at all, so omg YES, I think we have a winner!)
BUT 2 things to report, in order to know whether this should affect documentation at all:

With the base: set, when I open my repo in CodeSandbox, I get this screen when the dev server starts. (Clicking the link to the suggested base works fine, so I'm assuming that's not a problem for people in general?)

I needed to npm run build my site FIRST, before my gh-pages branch showed up in the Pages tab of Settings.

Maybe this sounds ridiculous to you both, but until recently, I honestly never "built" my site... I just let Netlify do it. And, on CodeSandbox/StackBlitz etc, there's almost no point in ever building... you just run in dev mode. It's only recently I realized that if I did npm run build I could see messages and stuff, and make sure things DID build before letting Netlify fail and reading those logs! 😅
So, I think that was where I was getting messed up before. I was getting a new astro starter from astro.new in CodeSandbox (and tried also in StackBlitz), commiting those starters back to a new repository in Github, then trying to follow the instructions (editing astro.config.mjs and adding the workflow file). BUT, without ever having ever built the site, it wasn't working. I don't even know what made me think of building... I just know that worked.
So, I don't even know whether that is something to document? Is that too "Sarah" to even mention? Anyway, just wanted to share that that is what  eventually worked for me, so we can decide whether it's noteworthy.

Thanks for trying this Sarah!
Were you committing dist? Otherwise I'm wondering if running npm run build was actually unrelated/a fluke? The GitHub action builds the site for you. It's basically Netlify except much more fiddly.
So you think this ok for now and we can revisit as we get reports of it not working?

I do think this is OK to merge now!

Can we LGTM this, so I can make other edits to this page without resolving conflicts!  😅


[Submission]: Grover controlled-diffuser (CUs)

Project name
Grover controlled-diffuser (CUs)
Github repo
https://github.com/albayaty/grover_controlled_diffuser
Description
The CUs is a new quantum diffusion operator for Grover’s algorithm to search for all correct solutions for Boolean oracles.
Email
<EMAIL_ADDRESS>Alternatives
There are no alternatives to this project.
License
Apache License 2.0
Affiliations
The Electrical and Computer Eng. Dept. at Portland State University.
IBM maintenance status

[ ] This project is officially maintained by IBM Quantum

Group
applications
Labels
Algorithms, Circuit building tool, Paper implementation
Documentation
No response
Website
No response
Reference paper
https://doi.org/10.21203/rs.3.rs-2997276/v1

Closed as per https://github.com/Qiskit/ecosystem/pull/765#issuecomment-2294917537


Cannot set type of column because  IColumnType detected undefined  Type 'string' is not assignable to type 'IColumnType | undefined'

Hi,
i hav datatable that need using html type column. On version 3.1.1 using angular 16 istill use html column type. but when i upgrade using version 3.2.0 i got issue with  IColumnType.
this my table settings
 tableSettings =  {
    columns: {
      status: {
        title: '',
        class:'column align-center',
        type:'html'
      },
      id:{
        title: 'ID',
        class:'column align-center'
      },
      name:{
        title: 'Name',
        class:'column align-center'
      }
    },
    editable:false,
    pager:{
      perPage:10
    },
    actions:{
      add:false,
      edit:false,
      delete:false,
    }
 }

and this what i get
Types of property 'columns' are incompatible.
    Type '{ status: { title: string; class: string; type: string; }; id: { title: string; class: string; }; name: { title: string; class: string; }; }' is not assignable to type 'IColumns'.
      Property 'status' is incompatible with index signature.
        Type '{ title: string; class: string; type: string; }' is not assignable to type 'IColumn'.
          Types of property 'type' are incompatible.
            Type 'string' is not assignable to type 'IColumnType | undefined'. [plugin angular-compiler]

how i suppose deal with it. Any change that type cannot using string anymore?
ANGULAR 17.0

I think the problem is that you don't specify the type annotation explicitly.
 It does not recognize that the string you specify is actually compatible to IColumnType.
From the point of view of the compiler, your tableSettings variable does not even have the type Settings. I think it should be sufficient to explicitly annotate the type (tableSettings: Settings).
Please try this first, if it doesn't work, we'll find a solution.

Sorry too late for me to reply.
thank you so much for your response. it's worked.
I think after update to angular version 17 they made strict on annotation explicitly. For me who doesn't give too much care on annotation data type need change habit.


Export Variable's category and grouping (Advanced Exports) with _get_property_list() are not working in Visual Script

Godot version:

Godot 3.2.3-stable
Godot 3.2.4-beta3
Godot 4 @ d834789

OS/device including version:

Issue description:

I tried to add categories and groups for my export variables with the _get_property_list() function as documented here. I can do it in GDScript but not in Visual Script with the exact same code.
In Godot 3.2.3-stable and 3.2.4-beta3:
It's not working at all. And when I closed and reopened the project again, the "make tool" button in the Visual Script editor which was previously set to on would always be off after I reopened the project. I can't add any node to the Visual Script editor unless I disconnected the script from the scene node. Otherwise, it will give me this error:

In Godot 4 @ d834789:
It works partially as the variable shows up in the inspector tab. However, the category and group don't show up at all:

I expect it to work like GDScript and doesn't give me errors:

Steps to reproduce:

Open the script.
Add the _get_property_list() function.
Calling the functions to add categories, groups, and desired properties (variables) to the inspector tab according to the document here.
Check the inspector tab.

Minimal reproduction project:

For Godot 3:
test3.zip
For Godot 4 (since some codes have been changed - tool >>> @ tool):
test4.zip

This issue still presents as of Godot v3.4.3.rc2.official [0ea54d07f] and Godot v4.0.alpha2.official [79077e6c1], as shown in the screen recordings below:
Godot v3.4.3.rc2.official [0ea54d07f]:
https://user-images.githubusercontent.com/1403194/154624970-8c51d54d-a8cc-4807-bf80-dd81b7aceaf4.mp4
Godot v4.0.alpha2.official [79077e6c1]:
https://user-images.githubusercontent.com/1403194/154625043-f9d6142d-a8df-4c86-a346-00e886ce5409.mp4
I also upload a new reproduction for Godot 4 as the old one doesn't compatible with the latest Godot 4 version (the engine would crash):
Test4New.zip


Refactor to allow caching of methods by name and arguments

Coverage increased (+1.5%) to 92.079% when pulling ddb7ddc235879ff342b433e5dae1dc65c6e24f1a on lyncodev:master into a869fe87c60d675c7d8799c5d5989d2b9d8664fa on jtwig:master.


unable to find genes when export to SPRING object

Hi scanpy team,
I convert Seurat obj to anndata with:
mda_ad <- Convert(from = mda, to = "anndata",filename = 'mda_day27_ad.h5ad')

mda_ad
AnnData object with n_obs × n_vars = 6039 × 19331
obs: 'n_genes', 'n_counts', 'orig_ident', 'percent_mito', 'S_Score', 'G2M_Score', 'Phase', 'old_ident', 'res_1_2'
var: 'gene.mean', 'gene.dispersion', 'gene.dispersion.scaled'
obsm: 'X_pca', 'X_tsne'

Then I run as scanpy's tutorial https://github.com/theislab/scanpy_usage/blob/master/171111_SPRING_export/SPRING_export.ipynb
to export SPRING, however, I was unable to find no response when I enter a gene in the web browser.
I have all required files in the folder.

Any suggestion how to solve it?
Thanks!

I fear you have to address the Spring authors directly, @swolock, for instance, who wrote the exporter.
If it continues to be buggy, you might also look at cellxgene, which is very professionally developed and directly reads in Scanpy's h5ad files.

Hi @MichaelPeibo,
It's possible there's an unknown SPRING bug behind your issue, in which case the easiest way for me to help would be for you to share your SPRING folder with me (if this is possible). But before doing that, answers to the following questions might help me narrow it down:

Can you confirm you're using Python 2 to start the local server?
Would you mind sharing the output from the console/terminal that is running the server?
What is the exact URL you entered?

And @falexwolf -- thanks for referring the issue to me!

Hi @falexwolf Thanks for pointing it out.
Hi @swolock
I went through it today.
I guess it may be due to the multiple web server error when I first start it?
Or maybe both my server and me need a rest and restart.....
Sorry to bother, very nice interactive tool!!!

@falexwolf @swolock
Hi, I recheck my web history, I doubted that it is due to old springViewer I used.
I followed this tutorial https://github.com/theislab/scanpy_usage/blob/master/171111_SPRING_export/SPRING_export.ipynb
and it gave the link is http://localhost:8000/<SPRING_INSTALLATION>/springViewer.html?<Relative_Path_To_SPRING_PROJECT>
However, I got through it with http://localhost:8000/springViewer_1_6_dev.html?


Doesn't Seem To Work On iOS8?

Hi, first off... cool plugin! I am considering using it in an app I am working on, however while it works great on just about every other device I have tried, it doesn't seem to respond on iOS8. The slider shows up, and I can still see a glow when I touch/tap the handle of the pathslider, but it won't actually let me drag the handle at all. I noticed it has the same issue on my app prototype as well as on your hosted pathslider demos, so I don't believe it's something specific I have done...
Any ideas why this is or how it can be fixed?

Hi @sddw!
I don't own any iOS devices (does an iPad 1 count?), so it is difficult for me to troubleshoot what the issue might be here. Does it work in a desktop browser for you, and/or do you see any errors in the console?
As you can see, I haven't touched this code in over 3 years, and it is still in the alpha stage of work... so it might take a bit more work to make it production-ready.

I don't see any console errors (on my laptop at least... not sure how to check the console on an actual iOS device?). It works great on my Windows 7 laptop (various browsers), two different Android devices, an iOS7 device, and an OSX desktop. I haven't tried it on more devices than that at this point, but right now the only one with issues is iOS8. When you try to grip a handle it scrolls the page instead of the handle itself.
I'm trying some tinkering with various settings but so far no luck. And as I mentioned it seems to have the same issue even on the demo sliders you have setup.
I am using it in conjunction with jQuery Mobile, and currently have the pathslider initializations tied to the "pageshow" event trigger:
$( document ).on( "pageshow", ...
$(function($){
$("#slider").pathslider({
points     : [ 8,85,25,-100,-25,-100,258,85 ],
value      : 50,
rotateGrip : true,
tolerance  : 3,
range      : 30,
curve      : { width:8, color:"#e9e9e9", cap:"round" }
});
});
...so far this has worked best, but still not on iOS8


Output files

Hi,
Our customer is asking if the following results are available in the output. If so, can you tell me in which files I can get the results. Thank you.

Genes (transcripts) and their expression values across all cells - if this is not possible - then at least median (or average) expression value of the genes in each cluster of the cells.

The list of DE genes for each cluster vs every other cluster.
The DE info to include p-values (or FDR/adj pvalue) and fold change or log2 fold change.

The number of captured cells, genes per cell info.

Thanks for @lishuangshuang0616 for help! The answers are as below.

In the folder "output/filter_matrix", there are 3 files. "barcodes.tsv.gz" is cell ID list. "features.tsv.gz" is gene ID list. "matrix.mtx.gz" is expression values for genes in cells (3 columns: gene, cell, expression).

The files can be read by Seurat:
# https://satijalab.org/seurat/articles/pbmc3k_tutorial
library(Seurat)
data <- Read10X(data.dir = "output/filter_matrix",gene.column = 1)

Another file 'output/filter_feature.h5ad' can be read by Scanpy:
# https://scanpy-tutorials.readthedocs.io/en/latest/pbmc3k.html
import scanpy as sc
data = sc.read_h5ad('output/filter_feature.h5ad')

The file "03.analysis/marker.csv" can be referred for this purpose.

Differentially expressed genes in each cell category are in this table. Each gene was tested for differential expression between each cluster and the rest of the samples.
For the columns of the table:

The P-val value is a measure of the statistical significance of expression differences, and the smaller the P-val value, the higher the similarity to theory.
p_val_adj is the adjusted p-value based on the bonferroni correction using all genes in the dataset.
avg_log2FC refers to the log value of the ratio of the expression of a gene in a cluster to the average expression in other cells.
pct.1 is the proportion of cells that detect this gene expression in the current cluster cells.
pct.2 is the proportion of cells that detect this gene expression in other cluster cells.

Estimated number of cell can be found in file "output/metrics_summary.xls".

The file "03.analysis/raw_qc.xls" contains the number of genes (column "n_genes_by_counts") and the number of transcript UMIs (column "total_counts") in each cell. One can also refer to the answer 1 for this info.
The final report "output/xxx_scRNA_report.html" also include most of the above information with multiple plots.


Remove "Off" from second currency in settings

Leave only 2 options: USD (Default) and BTC.
https://zpl.io/VYg5RpE

Current implementation

checked


Timesheet - 18/06/2021 - Dmitry Mugtasimov

Task 1
Produce test tasks potential Senior Developer candidates
Proof of Work

Confirm with Bucky, please

Time Spent
1 hours

Total Time Spent
1 hours
Account Number
757d598308bf1e2943bd1a9fc34ae7b8951ca864d64228b59e62614b27ddefc4

Any update on this @dmugtasimov ?

@manishram updated


Implementing DSProxy (testing internally)

Note: to plan out the fee to yam treasury implementation.

I can help with this after I finished a few other things this week, @ElmoArmy let me know if you want a second pair of eyes on that and we can have a meeting for that.

https://github.com/paulrberg/prb-proxy


Webhooks API

As a developer, I want full access to the Kazoo Webhooks API.

https://2600hz.atlassian.net/wiki/display/APIs/WebHooks


Update firstTexture

Is threre any way to update firstTexture  if it is already set and pafeFlip is doesn't done yet?
I try with getFirstPage().deleteAllTextures(); but it produces memory leak  and after many pafeFlip memory app increase a lot.

I think you can try
page.setFirstTexture(mBitmap);

It will set the first texture with given bitmap. If the page is not flipping, you can call PageFlip.drawPageFrame(); to update  screen after you set the first texture

Yes, that is what I have done. But, if I set First Texture before, I can't update it again by that way. So, when flip start, it shows the first image instead of the second one.