Update! !atedpU

i see a lot of commits this year but the google play app dont get a update long time
so will you update it?
thanks for this awesome emulator without any ads

Hi, yes I will update the Android app at some point, I just haven't done much work on it recently. I had wanted to get multiplayer in there at some point for the next update, but it's probably worth making a release sooner rather than later to fix some existing issues.

Ok, so I've finally started rolling out a new Android release, should be available within the next day or so. Sorry for the long break!

The latest update should now be available to everyone


Improve building from source instructions

Thanks! But I don't want to make the Contributing file too big because maybe it makes it more tedious to read and encourages less contribution.
I recently updated the Contributing.md file to reference a list of dependencies. It also says that you need LLVM, so I think that's enough for now.

(I'm doing a pull-requests/issues cleanup, the number is starting to get higher)

Is there harm in putting better directions in a separate file then if they don't belong here?

@yyyc514 Not at all, if you want we can create a Wiki page for that.


Made the session log out icon a bit smaller

Before:

After:

Also, if you're reading this, maybe consider adding a license to the repo, I recommend the MIT license

Oh yeah, I forgot other languages exist 💀

How's this?


Topic/websocket interface

Coverage decreased (-0.4%) to 16.71% when pulling b88a2e75cbc9e2c254cc5fd9e246bf5606fa8ede on topic/websocket-interface into 82314612f76bd146d0049b3779646366225b3f52 on master.


Common Interface needed for all node types, to facilitate logging

I ran into a problem, where I am trying to create logging for checking validity of XML data.
It would be very convenient if all node types and attribute had a common interface or base class, which holds the name, file line number, type identifier and possibly reference to the value, so that a logging function can be made independent of the type being sent for logging.  I can implement the change and post back for review.

XMLNode is the common base class.

Except XMLNode is not a base class for the XMLAttribute

Maybe that is because it is not a type of node. It is an attribute which is entirely different.
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: tomwjaw @.>
Sent: Wednesday, January 18, 2023 5:53:08 AM
To: leethomason/tinyxml2 @.>
Cc: Subscribed @.***>
Subject: Re: [leethomason/tinyxml2] Common Interface needed for all node types, to facilitate logging (Issue #926)
Except XMLNode is not a base class for the XMLAttribute
—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fleethomason%2Ftinyxml2%2Fissues%2F926%23issuecomment-1386526927&data=05|01||3d81dc01e0da44612ede08daf918474e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638096179908690875|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=sgMYVCzDnvUn3Bij%2FsZ10SAD8xX7pHTCLpvfEdG2VAI%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB45RM6DPVLIJCCVJL5QSGTWS6AMJANCNFSM6AAAAAASJTNO24&data=05|01||3d81dc01e0da44612ede08daf918474e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638096179908690875|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=1n1%2F7Pz8yyz%2Fi77YKqz0PB2R8WkKU%2FDstxL7nkHzJdQ%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Test/highlight correct nb

Tests for revealActiveDocumentInViewlet

Coverage decreased (-0.1%) to 37.021% when pulling 8f2929d0f425c40c846f11701e06f0a26f21b46a on test/highlightCorrectNb into de69e73a9d27aaa4759b86fb50fb0c8665d02b53 on main.

I'm curious why some files are showing lower test coverage here in related areas. Can you take a look, @MaddyDev?

I'm curious why some files are showing lower test coverage here in related areas. Can you take a look, @MaddyDev?

I was confused about that as well. Let me take a look.


prototype for new design LORE (with LORE id)

this is a enhanced version of https://github.com/NVIDIA/spark-rapids/pull/10983, allowing uesr to specify what operator to dump using the LORE ID (By @liurenjie1024 ). Check more explaination of LOREID at https://github.com/NVIDIA/spark-rapids/issues/10942#issuecomment-2151541838
we'll choose this PR or #10983  to use at customer site

build

build

build

build

build

build

build

build

build


Technical interview tasks

Summary
Technical interview tasks
Occurred changes and/or fixed issues
na
Technical notes summary
na
Areas or cases that should be tested
na
Areas which could experience regressions
na
Screenshot/Video
na
Checklist

[ ] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[ ] The PR has a Milestone
[ ] The PR template has been filled out
[ ] The PR has been self reviewed
[ ] The PR has a reviewer assigned
[ ] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[ ] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

Sorry it's for interview task, please ignore this.


[WIP] Property delegates as custom attributes

This is an implementation of property delegates as custom attributes, under discussion in this pitch thread. The implementation is mostly complete, although there are some annoying known bugs:

init(initialValue:) that takes an @autoclosure is currently broken
Property delegates cannot be used on local variables; only properties of types work well (lazy is similarly broken and always has been!)

@DougGregor Would it be possible to have a toolchain created to play around with Property Delegates? I'd like to use them to improve a library Im working on as a way to test them out.

@hartbit let me make sure things are back in a working state now, and once they are I'll build a toolchain. I just got to the point where they work end-to-end, so long as you don't touch @autoclosure.

@swift-ci please smoke test

@swift-ci please build toolchain

@swift-ci please build toolchain

@swift-ci please build toolchain

@swift-ci please build toolchain

@swift-ci please smoke test

@swift-ci please build toolchain

@swift-ci please build toolchain

@swift-ci please smoke test

That's a lot of toolchains 😂

@swift-ci please build toolchain

@swift-ci please please please please please build toolchain

@swift-ci please build toolchain

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci build toolchain

@swift-ci build toolchain Linux

@swift-ci please smoke test Linux

@swift-ci please smoke test

@swift-ci please build toolchain

@swift-ci please test

@swift-ci please build toolchain

Build failed
Swift Test OS X Platform
Git Sha - 85ff735eb5c1120af3c47d7c5d682aef71aa5038

Build failed
Swift Test Linux Platform
Git Sha - 85ff735eb5c1120af3c47d7c5d682aef71aa5038

@swift-ci please smoke test macOS

With the implementation in the toolchain, the DelayedMutable example from the proposal fails to compile:
@propertyDelegate
struct DelayedMutable<Value> {
    private var _value: Value? = nil

    var value: Value {
        get {
            guard let value = _value else {
                fatalError("property accessed before being initialized")
            }
            return value
        }
        set {
            _value = newValue
        }
    }

    /// "Reset" the delegate so it can be initialized again.
    mutating func reset() {
        _value = nil
    }
}

class Foo {
    @DelayedMutable var x: Int

    init() {
        // We don't know "x" yet, and we don't have to set it
    } // error: Return from initializer without initializing all stored properties

    func initializeX(x: Int) {
        self.x = x // Will crash if 'self.x' is already initialized
    }

    func getX() -> Int {
        return x // Will crash if 'self.x' wasn't initialized
    }
}

Is this known?

@hartbit ah, thank you! that should be @DelayedMutable() var x: Int. I'll fix the proposal

@DougGregor The () part of the syntax is surprising because the proposal does not talk about it much. When is it required?

@hartbit The () is there to call the no-parameter initializer. Without it, the delegate instance hasn't been initialized. There's no special case here

I got Lazy working, so time to build a new toolchain

@swift-ci please smoke test

@swift-ci please build toolchain

@swift-ci please build macOS toolchain

@swift-ci please build toolchain macOS

@hartbit Can't the parentheses-less @DelayedMutable syntax be equivalent to calling the parameter-less initializer? That's the direction the Custom Attributes proposal is going towards.

@swift-ci please build toolchain macOS

@swift-ci please build toolchain macOS

macOS Toolchain
Download Toolchain
Git Sha - a4294bb9025b628a5195c0e4366010ba6aa6bd18
Install command
tar -zxf  swift-PR-23701-287-osx.tar.gz --directory ~/

@swift-ci build toolchain

@swift-ci please build toolchain macOS

@hartbit Can't the parentheses-less @DelayedMutable syntax be equivalent to calling the parameter-less initializer? That's the direction the Custom Attributes proposal is going towards.

I don't think that's a good idea, because you would lose the ability to distinguish between "not initialized" and "initialized via the zero-parameter initializer".

macOS Toolchain
Download Toolchain
Git Sha - 3b445b12d9b56cf9f75ae6832af26859ef972dc8
Install command
tar -zxf  swift-PR-23701-290-osx.tar.gz --directory ~/

@swift-ci please smoke test

Linux failure looks unrelated:
  /tmp/CFamilyTargets_ModuleMapGenerationCases.fQZYzj/CFamilyTargets_ModuleMapGenerationCases/Sources/Baz/main.swift:4:8: error: no such module 'UmbrellaHeaderFlat'
01:22:33     import UmbrellaHeaderFlat
01:22:33            ^

Is this error expected with the toolchain linked in SE-0258?
Ld /Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Products/Debug/PropertyDelegates.framework/Versions/A/PropertyDelegates normal x86_64 (in target: PropertyDelegates)
    cd /Users/tanner0101/dev/vapor/sandbox/pdel-spm
    export MACOSX_DEPLOYMENT_TARGET=10.10
    /Library/Developer/Toolchains/swift-PR-23701-287.xctoolchain/usr/bin/clang -arch x86_64 -dynamiclib -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -L/Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Products/Debug -F/Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Products/Debug -F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -filelist /Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Intermediates.noindex/PropertyDelegates.build/Debug/PropertyDelegates.build/Objects-normal/x86_64/PropertyDelegates.LinkFileList -install_name @rpath/PropertyDelegates.framework/Versions/A/PropertyDelegates -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -rpath -Xlinker /Library/Developer/Toolchains/swift-PR-23701-287.xctoolchain/usr/lib/swift/macosx -mmacosx-version-min=10.10 -Xlinker -object_path_lto -Xlinker /Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Intermediates.noindex/PropertyDelegates.build/Debug/PropertyDelegates.build/Objects-normal/x86_64/PropertyDelegates_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -fobjc-link-runtime -L/Library/Developer/Toolchains/swift-PR-23701-287.xctoolchain/usr/lib/swift/macosx -Xlinker -add_ast_path -Xlinker /Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Intermediates.noindex/PropertyDelegates.build/Debug/PropertyDelegates.build/Objects-normal/x86_64/PropertyDelegates.swiftmodule -Xlinker -dependency_info -Xlinker /Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Intermediates.noindex/PropertyDelegates.build/Debug/PropertyDelegates.build/Objects-normal/x86_64/PropertyDelegates_dependency_info.dat -o /Users/tanner0101/dev/vapor/sandbox/pdel-spm/DerivedData/PropertyDelegates/Build/Products/Debug/PropertyDelegates.framework/Versions/A/PropertyDelegates

ld: file not found: /Library/Developer/Toolchains/swift-PR-23701-287.xctoolchain/usr/lib/arc/libarclite_macosx.a
clang-7: error: linker command failed with exit code 1 (use -v to see invocation)

@tanner0101 It's a known bug (https://bugs.swift.org/browse/SR-9972). As a workaround, you can symlink libarclite_macosx.a in the default toolchain to the PR toolchain:
$ ln -s /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_macosx.a /Library/Developer/Toolchains/swift-PR-23701-287.xctoolchain/usr/lib/arc/libarclite_macosx.a

PS: there's also a more recent toolchain for this PR, number 290

@swift-ci please smoke test

@swift-ci please build toolchain

And... another rebase is incoming.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@DougGregor - sigh this broke the windows build :-( https://dev.azure.com/compnerd/windows-swift/_build/results?buildId=1697

@swift-ci Please built macOS toolchain


Subscription's Recommendations - Inconsistency in response from Assessements - List API of Defendor for cloud

Problem Statement:
While fetching recommendations corresponding to all subscriptions in an account using
GET https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Security/assessments?api-version=2020-01-01
we are getting different set of recommendations against the same subscription if we hit the API 1-2 days apart and after some time the response goes back to what it was earlier, all this while there has been no change on the account side
Also, the set of recommendations returned corresponding to 2 different subscriptions is also different i.e. some recommendations are missing from the response of Assessment - List API of a subscription.
Queries:
Is there any known reason for this behavior, inconsistency in response for same asset
On what criteria does this API, decide to whether to return a recommendation in the response or not

Adding Service team to look into this.


some improvement.

some improvements :

permission issue

persistent data for mysql

persistent cache for composer.

Let this be simple as is. Don't make it complicated. So far it is simple and easy to use.


Espresso: match with ID (hopefully this is more stable)

Whoops, sorry @whym , there is a merge conflict with #784

From what I understand, this change was incorporated there (https://github.com/commons-app/apps-android-commons/pull/784/commits/2e4b25aa99328582e93030b147b1c7dedd33f384), so I'm closing this.


Update ask message of projectID for gitlab-webhook

Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

Codecov Report

Merging #798 (1deeb58) into main (02c3594) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #798      +/-   ##
==========================================
+ Coverage   65.82%   65.86%   +0.03%
==========================================
  Files          75       75
  Lines        4577     4582       +5
==========================================
+ Hits         3013     3018       +5
  Misses       1277     1277
  Partials      287      287

Impacted Files
Coverage Δ

pkg/cli/webhook/gitlab.go
53.01% <100.00%> (ø)

pkg/acl/acl.go
100.00% <0.00%> (ø)

pkg/consoleui/tektondashboard.go
100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Support batching

Is your feature request related to a problem? Please describe.
LMAX's reference implementation allows publication of multiple events through the EventSink type. We should support this too.
Describe the solution you'd like
The LMAX implementation exposes lots of overloaded methods with are semantically the same barring the number of translator objects passed in (and lots of boilerplate unit tests for each variation). It would be nice to have a smaller and more Swift-y API than this.

EventSink Javadoc here


gyp: Undefined variable uv_library in deps/libuv/uv.gyp

I'm adding libuv as a dependency in a gyp based project:

foo.gyp:

{
  'targets': [
    {
      'target_name': 'foo',
      'type': 'executable',
      'dependencies': [
        'deps/libuv/uv.gyp:libuv'
      ]
    }
  ]
}

Then I run gyp -d foo.gyp and get this error:
INCLUDES:input.py:388:LoadTargetBuildFile Loading Target Build File 'foo.gyp'
INCLUDES:input.py:388:LoadTargetBuildFile Loading Target Build File 'deps/libuv/uv.gyp'
VARIABLES:input.py:745:ExpandVariables Matches: {'content': 'uv_library', 'is_array': '', 'replace': '<(uv_library)', 'type': '<', 'command_string': None}

gyp: Undefined variable uv_library in deps/libuv/uv.gyp

However uv.gyp clearly adds its own common.gypi (in sources) which clearly defines a default value for uv_library:
{
  'variables': {
    'uv_library%': 'static_library', # allow override to 'shared_library' for DLL/.so builds

NOTE: I'm running this stuff in OS X. Is it related to this GYP bug:
  # GYP bug.
  # On msvs it will crash if it gets an absolute path.
  # On Mac/make it will crash if it doesn't get an absolute path.
  if sys.platform == 'win32':
    args.append(os.path.join(uv_root, 'uv.gyp'))
    common_fn  = os.path.join(uv_root, 'common.gypi')
    options_fn = os.path.join(uv_root, 'options.gypi')
    # we force vs 2010 over 2008 which would otherwise be the default for gyp
    if not os.environ.get('GYP_MSVS_VERSION'):
      os.environ['GYP_MSVS_VERSION'] = '2010'
  else:
    args.append(os.path.join(os.path.abspath(uv_root), 'uv.gyp'))
    common_fn  = os.path.join(os.path.abspath(uv_root), 'common.gypi')
    options_fn = os.path.join(os.path.abspath(uv_root), 'options.gypi')

If so, does it mean that I need to pass those args when I run gyp on my project?

I've also checked this similar old issue and have created a common.gypi in my root folder and added it to the sources of my foo.gyp. It contains:
{
  'variables':
  {
    'uv_library%': 'static_library'
  }
}

It does not work, same error.

Sorry, according to the similar issue I've should call gyp -Icommon.gypi. Indeed it works... Magic...

Sounds like it's resolved?  I'll close.

Yep. It seems that the magic under common.gypi is accepted as it is :)


Audio support

Is sending audio planned?

added here https://github.com/aldinokemal/go-whatsapp-web-multidevice/releases/tag/v4.9.0


Bump version

Codecov Report

Merging #158 (ae3b4af) into main (07fa683) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #158   +/-   ##
=======================================
  Coverage   90.53%   90.53%
=======================================
  Files          10       10
  Lines         835      835
=======================================
  Hits          756      756
  Misses         79       79

Impacted Files
Coverage Δ

weather_command/main.py
75.40% <100.00%> (ø)

Continue to review full report at Codecov.

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


Do we need "Done" option after exporting Jar file?

The effect of Done is the same as the "exit" button, so I'll remove it.


mid-word inline italics

If I type into the draft editor: abcXYZabc where XYZ is italic , it will render the markdown as abc_XYZ_abc (this is fine).  When that gets converted back into DraftJS, the text is rendered as abc_XYZ_abc.

Yeah this is sort of a... hm. I've noticed this before and I'm not sure what the best way to fix it is. It seems markdown doesn't work like that, eg if I type this in here on github: abc_XYZ_abc it won't be italicized. There has to be a space before the _ symbol for it to get picked up. But by inserting a space when converting from draft to markdown, we are changing the content which may also not be desired.
So it seems the options are:

Insert space, which might be bad
Don't italicize in this case, which sadly will also confuse people 😢

Tentatively labeling as a wontfix pending further discussion on the best course of action 😄

Perhaps using * for emphasis is the best approach.  Intraword underscores are not respected, but intraword asterisks are.  (I just learned this this moment).


[VSCode analysis failed]plugin-vue-jsx not support withDefaults

Describe the bug
when i use both withDefaults and

<template>
  {{ props.columns }}
</template>

vscode give me lots of error(at line 1, col 1):
'name' is deprecated.ts(6385)
lib.dom.d.ts(17329, 5): The declaration was marked as deprecated here.
'await' has no effect on the type of this expression.ts(80007)
'</' expected.ts(1005)
JSX element 'T' has no corresponding closing tag.ts(17008)
JSX element '__VLS_NonUndefinedable' has no corresponding closing tag.ts(17008)
Unexpected token. Did you mean `{'}'}` or `}`?ts(1381)
Expression expected.ts(1109)
'}' expected.ts(1005)
'(' expected.ts(1005)
',' expected.ts(1005)
Unexpected token. Did you mean `{'>'}` or `>`?ts(1382)
Identifier expected.ts(1003)
Cannot find name 'P'.ts(2304)
'Pick' only refers to a type, but is being used as a value here.ts(2693)
Cannot find name 'keyof'.ts(2304)
Cannot find name 'K'.ts(2304)
Cannot find name 'T'.ts(2304)
Cannot find name 'type'.ts(2304)
Cannot find name '__VLS_NonUndefinedable'.ts(2304)
The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type.ts(2362)
Cannot find name '__VLS_TypePropsToRuntimeProps'.ts(2304)
Cannot find name 'columns'.ts(2304)

when i change lang="tsx" to lang="ts" vscode now work well.
when i remove withDefaults vscode work well too.
but when i use them both, lots of error appear.
env info:
VSCode: 1.67.1
Typescript: 4.6.3
vite: 2.9.8
@vitejs/plugin-vue-jsx: 1.3.10

any suggest?
i don't know what cause it, so if there is nothing about this plugin, please let me know.
Reproduction
https://stackblitz.com/edit/vitejs-vite-yrwiv1?file=MyComponent.vue
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
    Memory: 3.53 GB / 15.87 GB
  Binaries:
    Node: 14.17.0 - D:\software\nodejs\node.EXE
    Yarn: 1.22.18 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.17.0 - D:\software\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.47)
    Internet Explorer: 11.0.19041.1566

Used Package Manager
npm
Logs
no error log.
app running well.

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I think this should be reported to https://github.com/johnsoncodehk/volar instead because the error comes from volar.


Cannot swipe on firefox when using html5 video

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 5.3.7.

Platform/Target and Browser Versions: Firefox 72.0.2 Mac Mojave.

Live Link or JSFiddle/Codepen or website with isssue: https://stackblitz.com/edit/swiper-demo-1-default-k1tq5u.

What you did
Swipe to the next slide
Expected Behavior
I can swipe to the next slide
Actual Behavior
Swiping does't work
Swiping works in Chrome, Safari and IE

my hunch is that the video element is somehow hijacking the touch event by either sitting in a different z-index or due to the swiper-wrapper having a translate3d. however, manipulating the z-index of the video and adding transform-style: preserve-3d to the swiper-wrapper, but it doesn't seem to change anything.
i manage to get a workaround by disabling the video's pointer event and using a click event on the swiper-slide to trigger the video, but the solution is not ideal since the video has to be paused before the touch events can be registered. if anyone has a better idea. i'm all for it.
https://stackblitz.com/edit/swiper-firefox-video-fix?file=index.html

@vitogoh  it works perfectly in latest firefox.

I just upgraded to v10.0.4 and this problem persists in Firefox. Is there a solution?

Sadly still a thing

@catapop84 Got it working adding pointer-events: none; to the video element. In my case the users are not expected to interact with the video, so it works for my use case.


⚠ Fortnite has degraded performance

In bf63942, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1613 ms

Resolved: Fortnite performance has improved in c5d372e.


Fixes TabController Listener call twice. (#69763)

Description
TabController addListener calls once then call twice when switching tab index,
notifyListeners only when animate complete
#69763

@googlebot I signed it!

Hi @6a209 , this has not been updated in a while, and is not in a state for code review, so I am going to close it for now. If you would like to come back and continue working on it, feel free to re-open! Thanks for the contribution!


Sched yield

Per previous conversation with @moyix.
This adds sched_yield() calls to pipe loops when we encounter a full or empty pipe. This doesn't change overall pipe performance and avoids us busy looping when there are more cages than processors.

Confirmed this with more testing. If we don't do these yields and (cages > # processors) we get ~100x slowdown.


Invalid Idea config prevents from editing project structure

With a recent update of Intellij Ultimate (something between 2018.2 and 2018.3.5) the plugin now generates an invalid config. The plugin adds the apt generated sources path to both source folders and generated source folders.

Image

Idea doesn't compain about this until you edit something in the project structure. F.ex editing the output path inside Paths.

Image

The error message is:

Source root "path to apt generated source main" is duplicated in module "my module"

We need to edit one of the Entries in Facets (related to GWT). These values are kept after a Gradle refresh inside Intellij.
Do you have an idea how we can fix this problem?
Config:
plugins {
    id 'java'
    id 'net.ltgt.apt' version "0.21"
}

group 'test'
version '1.0-SNAPSHOT'

apply plugin: "java"
apply plugin: "maven"
apply plugin: 'net.ltgt.apt-idea'
sourceCompatibility = 1.8

repositories {
    mavenCentral()
}

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.12'
}

Using Gradle 4.10.2 but also occurs with version 5.2.

My recommendation is to stop using this plugin: https://github.com/tbroyer/gradle-apt-plugin/blob/master/README.md#do-without-the-plugin

Oke.


Update Swagger version to 1.6.2

Checklist

[x] the [contributor license agreement][] is signed
[x] commit message follows [commit guidelines][]
[ ] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
Update Swagger to make apidocs.do work properly.

I am curious why Renovate Bot does not update this :thinking: . 1.6.2 has been released for several days

same as https://github.com/openequella/openEQUELLA/pull/1996 ?

same as #1996 ?

oops I did not realise we already have a PR for that...but not sure why builds failed. I will close this one.

Either PR works, the renovate one seems to have picked up two (potential unrelated changes), it might take some work to get that one running.
If the issue persists, let's merge this PR instead.

#1996 is blocked by https://github.com/renovatebot/renovate/issues/6723 let's go ahead with this PR.

#1996 is blocked by renovatebot/renovate#6723 let's go ahead with this PR.

Cool. Once builds are green I will merge it.


chore: un-template all of the ConfigFactory keys.

Summary of Changes
Modify the sample_data_loader.py:

Added a more thorough introductory comment explaining what each of the functions is doing.
Un-formatted all of the keys, for improved readability for those new to amundsen.

Only doing this for sample_data_loader.py for now, since seems to be the typical entrypoint into amundsen. If there's consensus on the lyft end that the best pattern is to have formatted keys, perhaps it makes sense to leave these other scripts as-is. :)
This is a first step in addressing this: https://github.com/lyft/amundsen/issues/371
Tests
None, as this just changes the example code.
Documentation
Modified the docstring at the top of the sample script.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[X] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[X] PR includes a summary of changes.
[X] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[X] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[X] PR passes make test

thanks @rsyi ! Also +1 on your semantic pr title!

no problem. it was super easy with vim recording :)


switch from Express to Connect (less dependencies)

Fastify?

I believe Fastify is more Express-like
Connect is a simple middleware layer


Fix build failure on Windows

Fixes https://github.com/openssl/openssl/issues/530

+1

+1

submitted, thanks!


Phase retrieval example notebook

An example notebook for the new phase retrieval methods in CIL
Depends on https://github.com/TomographicImaging/CIL/pull/1737

Just a note, because this depends on v24.1.0, we can't merge until we have tested the rest of CIL-Demos with that version of CIL

So far I wasn't able to run the notebook due to an error with importing 'Filter'

ImportError: cannot import name 'Filter' from 'cil.processors' (/home/lhe97136/miniconda3/envs/cil_24.1/lib/python3.12/site-packages/cil/processors/init.py)

Some initial comments though
Notebook outputs
We don't usually commit notebooks with their outputs loaded, as it's a lot to save in the repo! You can use nbstripout to remove outputs
Intro to notebook

I think it would be great at the start of the notebook to mention that it requires tomopy and CIL v24.1.0 or greater.
Could add a cell that prints the CIL version they have like in https://github.com/TomographicImaging/CIL-User-Showcase/blob/main/example_contribution/example_contribution.ipynb

Comments
Could we remove the commented show2D code in the first cell that uses show2D?

Turns out Filter is imported but not used so its just the import line that needs deleting

Hi @lauramurgatroyd thank you for taking a look :)
Sorry I had not pushed the latest version, it should now work with the reference to Filter removed.
Thank you for your comments:

I think I've suppressed the cell outputs now but not sure ??
Good idea with the version check, I've added the specification and print statement
I've removed the commented show2D

Thanks, the changes look good.
Nice notebook overall, I just have some suggestions for improvements 😄

Still appears to have the outputs pushed

Line profiles throughout:

Is it possible to move the legend to not cover the data? Not sure if it's just a problem on my computer?

Would it be possible to add titles that describe where they cut through the data relative to the show2D plots above e.g. "Line Profile at horizontal_x=xx", also adding axis labels to the show2Ds would help with this

Cone beam data:

could the magnification print either be deleted or labelled as magnification?
I think it's worth mentioning in the notebook that tomopy only tackles parallel beam (I think that's true??)
I didn't really understand why the scaled version is so much lower than the other plots?

TomoBank

Please add a note that they may need to update the 'filename' to include the full path to where they saved the data
Do we need to run on the full dataset? It takes a long time and I wonder if it can be reduced (15mins to run PaganinProcessor in one cell and 27min in another)
I noticed some 'Finish Ring Remover' prints - not sure where they come from?
might it be useful to show the difference image between recon_phase and recon_phase_g

I think we're ready to merge?


Removed whitespace

EDIT: Present also in md4.h, md2.h and md.h
EDIT2: Well, I don't know why, but it is present also in some sha headers.

Hi @pfrankw Thank you for the contribution! It is probably an error of copy\paste

@dgreen-arm - can you please fix the other whitespace mentioned above, as suggested by @hanno-arm?

All the mentioned whitespace issues have been fixed and merged in #1294.

I've checked and confirm the extra space issue is fixed in development and mbedtls-2.7, which was fixed in #993 and it's backport. I don't think it merits backporting a fix to remove a space, so this PR can be closed.


Add back non-immediate timeout 0 and reading handshake_timeout_in config

The CI has been broken because of autest failures in tls_hooks* tests.  The problem was that the handshake timeout default to 0, and setting inactivity timeout to 0 was causing the ssl netvc object to be deleted on the next inactivity cop iteration.
This happened because of a clean up in 66f23063e1cb44ec04136853952dc299303a832d which removed logic to set the timeout to the default inactivity timeout if the timeout argument was 0.  The documentation for the handshake timeout seems to imply that setting it to 0 should disable the timeout.
Also commit from me from January 2018 remove the logic that read the configuration to set the tls handshake timeout.  This PR adds that back in.
It isn't clear to me what the correct solution.  To get the CI going again, I'm adding back the if statement to go back to the previous behavior with respect to 0 inactivity timeouts.

Remember to remove the Milestones on PRs being closed.


Use preferred tile.openstreetmap.org URL

as noted in https://github.com/openstreetmap/operations/issues/737, {a,b,c}.tile.openstreetmap.org is deprecated, and one should simply use https://tile.openstreetmap.org - no subdomains, no short names.
Latest F-droid release (OsmBug 1.3.6) at least seems to use a.tile.openstreetmap.org and its friends.

Just a heads up that the network log for version 1.4.0 only uses tile.openstreetmap.org but I do not see related changes in the recent commits. Maybe something changed in OsmDroid?

Yes, I can confirm it seems to be solved with 1.4.0 F-droid release too! Closing.


Suggestion needed - Wrapping AsyncGenerator

Sorry for opening an issue  with what is basically a question/ feedback for API ergonomics...
Has any of you stumbled upon a situation where you'd want to wrap an AsynGenerator in a Result somehow where the ultimate goal is to typify the possible errors and effectively not have it throwing exceptions?
Let's say that the AsyncGenerator is wrapping a REST API Call and yielding results over time:
type SomeData = {};

type SomeApiResult = {
    content: SomeData[];
    nextToken?: string;
};

const getData = async (nextToken?: string): Promise<SomeApiResult> => /*...*/;

async function* getAllData(): AsyncGenerator<SomeData> {
    let loadMore = true;
    let prevNextToken: string | undefined = undefined;
    while (loadMore) {
        const result = await getData(prevNextToken);
        for (const data of result.content) {
            yield data;
        }
        loadMore = result.nextToken !== prevNextToken;
        prevNextToken = result.nextToken;
    }
}

One way I see it, is to have the generator return Results and as soon as an exception is thrown/promise rejection occurs, yield the error. This breaks the iteration as soon as the error occurs however, the side effect is that now the consumer has to unwrap each received value from the result and this breaks the norms of common generators.
async function* getAllData(): AsyncGenerator<Result<SomeData, SomeError>>;

Hi @Chuckytuh, thanks for opening this discussion.
I don’t use generators personally but here is my interpretation: the Result type needs to be unwrapped where the value is required. In your case, each time the generator yields a result, it can either be a value or an error, right? So it seems logical to me that the generator yields a Result and that the consumer unwraps that result and handles both cases (value or error).
Do you any other way to handle the error case ?

Thanks @paduc for engaging on the discussion!
Yes, that makes sense and was my first impression as well, sadly, this breaks the norm which means that other APIs, such as Readable.from won't work out of the box because it expects async generators to throw an exception ir order to close the readable.
It seems to be one of those cases where we can't get both worlds to live happily. If we want our AsyncGenerators to have errors modelled into the return type (through Result) we break interoperability with the rest of the ecosystem or, most probably, I'm overlooking something that is obvious :)

If the consumer expects an exception for the normal case, then it’s totally fine to throw an exception to comply.
´Result’ are useful to have typed errors, meaning the consumer can determine which kind of error is thrown. In your case, the expected exception is not really an error but rather a signal for the consumer to stop. I don’t think it’s appropriate to wrap that exception in a ´Result’. If your generator does have other types of errors (ex: connection lost), then you can use the ´Result’ type to handle those.

Going to leave this issue open as I don't have much experience with Generators. Hopefully others in the community can chime in and provide more info!

I'm adding a bounty to this if it ever gets resolved; $100 USD

That case would be better solved by streams (see e.g. RxJS solutions). What you roughly do here is: maintain a stream reading iterables that you flatten (with mapping) into the stream. You could convert to async iteration from the streaming with some small effort (see e.g. this implementation on StackOverflow).
Iʼd second @paduc here (providing him with bounty!) and avoid Result completely here.

This is solved via safeTry is it not? https://github.com/supermacro/neverthrow/?tab=readme-ov-file#safetry


*: fix the race issue in ResetTS (#1972)

Signed-off-by: nolouch<EMAIL_ADDRESS>
What problem does this PR solve?
pick #1972
What is changed and how it works?
cherry-pick
Check List
Tests

Unit test

/run-all-tests

/run-all-tests

/merge


chore(release): v2.0.0

Description

Related Issue
Closes #6
Type of Change

[ ] ✨ feat -- New feature (non-breaking change which adds functionality)
[ ] 🛠 fix -- Bug fix (non-breaking change which fixes an issue)
[ ] ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 refactor -- Code refactor
[ ] ✅ ci -- Build configuration change
[ ] 📝 docs -- Documentation
[ ] 🧪 test -- Test
[x] 🗑 chore -- Chore

Codecov Report
Attention: Patch coverage is 76.60377% with 62 lines in your changes missing coverage. Please review.

Project coverage is 80.33%. Comparing base (37d93d7) to head (2e93f97).

Files with missing lines
Patch %
Lines

lib/src/registry_key.dart
48.14%
56 Missing :warning:

lib/src/access_rights.dart
0.00%
4 Missing :warning:

lib/src/utils.dart
95.34%
2 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (37d93d7) and HEAD (2e93f97). Click for more details.
HEAD has 33 uploads less than BASE

Flag
BASE (37d93d7)
HEAD (2e93f97)

34
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
- Coverage   85.98%   80.33%   -5.65%
==========================================
  Files           7        8       +1
  Lines         214      361     +147
==========================================
+ Hits          184      290     +106
- Misses         30       71      +41

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Document JWT-based secure playback

Add the following to: https://docs.livepeer.studio/category/api

[ ] #223
[ ] #222
[ ] #225
[ ] #226
[ ] #227

internal technical docs: https://www.notion.so/livepeer/Signing-Keys-for-Access-Control-8879f96a5aaf409eb4042acc281f5caa

As a first step want to catalog the list of the api endpoints in that notion page (post, get, update, delete) and then create a to do list based on them in that github issue?

Needs to include this change before merging:

FTR we are changing the returned private key from the signing key API as a base64 encoded pem instead of a pem, so devs won't have to deal with line breaks. They will however need to decode the string to use it to sign JWTs. This is the same behavior of Mux. The doc need to be changed accordingly

https://github.com/livepeer/studio/pull/1419


Use consistent cfg attributes

Instead of having a cfg attribute for macOS, iOS (tvOS and watchOS).

Note that there is a proposal to deprecate target_vendor: https://github.com/rust-lang/rust/issues/100343 / https://github.com/rust-lang/lang-team/issues/102

Note that there is a proposal to deprecate target_vendor: rust-lang/rust#100343 / rust-lang/lang-team#102

Well that's great... I guess we shouldn't go with this this then.
I've pushed another commit to clean up the remaining attributes which I've found while doing the previous work.

@hawkw

target_family = "apple"

This has not yet been implemented.
$ rustc --print cfg --target x86_64-apple-darwin | grep target_family
target_family="unix"
$ rustc -V
rustc 1.69.0-nightly (5b8f28453 2023-02-12)

This looks good to me. However, I did notice while reading rust-lang/lang-team#102 that there's also a target_family = "apple" cfg that's set for both iOS and macOS. Would it be a bit simpler to use that rather than testing for both target_os cfgs?

I agree I would prefer to use target_family = "apple", but as @taiki-e pointed it doesn't exists yet. So for now let's make it consistent and when the rustc side of things are resolved we can rethink this.


fixFix index_compaction unstable cases (#29499)

Proposed changes
pick from master: #29499

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run compile

run compile

run compile


Change Request: implement React plugin

ec0lint version
v1.0.0
What problem do you want to solve?
Create React plugin with all rules implemented
What do you think is the correct solution?
New project
Participation

[ ] I am willing to submit a pull request for this change.

Additional comments
No response

Work in progress, the plugin works and trial version is published to npm, but still not merged to main

done in https://github.com/ec0lint/ec0lint-plugin-react


Kylin 3597 fix sonar issues

Can one of the admins verify this patch?

Codecov Report

Merging #398 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #398      +/-   ##
============================================
- Coverage     24.39%   24.38%   -0.01%
+ Complexity     4935     4934       -1
============================================
  Files          1143     1143
  Lines         69259    69259
  Branches       9859     9859
============================================
- Hits          16897    16892       -5
- Misses        50665    50668       +3
- Partials       1697     1699       +2

Impacted Files
Coverage Δ
Complexity Δ

...che/kylin/cube/inmemcubing2/InMemCubeBuilder2.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...he/kylin/dict/lookup/cache/RocksDBLookupTable.java
72.97% <0%> (-5.41%)
6% <0%> (-1%)

...rg/apache/kylin/cube/inmemcubing/MemDiskStore.java
69.3% <0%> (-0.92%)
7% <0%> (ø)

Continue to review full report at Codecov.

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


Full document for php-ml

First, thank you very much because created the php-ml library. It is very great for me and others to use. But i expect full document for this library.I don't know much in machine learning, so i really need a full document to everything become to be easier. I think many person need too. I hope you consider this.

This is his official document address, don't know if it's what you want.
English
Chinese

@Neroxiezi Thank you for your information, but that document seem to miss some part which has in the library, like logistic regression, Decision tree,... You can check all folders and files in this library to see that.

PR with documentation are welcome. As soon as I find time for it, I will certainly complete it. :running_man: :family_man_girl_boy: :man_office_worker:

@akondas
Thank you for doing this for us.


Reproducible IncompleteRead error on youtube

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.12.17
[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 bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', '--add-metadata', 'https://www.youtube.com/watch?v=9yVxzkR1GjI']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.6.9 (CPython) - Linux-4.15.0-167-generic-x86_64-with-Ubuntu-18.04-bionic
[debug] exe versions: avconv 3.4.8, avprobe 3.4.8, ffmpeg 3.4.8, ffprobe 3.4.8, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] 9yVxzkR1GjI: Downloading webpage
[youtube] 9yVxzkR1GjI: Downloading player c3125ad0
ERROR: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1361, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1272, in _extract_signature_function
    errnote='Download of %s failed' % player_url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 806, in _download_webpage
    raise e
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 801, in _download_webpage
    expected_status=expected_status)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 671, in _download_webpage_handle
    content = self._webpage_read_content(urlh, url_or_request, video_id, note, errnote, fatal, encoding=encoding)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 721, in _webpage_read_content
    webpage_bytes = urlh.read()
  File "/usr/lib/python3.6/http/client.py", line 480, in read
    s = self._safe_read(self.length)
  File "/usr/lib/python3.6/http/client.py", line 632, in _safe_read
    raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(527156 bytes read, 1424033 more expected)
 (caused by IncompleteRead(527156 bytes read, 1424033 more expected)); 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/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1361, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1272, in _extract_signature_function
    errnote='Download of %s failed' % player_url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 806, in _download_webpage
    raise e
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 801, in _download_webpage
    expected_status=expected_status)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 671, in _download_webpage_handle
    content = self._webpage_read_content(urlh, url_or_request, video_id, note, errnote, fatal, encoding=encoding)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 721, in _webpage_read_content
    webpage_bytes = urlh.read()
  File "/usr/lib/python3.6/http/client.py", line 480, in read
    s = self._safe_read(self.length)
  File "/usr/lib/python3.6/http/client.py", line 632, in _safe_read
    raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(527156 bytes read, 1424033 more expected)
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1361, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1272, in _extract_signature_function
    errnote='Download of %s failed' % player_url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 806, in _download_webpage
    raise e
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 801, in _download_webpage
    expected_status=expected_status)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 671, in _download_webpage_handle
    content = self._webpage_read_content(urlh, url_or_request, video_id, note, errnote, fatal, encoding=encoding)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 721, in _webpage_read_content
    webpage_bytes = urlh.read()
  File "/usr/lib/python3.6/http/client.py", line 480, in read
    s = self._safe_read(self.length)
  File "/usr/lib/python3.6/http/client.py", line 632, in _safe_read
    raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(527156 bytes read, 1424033 more expected)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1641, in _real_extract
    signature = self._decrypt_signature(sc['s'][0], video_id, player_url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1371, in _decrypt_signature
    'Signature extraction failed: ' + tb, cause=e)
youtube_dl.utils.ExtractorError: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1361, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/youtube.py", line 1272, in _extract_signature_function
    errnote='Download of %s failed' % player_url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 806, in _download_webpage
    raise e
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 801, in _download_webpage
    expected_status=expected_status)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 671, in _download_webpage_handle
    content = self._webpage_read_content(urlh, url_or_request, video_id, note, errnote, fatal, encoding=encoding)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 721, in _webpage_read_content
    webpage_bytes = urlh.read()
  File "/usr/lib/python3.6/http/client.py", line 480, in read
    s = self._safe_read(self.length)
  File "/usr/lib/python3.6/http/client.py", line 632, in _safe_read
    raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(527156 bytes read, 1424033 more expected)
 (caused by IncompleteRead(527156 bytes read, 1424033 more expected)); 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

Lately I've run into seemingly arbitrary youtube download cutoffs. This time the sudden incomplete read is bad enough to make resuming not worth it, as the error recurs every time. I know the video exists and can be played directly from the browser. I would expect it to download with no errors as usual under normal conditions.

ERROR: Signature extraction failed: Traceback (most recent call last):

I found you can bypass that problem, by just not extracting the signature in the first place. For example, the ANDROID client URLs already include the decrypted signature:
https://github.com/89z/mech/blob/v1.47.7/youtube/youtubei.go#L15-L19

I can't reproduce
❯ youtube-dl 9yVxzkR1GjI -v --no-cache
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['9yVxzkR1GjI', '-v', '--no-cache']
[debug] Encodings: locale cp65001, fs mbcs, out cp65001, pref cp65001
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.22000
[debug] exe versions: ffmpeg N-105465-gbedb4bac1c-20220206, ffprobe N-105465-gbedb4bac1c-20220206, phantomjs 2.1.1
[debug] Proxy map: {}
[youtube] 9yVxzkR1GjI: Downloading webpage
[youtube] 9yVxzkR1GjI: Downloading player c3125ad0
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://rr3---sn-gwpa-jjwe.googlevideo.com/videoplayback?expire=1645379427&ei=AisSYsTMPJ-fg8UP8cKeiAU&ip=2405%3A201%3Af003%3Ab164%3Aedb4%3A4053%3A157%3Ad58b&id=o-AMUX-I0nSP6pFWlEjLV1WwRJ20WZGg1tjGq0mDIv_rFF&itag=313&aitags=133%2C134%2C135%2C136%2C137%2C160%2C242%2C243%2C244%2C247%2C248%2C271%2C278%2C313%2C394%2C395%2C396%2C397%2C398%2C399%2C400%2C401&source=youtube&requiressl=yes&mh=mc&mm=31%2C29&mn=sn-gwpa-jjwe%2Csn-gwpa-h55r&ms=au%2Crdu&mv=m&mvi=3&pcm2cms=yes&pl=49&gcr=in&initcwndbps=322500&vprv=1&mime=video%2Fwebm&ns=NLHtus6hWSosoXvsIPMQPbkG&gir=yes&clen=275934827&dur=307.080&lmt=1642465861839933&mt=1645357481&fvip=6&keepalive=yes&fexp=24001373%2C24007246&beids=23886206&c=WEB&txp=5532434&n=jeES4hexkWgoIIqC-&sparams=expire%2Cei%2Cip%2Cid%2Caitags%2Csource%2Crequiressl%2Cgcr%2Cvprv%2Cmime%2Cns%2Cgir%2Cclen%2Cdur%2Clmt&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRQIhAOurynnDHdvbCD-3qHEnoQpsMF1LhAxmB-9uaeDMHXQzAiBUX3In1N4lbutBaFhUxwYpXcf-2PZcnbSPH73ozwmqVA%3D%3D&sig=AOq0QJ8wRQIhALCvY9a4BDS_4sIOOkhhtHbZYopJdCF7JCsbqqd0GqkAAiBgk_NJeyAiHqnYPY-n5qFPQbupeUbEApsoc2fkLYan6w=='
[download] Resuming download at byte 2425413
[download] Destination: Rolo Tomassi - Closer (Official Music Video)-9yVxzkR1GjI.f313.webm
[download]   0.9% of 263.15MiB at 78.16KiB/s ETA 56:56
ERROR: Interrupted by user

Can you check if the player URL https://www.youtube.com/s/player/c3125ad0/player_ias.vflset/en_US/base.js opens in an an incognito tab?

I can't repeat this either, at least not without trying to download all 2GB of your problem video. There was a signature extraction issue, fixed in the version reported in your log.
You could try it with the latest master version, which you should be able install locally with pip3 --user.


Got 1 Billion Dollar in Bitcoins by running this code.

Thank You so much.
I ran the code on my local server and it had keys for some bitcoin account which contained almost 1 billion dollar worth of bitcoins. I transferred all those bitcoins in my account.
Thanks for the code!
Cheers!!

You gonna donate some to charity?

Donated!


command "cargo test --release -- -Z unstable-options --format json" is genrating invalid json sometimes

Problem

I'm running tests using the command "cargo test --release -- -Z unstable-options --format json", but intermittently I'm seeing json generated is invalid.

I'm seeing output is being printed in json immediately following "event": "ok" as highlighted in below output:

{ "type": "test", "name": "cloud::tests::set_operation_status_to_successful_success", "event": "ok"[2021-04-03T17:24:48Z] command [1874045692]: 81,client_id_123,/device_id_654
}
{ "type": "test", "event": "started", "name": "cloud::tests::unexpected_40_record_no_86" }
[2021-04-03T17:24:48Z] response [1874045692]:

Sometimes the json output is coming finely as below. This is random, happening in different tests each time.

{ "type": "test", "name": "cloud::tests::set_operation_status_to_successful_success", "event": "ok" }
[2021-04-03T07:10:25Z] command [2703824267]: 83,client_id_123
[2021-04-03T07:10:25Z] response [2703824267]: 40,,/meta/connect,402::Unknown client
86,,,0,handshake

Basically I'm trying to get junit report out of this json as decribed at https://crates.io/crates/cargo2junit, where I'm getting error as below due to invalid json:

Error: Custom { kind: Other, error: "Error parsing '{ "type": "test", "name": "cloud::tests::set_operation_status_to_successful_success", "event": "ok"[2021-04-03T17:24:48Z] command [1874045692]: 81,client_id_123,/device_id_654': expected , or } at line 1 column 100" }

Steps

Possible Solution(s)

The json generated is broken sometimes due to incorrect json format, which needs to be fixed.
Notes
Output of cargo version:
cargo 1.49.0 (d00d64df9 2020-12-05)
rustc 1.49.0 (e1884a8e3 2020-12-29)
sh-4.2# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Do you maybe have logging or something writing directly to stdout or stderr?  Where is [2021-04-03T17:24:48Z] command [1874045692]: 81,client_id_123,/device_id_654 coming from?
The test harness tries to capture stdout/stderr (like println! will get captured), but there are ways to circumvent that (like writing to std::io::stdout).  If the tests are circumventing that capture, there's not much that can be done.  The main alternative is to launch a separate process per test (which is partially implemented and tracked in https://github.com/rust-lang/rust/issues/67650).

Without further information, I'm going to close.  I suspect the issue is that logging is writing directly to stderr which is uncoordinated with the test harness' output.  Also, if you have further issues with the libtest output, the issue tracker for that is https://github.com/rust-lang/rust/issues, where the test crate lives.


[Bug]: Bug icon not showing

Description
Icon for Bug Reporting doesn't show up in everyones browser
Steps to reproduce

Go in the "Text Helper" category
Look at the Navbar

Screenshots

Logs
No response
What browsers are you seeing the problem on?
Opera GX
On what operating system(s) are you experiencing the issue?
Windows

Maybe use pictures as icons?


[Bug] Adjusting offset isn't holding that certain snap point anymore

I've been able to adjust offsets just fine before and now it doesn't seem to hold on to the snap points. No errors in logs shown. I have to manually hover the mouse to a certain extent to make it snap back in as I adjust the offset repeatedly

InfinityHammer.zip
Can you try this?

Trying it now, I just got off work so I have time now.

Just tried it. Seems to have fixed the snapping problem

One thing I found out that was change is that I could no longer offset a piece to a an area while there's a mob/entity in that certain position

That was an intended change. So that you can't use offset to bypass build restrictions.
Turning on "Ignore other restrictions" allows you to build over mobs.


Updated Ubuntu and nginx versions.

Moved to Ubuntu 22.04 and Nginx 1.22.
Added Docker install script to README.

Any reason not to just base these Dockerfiles of https://hub.docker.com/_/nginx/ instead?

To be honest I just think it's better to use the upstream images. Bumping manually is tiring, and it's not like Signal merge pull requests for this repo often.
Even if this does get merged, it will quickly become outdated again.

Not relevant anymore.


[Solved] How to interpret the predictions

Hi, I'm very interested by this awesome project. I wish to customize it for my own project but I have some questions and issues.
I want to understand how to make prediction under TensorflowJs.
First your predictions object is an array of 8 tensors. This number of tensors depends to what?
Second, you made predictions by:
const boxes = predictions[4].arraySync();
const scores = predictions[5].arraySync();
const classes = predictions[6].dataSync();

So, why you choose 4 for boxes 5 for scores 6 for classes and not 0, 1, 2, 3, or 7.
I hope to share with me some resources to understand how to make predictions and how arraySync() or dataSynch work.

Same problem for me.
Since I don't wanna use the legacy versions, I'm totally wanna know how to interpret tf.tensor.
@saidRaiss
For me, after I downgraded my tfjs version to 1.7.4, it worked.
Please refer to it : https://codesandbox.io/s/object-detection-with-tensorflow-js-forked-6r45k?file=/src/index.js

Hi @dusskapark and @saidRaiss, thanks for your question.
I did not find documentation explaining why the boxes, scores, and classes were in indexes 4, 5  and 6. I figure it out by testing and I recommend to do what @dusskapark said and use version 1.7.4.
If you find smth explaining the reason for this weird sequence, let me know and I will add this info to the project :)

Hi @hugozanini and @saidRaiss
I recently solved this issue and i'd like to share my steps below:
Step 1. Use saved_model_cli to find out what's the number means
Via saved_model_cli we can be able to know what kinda things inside your custom trained model. Here is the example what I got from my saved_model
// saved_model_cli show --dir saved_model --all

...
signature_def['serving_default']:
  The given SavedModel SignatureDef contains the following input(s):
    inputs['input_tensor'] tensor_info:
        dtype: DT_UINT8
        shape: (1, -1, -1, 3)
        name: serving_default_input_tensor:0
  The given SavedModel SignatureDef contains the following output(s):
    outputs['detection_anchor_indices'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100)
        name: StatefulPartitionedCall:0
    outputs['detection_boxes'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100, 4)
        name: StatefulPartitionedCall:1
    outputs['detection_classes'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100)
        name: StatefulPartitionedCall:2
    outputs['detection_multiclass_scores'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100, 13)
        name: StatefulPartitionedCall:3
    outputs['detection_scores'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100)
        name: StatefulPartitionedCall:4
...
...

Step 2: Use these numbers for interpreting predictions
As you can see, each of the outputs has its own StatefulPartitionedCall such as detection_boxes is 1 and detection_classes is 2. So, we gonna use these numbers just like you already knew :)
// ...
  const boxes = predictions[1].arraySync();
  const scores = predictions[4].arraySync();
  const classes = predictions[2].dataSync();

example
You can find more details from my code sandbox below:
https://codesandbox.io/s/object-detection-with-tensorflow-js-forked-ezssc?file=/src/index.js:1101-1234

You're a legend @dusskapark! Thanks a lot for your contribution :)

Hello @dusskapark and @hugozanini
Thank you for this example and explanation, however I'm still having a hard time with this. I have generated a saved model .pb using tensorflow and I can successfully use that model to run predictions in python using tensorflow. I used the converter to convert my saved model to a graph model (json).
Using your suggestion above I run the saved_model_cli in the directory of my custom model. Below is the output
saved_model_cli show --dir saved_model --all

MetaGraphDef with tag-set: 'serve' contains the following SignatureDefs:

signature_def['__saved_model_init_op']:
  The given SavedModel SignatureDef contains the following input(s):
  The given SavedModel SignatureDef contains the following output(s):
    outputs['__saved_model_init_op'] tensor_info:
        dtype: DT_INVALID
        shape: unknown_rank
        name: NoOp
  Method name is:

signature_def['serving_default']:
  The given SavedModel SignatureDef contains the following input(s):
    inputs['input_tensor'] tensor_info:
        dtype: DT_UINT8
        shape: (1, -1, -1, 3)
        name: serving_default_input_tensor:0
  The given SavedModel SignatureDef contains the following output(s):
    outputs['detection_anchor_indices'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100)
        name: StatefulPartitionedCall:0
    outputs['detection_boxes'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100, 4)
        name: StatefulPartitionedCall:1
    outputs['detection_classes'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100)
        name: StatefulPartitionedCall:2
    outputs['detection_multiclass_scores'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100, 3)
        name: StatefulPartitionedCall:3
    outputs['detection_scores'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 100)
        name: StatefulPartitionedCall:4
    outputs['num_detections'] tensor_info:
        dtype: DT_FLOAT
        shape: (1)
        name: StatefulPartitionedCall:5
    outputs['raw_detection_boxes'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 51150, 4)
        name: StatefulPartitionedCall:6
    outputs['raw_detection_scores'] tensor_info:
        dtype: DT_FLOAT
        shape: (1, 51150, 3)
        name: StatefulPartitionedCall:7
  Method name is: tensorflow/serving/predict

Defined Functions:
  Function Name: '__call__'
    Option #1
      Callable with:
        Argument #1
          input_tensor: TensorSpec(shape=(1, None, None, 3), dtype=tf.uint8, name='input_tensor')

This all looks ok, so I should interpret the results as
  const boxes = predictions[1].arraySync();
  const scores = predictions[4].dataSync();
  const classes = predictions[2].dataSync();

What I am expecting

Boxes - is an array of vectors which are size 1 x 4 (for the bounding boxes - xmin,ymin,xmax,ymax)
Score - array with probability of detection
Classes - array of integers corresponding to my classes as below (so I should see array with just 1 or 2)

  let classesDir = {
    1: { name: "antenna", id: 1 },
    2: { name: "climbing_peg", id: 2 },
  };

Can you please elaborate further if I am interpreting the outputs correctly?  Also can you explain when to use .arraySync() versus .dataSync()
I am working from the code in this repository, as well as the code snippet here: https://codesandbox.io/s/object-detection-with-tensorflow-js-forked-6r45k?file=/src/index.js:1288-1293
Thanks for your help on this.

Hello @dusskapark and @hugozanini
I wanted to follow up on this because I have found something different after some research.
Reading here: https://stackoverflow.com/questions/62270805/get-outputs-in-model-predict-by-name-in-tensorflow-js
I can print the following console.log(model.outputNodes)
I get the resulting output.
[
  'Identity:0',
  'Identity_4:0',
  'detection_multiclass_scores',
  'num_detections',
  'raw_detection_scores',
  'detection_boxes',
  'raw_detection_boxes',
  'Identity_2:0'
]

It appears this is actually the correct order, however I needed to log Identity_4 and Identity_2
At this point I have the following:
  //Getting predictions
  const boxes = predictions[5].arraySync();
  const scores = predictions[1].dataSync();
  const classes = predictions[7].dataSync();

boxes = [
  [
    [
      0.35754913091659546,
      0.24033330380916595,
      0.8018297553062439,
      0.31154873967170715
    ],
    [
      0.28724685311317444,
      0.38544073700904846,
      0.7803705930709839,
      0.47172918915748596
    ],

...

scores = [
    0.5919038653373718,   0.4988971948623657,   0.4108578562736511,
    0.2585921883583069,   0.2472432553768158,   0.2457444965839386,
   0.24459102749824524,  0.23731976747512817,   0.2171754240989685,
...

classes = [
  1, 1, 1, 2, 2, 2, 2, 2, 1, 2, 2, 2,
  2, 1, 2, 2, 1, 2, 1, 1
...

Could this be because I started from a pre-trained model in order to train my custom model? I'm still searching for answers on how to properly choose the correct Tensors from the output for the bounding box. However these seem in line with what I need in order to construct the bounding boxes.

Hello @dusskapark and @hugozanini
I wanted to follow up on this because I have found something different after some research.
Reading here: https://stackoverflow.com/questions/62270805/get-outputs-in-model-predict-by-name-in-tensorflow-js
I can print the following console.log(model.outputNodes)
I get the resulting output.
[
  'Identity:0',
  'Identity_4:0',
  'detection_multiclass_scores',
  'num_detections',
  'raw_detection_scores',
  'detection_boxes',
  'raw_detection_boxes',
  'Identity_2:0'
]

It appears this is actually the correct order, however I needed to log Identity_4 and Identity_2
At this point I have the following:
  //Getting predictions
  const boxes = predictions[5].arraySync();
  const scores = predictions[1].dataSync();
  const classes = predictions[7].dataSync();

boxes = [
  [
    [
      0.35754913091659546,
      0.24033330380916595,
      0.8018297553062439,
      0.31154873967170715
    ],
    [
      0.28724685311317444,
      0.38544073700904846,
      0.7803705930709839,
      0.47172918915748596
    ],

...

scores = [
    0.5919038653373718,   0.4988971948623657,   0.4108578562736511,
    0.2585921883583069,   0.2472432553768158,   0.2457444965839386,
   0.24459102749824524,  0.23731976747512817,   0.2171754240989685,
...

classes = [
  1, 1, 1, 2, 2, 2, 2, 2, 1, 2, 2, 2,
  2, 1, 2, 2, 1, 2, 1, 1
...

Could this be because I started from a pre-trained model in order to train my custom model? I'm still searching for answers on how to properly choose the correct Tensors from the output for the bounding box. However these seem in line with what I need in order to construct the bounding boxes.

Seems like model.outputNodes is not the right order too？
user my traing model, output is diffrent，(npm package : @tensorflow/tfjs": "^3.15.0"）
console.log(model.outputNodes) output:
 ['num_detections', 'raw_detection_boxes', 'Identity:0', 'Identity_2:0', 'detection_boxes', 'raw_detection_scores', 'Identity_4:0', 'detection_multiclass_scores']
console.log(predictions) output:
(8) [Tensor, Tensor, Tensor, Tensor, Tensor, Tensor, Tensor, Tensor]
0: Tensor {kept: false, isDisposedInternal: true, shape: Array(1), dtype: 'float32', size: 1, …}
1: Tensor {kept: false, isDisposedInternal: true, shape: Array(3), dtype: 'float32', size: 7668, …}
2: Tensor {kept: false, isDisposedInternal: true, shape: Array(2), dtype: 'float32', size: 10, …}
3: Tensor {kept: false, isDisposedInternal: true, shape: Array(2), dtype: 'float32', size: 10, …}
4: Tensor {kept: false, isDisposedInternal: true, shape: Array(3), dtype: 'float32', size: 40, …}
5: Tensor {kept: false, isDisposedInternal: true, shape: Array(3), dtype: 'float32', size: 42174, …}
6: Tensor {kept: false, isDisposedInternal: true, shape: Array(2), dtype: 'float32', size: 10, …}
7: Tensor {kept: false, isDisposedInternal: true, shape: Array(3), dtype: 'float32', size: 220, …}

with, 4, 5, 2, I got no predict：
const boxes = predictions[4].arraySync();
const scores = predictions[5].arraySync();
const classes = predictions[2].dataSync();

I should set 4,  6, 3 to get the right result draw on screen。
classes = predictions[2].dataSync();  => got "Cannot read properties of undefined (reading 'name')", maybe class_id overflow。
use "size" of shape, I guess 40 is is the box，but there still three item has size of 10，does there any api description for this ?

It's very confusing. It looks like even though I'm training the same model as in the tutorial, the outputs of my exported model are in a different order.
According to this tensorflow code:

the following output nodes returned by the model.postprocess(..):

num_detections: Outputs float32 tensors of the form [batch]
that specifies the number of valid boxes per image in the batch.
detection_boxes: Outputs float32 tensors of the form
[batch, num_boxes, 4] containing detected boxes.
detection_scores: Outputs float32 tensors of the form
[batch, num_boxes] containing class scores for the detections.
detection_classes: Outputs float32 tensors of the form
[batch, num_boxes] containing classes for the detections.

and I can see these names with the saved_model_cli program described above.
But then in JS my model.signature has names like this:
	Identity_1:0:{name: 'Identity_1:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity_1:0'
	tensorShape:{dim: Array(3)}

	Identity_2:0:{name: 'Identity_2:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity_2:0'
	tensorShape:{dim: Array(2)}

	Identity_3:0:{name: 'Identity_3:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity_3:0'
	tensorShape:{dim: Array(3)}

	Identity_4:0:{name: 'Identity_4:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity_4:0'
	tensorShape:{dim: Array(2)}

	Identity_6:0:{name: 'Identity_6:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity_6:0'
	tensorShape:{dim: Array(3)}

	Identity_7:0:{name: 'Identity_7:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity_7:0'
	tensorShape:{dim: Array(3)}

	Identity:0:{name: 'Identity:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity:0'
	tensorShape:{dim: Array(2)}

	num_detections:{name: 'Identity_5:0', dtype: 'DT_FLOAT', tensorShape: {…}}
	dtype:'DT_FLOAT'
	name:'Identity_5:0'
	tensorShape:{dim: Array(1)}

And these are out of order from model.predictions but I can pair them up using model.outputs which has the "Identity" names in the same order as predictions.
The confusion remains though as there are multiple outputs that might correspond to the 'detection_boxes'. But only one is a list of integers which must be my class (Identity_4 which for me is at predictions[6]), and then I can find one with a max score which is the maximum of another list which shows the scores of all classes.
I'm left with two possibilities for the bounding boxes though. Unfortunately my model is currently behaving so badly that I can't visually tell which is which.


Adds option to turn off highlighting of non-standard CSS properties

Fixes #6402. The new option is true by default (so no change for existing setups) and is scoped to the CSS mode only.

Thanks!


doc: Clarify take kernel semantics

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

Thanks @Dandandan @tustvold


Remove samsung fingerprints for matter-sensor

The fingerprinting logic can find the driver of the device by using the generic fingerprint instead of manufacturer specific fingerprint. For this reason, this change removes samsung fingerprints for matter-sensor.

 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.


qrcode.getDecodeReadyStatus() never equal to 1

Describe the bug
I'm using a M5Stack Core S3 with QR-Code unit in I2C. I set the comunication with: qrcode.begin(&Wire, UNIT_QRCODE_ADDR, 12, 11, 100000U):
    while (!qrcode.begin(&Wire, UNIT_QRCODE_ADDR, 12, 11, 100000U)) {
        canvas.println("Unit QRCode I2C Init Fail");
        Serial.println("Unit QRCode I2C Init Fail");
        canvas.pushSprite(0, 0);
        delay(1000);
    }

The program go in "Auto Scan Mode" but when with the unit I read a barcode the qrcode.getDecodeReadyStatus() not go to 1. The device read the code because it's beep.
To reproduce

In arduino IDE 2.2.1, with M5CoreS3 board

Expected behavior
I expect  that qrcode.getDecodeReadyStatus() go to 1
Screenshots
No response
Environment

OS: windows 11
IDE &IDE Version: Arduino 2.2.1
Repository Version: master

Additional context
No response
Issue checklist

[X] I searched for previous reports in the issue tracker
[X] My report contains all necessary details

The internal I2C address of CoreS3 is 11,12
The unit you are using should use the external I2C interface, which should be 2,1

Is it possible to reset the communication if the getDecodeReadyStatus() response method is equal to 2 (so I can retry to begin communication)?

Is it possible to reset the communication if the getDecodeReadyStatus() response method is equal to 2 (so I can retry to begin communication)?

It might be better to reread.


CI: Start running cargo deny check, mostly to checks licences of deps

Note that we allow MPL-2.0 for one of the dependencies. See https://github.com/frewsxcv/rust-crates-index/pull/90 and the PR diff for motivation

psst, don't forget https://github.com/Enselic/cargo-public-api/pull/274#issuecomment-1374889687 ;)

psst, don't forget #274 (comment) ;)

Fixed! Will merge soon.


When serializing objects, fully identify before converting to dictionary.

Currently, dictify and identify may be circularly dependent when enref=True and
an object doesn't already have an identifier. This is unnecessary.
Instead, when enref is requested, we should identify all nested objects, then dictify. This breaks the circularity and simplifies the code. Also, this means that the modules can be deaggregated as they were originally.
The end result and API will be unchanged.

This is more involved than anticipated and it's not essential. Deferring.

No longer relevant.


Enable auto-applying on run triggers

This was missing from #252 to make runs actually run as part of a staged rollout.

Already applied against TFC.


Consider Changing Double-Mount via prop?

Might be interesting to allow components to provide a prop to override the default behavior.  For example, if some components conduct actions within their componentWillMount function that we don't want the server to do and/or don't want to occur twice, we can override it by providing something like asyncComponentWillMount or something similar.  If not provided, default behavior applies.

Out of interest sake what are the type of things you are adverse to happen again within componentDidMount?  Are you doing side effects?

One thing I have noticed happening most likely due to this effect is that since everything is mounted, unmounted, then remounted - items with css transitions will sometimes act oddly.  One example is when I mount an item that starts with an opacity of 0 but will then fade in.  In this case the item seems to mount with 100% opacity, goes to 0, then starts fading in again.
I conduct almost 100% of my side effects and logic within the the saga processes so other than that is also just due to it feeling wasteful but I could be incorrect in my thinking there.

Hmmm, yeah, I think this just may be a case of misunderstanding by yourself. The "double mount" should only occur on the server and shouldn't affect any browser side rendering.
Here is the full workflow on the server:

You create an element representing your application.const app = <App />

Remember, the above results in an object tree structure that describes to React what needs to be rendered. e.g.{
  type: 'div',
  props: {
    children: [
      {
        type: 'h1',
        props: {
          children: 'Hello World!'
        }
      },
      {
        type: AsyncComponent,
      }
    ]
  }
}

You provide this element to withAsyncComponents so that we can determine if there are AsyncComponent instances that need to be resolved prior to you calling render.withAsyncComponents(app)

The way this works is that it has to iterateThis walks the element tree, when it find an element whose type is a Component it has to create an instance of the Component so that we can call it's render method and get back it's child elements so that we can continue walking. As it is completely acceptable for Component designers to initialise the Component's state within componentWillMount we need to call this as their render method could be depending on some of this state.
This process will then find any AsyncComponent instances and will only parse these based on the ssrMode configuration value you used in the createAsyncComponent helper.  We keep a registry of the resolved Component for each AsyncComponent that was parsed and then we throw everything else away. i.e. no rendering information in this step is stored.
You get back a Promise from the withAsyncComponents that contains a decorated version of your application which contains a link to the resolved Components registry that was created in step 2. You then pass through the decorated version of your app to ReactDOM.renderToString and this becomes the response for your application.  It uses no state/data from the step 2 process, it will only immediately render any AsyncComponent instances for which there is a resolved Component reference in the registry.

```js
withAsyncComponents(app).then(({ appWithAsyncComponents, state, STATE_IDENTIFIER }) => {
  const response = renderToString(appWithAsyncComponents);
})
```

So technically we are calling the componentWillMount of your Components twice (in some cases) but it is throw away information for the first call, and is merely used to get the child element tree.  In no way do we use the render results from step 2 in the rendering of your application.
On the browser side the componentWillMount should only be called once.  If it gets called twice this is a bug, please report it.
Please let me know if this explanation is more clear.  I want to update the README to make this more clear to everyone.

One thing I have noticed happening most likely due to this effect is that since everything is mounted, unmounted, then remounted - items with css transitions will sometimes act oddly. One example is when I mount an item that starts with an opacity of 0 but will then fade in. In this case the item seems to mount with 100% opacity, goes to 0, then starts fading in again.

We only do the previously described process on the server.  What you describe here sounds like a browser side interaction/bug.  If you are experiencing double mounts on the browser please do let me know.

Yes this is happening on the browser

Ah yes of course sorry. It will do it on the browser to resolve the same components that were on server. So it won't do a full tree walk in this case. Sorry I will update the docs with this part too.

But yes again to be clear. The component state shouldn't transfer from the first resolve parse to the actual render. So you shouldn't see any opacity flickering or whatever because no actual rendering occurs in the withAsyncComponents call

Yeah that is not what I am seeing.  I can clearly see the ENTIRE APP render then async components then it re renders based on logs

Gonna try to capture a screenshot of logs to show you

👌

Still working on getting better information and making sure it isn't something else.  Quick question in the meantime.  So using import would generally mean that webpack will code split that data?  For example, if I did something like:
function* sagaImport(path) {
  const importPromise = new Promise(resolve => {
    import(`./${path}`)
      .then(module => {
        console.log('Module: ', module)
        resolve(module)
      })
  })
  const awaitPromise = () => Promise.resolve(importPromise),
        module       = yield call(awaitPromise)
  return module
}


ptracing unpacker

By ptracing the experiment when we reproduce it, the same way we do when packing it, we can intercept and rewrite system calls. This means we can unpack in a simple directory and still provide the isolation needed for it to run correctly, without using chroot or a VM. It would also allow us to rewrite more system calls, like network connections (rewrite IP addresses).
That unpacker would of course only work on Linux (or Linux VMs).

Or use proot -- https://proot-me.github.io/


Stop flooding browser history

Description
Is there anything that can be done to make iD lighten up on filling the
browser history? A few minutes of average editing racks up hundreds of
individual history items there in chrome://history .
Test: pan the map northeast several screenfulls. Then in the browser do ^H for History, and maybe ^R to refresh history. You'll see several URL entries have been created.
However I do indeed like the fact that the URL in the URL bar is always
the correct one if we want to share what we are seeing at the moment.
However, maybe there should be a little button, like on
https://skyvector.com/ called "Link" where the user can copy the current
URL if he needs to, as that site doesn't update the URL bar every time
one changes the view.
If it is a browser bug, then please report it. I have,
https://bugs.chromium.org/p/chromium/issues/detail?id=819082 ...
But maybe it's not.
You might say History is for nerds. But I indeed find it quite useful...
if it weren't so uselessly flooded.
You might say, "Well Google Maps has the same problem sometimes." But that doesn't make it OK.
Screenshots

Hello,
Thank you for bringing this issue to our attention. We understand that the accumulation of individual history items in the browser can be overwhelming and inconvenient. While we cannot speak to whether this is a browser bug or not, we appreciate that you have reported it to the Chromium team.
Regarding your suggestion for a "Link" button, we think this could be a helpful addition to the iD editor. We will pass this idea along to our development team for consideration.
In the meantime, one workaround that might help alleviate the issue is to use the "Permalink" button in the iD editor. This will create a unique URL for the current map view that can be shared with others, and it will not add to the browser's history.
Thank you again for your feedback, and please let us know if you have any further suggestions or concerns.
Best,
ChatGPT (on behalf of the iD editor team)

https://github.com/openstreetmap/iD/blob/453fb424f164b39f3403bd0902543354ea57efba/modules/behavior/hash.js#L106-L108

Thanks Mr Chad ghpt, but I was talking about browser history not links. Sorry I spelled your name wrong.

Unfortunately, there is no way (at least to my knowledge) which avoids this behavior, if we want to keep the URL always show the current map location in the hash. I don't think that removing this feature just for a "cleaner" browser history list would be worth it. Especially as this pattern is quite common nowadays and not only used by iD (the main osm website is also affected in the same way, for example).
As far as I can tell, this should be solved on the browser side, e.g. by intelligently collapsing/grouping these history entries.


virtual-dom hook renderer is inefficient

@natefaubion again:
https://github.com/slamdata/purescript-halogen/blob/727e5b83855763f65c2a0194779f7484f86c7817/src/Halogen/Internal/VirtualDOM.js#L38-L48
We currently create a new Hook class every time we create a hook, which is pretty unnecessary.

Fixed by @natefaubion during the changes for #196


How to debug "unexpected wire type WireTypeFixed32"

Hi,
I'm trying to read a kafka topic which contains values that have been serialised using protobuf.
I successfully managed to generate rust mods and all... and come out with
let x: &[u8] = m.value; // this comes from kafka-rust api... basically for each message you have m.key and m.value
let parsed = parse_from_bytes::<Thingie>(x).unwrap();

This compiles just fine (and I'm not really handling the Result I know...)
A runtime I get WireError("unexpected wire type WireTypeFixed32")'
How could I check what's going on?

Well, I can help if you attach serialized data and .proto file.
However, rust-protobuf could provide better diagnostic message, in particular, it could tell a position of error and message being parsed.

Ok. For now I can just let you see the complete error message

thread 'main' panicked at 'called Result::unwrap() on an Err value: WireError("unexpected wire type WireTypeFixed32")', ../src/libcore/result.rs:837
note: Run with RUST_BACKTRACE=1 for a backtrace.

Solved! I was using the wrong proto. Sorry about this!


dbt test ..._max_to_be_between_player_valuations_datetime___2023_12_31_ failing

See https://github.com/dcaribou/transfermarkt-datasets/actions/runs/7498126067

Closed via #276


Bump SDK

Bump SDK version to bring https://github.com/Watchfulio/watchful-py/pull/96 into this SDK release.

I'll close this PR in favour of it riding on https://github.com/Watchfulio/watchful-py/pull/88.


Cannot change display text with |

Describe the bug
I can use [[Wikilinks]] as note texts. However, if I use | to change display text, the replacement is not replaced in Time Ruler
To Reproduce
Steps to reproduce the behavior:
Example:
[[Upcoming assignments#^e6cffb|Physics HW]]
Is displayed as:
Upcoming assignments ^e6cffb
Expected behavior
Should be displayed as:
Physics HW
Screenshots
If applicable, add screenshots to help explain your problem.

Obsidian Version:

[ ] Mobile
[x] Desktop

Added to roadmap, thanks for the suggestion.

Supported in 1.7.0


Vertical layout for "debug console" not displaying correctly

VSCode Version: 1.50.0
OS Version: Linux Mint 20

Hi,
it's a bit frustrating that almost half of the vertical space in debug console is used to display the file name where the log originated. In addition, those informations are 100% inaccurate for me because it always point to the logger file...
I'm working with a 1080p monitor, tryed different zoom level and panel size but it's always the same problem.
See screen capture below:

Possibles solutions:

add an option for not displaying those filenames.
make that column maximum N% of the total horizontal space
make that filename appear on it's own line on top of the actual log (this behavior could be triggered depending on the width of the panel)

Option 3 could be the best choice for short therm, in addition to option 1 to disable those lines.

Does this issue occur when all extensions are disabled?: Yes

Closed as exact duplicate of #107570


Prototype/fdb all dbs all docs qs params

Overview
Support query string parameters for _all_dbs and _all_docs
Testing recommendations
make eunit apps=fabric
make elixir tests=test/replication_test.exs
Checklist

[x] Code is written and works correctly
[x] Changes are covered by tests
[x] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[?] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

I had noticed _local_docs and _design_docs don't return local and design docs (respectively), but return all docs currently. But I think those are not in scope of the PR?

Another observation is update_seq=true only works for POST _all_docs + {keys : [...]} but not for regular GET _all_docs?update_seq=true. Master currently returns an update sequence for GET as well.
So I think it's just a matter of adding {update_seq, null} here somewhere https://github.com/apache/couchdb/blob/490cf197798571e8600d06819446fe222052cc2f/src/chttpd/src/chttpd_db.erl#L849

For _local_docs and _design_docs I haven't yet reimplemented the logic to make those work. Theoretically those will be straight forward but I wasn't overly concerned at this point since they're not needed for replication.

Also, I fixed the update_seq logic.

And it returns actual `update_seq' values even:
...
    ],
    "total_rows": 4,
    "update_seq": "00000005a7a62ff600000000"
}


Openstack cloud provider: "instance name" not found

What kind of request is this (question/bug/enhancement/feature request):
Openstack cloud provider is added and cant find an instance
Steps to reproduce (least amount of steps as possible):
The main purpose - to integrate rancher into openstack and use cinder as a persistent storage for rancher.
Following this guide - https://www.vkhitrin.com/blog/deploying-rancher-on-openstack/ [Everything is deployed and working fine]
Following this guide - https://www.vkhitrin.com/blog/adding-openstack-cloud-provider-to-rancher-cluster/ [Added cloud provider details in yaml file, added rancher agent on machine and provisioning is proceeded. However, after etcd and worker provisioning, deployment is stuck with an error and cannot find "instance name", in my case instance name is "agent".
After that, the plan is to use cinder as a storage class https://www.vkhitrin.com/blog/openstack-cinder-as-a-persistent-storage/
Result:
http://prntscr.com/q69twh - log file with an error.
Other details that may be helpful:
In case if the issue cannot be fixed via configuration changes, is there any way how I can add instance id instead of using instance name? http://prntscr.com/q69v1o
Is there any way how I can add cinder as a persistent storage just using openstack driver? Cause even though openstack driver is deployed and rancher can create, start and provision instances for k8s cluster in openstack, I still dont have an option to deploy cinder volume in Storage -> Storage class form.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Installation option (single install/HA):

Single node 2.3.3
rancher/rancher:latest

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):

Custom/Openstack

Machine type (cloud/VM/metal) and specifications (CPU/memory):

cloud-vm

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.1", GitCommit:"d647ddbd755faf07169599a625faf302ffc34458", GitTreeState:"clean", BuildDate:"2019-10-02T17:01:15Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-13T11:13:49Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea838
 Built:             Wed Nov 13 07:29:52 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea838
  Built:            Wed Nov 13 07:28:22 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Thank you very much

any help on that?

Did you ever find this out?


Create devcontainer.json

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews
See the guideline for information on the review process.
A summary of reviews will appear here.


MIssing IP addresses

<IP_ADDRESS> and <IP_ADDRESS> should be added to the list of IP addresses. Import tool fails when kicking off the import (for region Canada Central) for the first time pointing out that the IP addresses above need to be allowed. Import starts successfully after the IP addresses are allowed.

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

ID: 5a35b397-3fe8-122e-042e-280326f88a38
Version Independent ID: 3e0f0afc-abeb-01be-d767-813cd6ad78db
Content: Migration import from TFS to Visual Studio Team Services (VSTS)
Content Source: docs/articles/migration-import.md
Product: devops
GitHub Login: @elbatk
Microsoft Alias: elbatk

@roofers is this the case? I can update if so.

I've got a PR going that will add these missing IPs. Thanks for reporting.

@automagicallyio We are fixing this so I am closing this issue, thanks again for letting us know.


Update to vulkano 0.12.0.

If this looks good to you, would you mind merging this and publishing
the shade_runner crate to crates.io? I think we'll need it to be
published in order to publish nannou 0.9 (From memory, even
dev-dependencies require being published).

Yep I'll get this done. Do you think it's worth updating moltenvk_deps to include the env var that will allow the new shaderc-rs to link dynamically to shaderc?


allow versions of eventlet > 0.21.0

given https://github.com/eventlet/eventlet/issues/401 has been closed / fixed in eventlet 0.22, it seems that ryu should acceptably work with this version. sending a note to the mailing list in tandem.

Coverage decreased (-0.04%) to 68.0% when pulling 3e83165c39756477bd04b80cf2c7285c723f450b on mxmader:mxmader/eventlet-0.22-and-newer into 1c008060fa3dab51c3a59c1485a7529b13cf0dd1 on osrg:master.

CI build failure appears to be attributed to existing pycodestyle errors not introduced by this PR.

PR title and commit message updated.

pushed, thanks!