Authentication in 1.2.1

When I upgraded to v1.2.1 my accessories/devices disappeared.  I checked my config over and over and all appeared good.  I rebuild by Raspberry PI and re-installed HomeBridge and the Tuya plugin, manually configured, only to have the same error:
[28/06/2021, 22:30:38] Loaded 0 cached accessories from cachedAccessories.0E6940212586.
Preparing Advertiser for 'TuyaPlatform C4A3' using bonjour-hap backend!
Initializing TuyaPlatform...
TuyaOpenAPI request: method = post, endpoint = https://openapi.tuyaeu.com, path = /v1.0/iot-01/associated-users/actions/authorized-login, params = null, body = {"country_code":61,"username":"XXXXX@gmail.com","password":"XXXXX","schema":"tuyaSmart"}, headers = {"t":"XXXXX","client_id":"XXXXX","nonce":"XXXXX","Signature-Headers":"client_id","sign":"XXXXX","sign_method":"HMAC-SHA256","access_token":"","lang":"en","dev_lang":"javascript","dev_channel":"homebridge","devVersion":"1.2.1"}
Starting to advertise 'TuyaPlatform C4A3' using bonjour-hap backend!
[28/06/2021, 22:30:38] Homebridge v1.3.4 (TuyaPlatform) is running on port 56345.
TuyaOpenAPI response: {"code":1004,"msg":"sign invalid","success":false,"t":1624883439708} path = /v1.0/iot-01/associated-users/actions/authorized-login
Please confirm that the Access ID and Access Secret of the Smart Home PaaS project you are using were created after May 25, 2021.
Please linked devices by using Tuya Smart or Smart Life app in your cloud project.
Failed to get device information. Please check if the config.json is correct.
So I decided to downgrade to v1.2.0 which was the last know config that worked without issue.
Using the same config parameters no issue - suggestive there is a bug in v1.2.1 around authentication.

Hi @Garth18 ,Sorry for the late reply.
Recently, our team has been sorting out interface codeNumber issues.
Hope this doc has been helpful: https://developer.tuya.com/en/docs/iot/Tuya_Homebridge_Plugin?id=Kamcldj76lhzt

I had exactly the same issue so rolled back to 1.2.1.  Thanks for the update on things @Hanh94 !

Hi @Garth18 @Daveblanche , Thanks for your feedback. We have adopted a new signature method in 1.2.1.
Please provide the latest error log for version 1.2.1, Thanks

Hi @Daveblanche @Garth18 , Please try again.

Done. Seems ok so far. I have lights!
Thanks guys.
Sent from my iPhone

On 2 Jul 2021, at 9:55 am, Hanh94 @.***> wrote:

Hi @Daveblanche @Garth18 , Please try again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Updated Contents

Why are changing the character count?
You need to have a design master to oversee your layout changes if you want them approved.
You are not yet trained nor authorized to change our character counts.
Move very slowly on this over the next few months as I do agree you probably need to add more text, but you cannot just submit changes without a design master working alongside you to ensure you're not breaking the elements in a Responsive environment.

I'm reverting it now.


Complete Tutorial on adding remark command

Create a PR from my fork to my team's repo.

Codecov Report

Merging #1 (c38f389) into master (f1ec2d7) will increase coverage by 1.03%.
The diff coverage is 89.33%.

@@             Coverage Diff              @@
##             master       #1      +/-   ##
============================================
+ Coverage     72.15%   73.19%   +1.03%
- Complexity      399      423      +24
============================================
  Files            70       73       +3
  Lines          1232     1287      +55
  Branches        125      131       +6
============================================
+ Hits            889      942      +53
- Misses          311      313       +2
  Partials         32       32

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
25.00% <14.28%> (+5.00%)
:arrow_up:

...c/main/java/seedu/address/model/person/Remark.java
87.50% <87.50%> (ø)

...java/seedu/address/logic/commands/EditCommand.java
97.05% <100.00%> (+0.04%)
:arrow_up:

...va/seedu/address/logic/commands/RemarkCommand.java
100.00% <100.00%> (ø)

...a/seedu/address/logic/parser/AddCommandParser.java
100.00% <100.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
100.00% <100.00%> (ø)

...ain/java/seedu/address/logic/parser/CliSyntax.java
85.71% <100.00%> (+2.38%)
:arrow_up:

...eedu/address/logic/parser/RemarkCommandParser.java
100.00% <100.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
97.77% <100.00%> (+0.15%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


No RomFS folder when mounting CCI of Captain Toad: Treasure Tracker (Europe and Japan)

fuse-3ds v1.2b3 windows 32bit. I don't get any errors in the command line window. They work with other tools.
The MD5 of the Europe CCI is 7850923CAE79964A3828938C05BBC54C and the MD5 of the Japan CCI is<PHONE_NUMBER>CCB36ED03830994B77C255.
You can PM me [on GBATemp]
(https://gbatemp.net/members/hiccup.230145/) about this if you want.

already fixed in 2387f44ce1ee43bd1bdff3118231ca7fe10fe75b

Thanks. Do you also have a 64-bit build?

32-bit was uploaded since you only mentioned 32-bit, but here: fuse-3ds-1.2b4.dev1-win64.zip


"Cannot read property 'sign_url' of null" error appears at Preparing CLA page on ICLA sign up

Steps :

Login PCC with valid credentials
Go to easyCla GitLab page
Connect GitLab groups
Create PR on projects, See-PR is gated & Missing on Commit button appears
Now click on Missing on Commit button
click on "Proceed as an Individual Contributor" options
See-Preparing CLA...page open & Sign CLA button remain disabled

Actual results :  Sign CLA button remain disabled & "Cannot read property 'sign_url' of null" error appears at console
main-es2015.397d93475eda22ddbe09.js:1 ERROR TypeError: Cannot read property 'sign_url' of null
    at f._next (main-es2015.397d93475eda22ddbe09.js:1)
    at f.__tryOrUnsub (main-es2015.397d93475eda22ddbe09.js:1)
    at f.next (main-es2015.397d93475eda22ddbe09.js:1)
    at g._next (main-es2015.397d93475eda22ddbe09.js:1)
    at g.next (main-es2015.397d93475eda22ddbe09.js:1)
    at F._next (main-es2015.397d93475eda22ddbe09.js:1)
    at F.next (main-es2015.397d93475eda22ddbe09.js:1)
    at Ou._next (main-es2015.397d93475eda22ddbe09.js:1)
    at Ou.next (main-es2015.397d93475eda22ddbe09.js:1)
    at W.notifyNext (main-es2015.397d93475eda22ddbe09.js:1)

https://images.zenhubusercontent.com/194341141/80f94e3e-d619-4857-9508-1a4d4ddc7049/gitlabicla.mp4

@thakurveerendras. Resolved this. Kindly verify

Issue is tested on dev site & found that reported console error issue is not reproducible, So making issue status QA-Done
https://images.zenhubusercontent.com/194341141/d7b6ae73-20c4-4a5d-b099-c44f5a727808/singcla_gitlab.mp4


Add cube-helix support

https://www.mrao.cam.ac.uk/~dag/CUBEHELIX/
http://bl.ocks.org/mbostock/11415064
http://gka.github.io/chroma.js/#chroma-cubehelix
cc @makella

Added in v0.21 for sequential scales, need to figure out how to add it to divergent scales. We may also need to look for the way to fine tune it.


problem.md text/grammar updates

I noticed some grammar issues and other minor text issues while running through the Expressworks workshop. Suggestions committed. These changes are for the English problem descriptions. I can't help with the Korean, French, or Simplified Chinese translations unfortunately.

Great, although I think an SHA is correct when you pronounce it letter by letter and a is correct when you pronounce it as one syllable /sha/

:+1:

Thanks - I agree, when SHA is pronounced as an initialism, it should be an SHA. I couldn't find a definitive source that prescribes a pronunciation, so I used what I hear in US English. It may be pronounced differently in other areas. :v:


Cannot open

Both buttons only close the window

Thank you for letting me know. It should be fixed now in the latest release.


foam duplicates reagents

Description
if you have a 100u reagent foam each foam entity has a copy of the 100u so you get extreme multiplication
its not either shared between each foam entity or evenly divided like explosion intensity for example

I haven't looked at the code in a long while, but I was under the impression the last fix that was added for this prevented you getting more than the 100u dose even if you enter multiple tiles. I guess you could still vomit-factory it, but it would at least be more work and doesn't overload the chemstream with 1 morbillion u if you're on more than one tile any more.

vomiting only giving 10% of reagents fixed vomit duping but the foam inherently creates more than was put in


fix kafka token-refreshing error with Azure identity support

Description
Resolves issue https://github.com/Azure/azure-sdk-for-java/issues/30719.
The root cause of the issue that KafkaOAuth2AuthenticateCallbackHandler cannot work with Kafka's ExpiringCredentialRefreshingLogin is that: Kafka's token-refreshing mechanism expects to fetch a new token object every time it performs the relogin operation, thus it will delete the old login context as well as the old token after each refreshing try.
However, for Azure AD, it doesn't work in that way: Azure AD will only return a new token when the current one gets expired, otherwise it will return the existing one for each request. Thus the KafkaOAuth2AuthenticateCallbackHandler used to follow Azure AD's pattern and cached a token locally, which violates with the design of Kafka.
To fix this, we will cancel the cache in the callback handler and hand over it to the underlying azure-identity implementation, thus we will return a new token object per kafka's refreshing call.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

When can we expect new release with this fix?

@mkrzywanski we plan to get this released in September


Failing regex left match in Jayway engine

Sample input:
{
  "image": "a",
  "image2": "b",
  "image3": "c",
  "image4": "d",
  "image5": "e"
}

JsonPath expression: $.[?(@ =~ /image*/)]
Expected output:
[
  "a",
  "b",
  "c",
  "d",
  "e"
]

This works with https://jsonpath.com/ 's evaluator but not with Jayway JsonPath :|

duplicate of #348

oops, closing then, sorry. Hope it gets fixed soon!

Hope it gets fixed soon!

don't wanna frustrate you but the original ticket is open since 2017...

#ohwell 😅 I thought the whole point of applying JsonPath is to write incredibly compact oneliners doing all the heavy lifting..

It certainly is but seems like not for all use cases ;)


Added build datetime to context

Useful to know when the docs were last built. Datetime format can be controlled in the template like so:
{{ build_date.strftime('%Y-%m-%d') }}

Okay, let's hold off on this for now. It might make sense to do this when we document and formalise the context that we pass to themes.

Incidentally "current year" usage has slightly made me consider this one again, but even so still not a priority so I'd still suggest focusing on core stuff until we're at 1.0. Anything that doesn't fall into that category is a distraction.


Use test builder.

This change introduces the builder pattern to the Marathon unit tests in order to simplify and reduce the amount of testing boilerplate.
Additional changes:

Add missing unit tests.
Make all tests look consistent.
Use dedicated type for task states for increased type safety.
Remove obsoleted getApplication function.

Note: I pushed the branch to the containous repo because I intend to submit another PR based onto this one.
@containous/marathon @containous/traefik PTAL.

/cc @marco-jantke happy to have your review too. :-)

@marco-jantke all comments addressed.

@timoreimann could you fix the linting?
Errors from golint:
provider/marathon/marathon.go:31:6: exported type TaskState should have comment or be unexported

@ldez should be good now.

Re: backend/frontend refactoring: I'd like to leave that for a separate PR as this one is already fairly big. Plus, we need to "builderize" the configuration in numerous places (server, kubernetes, etc.), so I'd rather do it in one focused wash (which will also make it easier to see how we need to design that builder).

Rebased and addressed all comments for now.
PTAL again.

I only added the prefix because I understood you asked for it. Will happily remove it again in another PR. :-)


Some tests fail using perl 5.22

http://bugs.debian.org/796944
After upgrading to perl 5.22 some tests from the test suite are failing (see issue above). A few of them could be solved by a patch from Gregor Hermann[1], but not all. Please be so kind to look at this. Instructions how to setup perl 5.22 on Debian can be found in the issue.
Hilmar
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796944;att=1;msg=40;filename=fix-perl-regex-braces

Are you testing the DEV branch? This should already be fixed.

Works in dev branch. Do you have a release date for biber 2.2 or could you provide a patch? Thanks!

Will be in September I think. You can always just use git and make a patch against the master branch?
PK

On 28 Aug 2015, at 12:27 pm, hpreusse<EMAIL_ADDRESS>wrote:
Works in dev branch. Do you have a release date for biber 2.2 or could you provide a patch? Thanks!
—
Reply to this email directly or view it on GitHub.

--
Dr Philip Kime

Commit fe8fe2df01c507392983d5c81e5d04406ba6cec0 solves the problem. Sorry for the noise!


chore(Analysis/Normed/Group): Move boundedness lemmas

Split a new file Analysis.Normed.Group.Bounded off Analysis.Normed.Group.Basic. Basically no imports get shaved off in this PR, but it's preparing the way to #13713.

This can't be merged simultaneously as #13894.

bors d+
(delegating because I am not sure this is ready to go since #13894 is merged)

Oh, I've already fixed the conflicts.
bors merge


clean up workflows to have successive steps

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:
Update the workflows to have successful steps
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

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

After a discussion with @cpanato we prefer to keep things as they are


Enhancement to Mac pList options

nw-builder allowed more general plist options in its build process, and since switching to this project, I have a need to customize the LSUIPresentationMode key with a non-default integer value in my app, but cannot do so without manually doing it after the built is completed.
Is there any way you can add a generic default options object with just key: value combinations?

Fixed in nwjs-builder-phoenix 1.12.0.
You should be able to do this by modifying build.mac.plistStrings. See the sample project and Options for more information.

Can you give an example of how CFBundleDocumentTypes would work? How would I use the config option in the plist to generate this in the target plist file
	<key>CFBundleDocumentTypes</key>
	<array>
        <dict>
            <key>CFBundleTypeName</key>
            <string>Document</string>
            <key>CFBundleTypeRole</key>
            <string>Viewer</string>
            <key>LSHandlerRank</key>
            <string>Owner</string>
            <key>LSItemContentTypes</key>
            <array>
                <string>com.adobe.pdf</string>
                <string>org.idpf.epub-container</string>
                <string>org.idpf.epub-folder</string>
                <string>com.apple.ibooks.epub</string>
            </array>
        </dict>
    </array>


not working in slack rss feed

I added the rss feed by slack command below
/feed subscribe https://jamesg.blog/hf-papers.xml

But nothing happens during several days.
As far as I know one of recent posts should be pop up instantly in the slack channel when the feed is added if the subscription is valid.
I noticed that the <author> element is invalid. See following address

https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fjamesg.blog%2Fhf-papers.xml

Or could anyone explain how to fix it?

Hello there! I will take a look to see what's going on and report back here.

The missing author shouldn't stop feeds from being able to subscribe. Can you try to re-subscribe and see what happens? I pushed a change today that fixes a few things.

Sorry for late response.
It still not work.
I tried it with other rss reader and it was successful.
So this may be an integration issue with slack.
RSS app is provided by slack team so I can't see any logs.
According to the guide they suggest to use validator if you got an error.
So I attach the validation error link

After the update in #4 I got the Slack feed reader to work. @zsaladin Can you check on your end? If it works, I think we can close this issue as resolved 🙂

@isnbh0
It's working now!! Thank you for the contribution!!!


Roche Cobas Multi-Swab Support

WHY?
The Roche Cobas super long name COVID test supports 3 different types of swabs. We would like users to be able to set the correct default swab type
AS A user of SimpleReport
I WANT the ability to set the default swab type for the Roche Cobas test
SO THAT the data can be captured and eventually sent along to report stream
GIVEN I have added a device for a facility or am in the process of adding a device and that device is Roche Cobas test
WHEN I have selected 'Roche Cobas' as the device
THEN the 'Sample type' [need to check with content on this] dropdown is populated with the following options:
Anterior nasal swabs (697989009)
Mid-turbinate nasal swabs (871810001)
Nasopharyngeal swabs (258500001)
AND
WHEN one of these options is selected
THEN the information is saved

@tim-skylight maybe you can fill me in on the swab type name and what it's describing. It might make sense to call this a "Collection method" but I can't say for sure until I understand this part of the process a bit better


Customizable kernel function

This PR introduces a new optional argument kernel to LimeTextExplainer, LimeImageExplainer, LimeTabularExplainer and RecurrentTabularExplainer. It represents the similarity kernel that takes euclidean distances and kernel width as input and outputs weights in range (0,1). If None, defaults to the exponential kernel that hardcoded in the code base as before. This should not result in any breaking changes.
In https://github.com/marcotcr/lime/issues/185#issuecomment-390373369 the maintainer mentions the choice for the kernel was a bit arbitrary. It would be nice to be able to explore the effect of different kernels on the explanations.

Thanks for the PR.
This is obviously a simple change that won't break anything, but I wonder if we need to provide this option. Would anyone use it? Have you found any situation where using a different kernel mattered?

In this paper, the author shows that he can only guarantee some desirable properties by choosing very specific loss function, complexity penalty and similarity kernel. In that case the choice of kernel does matter. I am not sure what impact the similarity kernel has on the explanation, but for exactly that purpose it would be nice to enable devs/researchers to play around with it. That being said, I realise this change is quite niche, so I would understand if you rather keep this a separate fork :)

You make a good point with Scott's paper.
Thanks,


[Feature] Setup SMTP server for Contact Us section

Description
I would like to add an SMTP endpoint to the Contact Us section.
Outcomes :

The information will be diverted to the user's email address directly upon Button Click.
Removing the Database complexities like storing the Contact Form Data in a database.
This will result a safe and secure information exchange without involvement of any third part software or a database

Implementation :

I will be creating an SMTP server using NodeJs and connect user requests to the backend. This will send mails to the owner of the repository.
SMTP server of GMAIL will be used for safe and secure information exchange.

Would be glad if you'd assign me this issue. @rohansx Thanks 😄
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@pooranjoyb ok go ahead


Adds SSM support in the README

Coverage remained the same at 93.723% when pulling e344a7e95bb15a52b1049138b7253f563a47c108 on mosampaio:master into b54ef0961f1171a64a51dc4721e4c3e69545f4ea on spulec:master.

Nice! Thank you


Fixed maven publishing

The publishing process of the gradle plugin changed.
I fixed the modules.
You need to publish the modules separatly like this:
./gradlew :flower-core:publish
./gradlew :flower-retrofit:publish
./gradlew :flower-ktorfit:publish

I've already tested it (under my repository) and the packages are available like this:
implementation("dev.datlag.flower-ktorfit:flower-core:3.0.0-beta02")
implementation("dev.datlag.flower-ktorfit:flower-retrofit:3.0.0-beta02")
implementation("dev.datlag.flower-ktorfit:flower-ktorfit:3.0.0-beta02")

Of course you only need either the Retrofit package or the Ktorfit package.
The core module is referenced and available in these.

Thanks @DATL4G. Appreciate quick pull requests.
I'm merging this request but have some more plans before publishing it.
Also, I'm new to multi-platform and will need your help to understand few things.
Is there any way to quickly connect with you? Like telegram? twitter?

Sure contact me on Twitter same username (@DatL4g)


CASSANDRA-17210: Remove unused port parameter from sstableloader documentation

The sstableloader documentation states that the native transport port can be specified using the --port parameter, but this parameter is not actually used in the code. The intended effect is achieved by specifying the port on the host address instead, which this PR intends to clarify.

this issue was solved, see ticket for CASSANDRA-17210.


grpc-device should convert string encoding to/from UTF-8 when necessary

Protocol Buffers requires strings to be encoded as UTF-8. However, many of the NI driver APIs supported by grpc-device use the Windows current ANSI code page, which is typically a single-byte encoding like ISO-8859-1 or a multi-byte encoding like Shift JIS.
NI driver APIs typically support internationalization for:

User-defined names, such as device aliases, DAQmx global channel names, and DAQmx task names
File paths
Localized error messages
Serialized configuration data for import/export

I haven't tested internationalization with grpc-device, but I would expect these results:

Sending strings that are not structurally valid UTF-8 may result in errors or coerced string contents.
Sending or receiving strings in languages that natively support Unicode (like C# and Python3) may result in mojibake.

Driver APIs:

DAQmx: nicaiu.dll uses ANSI/MBCS. nicai_utf8.dll uses UTF-8, but requires a different import library than the one that is checked into imports\lib\win64.
MI, RF, XNET I think these all use ANSI/MBCS.

Exception: The MI ImportAttributeConfigurationBuffer and ExportAttributeConfigurationBuffer functions pass an array of bytes containing a UTF-8 JSON string. Related issue: https://github.com/ni/grpc-device/issues/694

AB#2108036

Related, the test QuotedLocalizedDescription_ApiErrorAndDescriptionToStatus_MessageIsEncoded is not behaving in a sufficiently predictable way that meets everyone's expectations. While I'm baffled by the nuances of non-ANSI characters in C string constants, @bkeryan and Ben Craig are not convinced the code is doing anything to encode the characters.

Brad thought the constant std::string("\"chaîne localisée 😀\"") in MSVC would issue a code page warning, but I can confirm it does not.
I tried making the constant explicitly specify u8 encoding, but Ben pointed out that code would cease to compile when we move to a newer C++ standard.
I tried keeping a "normal" C string and using explicit Unicode characters std::string("\"cha\u00EEne localis\u00E9e\U0001F600\"") but that causes 2 problems:

Compiling: warning C4566: character represented by universal-ch aracter-name '\U0001F600' cannot be represented in the current code page (1252)
Running: C++ exception with description "[json.exception.type_error.316] invalid UTF-8 byte at index 5: 0x6E" thrown in the test body

The last part is the most concerning to me, as I would expect either inserting into the JSON object or stringifying it would take care of the encoding, but it doesn't seem to be the case. This likely needs to be addressed as part of solving this problem.

Long story short, MSVC has two character sets: source and execution. It uses the source character set to read the .cpp file and it uses the execution character set to write string constants to .obj files. By default, both character sets are ANSI. If you want to specify UTF-8 string constants using UTF-8 source code, you should set both character sets to UTF-8.

Brad thought the constant std::string(""chaîne localisée 😀"") in MSVC would issue a code page warning, but I can confirm it does not.

It depends on the code page and the character values. Some sequences of Windows-1252 (Latin-1) characters or UTF-8 bytes are not valid Windows-932 (simplified Chinese) byte sequences. Depending on the characters used, this may generate warnings when compiling with a Chinese locale.

Compiling: warning C4566: character represented by universal-ch aracter-name '\U0001F600' cannot be represented in the current code page (1252)

This confirms that the execution character set is Windows-1252. This code page cannot represent emoji.

Running: C++ exception with description "[json.exception.type_error.316] invalid UTF-8 byte at index 5: 0x6E" thrown in the test body

MSVC converted \u00EE to the Windows-1252 representation of 'î' and the resulting Windows-1252 byte sequence is not a valid UTF-8 byte sequence.
u8"\u00EE" would work, except for the C++20 changes.
"\xC3\xAE" should work regardless of source/execution encodings or language standard.

@bkeryan , are you good with marking this Issue closed? I'm good with the changes in the PR + tests that ran and the additional issue David made to capture using the additional work to use the better suited DAQmx DLL.
But you're more of the expert with this issue so wanted to check with you to see if you're good with closing it too.

I finally got back to this and it seems to work ok, at least for NI-DCPower.


OCPBUGS-11939: Fix minor codebase nits

What this PR does / why we need it:
Fixed minor codebase nits such as typos, deprecated methods, unused parameters, catch errors, etc. found along the way during development on OCPBUGS-11939.
Which issue(s) this PR fixes
Minor codebase cleanup as part of work on OCPBUGS-11939.
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
N/A This change includes docs.
N/A This change includes unit tests.

/area hypershift-operator
/area control-plane-operator

Thanks!
/test unit
/approve
/lgtm

/cherry-pick release-4.13


Some weird border radiuses on context menu items

I found that when right clicking the user settings button and opening its context menu, the second to last item had a weird border and the last item didn't have border radius. Here's some screenshots for better understanding:

I would fix it myself and make a pull request but I'm kinda dum hah

Fixed.


data preprocessing for lidar

Hi, I am very interested in your great work.
Could you share the script of data preprocessing in argoverse v2 dataset, especially with the point cloud processing.
Thanks in advance.

Hi, we followed the official repository of av2-api for data preprocessing. FYI only, I also uploaded our implemented preprocessing scripts here.
(Note that I currently do not have access to the raw data of the argoverse2 dataset since I have left the internship institution and the raw data is stored in their server. The uploaded scripts are my personal backup.)

Thanks very much.


super if defined? super

/bundle/ruby/3.0.0/bundler/gems/filewatcher-spinner-9246172e955e/lib/filewatcher/spinner.rb:27:in `before_pause_sleep': super: no superclass method `before_pause_sleep' for #<Filewatcher:0x0000aaaaf3de3a70 @unexpanded_filenames="d2/src/**/*.{js,ts,tsx}", @unexpanded_excluded_filenames="d2/src/queries/*.*", @keep_watching=true, @pausing=true, @immediate=nil, @interval=1, @logger=#<Logger:0x0000aaaaf3de39f8 @level=1, @progname=nil, @default_formatter=#<Logger::Formatter:0x0000aaaaf3de3908 @datetime_format=nil>, @formatter=nil, @logdev=#<Logger::LogDevice:0x0000aaaaf3de37c8 @shift_period_suffix=nil, @shift_size=nil, @shift_age=nil, @filename=nil, @dev=#<IO:<STDOUT>>, @binmode=false, @mon_data=#<Monitor:0x0000aaaaf3de3750>, @mon_data_owner_object_id=13480>>, @show_spinner=true, @on_update=#<Proc:0x0000aaaaf3de2f08 d2/scripts/update-graphql-schema.rb:217>, @last_snapshot=#<Filewatcher::Snapshot:0x0000aaaaf6d554c0 @data={"/vydia/d2/src/@types/react-suspender.d.ts"=>#<Filewatcher::Snapshot::SnapshotFile:13520 (NoMethodError)
...
...
Did you mean?  before_pausing_sleep
               before_resume_sleep
	from /bundle/ruby/3.0.0/gems/filewatcher-2.0.0.beta5/lib/filewatcher.rb:109:in `before_pause_sleep'
	from /bundle/ruby/3.0.0/gems/filewatcher-2.0.0.beta5/lib/filewatcher.rb:58:in `pause'

Can you provide some test?
I guess you're using this gem with old version of filewatcher. It's for a new one, 2.0, which is currently in beta: https://rubygems.org/gems/filewatcher
So, you can lock your filewatcher gem to something like ~> 2.0.0.beta5 and it should works.

@TSMMark friendly reminder. :wave:

The whole ecosystem has been updated.


Custom services setup

Right now it's only possible for the user to install a complete setup like Staking-Node or Blox SSV Operator. Users should be able to:

[ ] #499
[ ] #500
[ ] #501
[ ] #502

@daGscheid please provide some UI draft for this

I can approach writing everything I have on my mind out in multiple ways, I try to cover as much as possible.
So the basic logic of the pages is the following:
On the node page as well as the control page you are capable of using the services, edit their configuration, start and stop them and update them.
The "EDIT NODE PAGE" is used to setup the node itself.  This where the custom services magic happens, so entering it, you are greeted with a way to customize the components your node is made out of.  In my example this is empty and we are operating on the "Ethereum mainnet" (we aren't really, but ignore that haha)

There some basic rules when it comes to custom installation with this page. Making a change to the node is usually confirmed by pressing the giant confirm button on the right side, which will que tasks into the task manager.
Every change to be confirmed is listed in the que like list on the right.
Having it sorted is probably a smart idea.
I suggest this basic logic for the custom installation task que (visually at least):

REMOVING BEFORE ADDING

WHEN ADDING:

Execution
before

Consensus
before
Validator Client
before
services

Basic functionality:

#500 adding services

PATH 1# DRAG & DROP
https://user-images.githubusercontent.com/82385103/178147779-4777b30f-5280-41bc-8815-707a364e6a37.mp4

PATH 2# CHOOSE FROM LIST

The current display being changed in the Node Edit Tab to present all choices for the category to add to the Node

MENTIONS:

[ ] Selected to install items (but not yet installed) should have around 30% transparency
[ ] To remove a selected item from the custom installation que just drag it into the delete section / trash can or click the item on the custom installation task que on the right. (To remove an installed service refer to #502 explanation on this page)

#502 removing services

https://user-images.githubusercontent.com/82385103/178148597-d5f1b4a0-15cd-4123-a018-c1a6a2c96b3c.mp4
There is only one path currently to remove. It is by clicking the item in the middle and then clicking remove. While I would like to keep this way generally - clicking once selecting service - using this logic for #501 (a little below)
We should build the custom installation up to be also capable of using drag and drop. Dropping the items from the middle onto the trash can icon or at least onto the task que.

#501 modify services

Currently I would like to tackle #501 in combination with a similar UI solution present in #407.
FOR REFERENCE (solution currently worked on for #407)

How this looks like exactly I will follow up with when I get better grasp on how we can present the changes made to node and when editing them will/can take effect.


Disable push teardown on Content Management workflow (BROKEN)

Also includes several minor changes:

Change debug truthy var to "1" vs "true"
Add constants for env vars like OCI_ROOT_URL
Ensure all OCI_ vars are displayed in HTML report
Update README to reflect new workflow env vars

Resolves #141.
Resolves #140.

some unsolvable git signoff error in merge commit... going to reopen this

github state's been a mess of late.. sometimes you just have to do a de minimus change to the commit description and force push it to reset
otherwise ... I use the -s option on commits makes it easy to sign these things.


Updated the README.md to show all available tutorials and have links to them directly

1. This pull request resolves #63
2. Description
Updated the README.md to show all available tutorials and have links to go directly to the corresponding tutorials.
3. Fill in checklist by marking [x]

[x] I've read the CONTRIBUTING.md
[x] I was assigned to this issue
[x] My code is formatted using required linting
[x] I've run my code locally and checked it works

Merged ⭐


Select - fix size of select

Description / User Story
The following differences were found when comparing the Select in Storybook with the Select in Design:

Size

SM: Height in code is 18.5 px, in design it is 16px
Size in pressed state increases 1px to each side in code (ie when pressing the icon), but not in design

Border

Border in code is applied out side of the select, in design it is applied inside the defined size

Acceptance Criteria

[ ] The Select field has the same size in SM in code as in design (16px)
[ ] The Select field size does not change in pressed state in code
[x] In case props were changed: Props Excel has been updated / comments have been resolved and props changed from red to black font color > @thrbnhrtmnn or @angelicahoyss can support here

Background information

...

Review findings @ashk1996 :

I think the height of the input field in SM is still not correct. In code the inner container has a height of 18 px, but it should be 16 px according to design. In total the height should be 32 px, but it is currently 34 px.
The outline adds another 1 px in all directions, whereas the border in design is part of the input field height/widht. This occurs for all sizes, not only in SM.
In pressed state the border now does not increase the size anymore, but it has the wrong color token (should be sem/forms/inputfield/container/bordercolor/default/pressed, which is hsla(220, 10%, 70%, 1)).
The focus state still increases the size of the component by 1 px in each direction, but this could also be solved via another issue, as this was not part of the scope initially

Hey @larserbach , I think we need your support on this topic, maybe we can have a quick sync next week.
As I see it, borders in Figma can be applied "inside", "outside" and "centered". This design decision however is currently not saved within a design token.
Also the behaviour of borders seems to be different in Figma in that regard, that a border is not increasing the size of a container, whereas in code it does. This means, that we would need to implement a logic in code that reduces i.e. padding by 1 px if the border is applied "inside" the padding in design or that it would use an outline instead of a border.

As just discussed this ticket now can get approved and be merged. We fixed most issues, the only misalignment between design and code currently is that in design the border is applied inside, and in code it is applied outside (as an outline which does not increase the component size though).
After a sync with @larserbach about this we should decide if we need a follow up task to fix this misalignment as well.


Make linting work again with elm-analyse 0.14.2

Solves #184
The communication is now updated to the new message format. Because it provides the description so the hardcoded message description list got removed. Also it does not stop anymore on the first parsing error and gives a list of all message parsing errors. The errors gives a hint that we expect at least the version 0.14.2.
For everyone with an old elm-analyse version this box will be shown to the user in the bottom right corner:

If the message format changes again this thing will come too.
One thing what i noticed: The description provided by the message format contains the line and column numbers which are lower by 1 compared to the numbers in vscode.

I fixed the line and colum numbers in the description. Regex was not neccessary, because i know already all the regions.
In the second screenshot are no real duplicates.
This is the elm text which generates the RedefineVariable warning:
newCurveSegmentList : Int -> ( BuildCurveSegmentState, List Segment ) -> ( BuildCurveSegmentState, List Segment )
newCurveSegmentList _ ( state, segmentList ) =
    case newCurveSegment ( state, Nothing ) of
        ( state, Nothing ) ->
            ( state, segmentList )

        ( state, Just newSegment ) ->
            ( state, segmentList ++ [ newSegment ] )

These are the two original messages by elm-analyse:
Variable `state` is redefined at ((417,36),(417,41)) and ((419,22),(419,27))
Variable `state` is redefined at ((417,36),(417,41)) and ((422,22),(422,27))

I needed to duplicate them, so i can click between the two points. In this case the state function parameter is in conflict with two other definitions. Two different warnings hit the same range. I think the like a duplicate looking warnings are not possible to get filtered out.
Maybe the left and right side should be splitted to two different warnings. One says, that it will be redefined later and one that it redefines an existing definition. Redefine seems to be a special case.

Amazing, thanks a lot. Duplication makes sense in this case, indeed.


Portals Infnite Loop

When you link nether portals for example
world to nether
and
nether to world
You get stuck in a infinite loop
until you unlink 1 of the  worlds or someone force a /tphere
Spigot 1.9.4
Nether-Portals build 712
Core build 722

I have the same problem, just I don't link world with the command, I just rename them to world_nether but when anyone enter in a portal, the loading time inventory lets the player in the portal and when the inventory is loaded, the portal teleports the player again to the other dimension.

I think this craftbukkit commit can do something about it.
https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/ae93d4fb492bc737466666087dcd49c9f775e40c

Yes, That fixed it, i had already that commit but didnt notice until your comment... i'll close this now.
Thanks!


[CONTINT-4335] Add ECS agent version to agent flare

What does this PR do?

https://datadoghq.atlassian.net/browse/CONTINT-4335
Adds the ECS Metadata to the agent flare in a new file ecs_metadata.json. If not running on ECS, this file is not created. The only information present is the ECS Agent Version and ECS Cluster Name.
Motivation
The ECS Agent Version would be useful for debugging support tickets.

Additional Notes

Not sure if this change should have a release note. Primarily something that would be used by support and not customers, but let me know if one should be added in.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Start up an ECS cluster and deploy the agent (image must be amd64 architecture)
Check the ECS Agent Version

aws ecs describe-container-instances --cluster <cluster name> --container-instances <cluster instance>

Exec into the agent task

aws ecs execute-command \ --cluster <cluster name> \ --task <task id> \ --container datadog-agent \ --interactive \ --command "/bin/bash"

Call agent flare
Unzip the flare and check that ecs_metadata.json is created and verify the ECS agent version is present and the same as what was previously found

Additional QA:

Deploy the agent on a kind cluster
Exec into the agent and call agent flare
Unzip the flare and verify that ecs_metadata.json is not created

/merge


Frontend Badge does not respect Home Zone Friendly Name

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.59.2
Python release (python3 --version):
Python 3.5.3
Component/platform:
Zone / Device-State / Badge on Frontend
Description of problem:

Left: Device that has been discovered by router
Middle: Device currently not seen by router or other tracker
Right: Tile Device (non-home zone found via gps, text supplied by customize.yaml friendly name override)
I have multiple zones set up, including overriding my home zone to be somewhere else so that I could name my actual home Camelot. Obviously this is not ideal, but was the only way I could see to get it on the frontend. Recently I set up a device tracker (unifi direct) for my router, and it started overriding all my devices' states to be Home or Away, instead of respecting the zones I set up.
That is a different bug that I could file (add zone as an optional parameter for device_trackers) if you would like, but I figured that was a very advanced use case.
Expected:
Friendly Name of zone.home respected like other zones
Problem-relevant configuration.yaml entries and steps to reproduce:
I don't have great steps to reproduce, but the gist is have the home zone set up, override it with a friendly name (like Castle), and have a device_tracker set up with a device. On the frontend this will (or add it so it will) show up as a badge, and instead of Castle as the label, it will show Home.
Traceback (if applicable):
n/a
Additional info:
Irrelevant to problem, but I am on an RPi 3, installed via the virtualenv instructions. I have Unifi Direct and Owntracks HTTP device trackers set up.

FWIW I think that removing lines 530 and 531 in the device_tracker would solve the problem
https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/device_tracker/__init__.py#L530

I updated to the latest HA, and this issue is still happening..


VMware guest customizations fail due to lack of perl

Hi all, not sure what (if anything) can be done due to the circumstances, but here goes:
I've been using the vmware-desktop boxes, extracting them, and importing them into vSphere for use with Terraform. The Ubuntu boxes work correctly, but I tried doing the same with CentOS but it failed the guest customization. The logs show it failed because perl is required but is removed by Packer after the guest tools are installed. I booted up the template, installed perl, and guest customizations are now succeeding.
I guess since these boxes are created for use in Vagrant (and by extension specifically the vmware-desktop driver) making them compatible with ESXi is out of scope, but just thought I'd bring this up and get some feedback from you.

Makes sense to leave behind Perl for VMware


Enable contracts.updateSchedule

Some methods were remove from Contracts pallets. Verifying in https://polkadot.js.org/, you find the same result.
The only methods that are included in Contracts are: call, instantiate and instantiate_with_code


bump minio and redis charts and also update the spinnaker version

What this PR does / why we need it:
bump minio and redis and also use the latest spinnaker release
the old release of minio set the storageclass which should be commented out. the new release fix that
Which issue this PR fixes: fixes https://github.com/helm/charts/issues/7444
Special notes for your reviewer:
n/a

/approve


chore(value_test): Splitting testvalue_schema test to subtests

This PR splits the TestValue_schema test into multiple subtests to improve readability and maintenance.
This is per issue #385.

Coverage: 95.672%. Remained the same when pulling b197dde6d07d05614a299a67a3896b10b1245fbc on MattSilvaa:mmuniz/subtests-test-value-schema into e6ecc94d891c26835a09f97db494c9a872fcde3b on gavv:master.

Thanks!
PS. Please don't resolve discussion by yourself, this is usually done by reviewer to keep track what still needs re-review and what's not.

Also welcome to discord chat :) https://discord.gg/5SCPCuCWA9

@gavv just joined 😁 Looking forward to contributing more and being active in the channel!


Fix sporadic fail of URIExtractionNamespaceFunctionFactoryTest#testReverseFunction

Currently returned future does not guarantee completion of registered callbacks, which is actually makes functions to be used, causing sporadic failure of testReverseFunction.

LGTM

I don't think the cache updating post-runnable code path needs to be async. I honestly don't remember why I made it that way to begin with. Instead of making a complex workaround to make it partly synchronous, can we just make the post runnable called inside of futureWithString ?

I think @drcrallen would be right. Returning ListenableFuture expecting get() will return value only when all listeners are executed is not possible. I'll revised this.

@xvrl @drcrallen I've moved all logic into single Runnable. I couldn't sure current lock scheme is safe but I've not modified anything on that part.

Test passed. I'll bump few more times to confirm.

Met #2128

Passed. One more time.

:+1:


Possible bug code utils/metric_stats.py

I am using BinaryMetricStats to calcuate eer/threshold, and got following error
  RuntimeError: Tensors must have same number of dimensions: got 1 and 2

It maybe caused by code https://github.com/speechbrain/speechbrain/blob/develop/speechbrain/utils/metric_stats.py#L384
Here, self.labels == 0 gives all the index with 0 elements, but self.labels[self.labels == 0] only gives all the 0 elements
The correct code would be
  positive_scores = self.scores[self.labels.nonzero(as_tuple=True)]
  negative_scores = self.scores[(self.labels == 0).nonzero(as_tuple=True)]

or a more simplified writing should be
  positive_scores = self.scores[(self.labels==1).nonzero(as_tuple=True)]
  negative_scores = self.scores[(self.labels==0).nonzero(as_tuple=True)]

If this is indeed a mistake or a typo, hope you may find this issue helpful and fix it.
Many thanks!

If this is need a bug, I have already created a PR for your approval

Hi @aluminumbox,
thank you for reporting. Fortunately, we are not using it in the EER computation for the voxceleb example (because use directly the eer function). I don't remember where we use the BinaryMetricStats  stats. @popcornell, it looks like you work on it. Could you please take a look?

Hi @aluminumbox, thank you for reporting. Fortunately, we are not using it in the EER computation for the voxceleb example (because use directly the eer function). I don't remember where we use the BinaryMetricStats stats. @popcornell, it looks like you work on it. Could you please take a look?

The bug occurs when using recipe/LibriParty/VAD. In train.py, you used threshold=0.5. So, BinaryMetricStats do not calculate threshold. But if you do not pass threshold, BinaryMetricStats would calculate threshold from postive_scores/negative_scores, then the bug would occur.

Sorry for my late response been busy the last week.
I am not familiar with the EER computation here but this definitely looks like a bug.

Close this issue, for we are already working on it in a PR


Saulparedes/genpolicy sync [DO NOT MERGE]

Merge Checklist

[ ] Followed patch format from upstream recommendation: https://github.com/kata-containers/community/blob/main/CONTRIBUTING.md#patch-format

[ ] Included a single commit in a given PR - at least unless there are related commits and each makes sense as a change on its own.

[ ] Aware about the PR to be merged using "create a merge commit" rather than "squash and merge" (or similar)
[ ] genPolicy only: Ensured the tool still builds on Windows
[ ] genPolicy only: Updated sample YAMLs' policy annotations, if applicable
[ ] The upstream-missing label (or upstream-not-needed) has been set on the PR.

Summary

Associated issues

Links to CVEs

Test Methodology

Do not merge until changes in https://github.com/kata-containers/kata-containers/pull/9185/commits are incorporated

Closing for https://github.com/microsoft/kata-containers/pull/171


New version: Billfish.Billfish version <IP_ADDRESS>

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Resolves #38766

Microsoft Reviewers: Open in CodeFlow

The executable downloaded from that URL is a downloader, so I use Fiddler to capture the connections and Proxifier to force its connections to redirect to Fiddler.

BTW
https://front-gw.aunapi.com/applicationService/app/upgrade/check?appId=10301011&versionCode=<IP_ADDRESS>&queryHistory=1&packageSystemSupport=1


Allow Cake modules to be bootstrapped by Cake in a pre-processing phase

It would be nice if Cake itself could bootstrap modules in a pre-build phase.
I've created PR https://github.com/cake-build/cake/pull/1942 for this.

Fixed by  #1942


Add test for JSONP

JSONP is a way to get data across domains by inserting a script tag.
client app inserts this into DOM
<script src="https://status.github.com/api/status.json?callback=apiStatus"></script>

it also publishes apiStatus
window.apiStatus = function(data) { ... }

The server then responds with:
apiStatus({"Name": "Foo", "Id": 1234, "Rank": 7});

Because Script tag gets inserted there is a async side-effect which will escape the zone.

If we have control over the callback then the zone can be set up there right?

@petebacondarwin – yes, but that would mean that you can't drop in your favorite library and have it "just work"

@btford do you have idea of how this could be intercepted?

I'm trying a few approaches now.


Np 47873/terms conditions

I finally found the code.
one reason that it was lost, was that I did a refactoring of all the parameters in this class, and it was too many changes in one go.... still is many...

You are aware that @torbjokv is completing the "return token without access right claims if latest version of terms are not approved"? You are still committing code to this branch, so I think you and @torbjokv need to talk.

Build is failing. Re-request review when fixed.


Prepare for upcoming rustlang by fixing upcoming clippy warnings

Objective

Proactive changing of code to comply with warnings generated by beta of rustlang version of cargo clippy.

Solution

Code changed as recommended by rustup update, rustup default beta, cargo run -p ci -- clippy.
Tested using beta and stable.  No clippy warnings in either after changes made.

Changelog

Warnings fixed were: clippy::explicit-auto-deref (present in 11 files), clippy::needless-borrow (present in 2 files), and clippy::only-used-in-recursion (only 1 file).

bors r+


Uncaught TypeError: Cannot set property 'exports' of undefined at renderer.js:1

Describe the issue / bug.
Hi, I am having an issue with the following error: Uncaught TypeError: Cannot set property 'exports' of undefined at renderer.js:1,
I have setup a vue/electron app using electron-vue and it is working well for me however, when I import local JavaScript files (admin theme) into my index.ejs file i get the error, however I do not get this issue when using plain electron.
I want to use electron-vue as my application is developed using vue and it is making the whole integration of electron and vue together very easy.
How can I reproduce this problem?
The way I have got this error is simply by creating an electron-vue instance using yarn (or npm) and then imported a local JavaScript library into the index.ejs file in the renderer directory.
I wish I could supply more details on how to reproduce the issue however if i knew how to reproduce it then I would know the cause.
Tell me about your development environment.

Node version: 8.12.0
NPM version: Using yarn 1.13.0
vue-cli version: (if necessary) 3.5.2
Operating System: Windows 10

Any help would be great. Thanks
Sam

Can you paste the code snippet where you import local JS library ?
Try to import this library in renderer/main.js

@michalzaq12  I have already tried importing the local JS librarys into renderer/main.js but I then get a host of errors to do with jquery.
Here are how they are imported.

<script src="../static/assets/js/jquery-3.1.1.min.js" type="text/javascript"></script>
<script src="../static/assets/js/popper.min.js" type="text/javascript"></script>
<script src="../static/assets/js/bootstrap.min.js" type="text/javascript"></script>
<script src="../static/assets/js/plugins/metisMenu/jquery.metisMenu.js" type="text/javascript"></script>
<script src="../static/assets/js/plugins/slimscroll/jquery.slimscroll.min.js" type="text/javascript"></script>

<!--Custom and plugin javascript-->
<script src="../static/assets/js/inspinia.js" type="text/javascript"></script>
<script src="../static/assets/js/plugins/pace/pace.min.js" type="text/javascript"></script>

Hmm.
Some of your dependencies use 'ES modules' system and can not be loaded in index.ejs (without webpack).
I tried to load only jquery and it works.
Loading popper.js in index.ejs throw error: Uncaught SyntaxError: Unexpected token export
I found a few solutions: (only for popper.js but this probably applies to all dependencies )

In main.js
window.Popper = require('../../static/popper.min').default;
In index.ejs load popper with UMD system
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.11.0/umd/popper.min.js" type="text/javascript"></script>
In renderer.webpack.config
plugins: [   // ...   new webpack.ProvidePlugin({     Popper: ['popper.js', 'default'] }) // ... ]

Read how to correctly import bootstrap if you use webpack
https://getbootstrap.com/docs/4.0/getting-started/webpack/
Generally, I do not recommend using already compiled libraries.

@michalzaq12 It turned out to be the bootstrap import which was causing the main problem, after following the steps on the link it solved my issue. Thanks For your help.


Compute test and validation splits in one go using the same transforms

Right now we first need to create the dataset and then split it. The transforms are unfortunately defined when creating the dataset (there may be ways around this but haven't digged into it).
Since validation and test set will always have the same transforms, we reduce the repeated dataset generation by computing them in one go.

Yes, I am inclining towards this approach. Always use the same transform for both.

Codecov Report
Attention: Patch coverage is 0% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 30.93%. Comparing base (6086b97) to head (d07e6a9).

Files
Patch %
Lines

crabs/detection_tracking/datamodules.py
0.00%
4 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #147   +/-   ##
=======================================
  Coverage   30.93%   30.93%
=======================================
  Files          19       19
  Lines        1209     1209
=======================================
  Hits          374      374
  Misses        835      835

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


Add API Document

Add API Document

API.md
waifu2x/README.md - add API Document link

I do not intend to make it a documented API.
Also, I will not merge Pull Request from you because you look like just a malicious user.
Sorry for that.


[POC] Tox combined coverage report

Store the coverage data from each tox environment,
providing coverage data for each Python version,
and combine them into a final report which requires
100% coverage.

How does this affect Travis?

This follows from a discussion started on https://github.com/shazow/urllib3/pull/725 .  It has been on my todo list for a different project (https://phabricator.wikimedia.org/T74863), but it seemed worth exploring it here.
Immediate affect on Travis is none (other than the dependency on reFILE, which needs to be is fixed one way or another).
Ideally coverage data from Travis and Appveyor is sent to a service that can combine the coverage data, and report back to pull requests if the combined coverage reaches 100%.  So far, https://codecov.io/ looks like the best option.
e.g. https://github.com/codecov/codecov-python/pull/40 shows the coverage report in github, and on the Unified coverage report of that commit (https://codecov.io/github/codecov/codecov-python/codecov/init.py?ref=963697ffe8ea863986ea21ffce896751d08d85d9) you will see all platform specific branches of the code are show as green , but they are not covered on the respective individual job coverage reports (e.g. https://codecov.io/github/codecov/codecov-python/codecov/init.py?ref=963697ffe8ea863986ea21ffce896751d08d85d9&build=369.1 )
The outstanding issue with this model, IMO, is that travis and codecov.io do not offer the coverage data artifacts for download freely, so there is an element of lock-in which I dont like.  But there are workarounds that I am exploring.

I'm a strong -1 for anything that doesn't work in a purely-offline context. I do a lot of my dev on urllib3 while offline and I'd hate to depend on an online service to get the job done. :)

== @shazow on this, being able to get the feedback locally is as important as it is to be able to get it from a CI service.

@shazow & @sigmavirus24 ...
This patch provides the desired feedback locally.  This patch has nothing to do with a CI service.
It would remove '100% coverage feedback' from an individual nosetests run locally.  This has been inaccurate feedback.  No doubt you are well aware of those inaccuracies, and work with those inaccuracies in your mind when reading the nosetests coverage reports, but it still allows slippages in the real coverage, as the coverage report is explicitly omitting many branches.
With this changeset, to achieve such feedback, instead of relying on nosetests output the developer would need to use tox, or slightly quicker : tox -epy26,py27,py33,coveragereport , as that is sufficient to provide the desired combined coverage.
It is set up so that coverage data is stashed locally, so that after the initial coverage data has been stashed for all platforms, running tox -epy33,coveragereport will generate combined updated coverage report.

It's not inaccurate so much that we've whitelisted platform-specific branches. Code that we want exercised is still 100% exercised. I really don't see a way around this. To get full branch coverage, it would need to run on a permutated matrix of {multiple versions of windows, linux, multiple versions of osx, every version of python, with and without +ssl compiled, with and without pyopenssl} and probably some other cases I'm not remembering.
At best, we'll get slightly improved yet still incomplete coverage with a lot of changes/work in the process. :/

This changeset is only a proof of concept of one possible way to achieve cross-version branch coverage, by using tox instead of nosetests to provide the 100% coverage assurance locally.
I agree that some branches will be very difficult to provide accurate coverage for, as they would be prohibitively difficult for a developer to set up suitable environments in order to collect coverage for a few extra lines.  This changeset doesn't attempt to do that, and is not advocating for that.  Perfect is the enemy of good.  Using coverage omit or pragma's is more sensible for those hard to reach branches.
This changeset shows that, with minimal effort, using tox could eliminate a large cohort of branches currently being omitted (i.e. versions), and still achieve the desired 100% coverage assurance locally (and creating a path forward for CI-based verification of that assurance).  IMO that is striking the right balance, as tox makes it trivial and time-efficient for a developer to run tests in these version-based environments.
I can appreciate if you feel that cost/benefit is not the right balance for this project, based on its core teams needs.  This is just a proof of concept, and will be abandoned if the concept itself doesn't interest the core team.

Right now we have a simple heuristic: If it's a platform-specific branch, annotate it and move on. With a system like this, we'll have a much more complex heuristic that will require much more investigation.
I'm not opposed having combined coverage analytics in addition to what we already do, but I'm not convinced that this is easier/better in replacement to what we currently do.
May I propose a standalone script (or tox config) which gathers coverage while ignoring coveragerc across multiple tox points then collates it?

Certainly, having separate configurations is a good approach.
It would require a little duplication, as I assume a combined coverage would still want many of the existing coverage omit and exclude_line entries to produce a meaningful report.

Cool. If you can package this up into a reasonably isolated PR, we can keep it around. :)

Im not going to get back to this any time soon, and it needs to be restarted from the ground up to make it acceptable.

Thanks for giving it a try back then, sorry it never made it in. I'm sure this change will serve as an important reference in the future!


[network] decrease MAX_CONNECTION_DELAY_MS

10 minutes is too long for a maximum backoff, and it causes much longer
recovery times than expected.  It is now changed to 1 minute as a
maximum backoff to ensure that it retries every minute.

Would it harm if we reduce it even further (say 10 sec?) until we get proper fix for the issue?
Thing is, this number play some role as it increases duration of test and cause flakiness. So unless we think it will destroy prod I would have some small value here to make sure our dev experience does not suffer

Would it harm if we reduce it even further (say 10 sec?) until we get proper fix for the issue?
Thing is, this number play some role as it increases duration of test and cause flakiness. So unless we think it will destroy prod I would have some small value here to make sure our dev experience does not suffer

Yeah, we can reduce it further.  Usually, the only thing with decreasing a backoff like this is either 1. overloading the system with retries, or 2. cost.  And right now I don't think we have too much of a worry for either, so we can trade it off to be less flaky.

Thanks, let's put some small value then for now?

@bors-libra r+

:pushpin: Commit 32d811d has been approved by andll

:hourglass: Testing commit 32d811dc440ffc825cf437ad960244746aab3d52 with merge bf072747cb9a0dfc40a791f5087a9988aa8e798a...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r+

:bulb: This pull request was already approved, no need to approve it again.

This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.
There's another pull request that is currently being tested, blocking this pull request: #4357

:pushpin: Commit 32d811d has been approved by andll

:hourglass: Testing commit 32d811dc440ffc825cf437ad960244746aab3d52 with merge 998bd72954619a2627777d01bde3cc45eaa6672e...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: andll
Pushing 998bd72954619a2627777d01bde3cc45eaa6672e to master...


Old service IP address present in Istio Proxy route config

Bug Description
Overview
If I delete a service and then recreate it, the deleted IP address for the service is present in the list of domains in the Istio Proxy route config for the service but the new IP address is not present.
This means that requests directly to the service IP (i.e. requests with the service IP in the host header) are not handled correctly. In particular they fail if the mutual tls policy is STRICT as they go via the PassthroughCluster.
What I hit
Before deleting the internal-http service
Services
$ kubectl get services -n app
NAME                                   TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                         AGE
alt-http-service                       ClusterIP      <IP_ADDRESS>   <none>        7001/TCP                        3s
internal-http                          ClusterIP      <IP_ADDRESS>    <none>        7001/TCP,8082/TCP,8083/TCP      52s

Istio-Proxy route config on a client pod for route "7001"
      - version_info: 2022-02-15T15:48:46Z/44
        route_config:
          '@type': type.googleapis.com/envoy.config.route.v3.RouteConfiguration
          name: "7001"
          virtual_hosts:
           - name: allow_any
             ...
           - name: alt-http-service.app.svc.cluster.local:7001
              ...
           - name: internal-http.app.svc.cluster.local:7001
              domains:
                - internal-http.app.svc.cluster.local
                - internal-http.app.svc.cluster.local:7001
                - internal-http
                - internal-http:7001
                - internal-http.app.svc
                - internal-http.app.svc:7001
                - internal-http.app
                - internal-http.app:7001
                - <IP_ADDRESS>
                - <IP_ADDRESS>:7001

The Service IP address, <IP_ADDRESS>, is present in the list of domains
After deleting the internal-http service
Service deleted by:
kubectl delete service internal-http -n app

Services
$ kubectl get services -n app
alt-http-service                       ClusterIP      <IP_ADDRESS>   <none>        7001/TCP                        7m28s

Istio-Proxy route config on a client pod for route "7001"
      - version_info: 2022-02-15T15:55:56Z/45
        route_config:
          '@type': type.googleapis.com/envoy.config.route.v3.RouteConfiguration
          name: "7001"
          virtual_hosts:
            - name: allow_any
             ...
            - name: alt-http-service.app.svc.cluster.local:7001
             ...

The service has been removed from the route_config for route "7001"
After recreating the internal-http service
The service is recreated by doing a Helm upgrade on the Helm release that installed it.
Services
$ kubectl get services -n app
NAME                                   TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                         AGE
alt-http-service                       ClusterIP      <IP_ADDRESS>   <none>        7001/TCP                        8m3s
internal-http                          ClusterIP      <IP_ADDRESS>   <none>        7001/TCP,8082/TCP,8083/TCP      5s

Istio-Proxy route config on a client pod for route "7001"
     - version_info: 2022-02-15T15:56:44Z/46
        route_config:
          '@type': type.googleapis.com/envoy.config.route.v3.RouteConfiguration
          name: "7001"
          virtual_hosts:
            - name: allow_any
              ...
            - name: alt-http-service.app.svc.cluster.local:7001
              ...
            - name: internal-http.app.svc.cluster.local:7001
              domains:
                - internal-http.app.svc.cluster.local
                - internal-http.app.svc.cluster.local:7001
                - internal-http
                - internal-http:7001
                - internal-http.app.svc
                - internal-http.app.svc:7001
                - internal-http.app
                - internal-http.app:7001
                - <IP_ADDRESS>
                - <IP_ADDRESS>:7001

The old service IP address, <IP_ADDRESS> is present in the list of domains but the new service IP address, <IP_ADDRESS>, is not. The version info timestamps show that this route_config has been configured into istio-proxy after the service has been deleted and then recreated.
Version
$ kubectl version --short
Client Version: v1.21.1
Server Version: v1.21.7

$ helm version --short
v3.6.0+g7f2df64

Version of Istio Helm chart: 1.12.2
Additional Information
Relevant logs from Istiod:
On service deletion:
{"level":"info","time":"2022-02-15T15:55:56.355882Z","scope":"ads","msg":"Incremental push, service internal-http.app.svc.cluster.local has no endpoints"}
{"level":"info","time":"2022-02-15T15:55:56.456505Z","scope":"ads","msg":"Push debounce stable[53] 3 for config ServiceEntry/app/internal-http.app.svc.cluster.local: 100.462629ms since last change, 104.975426ms since last push, full=true"}

On service recreation:
{"level":"info","time":"2022-02-15T15:56:44.194493Z","scope":"ads","msg":"Full push, new service app/internal-http.app.svc.cluster.local"}
{"level":"info","time":"2022-02-15T15:56:44.194524Z","scope":"ads","msg":"Full push, service accounts changed, internal-http.app.svc.cluster.local"}
{"level":"info","time":"2022-02-15T15:56:44.294977Z","scope":"ads","msg":"Push debounce stable[54] 3 for config ServiceEntry/app/internal-http.app.svc.cluster.local: 100.427613ms since last change, 112.645002ms since last push, full=true"}

I can reproduce on master

cc @bianpengyuan

Let me take a look at this.

Thanks for the report


Master -> Main Rename

Part of https://github.com/Islandora/documentation/issues/1595

Something I noticed yesterday when I made #1602 is that we have some PR going into master right now and some into main, so the two branches are diverging. It looks like #1601 went in against master. And this PR is against master.

It seems like master needs to be merged into main and then deleted, as @whikloj noted in https://github.com/Islandora-Devops/ansible-role-grok/pull/9, so they don't keep getting out of sync. Just wanted to note it here so that it doesn't get lost on this PR.

rolls up his sleeves and gets to it :man_mechanic:

eh... that rebase half worked....  let me see...

Ok, this has master and main pulled in.  Should be ready now.  Please squash and merge.

A little extra de-CLAWing whilst I'm in there :tophat:

ping @whikloj - Github's blocking, pending your change request.

@whikloj, would you mind releasing your hold on this one?

@whikloj bump


possible brick after custom UFI Firmware

I have a asus cn62 in the past I used your setup-kodi.sh just fine.
My chromebox was in developer mode, I hit  CTRL-ALT-F2 to get to command line, I entered "chronos"
I ran
curl -L -O https://mrchromebox.tech/setup-kodi.sh && sudo bash setup-kodi.sh
I choose 6, the backed up the current firmware.
It seemed to attempt to update the firmware to coreboot_tiano-guado-mrchromebox_20180204.rom but failed.  It said "An error occurred flashing the Full ROM firmware. DO NOT REBOOT!"
I tried 6 again and it failed.  So I though, ok ill just do a dual boot, so I choose option 1 and it said it worked and I should reboot to allow chrome os to "repair"
Upon reboot, a black screen via hdmi.  The power white light comes on for about 30 seconds then turns off.  I have not been able to see anything on screen when it powers on.
Did I brick it, or can I somehow restore the saved firmware.  I tried to do the standard chrome OS recovery with the reset button but noting appears on screen.
Let me know if you have any ideas for recovery.

Did I brick it, or can I somehow restore the saved firmware

yes to both.  you bricked it by not restoring your stock firmware backup after it gave an error flashing the UEFI Full ROM firmware.  At that point, you system was in an unstable/undetermined state, and restoring the stock backup was the only safe move.  Switching to a dual boot setup would first require you to restore the stock backup so you'd be starting from a working baseline.
since your device is bricked, you'll need to either reflash the firmware using an external programmer, or have me do it for you.  Shoot me an email at MrChromebox at gmail and we'll discuss the options to get you back up and running


Accept dash sign in routing segment default value.

From IsParameterized extension method source code, it accept [A-Za-z0-9_] as default value. But I think it should accept dash (-) too.
Basically, change the regex to the following should resolve this
{(?<name>[A-Za-z0-9_]*)(?:\?(?<default>[A-Za-z0-9_-]*))?}

@lijunle Would you care to send us a pull-request for this? Thanks

Do I need to add one test case for this?

@lijunle From what I can tell, we do not have any test for IsParameterized, so we would not enforce it. Bonus points if you added test coverage for the extension method :smile_cat:

However, I just resolve it without test. :dog:


Asterisk not showing

Using Jablotron with prefixes so for example:   4*9999 as codes. No matter what i do, no * will be on the keypad.
I've entered the master code with asterisk in the configuration.

What keypad do you see? Can you post a screenshot?

Sure!

The detection is here: https://github.com/kukulich/home-assistant-jablotron100/blob/6220840e1f844646e4383468b8f9d29f14e6e6b0/custom_components/jablotron100/jablotron.py#L273
I cannot test is it so you can change it here to check where’s the problem.

Sorted! Reinstalled it. Not sure what was wrong tho. Thanks


Error Messages are not helpful

hey @FriedrichWeinmann, the error messages are back to not as useful and I can't fix it with my PS1 scripting skills. Can you take a look, please? Attached is a screenshot and a support package.

dbatools_support_pack_2018_08_12-10_37_01.zip

closed as dupe of #4369 which is more recent


How does reply_to=123 work?

It appears that i don't really understand how the reply_to parameter for a tweet can be used.
I used it like:
account.tweet(msg,reply_to = ele[0])
Where msg is a string and ele[o] is the id if the tweet i want to answer.
The msg string is beginning with an @name.
What am i doing wrong?
Edit: stunning work btw.

I just saw in your code that reply to is only available for sceduled tweets, right?
As you know your code muuuuch better, would a change here be possible?
I don't want to be demanding and would use a workaround if you don't want/can change this atm..
Regards :)

I think someone else also had a similar issue. I'm going to be removing those keyword arguments for tweet() in the future to avoid confusion. I may also refactor these methods to make the API slightly more intuitive.
Basically, tweet() is only intended to accept a message and an optional media parameter. Kwargs aren't supposed to be used directly, only the methods reply(), quote(), and create_poll() are supposed to be using them. This is because all of these methods are calling the same endpoint that tweet() does, but with some extra parameters
On the other hand retweet() and schedule_tweet() use entirely different endpoints, so they cannot simply call tweet() with extra params.
To answer your specific questions:

I just saw in your code that reply to is only available for sceduled tweets, right?

Nope, we can reply to a tweet simply using reply(). Scheduled tweets use a different endpoint, so I've currently created a seperate method for them as you may have seen in the readme.

What am i doing wrong?

If you only care about replying to a tweet you can simply use the method reply()
account.reply(123, 'my reply')

If you want to schedule a reply, a different method is used:
account.schedule_tweet('my scheduled reply', '2023-04-20 19:11', reply_to=123456)

## or with a unix timestamp
# account.schedule_tweet('my scheduled reply',<PHONE_NUMBER>, reply_to=123456)

i was dumb enough to not see the reply function...
Thanks a lot for clarification!


Scope 'ui' is not active for the current thread

Hi. i have a problem when using vaadin4spring without spring boot.
web.xml :
<listener>
		<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
	</listener>

	<listener>
		<listener-class>org.springframework.web.context.request.RequestContextListener</listener-class>
	</listener>

	<!-- Spring Security -->
	<filter>
		<filter-name>springSecurityFilterChain</filter-name>
		<filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
	</filter>
	<filter-mapping>
		<filter-name>springSecurityFilterChain</filter-name>
		<url-pattern>/*</url-pattern>
	</filter-mapping>

<servlet>
		<servlet-name>Vaadin GUI</servlet-name>
		<servlet-class>org.vaadin.spring.servlet.SpringAwareVaadinServlet</servlet-class>
		<init-param>
			<param-name>UI</param-name>
			<param-value>com.example.exampleProject.testUI</param-value>
		</init-param>
	</servlet>
	<servlet-mapping>
		<servlet-name>Vaadin GUI</servlet-name>
		<url-pattern>/*</url-pattern>
	</servlet-mapping>
	<servlet-mapping>
		<servlet-name>Vaadin GUI</servlet-name>
		<url-pattern>/VAADIN/*</url-pattern>
	</servlet-mapping>

Project opens, but when I press any button for navigate to another view I'm getting this errors :
org.springframework.beans.factory.BeanCreationException:  Error creating bean with name 'roleUserView': Scope 'ui' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is

Caused by: java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

Does someone help me?
Thx.Have a nice day.

Could you provide an example using SpringAwareUIProvider with Spring (no Spring- Boot)?

This issue will be addressed by the official Vaadin Spring add-on that is currently under development. See https://github.com/vaadin/spring.


[docker] reduction in the number of layers for controller image

What this PR does / why we need it:
A small improvement in the form of reducing the number of layers in the final docker image
Type of changes
Please delete options that are not relevant.

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

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

A small improvement in the form of reducing the number of layers in the final docker image

/lgtm
/approve

thanks @alekseyolg !


View close context

I reviewed this, cuz nobody else does...

I reviewed it for myself, cuz nobody else does...


SchemaProvider::getRelationships default behaviour

Hi,
I don't really understand the default behaviour for the method Neomerx\JsonApi\Schema\SchemaProvider::getRelationships, this line exactly : https://github.com/neomerx/json-api/blob/master/src/Schema/SchemaProvider.php#L201
is there some magic I don't understand ?
Thanks

Suppress 'unused variable' warning. The code will be removed by optimizer.

Thanks for your answer but suppress to don't have warning in what ? php code_sniffer ?

I'm using PhpStorm which annoys me with warnings on this. Great IDE though.
IMHO from PHP 7 it's better to use assert(...).

... did you know you can suppress these things ? Making things because of a tool (PHPStorm, Scrutinizer, unit tests, ...) is kind of a sign of bad design...
P.S : assert is not for that (it's to assert a value actually, triggering an exception if it's not valid)

well IMHO you should do nothing, this is not because your IDE blink a little bit that you should implement dead and useless code. And I don't understand why you would like to use assert, there is nothing to check here.

Thanks all for your positive comments. Feel free to override the method you like.

@lunika For the reason that from PHP 7 the framework guarantees you that any code in assert will be removed when run in production mode. Before PHP 7 I had to rely on how optimizer works among 5.5, 5.6 and HHVM. I considered a few options and found that one meeting the needs.

@Taluu Have a screenshot of you comment and put it to your calendar to review in 5 years. I bet you will see you 'design mantra' differently. Just a pro advice.

@neomerx For the assert, reading the docs (and the rfc, etc), the default is that a warning will be generated (because the default is not "ignore in prod" -- yes, you SHOULD configure properly, but note that it is not a MUST).
BTW, my "design mantra" as you call it is evolving. Whenever I find something that displease me while it was looking good even a month back, I'm trying NOT to continue in the wrong path. I'm not "oh well my opinion will change". Especially when someone points me something is wrong. This is my "pro advice".
But... whatever. Your project, your ideals.


Poor visualizations, getting zero SDR, SIR, etc. on evaluation

I was trying to evaluate on 16 videos using downloaded trained model but I am unable to see the results in visualization. Video1 and video2 have only 3 frames each with no audio and predicted audio are also silent.
I'm getting the following output after evaluation:
Loading weights for net_frame
Loading weights for net_synthesizer
samples: 6300
samples: 16
1 Epoch = 196 iters
Evaluating at 0 epochs...
[Eval] iter 0, loss: 0.0115
[Eval Summary] Epoch: 0, Loss: 0.0115, SDR_mixture: 0.0000, SDR: 0.0000, SIR: 0.0000, SAR: 0.0000
Plotting html for visualization...
Evaluation Done!
Hope I would get some help
Thanks

Problem got solved

hi, deepakee13,  I got the same problem as you, so can you give me some ideas on how to solve this problem? thanks~

I removed normalization coefficient of 2^-31 from raw audio and took
transpose of it which was probably in base.py and then it worked fine.
........................
Deepak Kumar
On Wed 12 Jun, 2019, 7:59 AM yifan254<EMAIL_ADDRESS>wrote:

hi, deepakee13, I got the same problem as you, so can you give me some
ideas on how to solve this problem? thanks~
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/hangzhaomit/Sound-of-Pixels/issues/7?email_source=notifications&email_token=AGYHMBXCGBKBT6FO5UJKM53P2BNO7A5CNFSM4HMTSLQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXPB7AA#issuecomment-501096320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGYHMBSKXC7DDPFOWI5YMBDP2BNO7ANCNFSM4HMTSLQA
.

hello, I want to know what can be calculated by modifying that part in base.py.

@deepakee13 can you share the your  code snippet after you made the correction to the function? (The transpose part specifically) Thanks!

@JusperLee If you can also provide any input then it will be great. Thanks in advance.

@parth1497 #9


improved contains

contains returns only results that match string, object or array.

all is well what ends well!


gstreamer for steam-run broken on master

Issue description
Build fails for steam-run when using current nixpkgs master:
$ nix-shell '<nixpkgs>' -A steam-run --pure
these derivations will be built:
  /nix/store/vzvp6d8mml24f0f98a1c4pb6gpacd9kh-gst-plugins-base-1.16.0.drv
  /nix/store/xn3kz23bpi2i2h96b89y2fmq7qsfz4g3-gst-plugins-ugly-1.16.0.drv
  /nix/store/831qz5iw51p27fja2fq0vy7v820zkys4-steam-run-usr-multi.drv
  /nix/store/g9qgp240gmj8hgg0k771hay72qlr2p3r-gst-plugins-base-1.16.0.drv
  /nix/store/4vxlg34v3lfx8i6jzhdbjmx1zf5kpv72-gst-plugins-ugly-1.16.0.drv
  /nix/store/vz2fxafddp9zfl09jcran3x790idbi49-steam-run-usr-target.drv
  /nix/store/080al2r06g3f03wa0sxvq7c7b3riz6l7-steam-run-fhs.drv
  /nix/store/20cnnn682bki449wnx2rz3xmcj8amjpl-steam-run-init.drv
building '/nix/store/g9qgp240gmj8hgg0k771hay72qlr2p3r-gst-plugins-base-1.16.0.drv'...
building '/nix/store/vzvp6d8mml24f0f98a1c4pb6gpacd9kh-gst-plugins-base-1.16.0.drv'...
unpacking sources
unpacking source archive /nix/store/ny4rkf83c82k6vn17vpzpq6y4p8f1r3i-gst-plugins-base-1.16.0.tar.xz
unpacking sources
unpacking source archive /nix/store/ny4rkf83c82k6vn17vpzpq6y4p8f1r3i-gst-plugins-base-1.16.0.tar.xz
source root is gst-plugins-base-1.16.0
source root is gst-plugins-base-1.16.0
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file gst-plugins-base-1.16.0/po/zh_CN.po
patching sources
applying patch /nix/store/x7py1q1yqdc1kkk9k469qi24mm83j7rd-fix_pkgconfig_includedir.patch
patching file pkgconfig/meson.build
patching script interpreter paths in .
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file gst-plugins-base-1.16.0/po/zh_CN.po
patching sources
applying patch /nix/store/x7py1q1yqdc1kkk9k469qi24mm83j7rd-fix_pkgconfig_includedir.patch
patching file pkgconfig/meson.build
./depcomp: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
patching script interpreter paths in .
./config.sub: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./depcomp: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./install-sh: interpreter directive changed from "/bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./config.sub: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./test-driver: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./install-sh: interpreter directive changed from "/bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./common/extract-release-date-from-doap-file: interpreter directive changed from "/bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./test-driver: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./common/download-translations: interpreter directive changed from "/bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./common/extract-release-date-from-doap-file: interpreter directive changed from "/bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./common/download-translations: interpreter directive changed from "/bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./common/check-exports: interpreter directive changed from "/bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./common/scangobj-merge.py: interpreter directive changed from "/usr/bin/python" to "/nix/store/wd9cd2hhfim7i64ff1p1vsm6cb5kf4gq-python3-3.7.3/bin/python"
./common/check-exports: interpreter directive changed from "/bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./common/gst-indent: interpreter directive changed from "/bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./common/scangobj-merge.py: interpreter directive changed from "/usr/bin/python" to "/nix/store/4c4ajgdnhlqk994hilagk5cgv7vw9yzg-python3-3.7.3/bin/python"
./compile: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./common/gst-indent: interpreter directive changed from "/bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./config.guess: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./compile: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./autogen.sh: interpreter directive changed from "/bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./config.guess: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./config.rpath: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./autogen.sh: interpreter directive changed from "/bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./missing: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./config.rpath: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
./configure: interpreter directive changed from " /bin/sh" to "/nix/store/j1qjqdwxlyc62fadqw4kya5cn0qyf2sc-bash-4.4-p23/bin/sh"
./missing: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
configuring
./configure: interpreter directive changed from " /bin/sh" to "/nix/store/w9ngash2dw3pvl98ysd79qy2rkkmc8my-bash-4.4-p23/bin/sh"
meson flags: --buildtype=release         --libdir=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0/lib --libexecdir=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0/libexec         --bindir=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0/bin --sbindir=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0/sbin         --includedir=/nix/store/47yy0agwxzl5wks4zjjilpcgk66mawai-gst-plugins-base-1.16.0-dev/include         --mandir=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0/share/man --infodir=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0/share/info         --localedir=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0/share/locale         -Dauto_features=disabled         --prefix=/nix/store/qls86h2ipf9x79i05msba23v4rbb9wic-gst-plugins-base-1.16.0 -Dauto_features=enabled -Dexamples=disabled -Dgl-graphene=disabled -Dgl_winsys=[x11,wayland] -Dgtk_doc=disabled
configuring
meson flags: --buildtype=release         --libdir=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0/lib --libexecdir=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0/libexec         --bindir=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0/bin --sbindir=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0/sbin         --includedir=/nix/store/mgw15jqamf2jw0qqfdch3vb68qjm8b7w-gst-plugins-base-1.16.0-dev/include         --mandir=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0/share/man --infodir=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0/share/info         --localedir=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0/share/locale         -Dauto_features=disabled         --prefix=/nix/store/hzlqdrgln5kmlp3sqdl8nblhlpi5kqd0-gst-plugins-base-1.16.0 -Dauto_features=enabled -Dexamples=disabled -Dgl-graphene=disabled -Dgl_winsys=[x11,wayland] -Dgtk_doc=disabled
gcc: error: /build/gst-plugins-base-1.16.0/build/meson-private/sanitycheckobjc.m: Objective-C compiler not installed on this system
gcc: error: /build/gst-plugins-base-1.16.0/build/meson-private/sanitycheckobjc.m: Objective-C compiler not installed on this system
The Meson build system
Version: 0.49.2
Source dir: /build/gst-plugins-base-1.16.0
Build dir: /build/gst-plugins-base-1.16.0/build
Build type: native build
Project name: gst-plugins-base
Project version: 1.16.0
Native C compiler: /nix/store/x3fl1fblijxrmnsiwipsssqhpffz168r-gcc-wrapper-7.4.0/bin/cc (gcc 7.4.0 "gcc (GCC) 7.4.0")
Build machine cpu family: x86
Build machine cpu: i686
Native C++ compiler: /nix/store/x3fl1fblijxrmnsiwipsssqhpffz168r-gcc-wrapper-7.4.0/bin/c++ (gcc 7.4.0 "g++ (GCC) 7.4.0")
Compiler for language objc not found.
Compiler for C supports link arguments -Wl,-Bsymbolic-functions: YES
Compiler for C supports arguments -fvisibility=hidden: YES
Compiler for C supports arguments -fno-strict-aliasing: YES
Has header "dlfcn.h" : YES
Has header "emmintrin.h" : YES
Has header "inttypes.h" : YES
Has header "memory.h" : YES
Has header "process.h" : NO
Has header "smmintrin.h" : YES
Has header "stdint.h" : YES
Has header "stdlib.h" : YES
Has header "strings.h" : YES
Has header "string.h" : YES
Has header "sys/socket.h" : YES
Has header "sys/stat.h" : YES
Has header "sys/types.h" : YES
Has header "sys/wait.h" : YES
Has header "unistd.h" : YES
Has header "winsock2.h" : NO
Has header "xmmintrin.h" : YES
Has header "linux/dma-buf.h" : YES
Library m found: YES
Checking for function "dcgettext" with dependency -lm: YES
Checking for function "gmtime_r" with dependency -lm: YES
Checking for function "lrintf" with dependency -lm: YES
Checking for function "mmap" with dependency -lm: YES
Checking for function "log2" with dependency -lm: YES
Checking for size of "char" : 1
Checking for size of "int" : 4
Checking for size of "long" : 4
Checking for size of "short" : 2
Checking for size of "void*" : 4
Compiler for C++ supports arguments -Waggregate-return: YES
Compiler for C supports arguments -Wmissing-declarations: YES
Compiler for C++ supports arguments -Wmissing-declarations: YES
Compiler for C supports arguments -Wredundant-decls: YES
Compiler for C++ supports arguments -Wredundant-decls: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C++ supports arguments -Wundef: YES
Compiler for C supports arguments -Wwrite-strings: YES
Compiler for C++ supports arguments -Wwrite-strings: YES
Compiler for C supports arguments -Wformat: YES
Compiler for C++ supports arguments -Wformat: YES
Compiler for C supports arguments -Wformat-nonliteral: YES
Compiler for C++ supports arguments -Wformat-nonliteral: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C++ supports arguments -Wformat-security: YES
Compiler for C supports arguments -Winit-self: YES
Compiler for C++ supports arguments -Winit-self: YES
Compiler for C supports arguments -Wmissing-include-dirs: YES
Compiler for C++ supports arguments -Wmissing-include-dirs: YES
Compiler for C supports arguments -Waddress: YES
Compiler for C++ supports arguments -Waddress: YES
Compiler for C supports arguments -Wno-multichar -Wmultichar: YES
Compiler for C++ supports arguments -Wno-multichar -Wmultichar: YES
Compiler for C supports arguments -Wvla: YES
Compiler for C++ supports arguments -Wvla: YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C++ supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wdeclaration-after-statement: YES
Found pkg-config: /nix/store/y1anxcj45n8w4pbzjlq5m10b2fnhc3jw-pkg-config-0.29.2/bin/pkg-config (0.29.2)
Dependency x11 found: YES 1.6.7
Dependency glib-2.0 found: YES 2.60.3
Dependency gobject-2.0 found: YES 2.60.3
Dependency gio-2.0 found: YES 2.60.3
Dependency gio-unix-2.0 found: YES 2.60.3
Dependency gmodule-no-export-2.0 found: YES 2.60.3
Dependency gdk-pixbuf-2.0 skipped: feature examples disabled
Dependency gtk+-3.0 skipped: feature examples disabled
Dependency gtk+-x11-3.0 skipped: feature examples disabled
Dependency gstreamer-1.0 found: YES 1.16.0
Dependency gstreamer-base-1.0 found: YES 1.16.0
Dependency gstreamer-net-1.0 found: YES 1.16.0
Found CMake: NO
Dependency gstreamer-check-1.0 found: NO (tried pkgconfig)
Looking for a fallback subproject for the dependency gstreamer-check-1.0
Couldn't use fallback subproject in subprojects/gstreamer for the dependency gstreamer-check-1.0
Reason: Failed to initialize 'subprojects/gstreamer':
Subproject directory not found and gstreamer.wrap file not found

meson.build:303:0: ERROR:  Dependency "gstreamer-check-1.0" not found, tried pkgconfig

A full log can be found at /build/gst-plugins-base-1.16.0/build/meson-logs/meson-log.txt
builder for '/nix/store/vzvp6d8mml24f0f98a1c4pb6gpacd9kh-gst-plugins-base-1.16.0.drv' failed with exit code 1
cannot build derivation '/nix/store/xn3kz23bpi2i2h96b89y2fmq7qsfz4g3-gst-plugins-ugly-1.16.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/831qz5iw51p27fja2fq0vy7v820zkys4-steam-run-usr-multi.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/080al2r06g3f03wa0sxvq7c7b3riz6l7-steam-run-fhs.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/20cnnn682bki449wnx2rz3xmcj8amjpl-steam-run-init.drv': 1 dependencies couldn't be built
error: build of '/nix/store/20cnnn682bki449wnx2rz3xmcj8amjpl-steam-run-init.drv' failed

The meson-logs mentioned in the output do not exist anywhere as far as I can tell.
The build works fine on a718f72a8e88a97bb4381a4ece5d63c69ab1a217.
Steps to reproduce
Try to build steam-run from current master (987ec8aed453ea944a4d53aa0ee47d8371c6844c).
Technical details

system: "x86_64-linux"
host os: Linux 5.1.12, NixOS, 19.09pre-git (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): ""
channels(gaisseml): ""
nixpkgs: /nix/store/rs0pi5j63ihrvfalfc6q5cy02q9x4rd2-src/nixpkgs

nix-info output looks that way since I build from a nixpkgs git checkout and do not use channels.

building gst-plugins-base works, since this builds a different version (0.10.36)

Fixed by #63637.