Bot crashes when 'stop' command executed

When executing the 'stop' command and the bot is in a voice channel, the bot will crash

Traceback (most recent call last):
File "C:/Users/Justin/PycharmProjects/goldmine/goldmine.py", line 40, in
retval = core.main(use_uvloop)
File "C:\Users\Justin\PycharmProjects\goldmine\core.py", line 76, in main
runbot(loop, bot)
File "C:\Users\Justin\PycharmProjects\goldmine\core.py", line 41, in runbot
loop.run_until_complete(bot.start(bot_token))
File "C:\Users\Justin\AppData\Local\Programs\Python\Python35\lib\asyncio\base_events.py", line 325, in run_until_complete
self.run_forever()
File "C:\Users\Justin\AppData\Local\Programs\Python\Python35\lib\asyncio\base_events.py", line 295, in run_forever
self._run_once()
File "C:\Users\Justin\AppData\Local\Programs\Python\Python35\lib\asyncio\base_events.py", line 1218, in _run_once
event_list = self._selector.select(timeout)
File "C:\Users\Justin\AppData\Local\Programs\Python\Python35\lib\selectors.py", line 314, in select
r, w, _ = self._select(self._readers, self._writers, [], timeout)
File "C:\Users\Justin\AppData\Local\Programs\Python\Python35\lib\selectors.py", line 305, in _select
r, w, x = select.select(r, w, w, timeout)
OSError: [WinError 10038] An operation was attempted on something that is not a socket

Process finished with exit code 1
Running Win 10 64bit - I've drilled down and found the bug to be this function:
C:/Users/Justin/AppData/Local/Programs/Python/Python35/Lib/site-packages/discord/voice_client.py
   @asyncio.coroutine
    def disconnect(self):
        """|coro|

        Disconnects all connections to the voice client.

        In order to reconnect, you must create another voice client
        using :meth:`Client.join_voice_channel`.
        """
        if not self._connected.is_set():
            return

        self._connected.clear()
        try:
            yield from self.ws.close()
            yield from self.main_ws.voice_state(self.guild_id, None, self_mute=True)
        finally:
            self.socket.close()

self.socket.close() seems to be causing the issue. Not sure if there is much you can do as it's in the discord package

Can you check if C:/Users/Justin/AppData/Local/Programs/Python/Python35/Lib/site-packages/discord/voice_client.py has a definition of class VoiceClientProtocol(asyncio.Protocol) right above class VoiceClient?

Yes, it's there
class VoiceClientProtocol(asyncio.Protocol):
    def __init__(self, secret_key, callback):
        self.callback = callback
        self.box = nacl.secret.SecretBox(bytes(secret_key))
        super().__init__()

    def datagram_received(self, data, addr):
        """
        Decrypt the data before passing it to the callback
        """
        nonce = bytearray(24)
        nonce[:12] = data[:12]
        sequence, timestamp, ssrc = struct.unpack_from('>2xHII', data)
        self.callback(self.box.decrypt(data[12:], nonce=bytes(nonce)), ssrc, sequence, timestamp)

class VoiceClient:

Just reinstall discord.py and it should work fine.


GUI: v0.1.7-rc1 about version is incorrect

Clicking on the "About Bison Relay" icon in rc1 of v0.1.7 shows 1.0.0 instead of the correct version.

  It looks like the screen is a bit "thinner" than normal size.  Does it look normal when you expand the window to the right?

Even in full screen the issue persists.

Hrm ok

This version part of this is resolved with the final 0.1.7 bins.


New API for communication call settings [Private preview]

Data Plane API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

Introducing new provisioning API for ACS calling, that will allow customers to store call related settings on ACS resource level and ACS participant level.
TypeSpec link
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[x] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc: N/A
Updated paths: N/A

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Schedule a data plane REST API spec review

Getting help

First, please carefully read through this PR description, from top to bottom.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

fix https://github.com/Azure/azure-rest-api-specs/issues/30399

From our prior conversations, this is only for private preview.
If we're going with the new Swagger route, then we should include the TypeSpec sources.


Cannot find RCTView in scope

Today I upgraded my app from v1 to v2 and after that, the build started failing as you see below, the error seems related to react-native-ios-utilities. Also, If it helps, my app is a bare react native app with expo modules. I'm using Expo SDK 50 with RN 73.

Versions
"react-native": "0.73.2",
"expo": "50",
"react-native-ios-context-menu": "2.3.0",
"react-native-ios-utilities": "4.2.3",

Hey @focux, can you show me how you fixed this? I only have two targets, project and projectTest, and having this in both isn't solving this.

Is your RN app a bare + expo modules app?


Catch errors thrown by custom snapshot serializers

Summary
In this commit, we are changing the function toMatchSnapshot to catch errors thrown by custom snapshot serializers.
When these errors are caught, toMatchSnapshot is going to throw the stack of the respective error, uncovering errors that might occur in custom snapshot serializers.
Fixes #3302
Test plan
Given a test file foo.test.js:
test("should match the snapshot", () => {
  const bar = {
    foo: {
      x: 1,
      y: 2
    }
  };

  expect(bar).toMatchSnapshot();
});

And a custom snapshot serializer my-serializer-module.js
module.exports = {
  test: val => {
    throw new Error("Where is this error?");
  },
  print: val => ""
};

And a package.json:
{
  "jest": {
    "snapshotSerializers": ["./my-serializer-module"]
  }
}

When jest is run, with the current implementation, the failure message has no trace of the error thrown by the custom serializer:

With the new implementation we have a failure message that includes a trace from the error thrown by the custom serializer:

@nicolasiensen Thank you for submitting this pull request!
Extending comment by @Nargonath let’s see if we can adjust PR to catch errors thrown by either:

test method of plugin
print or serialize method of plugin

for either:

snapshot test
display Expected/Received values after assertion fails, for example toEqual or toMatchObject

Could you see what happens if instead you catch errors in two places in pretty-format package:

for top-level value: https://github.com/facebook/jest/blob/master/packages/pretty-format/src/index.js#L431-L434
for descendant value, for example, array item or object property value: https://github.com/facebook/jest/blob/master/packages/pretty-format/src/index.js#L287-L290

As a reminder, please update the changelog as well

@nicolasiensen You have my apology if the suggestion thinking from-the-inside-out undid your solution from-the-outside-in as a developer actually experiences it in Jest.
Because catching and re-throwing errors is an area for me to learn, I ran a few tests using code from master and then compared to a clone from your branch. I was not able to repeat the improvement that I see in the picture that you took of your original commit.
Can you repeat your original test to confirm whether or not it still gives result you saw before?
If the improvement has been lost, then let’s return to what worked.

@pedrottimark you don't have to apologize :)
I confirm that the later changes are working, here is a gif where you can compare this branch with the master:

Have you built jest with yarn run build before trying this branch?

I'm a bit confused about why doing new Error(oldError.stack) helps. Is it us stripping out the useful part of the stacktrace as part of prettifying the error? Are you able to discover what part of the code makes us lose the stack? Or if I'm missing something, please enlighten me! 🙂

@SimenB The part that makes us lose the information is this one: https://github.com/facebook/jest/blob/0748e6f76394b58ce24aee42e08c96fb509e8744/packages/expect/src/index.js#L203
As of my understanding, captureStackTrace is used to removed Jest inners as part of the stack traces so it would point to the users' failed tests code. However in this case we want to keep that information because the problem is coming from Jest serializer test() call which may not be in users test code.
I didn't think about that solution though and I must admit that I don't really understand why it is solving our issue here.

@SimenB Your experience with improving stack traces in Jest is welcome here :)

When I started working on this pull request, I didn't fully understand why the stack trace was incomplete. But I realized that we could get the desired outcome by throwing the stack trace itself.
In this pull request, when an error is thrown by a plugin's serialize, print or test function, Jest is going to:

collect the stack trace, that will be further overwritten as @Nargonath pointed out
throw it, making it the error message the stack trace itself

Does it make sense? Should we, instead of throwing the stack trace, avoid to call Error.captureStackTrace when something goes wrong in a Jest plugin?

Does it make sense? Should we, instead of throwing the stack trace, avoid to call Error.captureStackTrace when something goes wrong in a Jest plugin?

This feels more correct, as it fixes the issue, and not the symptom.
The purpose of Error.captureStackTrace is to avoid the matcher part of the stack trace, not actual internal errors

@nicolasiensen why close it?

Shall I make a PR as this one is closed and it seemed that we are heading the way I intended to solve it?

@Nargonath Yes please. Would love to get this is, I'm not sure why the PR was closed

Hey @SimenB, I closed this one since we agree that there is a better solution. Please, check #4787.

Ah, OK! We could have just changed this PR, but a new one is fine 🙂


How can I add shadows?

How can I add shadows to buttons and TextInput?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/24944001-how-can-i-add-shadows?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

Hello there.
I'm afraid there's no easy way to do that like in css3, to may my shadows I'm using an image like this:

and a rule like this:
canvas.before:
Color:
rgba: 1,1,1,0.3
BorderImage:
border: 25,25,25,25
source: 'theme/_shadow1lr.png'
pos: self.x+myoffset, self.y+myoffset
size: self.width+myspread, self.height+myspread
obviously you'll want to take the 'myspread' into account for the offset


Undefined array key ""

ErrorException
Undefined array key ""
:dart: Illuminate\Foundation\Bootstrap\HandleExceptions::handleError
:page_facing_up: /app/app/Traits/HasDisplayRegion.php
11  {
12      return Attribute::make(
13*         get: fn () => ProvinceOrTerritory::labels()[$this->region],
14      );
15  }

Open in Flare

The individual with ID 21 on staging has a region value of ON (confirmed as of Nov. 16 at 15:50 Atlantic time — can be verified from the console using Laravel Tinker: Individual::find(21)->region): https://staging.accessibilityexchange.ca/en/individuals/ben
We've been using this account for testing and it seems like that value keeps getting lost from day to day. I'm putting a pin in this so I can come back and check tomorrow.

Checked again, seems to be resolved.


DateTime -> DayOfWeek

Great work on this site!
I expected this DateTime -> DayOfWeek to return the DayOfWeek property.  Are properties ever returned?

Please use receiver => propertyType query (e.g. DateTime => DayOfWeek).
more information: https://github.com/fsdn-projects/FSDN#search-members

Oh I see.  I think it would be better to just unify these - keep the search syntax very, very simple.

I think it's confusing since string -> int returns System.Int32.Parse.   So I immediately thought oh good, it searches for members too.  I understand that's a static method, which matches the given signature.  But as a naive user I was then surprised that properties were not returned.
I do think just always searching for instance members too is the right default

+1 to search members too by -> by default :+1:

Thank you for the suggestion, @dsyme.
We will implement the function here: https://github.com/hafuu/FSharpApiSearch/issues/80
After it's implemented, we will update FSDN web UI to enable the functionality.

We applied FSharpApiSearch 0.4.0-beta and deployed few days ago https://twitter.com/htid46/status/747333803216015360 .


refactor: fix linter issues

add explicit visibility modifiers
remove unused imports
use individual import instead of global one
had to ignore one line because of inconsistent formatter behavior

C


can not compile the example ...or implement in existing project

Here is the errors (platform set to 10 as per instructions:
(I know this is a long paste ...but can anyone advise how I can implement it...
if I add the plugin to an existing app it ...get the same error and them just corrupts the build ...even after removing and cleaning the project
Error output from Xcode build:
↳
objc[18881]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x1edf5bad8) and
/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x10d1d02c8). One of the two will be used. Which one is undefined.
objc[18881]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1edf5bb28) and
/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x10d1d0318). One of the two will be used. Which one is undefined.
** BUILD FAILED **
Xcode's output:
↳
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvConfirmationViewControllerDelegate.swift:4:56:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvConfirmationViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvInputViewDelegate.swift:4:39: warning: using 'class'
keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvConfirmationViewControllerDelegate.swift:4:56:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvConfirmationViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvInputViewDelegate.swift:4:39: warning: using 'class'
keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardViewControllerDelegate.swift:4:45: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ExpirationDatePickerDelegate.swift:4:47: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol ExpirationDatePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ThreedsWebViewControllerDelegate.swift:4:51: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol ThreedsWebViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/PhoneNumberKit/UI/CountryCodePickerViewController.swift
:7:37: warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
protocol CountryCodePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CountrySelectionViewControllerDelegate.swift:4:57:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CountrySelectionViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/PhoneNumberKit/UI/CountryCodePickerViewController.swift
:7:37: warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
protocol CountryCodePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CountrySelectionViewControllerDelegate.swift:4:57:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CountrySelectionViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvConfirmationViewControllerDelegate.swift:4:56:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvConfirmationViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvInputViewDelegate.swift:4:39: warning: using 'class'
keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvConfirmationViewControllerDelegate.swift:4:56:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvConfirmationViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvInputViewDelegate.swift:4:39: warning: using 'class'
keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ExpirationDatePickerDelegate.swift:4:47: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol ExpirationDatePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardViewControllerDelegate.swift:4:45: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/PhoneNumberKit/UI/CountryCodePickerViewController.swift
:7:37: warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
protocol CountryCodePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CountrySelectionViewControllerDelegate.swift:4:57:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CountrySelectionViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/PhoneNumberKit/UI/CountryCodePickerViewController.swift
:7:37: warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
protocol CountryCodePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CountrySelectionViewControllerDelegate.swift:4:57:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CountrySelectionViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ThreedsWebViewControllerDelegate.swift:4:51: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol ThreedsWebViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/AddressViewControllerDelegate.swift:4:48: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol AddressViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: warning: immutable
property will not be decoded because it is declared with an initial value which cannot be overwritten
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: set the initial
value via the initializer or explicitly define a CodingKeys enum including a 'type' case to silence this warning
let type = "applepay"
^
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ApplePayTokenRequest.swift:7:9: note: make the property
mutable instead
let type = "applepay"
~~~ ^
var
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardNumberInputViewDelegate.swift:5:46: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardNumberInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/PhoneNumberKit/UI/CountryCodePickerViewController.swift
:7:37: warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
protocol CountryCodePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CountrySelectionViewControllerDelegate.swift:4:57:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CountrySelectionViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/PhoneNumberKit/UI/CountryCodePickerViewController.swift
:7:37: warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
protocol CountryCodePickerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CountrySelectionViewControllerDelegate.swift:4:57:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CountrySelectionViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CardViewControllerDelegate.swift:4:45: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CardViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ThreedsWebViewControllerDelegate.swift:4:51: warning:
using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol ThreedsWebViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvConfirmationViewControllerDelegate.swift:4:56:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvConfirmationViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvInputViewDelegate.swift:4:39: warning: using 'class'
keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvConfirmationViewControllerDelegate.swift:4:56:
warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvConfirmationViewControllerDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/CvvInputViewDelegate.swift:4:39: warning: using 'class'
keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol CvvInputViewDelegate: class {
^~~~~
AnyObject
/Users/saabir/Documents/development/tr/flutter_checkout_payment/example/ios/Pods/Frames/Source/ExpirationDatePickerDelegate.swift:4:47: warning: using
'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
public protocol ExpirationDatePickerDelegate: class {
^~~~~
AnyObject
lib/main.dart:10:8: Error: Error when reading 'lib/Keys.dart': No such file or directory
import 'Keys.dart';
^
lib/main.dart:50:66: Error: The getter 'Keys' isn't defined for the class '_HomeScreenState'.
- '_HomeScreenState' is from 'package:flutter_checkout_payment_example/main.dart' ('lib/main.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'Keys'.
bool isSuccess = await FlutterCheckoutPayment.init(key: "${Keys.TEST_KEY}");
^^^^
../../../../flutter/.pub-cache/hosted/pub.dartlang.org/credit_card-0.1.6/lib/credit_card_widget.dart:146:68: Error: The getter 'title' isn't defined
for the class 'TextTheme'.
- 'TextTheme' is from 'package:flutter/src/material/text_theme.dart' ('../../../../flutter/packages/flutter/lib/src/material/text_theme.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'title'.
final TextStyle defaultTextStyle = Theme.of(context).textTheme.title.merge(
^^^^^
../../../../flutter/.pub-cache/hosted/pub.dartlang.org/credit_card-0.1.6/lib/credit_card_widget.dart:267:68: Error: The getter 'title' isn't defined
for the class 'TextTheme'.
- 'TextTheme' is from 'package:flutter/src/material/text_theme.dart' ('../../../../flutter/packages/flutter/lib/src/material/text_theme.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'title'.
final TextStyle defaultTextStyle = Theme.of(context).textTheme.title.merge(
^^^^^
Failed to package /Users/saabir/Documents/development/tr/flutter_checkout_payment/example.
Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Planning
note: Build preparation complete
note: Building targets in dependency order
Could not build the application for the simulator.
Error launching application on iPhone 12 Pro.

Is this still happening ?? @SaabirMohamed
Can you help us here please @edwardmp  ?

Closed due to no response.


EMOD-304 update order states colors

These colors will be applied on new module installations. Is it planned to update the current shops?


Fix single thread exporting

Description
Fix maxThreads: 1 case.
Changes/Tasks
The exporter now takes routes as a seperate arg, separate from config.
Screenshots (if appropriate):

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

I think you'll need to make a change here too https://github.com/nozzle/react-static/blob/master/src/static/index.js#L205

Hm, I did?

Or did you mean something else?


Update links of apparmor doc

Update links for AppArmor failures and AppArmor_Core_Policy_Reference in apparmor doc.

@ping035627 Thanks for your PR! I checked the updates you made on : https://deploy-preview-12593--kubernetes-io-master-staging.netlify.com/docs/tutorials/clusters/apparmor/ and they look fine to me. However, there are a couple of other broken links as well.
https://%!s()/blob/master/content/en/docs/tutorials/clusters/deny-write.profile

error code: 404 (not found), linked from page(s):
https://deploy-preview-12593--kubernetes-io-master-staging.netlify.com/docs/tutorials/clusters/apparmor/

https://%!s()/master/content/en/examples/pods/security/hello-apparmor.yaml

error code: 404 (not found), linked from page(s):
https://deploy-preview-12593--kubernetes-io-master-staging.netlify.com/docs/tutorials/clusters/apparmor/

Could you please fix them as well.

/assign @zparnold

@Rajakavitha1 They links seem to work for me.
/lgtm
/approve

@zparnold The the links that @ping035627 fixed work fine.
However, in the same page (https://deploy-preview-12593--kubernetes-io-master-staging.netlify.com/docs/tutorials/clusters/apparmor/)there are two more broken links:

https://%!s()/blob/master/content/en/docs/tutorials/clusters/deny-write.profile
error code: 404 (not found), linked from page(s):
https://deploy-preview-12593--kubernetes-io-master-staging.netlify.com/docs/tutorials/clusters/apparmor/

https://%!s()/master/content/en/examples/pods/security/hello-apparmor.yaml

error code: 404 (not found), linked from page(s):
https://deploy-preview-12593--kubernetes-io-master-staging.netlify.com/docs/tutorials/clusters/apparmor/

@Rajakavitha1 This is a universal problem. The places of "codenew file=" in other pages are error too.

@ping035627 May I request you to raise an issue and mark it as good first issue and help wanted.


[service-bus] pass abortSignal to link initialization and awaitableSender

Fixes #15311 and #13504.
This update passed the abortSignal to the link initialization method and the awaitableSender.send() method.
It also replaces the defaultLock from core-amqp with defaultCancellableLock which honors the optional abortSignal and timeoutInMs props.
Note: Some operations weren't supporting a timeout today, so I used the default operation timeout where it seemed to make sense to do so.

The CancellableAsyncLockImpl.acquire() should mention that the behavior for both abort and timeout are the same (they only are in effect prior to the inner task being invoked). It's clear for task but not for abort.

Created https://github.com/Azure/azure-sdk-for-js/pull/15417 to address this.

/azp run js - service-bus - tests

/azp run js - service-bus - tests


panic upon encountering an error, so as to cause an OOG in geth

Upon encountering an error in a precompile, geth will OOG and this PR aims at reproducing this behavior.

Related to https://github.com/ewasm/ewasm-precompiles/issues/45


backbone.layoutmanager screencast source does not work with backbone.layoutmanager v0.0.4 without changes

Here's a gist of the changes I made to get it to work.

Well the source code and that screencast are now outdated.  I'll have to create a new one at some point to show off the new features.  The code + screencast are still completely valid for the initial release through 0.0.3


Material Select "offsets" text when leading or trailing whitespace is present

When creating a Select element with the following markup
<select name="language">
    <option value="EN">
                  English
    </option>
    <option value="EN">
                  Romulan
    </option>
</select>

the JavaScript will interpret the HTML including the whitespace leading the text "English" and "Romulan" and append it to the generated span element. This causes the selected option text to be offset by X amount of whitespace producing the Codepen below
The offending JavaScript file seems to be:
https://github.com/Dogfalo/materialize/blob/f7390445388813882d3b6948b0f034dec3eb700a/js/forms.js
And offending lines: L416, L418, L425, L427
The fix "could" be a simple .trim() on the HTML to rid the leading and trailing whitespace.
Codepen for not working scenario: http://codepen.io/webhenrik/pen/mEPOwx
Codepen for working scenario: http://codepen.io/webhenrik/pen/jrqVwo

Same problem here... Is an official fix coming?

I fixed this once for me by simply adding .trim(): https://github.com/Dargmuesli/materialize/commit/b1a32c91b14ef388397e0b4fbac1e314832ee816#diff-338f03716a63d52eee0f79b4510d617c
I guess for v1 it needs to be added (at least) here: https://github.com/Dogfalo/materialize/blob/4a68ebd12c85b81e188988760ec6f16899864da3/js/select.js#L365

Fixed on https://github.com/materializecss/materialize/pull/100


TextEditor.editorElement is deprecated.

TextEditor.prototype.editorElement has always been private, but now
it is gone. Reading the editorElement property still returns a
reference to the editor element but this field will be removed in a
later version of Atom, so we recommend using the element property instead.
TextEditor.editorElement (<embedded>:2381:20)
atomSetPosition (/Users/bayram/.atom/packages/atom-lupa/lib/atom-bindings/middleware.js:5:24)
<unknown> (/Users/bayram/.atom/packages/atom-lupa/lib/atom-bindings/middleware.js:85:21)
<unknown> (/Users/bayram/.atom/packages/atom-lupa/lib/lupaMiddleware.js:89:9)
GoToTransformer.goTo (/Users/bayram/.atom/packages/atom-lupa/lib/middleware/domMiddleware.js:56:32)
GoToTransformer.dispatch (/Users/bayram/.atom/packages/atom-lupa/lib/middleware/domMiddleware.js:76:41)

On my installation*  atom-lupa threw exception in file atom-lupa/lib/atom-bindings/middleware.js (like in your stack trace) but in other place.
On my installation editorElement still exists and is equal to element (but I changed it to element anyway).
On the other hand element.presenter does not exist (I used presenter for this:
presenter.commitPendingScrollTopPosition();.

not sure what this was for, but probably for fixing some issues with Atom scrolling behavior.
Although it seems that even without this line atom-lupa scrolls properly, so I commented it.
*I haveAtom 1.19.1


Update: Multi Content Card

https://issues.redhat.com/browse/RHCLOUD-34201
Structurally/architecturally this component would be a reflection of the way it is built within the horizontal card

[ ]  !important override being used to control margin. It is set to 16px override but should be updated to 8px using: global/spacer/gap/text-to-element: 8px/spacer-200 -- this might be automatically fixed when the changes to semantic spacers are launched, not sure. Lets try to avoid overrides if possible :)

[ ] Icon color and section heading text color need updated to be global/icon/color/brand/default and global/text/color/brand/default

[ ] Card heading size H4 needs updated to be Heading/sm(h3)

use --pf-t--global--spacer--control--horizontal--plain for margin

icon color should be --pf-t--global--icon--color--regular

heading text color should be --pf-t--global--text--color--brand--default

heading size should be --pf-t--global--font--size--heading--h3

Hey @fhlavac Looks like the spacing is off on the expandable multi content card - Seems correct on the basic. When I inspected it, it appears that there is a 24px top padding applied to the class="pf-v6-c-card__header" for "Getting Started" Lets remove the 24px top padding on all headings below the expandable content heading. Not sure if it's best practice to apply margin to correct the spacing of the item or use padding to correct the spacing?? Thinking the top level heading that says expandable card toggle text needs to have a bottom padding of 16px applied and the 2nd level headings that say "getting started" and "next steps" should have no top heading or margin applied.
Also thinking that maybe we can apply some labels to show that this is an option?
Heres a screenshot of what it needs to look like for spacing :

Here is an example of a label within the multi content card:

@kaylachumley I opened a PR adding these changes, just not sure about the heading sizes - expand toggle vs the card titles (Getting started, Next steps - should probably be smaller, just not sure about the size) https://react-component-groups-pr-component-groups-245.surge.sh/extensions/component-groups/multi-content-card#expandable-multi-content-card-with-actions-and-labels
Thank you

Hey! @fhlavac I added a screenshot to show context for what the text sizing should visually look like. Let's make all the main heading that says "Card actions with toggle text" to be --pf-t--global--font--size--heading--h3  and then lets make all second level headings "Getting started"and "next steps" etc. to be --pf-t--global--font--size--heading--h4
But note that there is not always a scenario to have an H4 across all use cases. I imagine there being use cases where there is only a label.


Set correct hasChanged and set it on all entry persistence actions

- Summary
Bugfix; closes #287 (for real this time).

- Test plan
Manually tested on editorial workflow and regular workflow, with both github and test backends.

- Description for the changelog

Don't ask for navigation confirmation on save

- A picture of a cute animal (not mandatory but encouraged)

LGTM, tested locally as well. Works in and out of editorial workflow.


Merge release branch to master

Title (required)
Merge release branch to master
Description (required)

Hmm, I got the same issue with unnecessary file changes the last time I tried to do this as well @maskaravivek . :/ I think it might have something to do with the buggy PR that was merged previously. Master already has up to 2.8.3 so we can probably just cherry-pick 525d5da and 9b708db onto master and we'll be sorted. No need to cherry-pick the 2.8.4 change (the target SDK change) because the ideal fix is already in master.

As discussed in #1931, I am just cherry-picking 525d5da and 9b708db to be merged with master.

Codecov Report

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

@@            Coverage Diff            @@
##           master   #1932      +/-   ##
=========================================
- Coverage    3.71%    3.7%   -0.01%
=========================================
  Files         192     192
  Lines        9915    9933      +18
  Branches      886     889       +3
=========================================
  Hits          368     368
- Misses       9520    9538      +18
  Partials       27      27

Impacted Files
Coverage Δ

app/src/main/java/fr/free/nrw/commons/Utils.java
27.39% <ø> (ø)
:arrow_up:

...java/fr/free/nrw/commons/upload/UploadService.java
0% <0%> (ø)
:arrow_up:

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 e36a71a...f508002. Read the comment docs.

Thanks @maskaravivek !


genioglossus, belied

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 5
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,g]

/trunk merge


Adding first game in rust

Hello, It is my first open-source PR
If I make mistakes let me know I gonna makes changes

Looks good thank you!


For V2 only- search PBot ID

Matt thought it would be helpful to just be able to search on a PBot ID and find out what it is. I agree, but this is definitely a v2 thing, as you would also need a new check bubble on the lefthand side of the window.

I concur. This should theoretically be doable through the API already though.


Fixes empty list decoding by bumping Poison version

Updates Poison to get this fix. No changelog despite the major, but doesn't look like the API was updated, plus the tests are passing.
No issues on the inch_ex major either.

@jmnsf Thanks for all the PRs. I'll take a look at them soon


Implement Invoking subscription functions in Ballerina

Purpose
#TODO
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #19397   +/-   ##
=======================================
  Coverage   15.71%   15.71%
=======================================
  Files          47       47
  Lines        1266     1266
  Branches      197      197
=======================================
  Hits          199      199
  Misses       1054     1054
  Partials       13       13

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 62357eb...4d6be63. Read the comment docs.


Use MySqlConnector for async I/O

The MySqlDapper code uses Dapper's QueryMultipleAsync, which will call DbConnection.ExecuteReaderAsync. It's a long-standing bug in MySql.Data (bug 70111) that async I/O is not implemented correctly; thus all these methods will actually run synchronously. (See also here and here on Stack Overflow.)
To fix this, you could switch to https://github.com/mysql-net/MySqlConnector, an OSS replacement for MySql.Data that supports true asynchronous I/O; it also has full .NET Standard/.NET Core support.
If you're interested in this, I'd be happy to open a PR.

Thanks, I will fix it


Typo in footer

Expected text:

The source code for this website...

Current text:

The source coooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooode for this website...

typo in the footer

I  will claim this issue!

I'll claim this issue

Claiming

claiming too


Fix Reckless Attack

I think that Reckless Attack should be split into two different effects.
Currently it both grants you advantage on attacks and grants enemies advantage on attacks against you until your next turn.
However, you should only get advantage on attacks until the end of your current turn, and not on readied attacks or opportunity attacks and the like.

Good idea. I'll update it so it does this

Fixed in v3.2.0


Using fork of cookiecutter

post_gen_project.py is calling a cookiecutter function that is only found in this fork:
https://github.com/luzfcb/cookiecutter
from cookiecutter.prompt import query_yes_no
should be
from cookiecutter.prompt import read_user_yes_no
and the function calls changed accordingly. Note, you must provide a default_value in the call now.
def configure_role():
    print('\n\nROLE CONFIGURATION:\n===================')
    for folder_name, folder in folders.items():
        if read_user_yes_no(folder['question'], default_value=u'yes'):

            try:
                # this file has to be there, git doesn't store empty folders.
                os.remove(os.path.join(folder_name, '.empty'))
            except OSError:
                pass

            if 'hint' in folder:
                with open('{}/main.yml'.format(folder_name), 'a') as fp:

                    if 'pre_hint' in folder:
                        if read_user_yes_no(folder['pre_hint'], default_value=u'yes'):
                            fp.write(folder['pre_action'])

Same problem here.

Merged into master


Make qq namespace accessible via the wrapper classes

...so that items such as qq.status and qq.supportedFeatures can be accessed. For example:
import FineUploaderTraditional from 'react-fine-uploader'

const uploader = new FineUploaderTraditional({...})
const canDropFolders = uploader.qq.supportedFeatures.folderDrop

All exposed components that have qq.status values hardcoded should be updated to pull the values from qq.status after this change.

Implemented in the wrapper library in FineUploader/fine-uploader-wrappers@c61dd93a246865e706b81bbf17942f5c73ab9e3e.
TODO:

Update React Fine Uploader to make use of this newly exposed qq namespace.


when typing, everything appears 6 characters to the left of the cursor

When you place the cursor to type, and then start typing, the letters appear 6 characters to the left of the cursor. In the attached screenshot, you can see the cursor and you can see the 'xxx' that was typed and where it was inserted.

I just had the exact same issue.
kikko088's fix worked for me too, but I think this issue should be addressed!?

Agree this should be done. I'm short of time at the moment.
The ACE editor is a submodule, located: https://github.com/faceleg/ACEView/tree/master/ACEView/Dependencies
If someone bumps that and submits a PR I'll gladly accept!

@planerde's PR #33 should have fixed this!


Fixed merge errors and screenshots

You can watch the snapshot from #32
This is just better version.

Get this branch into the production line. Had to watch a 30 min video to learn to avoid merge conflicts.

I have added better images. You may checkout them on #32.

Just recreated this meme with the website. Anyways get this #32 merged to fix them.

Why merge closed PR ??


Bump version

Since we've made breaking API changes, cut 1.0a2 so we can propagate those changes to PPB.

bors r+


Defchain Bridge "Confirm" Button not working properly

I tried sending DFI to the Binance Smart Chain which was working pretty well until I wanted to apply the 10/10 confirmations.
I was not able to confirm the funding of the Metamask wallet, the button was not working and the funds have not been credited to my MetaMask Wallet.
10 DFI have been send to the given address: 8PxzEk3KbuPrkyXUqUz4vkaHP1GcMCvfjf
My Metamask: 0x9eEA08a334268e842Bc7Bc12F9FF5413b62Aa80d
Here are the TX:
https://defiscan.live/transactions/d87018c5560979c60f13c389fddcfbcd3bc54b13a9cf0c14e14064c2a5b12c6f
https://defiscan.live/transactions/68b8c16414bef6c3327a730936c8b1ed6f224523a09af20b0c0e58c905361050
I am not able to recover my funds. Is there any plan, when the funds have not been confirmed to send back the tokens to the original address as part of the smart contract?
My DFI address: dSiY9xDmzqANWDig3ZXNkYHx894HpYZvXh

May you had a chance to take a look on the transactions? Would be keen to know whats going on before putting more money into the system/bridge.
Thank you!


chore(chat): fix clear all and refactor of util-methods (part 2) (Issue #793, #780, #842)

Description:
Refactoring of util-methods:

[ ] regex escape from lodash-es

Issues:

Issue #793
Issue #780
Issue #842

UI changes
<Please, provide Screenshots or Figma links>
Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


Add option to allow analyze to detect multiple faces

Dear Sefik,
This PR adds the optional flag enable_multiple to DeepFace.analyze, which analyzes multiple faces in the given input image and returns a result for each one of them. If it is set to False, all output should remain the same as it was before (except that I renamed the keys from instance_n to image_n.
It's quite a lengthy PR, especially because I have reformatted the functions.py file, as it contained tabs instead of spaces.
I tried to create small commits that contain individual changes and refactors as I went along, so I would suggest to look at the individual commits + messages for the best understanding of my changes.
Furthermore I noticed that some people requested this feature before, but you mentioned it was 'out of scope' of this library, so I understand if you do not want to merge this (in that case i'll continue on my own fork) but I would like to at least share my changes with you in case you are interested.

Sorry for the delay. It seems that I can spend time on 2nd week of Oct.

Sorry for the delay. It seems that I can spend time on 2nd week of Oct.

No problem, thanks for the heads-up! In the mean time I'll resolve the conflicts with master.

Thank you for your understanding, I am going to be on a vacation for a week.

Any updates about this issue? The added feature - detect multiple faces - is quite useful!

@RoelofRuis Do you mind share your multiple faces fork with me? I'd like to try it, thanks!

@RoelofRuis Do you mind share your multiple faces fork with me? I'd like to try it, thanks!

@yiouyou I think you can just refork my fork that holds this feature at https://github.com/PBWebMedia/deepface/tree/detect-multi-face
On the develop branch of that fork, there are some more features/changes, they are incrementally built on top of this one. You can check them out as well if you like, just take a look at the commit messages to see what I've changed/added.

Dear Sefik,
Let me first say I understand you having a chaotic time, so no need to feel sorry for not handling this earlier :)
But as of coming wednesday december the first, I will not have access anymore to the PBWebMedia organization and thus their fork of this project. Therefore I will close this MR.
If you have any interest in this feature in the future, please contact me and I'll see if I can invest time to resolve the current conflicts with master using a fork from my personal account and open a new MR.

@RoelofRuis
There is no multi-support for DeepFace.find(), is it only analyze?


fix module import

sorry for that I can not import "HtmlFormattor" in module "pygments.formatters",but I found it under "html" which is imported from module "pygments.formatters".

Merged with 86919082e44f7256557646f4a764e2af92e53951
Pygments removed the import of HtmlFormattor in the new releases.


Laravel 5.5 support

Please add Laravel 5.5 support (auto package discovery) and create a new version. And maybe fix the markdown in de readme?

I will try to find time next week.
What's wrong with the markdown in the readme?

The headings, for example these:

https://github.com/ied3vil/LanguageSwitcher/pull/12

Fixed the headings

Thanks! But the headings are fixed but still no auto package discovery support voor Laravel 5.5


Fix expectedFailures for Documents

This PR fixes two expectedFailures for Documents:

The documents are given a random suffix to prevent filename collision, and this was not taken in to account in the tests. Serving documents with the original, uploaded filename would require a new field being added to record the initial name, which does not seem worth the cost. Now, the tests check the document is served with the suggested filename including the random suffix.
Accessing the serve method with an incorrect filename was expected to return a 404 response, but it was instead serving the file. In my opinion, this is the correct behaviour, so the test has been updated to match, and my opinion has been added as a docstring.

Both of these are opinionated changes, but in my opinion these are the right changes to make.
This PR was broken out of #1778

I agree with both, thanks!


SAMZA-2498: [Job coordinator isolation] Classloader isolation for SamzaApplication.describe execution in job coordinator

Feature: https://cwiki.apache.org/confluence/display/SAMZA/SEP-24%3A+Cluster-based+Job+Coordinator+Dependency+Isolation#SEP-24:Cluster-basedJobCoordinatorDependencyIsolation-HandlingSamzaApplication.describe
Changes:

Add a method IsolatingClassLoaderFactory.buildSamzaApplicationClassLoader to construct a classloader for loading the SamzaApplication implementation for an app.
If isolation is enabled, then call buildSamzaApplicationClassLoader to load the SamzaApplication implementation in the job coordinator.

Tests:
Deployed wikipedia-feed application (uses low-level API, has custom input descriptor, uses Kafka output descriptor) and wikipedia-parser application (uses low-level API, Kafka descriptors) in split deployment mode with some debug logs, and verified the following:

TaskApplicationDescriptorImpl and KafkaSystemDescriptor came from the framework infrastructure classloader.
WikipediaSystemDescriptor (custom descriptor) came from the application classloader.
WikipediaFeedTaskApplication (impl of SamzaApplication) came from the newly built application describe classloader.
Lambda which was used for the TaskFactory in WikipediaFeedTaskApplication came from the newly built application describe classloader, and it implemented the StreamTaskFactory interface which was loaded by the framework API classloader.
Verified expected system-stream metadata from custom system (WikipediaSystemFactory)
Deployed wikipedia-parser application (uses low-level API, Kafka descriptors) and verified the classloaders using debug logs.

API/usage changes: None

This approach does not properly satisfy the isolation requirements. I will open up a separate PR with a different solution.


Nginx Transparent Mode Support

Nginx (apparently) support transparent layer 2 support. This might be an easier way to run mod_security (within Nginx) since it would provide the layer 2 support that mod_security by itself does not provide.
https://rickheil.com/nginx-as-a-transparent-reverse-proxy/

Unfortunately in that example it's being used the same was a mod_security as a transparent reverse proxy, which is happening at layer 3. You access the nginx on port 80, then it reverse proxies to the graylog server which is running locally on 9000.
For most of the layer 2 stuff we are looking at, the easiest way to tell if an application can do layer 2 work is if it listens promiscuously on an entire interface, just like snort in inline mode.


[hotfix] FigShare OAuth canellations redirected incorrectly

Purpose
Ensure redirects for user OAuth requests that are cancelled are handled correctly
Changes
Cancelled requests from a user's settings page will redirect to their /settings/addons/ and cancelled requests from a projects settings page will be redirected to the project's /settings/ page
Side Effects
None
Closes-Issue: #1844

@HarryRybacki Can you please add a regression test for this?

Re-opened in PR: #1910


SILGen: Delay function conversions to types with opened archetype arguments.

This comes up when invoking protocol methods on an existential that have covariant arguments of function type with Self arguments, e.g.:
protocol P {
  mutating func foo(_: (Self) -> Void)
}
func bar(x: inout P) {
  x.foo { y in return }
}

Although the type-erased method is presented as formally taking an argument of the existential type P, it still has a conversion thunk to perform type erasure on the argument coming from the underlying implementation. Since the self argument is inout, it isn't formally opened until late when formal accesses begin, so this closure conversion must also be deferred until after that occurs.
rdar://problem/42215661

@swift-ci Please test

@swift-ci Please test source compatibility

Wow, that’s simpler than I expected! Nice job.

@jckarter Thanks!


Make tracking of kprobe request headers optional

Tracking and processing request headers in kprobes mode can introduce additional CPU overhead, because we capture request buffer values of up to 1K bytes. This processing is wasteful if the customer is only interested in Beyla metrics or they don't pass 'Traceparent' in their requests. At the same time, we currently cannot propagate the 'Traceparent' context for kprobe based request tracing, so the header tracking is of limited value.
With this PR I'm adding making the 'Traceparent' processing of kprobe based request tracing optional, and it's disabled by default. Customers can opt-in if they want their traces to respect the incoming traceparent for HTTP services.

Codecov Report
Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (a1d9782) 43.06% compared to head (a1612d5) 42.79%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #416      +/-   ##
==========================================
- Coverage   43.06%   42.79%   -0.28%
==========================================
  Files          55       55
  Lines        4400     4407       +7
==========================================
- Hits         1895     1886       -9
- Misses       2386     2399      +13
- Partials      119      122       +3

Flag
Coverage Δ

unittests
42.79% <0.00%> (-0.28%)
:arrow_down:

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

Files
Coverage Δ

pkg/internal/ebpf/common/common.go
62.50% <ø> (ø)

pkg/internal/ebpf/httpfltr/httpfltr.go
32.00% <0.00%> (-0.61%)
:arrow_down:

... and 2 files with indirect coverage changes

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

LGTM!

Thanks Mario!


Plugin usage with known playlists

Hello,
since the actually for-this-more-suitable-tool "Streamlink" is quite buggy when it comes to random read timeout errors for whatever reason, I'm looking for an alternative which is capable to download segments from m3u8 playlists in multiple threads to increase the effective data throughput and resemble them in one file.
While your tool seems to support URL detection from websites, I wonder how I can use your tool when I already know the m3u8-URL of a specific stream. At least in text form or entered a HREF in an HTML file, it doesn't seem to detect anything ...

this plugin simple doesnt detect the playlist... would be so much simplier to give option to provide the playlist url

Part of v3.1.0, due to chrome removal, you will need to install manually, check out here: https://github.com/puemos/hls-downloader-web-extension#installation


Adding Force to GameObjects in Unity (using MuJoCo physics)

Hi. I am trying to add a force vector to a cube in Unity, yet to my best knowledge, in order to add a force vector to a GameObject in Unity, the script itself needs a rigidbody. If using MuJoCo physics in Unity, which replaces the need for rigidbodies, how do I add a force vector? The following C# script is how I simply added a force vector to a cube that is not using MuJoCo physics properties and does in fact have a rigidbody.

AddForce
using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class AddForce : MonoBehaviour
{

    Rigidbody m_Rigidbody;
    public float m_Thrust = 1000f;

    void Start()
    {
        //Fetch the Rigidbody from the GameObject with this script attached
        m_Rigidbody = GetComponent<Rigidbody>();
        m_Rigidbody.AddForce(transform.forward * m_Thrust);
    }

}

Take a look at how MjMouseSpring.cs does it, its inside the Editor components folder of the plugin. Basically its editing a field in the mujoco scene's data structure, something like this:
scene.Data->xfrc_applied[6*body.MujocoId + 0] = appliedForce.x;
scene.Data->xfrc_applied[6*body.MujocoId + 1] = appliedForce.y;
scene.Data->xfrc_applied[6*body.MujocoId + 2] = appliedForce.z;

Where appliedForce is the Mujoco vector representation of your force. You may need to convert it to that format first with MjEngineTool.MjVector3(Vector3 unityVec) first. Also as far as I can tell xfrc_applied is persistant, i.e. you need to set it to 0 once you are done with accelerating something.
Alternatively if your cube is just a free body (i.e. has a freejoint) you may also control the appropriate elements of qfrc_applied as well, which may be equivalent in this case.
For more info you can check out the docs adressing this:
https://mujoco.readthedocs.io/en/latest/APIreference.html
https://mujoco.readthedocs.io/en/latest/programming.html?#simulation-loop

Ok. I was looking around MjMouseSpring, MjBody, etc. and was still a little lost (I am very new to MuJoCo so its just a little confusing for me). The goal for what I am doing is to apply a force on the Z axis only to a free body cube. I understand that I would want to do something like
scene.Data->qfrc_applied[body.MujocoId + 2] = appliedForce.z;
but the problem that I kept running into was that I am trying to do this in a MonoBehavior class but then I kept getting stuck on how to add MjBody body = target as MjBody; in order to call .MujocoId on the object itself (basically what I am saying is that I do not know how to implement the qfrc_applied onto a specific game object and therefore use the appliedForce method in a MonoBehavior script)
Thank you in advance. I'm just starting with Mujoco and your help is greatly appreciated.

No problem! In Mujoco there is a slightly different approach to how information about elements in a scene are stored and accessed when compared to how Unity handles it on a surface level. I may go into details that you are already familiar with, but I'd like to mention them just in case.
But first to explain how target as MjBody is used. That is actually only related to the fact that MjMouseSpring is an editor script. When you use the mouse spring, you need to tell the Editor that the component currently selected while clicking is an MjBody specifically. In a regular MonoBehaviour you don't need to cast the component to an MjBody, you can just Get the component once and store it as an MjBody.
Once you have a GameObject with an MjBody attached, an MjScene will be created at the start of play mode. After that, all information about the Mujoco side of the simulation can be accessed through that MjScene. Instead of each MjBody storing all information about their state themselves, the MjScene keeps track of all bodies' current states, velocities and accelerations on separate arrays. Since, for example, all positions are stored in one array, if you want to find the data of a specific body, you need to know where to start within that array. This address will be different for different arrays, depending on how many array elements there are per body/component. There are different ways to access this address for each array, but it is often body.MujocoId * someConstant. In your case that constant is 6 for xfrc_applied (since there are 3 elements for position, 3 for rotation for each body). If you want to use qfrc_applied instead, you need to get the qpos address of the freejoint that is the child of MjBody. I recommend sticking with xfrc for now.
Now that you have the address of where your current MjBody's information starts in the xfrc_applied array, you need the array itself. You access it from the MjScene like this:
MjScene.Instance.Data -> xfrc_applied
Behaviours that often need to access the mujoco Data may store the reference to the MjScene like this:
MjScene scene = MjScene.Instance
Also don't forget that in Mujoco the order of vector components are different (the Z component is up). Perhaps the best way to get the mujoco force vector that accelerates your object towards the local forward is to use MjEngineTool.MjVector3(transform.forward) and apply all 3 components to xfrc_applied.
Let me know if anything else is unclear!

If you frequently have to apply xfrc to MjBodies it might be worth writing an extension method for that. Something like this (untested):
public static unsafe void AddForce(this MjBody body, Vector3 unityFrc)
{
    Vector3 appliedForce = MjEngineTool.MjVector3(unityFrc);
    MjScene scene = MjScene.Instance;
    scene.Data->xfrc_applied[6*body.MujocoId + 0] = appliedForce.x;
    scene.Data->xfrc_applied[6*body.MujocoId + 1] = appliedForce.y;
    scene.Data->xfrc_applied[6*body.MujocoId + 2] = appliedForce.z;

}

That is very helpful! The only problem that I am running into right now is during runtime, a NullPointerException is thrown, stating that an object reference is not set to an instance of the object. I presume this issue is coming from the body.MujocoId. I have been playing around with how to properly initiate and declare MjBody body.

Ok. Is the way I initiated and declared correct (as in setting Mujoco.MjBody body = GetComponent<Mujoco.MjBody>())? I know that I can't use MjBody body = new MjBody() or use MjBody body= MjBody.Instance. At this moment, after making sure that the scene is initialized before start by redefining the execution order, I still obtain the same error of null pointer exception due to an object reference is not set to an instance of the object.

   Hi. I'm sorry for the repeated questions. I got it to a point where there are no compiler or runtime issues. I have safeguards to make sure that the `scene` and the `body` references are present and attached to the gameObject. When ran, the block that the force should be enacted on is not moving at all, which is strange because I even have 3 lines that are printed to the console that prints the forces enacted on each the x, y, and z axis. Not really sure where my issue is coming from now. LMK if you have any ideas but I greatly appreciate your help.

   `public float m_Thrust = 1000f;
    Mujoco.MjBody body;
    Mujoco.MjScene scene;
    Vector3 unityVec;
    unsafe void Awake()
    {
        scene = MjScene.Instance;
        scene.CreateScene();
        body = GetComponent<Mujoco.MjBody>() as MjBody;
    }

    unsafe void Start()
    {
        //The unity vector uses the Unity strange coordinates (where z is the blue line)
        unityVec = new Vector3(0.0f, 0.0f, 50.0f);
        Vector3 appliedForce = MjEngineTool.MjVector3(m_Thrust * unityVec);

        if(!scene)
        {
            Debug.Log("scene not found");
        }

        if (!body)
        {
            Debug.Log("body not found");
        }

        if (scene != null)
        {
            scene.Data->xfrc_applied[6 * body.MujocoId] = appliedForce.x;
            scene.Data->xfrc_applied[6 * body.MujocoId + 1] = appliedForce.y;
            scene.Data->xfrc_applied[6 * body.MujocoId + 2] = appliedForce.z;
            Debug.Log("x-axis force: "+ appliedForce.x);
            Debug.Log("y-axis force: "+ appliedForce.y);
            Debug.Log("z-axis force: "+ appliedForce.z);
        }

        else
        {
            MjScene.Instance.CreateScene();
        }

    }

}`

Hi. I'm sorry for the repeated questions. I got it to a point where there are no compiler or runtime issues. I have safeguards to make sure that the scene and the body references are present and attached to the gameObject. When ran, the block that the force should be enacted on is not moving at all, which is strange because I even have 3 lines that are printed to the console that prints the forces enacted on each the x, y, and z axis. Not really sure where my issue is coming from now. LMK if you have any ideas but I greatly appreciate your help.
`public float m_Thrust = 1000f;
        Mujoco.MjBody body;
        Mujoco.MjScene scene;
        Vector3 unityVec;
        unsafe void Awake()
        {
            scene = MjScene.Instance;
            scene.CreateScene();
            body = GetComponent<Mujoco.MjBody>() as MjBody;
        }

        unsafe void Start()
        {
            //The unity vector uses the Unity strange coordinates (where z is the blue line)
            unityVec = new Vector3(0.0f, 0.0f, 50.0f);
            Vector3 appliedForce = MjEngineTool.MjVector3(m_Thrust * unityVec);

            if(!scene)
            {
                Debug.Log("scene not found");
            }

            if (!body)
            {
                Debug.Log("body not found");
            }

            if (scene != null)
            {
                scene.Data->xfrc_applied[6 * body.MujocoId] = appliedForce.x;
                scene.Data->xfrc_applied[6 * body.MujocoId + 1] = appliedForce.y;
                scene.Data->xfrc_applied[6 * body.MujocoId + 2] = appliedForce.z;
                Debug.Log("x-axis force: "+ appliedForce.x);
                Debug.Log("y-axis force: "+ appliedForce.y);
                Debug.Log("z-axis force: "+ appliedForce.z);
            }

            else
            {
                MjScene.Instance.CreateScene();
            }

        }

    }`

Are you sure that the gameobject has a child gameobject that has a mjfreejoint component? In Mujoco by default bodies are not allowed to move. You need to allow a body degrees of freedom (number of ways it can move in relation to its parent body) by associating a joint with it. Freejoint allows unrestricted movement, which is what you need.
If you didnt have a joint, then there is also a chance you dont have an MjGeom either. MjGeom components are the equivalent of colliders in mujoco. That should be attached to another child gameobject (sibling of the joint). That gives you a collider but no rendering. You can right click the geom component and you should see the option to automatically add the corresponding mesh renderer.


Kindle Fire 7 2019 - App crashes frequently when we background and foreground the app.

Phaser Version:
3.5.0

Description
Bug effecting many Kindle devices particularly Kindle 7 2019
Example Test Code

Additional Information
We are working on children's Apps at the BBC. Our game supplier agency have reported this bug which we believe affects many of our games and many upcoming planned releases. It would be brilliant if you had any advice or suggestions on how to resolve this.
https://github.com/bbc/cbeebies-go-explore-app-numberblocks-mathematics/issues/153
We’re pretty sure now this issue is being caused by a bug in Phaser 3.x on this device and is not memory related at all. We have tried hugely reducing the memory imprint of the game- made no difference. We discovered in fact that the game is crashing with the WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost error the moment it is backgrounded, not when foregrounded as you might expect if we were running out of memory.
We then investigated what apps/games this is happening to and if there was commonality- and on the Go Explore games at least- the two games with the issue are Numberblocks and JoJo and Gran Gran, both of which use Phaser 3.5.x. Games using older version 2.x of Phaser such as Biggleton or Alphablocks are not showing the issue.
We then tested some basic Phaser 3 demos on the device (in the Silk browser) and they are crashing in the exact same way- the moment you background the browser, contexts are lost, the demo crashes and the browser reloads. This Phaser 3 benchmark test is a good example- it’s not remotely heavy memory wise, but has the issue on the Kindle 7 2019-
https://phaser.io/examples/v3/view/game-objects/blitter/benchmark-test-3
Phaser 3.5 does have some methods for testing for CONTEXT_LOST and we tried listening for this to see if we could catch the error before the crash, but that has not worked. We also tried updating the game to use the latest Beta version of Phaser 3.6- but that did not help. In fact in the release notes for 3.6 we found the following:
The CONTEXT_RESTORED Game Event has been removed and the WebGL Renderer no longer listens for the contextrestored DOM event, or has a contextRestoredHandler method. This never actually worked properly, in any version of Phaser 3 - although the WebGLRenderer would be restored, none of the shaders, pipelines or textures were correctly re-created. If a context is now lost, Phaser will display an error in the console and all rendering will halt. It will no longer try to re-create the context, leading to masses of WebGL errors in the console.
This never actually worked properly, in any version of Phaser 3 - although the WebGLRenderer would be restored, none of the shaders, pipelines or textures were correctly re-created.
We have also tried the beta version of Phaser 3.6

If your game doesn't rely on webgl-specific issues you can force canvas renderer for troublesome devices/browsers.

@vforsh Thanks for your response
We have tried switching to Canvas rendering, but the game uses the Spine runtime in Phaser for environments and animation and this does not have support for using meshes in Canvas- you must use WebGL for this as described here:
http://en.esotericsoftware.com/forum/Problem-with-Canvas-rendering-12727
Unfortunately there's no way now the game could be rebuilt to not use meshes.

I do work at the BBC. Leave it ewith me and I'll see what might be possible and will let you know via email.

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


Add ability to minimize the map portlet

We have some older code that @mmoayyed and @bourey worked on in our version of this portlet. We'll commit this back to the project.

Awesome @asgrant!
Looking forward to seeing a PR for this!

:bell: any update on this?

We no longer use this portlet, although I can ask one of our student developers to look at adding this feature in.


[CODEOWNERS] Addition for Recovery Services Backup

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/check-enforcer override


fix: upgrade to version 3.2.62

from: https://github.com/jenkins-x/jx

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign daveconde
You can assign the PR to them by writing /assign @daveconde in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test tls

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
66366234bb039e25b5f5a2fb4ac3269d2a1c8269
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Remove unused resource package

This got moved to pkg/release - we remove it here to get an better overview of what is actually used.

Rebased on top of latest master.

chart-operator is using resource pkg still, and it has to move to pkg/release.
@MarcelMue How did you check this? Any migration did you do before you do this PR, so I can also look into it?

@tomahawk28 I did check this by vendoring it but it was in April. This was merged by Stevo - My assumption would be that you can use the new functions in place of the old ones. Uncertain as I would need to take a deeper look to get back into it.


Hard to intercept output when redirecting StdErr

I tried to execute an executable (tfx) and in case of an error capture the error message. This turns out to be very difficult.
let tr = new tr.ToolRunner(tl.which("tfx.cmd"));
tr.exec(<any>{ failOnStdErr: false, errStream: myStream });

Doesn't redirect anything to myStream, it turns out thet when failOnStderr is false output is instead redirected to StdOut.
But when I capture stdOut, the error message isn't added to my buffer:
let tr = new tr.ToolRunner(tl.which("tfx.cmd"));
tr.exec(<any>{ failOnStdErr: false, outStream: myStream });

Turns out this may have to do with the fact that I did't set IgnoreResultCode: false, because if that's set, it will fail the task before actually allowing me to inspect the result.
I looked at the ANT task and stole
https://github.com/Microsoft/vsts-tasks/blob/master/Tasks/ANT/anttask.ts#L241-L253
But that doesn't seem to work, it doesn't ever receive a line.
I simplified the code and removed the buffer (I get why it's there, but it isn't working it seems) and ended up with:
var buffer;
    tfx.on('stderr', function (data) {
        if (data) {
            var line =  data.toString();
            if (line.indexOf("Error:") >= 0) {
                var tferrorIndex = line.indexOf("TF1590010");
                if (tferrorIndex < 0) {
                    tl.setResult(tl.TaskResult.Failed, line);
                }
                else {
                    console.log(line.substring(tferrorIndex + 11));
                }
            }
        }
    });
    var result = tfx.exec({ silent: true, failOnStdErr: false });

and after a lot of frustration I finally found a way to (so far) reliably intercept the error output and override it.
All in all it took way too much time and I encountered too many surprises.
My expectations would have been:

If I supply a error stream, it is called regardless of silent:true and failOnstdErr:false
If I set failOnStdErr:true, I expect the task to fail, but still allow me to intercept the output
If stdErr is redirected to stdOut by your code, I expect the output to end up in the supplied outStream, right now it bypasses the supplied outStream and is logged to the console.

Found another way which seems to be the easiest:
    const result = tfx.execSync(<any>{ silent: false, failOnStdErr: false });
    if (result.stderr.search("error: Error: (?!.*TF1590010)") >= 0) {
        tl.setResult(tl.TaskResult.Failed, "Failed");
    } else {
        tl.setResult(tl.TaskResult.Succeeded, "Succeeded");
    }

It doesn't let me intercept the message (so I can remove the "ERROR:" part from it, but at least I get to inspect what I want.

tool runner emits stderr and stdout events that can be listened to.
also, it seems like it may be better for the lib to write to whatever stream it was given. that would give the user the flexibility to use the same stream if they want. the only thing that concerns me, i'm not sure offhand whether that would introduce any challenges due to stdout buffering.

I've had very inconsistent results with the events as well, especially
since they act on buffers and not on lines. Plus they seem to influence the
standard behavior.
On Dec 2, 2016 10:47 PM, "ericsciple"<EMAIL_ADDRESS>wrote:

tool runner emits stderr and stdout events that can be listened to.
also, it seems like it may be better for the lib to write to whatever
stream it was given. that would give the user the flexibility to use the
same stream if they want. the only thing that concerns me, i'm not sure
offhand whether that would introduce any challenges due to stdout buffering.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vsts-task-lib/issues/183#issuecomment-264571393,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD-uSyKD7zMNl_uThMfyumMsawjsoGB5ks5rEJH8gaJpZM4LC4Aj
.

Obviously this issue has been alive for a while, so some of the things you initially noted may have changed, my answer is based on the current version of the library:

If I supply a error stream, it is called regardless of silent:true and failOnStdErr:false

I don't think it makes sense to send the error stream to stdErr (or an errStream that is supplied in place of stderr), this is discussed in more detail in #333. In short, if we don't want to failOnStdErr, then the error in the execution of a tool probably shouldn't be considered an error in the execution of an entire task.

If I set failOnStdErr:true, I expect the task to fail, but still allow me to intercept the output
If stdErr is redirected to stdOut by your code, I expect the output to end up in the supplied outStream, right now it bypasses the supplied outStream and is logged to the console.

I think this currently is the behavior - see here

I've had very inconsistent results with the events as well, especially since they act on buffers and not on lines. Plus they seem to influence the standard behavior.

I haven't run into this (maybe something that has been fixed since this was opened). Is this still an issue?

I'm going to close here, please reopen if appropriate.


Dependency issues regarding security

I'm getting similar errors like this that indicates module changes, vulnerabilities and deprecated packages.
warning react-native > xcode ><EMAIL_ADDRESS>use uuid module instead
warning gitbook-cli > npm > request ><EMAIL_ADDRESS>use uuid module instead
warning gitbook-cli > npm > request ><EMAIL_ADDRESS>ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
warning gitbook-cli > npm ><EMAIL_ADDRESS>This package is deprecated. Use Array.isArray.
warning gitbook-cli > npm > node-gyp ><EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning gitbook-cli > npm > node-gyp > glob ><EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

I'm going to close, but let me know if you have any more questions.


Incorporate SSR core (nations) into the Soviet union.

fr-rein
If you help that Azerbaijan, you get 2 states of Azerbaijan existing - one is a newly formed Iranian part, and the other is not represented Soviet part.
In-game mechanics... favors the de-facto independent Azerbaijan to return it's territories. Even if you sphere it and install communism (by force if necessary). You get crisis, upset relations and such.
Lets face it: USSR wouldn't really give up the Azerbaijan Soviet Socialistic Republic. It would instead incorporate the new Azerbaijan - in a manner it happened with Western Ukraine and Western Belarus in 1939, after Molotov-Ribbentrop pact, "reuniting" the countries under Soviet banner.

A point I would like to add is however unlike what happened in Poland when it lost territory to Belarus and Ukraine, Iran is likely to maintain claims over those areas as it was not a puppet of the USSR unlike Poland which have claims to Kresy as it was at that time a satellite of the USSR. If the USSR still collapses in 1991 as in real life and the Nagarno Karabakh War still happens Azerbaijan could face a two front war between Iran and Armenia causing massive problems for Azerbaijan and possibly setting the stage for Iranian Irredentistism.


[Infineon]Add All-Clusters example app for P6 platform

Problem
Add all-clusters example app for Infineon P6 platform
Add LWIP Stable-2.1.X branch for P6 compile
Change overview

Added Infineon P6 All-clusters app files

Added Infineon P6 CI workflow support and app to vscode.json

Added LWIP Stable 2.1.X branch as git submodule for P6 compile

src/inet/IPAddress.cpp change required as latest LWIP has other variables in structure ip6_addr

Below file changes to address compile error like
../../examples/all-clusters-app/p6/third_party/connectedhomeip/src/app/util/util.cpp:423:27: error: format '%x' expects
argument of type 'unsigned int', but argument 4 has type 'chip::CommandId' {aka 'long unsigned int'} [-Werror=format=]
src/app/clusters/barrier-control-server/barrier-control-server.cpp
src/app/clusters/door-lock-server/door-lock-server-core.cpp
src/app/util/util.cpp

this is seen with other platform like EFR32 if we compile lock app (and link all-clusters-common instead of lock-common)

Testing
Build and run examples manually
Logs for all-Clusters P6 app commissioning using CHIPTOOL attached
All_Clusters_P6LOG.txt

@praveenCY Is the .bss increase for lock-app expected?

@praveenCY Is the .bss increase for lock-app expected?

Yes.. We have updated lwipopts.h to use different PBUF_POOL_SIZE size and this is the reason for increase in BSS size

Fast tracking, given platform vendor adding tests to their own platform.
@praveenCY Can you fix the conflicts please?


⚠ Bofrost.es has degraded performance

In 2ad2774, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1414 ms

Resolved: Bofrost.es performance has improved in f649550 after 6 minutes.