Docker image cypress/included crashes (7.0.0)

I think this is related to https://github.com/cypress-io/cypress-docker-images/issues/472
according to https://github.com/cypress-io/cypress/issues/15814, 7.0.1 should be released
however, docker image 7.0.1 is missing:
https://hub.docker.com/r/cypress/included/tags?page=1&ordering=last_updated
The error I'm getting with the 7.0.0 docker image:
$ cypress run --project ./frontend
(node:1521) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `Cypress --trace-warnings ...` to show where the warning was created)
(node:1521) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
====================================================================================================
  (Run Starting)
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:    7.0.0                                                                              │
  │ Browser:    Electron 89 (headless)                                                             │
  │ Specs:      1 found (e2e.spec.js)                                                              │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  e2e.spec.js                                                                     (1 of 1)
  Error handling
We detected that the Chromium Renderer process just crashed.
This is the equivalent to seeing the 'sad face' when Chrome dies.
This can happen for a number of different reasons:
- You wrote an endless loop and you must fix your own code
- There is a memory leak in Cypress (unlikely but possible)
- You are running Docker (there is an easy fix for this: see link below)
- You are running lots of tests on a memory intense application
- You are running in a memory starved VM environment
- There are problems with your GPU / GPU drivers
- There are browser bugs in Chromium
You can learn more including how to fix Docker here:
https://on.cypress.io/renderer-process-crashed
We detected that the Chromium Renderer process just crashed.
This is the equivalent to seeing the 'sad face' when Chrome dies.
This can happen for a number of different reasons:
- You wrote an endless loop and you must fix your own code
- There is a memory leak in Cypress (unlikely but possible)
- You are running Docker (there is an easy fix for this: see link below)
- You are running lots of tests on a memory intense application
- You are running in a memory starved VM environment
- There are problems with your GPU / GPU drivers
- There are browser bugs in Chromium
You can learn more including how to fix Docker here:
https://on.cypress.io/renderer-process-crashed
  (Results)
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Tests:        0                                                                                │
  │ Passing:      0                                                                                │
  │ Failing:      1                                                                                │
  │ Pending:      0                                                                                │
  │ Skipped:      0                                                                                │
  │ Screenshots:  0                                                                                │
  │ Video:        true                                                                             │
  │ Duration:     0 seconds                                                                        │
  │ Spec Ran:     e2e.spec.js                                                                      │

We have released a fix for this in 7.0.1 http://github.com/cypress-io/cypress/releases/tag/v7.0.1

Thanks @bahmutov! 👍🏼


Add support for winit 0.20-alpha via feature toggle

Winit's next version introduces many breaking changes. This PR adds support for 0.20 via a feature toggle while keeping backwards compatibility with version 0.19 by default.

Thanks! :smile:
Upgrading to winit 0.20 is definitely something we want to do, but I'm a bit unsure at this point about supporting both winit versions at the same time...other crates don't seem to do it and it's going to be much more complicated to maintain.

The intent was to only support 0.19 until 0.20 left the alpha phase. This would allow people to start using imgui-rs with winit 0.20 sooner rather than later while not disrupting others with the 0.20 alpha churn. I didn't clarify that on the initial PR, so apologies on that front.

I've given this some more thought and think we need to support both versions at least temporarily.
The main reason for supporting both versions is that gfx-rs is still on 0.19, so we can't just upgrade to 0.20. I've got a hunch we'll need to drop gfx-rs support soon completely because it's not maintained actively...


How to install applications from AppStore?

Hi,
How to install applications from Apple App Store?
It is giving me error when i try log into my iCloud account.

I need install Xcode and Command Line tools.
Thanks.

Duplicate of #3617

If we run in x86_64 using Rosetta, it works?


Regex LDAP Authenticator does not work

Regex LDAP Authenticator does not work in version 3.6.0.
I have a server configured with Samba DC. I am trying to configure this authenticator. Everything works without SSL, but if I turn it on (changing all the related parameters), I press the "Test" button, an error appears:
Test failed: option error
In the server logs:
Traceback (most recent call last):
  File "/usr/share/openuds/uds/core/util/ldaputil.py", line 148, in connection
    l.set_option(ldap.OPT_X_TLS_NEWCTX, 0)  # type: ignore
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3/site-packages/ldap/ldapobject.py", line 698, in set_option
    return self._ldap_call(self._l.set_option,option,invalue)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3/site-packages/ldap/ldapobject.py", line 128, in _ldap_call
    result = func(*args,**kwargs)
             ^^^^^^^^^^^^^^^^^^^^
ValueError: option error
ERROR 2023-07-13 13:53:01,193 ldaputil connection 156 Exception connection:
Traceback (most recent call last):
  File "/usr/share/openuds/uds/core/util/ldaputil.py", line 148, in connection
    l.set_option(ldap.OPT_X_TLS_NEWCTX, 0)  # type: ignore
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3/site-packages/ldap/ldapobject.py", line 698, in set_option
    return self._ldap_call(self._l.set_option,option,invalue)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3/site-packages/ldap/ldapobject.py", line 128, in _ldap_call
    result = func(*args,**kwargs)
             ^^^^^^^^^^^^^^^^^^^^
ValueError: option error

Why can this error occur?

Which ldap package do you use? python-ldap.
I have it working fine on Debian, with python-ldap module, (BTW, using GNUTLS library for building python-ldap)...
Try from an python or an ipython, something like this:
Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.12.0 -- An enhanced Interactive Python. Type '?' for help.
In [1]: import ldap
In [2]: ldap.OPT_X_TLS_NEWCTX
Out[2]: 24591
In [3]: ldap.version
Out[3]: '3.4.3'
It's something related to the python-ldap library by sure...
You will get probably same output (because if the variable is not defined, it will probably get an error).
I think the problem could come that you may be using "openssl" python library (the one used by python-ldap), and i have done it with gnutls version.
look:
~/projects/uds/4.0/openuds/apps-server_enterprise/ ldd ../../env/lib/python3.11/site-packages/_ldap.cpython-311-x86_64-linux-gnu.so
linux-vdso.so.1 (0x00007ffe4b16a000)
libldap-2.5.so.0 => /lib/x86_64-linux-gnu/libldap-2.5.so.0 (0x00007fdd239bf000)
liblber-2.5.so.0 => /lib/x86_64-linux-gnu/liblber-2.5.so.0 (0x00007fdd239af000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdd237ce000)
libsasl2.so.2 => /lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007fdd237b1000)
libgnutls.so.30 => /lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007fdd23400000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdd23a52000)
libp11-kit.so.0 => /lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007fdd2367b000)
libidn2.so.0 => /lib/x86_64-linux-gnu/libidn2.so.0 (0x00007fdd2364a000)
libunistring.so.2 => /lib/x86_64-linux-gnu/libunistring.so.2 (0x00007fdd2324a000)
libtasn1.so.6 => /lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007fdd23635000)
libnettle.so.8 => /lib/x86_64-linux-gnu/libnettle.so.8 (0x00007fdd231fc000)
libhogweed.so.6 => /lib/x86_64-linux-gnu/libhogweed.so.6 (0x00007fdd231b3000)
libgmp.so.10 => /lib/x86_64-linux-gnu/libgmp.so.10 (0x00007fdd23132000)
libffi.so.8 => /lib/x86_64-linux-gnu/libffi.so.8 (0x00007fdd23627000)
This is my python-ldap bynary module (you can see, it use "libgnutls".
If yours is SSL, the problem are the Ciphers. Default settings file uses very strong cyphers, but using GNUTLS naming convention, here:
https://github.com/VirtualCable/openuds/blob/bd7faf786747b740f3e90c8921402870e049ea9c/server/src/server/settings.py.sample#L176
You can try, first, as single thing, commenting out this line:
https://github.com/VirtualCable/openuds/blob/bd7faf786747b740f3e90c8921402870e049ea9c/server/src/uds/core/util/ldaputil.py#L146
Or removing for testing the full "set-ciphers" part of the code.
Please, also note that if the ciphers are not defined on settings file, these are the ones used (again, for GNUTLS):
https://github.com/VirtualCable/openuds/blob/bd7faf786747b740f3e90c8921402870e049ea9c/server/src/uds/core/util/ldaputil.py#L55
Hope this helps.
Regards

Yes, i thing the problem is that your libldap is compiled against libssl.
Look, from an altlinux10:
[root@altlinux ~]# ls -la /usr/lib64/python3/site-packages/_ldap.cpython-39.so
-rw-r--r-- 1 root root 74560 Jul  6  2020 /usr/lib64/python3/site-packages/_ldap.cpython-39.so
[root@altlinux ~]# ldd /usr/lib64/python3/site-packages/_ldap.cpython-39.so
linux-vdso.so.1 (0x00007ffc6b9f7000)
libldap_r-2.4.so.2 => /usr/lib64/libldap_r-2.4.so.2 (0x00007f78c0ece000)
liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f78c0eba000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f78c0e99000)
libc.so.6 => /lib64/libc.so.6 (0x00007f78c0cc0000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f78c0ca6000)
libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f78c0c87000)
libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007f78c0bf2000)
libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007f78c0916000)
/lib64/ld-linux-x86-64.so.2 (0x00007f78c0f61000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f78c0910000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f78c08d9000)
libz.so.1 => /lib64/libz.so.1 (0x00007f78c08bb000)
As you can si, it shoes "libssl" instead of "libgnutls", so fixin up ciphers should work (for example, from here: https://developers.cloudflare.com/ssl/reference/cipher-suites/recommendations/)
Let me know how it goes,
Regards,

Looking at python-ldap code, i see why the ldap.OPT_X_TLS_PROTOCOL... vars are missing... It's due the the libldap version..
Look:
https://github.com/python-ldap/python-ldap/blob/91e0918f822e5a28d5b66b0bdf9b99b596f5be3c/Lib/ldap/constants.py#L307C13-L307C13
Alt linux 10.1 has 2.4 release, as you can see on previos post.
Anyway, with the fix, UDS will not be able to set the minumum TLS version, but if you use valid OpenSSL ciphers, i think that will work, or it should at least :)

Glad that this helped :).
BTW, i have merged your PR on udsactor.
Did you used OpenSSL ciphers?

Yes, I used:
LDAP_CIPHER_SUITE = 'HIGH:-SSLv2:-SSLv3:-TLSv1.0:-TLSv1.1:+TLSv1.2:+TLSv1.3'

Thank you very much!, just to check the cipher suite for OpenSSL python-ldap version and leave it here (probably, i'll include it on sample file ;-)
Thanks a lot!!


[T2A2][W15-A1] Xu Bili

PR for [LO-Refactor] and [LO-MethodAbstraction].

Ready for review

Some comments added. Feel free to add more comment if you have any questions. Once you are done, you may close the PR after reading comments.


Compute Forc home directory in only one place

#674 uses manually computed home directory paths. The Forc home directory (default $HOME/.forc/) should be a thing that's computed/set once, and usable everywhere in the codebase.

#674 uses ~/.fuel, while @adlerjohn your suggestion above uses ~/.forc.
I can see how .fuel makes sense in that its related to the Fuel VM, however I think there's a strong case for using .forc in that explorer is a part of the forc tooling and we already use .forc for checking out dependencies.
@alex-matthe what are your thoughts on having the current ~/.fuel/explorer directory moved to ~/.forc/explorer?
I'm thinking I'll tackle this soon, but just wanted to get a consensus on the directory location first.


Add YAML example for self-hosted agent or pool

The only way I found in this page to specify an agent is for hosted agents.

pool:
vmImage: 'ubuntu-16.04' # examples of other options: 'macOS-10.13', 'vs2017-win2016'

This block mentions you can set up a self-hosted agent and links to how you can set those up and their capabilities.

As an alternative, you can set up a self-hosted agent and save the cost of running the tool installer.

What I would expect from this page

An example of how to explicitly specify which hosted agent (or pool) is being used. If multiple ways exist, explain them.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ec716c61-248c-75c9-2bc7-262749cc7421
Version Independent ID: 45f47edc-e800-2c42-416a-92cd93c9e892
Content: Build, test, and deploy .NET Core apps - Azure Pipelines
Content Source: docs/pipelines/ecosystems/dotnet-core.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliakm
Microsoft Alias: jukullam

Seems like the missing info is here

https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#pool

@jawn  Thank you for the feedback and for providing the solution.
The documentation has been updated and is pending review.


Missing error when freeing a renderpass that was used to create active framebuffers

In this sequence of events:

vkCreateRenderPass(..., &dummyPass);
vkCreateFramebuffer(..., {... .renderPass = dummyPass }, &framebuffer);
vkDestroyRenderPass(..., dummyPass);
... later
vkCreateRenderPass(..., &realPass);
vkCmdBeginRenderPass(..., { .renderPass = realPass, .framebuffer = framebuffer });

I get a segfault in libnvidia-gl.so. I'm not entirely sure if this is legal by spec or not - I was not aware that you had to keep around the “dummy pass” used to determine framebuffer compatibility for as long as you keep the framebuffer around. It certainly surprises me. So in case this is, in fact, undefined behavior (and not an nvidia bug), a warning would be very beneficial.

Based on the discussion in issue #516 I think what you're doing is valid and that is an NVIDIA bug.

Okay. What's the status quo of vendor bugs in the layers? Do you bother printing a debug message in cases where code is technically correct but is known to crash on some platforms, or is that considered out-of-scope of the validation layers?

Cross-posted to https://devtalk.nvidia.com/default/topic/1022963/linux/vulkan-driver-segfaults-on-spec-compliant-call-sequence/

@haasn, we don't do any vendor-specific stuff in the layers (thank goodness).  Will close this for now, reopen if the focus shifts back to validation.  Thanks!

@haasn what driver version were you using? We recently fixed a bug in our driver related to this. The fix isn't yet available in a general-release driver, but it is in the latest Vulkan beta driver, if you want to try it out: https://developer.nvidia.com/vulkan-driver.

@pdaniell-nv Apologies for not specifying. I was using 384.59-r1.

@haasn thanks for the follow-up. Driver 384.59 has the bug I was thinking of that's now fixed in the beta driver. A general-release driver with the fix should be coming out soon.


Not possible to use custom connect headers in WebSocketHttpHeadersCallback

Currently it's not possible to utilize any custom headers sent via STOMP connect command (for example custom authentication data). This is due to the fact that connectToProxiedTarget doesn't accept WebSocketMessageAccessor as other command methods do.

PR #11 solves the issue


Locale Autoswitch Class

A Locale/language class(Library) that:-

Autoswitches to browser default language
Or defaults to English

Will work this one after task of #5, #6 and #7

Alright.

Check PR #18 and check out the master, added the multilanguage on controller layer by overriding the core controller, as of now it has default language English and Tagalog for example, hope this resolves the concern ^^

@slax425  Will always to improve time to time, feel free to submit PRs too! and highly appreciated


Promotion is failed sort of sliently

Click one freight to promote.
(The promtion actually failed due to credential error).
You won't be able to tell anything has happened. (The stage is showing healthy)
Until you click into the stage detail, and check the last promotion error state.

I think the last promotion status should be surfaced in the top object.

Duplicate of https://github.com/akuity/kargo/issues/1207


\yii\db\ColumnSchema::dbTypecast calls phpTypecast, value correction undone

\yii\db\ColumnSchema has methods dbTypecast and phpTypecast so data can be transformed as it gets written and read.
My database engine, Apache Cassandra, stores timestamps in milliseconds, so all times written by Yii2, which thinks in seconds, are deep in 1970.
I fixed this in my overriding dbTypecast and phpTypecast by multiplying and dividing by 1000 respectively - only to find what they cancel out each other on write !
Proposed fix: move common code into readWriteTypecast or something like this, call it from both methods but do not call one from another.

why don't you configure TimestampBehavior to store correct value directly?

Because this is storage layer encoding/format problem and not data model problem. What if I will have timestamp columns from domain model (like task due moment) and not the auto-timestamping ? It will be a nasty gap in mental model of project !
Even more, any other type will have same problem. For example, I have DecimalType read as 2-item array, so I coerce it to number. What if it break in subtle way because of conversion cancellation ?

Could you show your dbTypecast and phpTypecast code?

<?php

namespace myvendor\yii2\db\cassandra;

use PDO;

class ColumnSchema extends \yii\db\ColumnSchema {

    /** @var int ? Place in Cassandra clustering key, 0-based, null is partitioning key */
    public $componentIndex;

    // Solve problems of type-casting before writing to Cassandra, case by case
    // Point of knowing both types
    // Was split: https://github.com/yiisoft/yii2/issues/2287

    // Read. From DB to PHP. Misleading name.
    public function phpTypecast($value) {

        // NB: this comment remained from time before split of typecast()
        // FIXME: debug_backtrace() hits performance, https://github.com/yiisoft/yii2/issues/2287

        if ( 'DecimalType' == $this->dbType ) {
            // READ. Returned as array by Cassandra or PDO driver
            if ( is_array($value) ) {
                $precision = $value[0];
                $value = round($value[1] / pow(10,$precision), $precision );
            }
        }

        // Raw value in timestamp
        if (('TimestampType' == $this->dbType) && (8 == strlen($value))) {
            $value = hexdec(bin2hex($value));
        }

        // Yii thinks in seconds, Cassandra - in milliseconds
        // Added 2015-02-19, raised https://github.com/yiisoft/yii2/issues/7357
        if ('TimestampType' == $this->dbType) {
            $value = intval($value/1000);
        }

        $value = parent::phpTypecast($value);

        return $value;
    }

    // Write. Names are so misleading !
    public function dbTypecast($value) {

        if ( 'DecimalType' == $this->dbType ) {
            // WRITE. Empty string on write = exception
            if ( empty($value) ) {
                $value = null;
            }
        }

        $value = parent::dbTypecast($value);

        // Must hint, otherwise integer as string refused by Cassandra
        if ( 'UTF8Type' === $this->dbType ) {
            $value = array( (string)$value, PDO::PARAM_STR );
        }

        // Booleans must be de-quoted
        if ( 'BooleanType' === $this->dbType ) {
            $value = array( (string)$value, PDO::PARAM_BOOL );
        }

        // Yii thinks in seconds, Cassandra - in milliseconds
        if ('TimestampType' == $this->dbType) {
            $value = 1000 * $value;
        }

        return $value;
    }

}


[TEST] Rework on the image test cases

What's the test to develop? Please describe
Implementation of the image related test cases.
Describe the items of the test development (DoD, definition of done) you'd like

[x] Create image from Volume
[x] Create ISO, raw, windows image.
[x] Create with invalid image
[x] Edit images which is not in use and which is in use.
[x] Delete image and create with same name.

Done the initial draft of following test plans:

Create ISO, raw, windows image.

test_create_image_url
test_upload_image_file

Create with invalid image

test_create_invalid_url
test_create_invalid_file

Delete image and create with same name.

test_delete_image_recreate

Compare network backend rework with existing daily api test to find duplicate.

Daily API Test
Backend Rework

test_create_image_from_volume

V

test_create_image_url (qcow2)
V
V

test_create_image_url (img)

V

test_upload_image_file
V
V

test_delete_image_recreate (URL)

V

test_delete_image_recreate (File)

V

test_create_invalid_url

V

test_create_invalid_file

V

test_edit_image_in_use
V
V

test_edit_image_not_in_use

V

test_delete
V
V


[Bug]: Infinite Rebuild Loop with CopyRspackPlugin in Watch Mode when Using "*.txt" Pattern

System Info
System:

OS: macOS 15.0.1
CPU: (8) arm64 Apple M1
Memory: 101.53 MB / 16.00 GB
Shell: 5.9 - /bin/zsh

Binaries:

Node: 22.9.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.8.3 - /opt/homebrew/bin/npm
pnpm: 9.12.2 - /opt/homebrew/bin/pnpm

Browsers:

Chrome: 129.0.6668.101
Safari: 18.0.1

npmPackages:

@rspack/cli: 1.0.13 => 1.0.13
@rspack/core: 1.0.13 => 1.0.13

Details
I'm experiencing an issue with the CopyRspackPlugin in rspack when using a pattern like "*.txt". When running the compiler in watch mode and making changes to a .ts or .js file, the compiler enters an infinite loop, continuously creating new builds without stopping.
I attempted to reproduce the issue in a GitHub Codespace, but the problem did not occur there. However, on my Mac, the issue consistently manifests. I've created a sample repository that demonstrates this behavior.
Reproduce link
https://github.com/bankmonitor-mihaly-szalai/rspack-repro
Reproduce Steps

Run npm run dev
Make a change in src/index.jsfile
Observe the compiler's behavior.

Is it similar to this issue?

Yes


6play extractor is no longer working.

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2019.11.28
[x] I've checked that all provided URLs are alive and playable in a browser
[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

Verbose log
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', '-f', 'best', 'https://www.6play.fr/n-c-i-s-p_843/saison-16-episode-4-c_12557347']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.11.28
[debug] Python version 3.7.5 (CPython) - Linux-5.3.13-e1-x86_64-with-debian-bullseye-sid
[debug] exe versions: ffmpeg 4.2.1, ffprobe 4.2.1, phantomjs 5, rtmpdump 2.4
[debug] Proxy map: {}
[6play] 12557347: Downloading JSON metadata
[6play] 12557347: Downloading webpage
[6play] 12557347: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 404: Not Found
[6play] 12557347: Downloading MPD manifest
WARNING: Failed to download MPD manifest: HTTP Error 404: Not Found
[6play] 12557347: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 404: Not Found
[6play] 12557347: Downloading MPD manifest
WARNING: Failed to download MPD manifest: HTTP Error 404: Not Found
[6play] 12557347: Downloading m3u8 information
WARNING: Failed to download m3u8 information: HTTP Error 404: Not Found
[6play] 12557347: Downloading MPD manifest
WARNING: Failed to download MPD manifest: HTTP Error 404: Not Found
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 796, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 530, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/sixplay.py", line 113, in _real_extract
    self._sort_formats(formats)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 1327, in _sort_formats
    raise ExtractorError('No video formats found')
youtube_dl.utils.ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description
The 6play extractor was working last week, but not today. It seems 6play have changed again
his format. Thanks for your very good job.

So , that's no longer possible to use youtube-dl on linux for downloading videos from 6play. I don't know how to get DRM working on linux, create an account is not sufficient.

So does it work in Windows or Mac?

On Sat, Dec 21, 2019 at 06:37:32AM -0800, K Nguyen wrote:

So does it work in Windows or Mac?
I don't know. I use only linux. What I know is that is no way
to play video on 6play from linux due to DRM in a browser.
At least, I don't know of playing theses.
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/ytdl-org/youtube-dl/issues/23411#issuecomment-568185595


Team Plan ML

Person 3 (Rayane):

Rayane will work on the model (find data using kaggle regarding betting on NBA games)
will use chat gpt to help me create a skeleton for the model

Person 2 (Remy):

For 3-person Titanic model exercise - setup backend for Titanic


Change geometry type in the items table

Related Issue(s):
https://github.com/stac-utils/stac-fastapi/issues/284
Description:
This generalizes the geometry type of the geometry column in the Items table from Polygon to Geometry.

As far as I understood, Polygon is a subset of Geometry, so this migration does not require a data migration step.
I am not sure about the downgrade migration. It will only work if no other geometries are added to the DB after the change. So maybe there the alternative is simply be a pass, as the data in the table might not be backwards compatible. On the other hand, the way its proposed its the proper downgrade from a type perspective.

PR Checklist:

[x] Code is formatted and linted (run pre-commit run --all-files)
[x] Tests pass (run make test)
[x] Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
[x] Changes are added to the CHANGELOG.

I added a copy of a stac item from the L28 L2 collection that has a multipolygon feature (the one that I referenced in the issue https://github.com/stac-utils/stac-fastapi/issues/284).
With that I added a test for ingesting the item and running a search against it. I am not sure if that is sufficient to properly test the change. So @lossyrob , when you have a moment please have a look and let me know if anything is missing.

:+1: thanks for your help on this @lossyrob


Kafka Indexing Service consumer properties not respected

I used the unified console to create a Kafka Indexing supervisor and have been adding custom configurations in the consumer properties that include the bootstrap servers and a custom deserializer, which has worked flawlessly until I added another property (auto.offset.reset).  When I look at the resulting log files, I see that the auto.offset.reset property is, in fact in my ingestSpec, but is not passed on to the Kafka consumer properties.  My setting is 'earliest' and the consumer properties shows 'none'.
I have inspected org.apache.druid.indexing.kafka.KafkaConsumerConfigs and found that the probably culprit is that 'auto.offset.reset' is hard-coded.  Perhaps the simplest fix might be to remove the hard-coded setting here, but maybe I am missing something:
/*
 * Licensed to the Apache Software Foundation (ASF) under one
 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 *   http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing,
 * software distributed under the License is distributed on an
 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */

package org.apache.druid.indexing.kafka;

import org.apache.druid.indexing.common.task.utils.RandomIdUtils;
import org.apache.druid.java.util.common.StringUtils;

import java.util.HashMap;
import java.util.Map;

/**
 * Common place to keep all kafka consumer configs
 */
public class KafkaConsumerConfigs
{

  public static Map<String, Object> getConsumerProperties()
  {
    final Map<String, Object> props = new HashMap<>();
    props.put("metadata.max.age.ms", "10000");
    props.put("group.id", StringUtils.format("kafka-supervisor-%s", RandomIdUtils.getRandomId()));
    props.put("auto.offset.reset", "none");
    props.put("enable.auto.commit", "false");
    props.put("isolation.level", "read_committed");
    return props;
  }

}

Hi @abossert, I believe it is hard-coded by design. The Kafka indexing service is designed to guarantee the exactly-once ingestion which requires Druid to track valid offsets of partitions. If some offsets are expired and automatically reset in Kafka, Druid will find some gaps between the offsets from Kafka and the ones it is aware of, which will lead to an internal error. If you want to reset automatically with the Kafka indexing service, please consider setting resetOffsetAutomatically and useEarliestOffset properly in the tuningConfig. Also, please note that resetting automatically will lead to DATA LOSS (when useEarliestOffset = false) or DATA DUPLICATION (when useEarliestOffset = true).


Broken Integrations / Matrix apps - How to fix it

To fix stickers, conference calls and other integrations on riot-ios, accept the consent of modular, the integrations manager, first on riot-web.
To accept them, open the integrations manager on riot-web. The terms agreement will be then displayed.
The issue started with the privacy update on riot-web, synapse and modular.
This will be fixed by the coming riot-ios release which includes all privacy update mentioned in this blog post.

We display terms now when a scalar token is required (opening a widget for the first time, integrations manager, sticker picker)


bbp_hetero notebook is not using three layers

In the class BBP_Heteroscedastic_Model_UCI, three layers are declared but in the forward method layer3 calling is missing. I added and worked fine.

OK, thanks, good to know!
I think we might have used 2 layers to make our results comparable with (Hernández-Lobato and Adams, https://arxiv.org/pdf/1502.05336.pdf). It has become somewhat of a benchmark in the BNN community to test UCI datasets on single hidden layer MLPs. However, this benchmark has serious limitations as highlighted by (Foong et. al. https://arxiv.org/pdf/1909.00719)


MixItUp with Jets.js

I'm using Jets.js for searching (I prefer the performance boost over JS for large lists and I don't mind the lack of animation on searching). Jets.js searches via inline style tags a-la
#jetsContent > :not([data-jets *= "search_query"]){ display:none; }

Obviously, this doesn't work because MixItUp uses inline style tags for setting the display. In Jets, I can therefore request it add !important to its display: none declaration.
However, when doing this, MixItUp stops working. When using the debugger, I see that after searching with Jets, "[MixItUp][element][_cleanUp] The operation completed successfully." no longer fires. I'm guessing MixItUp has some issue with visibility mismatches?
Is there a way around this?

Closing for now as MixItUp 3 no longer requires the setting of display: none on elements. Please comment if still an issue.


[OBCQ Recipe UX Change] Remove target_ids

This PR removes target_ids param from OBCQ modifier; now this param is not needed and will be inferred automatically
Test plan: Run obcq on both llama, and opt-1.3b; and assert we do not drop in perplexity
Expected perplexity:

opt - b/w 18-20
llama - b/w 7-8

Test commands:

[X] OPT

python3 src/sparseml/transformers/sparsification/obcq/obcq.py faceb
ook/opt-1.3b c4 --recipe src/sparseml/transformers/sparsification/obcq/example.yaml --eval wikitext2

Output: (Truncated)
2023-10-31 10:55:11 sparseml.modifiers.obcq.utils.helpers INFO     Perplexity: 18.037699

[X] LLama-7B

python src/sparseml/transformers/sparsification/obcq/obcq.py /home/rahul/llama/training open_platypus --recipe src/sparseml/transformers/sparsification/obcq/example_llama.yaml --eval wikitext2

Output: (Truncated)
2023-11-01 09:12:28 sparseml.modifiers.obcq.utils.helpers INFO     Perplexity: 7.168426

Changes in existing recipes: Look at example.yaml/example_llama.yaml but TLDR; just remove target_ids field altogether

LGTM pending the other PR comments, I agree having a list of default ids would be useful


Multi-page redirect loop

Hi,
I'm creating a bootstrap tour unfortunately when I get to the step that goes off to another page it gets stuck in a loop.  This is my code:
`      var tour = new Tour({
steps: [
{
element: ".strapline-wrapper",
title: "Welcome to",
content: "Content of my step",
},
{
element: ".view-most-popular-videos.view-display-id-block_1 .views-row-1 .view-mode-teaser img",
title: "Explore our most popular videos",
content: "Nulla quis lorem ut libero malesuada feugiat. Vestibulum ante ipsum primis in faucibus orci luctus"
},
{
element: ".view-most-popular-videos.view-display-id-block .views-row-1 img",
title: "Select videos by category",
content: "Nulla quis lorem ut libero malesuada feugiat. Vestibulum ante ipsum primis in faucibus orci luctus"
},
{
element: ".view-most-popular-videos.view-display-id-block_2 .views-row-1",
title: "Select videos by channels",
content: "Nulla quis lorem ut libero malesuada feugiat. Vestibulum ante ipsum primis in faucibus orci luctus"
},
{
element: ".fixed-search-form-wrapper #views-exposed-form-db-search-page-1",
title: "Smart search",
content: "Type in a search word, video title or actor to find something more specific"
},
{
element: ".h5p-video-wrapper",
title: "Play and Learn",
content: "When watching this video there will be some questions popping up which you can answer.",
path: "/interview/kate-winslet-shares-her-acting-secrets/"
},
{
element: "#views-exposed-form-db-search-page .form-item-field-channel-taxonomy .bootstrap-select-inner-wrapper",
title: "Filter search results",
content: "TNulla quis lorem ut libero malesuada feugiat. Vestibulum",
path: "/search/"
}
    // {
    //   element: "#block-views-related-videos-block-1",
    //   title: "Related videos",
    //   content: "These are some more learning activity videos that are related in topic to this one."
    // }
  ],
  backdrop: true,
  storage: false

});

  // Initialize the tour
  tour.init();

  // Start the tour
  tour.start();`

I actually think this is because the element I'm targeting is not visible in the DOM yet.  Would someone be able to post an example of how to wait or an element to be visible before firing the step?


404 on https://nucleo.neatocloud.com/vendors/neato/robots/XXXXXXX/messages

Hi,
I just tried your API (well, the python version)
Byt, I got 404 on all calls. Did they change the API routes ? I noticed they released a new App to support D3 and D5 robots, maybe its related ?

Just tested and everything works as it should, are you sure you have tested everything correctly?

API reponds 404 with something like "No robot found with serial for given vendor" (I dont have the exact message right now, i am on my phone).
I have double and tripled checked my robot serial in the url.
I tried manually (with certs and auth ect...) and with the lib.

hmm, for me it sometimes happened that the secret changed for some reason ... and if i remember correctly it revealed a message similar to what you're seeing.
did you already try to fetch the robots again? does the secret match?

Well, I should have looked at this before. Secret did change.
All is fine, I can close this issue.
Thanks for your inputs :)

👯  i like those most! happy cleaning! :)

Thanks. I'm gonna create a docker image that syncs my google calendar to adjust cleaning hours depending on working hours :)


added meetings container

Context

Inbox UI looked a little ug to me

Implementation

added container

Preview

Merge Checklist

[x] Correct Target Branch
[x] Pre-Review Diff Check
[x] PR Description
[x] Add Reviewers and Assignees
[ ] Review Complete
[ ] Rebase
[ ] Rebase Approved

Wait so what is this for?

Wait so what is this for?

im confused. See picture?

Is this for the meeting edit page?

Is this for the meeting edit page?

Inbox page, can you see the picture?


Add targets to allow running individual tests.

For example:
make translate.FunctionizerTest

We'll leave it as is, to encourage Eclipse debugging.


Option to log pitch and yaw of mouse click to console to aid with positioning hot spots

Currently, positioning hot spots is rather inconvenient, often devolving to trial and error. To make this process easier, a configuration option should be added that logs the mouse's pitch and yaw position values when the mouse button is clicked. Obviously, this option shouldn't be used in production.

There's now a hotSpotDebug option that, when set to true, logs the mouse pointer's pitch and yaw coordinates to the console when the mouse button is clicked.

Great! thx! :D

Just found this!!!!!!!!! Saves so much time!!!!!!! >=D


Remove trailing commas for Google Closure compatibility

By default, the Google Closure Compiler is rather pedantic about backward compatibility and chokes on trailing commas. Removing them would allow Pixi to be compiled with Closure, and improve stylistic consistency. (As far as I see, trailing-less is already the dominant style in your codebase; I suppose the occasional trailing comma springs up because JSHint does not detect it.)
It seems that Pixi does not support advanced Closure compilation (#573), but basic compatibility would be nice nonetheless.
For context, I should add that I am writing a Pixi wrapper in Clojurescript, which uses Closure. Compiling the wrapped library is generally desirable.

Sorry for hijacking this thread! Any chance someone here has complete extern files for pixi.js?
I'd like to package it up for Clojurescript (@cljsjs) and extern files are required for things to work across all optimisation modes in Clojurescript.


Add tile source _dtype attribute

This would be nice to have; curious what's motivating this?

When we show controls for picking the minimum and maximum values for a band, it would be nice to be intelligent about what values are allowed.  uint8 data should be limited to [0,255]; uint16 to [0,65535], float should suggest from [0,1].  We can glean this information from the histogram data, but that is expensive to compute.

Ah, makes sense! One request, can we put this in the metadata?

Ah, makes sense! One request, can we put this in the metadata?

Yes.  That is one of the goals.

Not sure how this is implemented;  is the _dtype computed during the initial file import, or is this done lazily so it's computed the first time the tileInfo is requested, and then cached?
Depending on performance, may also want to have a maintenance function that could pre-compute this at a folder / item level to prevent the user having to wait for this the first time an image is loaded.

The CI is still failing because the DummyTileSource doesn't have a _classkey (deliberately, as it isn't eligible for styling or caching).  I'll push a change to handle that.


mob-suite :: ete3 import TreeStyle error

Hello after installing mob-suite using conda as described on the README
I have the following error
(py36) mob-suite:~/tt> mob_typer --infile AB040415.fasta --outdir xx
Traceback (most recent call last):
  File "/opt/miniconda/envs/py36/bin/mob_typer", line 8, in <module>
    from mob_suite.mob_typer import main
  File "/opt/miniconda/envs/py36/lib/python3.6/site-packages/mob_suite/mob_typer.py", line 28, in <module>
    from mob_suite.mob_host_range import getTaxonomyTree, getLiteratureBasedHostRange, loadliteratureplasmidDB, \
  File "/opt/miniconda/envs/py36/lib/python3.6/site-packages/mob_suite/mob_host_range.py", line 9, in <module>
    from ete3 import NCBITaxa, TreeStyle
ImportError: cannot import name 'TreeStyle'

regards
Eric

Hi Eric. We've also observed this behaviour with ete3 library. Other users also reported this issue. Unfortunately ete3 does not have a nice error exception message when it fails to import TreeStyle submodule responsible for graphically rendering trees. It happens because the qt5 library is not installed or it is non-functional. This issue was mentioned before here. See if you can install qt5 by running the commands below and make ete3 to be fully functional.
conda install -c conda-forge pyqt=5.9.2
conda install -c conda-forge qt=5.9.7

I am thinking to replace the ete3 dependency by our own code, but did not have time to write this functionality.

thanks for the advice.
unfortunatly this not solve the problem.
after digging on pyqt libraries I noticed that some libraries are linked vs system libs that are missing
 (py36) mob-suite:/opt/miniconda/envs/py36/lib/python3.6/site-packages/PyQt5> ldd *.so | grep 'not found'| sort | uniq
        libEGL.so.1 => not found
        libGL.so.1 => not found
        libXcomposite.so.1 => not found
        libXcursor.so.1 => not found
        libXdamage.so.1 => not found
        libXfixes.so.3 => not found
        libXi.so.6 => not found
        libXrandr.so.2 => not found
        libXss.so.1 => not found
        libXtst.so.6 => not found
        libasound.so.2 => not found

installing libgGL.so.1 missing library (debian: libgl1-mesa-glx)
solved the problem

FIY here is the singularity recipe I've come with.
Bootstrap: docker
From: ubuntu:16.04

%environment
    PATH="/opt/miniconda/condabin/bin:$PATH"

%post
    #---- system
    #        libgl1-mesa-glx required to fix https://github.com/phac-nml/mob-suite/issues/28
    apt-get update
    apt-get install -y python3 python3-pip wget libgl1-mesa-glx
    apt-get clean

    #---- install conda
    wget https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh -O miniconda.sh && \
       bash miniconda.sh -b -p /opt/miniconda && \
       rm -f miniconda.sh

    #---- conda config
    . /opt/miniconda/bin/activate
    conda config --add channels defaults
    conda config --add channels conda-forge
    conda config --add channels bioconda

    #---- default conda use python3.7 => some reuirements of mob-suite requires python3.6
    conda create -y -n py36 python=3.6 conda
    conda activate py36

    #---- install mob_suite
    conda install -y blast amos mash circlator mob_suite
    sed -i 's%/usr/local%${CONDA_PREFIX}%g' ${CONDA_PREFIX}/bin/minimus2
    mob_init

%runscript
    #---- export PYTHONNOUSERSITE=1 in order to avoid container's python
    #     to check ${HOME}/.local aka user installed libraries
    #     as we will mount ${HOME} in the container at run time
    . /opt/miniconda/etc/profile.d/conda.sh && conda activate py36 && PYTHONNOUSERSITE=1 exec ${1+"$@"}

Thank you Eric. I did not know that you were trying to build a singularity container.  We also have a docker container and instructions on how to convert it to singularity container at https://hub.docker.com/r/kbessonov/mob_suite.
Thank you for the singularity recipe. It is very valuable and It fixes both the ete3 dependency on mesa graphic libraries and minimus2 fixed path bugs that we had in the past.

We had removed TreeStyle submodule dependency in version 2.0.1.


bug: aligning the value names

Describe the bug
names for values arenot aligned:
alle named: vehicle-data.....
except: driver_temp_setting and rawJSON
Expected behavior
all names should have the same alignement
Screenshots & Logfiles

Versions:
0.2.0

This had been fixed in 0.1.5 .... you have to delete all states - or the folder "vehicle-data" to get the states re-initialized.
Possible links or aliases are still working afterwards.

states deleted
bug is now fixed in my installation


Support the workflow under Windows. #9

I found and fixed the first file/path issue, while running j2cl native with Windows 10 ... added the following fix ".replace('\', '/')" here "com.google.j2cl.generator.OutputGeneratorStage#generateOutputs:87"
String typeRelativePath = getRelativePath(type).replace('\', '/');
Not sure if this fix is well placed, but is corrects the issue (looking up an windows path in a map with unix paths)...

@rluble  could you pull this in?


Moved "no-shared" so that also windows statically link to the libraries

Moved the argument and added it close to the "no-dso", as it's seems it's a "related" configuration switch.

Thanks! Since I'm not entirely sure whether we have CI for it or not, have you confirmed this works for you both with and without crt-static?

Thanks! Since I'm not entirely sure whether we have CI for it or not, have you confirmed this works for you both with and without crt-static?

I'll double check.

I'll double check.

It looks like we do have CI coverage for that I think: https://github.com/alexcrichton/openssl-src-rs/blob/master/.github/workflows/main.yml#L99-L107

It looks like we do have CI coverage for that I think: https://github.com/alexcrichton/openssl-src-rs/blob/master/.github/workflows/main.yml#L99-L107

Also, @alexcrichton should the crt-static workflow here be phased out given it was used only to check the two different linking version (wondering how it was working though...)?
https://github.com/molleafauss/openssl-src-rs/blob/master/.github/workflows/main.yml#L90

Also, @alexcrichton should the crt-static workflow here be phased out given it was used only to check the two different linking version (wondering how it was working though...)?
https://github.com/molleafauss/openssl-src-rs/blob/master/.github/workflows/main.yml#L90

I am a bit confused as to what changed from when this was written to now though: https://github.com/alexcrichton/openssl-src-rs/commit/3bce2e86cea1ce9e13d3a44ecc9e3fba17e3f3fd. Presumably that was made for a good reason!

I am a bit confused as to what changed from when this was written to now though: https://github.com/alexcrichton/openssl-src-rs/commit/3bce2e86cea1ce9e13d3a44ecc9e3fba17e3f3fd. Presumably that was made for a good reason!

Hm so C/C++ code needs to be compiled with a different flag depending on the crt-static value, and typically that happens through the cc crate but reviewing the code here it looks like cc may not be used and the no-shared/etc flags are what's being used. In that case @molleafauss when testing this I'd expect it to fail?
Looks like CI is at least busted in one way because there's failures which aren't failing CI. I'll look into that.

Hm so C/C++ code needs to be compiled with a different flag depending on the crt-static value, and typically that happens through the cc crate but reviewing the code here it looks like cc may not be used and the no-shared/etc flags are what's being used. In that case @molleafauss when testing this I'd expect it to fail?
Looks like CI is at least busted in one way because there's failures which aren't failing CI. I'll look into that.

Haven't looked into what tests are run in this crate, and how the built openssl lib is used.
I would indeed expect that the build missing the no-shared would fail, as it would not be able to load the openssl dlls, unless those libraries were available system-wide (i.e. via %PATH%) in the docker image used for testing?
But if the tests are only checking that the openssl sources are built properly, both shared and dll build for windows are working, the issue is with the upstream dependencies (openssl->openssl-src->this crate) and what they end up linking ultimately.
When the dll were built, then rustc was linking only the stubs to your binary, and then the binary would fail running, as the .dll were nowhere to be found.

Haven't looked into what tests are run in this crate, and how the built openssl lib is used.
I would indeed expect that the build missing the no-shared would fail, as it would not be able to load the openssl dlls, unless those libraries were available system-wide (i.e. via %PATH%) in the docker image used for testing?
But if the tests are only checking that the openssl sources are built properly, both shared and dll build for windows are working, the issue is with the upstream dependencies (openssl->openssl-src->this crate) and what they end up linking ultimately.
When the dll were built, then rustc was linking only the stubs to your binary, and then the binary would fail running, as the .dll were nowhere to be found.

ouch - think I see the issue: this is in the windows build; both x86_64-msvc-static and x86_64-msvc. But the build passes... 🤦♂

ouch - think I see the issue: this is in the windows build; both x86_64-msvc-static and x86_64-msvc. But the build passes... 🤦♂

And as I was suspecting this is the build environment: the OpenSSL 1.1.1 is included...

And as I was suspecting this is the build environment: the OpenSSL 1.1.1 is included...

Hm ok so testing this locally, I'm surprised that this ever worked actually. The problem the current static builds (pre-this-PR) is that a new dependency (user32.dll) was introduced and we're not linking it. That's easily fixed, however. The pre-this-PR non-static builds are actually doing entirely the wrong thing. They're attempting to statically link the import libraries, which is causing the duplicate symbol error. This crate was never intended to build shared libraries, so the fact that it's building shared libraries when +crt-static is missing is entirely a mistake.
This PR definitely fixes that issue and can be fixed in CI by adding an extra-linked library (user32.dll), but the problem still remains that the C code is compiled with /MT instead of /MD with -crt-static. I don't know how to fix that with OpenSSL's build system at this time, though. Somehow that needs to be fixed as well to fully fix this

Hm ok so testing this locally, I'm surprised that this ever worked actually. The problem the current static builds (pre-this-PR) is that a new dependency (user32.dll) was introduced and we're not linking it. That's easily fixed, however. The pre-this-PR non-static builds are actually doing entirely the wrong thing. They're attempting to statically link the import libraries, which is causing the duplicate symbol error. This crate was never intended to build shared libraries, so the fact that it's building shared libraries when +crt-static is missing is entirely a mistake.
This PR definitely fixes that issue and can be fixed in CI by adding an extra-linked library (user32.dll), but the problem still remains that the C code is compiled with /MT instead of /MD with -crt-static. I don't know how to fix that with OpenSSL's build system at this time, though. Somehow that needs to be fixed as well to fully fix this

There is this thing that README.Windows mentions briefly you're supposed to compile into your application: https://github.com/openssl/openssl/blob/master/ms/applink.c. Maybe it does that to avoid dealing with static vs dynamic linkage to the crt?

There is this thing that README.Windows mentions briefly you're supposed to compile into your application: https://github.com/openssl/openssl/blob/master/ms/applink.c. Maybe it does that to avoid dealing with static vs dynamic linkage to the crt?

Ok so there's actually a whole mess of problems wrong with this crate and its CI right now:

CI doesn't actually ever enable crt-static testing, it's incorrect GitHub Actions configuration.
When crt-static is disabled, OpenSSL dynamic libraries are built but they're linked statically according to the info we provide rustc, this generates linking errors because you're not supposed to do that.
When compiled as a static library we're missing the -luser32 link argument, meaning that linking always fails if you actually enable crt-static.
CI was accidentally ignoring some failures on Windows due to using the wrong shell.
The directory with the dlls for OpenSSL wasn't actually added to Cargo's search path on MSVC.

I think those are all fixed with #84, however. Want to try rebasing over that and see what happens?
It may still be the case that +crt-static appears to work, but I don't think it will in general because there still isn't any supporting code to figure out how to compile libssl.lib with /MD for linking to libcmt.lib

Ok so there's actually a whole mess of problems wrong with this crate and its CI right now:

CI doesn't actually ever enable crt-static testing, it's incorrect GitHub Actions configuration.
When crt-static is disabled, OpenSSL dynamic libraries are built but they're linked statically according to the info we provide rustc, this generates linking errors because you're not supposed to do that.
When compiled as a static library we're missing the -luser32 link argument, meaning that linking always fails if you actually enable crt-static.
CI was accidentally ignoring some failures on Windows due to using the wrong shell.
The directory with the dlls for OpenSSL wasn't actually added to Cargo's search path on MSVC.

I think those are all fixed with #84, however. Want to try rebasing over that and see what happens?
It may still be the case that +crt-static appears to work, but I don't think it will in general because there still isn't any supporting code to figure out how to compile libssl.lib with /MD for linking to libcmt.lib

Did rebase the work, all tests are passing. I've removed the crt-static flag, given it seems pointless, basically making the configurations msvc and msvc-static identical.
I see that the tests are run.
Let me know your thoughts.

Ok I did some testing locally and happened to stumble upon https://stackoverflow.com/questions/3469841/mixing-code-compiled-with-mt-and-md. Indeed OpenSSL is compiled with /Zl, and testing locally I can mix a /MT OpenSSL with a /MD object file and it appears to work. Given that OpenSSL seems like it may be passing that option intentionall then this looks good to me!
Sorry for the runaround with weird CI and such...
In any case, want to drop the shared flag now since it's always false? Other than that seems good to merge to me!

Ok I did some testing locally and happened to stumble upon https://stackoverflow.com/questions/3469841/mixing-code-compiled-with-mt-and-md. Indeed OpenSSL is compiled with /Zl, and testing locally I can mix a /MT OpenSSL with a /MD object file and it appears to work. Given that OpenSSL seems like it may be passing that option intentionall then this looks good to me!
Sorry for the runaround with weird CI and such...
In any case, want to drop the shared flag now since it's always false? Other than that seems good to merge to me!

no probs, will give a look later tonight (you might have guessed I'm on GMT here)

no probs, will give a look later tonight (you might have guessed I'm on GMT here)

Also should we remove the MSVC CI configs for the crt-static, leaving only 2 and not 4 for windows?

Also should we remove the MSVC CI configs for the crt-static, leaving only 2 and not 4 for windows?

Nah since that's different enough at the rustc level I'd prefer to not drop them just yet.

Nah since that's different enough at the rustc level I'd prefer to not drop them just yet.


About the mixed real world dataset

Thanks for your amazing work！
I would like to train a smaller model on this dataset.
Would you mind sharing the composition of the mixed dataset and its training hyperparameters?

I'm busy these days, and I may upload it next week.

Thanks for your response！

For convenience, I uploaded the dataset to baidu pan:
https://pan.baidu.com/s/1oXmYvrwejVsazmaKaIyhjg?pwd=wu5n


RH supp style guide: termserrors update

updated termserrors and termswarning to match RH supplementary style guide
https://github.com/redhat-documentation/vale-at-red-hat/issues/317

LGTM


Support QBSchema Packet for loading packets

We should support QBSchema's Packet class as an import for packets. Depending on what the file format is, we may have to add some logic to the JSON-parsing class to distinguish between YAPP-parsed packets and QBSchema packets.

Can't work on this until the issue with Question  is resolved.


[Bug]: Cannot deploy checkout ui extension

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Extension
Expected behavior
The extension deployment should work just fine.
Actual behavior
I cannot deploy my checkout ui extension in production.
I keep getting a generic unhelpful error.
It seems related to https://github.com/Shopify/cli/issues/1146
EDIT:
I was able to deploy my production extension from my local environment. It seems the issue only occurs when trying to use a CLI partner token and deploying with the force flag -f.
Stack trace
$ shopify app deploy -f
╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                              │
│                                                                              │
│    The Partners GraphQL API responded unsuccessfully with the HTTP status    │
│  200 and errors:                                                             │
│                                                                              │
│    [                                                                         │
│    {                                                                         │
│      "message": "Unexpected system error",                                   │
│      "extensions": {                                                         │
│        "code": "500"                                                         │
│      }                                                                       │
│    }                                                                         │
│  ]                                                                           │
│                                                                              │
│                                                                              │
│  To investigate the issue, examine this stack trace:                         │
│    at (graphql-request/src/index.ts:410)                                     │
│      throw new ClientError(                                                  │
│    at step (graphql-request/dist/index.js:63)                                │
│      op = body.call(thisArg, _);                                             │
│    at next (graphql-request/dist/index.js:44)                                │
│      function verb(n) { return function (v) { return step([n, v]); }; }      │
│    at fulfilled (graphql-request/dist/index.js:35)                           │
│      function fulfilled(value) { try { step(generator.next(value)); } catch  │
│       (e) { reject(e); } }                                                   │
│    at processTicksAndRejections (node:internal/process/task_queues:95)       │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Reproduction steps

Create new app boilerplate using npm init @shopify/app@latest
Create a new extension inside app using npm run shopify app generate extension
Run npm run deploy -f to try to deploy the app & extension

Operating System
GitHub Actions Workflows
Shopify CLI version (check your project's package.json if you're not sure)
^3.44.1
Shell
No response
Node version (run node -v if you're not sure)
No response
What language and version are you using in your application?
No response

I looked at this again today and it seems that the first time the extension needs to be deployed from your local setup. https://shopify.dev/docs/apps/tools/cli/ci-cd
After the initial deploy (which creates the extension), you can then use CI/CD to keep deploying.

I try to init a new Shopify app and try to run it, then this error happens:

any suggestions?

I have the same issue when I run my app using "npm run dev"
╭─ error ────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│                                                                                │
│    The Partners GraphQL API responded unsuccessfully with the HTTP status 200 and errors:          │
[│..................                                                                                │] / :
timing│     npm:load[                                                                                Completed in 53ms│
│    {                                                                                │
│      "message": "Unexpected system error",                                                         │
│      "extensions": {                                                                               │
│        "code": "500"                                                                               │
│      }                                                                                │
│    }                                                                                │
│  ]                                                                                │
│                                                                                │
│                                                                                │
│  To investigate the issue, examine this stack trace:                                               │
│    at (graphql-request/src/index.ts:410)                                                           │
│      throw new ClientError(                                                                        │
│    at step (graphql-request/dist/index.js:63)                                                      │
│      op = body.call(thisArg, _);                                                                   │
│    at next (graphql-request/dist/index.js:44)                                                      │
│      function verb(n) { return function (v) { return step([n, v]); }; }                            │
│    at fulfilled (graphql-request/dist/index.js:35)                                                 │
│      function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }   │
│    at processTicksAndRejections (node:internal/process/task_queues:96)                             │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────╯
PS : I didn't change any thing. I get up today, I tried to launch my app and then I got this error!

I looked at this again today and it seems that the first time the extension needs to be deployed from your local setup. https://shopify.dev/docs/apps/tools/cli/ci-cd
After the initial deploy (which creates the extension), you can then use CI/CD to keep deploying.

Hi @Arkham, we just spent a lot of time figuring this out. We avoid Shopify CLI at our company because of its API instability and cumbersome dependencies. We run a Shopify CLI wrapper on AWS Lambda for tasks which cannot be performed using a normal API.
It would be great if Shopify exposes this functionality in the Partner GraphQL API so we can abandon Shopify CLI. But at the very least Shopify CLI needs to lend itself to automation.

Thanks for your feedback. I'll close this in the meanwhile.

New version created, but not released.                                      │
│                                                                              │
│  App9 [1]                                                      │
│                                                                              │
│  Network access must be requested and approved in order for this extension   │
│  to be published.                                                            │
│

@Vjndevshopify ye well it's not a bug, it literally tells you what to do.
You need to go to your app settings in your partners dashboard and request access for network.

@aurelienbobenrieth  i am sorry its bymistkae i comment .
Thank you its solved


Making stubs great again

@casualjim
Please don't ditch this repo: it is awesome, albeit unfinished work.
I'll try to revive it. I managed to make it up and running and I am starting to figure out the many shortcomings. That's quite a heavy task.
Here is a todo that came up after a couple hours tinkering with the package.
What remains to be done. Feel free to comment.

workable faker for numbers and integers, according to format (format given as Arg to ValueGenerator)
faker for date, date-time and duration formats (duration is simple starting from a random int and using random alternate text marshaller,
date is not so complex: take time.Now() and subtract a random number of days then marshal as text
relocate the reseed at top level (as top level option)
taking into account validations (planned dev, but no actual implementation)
abide by generation flags to control when generating a passing case and a non passing case (currently not implemented)
faker for slices (with option to produce a parsable string using CollectionFormat)
a testable fixture generator to instruct a test client (or a unit testing program)
a spec walker (may reuse the one under development with validate) to generate test cases for parameters, headers and responses
a test case orchestrator to plan for a full coverage of validation points
rule-based option detection for simple types: the idea is to find a smart way to select the ValueGenerator according to rules

simple types and formats should provide straightforward rules

a fuzzy-er based on title and description tags, along the lines of what meqqa suggests
the idea is to detect proper options according to hints in title/doc
investigate go native solution for NLP (meqqa use Python)
limit the use of x-datagen extension tag
generate combinatorial test suite with required / non required / allowsEmpty items
find a way to customize the faker dictionary

@fredbi I am in for contribution


Stack trace printed when the program panics contains $anonType$_0

Description:
When a ballerina program panics, the stack trace it returns contains something like $anonType$_0. The users won't be able to map it with his/her source code.
Steps to reproduce:
Add a panic statement to the code and run the program. It will print a stack like the following.
error: Test Error
        at janesmith.pkg.0_1_0.$anonType$_0:$get$sayHello(svc.bal:14)

Affected Versions:
Ballerina Swan Lake Alpha 1

I think uses will be able to map because svc.bal:14 part will point to the correct location.
Anyway it's better if we can avoid $anonType$, but I don't have a good suggestion on how it should look.


Pylance can't resolve .pyw imports

Environment data

Language Server version: v2020.11.2
OS and version: Windows 10
Python version: 3.8.3

Expected behaviour
from GSM import Backup
(No error)
Actual behaviour
from GSM import Backup
(Import "GSM" could not be resolvedPylance (reportMissingImports))
GSM is a .pyw file
If I rename it to .py then it does resolve properly.
Code Snippet / Additional information
from GSM import Backup
# GSM is a .pyw file

Thanks for the suggestion. This is a less common scenario that we don't support yet.

This is a duplicate of #739. A more generic version of this issue

I am experiencing the same issue.
My team developed a language on top of Python and Pylance can be a huge plus there.
However, since the modules need to go through AST transformation, they end with "*.pyt"
Pylance does not recognize such an extension.
Maybe add some configuration that allows user to set what extensions Pylance should look for?
I am using the latest release of Pylance at the moment.

Moving this issue to discussion as an enhancement request for comments and upvotes.


fix: release-service-catalog CI config

Description

fix of the condition for rehearsal job for release-service-catalog

Issue ticket number and link
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
in CI
Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/lgtm
/approve

/approve

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/retest-required

/retest-required


JsxToHeex not working

did you remove this? The demo doesn't convert jsx to heex.
Could you add some more color on this functionality? I'm interested in adopting this library
https://salad-storybook.fly.dev/examples/convert_shadui

@geofflangenderfer after pasting jsx code to the input textarea, click outside the textarea. It works on blur event. I'm thinking of adding a button


Potential vulnerability: topic names from ROS parameters

Hi,
We notice that you are using topic names from ROS parameters at the following locations:
https://github.com/fictionlab/pincher_arm/blob/8c1f6fbdd7b9995ad57ba652f95ce8ad97d7b382/pincher_arm_bringup/scripts/gripper_controller#L49
https://github.com/fictionlab/pincher_arm/blob/8c1f6fbdd7b9995ad57ba652f95ce8ad97d7b382/pincher_arm_bringup/scripts/gripper_transmission#L112
https://github.com/fictionlab/pincher_arm/blob/8c1f6fbdd7b9995ad57ba652f95ce8ad97d7b382/pincher_arm_bringup/scripts/gripper_transmission#L117
For security reasons detailed below, we strongly suggest avoiding the usage of strings from parameters as topic names.
Although parameters are usually set in parameter files, they can also be changed by nodes. Specifically, other nodes in the same ROS application can also change the parameters listed above before it’s used, either by accident or intentionally (i.e., by potential attackers). If any of gripper_transmission/source_joint, gripper_transmission/target_joint, or gripper_controller/joint parameters is changed, the joint commands will not be passed as designed, and the robot arm will not grip when it is commanded to. Moreover, if an attacker exists, she can take full control of the robot arm gripper by manipulating the parameters. One way to do this is to first change gripper_transmission/source_joint parameter from gripper_joint to gripper_joint_fake before it’s used by the gripper_transmission node, which fools the gripper_transmission node to publish to gripper_joint_fake/command; then she can forward all messages from gripper_joint_fake/command to gripper_joint/command after changing the contents. She can also simply publish anything as she wants to gripper_joint/command. Because ROS is an OSS (open-source software) community, third-party nodes are widely used in ROS applications, usually without complete vetting of their behavior, which gives the opportunity to potentially malicious actors to inject malicious code (e.g, by submitting hypocrite commits like in other OSS systems [1]) to infiltrate the ROS applications that use it (or software supply chain attacks, one of the primary means for real-world attackers today [2]).
We understand that using parameters to set topic names brings flexibility. Still, for the purpose of security, we strongly suggest that you avoid such vulnerable programming patterns if possible. For example, to avoid the exposure of this specific vulnerability, you may consider alternatives like remapping, which is designed for configuring names when launching the nodes.
[1] Q. Wu and K. Lu, “On the feasibility of stealthily introducing vulnerabilities in open-source software via hypocrite commits,” 2021, https://linuxreviews.org/images/d/d9/OpenSourceInsecurity.pdf.
[2] Supply chain attacks are the hacker’s new favourite weapon. and the threat is getting bigger. https://www.zdnet.com/article/supply-chain-attacks-are-the-hackers-new-favourite-weapon-and-the-threat-is-getting-bigger/.

Hi there, I wanted to follow up on this security vulnerability. Could you please let me know if there have been any updates or concerns regarding this issue? Thanks


schedule renovate after hours

Do you have a link to the renovate docs? A link to the docs in the PR comments would help reviewers/us later when looking back at this


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1656 ms

Resolved: Bofrost.at performance has improved in 4c58c6a after 6 minutes.


[DialogTitle] Update default element from h6 to h2

Closes #16569

[x] I have followed (at least) the PR section of the contributing guide.

@dayander Very much appreciated.
Waiting for reports that this broke because people used h7+ headings in their dialogs though :smile:


intersect -f -F switch

Hi Aaron,
It seems the following bedtools intersect command is not working as expected. I was using bedtools 2.26.0.
$ cat A.bed
chr1    1    1
chr1    2    2
$ cat B.bed
chr1    1    2
$ bedtools intersect -a A.bed -b B.bed -c -f 1.0
chr1    1    1    0
chr1    2    2    0
$ bedtools intersect -a A.bed -b B.bed -c -F 1.0
chr1    1    1    1
chr1    2    2    1
I think the -f and -F options in this context are switched. Is this a known bug?
Thanks,
Jackie

I think this is because you are using zero length records in A.bed. BED format uses zero-based starts and 1-based ends.

I see. Thanks for the clarification.
On Fri, May 26, 2017 at 5:31 PM, Aaron Quinlan<EMAIL_ADDRESS>wrote:

I think this is because you are using zero length records in A.bed. BED
format uses zero-based starts and 1-based ends.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/arq5x/bedtools2/issues/456#issuecomment-304392432,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADogKKVNiAUbEYxuRDuJpliqbOnKX31Fks5r90SigaJpZM4Kt7-E
.


[shell] improve mawk detection

Use the all-compatible mawk -W version option. https://github.com/junegunn/fzf/pull/3313#issuecomment-1747934690.
Do not remap the history key if no dependent commands is installed (perl, awk or mawk in this order).
Run the command and not a function consistently with #3462.

The version check bash code relies on the following mawk source code, extracted from mawk 1.3.4 20230322.
version.c:
18-  #include "init.h"
19-  #include "patchlev.h"
20-
21:  #define	 VERSION_STRING	 \
22-    "mawk %d.%d%s %s\n\
23-  Copyright 2008-2022,2023, Thomas E. Dickey\n\
24-  Copyright 1991-1996,2014, Michael D. Brennan\n\n"
....
30-  void
31-  print_version(FILE *fp)
32-  {
33:      fprintf(fp, VERSION_STRING, PATCH_BASE, PATCH_LEVEL, PATCH_STRING, DATE_STRING);
34-      fflush(fp);
35-
36-  #define SHOW_RANDOM "random-funcs:"

patchlev.h:
13-  /*
14-   * $MawkId: patchlev.h,v 1.128 2023/03/23 00:23:57 tom Exp $
15-   */
16:  #define  PATCH_BASE	1
17-  #define  PATCH_LEVEL	3
18-  #define  PATCH_STRING	".4"
19-  #define  DATE_STRING    "20230322"

Other than the comments made in the code above, I think it looks mostly good, I especially like that you saved at least one execution of awk, though:

I'd split it up in more commits, you do now various mostly unrelated things in one commit, adding the command, fixing the version check, changing the output redirection (which I would however drop completely), make the code handle the situation when both perl and [m]awk aren't available.
I think it's easier to understand and follow in smaller pieces
Handling the case that awk isn't available is in principle fine by me, though at least POSIX wise, systems are expected to have awk. So assuming POSIX systems, handling this is unnecessary.
btw: I think the (x *1000 +y) *1000 +z >= 1003004 part is at least a bit fragile, should e.g. ever a big minor version number be used. Also you still have the check for the date, so apart from me not liking such a runtime check in general, t should be fine.

I checked it on Debian with mawk <IP_ADDRESS>00120-3.1, which yields __fzf_awk=awk, and with <IP_ADDRESS>30808-1, which yields __fzf_awk=mawk. So that works :-)

@calestyo thank you for testing on Debian.
@junegunn you're right, who can be sure how all target platforms and bash versions will behave when stdout is closed. Better be safe.

Handling the case that awk isn't available is in principle fine by me, though at least POSIX wise, systems are expected to have awk. So assuming POSIX systems, handling this is unnecessary.

I also think it's unnecessary. The absence of awk can be a sign of a broken system, and we should probably warn the user with an error instead of silently disabling a subset of our feature, making it harder to fix the system.

Merged, thanks!

Looks good to me, though I probably still have placed the command  inside the variable, as described above.

Oh, one more thing that I had noticed before, but forgot to write down:
https://github.com/junegunn/fzf/blob/884856023ab53fa1eb7f8dbf158aa522daef0ae5/shell/key-bindings.bash#L75
Wouldn't it be safer to use read -r?


Increase add/edit timeout length to decrease chance of ui being out of sync

Closes #699

This isn't a real solution to the problem unfortunately because it happens to rely on the cluster conditions at that particular point in time. I think we need to leave this issue open and fix it deterministically, but we can accept this PR as a band-aid.


Consider turning on driver logs by default (log to file)

This would make it much easier to do post-mortem debugging with users without having to explain to them how to enable those, and that they need to wait or reproduce their issue.

I have disabled all logs because they slowed down the storage it was running on. I only enable them when needed.
For those running this on a raspberry pi microsd card it might also be better to keep it disabled since it creates a lot of unnecessary writes to the card.

@thecobra666 making them enabled by default wouldn't make any difference for the ones that already have a configuration, it will enable them just for the once that use zui first time with no configuration saved yet

@thecobra666 making them enabled by default wouldn't make any difference for the ones that already have a configuration, it will enable them just for the once that use zui first time with no configuration saved yet

I do still stand by my point in regards to the unnecessary writes to disk. These logs, when not needed, would keep using up IO which is not needed. Enabling them when necessary should be the better option. Why not include a simple button that enables a debug 'mode' and thus sets the correct log settings
When finished the user can disable it again and all goes back to normal.

Yeah I understand you point, but from our prospective it would make easier and faster to support users, most common answer to issues is 'please make a driver/application log and attach it to the issue', this requires users to check docs and enable logs and reproduce the issue and this could be hard for newbies. Anyway if someone knows what he is doing can simply disable them when setting up zui the first time

Maybe this request is meant for the Z-Wave JS UI add-on, which disables the logging by default?

Yeah I just checked this and seems them are already enabled by default, I have no clue about how the addon can disable them by default, maybe they create a pre-configured settings file?

Ok so I close this issue as should be moved/requested in the addon instead
cc @Frenck


Issue #100778 closed due to inactivity of Flutter team members

I don't think this issue is different from https://github.com/flutter/flutter/issues/100777 apart from Another exception was thrown: Instance of 'DiagnosticsProperty<void> exception. Would be good to track this in already triaged and linked issue.
Closing this as duplicate. If you disagree, write in comments and I'll reopen it.

Originally posted by @darshankawar in https://github.com/flutter/flutter/issues/100778#issuecomment-1080641191
I've responded here: https://github.com/flutter/flutter/issues/100778#issuecomment-1080737799 but @darshankawar haven't reacted until issues gets closed by bot.
I could not post comments in a closed issue hence I'm creating a new ticket, intentionally omitting a template. After #100778 gets reopened this one can be closed.

Thanks @koral-- for pointing this. The linked issue somehow got lost in the notifications.
I'll reopen it and closing this.


NoHyphenation: non-splitting implementation of WordSplitter

This type can be used in case words shouldn't be split at all, not
even on existing hyphens.

Using this word splitter is analogous to break_on_hyphens=False in Python: https://docs.python.org/3/library/textwrap.html#textwrap.TextWrapper.break_on_hyphens


Error rendering Twitch demo video

Current Behavior
When i set the demo Twitch url in my local project the player is not rendered. With YouTube, Vimeo and Dailymotion it works. I'm using the latest version of react-player (1.13.0).
Expected Behavior
Render the player and the video normally.
Steps to Reproduce

Using a localhost alias, for example example.test create a React project with nginx as reverse proxy.
Inside a component, create a simple log methods this.onDuration and this.onProgress and write:

<ReactPlayer
  ref={this.ref}
  className="watch__embed-container"
  controls={true}
  width='100%'
  height='100%'
  url={`https://www.twitch.tv/videos/106400740`}
  playing
  onDuration={this.onDuration}
  onProgress={this.onProgress}
/>

Environment

URL attempting to play: https://www.twitch.tv/videos/106400740
Browser: Google Chrome 78
Operating system: Windows 10
jsFiddle example: I don't know how to import ReactPlayer with jsFiddle.

Other Information

This can happen when playerId is not correct here:
https://github.com/CookPete/react-player/blob/1e41ce5ce5e2d6946701723f60e74326385df92d/src/players/Twitch.js#L32
playerID should be twitch-player- plus a random string:
https://github.com/CookPete/react-player/blob/1e41ce5ce5e2d6946701723f60e74326385df92d/src/players/Twitch.js#L18
Is the ID not being set correctly in your DOM?

The random string id is well generated in my DOM. For example twitch-player-8rn47, as you can see.

I'd just like to chime in and say that I'm experiencing the same issue with all Twitch embeds. Here's a codesandbox if this helps.

@SiroDiaz There must be something wrong with your specific environment or implementation. Your example code works fine for me in jsFiddle with v1.13.0: https://jsfiddle.net/gx5802o9/
@jackhenry Your example doesn't work because https://www.twitch.tv/p/watch/esfand isn't a valid Twitch URL. Visiting it gives me a 301 redirect to https://www.twitch.tv/p/watch/esfand which then returns a 404 page.

@CookPete i think the same. I'm going yo try others things. If i don't solve the problem i will notice you more about muy environment

@CookPete Sorry, I was in a rush. Try this
I've double checked that link and that's the same format for the twitch urls I've been using.
The issue is with the controls property. If set to false, I just get a black screen. If it's set to true, it works. You can replace the url with any other url and the issue should be the same.
Also note, I've only got this issue with embedded twitch live streams. Not embedded twitch videos.

The issue is with the controls property. If set to false, I just get a black screen. If it's set to true, it works. You can replace the url with any other url and the issue should be the same.

So it only breaks for live streams when controls={false}? I can add a note to the readme but this seems like a bug with the twitch player.

@CookPete You're probably right. The Twitch Dev team is notorious for introducing breaking bugs without any notice.
It appears to be an issue with the format of the url used for the iframe.
This doesn't work: https://player.twitch.tv/?allowfullscreen&video=&channel=yogscast&!playsinline&!autoplay&!muted&!controls&origin=http%3A%2F%2Flocalhost%3A3000
This does work https://player.twitch.tv/?allowfullscreen&video=&channel=yogscast&!playsinline&!autoplay&!muted&origin=http%3A%2F%2Flocalhost%3A3000
The only difference between the two is !controls is present in the url that doesn't work, and it isn't present in the one that works.
The first url is what React-Player generates if the controls property is set to false.

I found the error @CookPete . I'm using next.js for server side rendering. When the player is rendered in the browser Twitch works perfectly, but when the page is reloaded, it says:

So, what conclusion? I'm going to investigate if my server is wrong (for example render twice or redux error with second rendering) but could you check if something in react-player has incompatibilities with server side rendering with nextjs?
Thanks

Example here: nextjs with Twitch video


Send "collective" report to hosts with active budget

@alanna This how it's gonna look in this state.
Sample Foundation July 2020

Sample OCNZ July 2020

Cool - looks good for MVP. Obviously we could improve reports a lot but that's another project.


RC Spot Check: Atomic Interactions 1.2.0-rc.3

@KatieWoe, @ariel-phet, and @arouinfar - atomic-interactions/1.2.0-rc.3 is ready for spot-check testing.  This release is phet brand only.  It is derived from the same code snapshot as the recent States of Matter 1.2 release, and we've already done a couple of RCs from this branch, so a spot check that focuses on the resolved issues should be sufficient.
For this testing, please only report issues that do not exist on the published version unless they are particularly egregious.
Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book
for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Test the Game Up harness on at least one platform.
Check this LoL
spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version
Try to include version numbers for browsers
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if
there is a problem.

Focus and Special Instructions
This is the 3rd RC from the 1.2 branch, so the focus should be on verifying that the issues found during testing of the previous RC have been adequately addressed.

Issues to Verify

[ ] Mouse can be off set while dragging adjustable attraction values
[ ] Possible to drag force arrows to move atom

Link(s)

Simulation
iFrame
XHTML
Test Matrix
Legends of Learning Harness

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

[ ] Win 10 Chrome
[ ] Win 10 Firefox
[ ] Mac 11 Safari
[ ] iPadOS Safari
[ ] ChromeOS

[ ] Win 10 Chrome
[ ] Win 10 Firefox
[ ] Mac 11 Safari
[ ] iPadOS Safari
[ ] ChromeOS

Closing due to https://github.com/phetsims/QA/issues/606


Comprehensive Frame Update

Introduction
Purpose of this ticket is to keep track the recount of all characters in accordance with gcsim's frame framework, which differs slightly from existing count in that we require recovery frame and cancellable frame for all possible combination of actions.
We're looking for help from everyone with both recording and frame counting. If you are able to contribute please leave a comment below. Looking for help both in terms of just providing raw footage as well as performing the count. It'd help us greatly if you can provide help with either or (or both should you desire).
Recording requirement

Record at consistent 60fps 720p minimum
For each character, record all possible combinations of various ability, including but not limited to

string of normal attacks i.e. N1 -> N5 -> N1 (usually done by button mashing)
cancelling of each normal attack with charge attack i.e. N1 -> CA, N2 -> CA, etc...
cancelling of skill with every other possible action i.e. NA, CA, skill, burst, dash, jump swap
cancelling of burst with every other possible action i.e. NA, CA, skill, burst, dash, jump swap
cancelling of CA with every other possible action i.e. NA, CA, skill, burst, dash, jump swap
any other combinations for character with special abilities i.e. skill hold, etc...

We'll need 3 trials of every combination to help average out any recording error
All footage should be done vs empty air (not hitting trees) as sim is using no hitlag frames
Footage should start clearly from standing/rest position and end at standing/rest position to avoid cutting off any part of the animation
Footage should not be obstructed in anyways by trees, rocks, enemies, etc...

 Original comment from Tsym as follows:
This is a global issue to track frame data issues/fixes. After some investigation, the primary set of issues relate to how KQM frames are measured:

For NA/CA frames, KQM frames are usually until hitmark (or from hitmark to hitmark). Currently, the frames that we have loaded are therefore usually ok until the last NA/CA in the sequence, when there will be no ending animation. However practically this is not a significant concern because most NA/CA chains in the game are cancelled in some way (mostly through dashes or jumps).

The one exception here are aimed shots, whose frames in KQM are from start until shot release. Since aimed shots are usually not dash/jump cancelled, these require special attention.

For skill/bursts that do involve a hit, KQM frames are until the hitmark, so they will tend to run fast.
For skill/burst frames that do not involve a hit during the main animation (e.g., Barbara, Venti), KQM frames are until the end of the animation and so are usually decently accurate.

The sim running a bit fast is therefore partially a result of skill/bursts with hits having missing ending animation frame data. This will however take a significant amount of time to fix.
The current proposed plug solution is to add a delay parameter so users can add a custom delay to the end of animations. See #206

Ayaka cancel frames to count:
https://youtu.be/ulTSQRrR4n8

https://docs.google.com/spreadsheets/d/1BdWsPgnZFJ2xFmKgYevvBXYQeDqOLaPpL_VsFzjjiiI/edit?usp=sharing
xingqiu frames sheet. currently only 1 trial each (in future counts I will do 3) and not all combos tested, let me know how much more needs to be done before opening a pr.

https://docs.google.com/spreadsheets/d/1BdWsPgnZFJ2xFmKgYevvBXYQeDqOLaPpL_VsFzjjiiI/edit?usp=sharing xingqiu frames sheet. currently only 1 trial each (in future counts I will do 3) and not all combos tested, let me know how much more needs to be done before opening a pr.
more chars: Bennett: https://docs.google.com/spreadsheets/d/1wzaBId5I0wxqlikpdZZlXaXRDuCykbdn4izbK__OHss/edit?usp=sharing Xiangling: https://docs.google.com/spreadsheets/d/1lWpwV9RVKsk9X3ghww7ooujxJsonfqC9krWzrXffv3c/edit?usp=sharing

ideally we get to 3 samples but I'll start coding these in as soon as I get the chance to

used koli's video to implement ayaka frames here, macro footage really does make this process a lot easier

#447 updates noelle but missing:
attack -> charge
attack -> walk
charge -> x

all done (for now until tomorrow) :) this is also tracked in docs as well


Object composition in propTypes causes 'default-props-match-prop-types' error

Consider the following functioning example:
elementEventCardBaseShape = {
  calendarLink: mediaFileShape,
  mapLink: PropTypes.string,
  startDate: PropTypes.string,
  locationName: PropTypes.string,
  street: PropTypes.string,
  city: PropTypes.string,
  region: PropTypes.string
};

ElementEventCard.propTypes = {
  ...elementEventCardBaseShape,
  lang: PropTypes.string
};

ElementEventCard.defaultProps = {
  lang: 'en',
  calendarLink: {},
  mapLink: '',
  startDate: '',
  locationName: '',
  street: '',
  city: '',
  region: ''
};

Where all but 'lang' throw an error for said prop supposedly having no matching propType.
Am I missing something?

I think that we probably need a shared way of getting all propTypes of a component; that way should handle in-file spreading of other object literals; and that would address this bug.

One would think having babel as the parser would take care of this... Would love to give this a try, yet I'm afraid at first glance this is complexity beyond my current understanding of the package.

babel has a jsx parser; it's not a React parser.

So Babel's parser wouldn't expand the '...' into something the react parser would make readable for eslint? haha as said before, the understanding of interactions and dependency complexities here eludes me. Wish I could be more useful 👍

Sorry if I'm being unclear; there's no such thing as a "React parser".
This plugin has heuristics to try to statically determine when something is a React component; it similarly has heuristics to try to statically infer the propTypes from an inferred React component; I suspect that if all rules used the same logic for both, everything would get much more reliable.

Need this fixed!!! Importing propTypes via spread causes plugin to bug out.

@virgofx a PR is welcome.

We import things via spread all the time, so I don't think this is the blocker you're perceiving it to be.
There's no "high priority" tag; everything that people have time for is addressed quickly, for everything else, it doesn't matter what the priority is if nobody has time to fix it.

I think that we probably need a shared way of getting all propTypes of a component; that way should handle in-file spreading of other object literals; and that would address this bug.

https://github.com/yannickcr/eslint-plugin-react/issues/1674#issuecomment-362729395
FWIW I've been thinking about this comment in the background for some time, I think this could be a huge improvement.
I feel like this can be handled in a similar way to how Components.detect() works, by defining certain hooks and "mixing" them into the rules, which would then read components.list() and make use of the accumulated data in their own Program:exit. Although not sure if adding all of this functionality to Components.js would bloat it too much.

We could always make a new propTypes.js alongside it.

Hi, any improvements on this issue ? Is there an available hack/pattern ?
I don't like the idea of disabling eslint rules either.
Thanks

Same issue here. Would love to see it fixed. Unfortunately I have no idea how to help 😞


DisplaySettings json & md file updated as per code

Documentation enhancement for Display Settings plugin

 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.


Notification Device on Android TV

Hello,
First of all, thank you for your plugin.
I'm using it for an Android TV application.
Everything works fine but every time a video starts, I get the message “Device is a TV” which appears at the beginning of the video for 3/4 seconds.

Hello @jepiqueau,
Thank you very much !!!
thank you very much
I have deleted the lines mentioned and the message no longer appears.
🎉👍

@stephanevallejo you are welcome


Own _ViewImports.cshtml file change detection

Right now WTE owns the monitoring of _ViewImports.cshtml and then appropriately re-parsing impacted cshtml files. We should own that code.

https://github.com/aspnet/Razor/commit/8abbaa46ccc28abf30d39f841a73a69df9b9a3bc


Any interest in support for SCSS?

If there's interest, I can submit a PR, I recently added this to my project using mern...cool project!

Send a PR @evansendra ! :wink:

done!