Continuous fuzzing by way of OSS-Fuzz

Is your feature request related to a problem? Please describe.
My feature request is for integrating continuous fuzzing by way of OSS-Fuzz? Fuzzing is a way to automate test-case generation and can be used to find unexpected exceptions in Python.
I did an initial integration here: https://github.com/google/oss-fuzz/pull/8161 I did an initial integration into OSS-Fuzz.
The current fuzzer is targetting the parse_source function for the PythonParser class.
Describe the solution you'd like
The fuzzing will run continuously and emails will be sent out with links to reports when a bug is found. As such, if you would like to integrate, the only thing I need is a list of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.
Down the line we can move fuzzers from OSS-Fuzz and upstream into the coveragepy repository.

(oops, I commented on the oss-fuzz PR).   You can use my email address for reports<EMAIL_ADDRESS> I'm also wondering how best to connect to this from the coverage.py repo?

Thanks @nedbat I added it in the OSS-Fuzz repo now!
I think the best way to connect the coveragepy repository with OSS-Fuzz would be to place the fuzzer source code somewhere e.g. tests/fuzz and then have the oss-fuzz build.sh script build the fuzzers using the source code from here.
The fuzzers are written to use Atheris: https://github.com/google/atheris
In the OSS-Fuzz repository we have to compile the fuzzers using pyinstaller and the reason being OSS-Fuzz will run the fuzzers continuously in an environment that is different than the one where the fuzzers gets build. However, once you have atheris installed (which can be done by way of pip) then you can run the fuzzers locally as well. By "fuzzer" I mean this code: https://github.com/google/oss-fuzz/pull/8161/files#diff-c15265aa2ea458493da915659a527d7a818f62c4709c498d81662226d1953328 Depending on what you prefer, we could do various things too, e.g. integrate it into the testing suite or the CI (OSS-Fuzz provides CI support as well).
I suggest the first thing we do is merge https://github.com/google/oss-fuzz/pull/8161 then you will get experience with OSS-Fuzz when emails are sent out (assuming some issue will be found), then follow up with integrating it into the codebase here.

I've fixed the first bug found in https://github.com/nedbat/coveragepy/commit/3703bae58b53efec3314bc07b9de157049ad8b70.
I'm happy to let Google continue running the fuzzer, I don't need to do it locally I don't think.

I've fixed the first bug found in 3703bae.
I'm happy to let Google continue running the fuzzer, I don't need to do it locally I don't think.

Wonderful @nedbat ! Looking forward to providing more fuzzers then!


[FEAT] Publish to npm

Objective
It would be great if I could just npm install this without mucking about with third-party registries.
The config file editing is mildly annoying. The real annoyance, however, is that I have to authenticate to GitHub before it'll let me install packages: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#authenticating-to-github-packages
This raises the barrier to entry a decent amount and IMO may be enough to discourage drive-by skill writing by people who might be interested if we're able to pull them into the Mycroft community.
Initial Implementation Requirements

npm publish
profit

Other Considerations
No response

@mikejgray thanks! In case you didn't see though, the workflow failed: https://github.com/mikejgray/ovos-skill-projen/actions/runs/5709697090/job/15468937331

Yep, although I'm not sure how to fix it at this point, so I've manually published 0.0.14 to npm for now. I'll keep this issue open until I've got an automated fix. Thanks for the callout!

Thank you! I see it on the registry, much appreciated.


Migrate to Python 3

Title

Got a list of the files that are specifically not working in py3?

Well, not really.
All python scripts are placed here, but I have not actually tested if they will work in py3. I suppose there should not be any major issues, but still.
So this issue overall:

Test scripts under py3
Fix if something does not work
Update CMakeLists.txt & README.md

Currently working on this issue.


change robot-item-information font

can you combine the the changes regarding the stylings together in one PR? For example, the panels all look different currently


PC-1220: Connect to Open EPC API

Description
this is draft as PC-1299 is not yet merged
Checklist

[ ] I have made any necessary updates to the documentation
[ ] I have checked there are no unnecessary IDE warnings in this PR
[ ] I have checked there are no unintentional line ending changes
[ ] I have added tests where applicable
[ ] If I have made any changes to the code, I have used the IDE auto-formatter on it
[ ] If I have made any changes to Python files (even if not changing any content strings), I have run make extract-translations
[ ] If I have made any changes to website flow, I have updated the Flow Miro Board
[ ] If I have made any changes to website flow, I have checked forward and back behaviour is still consistent

Screenshots

Broadly looks fine: couple of comments. Main thing to think about is how we document what we're expecting to get back from the API.


feat: add test functions connection and authentication

Summary

Added Test-EndpointConnection to test the connectivity to an endpoint based on PowerShell edition.
Added Test-EsxiConnection to use Test-EndpointConnection with TCP 443 (HTTPS) and TCP 22 (SSH). Default: TCP 443 (HTTPS).
Added Test-EsxiAuthentication to test the authentication to an ESXi host.
Update CHANGELOG.md
Bump module manifest version to v<IP_ADDRESS>0.

Type

[ ] Bugfix
[x] Enhancement or Feature
[ ] Code Style or Formatting
[ ] Documentation
[ ] Refactoring
[ ] Chore
[ ] Other
Please describe:

Breaking Changes?

[ ] Yes, there are breaking changes.
[x] No, there are no breaking changes.

Test and Documentation

[x] Tests have been completed.
[ ] Documentation has been added or updated.

Issue References

Additional Information

Once merged, the following functions will be updated to use the Test-EndpointConnection for one of more tests.

Test-VCFConnection
Test-VsphereConnection
Test-SSOConnection
Test-vSphereApiConnection
Test-NSXTConnection
Test-vRSLCMConnection
Test-vROPSConnection
Test-vRLIConnection
Test-vRAConnection
Test-WSAConnection
Test-VrmsVamiConnection
Test-SrmVamiConnection
Test-SRMConnection

This is awesome @tenthirtyam! I can confirm that when testing the branch feat/add-test-esxi-conn-auth the function Request-EsxiPasswordExpiration from powershell-module-for-vmware-cloud-foundation-password-management fails, because it uses Test-VsphereConnection.
However, I think what you have planned is something like this: https://github.com/nzRegularIT/power-validated-solutions-for-cloud-foundation/tree/feat/add-test-esxi-conn-auth, which I can confirm works in PowerShell Core on Linux.


Add type to MultisigExecutionDetails

Closes #376

MultisigExecutionDetails now extends ExecutionDetails.
type attribute is added to MultisigExecutionDetails via new class constructor.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 19 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 92.251%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
4035

Relevant Lines:
4272

💛  - Coveralls


Windows 11 App Interface Gliches out graphics

Is there an existing issue for this?

[X] I have searched the existing issues.

What's the problem?

when opening the app:
all the graphics get all weirdly streached out. both in full screen and small size.

if i move the mouse the large stretched letters move around and glitch out. making the app unuseable
Manufacturer        : Dell Inc.
Model               : XPS 13 9380
TotalPhysicalMemory :<PHONE_NUMBER>0
WindowsVersion      : 2009
How did you install the app?
downloaded one of the provided packages
Operating System
Windows
Additional context
No response

Hi @wisehackermonkey
Check #312 for the solution

From #312:

This is due to incompatibilities between your graphical adapter and wgpu, the default renderer used by iced.
The problem is usually solved by using an alternative renderer (glow).
Here you are the download link for the Windows version of Sniffnet using it: https://github.com/GyulyVGC/sniffnet/suites/13469079922/artifacts/739158257
Let me know if it solves the issue!

I'm closing since this issue has already been solved a number of times.
All you have to do is installing the version using the glow renderer.
Feel free to reopen the issue if you still have problems.

thanks!


Improvement: Offer image optimisation

I'd appreciate a lot if Intervention offered an easy-to-use image optimisation feature. Maybe even on a 'optimize()' method!
Meanwhile, if you could share how that could be done by myself, I'd appreciate. Here is a lot of details about image optimisation:
https://www.smashingmagazine.com/2015/06/efficient-image-resizing-with-imagemagick/
Thanks for your great library!

Would be nice to have. But I can't see this applied to both GD and Imagick in a similar way.

Thanks @olivervogel for considering.
That's definitely understandable to have the image optimisation only via Imagick. Just like exif() only works when the exif library is compiled in php.
If you have the time, I'd strongly support the optimisation feature! It's just too important to ignore nowadays.
Even Wordpress 4.5 has added image optimisation to the core.


Pause on Hover does not work with Headless UI

I am working on the admin dashboard panel and I use the Headless UI Modal component to create new records. When an error is returned from the server I create a custom toast but the toast is rendered in the __next div and the Headless UI renders in the portal div.
The problem is the Headless UI Modal renders in front of the toast. In this case "Pause on Hover" property does not work.

Kind regards.
Abdulrahman Elheyb

@Abdulrahmanelheyb hello did you by any chance find a solution to put your toaster above the dialog?

I am stuck on the same problem, can't hover or click on the toast's content. Still can't find a solution to this problem.


chore: do not use Result in tests

Description
As mentioned in this PR comment, we prefer not to use Result in tests:
https://github.com/kubewarden/policy-fetcher/pull/152#discussion_r1311891401
This PR refactors the existing tests that do not comply.
Test

Additional Information
Maybe we could create a coding convention and guideline docs for all the rust projects.
This doc could collect testing-related information too: e.g. helper libraries to use, test organization, testing patterns, etc...

As for the coding conventions, I think it would be nice to have some guideline. That wouldn't mean we would have to go out and fix all the existing codebase to ensure everything is compliant with them. Let's discuss that with the rest of the team

Maybe we can write something in our .github repo and add a link to the  CONTRIBUTING guidelines.


Prevent Panic'ing on Timeout

The Process function panics when the Do method returns a non-nil error. Some errors may be worth Panic'ing at that point, but others are not.
https://github.com/miguelbernadi/monkeylearn-go/blob/e8a4c009ec9d3ef61b5665cfaab76fba7ec9b809/pkg/monkeylearn/client.go#L38
Identify the sources of error in that case and explicitly handle sanely those situations that can be handled. Also document the tradeoffs clearly in the project documentation.

The returned error is supposed to be of type url.Error https://godoc.org/net/url#Error which includes methods to verify if it's a temporary error or a timeout. Let's decide what we should in each case.


Help me, connectToServer Bug

Hello, having spent one hour trying to solve my problem, I post on this forum.
I want to clarify that I'm French and if I'm spelling mistakes excuse me. ( si il y a des Français ici, vous pouvez me répondre en français).
My problem is that trying to make a connection to a server button, my crash games.
I am inspired by a model on the forum, here: https://github.com/lumien231/Custom-Main-Menu/issues/64
Here are the logs of the crash: http://pastebin.com/04LDv5DA
Logs Custom Main Menu: http://pastebin.com/Q2KmrADc

You should run your menus through online json checkers before reporting problems :). Your json is invalid.


How Slave Gets Encryption Error Information

I created a HID Server and paired it with the phone.
When I use
NimBLEDevice::deleteAllBonds();
to delete the binding information, the phone can still connect to the server,  but it will be disconnected immediately.
The ondisconnect event triggers, but I don't know how to get the reason for the disconnection.
Through sniffer, we know that the reason  is "PIN or Key Missing"
We can't trigger a re-pair unless we choose to ignore this hid device on the phone.
My question is, is it possible to get the error message and even request re-pairing from the slave side?
BLE Sniffer:
Bluetooth Low Energy Link Layer
Access Address: 0xaf9aabed
[Master Address: 67:86:ee:88:51:3a (67:86:ee:88:51:3a)]
[Slave Address: Espressi_56:db:7a (a0:76:4e:56:db:7a)]
Data Header: 0x0317
Control Opcode: LL_REJECT_IND_EXT (0x11)
Reject Opcode: LL_ENC_REQ (0x03)
Error Code: PIN or Key Missing (0x06)
CRC: 0x8e0ec0
Thank you!

If the error only comes after the disconnection then it would be too late to trigger the pairing anyway. The client needs to delete the bond on it's side as well. I will look to change the callback in the future to provide the reason code.

Reason code is now provided in the onDisconnect callback.


Fix starring icon after semantic ui update

Fixes #4515, replaces #4532

Codecov Report

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

@@          Coverage Diff           @@
##           master   #4628   +/-   ##
======================================
  Coverage    20.8%   20.8%
======================================
  Files         158     158
  Lines       31908   31908
======================================
  Hits         6637    6637
  Misses      24293   24293
  Partials      978     978

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 c7a6ee5...6f4a16e. Read the comment docs.


Feat/nishauri profile etl

Adds scripts for loading Nishauri data from MhealthCentral to ODS

Nishauri Profile
Nishauri Feature Access

Okay, let me remove them.

I have made changes to the scripts and have removed the unique variables.  Advise if there's a variable I have missed. Thanks


Is there a check syntax command ?

running vscode abl on linux over ssh.
Can I check the syntax of the current file ?
I looked at the ABL commands, but I can't see a check syntax option.
Currently, my build contains 4K+ problems, mainly windows code I cannot yet manage to exclude from build.
I'd like to be able to check the current source or limit problems to the current source.

As Peter said, there's no Check syntax button, you have to save the file to trigger the compilation.


Look into diff playcounts resetting on update

this is a problem on osu's end but tracking it here until it's known where and how it could be fixed.

have since reported this on osu-web instead.


Increase soil moisture sensor from 8 to 16

Recent Ecowitt firmware allowed hubs to receive data from 16 soil moisture sensors, instead of 8. This change just adds sensor mappings for sensors 9-16.

Please review and approve this so I can have the extra channels enabled

@pvizeli would it be possible to quickly review this and the other PRs in this repo? They're all very small, and I believe would all result in closed bugs in HA core. Please let me know if there is anything I can do to move it along. Thank you.

@pvizeli I've reviewed zacs code and it looks pretty straight forward. Is there anything stopping you from merging?


fix(line): Ensure null check to avoid Cannot set properties of null (setting 'hoverState') error

Brief Information
This pull request is in the type of:

[x] bug fixing
[ ] new feature
[ ] others

What does this PR do?
This PR fixes the following error:
Uncaught TypeError: Cannot set properties of null (setting 'hoverState')
    at setStatesFlag (states.js:117:1)
    at __webpack_modules__../node_modules/echarts/lib/chart/line/LineView.js.LineView._changePolyState (LineView.js:763:1)
    at Symbol.changePolyState [as onHoverStateChange] (LineView.js:667:1)
    at doChangeHoverState (states.js:72:1)
    at singleLeaveBlur (states.js:93:1)
    at states.js:311:1
    at __webpack_modules__../node_modules/zrender/lib/graphic/Group.js.Group.traverse (Group.js:131:1)
    at __webpack_modules__../node_modules/zrender/lib/graphic/Group.js.Group.traverse (Group.js:133:1)
    at states.js:310:1
    at Global.js:511:1

By removing a redundant call to setStatesFlag missing a null/undefined check
Fixed issues

I haven't created a separate issue, but I can if you would like
Details
Before: What was the problem?

There can be a race condition between the tooltip and instance.dispatchAction({type: 'downplay'}) that causes the chart to freeze with an exception

After: How does it behave after the fixing?

There is no longer an error

Document Info
One of the following should be checked.

[x] This PR doesn't relate to document changes
[ ] The document should be updated later
[ ] The document changes have been made in apache/echarts-doc#xxx

Misc
ZRender Changes

[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
N.A.
Others
Merging options

[ ] Please squash the commits into a single one when merging.

Other information

Thanks for your contribution. Can you add a test case for this fix?

Thanks @plainheart, I have added a couple test cases


[#5661] feat(auth): Add JDBC authorization plugin interface

What changes were proposed in this pull request?
Add JDBC authorization plugin interface
Why are the changes needed?
Fix: #5661
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add a UT

This PR is too big to review effectively. Can we split it into a few smaller ones?

It's hard to split otherwise we can't get whole picture of this feature.

@tengqm Do you have any other suggestion? I can raise a follow up pull request to fix them.

@tengqm Do you have any other suggestion? I can raise a follow up pull request to fix them.

Thanks for asking. None of the issues I raised were meant to be blockers.


install duster as dev dependency

duster shouldn't be installed as a real dependency but dev

Thanks @Gummibeer!


chore(frontend): add X-Frame-Options header

Changes proposed in this pull request

I think this is my first frontend PR ever 😂
Adds X-Frame-Options header to Admin UI.
Context

fixes #2418

Checklist

[x] Related issues linked using fixes #number
[ ] Tests added/updated
[ ] Documentation added
[ ] Make sure that all checks pass
[ ] Bruno collection updated

LGTM

Should we add the Content-Security-Policy: frame-ancestors 'self'; header as well?
https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html#defending-with-content-security-policy-csp-frame-ancestors-directive

Should we add the Content-Security-Policy: frame-ancestors 'self'; header as well?
https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html#defending-with-content-security-policy-csp-frame-ancestors-directive

The limitations of that mentioned in the cheat sheet are that X-Frame-Options takes priority.


Kaizen

What kind of change does this PR introduce?
Bug fix + some cleanup.
What is the new behavior?

Remove docs: these are pretty outdated, we can add back OAS stuff later when we need it.
Remove unused stuff from src/server: these are stubs for using the new lib, but are currently unused.
Move old stuff to src/old: makes it clear which parts are the new lib stuff and which are the old routes.
Pluralize PostgresMeta objects (PostgresMetaColumns, etc.)
Fix /publications: forgot to update the logic & tests in #98. 😅 Probably better to specify tables using OIDs when creating publications, but this'll do for now.

will have to trust you on this one 😅


kubernetes_apiserver: Introduce bundle_unspecifed_events to send bundled and unbundled events both

What does this PR do?

Send bundled and unbundled events both when unbundle_events: true and bundle_unspecifed_events: true.

Unbundle events based on collected_event_types config.
Bundle the rest of events.

Motivation

When unbundle_events: true, we cannot collect events that do not match collected_event_types.
Additional Notes

Since bundle_unspecifed_events: false is the default value, the default behavior will not change.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Unbundle all Pod events.
Bundle other events.

apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
  name: datadog
spec:
  override:
    clusterAgent:
      image:
        name: cluster-agent-dev
        tag: keisku-enhance-unbundle-events
        pullPolicy: Always
      extraConfd:
        configDataMap:
          kubernetes_apiserver.yaml: |-
            init_config:
            instances:
            - unbundle_events: true
              bundle_unspecifed_events: true
              collected_event_types:
              - kind: Pod
              filtered_event_types:
              - reason!=Created

Exclude reason:created events.
Unbundle Pod Events and bundle the rest of events.

/merge


demo run failed

Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter build flx --suppress-analytics --target lib/main.dart --output-file D:\flutter\examples\hello_world\build\app\intermediates\flutter\debug/app.flx --snapshot D:\flutter\examples\hello_world\build\app\intermediates\flutter\debug/snapshot_blob.bin --depfile D:\flutter\examples\hello_world\build\app\intermediates\flutter\debug/snapshot_blob.bin.d --working-dir D:\flutter\examples\hello_world\build\app\intermediates\flutter\debug/flx
exception
SocketException: SocketException: OS Error: 信号灯超时时间已到
, errno = 121, address = android.googlesource.com, port = 64226
#0      fetchUrl (package:flutter_tools/src/base/net.dart:18)
<asynchronous suspension>
#1      _downloadFile (package:flutter_tools/src/cache.dart:405)
<asynchronous suspension>
#2      _downloadZippedTarball.<anonymous closure> (package:flutter_tools/src/cache.dart:421)
<asynchronous suspension>
#3      _withTemporaryFile (package:flutter_tools/src/cache.dart:433)
<asynchronous suspension>
#4      _downloadZippedTarball (package:flutter_tools/src/cache.dart:420)
#5      GradleWrapper.updateInner (package:flutter_tools/src/cache.dart:394)
<asynchronous suspension>
#6      CachedArtifact.update (package:flutter_tools/src/cache.dart:223)
<asynchronous suspension>
#7      Cache.updateAll (package:flutter_tools/src/cache.dart:196)
<asynchronous suspension>
#8      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:225)
<asynchronous suspension>
#9      BuildSubCommand.verifyThenRunCommand (package:flutter_tools/src/commands/build.dart:50)
<asynchronous suspension>
#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:181)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:194)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:276)
<asynchronous suspension>
#13     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109)
#14     new Future.sync (dart:async/future.dart:222)
#15     CommandRunner.run (package:args/command_runner.dart:109)
#16     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:161)
#17     run.<anonymous closure> (package:flutter_tools/executable.dart:143)
<asynchronous suspension>
#18     AppContext._run (package:flutter_tools/src/base/context.dart:76)
<asynchronous suspension>
#19     AppContext.runInZone.<anonymous closure> (package:flutter_tools/src/base/context.dart:66)
#20     _rootRun (dart:async/zone.dart:1120)
#21     _CustomZone.run (dart:async/zone.dart:1001)
#22     runZoned (dart:async/zone.dart:1467)
#23     AppContext.runInZone (package:flutter_tools/src/base/context.dart:65)
#24     run (package:flutter_tools/executable.dart:114)
<asynchronous suspension>
#25     main (package:flutter_tools/executable.dart:67)
<asynchronous suspension>
#26     main (file:///D:/flutter/packages/flutter_tools/bin/flutter_tools.dart:16)
#27     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:263)
#28     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)

flutter doctor
[✓] Flutter (on Microsoft Windows [Version 10.0.15063], locale zh-CN, channel master)
    • Flutter at D:\flutter
    • Framework revision 2859a563ce (11 hours ago), 2017-09-18 14:55:20 -0700
    • Engine revision 82fb559566
    • Tools Dart version 1.25.0-dev.11.0

[✓] Android toolchain - develop for Android devices (Android SDK 26.0.1)
    • Android SDK at D:\SDK
    • Platform android-26, build-tools 26.0.1
    • ANDROID_HOME = D:\SDK\platform-tools;D:\SDK\tools
    • Java binary at: F:\android-studio-ide-171.4195411-windows\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[✓] Android Studio (version 2.3)
    • Android Studio at C:\android-studio\android-studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] Android Studio (version 3.0)
    • Android Studio at F:\android-studio-ide-171.4195411-windows\android-studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[-] IntelliJ IDEA Ultimate Edition (version 2017.2)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.io/intellij-setup/#installing-the-plugins

[✓] Connected devices
    • MIX • a8331689 • android-arm • Android 6.0.1 (API 23)

This looks like https://github.com/flutter/flutter/issues/11681


[FIX]: Responsive directional space

I was also affected by #7 so I decided to have a look at it.
The problem is that the current joinObj method does a shallow merge, which screws up the "media" entries (because those are objects).
Thank you so much @angusfretwell for those tests, they've made the fix super easy. I'm including your commit in my PR, so I guess that if this PR gets merged you should also get credit for your contribution. I hope that's ok with you :wink:

Woohoo, thanks for taking the time to fix this. Glad the tests came in handy!

Thanks, this looks great! I'll probably export util.joinObj and add tests for that as well since it's not currently covered


question about code

Very interesting work! When will the code be released?

Thanks you for your interest in our paper. The code is just released.


Processing for incoming ping requests

When we get a ping, send back a response.

@illicitonion: PTAL

One comment, LGTM, ish :)


Dialog close on navigation

When clicking the browser back button, or the phones back button, an option to close the last opened dialog instead of navigating back a page should be available.
https://v10.material.angular.io/components/dialog/api

closeOnNavigation: boolean
Whether the dialog should close when the user goes backwards/forwards in history. Note that this usually doesn't include clicking on links (unless the user is using the HashLocationStrategy).

I tried to hack together a solution using:
https://developer.mozilla.org/en-US/docs/Web/API/History/pushState

When dealing with back buttons (especially in mobile) this is a router solution, and so out of scope of BeerCSS I should think.
I just managed that myself in my app. Basically, my routing (I'm just using hash-routing as it works, I don't use SSR, and it saves trouble writing the rewrite rules on apache2) will have the path, then a | with additional things, like "dialog=...".
So my player's current URL is https://domain/demo5/#/search|dialog=playQueue&player=default
So instead of relying on the #selector approach or direct calls to ui(), I have my components look at dialog= (only one is allowed at a time) and render that dialog (add the 'active' class) if they have it.  Then close dialog is a 'history.popState()' rather than actively taking any action. route changes, renders re-run, dialog not in url so it goes away.
now some kind of assistance methods might help to better automate this against the dialog IDs so the old ui() and data- approaches could be coded (e.g., global callbacks to indicate that a dialog was opened/closed with its ID). but BeerCSS really shouldn't set/force a policy on routing because it could interfere with the routing systems of libraries that are using it (like react-router-dom) or home-grown routing systems like my own.

When dealing with back buttons (especially in mobile) this is a problem with a router solution, and so is out of scope of BeerCSS I should think.
I just managed that myself in my app. Basically, my routing (I'm just using hash-routing as it works, I don't use SSR, and it saves trouble writing the rewrite rules on apache2) will have the path, then a | with additional things, like "dialog=...".
So my player's current URL is https://domain/demo5/#/search|dialog=playQueue&player=default
So instead of relying on the #selector approach or direct calls to ui(), I have my components look at dialog= (only one is allowed at a time) and render that dialog (add the 'active' class) if they have it. Then close dialog is a 'history.popState()' rather than actively taking any action. route changes, renders re-run, dialog not in url so it goes away.
now some kind of assistance methods might help to better automate this against the dialog IDs so the old ui() and data- approaches could be coded (e.g., global callbacks to indicate that a dialog was opened/closed with its ID). but BeerCSS really shouldn't set/force a policy on routing because it could interfere with the routing systems of libraries that are using it (like react-router-dom) or home-grown routing systems like my own.

This is really interesting, I would like to research this method further, do you have any more reading material on this method? Maybe it's not recommended, but I have some nested dialogs, so expanding this to support that also would be useful for me. I use Nginx and Laravel.

This is a router issue, not Beer CSS itself. You can handle this, with something like that:
// listening to change hash event
window.addEventListener("hashchange", () => {
  closeAllOpenedDialogs();
});

// close all opened dialogs
function closeAllOpenedDialogs() {
   const elements= document.querySelectorAll('dialog.active, dialog[open]');
  for(let i=0; i<elements.length; i++) ui(elements[i]);
}

// added a hash before open a dialog
function openDialog(selector) {
  window.location.hash = "dialog";
  ui(selector);
}


Fix "startstop" function

The function doesn't work when a timer is finished.

Nvm, this is very specific use case.


Convert to latest Swift

Looks good, just one comment to address. Thank you!

Thanks for the catch :) I found no reason there for the map replacement. Map can be used here. I fixed this and also added one fix for Swift 3 which is related to this https://github.com/apple/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md

👍 Thank you very much!


[Chronicles of Darkness] Image not updating on Roll20 VTT

An image was updated in the master branch over 3 weeks ago, but the image loaded in the Roll20 character sheet remains the old one.
Old image
New image
Image displayed in Roll20 VTT:

The complete url used for loading the image in the VTT is https://imgsrv.roll20.net/?src=https%3A//raw.githubusercontent.com/Roll20/roll20-character-sheets/master/Chronicles%2520of%2520Darkness/images/geist.png
The url as set in the source code can be seen here: https://github.com/Roll20/roll20-character-sheets/blob/master/Chronicles of Darkness/CofD.html#L206

Did you try to rename the file and use the new name on the sheet to forcefully update it?

I'd rather not go with a new filename if it can be avoided.

If the point of the question is to see whether there's something wrong with the new file itself, the imgsrv.roll20.net request works just fine if sourced from my repository:
https://imgsrv.roll20.net/?src=https%3A//raw.githubusercontent.com/PrimalZed/roll20-character-sheets/master/Chronicles%2520of%2520Darkness/images/geist.png
(For some reason the request for the image from the Roll20 repository returns a 301 Moved Permanently status code, redirecting to https://s3.amazonaws.com/files.d20.io/images/145490373/NckRfmPHoDwVkDRCIcIhug/max.png while the request for the image from the PrimalZed repository just returns a simple 200 with the image.)

Is renaming the image file the only way to overcome the cache for the VTT? Did I somehow stumble into a isolated issue, or is this a broader systemic issue for updating images used in character sheet templates?
@Reonin Since you previously helped out with a systemic issue (getting a new community sheet alternative to the orphaned "by Roll20" sheet), can I ask you to get eyes on this?

So renaming a file is always a good way to bust a cache but before we go to those as viable solutions want to confirm the cache is not being saved on the browser/client side and a hard refresh doesn't resolve it. If that's still the case I'll bring it up tomorrow and see if anything changes in our caching of sheets.

I've tried it with different browsers, and with incognito and "disable cache" checked. I'm pretty sure that eliminates the possibility of browser caching.

Yeah, and when I looked at the sheet as well, it showed the old image.
Whatever is going on, it's so pervasive that it's happening for multiple people, and need a proper fix, either manually updating the image with new name, or to check whatever is going on with the roll20 image hosting cache.

Hey @PrimalZed  and @Anduh I was able to reach out to the team this week regarding the image cache. For the here and now renaming the image is the only way to update the cache. There are some limitations on the way we host character sheet images that may be changing in the future. If I hear anymore on this I'll you all know!

the issue should be closed, if this is now fixed

I'll close out this issue since we found a workaround I can use, but the root problem that an image used in the character sheets is cached indefinitely is still outstanding.


Add .gitattributes. Remove .gitkeep. Add license

Add .gitattributes so that Github shows Solidity syntax highlighting. I learned about this in Open Zeppelin's repo
Remove .gitkeep files. They were originally added to truffle boxes so that empty directories could be committed to github. Now those directories aren't empty so those files aren't needed.
Add MIT License per the package.json

Awesome! Thanks for the PR :)


stdenv: Better message for deprecated isArm

Also, libgpg-error: Don't use deprecated isArm.
Motivation for this change
The message should say what to do instead.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

Success on x86_64-linux (full log)
Attempted: stdenv
Partial log (click to expand)
/nix/store/i6vl5lwlz5jbkg4r6p340dwmj6fha3xq-stdenv-linux

Success on aarch64-linux (full log)
Attempted: stdenv
Partial log (click to expand)
/nix/store/pjq5v1xgljr4ygb1h1xfybdjydczcqiw-stdenv-linux

Success on x86_64-darwin (full log)
Attempted: stdenv
Partial log (click to expand)
/nix/store/95bw3cdcgc8c0rrvqwvhvc805pdv7rmx-stdenv-darwin


onChange is fired when the value is changed by higher order component

onChange should only be fired when the value of the component was changed, but not if the props.value given from the higher order component was changed. Since the component is controlled, there should be no state to be changed or at least the state has to be resetted when new props are incoming.

@kromit I think this is fixed in 3.0. Have a look at this example, and let me know if you think that it still doesn't behave as expected.


Portainer shows container as healthy despite being stopped and unhealthy

Bug description
A container that has stopped is shown as healthy.

Expected behavior
Should not be shown as healthy at least, maybe as stopped.
Portainer Logs
Provide the logs of your Portainer container or Service.
You can see how here
Steps to reproduce the issue:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Technical details:

Portainer version: 2.9.2
Docker version (managed by Portainer): Standalone 20.10.9
Kubernetes version (managed by Portainer):
Platform (windows/linux): Linux
Command used to start Portainer (docker run -p 9443:9443 portainer/portainer):
Browser: Microsoft Edge
Use Case (delete as appropriate): Using Portainer at Home
Have you reviewed our technical documentation and knowledge base? No

Additional context
Add any other context about the problem here.

@agneevX
That is weird. Can you check using a different browser or after clearing cache to see if that is a caching issue?

Can you confirm what the health check is and the interval please?

# compose.yml
    healthcheck:
      test: ["CMD", "curl", "localhost:5055", "-fso", "/dev/null"]

Can you check using a different browser or after clearing cache to see if that is a caching issue?

It was the same in incognito. Now of course, once I realized that the container wasn't functional, I stated it back up.

Closing until I get the chance to check this without a healthcheck, since it cannot be reproduced.

I had this same issue yesterday: The container was shown as "healthy" in the overview, when in fact it was unhealthy/stopped, which is also what was reported when looking at its details page. Seeing the request for more debug information here, I tried to save plenty of data from this state, which I'm happy to share.
Regarding the healthcheck config, this is what it looks like in this case:
"Healthcheck": {
	"Interval":<PHONE_NUMBER>0,
	"Retries": 3,
	"StartPeriod":<PHONE_NUMBER>0,
	"Test": [
		"CMD",
		"ak",
		"healthcheck"
	],
	"Timeout":<PHONE_NUMBER>0
},

... which I must admit makes no sense as 30 billion seconds is almost 1000 years, but don't blame me, I didn't set this up :P
But still, to me it's not convincing that when one part of Portainer (the details page) knows that the container is down, that another part (the overview) still shows it as healthy...
I wasn't able to test it in another browser to rule out caching issues, but to be honest if it was related to caching, I'd argue that this is still a bug as caching shouldn't affect these real-time information in the first place.
@samdulam or anyone else willing to look into it: Please let me know what other information you need (and maybe reopen the issue?) -- I copied the entire "container inspect" but don't want to just paste the whole thing here.
NB: I'm a very novice Portainer user and my knowledge of Docker is not as novice but certainly not expert either.

@christophfriedrich
Thanks for the info. I'll raise this with engineering internally and get back to you when I have an update.


[Question]: 1] ImportError: cannot import name 'session' from 'llama_index.core.workflow'

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
cannot import session from the standard 'llama_index.core.workflow'
Error message : 1] ImportError: cannot import name 'session' from 'llama_index.core.workflow' (/venv/lib/python3.11/site-packages/llama_index/core/workflow/init.py)

@Tisha-linkenite where did you see this import? This concept was removed, everything is bundled into the Context object now


Add an e2e test for the device plugin feature

Our e2e tests currently do not verify anything related to the device plugin feature. We should create a dummy device plugin for the CI module and verify that the information is properly exposed to the kubelet.

Tracked in Red Hat ITS as MGMT-10538.


bump nscala to 2.10.0 and joda to 2.9.2

nscala-time resolves most of our needs (especially in data products) in terms of date time operations. However, the old versions were missing some of the functionalities that we often use. Recently, I have updated nscala-time meet some of these requirements, and I wanted this to be available across the projects and hence this PR.
https://github.com/nscala-time/nscala-time/pull/99
https://github.com/nscala-time/nscala-time/issues/100
It seems we have unusually complex codes (in data products stash repositories) to handle date-time operations regardless of the simplicity in the use-cases it tries to solve. This PR is the first step forward..

@stephanh could you please review this ?

Can you please update the PR comment with why you want the later versions of nscala/joda time?

@stephanh I have updated the description. Hope it makes sense :)

:+1:


add a cool banner logo to sites

We should have a cool banner logo for our sites. We can add this to the README.md our crates.io docs, etc. Something similar to:

@chrisaddy I think you're missing the example content in the issue.

Closing due to priority.


in Playground Make images bigger by Mousing Over or Click

In the playground, some images show off too small, so it would be convenient to have a way to enlarge them either by mousing over or by clicking on it to open a pop-up.

bold up the intents which are not saved


Something went wrong :/ No module named 'psutil'

When trying to add a .md file as a document, this error appears Something went wrong :/ No module named 'psutil'
Open WebUI Version (DOCKER)
v0.3.8

Should be fixed with the latest, let me know if the issue persists!


[Windows] Tray keeps crashing

It crashes periodically without any activity. However it is worst when generating an SSH key.

done in dev


Globally remember advanced toggle in project settings

Currently the Advanced button in Project Settings dialog is remembered per project.
It's safe to assume that when you enable it, you are an advanced user and want to see more settings. And if you enable it in one project, it's safe to assume that you are advanced user in any project.
This PR makes the option remembered globally for all projects.
Originally discussed here: https://github.com/godotengine/godot/pull/96467#discussion_r1741121165

Thanks!


Add transpose_kernel argument to ConvTranspose.

This is a proposal for #2577, adding a transpose_kernel option to ConvTranspose such that the previous behavior is maintained by default.

Add an additional transpose_kernel parameter to ConvTranspose which is passed to jax.lax.conv_transpose
For  padding='CIRCULAR': To maintain the previous convention of ConvTranspose, the alignment of the kernel is changed depending on transpose_kernel.# Divide the padding equally between left and right. The choice to put
# "+1" on the left (or on the right) represents a convention for
# aligning even-sized kernels.
if self.transpose_kernel:
  # match convention in Conv to achieve the proper transpose
  total_pad = [
     (size_diff // 2, (size_diff + 1) // 2) for size_diff in size_diffs
  ]
else:
  # keep the previous convention for backward compatibility
  total_pad = [
     ((size_diff + 1) // 2, size_diff // 2) for size_diff in size_diffs
  ]

Codecov Report

Merging #2578 (062eed3) into main (7d21975) will decrease coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2578      +/-   ##
==========================================
- Coverage   79.50%   79.42%   -0.08%
==========================================
  Files          49       49
  Lines        5206     5162      -44
==========================================
- Hits         4139     4100      -39
+ Misses       1067     1062       -5

Impacted Files
Coverage Δ

flax/linen/linear.py
97.55% <100.00%> (+0.04%)
:arrow_up:

flax/core/nn/linear.py
42.34% <0.00%> (-0.52%)
:arrow_down:

flax/struct.py
78.12% <0.00%> (-0.34%)
:arrow_down:

flax/core/scope.py
89.72% <0.00%> (-0.07%)
:arrow_down:

flax/core/lift.py
95.81% <0.00%> (-0.07%)
:arrow_down:

flax/linen/normalization.py
97.08% <0.00%> (-0.05%)
:arrow_down:

flax/core/frozen_dict.py
96.19% <0.00%> (-0.04%)
:arrow_down:

flax/linen/summary.py
99.00% <0.00%> (-0.01%)
:arrow_down:

flax/traverse_util.py
99.01% <0.00%> (-0.01%)
:arrow_down:

flax/linen/recurrent.py
100.00% <0.00%> (ø)

... and 5 more

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

@mathisgerdes @cgarciae this PR has build failures so I have removed the "pull ready" label. Could you please fix those first?

@mathisgerdes @cgarciae this PR has build failures so I have removed the "pull ready" label. Could you please fix those first?

I believe those were problems with the previous commit, not any changes here. I've rebased to the latest commit.

Is there still something to be done here, @cgarciae, @andsteing?


Is this project currently maintained?

Is this project currently maintained?
Do I have to open any additional ports on my Linux server?
Can I use this API to add transactions to the Ropsten Testnet?

Can I use this to interact via infura server?

Many questions:

Yes. I will have time to work on it again soon.
No. You don't need to run you own Ethereum node.
No. "Add transactions" means "signing with your private key". This is currently out of scope of the library. The first scope of ethereum-php is a "pull data from Ethereum" approach. Please have a look here: http://slides.com/digitaldonkey/drupal-ethereum#/20 But It might be implemented later.
Yes.

Is there a PHP ethereum API or SDK that allows you to add transactions?
I don't want to sync, so it must be a light-client.
I don't want to open any additional ports on my Linux server.
I need to add transactions to the Ropsten Testnet.
There can't be any limits to requests (such as 200 requests per hour), and there can't be a monthly fee.

Seems you have a lot of work in front of you :)


Add a test of #399

Fixing this will likely require a sizeable rewrite of the monomorphization system. The fundamental problem is MonoTy, a shameful hack that has predictably ruined everything.

Narrator: it did not, in fact, require a big rewrite of the monomorphization system.


Auto-determine a sane value for camera bufs based on camera FPS, if possible

Might still need to check whether there's a useful v4l2 ioctl for this that I can directly query; previously I may only have been looking at what the v4l2capture module exposes.

This needs a bump.
Basically if we want to be able to withstand a 1-second hangup on consumption of frames by the tracker, and we're hypothetically capturing at 15 fps, then we need 15 buffers to satisfy that 1-second worst-case condition.
The problem right now is that, after looking into the available IOCTLs from V4L2, and implementing both VIDIOC_ENUM_FRAMEINTERVALS and VIDIOC_G_PARM (each of which should be able to give framerate information), our webcam and/or driver seems to be incapable of returning any such information.
I really want to get rid of that obnoxious mandatory --camera-bufs command line argument though, so I may just make it optional and set an arbitrary default that's, like, really high. If it's too high, then the VIDIOC_REQUESTBUFS IOCTL will just give us fewer than we asked for. And we can have the default be like 100 or whatever, it doesn't really matter as long as it's a reasonably high figure, since we seem to be incapable of basing it on Real Information such as the camera's framerate.

Webcam has been retired from our hardware lineup so this is no longer a priority.


Add support for Python Notebooks (.ipynb) files

Description
Support for coding in Jupyter notebook files properly (with cells etc.)
Alternatives Considered
No response
Additional Context
No response
Screenshots
No response

Isn't this a duplicate of #830 ?

Isn't this a duplicate of #830 ?

Yes


Rreasonable loss of pre-training (Stage-1) loss.

Question
Thank you for your wonderful work,
May I know the reasonble loss of LLaVA during the 1-st stage of pre-training?

Hi, we have provided all training logs in MODEL ZOO for LLaVA-1.5. You can check out the figure.
https://github.com/haotian-liu/LLaVA/blob/main/docs/MODEL_ZOO.md#llava-v15
Training logs: wandb.

Thanks!


Make strings for the current language and language switching available on Rust side

Currently, the Rust side cannot access any translations. These are only available in the frontend.
Ideally, the frontend should send the translations to the Rust side on startup, as well as whenever the language is changed.
The Rust side should be able to update its shown translations (e.g. for the system tray from #22) whenever the active language is updated.

Maybe this is best suited for a tauri command?
see https://tauri.app/v1/guides/features/command
could just have a command that tells rust what lang to use and go from there

Oh yeah it very much is. How to get things from/to the Rust side isn't really an issue.
OyasumiVR already makes heavy use of Tauri commands (and events). Barely anything it does would be possible without any native functionality written in Rust.
The complexity comes more from how to structure this in a sane and generic way: You ideally only want to have a single source of translations, have the ability to update everything on the fly while keeping things in sync, and have it be a solution that is generic enough that it can be reused for various (future) translations, e.g. not just the system tray.
It's likely not rocket science, but it's mostly a nice to have, and for me personally, the gain of looking into it currently isn't worth the time that I could spend on improving OyasumiVR elsewhere.


Add modal component and tree modal

Description
When you hover over the tree name column your cursor will now turn into a pointer, and you can click on any of the (icon | name | external link icon) to pop up a modal!

Once the backend part is added, then we can simply pass the right link to the Confirm button.
Relies on #233.
Issue
ch120777
Test plan
Go to tree table, click on a name; test that both the confim and cancel buttons work.

In order to resolve the merge conflicts and rebase from trunk, I created a new branch/PR here to replace this one!
PTAL thank you!

https://github.com/chanzuckerberg/aspen/pull/253 is merged!


Any way to pull upcoming opponents?

New to nflgame (and python/programming), thanks for setting all this up.
I've built a simple scoring system to rank players for the upcoming week, but it relies on season-to-date statistics measuring the opponent's strength vs. the run and pass.
Is there a way to pull opponents for games in the upcoming week? The code below only works for games that have already been played.
Alternatively, can someone point me to how I'd scrape a website like this?: http://www.nfl.com/liveupdate/scorestrip/scorestrip.json
import nflgame
import pandas as pd

current_year = 2016
current_week = 11

next_opp = pd.DataFrame() # empty

games = nflgame.games(current_year,current_week)
for g in games:
    home_first = pd.DataFrame({
        'year' : current_year,
        'week' : current_week,
        'team' : g.home,
        'opp' : g.away
        }, index = [str(current_year)+'/'+str(current_week)+ '/'+ g.home])
    away_first = pd.DataFrame({
        'year' : current_year,
        'week' : current_week,
        'team' : g.away,
        'opp' : g.home
        }, index = [str(current_year)+'/'+str(current_week)+ '/'+ g.away])
    next_opp = pd.concat([next_opp, home_first, away_first])
    del home_first
    del away_first

You can get this from nfldb:
weeknumber = 15

db = nfldb.connect()
q = nfldb.Query(db).game(week=weeknumber, season_year=2016)

for game in q.as_games():
#     print game
    fixtures[game.home_team] = game.away_team
    fixtures[game.away_team] = game.home_team

print fixtures

{'MIN': 'IND', 'MIA': 'NYJ', 'CAR': 'WAS', 'ATL': 'SF', 'DET': 'NYG', 'CIN': 'PIT', 'NYJ': 'MIA', 'DEN': 'NE', 'BAL': 'PHI', 'NYG': 'DET', 'OAK': 'SD', 'TEN': 'KC', 'NO': 'ARI', 'DAL': 'TB', 'NE': 'DEN', 'SEA': 'UNK', 'CHI': 'GB', 'TB': 'DAL', 'PIT': 'CIN', 'CLE': 'BUF', 'HOU': 'JAC', 'GB': 'CHI', 'UNK': 'SEA', 'WAS': 'CAR', 'JAC': 'HOU', 'KC': 'TEN', 'PHI': 'BAL', 'BUF': 'CLE', 'IND': 'MIN', 'ARI': 'NO', 'SF': 'ATL', 'SD': 'OAK'}

The info exists in nflgame as well.  It's just not as conveniently exposed as previous games.
import nflgame

past_games = nflgame.games(2016, 10)
for game in past_games:
    print game

print '-'

future_games = nflgame.live._games_in_week(2016, 11)
for game in future_games:
    print '{} at {} on {}/{} {}'.format(game['away'], game['home'], game['month'], game['day'], game['time'])

CLE (7) at BAL (28)
KC (20) at CAR (17)
HOU (24) at JAX (21)
DEN (25) at NO (23)
LA (9) at NYJ (6)
ATL (15) at PHI (24)
CHI (10) at TB (36)
GB (25) at TEN (47)
MIN (20) at WAS (26)
MIA (31) at SD (24)
SF (20) at ARI (23)
DAL (35) at PIT (30)
SEA (31) at NE (24)
CIN (20) at NYG (21)
-
NO at CAR on 11/17 8:25
BUF at CIN on 11/20 1:00
PIT at CLE on 11/20 1:00
BAL at DAL on 11/20 1:00
JAX at DET on 11/20 1:00
TEN at IND on 11/20 1:00
TB at KC on 11/20 1:00
ARI at MIN on 11/20 1:00
CHI at NYG on 11/20 1:00
MIA at LA on 11/20 4:05
NE at SF on 11/20 4:25
PHI at SEA on 11/20 4:25
GB at WAS on 11/20 8:30
HOU at OAK on 11/21 8:30

EDIT to above: I notice that with that sample code a game that has already happened this week (ie. NO @ CAR) appears in both lists.  Fixing that is easy enough, but the code gets a bit uglier :)
import nflgame

past_games = nflgame.games(2016, 11)
for game in past_games:
    print game

print '-'

future_games = [game for game in nflgame.live._games_in_week(2016, 11) if game['eid'] not in [g.eid for g in past_games]]
for game in future_games:
    print '{} at {} on {}/{} {}'.format(game['away'], game['home'], game['month'], game['day'], game['time'])

Exactly what I needed, thanks!


Configure Hound CI

Some of the code (if not most) is written using single quotes. Hound CI complains every time someone submits a pull request with single quotes. I think we should pick one style and stick to it. I could submit a pull request with these changes, that will include converting all code to one style and adding Rubocop and Hound CI config files to the repo.

Yes please, its annoying. I prefer single quotes ' instead of hounds configuration. If you like to do it, it would be a good improvement. I will not merge any other PR to avoid the conflict trouble.

@rocknruby Fixed this in Pull request #253.

@itsdn - sweet thank you


fix(docs): wrong trigger name under cognito-user-pool

Fixes #538

Thanks!

Thanks @EduSantosBrito! Will be in the next release.


docs: Add link to the thread describing a successful migration from 14.04 to 16.04

Testing Plan:
GIFs or Screenshots:

Not sure if I should use url-shortener or disable lint on the file.

My leaning is towards documenting this upgrade process properly.

Closing, since we added proper documentation based on that thread several months ago.


Fix handling node state

This fixes 2 issues:

On "node ready" event a full state of the node is dumped including values. The new values were not stored and thus HA discovery was failing when a new node was added to the mesh.
When a node is in the process of being added, first a partial node state is sent, missing most values. Once the interview progresses/completes these values come in. So basically all attributes for the Node model are optional to account for this behaviour.

Fixes HA issue: https://github.com/home-assistant/core/issues/45631

It would be good to add tests for these cases mentioned in the description.

It would be good to add tests for these cases mentioned in the description.

It would be good to add tests for these cases mentioned in the description.

How? The info is completely random. Sometimes values XYZ included, sometimes not.
We have to assume a dict with node_id as bare minimum and more info comes in later.

It would be good to add tests for these cases mentioned in the description.

How? The info is completely random. Sometimes values XYZ included, sometimes not.
We have to assume a dict with node_id as bare minimum and more info comes in later.

We simulate the conditions mentioned above.

We simulate the conditions mentioned above.

We simulate the conditions mentioned above and make sure the library acts appropriately.

OK, again, how ? I have no idea. You're the tests wizard ;-)

We simulate the conditions mentioned above and make sure the library acts appropriately.

OK, again, how ? I have no idea. You're the tests wizard ;-)

this is what happens btw:

node inclusion started
node added event with limited node object (no values and not all keys there)
node read event (all/most keys there and values list)

this is what happens btw:

node inclusion started
node added event with limited node object (no values and not all keys there)
node read event (all/most keys there and values list)

Yes, exactly. Create a node with some minimum state. Then receive the node ready event with needed data and assert that values are updated ok.

Yes, exactly. Create a node with some minimum state. Then receive the node ready event with needed data and assert that values are updated ok.

test added

test added


Separate out Fauxton compilation from core CouchDB

This separates compilation of core CouchDB from compilation of Fauxton. I'm not attached to the name compile-core, and it might also be worth changing the target fauxton to compile-fauxton.

+1

+1

Merged.


Add almost unified for ores

Completed with https://github.com/Conquerix/The-InBetween/commit/882993ecf10a3f7a0972c5299496db12207d251c


Adds reference emission flag

Note for observers: this is a private, temporary change to accommodate an internal need at Netflix, and this behavior will not be ported to 2.x+.

LGTM.


fix tensorflow version on non-gpu version and fix tfjs version

this rely on tensorflow stable and tensorflowjs 0.8.6

NOTE: I only tested it on non-gpu version

I signed the CLA


MaxListenersExceededWarning

Describe the bug
I get an error when running my tests
To Reproduce
Steps to reproduce the behavior:

Clone https://github.com/kaaaxcreators/Discord-MusicBot
Switch to Branch 'test'
Install Packages
Run script test
see error

Expected behavior
every test case should succeed
Desktop (please complete the following information):

OS: Windows 10
Terminal: Powershell
Corde version: 4.1.0

Additional context
Log: ```
● BeforeStartError: timeout

    at Object.<anonymous> (dist\test\bot.test.js:5:9)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)

(node:1584) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners()
to increase limit
(Use node --trace-warnings ... to show where the warning was created)
Test Files: 1 failed. 1 total
Tests:      18 failed. 18 total
Time:       22.75s
The Bot sends messages but still fails

hmm, It seems like beforestart hook is not handling the timeout value defined in configs. I'm going to take a look at that.

hey @kaaax0815, upgrade corde's version to 4.1.1 😊

Running corde throws this error: _pathsDir.filter is not a function. literally nothing else

@lucasgmagalhaes after updating corde throws this error: _pathsDir.filter is not a function

Fixed in 4.1.2 @kaaax0815

Log in 4.1.2 (new package-lock and node_modules)

    ● BeforeStartError: timeout

        at Object.<anonymous> (dist\test\bot.test.js:5:9)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)

(node:10196) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)

Test Files: 1 failed. 1 total
Tests:      18 failed. 18 total
Time:       20.927s

Can you try to delete node_modes and reinstall it?

As I said I already did that

Ok, Sorry

Ok, Sorry

Dont have to say sorry
Do you maybe know why this happens or is it maybe me bot architectur

@kaaax0815, corde was expecting the property timeOut, not timeout as is in your config. I've renamed corde to use the nomenclature that you are using (which is the correct one). It's in version 4.2.0

The BeforeStartError error is now gone, the MaxListeners is still there unfortunately though
(node:14140) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)

Test Files: 1 failed. 1 total
Tests:      18 failed. 18 total
Time:       20.725s

@kaaax0815  looks like that the problem is in yours commands. invite command is throwing an invalid URL.
Unhandled Rejection at:  Promise {
  <rejected> [    at toReturn processTicksAndRejections (node:internal/process/task_queues:96:5)] {
    name: 'DiscordAPIError',
    message: 'Invalid Form Body\n' +
      'embed.url: Not a well formed URL.\n' +
      'embeds[0].url: Not a well formed URL.',
    method: 'post',
    path: '/channels/522581719568744470/messages',
    code: 50035,
    httpStatus: 400
  }

@kaaax0815 looks like that the problem is in yours commands. invite command is throwing an invalid URL.
Unhandled Rejection at:  Promise {
  <rejected> [    at toReturn processTicksAndRejections (node:internal/process/task_queues:96:5)] {
    name: 'DiscordAPIError',
    message: 'Invalid Form Body\n' +
      'embed.url: Not a well formed URL.\n' +
      'embeds[0].url: Not a well formed URL.',
    method: 'post',
    path: '/channels/522581719568744470/messages',
    code: 50035,
    httpStatus: 400
  }

Thats also possible because you didnt send every env var. because if i run my bot without corde the command works fine

This is the log from Github Actions (it has more infos, but is weirdly censored)
Run np*** run test:only

><EMAIL_ADDRESS>test:only /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot
> corde

- login to corde bot
[90***2021-07-01 15:14:09.681 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:100][39*** Loading Event: ***essage
[90***2021-07-01 15:14:10.443 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:100][39*** Loading Event: ready
[90***2021-07-01 15:14:10.448 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: earrape
[90***2021-07-01 15:14:10.450 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: leave
[90***2021-07-01 15:14:10.452 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: loop
[90***2021-07-01 15:14:10.584 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: lyrics
[90***2021-07-01 15:14:10.588 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: nowplaying
[90***2021-07-01 15:14:10.590 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: pause
[90***2021-07-01 15:14:10.904 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: play
[90***2021-07-01 15:14:10.913 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: playlist
[90***2021-07-01 15:14:10.915 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: queue
[90***2021-07-01 15:14:10.917 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: radio
[90***2021-07-01 15:14:10.919 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: re***ove
[90***2021-07-01 15:14:10.921 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: resu***e
[90***2021-07-01 15:14:10.923 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: search
[90***2021-07-01 15:14:10.925 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: shuffle
[90***2021-07-01 15:14:10.927 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: skip
[90***2021-07-01 15:14:10.929 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: skipto
[90***2021-07-01 15:14:10.931 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: stop
[90***2021-07-01 15:14:10.933 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:117][39*** Loading Music Co***and: volu***e
[90***2021-07-01 15:14:10.936 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:134][39*** Loading General Co***and: count
[90***2021-07-01 15:14:10.938 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:134][39*** Loading General Co***and: help
[90***2021-07-01 15:14:10.939 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:134][39*** Loading General Co***and: invite
[90***2021-07-01 15:14:10.941 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:134][39*** Loading General Co***and: ping
[90***2021-07-01 15:14:10.943 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:134][39*** Loading General Co***and: prefix
[90***2021-07-01 15:14:10.945 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:134][39*** Loading General Co***and: serverstats
[90***2021-07-01 15:14:10.948 [39***[1***[94***INFO[39***[22*** [90***[src/index.ts:134][39*** Loading General Co***and: stats
[90***2021-07-01 15:14:11.204 [39***[1***[94***INFO[39***[22*** [90***[src/events/ready.ts:34][39*** [API] Logged in as kaaaxTest
 RUNS   dist/test/bot.test.js
 RUNS   dist/test/bot.test.js
   ● various co***ands should return sa***evc
 RUNS   dist/test/bot.test.js
   x ***usic co***ands -> various co***ands should return sa***evc   7.796s
 RUNS   dist/test/bot.test.js
   x ***usic co***ands -> various co***ands should return sa***evc   7.796s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

 RUNS   dist/test/bot.test.js
   x ***usic co***ands -> various co***ands should return sa***evc   7.796s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:15:35

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:15:35

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:15:35

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:16:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:16:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:16:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:17:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:17:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:17:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:18:34

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:18:34

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:18:34

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:19:34

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:19:34

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:19:34

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:20:35

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:20:35

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:20:35

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:21:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:21:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:21:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:22:36

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:22:36

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:22:36

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:23:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:23:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:23:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:24:34
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:23:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:24:34
   ● various co***ands should return novc
(node:1656) MaxListenersExceededWarning: Possible EventE***itter ***e***ory leak detected. 12 unhandledRejection listeners added to [process]. Use e***itter.setMaxListeners() to increase li***it
(Use `node --trace-warnings ...` to show where the warning was created)
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:23:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:24:34
   x ***usic co***ands -> various co***ands should return novc   6.369s
    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:24:34
   x ***usic co***ands -> various co***ands should return novc   6.369s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in the sa***e voice channel a
s ***e!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:24:34
   x ***usic co***ands -> various co***ands should return novc   6.369s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:32:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:32:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:32:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:33:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:33:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:33:32

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:34:36

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:34:36

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:34:36

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:35:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:35:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:35:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:36:34
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:35:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:36:34
   ● count
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:35:33

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:36:34
   x ***ainco***ands -> count   5.592s
    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:36:34
   x ***ainco***ands -> count   5.592s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 16776960,
    +   "color": "YELLOW",
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    + Received  + 1

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:36:34
   x ***ainco***ands -> count   5.592s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 16776960,
    +   "color": "YELLOW",
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:46:33

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:36:34
   x ***ainco***ands -> count   5.592s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 16776960,
    +   "color": "YELLOW",
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:46:33
   ● invite

      Object {
    -   "color": 15158332,
    +   "color": "RED",
        "description": "I'*** sorry but you need to be in a voice channel to play
***usic!",
        "footer": "So***ething went wrong :(",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:36:34
   x ***ainco***ands -> count   5.592s

    - Expected  - 1
    + Received  + 1

      Object {
    -   "color": 16776960,
    +   "color": "YELLOW",
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:46:33
   x ***ainco***ands -> invite   194***s
    -   "color": 16776960,
    +   "color": "YELLOW",
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:46:33
   x ***ainco***ands -> invite   194***s

    - Expected  - 3
    + Received  + 2

      Object {
    -   "color": 3447003,
    +   "color": "BLUE",
        "description": "Want ***e in your server? Invite ***e today!

    -  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
283796&per***issions=2205281600&scope=bot)",
    +  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
2837966&per***issions=2205281600&scope=bot)",
        "title": "Invite kaaaxTest",
    -   "url": "https://discord.co***/oauth2/authorize?client_id=78202575737428379
6&per***issions=2205281600&scope=bot",
      }

    +   "color": "YELLOW",
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:46:33
   x ***ainco***ands -> invite   194***s

    - Expected  - 3
    + Received  + 2

      Object {
    -   "color": 3447003,
    +   "color": "BLUE",
        "description": "Want ***e in your server? Invite ***e today!

    -  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
283796&per***issions=2205281600&scope=bot)",
    +  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
2837966&per***issions=2205281600&scope=bot)",
        "title": "Invite kaaaxTest",
    -   "url": "https://discord.co***/oauth2/authorize?client_id=78202575737428379
6&per***issions=2205281600&scope=bot",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:56:34
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:46:33
   x ***ainco***ands -> invite   194***s

    - Expected  - 3
    + Received  + 2

      Object {
    -   "color": 3447003,
    +   "color": "BLUE",
        "description": "Want ***e in your server? Invite ***e today!

    -  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
283796&per***issions=2205281600&scope=bot)",
    +  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
2837966&per***issions=2205281600&scope=bot)",
        "title": "Invite kaaaxTest",
    -   "url": "https://discord.co***/oauth2/authorize?client_id=78202575737428379
6&per***issions=2205281600&scope=bot",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:56:34
   ● test didyou***ean suggestion
        "description": "The Bot is currently in 2 Servers",
        "footer": "Use ***invite to add/invite the Bot to your server",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:46:33
   x ***ainco***ands -> invite   194***s

    - Expected  - 3
    + Received  + 2

      Object {
    -   "color": 3447003,
    +   "color": "BLUE",
        "description": "Want ***e in your server? Invite ***e today!

    -  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
283796&per***issions=2205281600&scope=bot)",
    +  [Invite Link](https://discord.co***/oauth2/authorize?client_id=782025757374
2837966&per***issions=2205281600&scope=bot)",
        "title": "Invite kaaaxTest",
    -   "url": "https://discord.co***/oauth2/authorize?client_id=78202575737428379
6&per***issions=2205281600&scope=bot",
      }

    at toReturn /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/test/bo
t.test.js:56:34
   x didyou***ean -> test didyou***ean suggestion   230***s

    - Expected  - 5
    + Received  + 4

      Object {
    -   "color": "DARK_VIVID_PINK",
    +   "color": 11342935,
        "description": "Did you ***ean `play`?",
        "fields": Array [
          Object {
    -       "na***e": "Description",
    +       "inline": false,
    +       "na***e": "Description:",
            "value": "Play a Song",
          },
        ],
    -   "footer": Object {
    -     "text": "kaaaxCorde",
    -   },
    +   "footer": "kaaaxCorde",
        "title": "🤔 didyou***ean",
      }

    - Expected  - 5
    + Received  + 4

      Object {
    -   "color": "DARK_VIVID_PINK",
    +   "color": 11342935,
        "description": "Did you ***ean `play`?",
        "fields": Array [
          Object {
    -       "na***e": "Description",
    +       "inline": false,
    +       "na***e": "Description:",
            "value": "Play a Song",
          },
        ],
    -   "footer": Object {
    -     "text": "kaaaxCorde",
    -   },
    +   "footer": "kaaaxCorde",
        "title": "🤔 didyou***ean",
      }

    at toE***bedMatch /ho***e/runner/work/Discord-MusicBot/Discord-MusicBot/dist/tes
t/bot.test.js:70:31

Test Files: 1 failed. 1 total
Tests:      18 failed. 18 total
Ti***e:       20.373s
np*** ERR! code ELIFECYCLE
np*** ERR! errno 1
np*** ERR<EMAIL_ADDRESS>test:only: `corde`
np*** ERR! Exit status 1
np*** ERR!
np*** ERR! Failed at the<EMAIL_ADDRESS>test:only script.
np*** ERR! This is probably not a proble*** with np***. There is likely additional logging output above.

np*** ERR! A co***plete log of this run can be found in:
np*** ERR!     /ho***e/runner/.np***/_logs/2021-07-01T15_14_55_068Z-debug.log
Error: Process co***pleted with exit code 1


DapperRepository method missing CancellationToken override.

@pengweiqhca Can you raise a PR?

@pengweiqhca I reverted changes in main branch. I see that you add tt and generated files. Can you remove these templates, clean up and raise PR again?

Merged