Add missing row duplication event handler

Nested tables show the duplicate option in the row actions, but the event triggered by clicking it is not handled, so the model is never duplicated. This PR fixes that by matching the functionality seen in TableRow.vue.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Remove interactive_move_point_3d.py example as moving poin in 3d has natove support

Description

Based on information from @alisterburt This example is no longer needed because of native support.
It is also not working as import contains project_points_onto_plane and code calls project_point_onto_plane (one s of difference). So I think that in such a situation, it is better to remove it rather than try to fix it.
Type of change

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

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

for the main branch I remove this file in #5275


Don't allow a range selection in the table to begin with a row that was deselected

Pull Request
🤨 Rationale
Resolves #2239
👩💻 Implementation
The desired multiselect behavior is that a row will only be considered the start of a shift-select range if that row was being selected (either via selection checkbox or via clicking the row), but it will not be considered the start of a shift-select range if that row was deselected.
To achieve this behavior, I've updated the MultiSelectionManager to assign the current row ID to shiftSelectStartRowId only if the row is being selected. If the row is being deselected, shiftSelectStartRowId is reset to undefined.
🧪 Testing

Manually tested in storybook, including keyboard selection
Added two new unit tests

✅ Checklist

[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.

@m-akinc, can you buddy this PR for me?

Think we should have @jattasNI or @fredvisser verify the interactions on Safari mac + maybe also Chrome/ Firefox mac


Cannot find app.module.ts file in project generated by CLI

I can't believe I'm going to be that guy that drives everyone nuts and posts a question in the issues, but I've done absolutely everything I can think of and still can't find the app.module.ts file for my project -- in fact, I can't find any files at all in the project that contain an import for NgModule at all!
 Does anybody have a second to explain my mistake?
angular-cli: 0.0.39
node: 5.3.0
os: darwin x64 (OS X 10.11.6)

Now I noticed that you have 0.0.39 reported in your version. (Thank you this was very helpful to potentially identify your issue). I would recommend that you update the angular-cli to the latest version npm install angular-cli@webpack -g
You can refer to our WEBPACK UPGRADE docs to properly migrate.
Also if you create a new app you will find the app.module.ts located in the app folder of your src.


[FLINK-7430] Set StreamTask.isRunning to false after closing StreamOperators

What is the purpose of the change
Closing StreamOperators is still part of the StreamTask's running lifecycle,
because operators which perform asynchronous operations usually finish their
work when the StreamOperator is closed. Since this also entails that errors
can occur and that a checkpointing operation is triggered, we should only set
the StreamTask's isRunning to false after all StreamOperators have been closed.
Furthermore, this commit introduces a while guard for the waiting condition in
ContinuousFileReaderOperator#close.
R @aljoscha.
Brief change log

Set StreamTask#isRunning to false after all operators have been closed
Use while loop instead of if condition for guarding synchronization in ContinuousFileReaderOperator#close

Verifying this change
This change added tests and can be verified as follows:

StreamTaskTest#testOperatorClosingBeforeStopRunning verifies that StreamTask#isRunning == true when the close method of the StreamOperators is called.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
Affects the StreamTask lifecycle

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Code looks good! I think you can merge as soon as travis is green.
Excellent, that you added a test. And it's quite concise with the new Java 8 magic. 😃

Thanks for the review @aljoscha. Travis passed. Merging this PR.


Fix copy/paste errors.

Looks like the description for find_config_file() was copy/pasted and not fully updated.

Thanks!


fix: load ts config file synchronously

This PR makes config loading from a TS file synchronous.
Fix #290

LGTM, thanks @alvis :)

Released in<EMAIL_ADDRESS>

It doesn’t work. I don’t know if it’s the version of ts-node. The version of ts-node is not indicated here.
Below is my error：
export default {
^^^^^^
SyntaxError: Unexpected token 'export'

@Sneaken could you share your tsconfig.json?
seems like you have set module other than 'commonjs', which is required by ts-node to work.


[BUG] - I cannot download the YouTube videos from some video stream URLs

I am using a function to download a video at a specific URL which relies on YouTubeKit:
    func download(to directoryURL: URL) async {
        downloading = true
        defer { downloading = false }

        // Make sure thre URL exists
        if videoURL.isEmpty {
            error = "Please provide a URL"
            return
        }
        guard let url =  URL(string: videoURL) else {
            error = "Could not parse you input to a URL"
            return
        }

        // Make the YouTube video
        let video = YouTube(url: url)
        guard let videoTitle = try? await video.metadata?.title else {
            self.error = "Could not get video title"
            return
        }
        // get the streams and filter for highest resolution
        do {
            let streams = try await video.streams

            guard let stream = audioOnly ? streams.highestAudioBitrateStream() : streams.highestResolutionStream() else {
                self.error = "Could not get the highest stream resolution"
                return
            }

            // Download the video
            let url = stream.url
            print("URL is \(url.absoluteString)")

            do {
                let (data, _) = try await URLSession.shared.data(from: url)
                let fileURL = directoryURL.appendingPathComponent(videoTitle, conformingTo: audioOnly ? .mpeg4Audio : .mpeg4Movie)
                print("File URL = \(fileURL.relativePath)")
                try! data.write(to: fileURL)
                print("SUCCESS!")
            } catch {
                self.error = "Could not write the video data to disk"
            }

        } catch {
            self.error = "Could not get video streams"
        }
    }

However when videoURL = "https://www.youtube.com/watch?v=byrRbWGN1Nk&t=2s" the url links gives me a 403 code which of course means the video cannot be downloaded.
However with other videos, eg: https://www.youtube.com/watch?v=kOf54RdoH7A the video will download.
You mentioned this project corresponds somewhat with Pytube for Python: I tested the same (broken) video URL with Pytube on Python and the video URLs both libraries gave were similar but different.
Here is the video URL from YouTubeKit (https://www.youtube.com/watch?v=byrRbWGN1Nk&t=2s): https://rr4---sn-cu-h5oe7.googlevideo.com/videoplayback?expire=1717471505&ei=sTReZu2JGLXYxN8P9IStmAc&ip=2a00%3A23c6%3A8916%3A4601%3A3ccd%3A97d2%3A584%3Ab609&id=o-AMh2onJ7kBeM1TcBSzEH3AHwi3RxBvc1g5MIfnOf5w_f&itag=313&aitags=133%2C134%2C135%2C136%2C137%2C160%2C242%2C243%2C244%2C247%2C248%2C271%2C278%2C313&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&mh=na&mm=31%2C29&mn=sn-cu-h5oe7%2Csn-cu-auod&ms=au%2Crdu&mv=m&mvi=4&pcm2cms=yes&pl=44&initcwndbps=2188750&bui=AbKP-1OvLtwCb4L6dwT1GMEbkK3ZrL7X3gxm7Jk2uN3SPgdGh3yM2NERxfv-OI8gbvJZsqTLa-8SccZ_&spc=UWF9fxsIyYb90o96SI929OsJfiC5ftcu7cmAbYWrLrXY1meJws4thG_mk5sC&vprv=1&svpuc=1&mime=video%2Fwebm&ns=c1SX90TtWbl62x8S5MhcphYQ&rqh=1&gir=yes&clen=41458899&dur=251.920&lmt=1634000891472896&mt=1717449442&fvip=4&keepalive=yes&c=WEB&sefc=1&txp=6216224&n=G66MYAPZ87IsYsFCO&sparams=expire%2Cei%2Cip%2Cid%2Caitags%2Csource%2Crequiressl%2Cxpc%2Cbui%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cns%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&sig=AJfQdSswRgIhAMO0Pdosml7oxsuppKGIpKLSussPwkE7nwdrtEVXBNyFAiEA2EKgHHo4d0MUPosLPhHQZryODpoMejeeHDj1yNr_F9k%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AHlkHjAwRgIhAPNn3zf-pAHhlEGjbsrVn7fjeWZ0fOVcUepyieRln2iMAiEAuHEKzTdThDUEtTrWVe64qgB6GWv-DFsAZZJcOXn9YWM%3D and here it is from Pytube: https://rr4---sn-cu-h5oe7.googlevideo.com/videoplayback?expire=1717471554&ei=4jReZrKbB8eKmLAPm-u2qAQ&ip=2a00%3A23c6%3A8916%3A4601%3A3ccd%3A97d2%3A584%3Ab609&id=o-ANagADo5V_Hh4UtyXzzaZEFTX4S4ekFAI4OaX1uxc1L9&itag=22&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&mh=na&mm=31%2C29&mn=sn-cu-h5oe7%2Csn-cu-auod&ms=au%2Crdu&mv=m&mvi=4&pcm2cms=yes&pl=44&initcwndbps=2191250&bui=AbKP-1MGBozmWktaGcxs8nIzz7TRKbdAbxOSv-yL2rwxjGZlrF2wxZLfga6IxX3NSWnT47RiiUXRARtC&vprv=1&mime=video%2Fmp4&rqh=1&cnr=14&ratebypass=yes&dur=251.982&lmt=1634000896163657&mt=1717449687&fvip=4&c=ANDROID_EMBEDDED_PLAYER&txp=6211224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cbui%2Cvprv%2Cmime%2Crqh%2Ccnr%2Cratebypass%2Cdur%2Clmt&sig=AJfQdSswRQIhAJ1MSgLtyxWxLnQobNiRgFntwlN3p-oJ0RzqPxHknq4zAiBcbtfpxkSFvMYRtmMl2JyFp9KfhpXkOIDZRAm5fy_TCw%3D%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AHlkHjAwRQIgdi5NBPdmU2IOAQCFBTY_2Mr_kZLFu3NUh1aZ9jICM1cCIQCgrRs5TdeaLnJ4wq40U9Ni8nPgOJQ6qONtLzWwdJ67Zw%3D%3D.
Hope this helps.

Hello! I'm not sure if you're talking about the right YouTubeKit project (maybe this?) because I'm not really relying on pytube for the API and I don't recognize the calls that you do in the code you provided. Can you make sure that b5i/YouTubeKit is the right repository that you used in your project?
Thanks
Antoine

Hello b5i I am so sorry about this, you are correct. Thank you so much for pointing me to the correct API. My confusion arose from 2 packages with the same name!


PHP Fatal Error with laminas/laminas-crypt:^3.4

Bug Report
Installing on Symfony 6.2 project with PHP 8.1

Q
A

Version(s)
3.0.6

Summary
Get this Exception :
PHP Fatal error:  Declaration of Laminas......::has($name) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool in /path/info line int
Same as described here: https://github.com/laminas/laminas-di/issues/78
Expected behavior
Solution: replace laminas/laminas-crypt:^3.4 by laminas/laminas-crypt:^3.10 where bug has been fixed.

Thanks a bunch! I'm preparing a new release.

Released 3.0.7. Appreciate your report and pull-requests =)


cmd/server: async: send webhooks on company/customer name watches

This also includes the match percentage in the webhook body.

Codecov Report

Merging #80 into master will increase coverage by 0.49%.
The diff coverage is 61.6%.

@@            Coverage Diff             @@
##           master      #80      +/-   ##
==========================================
+ Coverage   55.62%   56.12%   +0.49%
==========================================
  Files          21       21
  Lines        1981     2081     +100
==========================================
+ Hits         1102     1168      +66
- Misses        752      779      +27
- Partials      127      134       +7

Example:
$ go run ./examples/webhook/
ts=2019-04-26T20:06:47.351946Z caller=main.go:34 startup="Starting moov/ofac-webhook-example:v0.8.0-dev"
ts=2019-04-26T20:06:47.352062Z caller=main.go:66 transport=HTTP addr=:10101
ts=2019-04-26T20:06:58.119661Z caller=webhook.go:49 webhook="got webhook for Customer 22790 (MADURO MOROS, Nicolas) match=0.94"


(FEAT) / Add daooda.dev on world-portfolios 🚀

Hello @ln-dev7
I'm adding my portfolio that I recently updated!
Nice project otherwise, I love it ❤

Thanks youuuu ❤


How to add an extra stage layer in lua

What is your question?
Like does it work if I have a folder full of poemUI and name the stage “isPoemStage” because it didn’t work for me

That's not how it works so no

Oh


SecContentInjection is not yet supported

I am getting below error when using ContentInjection rule vi /etc/nginx/nginx.conf nginx -s reload 10:26:25 [notice] 118#118: ModSecurity-nginx v1.0.0 10:26:25 [emerg] 118#118: "modsecurity_rules" directive Rules error. File: <>. Line: 1. Column: 16. SecContentInjection is not yet supported. in /etc/nginx/nginx
rg] "modsecurity_rules" directive Rules error. File: <>. Line: 1. Column: 16. SecContentInjection is not yet supported. in /etc/nginx/nginx.conf:66

Yes. As stated by the error message and the reference manual, SecContentInjection is not supported in libModSecurity.

Thanks, What are the rules setup for preventing CSRF in libmodsecurity

@dvyas, You could try virtual patching the vulnerable parameters.

@victorhora can you give me one example...I am newbie to modsecurity...is there any rules file for virtual patching

How can I add a CSRF token like in modsecurity v2 it is SecContentinjection and then use append to ad token to desired forms

You can't append content with SecContentInjection as of now with libModSecurity. This functionality is not planned to be implemented. See https://github.com/SpiderLabs/ModSecurity/issues/1001#issuecomment-339754076.
This functionality was experimental in v2 and due to performance reasons and also due to the functionality also being too tied to the connector rather than the library it's currently deprecated.
I recommend that you follow OWASP guidelines on implementing CSRF protection:
https://www.owasp.org/index.php/Category:OWASP_CSRFGuard_Project
https://www.owasp.org/index.php/CSRFProtector_Project
https://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API

@victorhora Is there other setting to replace SecContentInjection that can produced token with every phaser.


How can I get the message using Uid?

I remember using Uid to get a specific message previous but I saw the newer version is using Message Number rather than Uid.
I'm not sure why this change was applied as message number gets constantly change if the messages are removed/moved.
I want to know if it's possible to fetch a specific message with Uid? If yes, please let me know.
Thanks!

Oops! My apologies, I didn't saw that the recent version is indeed using Uid.

Okay, so I upgraded to the latest version 2.3.0 and everything stopped working 😂
Below is my code and it results in "no headers found" exception.
        $cm = new ClientManager([
            'options' => [
                'fetch' => \Webklex\PHPIMAP\IMAP::FT_PEEK,
                'fetch_order' => 'desc',
                'sequence' => \Webklex\PHPIMAP\IMAP::FT_UID,
            ],
        ]);
        $client = $cm->make([
            'host'          => 'XXXXXXX',
            'port'          => 993,
            'encryption'    => 'ssl',
            'validate_cert' => true,
            'username'      =><EMAIL_ADDRESS>            'password'      => 'XXXXXXXXXXXXXX',
            'protocol'      => 'imap',
            'authentication' => null,
        ]);
        $mailbox = $client->getFolder('INBOX');
        return $mailbox->query()->getMessage(14);

However, if I ran below code, I do get the message headers
        $headers = $mailbox->overview();
        if (isset($headers[14])) {
            return $headers[14];
        } else {
            return "Message not in folder";
        }

I'm not sure what I'm doing wrong. Can you please help?
Thanks!

Hi @harshitpeer ,
thanks for your report.
Please update to the latest version (v2.3.1). You can now query for a message by its uid or msgn directly:
$message = $folder->query()->getMessageByUid($uid);
$message = $folder->query()->getMessageByMsgn($uid);

Best regards,

You're a ROCKSTAR!
BTW, why you don't have a DONATE link on your Github or Documentation page? I (and pretty sure others as well) would love to do some small contribution towards your efforts on keeping this repo active.


How can I get the data from the table which in the EOS smart contract?

I am  trying to develop my DAPP by using demux. Now I need to get the data from my contract. How should demux be implemented?

[EOS TRANSFER EXAMPLE]Check out https://github.com/EOSIO/demux-js/blob/develop/examples/eos-transfers/)
you can test it out by running it and deploying the eosio.token contract, it will catch the actions as they occur. Change the NODE its pointing at to your line 28 index.js.
https://github.com/EOSIO/demux-js/blob/develop/examples/eos-transfers/handlerVersions/v1/index.js
if you go down to line 71 and  49 Demux being told to watch ACCOUNT.ACTION. Replace these with your account name and action in the ABI file of your contracts. Edit updateTransferData() a bit too, incoming data the data is in the payload object.  That's pretty much the basics.
How you use/store the data is up to you in the effects and updater functions, i think there are Mongo and Postgres implementations for database storage.

[EOS TRANSFER EXAMPLE]Check out https://github.com/EOSIO/demux-js/blob/develop/examples/eos-transfers/)
you can test it out by running it and deploying the eosio.token contract, it will catch the actions as they occur. Change the NODE its pointing at to your line 28 index.js.
https://github.com/EOSIO/demux-js/blob/develop/examples/eos-transfers/handlerVersions/v1/index.js
if you go down to line 71 and 49 Demux being told to watch ACCOUNT.ACTION. Replace these with your account name and action in the ABI file of your contracts. Edit updateTransferData() a bit too, incoming data the data is in the payload object. That's pretty much the basics.
How you use/store the data is up to you in the effects and updater functions, i think there are Mongo and Postgres implementations for database storage.

Thanks for your help. But I need to call the data that has been saved on the chain in the multi-index table. Demux seems to have no  API for it?

I don't think that is its intended function. No.
For getting the current state i use a RPC (https://github.com/EOSIO/demux-js/blob/develop/examples/eos-transfers/index.js)  call or a cleos shell command.
But this way can get tedious to maintain application data.
Demux can help alleviate having to check the chain state all the time by caching the state in a DB as is changes, making it easy to query.

This is a planned feature coming to EOSIO/demux-js-eos, but is currently on hold due to some changes needed to eosio and chainbase to help support it. If all goes well, we should be able to have a per-action diff for state changes (possibly even more granularly per-operation), which can be used in your updater functions.
Since this issue should be EOSIO/demux-js-eos, I'm closing this. Feel free to open another issue there.


[CT-1933] [Bug] Time ingestion partitioning doesn't work with date data_type

Is this a new bug in dbt-bigquery?

[X] I believe this is a new bug in dbt-bigquery
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When using "time_ingestion_partitioning": true and "data_type": "date", a dbt run will fail with following error
BadRequest('PARTITION BY expression must be _PARTITIONDATE, DATE(_PARTITIONTIME), DATE(<timestamp_column>), DATE(<datetime_column>), DATETIME_TRUNC(<datetime_column>, DAY/HOUR/MONTH/YEAR), a DATE column, TIMESTAMP_TRUNC(<timestamp_column>, DAY/HOUR/MONTH/YEAR), DATE_TRUNC(<date_column>, MONTH/YEAR), or RANGE_BUCKET(<int64_column>, GENERATE_ARRAY(<int64_value>, <int64_value>[, <int64_value>]))')

Expected Behavior
Expected behavior is that the model is created and working as intended.
Steps To Reproduce
Using following model
{{
    config(
        materialized = 'incremental',
        incremental_strategy='insert_overwrite',
        partition_by = {
          "field": "day",
          "data_type": "date",
          "granularity": "day",
          "time_ingestion_partitioning": true
        }
    )
}}
SELECT DATE('2023-01-25') as day, 1 as value

The failure can be reproduced
Relevant log output
No response
Environment
- OS: MacOS 12.6
- Python: 3.10.6
- dbt-core: 1.4.0-rc1
- dbt-bigquery: 1.4.0-rc1

Additional Context
No response

Thanks for opening a PR for this as well @github-christophe-oudar !

This issue will not be the end of this saga. This library has lots of edge cases and mutually exclusive DDL elements. To get total coverage, a new issue will need opening.


Improve JavaDoc of TaskInputs.property

@bot-gradle test and merge

OK, I've already triggered a build for you.


5/28 PM Publishing

Docs Build status updates of commit ab09f99:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-6.0.0/azureps-support-lifecycle.md
:white_check_mark:Succeeded
View (azps-6.0.0)

docs-conceptual/azps-6.0.0/toc.yml
:white_check_mark:Succeeded
View (azps-6.0.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


DEV-23: Add possibility of absolute imports

At the moment all the imports in the project are relative, that means that sometimes it can leat to the situation, where the import looks like this:
import { something } from '../../../../../../../../../../../../../../../somewhere.js';
To avoid such situations, we can use an absolute import approach. In this case the src folder will be considered as root and then we can import just from 'somewhere.js'.
You can find more info in this video: https://www.youtube.com/watch?v=h5ekwDyjmW4
To work on this issue, please use a branch DEV-23 created from devel. When the work is finished - create a PR to the devel branch. At the end of each development circles, code from the devel branch (if everything is ok) goes to the master branch and deploys to production.
IMPORTANT! Before creating a PR be sure that all the tests are passing and the coverage is 100%

I tested the code after change both on local and PRE environments and everything works fine.
After merging the PR this issue can be closed.

The PR is merged so the issue can be closed


custom rpc support in various explorers

What happened?

SolanaFM is giving a wrong url for custom rpc

Add custom rpc support for Solana Explorer

Solscan doesn't support localhost but support custom rpc

Errors & Logs
No response
App Version
v1.0.0-alpha.38
Web Browser
Chrome

closed by #58


New feature urlview in mutt & weechat to open urls

This PR will introduce the use of urlview in Weechat and Mutt.
urlview will extract URLs from text within the current Weechat buffer or email in Mutt and display a menu from which you may select the desired link and launch from within the shell using Lynx. In the case of multiple URLs in buffer/email, it will allow you to select the desired URL from a list.
In #! and #!social multiple links will often be the case due to URL shortener, but should not pose any issue.
Weechat Use
/urlview
Mutt Use (listed in .muttrc)
ctrl + b
I can also add something to man.

Ctrl+b is already taken by tmux. It will be confusing (and unused) to use it for mutt too.

I can't believe I didn't even consider that. Will change to something else, once i figure out what that should/could be.

@daurnimator are you saying useless?

No, just that if it was behind Ctrl+B (and tmux was too) no one would bother using it :p

@daurnimator turns out you don't need any .muttrc settings to make this work. It's built into mutt as hold Ctrl+B (Ctrl&B?). Think I should go with that, cause as far as I can tell the only keys not binded in mutt were
Ctrl+0
Ctrl+,
Ctrl+'
unless we got shift involved or used numbers from the number pad, but all users may not have a keyboard with a numberpad

@daurnimator turns out you don't need any .muttrc settings to make this work. It's built into mutt as hold Ctrl+B (Ctrl&B?).

Do you mean Ctrl+b or Ctrl+Shift+b?

@daurnimator Hold down Ctrl+B. Urlview is installed, so you can test it on your mutt if you like

Took a long time for me to make such a simple change, but can i get a :thumbsup: now?

okay. :+1:


Adding a helper function for making custom coders.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @lostluck
As an aside, and not in this PR, what do you think about refactoring the locations of all the coder code in the SDK right now. I noticed while trying to figure out how to make some coders that its very unintuitive trying to figure out how to make coders for certain types (for example ints). Right now it seems like built-in coders are all in graph/coder and custom coders for Go types are in runtime/coderx. I was thinking of moving those into the same directory and splitting them into a file for builtin coders, a file for custom coders (for code generation I'm guessing), and a file for helpers for users to create custom coders for various types.
None of that is urgent at all, it's all just stuff that I think makes the SDK a bit more intuitively organized.

Not while I'm in the middle of modifying all the coder code for Schemas :D
As you've described, there's a reason for the two packages, one is for Beam Model coders, and the other is for not beam model coders. That signal is valuable though I agree it's a bit subtle, and not called out very well. It's the kind of thing that I'd have called out in a document of a walkthrough of the Go SDK, but didn't in my talk.
The value is that it's harder to accidentally use a non-standard coder when one must use a standard one.
By being separate, they also serve as an example of how to write some of these.

I do agree that the runtime folder is probably not the right place for the coderx package though. It's also a bit moot since it's not a package users will interact with.
If we were to get rid of the coderx package, I'd rather the coders move to the main beam package or similar, since they're invoked in inferCoders IIRC?
These are good things to think about, and the whole SDK could use a clear overhaul, but we should have a total plan for that so we can apply them evenly to all facets of the SDK at once, rather than one at a time.
Note, that this would probably need to wait until a beam v3 or similar, as disrupting so many packages would break folks who are importing them for some reason out of the SDK.

If we were to get rid of the coderx package, I'd rather the coders move to the main beam package or similar, since they're invoked in inferCoders IIRC?

My only objection is that we'd likely want to use those coders in packages further down in the SDK, but importing beam from those is a common cause of import cycles from my experience, so I'd prefer putting it in a subpackage instead (and we could always forward it to beam if we really want). I think having something like graph/coder/custom would be better. It's consolidated in the same directory tree as the builtin coders, but clearly separate since its in a subdirectory, and the package name is still clear (ex. custom.NewIntCoder()).
Agreed with everything else, including waiting until a major version update before going through with this.


Fail to install new docker-engine package: size mismatch

# apt-get install docker-engine
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  aufs-tools cgroup-lite
The following NEW packages will be installed:
  aufs-tools cgroup-lite docker-engine
0 upgraded, 3 newly installed, 0 to remove and 4 not upgraded.
Need to get 5,691 kB/5,787 kB of archives.
After this operation, 28.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://apt.dockerproject.org/repo/ ubuntu-trusty/main docker-engine amd64 1.8.2-0~trusty [5,691 kB]
Fetched 5,691 kB in 0s (7,373 kB/s)
E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~trusty_amd64.deb  Size mismatch

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Hi,
I'm geting the same thing: Ubuntu 3.19.0-15-generic.
Linux kuba 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
I'm following the basic instructions here:
https://docs.docker.com/installation/ubuntulinux/
Get:1 https://apt.dockerproject.org/repo/ ubuntu-vivid/main docker-engine amd64 1.8.2-0~vivid [5,699 kB]
Fetched 5,697 kB in 2s (2,396 kB/s)
E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~vivid_amd64.deb  Size mismatch
I assume this is a very very new issue? What else can i provide?
RB

Same issue here :
Trying to install docker on ubuntu :
Linux ubuntu-14 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

via this command :
curl -sSL https://get.docker.com/ | sh

and get this error :
Reading package lists... Done
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  docker-engine
0 upgraded, 1 newly installed, 0 to remove and 215 not upgraded.
Need to get 5,691 kB of archives.
After this operation, 28.5 MB of additional disk space will be used.
Get:1 https://apt.dockerproject.org/repo/ ubuntu-trusty/main docker-engine amd64 1.8.2-0~trusty [5,691 kB]
Fetched 5,691 kB in 3s (1,445 kB/s)
E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~trusty_amd64.deb  Size mismatch

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Seeing the same problem on a fresh AWS box.
 Done
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  aufs-tools cgroupfs-mount
The following NEW packages will be installed:
  aufs-tools cgroupfs-mount docker-engine
0 upgraded, 3 newly installed, 0 to remove and 58 not upgraded.
Need to get 5,699 kB/5,796 kB of archives.
After this operation, 28.9 MB of additional disk space will be used.
Get:1 https://apt.dockerproject.org/repo/ ubuntu-vivid/main docker-engine amd64 1.8.2-0~vivid [5,699 kB]
Fetched 5,697 kB in 0s (20.6 MB/s)
E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~vivid_amd64.deb  Size mismatch

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

ping @jfrazelle

Same here, looks like docker has a bit of a broken somewhere... no wonder no one I asked could tell why it wasn't working even though apt-get upgrade did on the line just before

Same issue here (on fresh aws box after an apt-get update).

Same on DigitalOcean.

Getting the same when trying to install:
$ curl -sSL https://get.docker.com/ | sh
Output:
Fetched 5691 kB in 0s (5962 kB/s)
E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~trusty_amd64.deb  Size mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?```

Machine: `Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-48-generic x86_64)`

I think this is enough evidence, I'd guess there's an investigation and fix in-process now

Same here, Ubuntu 12.04 (Vagrant):
file: docker-engine_1.8.2-0~trusty_amd64.deb

Current:
  size: 5690994
  md5: 809a064aa451849dfdce77b41d89a9f5

Expected (in Docker APT repo in Packages.bz2 manifest):
  size: 5690966
  md5: 178c3d51507cd9a7b8e69c3bb9f057c4

Ditto - 14.04 Trusty on AWS and Parallels.

same for cloud66. 	Deployment failed: Failed command: sudo DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install docker-engine=1.8.2-0~trusty. Error output: E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~trusty_amd64.deb Size mismatch E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

apt-get install docker-engine=1.8.1-0~trusty still works FWIW

I get the same error when I run vagrant up using the following Vagrantfile (it worked without any errors before):
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.define "host"
  config.vm.network "private_network", ip: "<IP_ADDRESS>"
  config.vm.synced_folder ".", "/app", type: Vagrant::Util::Platform.windows? ? "smb" : "nfs"

  config.vm.provider "virtualbox" do |vb|
    vb.customize ["modifyvm", :id, "--memory", "1536"]
  end

  # Add swap
  config.vm.provision :shell, inline: "fallocate -l 4G /swapfile && chmod 0600 /swapfile && mkswap /swapfile && swapon /swapfile && echo '/swapfile none swap sw 0 0' >> /etc/fstab"
  config.vm.provision :shell, inline: "echo vm.swappiness = 10 >> /etc/sysctl.conf && echo vm.vfs_cache_pressure = 50 >> /etc/sysctl.conf && sysctl -p"

  # Install docker
  config.vm.provision "shell", inline: "curl -sSL https://get.docker.com/ | sh"

  # Install docker-compose
  config.vm.provision "shell", inline: "apt-get install -y python-pip"
  config.vm.provision "shell", inline: "pip install -U docker-compose"
end

Error response:
# ...
==> host: E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~trusty_amd64.deb  Size mismatch
==> host:
==> host: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Having same issue here (ubuntu 14.04)!!!!

Also happening on Debian Jessie.

Same here- Vagrant w/ 14.04

Same on kvm ubuntu 14.04, docker ubuntu

this seems to do the trick:
$ wget https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~trusty_amd64.deb
$ sudo dpkg -i docker-engine_1.8.2-0~trusty_amd64.deb

Same issue on Ubuntu 15.04/vivid

Thanks guys we're working on it

@marcsalomon - Yes good workaround.

@marcsalomon thanks man

It would not be a good idea to bypass the gpg checking here, imo.

@marcsalomon, Thanks for the workaround :+1:

Failed on 3.13 kernel
Linux my-server-1 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
worked on 3.19 kernel
Linux my-server-2 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:09:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Encountered same issue
0 upgraded, 6 newly installed, 0 to remove and 174 not upgraded.
Need to get 9,133 kB of archives.
After this operation, 50.4 MB of additional disk space will be used.
Get:1 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ trusty/universe aufs-tools amd64 1:3.2+20130722-1.1 [92.3 kB]
Get:2 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ trusty/main liberror-perl all 0.17-1.1 [21.1 kB]
Get:3 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ trusty-updates/main git-man all 1:1.9.1-1ubuntu0.1 [698 kB]
Get:4 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ trusty-updates/main git amd64 1:1.9.1-1ubuntu0.1 [2,627 kB]
Get:5 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ trusty/main cgroup-lite all 1.9 [3,918 B]
Get:6 https://apt.dockerproject.org/repo/ ubuntu-trusty/main docker-engine amd64 1.8.2-0~trusty [5,691 kB]
Fetched 9,133 kB in 0s (10.6 MB/s)
E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.8.2-0~trusty_amd64.deb  Size mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
ubuntu@ip-172-31-33-55:~$ uname -a
Linux ip-172-31-33-55 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

@tiborvass this should be as simple as reindexing the apt archive. You may need to remove / re-add the package and then regenerate.

@marcsalomon, Thanks for the workaround! Works perfect!

We should be back: let us know if you're still seeing issues, thanks for your patience.

@icecrime seems to be working, thx for the fix

@icecrime Thanks :)

I just got this error for version 1.10.3, forcing apt to install the previous version with sudo apt-get install docker-engine=1.10.2-0~trusty solved the problem

@hernandesbsousa that's weird, do you still have a box with the issue? I can't reproduce.

Thanks a lot for the quick response.
I tried to reproduce this today on a fresh system and failed. On the old one which did not have the latest version, apt-get update && apt-get ugpgrade did not throw any erros (maybe I should not have updated the apt cache before trying to upgrade the package). Anyway it's working fine now, thank you!

I'm having the same problem with a later version:
E: Failed to fetch http://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.11.2-0~trusty_amd64.deb  Size mismatch
Running sudo apt-get install docker-engine=1.11.2-0~trusty worked.  I, however, need to release a script to others that uses the latest.

@thomasshanks are you installing on a local machine, on a cloud provider? Could there be an apt-cacher running?

Err https://apt.dockerproject.org/repo/ ubuntu-trusty/main docker-engine amd64 1.12.1-0~trusty
gnutls_handshake() failed: A TLS packet with unexpected length was received.
E: Failed to fetch https://apt.dockerproject.org/repo/pool/main/d/docker-engine/docker-engine_1.12.1-0~trusty_amd64.deb  gnutls_handshake() failed: A TLS packet with unexpected length was received.
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?


Size unmatched when running EAP-IG notebook

Hello!
Thank you very much for your outstanding work. I have encountered a question when I am trying to run EAP-IG notebook. I was running knowledge_eap.ipynb using gpt2-medium and found that
Activation Hook Error hook_embed torch.Size([1, 18, 1024]) torch.Size([1, 17, 1024]) 0 and
RuntimeError: The size of tensor a (18) must match the size of tensor b (17) at non-singleton dimension 1
I tried to solve the problem following #7 in EAP-IG but it didn't work.

Can you provide your code and running examples?

g = Graph.from_model(model)
start_time = time.time()
# Attribute using the model, graph, clean / corrupted data and labels, as well as a metric
attribute(model, g, data, partial(logit_diff, loss=True, mean=True), method='EAP-IG-case', ig_steps=100)
# attribute(model, g, data, partial(direct_logit, loss=True, mean=True), method='EAP-IG-case', ig_steps=30)
# attribute(model, g, dataloader, partial(logit_diff, loss=True, mean=True), method='EAP-IG', ig_steps=30)
g.apply_topn(5000, absolute=True)
g.prune_dead_nodes()

g.to_json('graph.json')

gz = g.to_graphviz()
gz.draw(f'graph.png', prog='dot')

end_time = time.time()
execution_time = end_time - start_time
print(f"程序执行时间：{execution_time}秒")

I was running the knowledge_eap.ipynb and all went well until I got to the block I mention above. and I got the output of

Hello, sorry for being late.
This problem is due to the different lengths of the tokenized corrupted and clean subject tokens.
The tokenizers of GPT2 and LLAMA2 are different, making the case I used here unmatched. You can use different corrupted subjects to make sure the length is the same as Eiffel Tower such as the Santa Monica Beach.

hi buddy, do you have any further questions?


Proposal: Please start using Semantic Versioning

I found that this project already supports Go modules. But sadly, the tags doesn't follow Semantic Versioning, which means that all tags of this project will be ignored by Go modules and replaced by pseudo-versions, go get acts weirdly when tags are not in that form. It would be great to have the tagged release be named in the format vX.X.X format so that go mod can read it.
	github.com/qor/qor v0.0.0-20200729071734-d587cffbbb93

Else the mod file shows something like github.com/qor/qor v0.0.0-20200729071734-d587cffbbb93 which is not very readable and difficult to upgrade. It’s hard to verify which version is in use. This is not conducive to version control
So, I propose this project to follow Semantic Versioning in future versions. For example, v1.0.1, v2.0.0, v3.1.0-alpha, v3.1.0-beta.2etc.

@raven-chen  @jasonweng  Could you help me review this issue? Thx :p

Hi @KateGo520
Thanks for your proposal. Yes, we are considering introducing semantic versioning to QOR. We have a breaking change here https://github.com/qor/qor/pull/252 we plan to bump the major version when this gets merged and the semantic versioning will be added too.

@raven-chen   Thank you for your reply. Looking forward to the new version! : D


[TEVA-231] - Set StatusCake node_locations to UK and Ireland

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-2312
Changes in this PR:

Choose StatusCake servercode identifier from https://app.statuscake.com/Workfloor/Locations.php
Use locations in StatusCake tests to avoid false positives originating from Texas

Review app deployed to https://teaching-vacancies-review-pr-3182.london.cloudapps.digital


Struggling to setup requests to use our settings.

Hi.
I'm trying to use my own axios instance, with my preset headers with vue-mc. From our login we have quite a few headers set to be able to talk to our backend properly, as well as the logout being tied to that instance as well. I saw a reference elsewhere that I should extend vue-mc's Model class and overwrite the getRequest method. So I made a BaseModel class.
However the getRequest method wants to return a Request instance, which is a class not exported from vue-mc, and the axios instance seems to be in the send function of the Request class. So I dug into the code, and made my own identical BaseRequest to return from my BaseModel's getRequest class.
However the send function again wants to return a RequestError or a Response instance, neither of which are exposed. So I made a BaseRequestError and a ....
So this rabbit-hole just seems to go deeper, I end up getting new error messages from functions and classes expecting new classes or more methods from my instances every time, clearly this is not how it's intended to be used.
Are there any good examples on how I can just overwrite the getRequest-method of my extended Model class to achieve my intended results?
It would be great if there just was a simple param set once, (or twice then, for "BaseCollection" too). Something like this pseudocode:
    import Vue from 'vue';
    import { Model, } from 'vue-mc';

    class BaseModel extends Model {

        constructor() {
            super();
            // set all models $http-client to our preset axios instance, which we've already set to Vue.prototype at login...
            this.$http = Vue.prototype.$http;
        }
    }

Ok, so writing the above post triggered that ol' rubberduck in me, and I came up with this which seems elegant enough.
    import _          from 'lodash';
    import Vue        from 'vue';
    import { Model, } from 'vue-mc';

    /**
     * BaseModel
     * A base model class using the application's default axios settings.
     * Note: Always extend from this class, not the vue-mc Model.
     * @version 0.0.3
     */
    class BaseModel extends Model {

        /**
         * Parses every request made by any Model in the system.
         * @param config  Config options for any restful http call.
         * @returns {Request} A new `Request` using the given configuration and our default axios instance's settings.
         */
        getRequest( config ) {
            // Vue.prototype.$http contains our axios instance, we extend the given config with it's settings.
            config = _.extend( config, Vue.prototype.$http.defaults );
            return super.getRequest( config );
        }
    }

    export default BaseModel;

So unless there's something I've failed to understand with the intent of vue-mc, this should be a working implementation?

Added the same getRequest to a "BaseCollection" class, and everything seems to work fine.
Changed the title in case anyone else struggles with their settings the way I did.

This can help if you want use the instance instead pass only configs to vue-mc instance: https://github.com/FiguredLimited/vue-mc/issues/23#issuecomment-538444274


🚨⚠ Important Announcement ⚠🚨

Moving forward Swiper.js is moving to web components. Removing support for Vue/React libraries in favor of web components. This means that nuxt-swiper will be obsolete in the coming months for the swiper/vue package. This means that if you see any bugs within the swiper/vue modules it's most likely it will not be fixed 🙁
So what does this mean?
Well this means that I will have to a totally re-write to support swiper/elements, Which in this case -- I really don't know if there is really any benefit of doing so when you can just import the element straight to your project to work out of the box. When creating nuxt-swiper I wanted to make it easier setting up swiper.js for my various personal projects and it worked for what I needed.

In the recent months I have been receiving issues that are non related to nuxt-swiper itself, as it makes swiper.js easier to work with all the great things Nuxt provides which is Auto Imports, Typescript types and the plug n' play module system it has. I've have been trying to help many people with there problems but some are just beyond my capabilities to fix since I do not maintain the swiper/core.
So I would love to discuss potentially implementing swiper/elements but I would love to talk to the community to see if it something that is even feasible to do. I appreciate everyone that has supported and starred the project! It means the world! Please feel free to discuss what you think below.
Links:

Swiper Elements: Here
Swiper Vue: Here

Thanks,
CP 💚

I have no experience with Web Components, but what happens to TypeScript, do we go back to vanilla JavaScript when interacting with these?
Does it mean, we need also need go back to manually importing, every Module/CSS file that we want, explicitly?
Thanks for sharing.

@FranciscoKloganB
Hey 👋! I will have to look into as I never worked with web components with Typescript but I think it's possible still but I just have to see how it works. I will let you know.
Technically yes but I could re-write the package to include the web components in this package so you wouldn't have to import manually. I just have to figure it out if it's even useful for everyone to make the change!
Thanks,
CP

@cpreston321
Should we leave nuxt-swiper on the stable version of Swiper 8 which will still support Vue components or start a new branch with a module that will work with the new Swiper and will also provide a wrapper for the WebComponents?

I do not know what it is, but from the example code looks like the same as the usual components

Hey @NnicanBuak!
I think the current version of Swiper 9 is best bet to keep bugs limited but knowing we are going to loose support for the main package will come will drawbacks including bugs which I don't control. I think we can keep it on Swiper 9 until compatibility is lost.
I do think it's feasible to do a major version bump to then support elements out of the box. I am going to look more into it to see if there is a way implement typescript types. If so that might be the best route.

I can try to gather as much information as I can, but I mostly a backend developer playing "the frontend world". 😅
If I find relevant information, I will share it here.

Have not been able to figure out much but here are the things that are "obvious" after trying to migrate from this package to web-components solution.

Way more boilerplate

Have to load modules manually (classic swiper procedure)
Have to inject styles in a way that was not required with swiper/vue (still figuring how to do this one) in Nuxt (did not find any examples on the web, nor docs on swiper)
Have to use onMounted lifecycle hook if you want to use breakpoints.
Register
Typescript not fully supported at the Webcomponent level (e.g., within

So far this has translated in all this code (still missing proper style injection)
/**
* nuxt.config.ts - add to add isCustomElement function
*
* @see https://vuejs.org/guide/extras/web-components.html#using-custom-elements-in-vue
* @see https://nuxt.com/docs/api/configuration/nuxt-config#compileroptions-1
*/
  vue: {
    compilerOptions: {
      isCustomElement: (tag: string) =>
        ['swiper-container', 'swiper-slide'].includes(tag),
    },
  },

<script setup lang="ts">
// Can still be somewhat typesafe because we have access to Swiper as usual - but web components are typed as `Any`.
import type { SwiperOptions } from 'swiper'

// Import swiper element registration
import { register } from 'swiper/element/bundle'

// Manually import  desired modules.
import { Autoplay, Pagination, Scrollbar } from 'swiper'
import 'swiper/css/autoplay'
import 'swiper/css/navigation'
import 'swiper/css/pagination'

onMounted(() => {
  /**
   * @see https://swiperjs.com/element#core-version-and-modules
   * @see https://swiperjs.com/element#parameters-as-props
   */
  const swiperContainerEl: (HTMLElement & { initialize: () => void }) | null =
    document.querySelector('swiper-container')

  if (swiperContainerEl) {
    Object.assign(swiperContainerEl, params)

    swiperContainerEl.initialize()
  } else {
    throw createError({
      message: `Could not create carousel. Missing DOM element <swiper-container />.`,
      statusCode: 500,
      statusMessage: `Internal Server Error`,
    })
  }
})
</script>

Hello all!
I have been working on a new branch that contains this work, but it seems that there is still some on going issues with swiper elements to make the full implementation.
Branch:  https://github.com/cpreston321/nuxt-swiper/tree/feat/elements

@FranciscoKloganB Thanks again for initial research on how to best implement native web-components! 🙏🏼
I really do appreciate the community helping me out it means the world.
Thanks,
CP 🚀

I've actually updated the pseudo-code below to modify the useSwiper composable. By using an Vue ref and assigning it to <swiper-container ref="swiperContainerRef" :init="false"> my Swiper stopped breaking as I navigated across pages. It was also a problem that only happened in development, but no longer does. :)
Good luck with the implementation! I hope my poc was useful in anyway.

Any news about elements branch? :)

@NeekoDev Yes! I got it working last week you can check it out here: https://github.com/cpreston321/nuxt-swiper/tree/feat/elements 😀
While testing there are some modules like creative-effects not working with elements which seems to be upstream issue. I will submit an issue here soon. I also want a clean way to implement bundled vs base (meaning you have to import the styles and modules you want to enable on each instance of swiper). I also wanted to create some composables to help reference a swiper instance like how the current vue implementation.
In the meantime I am setting up a edge releases for elements so we can test in the mean time while keeping the current release as is. This will be good for reporting bugs etc.
Thanks,
CP 🚀

The next version works fine (I've been using it for months without issues). Might be time to publish the changes under latest.

@hacknug This is done ✅


WatchLive!. Leicester City vs Tottenham Hotspur Live Stream FREe EPL ON TV 19 August 2024

Listen Live: Leicester City vs. Tottenham Hotspur. Join us for Matchday Live as Leicester City start their new Premier League season by ..
🔴 GO LIVE==►► CLICK HERE TO WATCH LIVE

🔴 STREAMING==►► CLICK HERE TO WATCH LIVE

Leicester City v Spurs is being shown live on Sky Sports Main Event and Sky Sports Premier League. You can therefore live stream the match by ...
Leicester City v Tottenham TV channel, kick-off time and live stream details
Spurs are aiming for a Champions League place after missing out last season.
Newly-promoted Leicester City host Tottenham Hotspur in the first Monday night fixture of the new Premier League season.
The Foxes won the Championship last season, and have bounced straight back up to the top flight. They were surprisingly relegated from the Premier League in 2023, just seven years after they won it.
Ange Postecoglu goes into his second season as Spurs manager, after joining from Celtic. Leicester, on the other hand, are adjusting to life after Enzo Maresca, who is now the manager of Chelsea. Welsh manager Steve Cooper is now at the helm for the former Premier League champions.
READ MORE:Cardiff City close in on Norwegian defender
READ MORE:Erol Bulut addresses Aaron Ramsey injury
Here's everything you need to know about the match tonight.
What time is Leicester City v Spurs kick-off?
Leicester City v Spurs kicks off at 8pm on Monday, August 19, at the King Power Stadium in Leicester.
Leicester v Tottenham LIVE: Premier League team news and line-ups with Dominic Solanke set for Spurs debut
Will Dominic Solanke lead Tottenham to the perfect start or can Leicester return to the top flight with a bang at the King Power? Follow all the action from the Premier League clash
Leicester City host Tottenham Hotspur at the King Power Stadium tonight as the Foxes begin their bid to ensure Premier League survival against a Spurs side aiming to regain their Champions League status.
Leicester lost manager Enzo Maresca to Chelsea at the end of last season, replacing the Italian with former Nottingham Forest manager Steve Cooper, and the club have made a string of summer signings as they look to avoid relegation. They begin the season without strikers Jamie Vardy and Patson Daka, though, leaving Cooper short of forward options.
Ange Postecoglou is meanwhile looking to build on a solid first season in charge of Tottenham, having just missed out on Champions League qualification. Striker Dominic Solanke has been secured for a club record fee of £65m off the back of a 19-goal season for Bournemouth as Spurs seek to compete with the rest of the Premier League’s biggest clubs for a top four finish.
Follow the latest score and match updates below as Leicester take on Tottenham in the Premier League.

🔴📺Watch Live 📲👉📱👉 https://cutt.ly/aeextrLq 1080p | No Ads | Mobile Yes & PC

🔴📺Watch Live 📲👉📱👉 https://cutt.ly/aeextrLq 1080p | No Ads | Mobile Yes & PC

🔴📺Watch Live 📲👉📱👉 https://cutt.ly/aeextrLq 1080p | No Ads | Mobile Yes & PC

🔴📺Watch Live 📲👉📱👉 https://cutt.ly/aeextrLq 1080p | No Ads | Mobile Yes & PC

🔴📺Watch Live 📲👉📱👉 https://cutt.ly/aeextrLq 1080p | No Ads | Mobile Yes & PC

🔴📺Watch Live 📲👉📱👉 https://cutt.ly/aeextrLq 1080p | No Ads | Mobile Yes & PC

📺📱 🔴▶ Leicester City vs Tottenham Hotspur live stream
📺📱 🔴▶ Leicester City vs Tottenham Hotspur live stream
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.

https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/
https://expresssportshub.store/soccer/epl/

https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/
https://kayotvs.store/soccer/


Quick Demo?

Hi there, was evaluating the product, is there anybody that can give me a super quick 10min demo of the platform?

There is a homepage that showcases the core functionality here. Since this isn't a paid product, any further evaluation of sixpack is up to your organization.


Wrong title bar name

Sometimes the name of the torrent is wrong in the title bar.
http://www.torrentz.com/4367d111560f00fc814680e486f7d8c754c36ab0

this may happen from time to time because the data is retrieved from www.opensubtitles.org which might identify the video wrongly.

Another torrent I tested has this problem of wrong subtitle identification (http://www.torrentz.com/646281cd81a498c30f4bd923ee16676d0774975a). But the subtitle of the torrent I linked before (http://www.torrentz.com/4367d111560f00fc814680e486f7d8c754c36ab0) appears OK in that regard.


cmd/go/internal/test: -vet accepts bad input

What version of Go are you using (go version)?

$ go version
go version go1.16.6 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/user/go/pkg/mod"
GOOS="linux"
GOPATH="/home/user/go"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.6"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2105906029=/tmp/go-build -gno-record-gcc-switches"

What did you do?
https://play.golang.org/p/t6Q8DJU3ON6
go test .
go test -vet=all .
go test -vet=c=2 .

What did you expect to see?
ok  	trash/five	(cached) [no tests to run]
deprecated flag provided: -all
# trash/five
./main.go:7:8: using r before checking for errors
5	func main() {
6		r, err := http.Get("example")
7		defer r.Body.Close()
8		if err != nil {
9			panic(err)

What did you see instead?
ok  	trash/five	(cached) [no tests to run]
# trash/five
./main.go:7:8: using r before checking for errors
FAIL	trash/five [build failed]
testing: warning: no tests to run
PASS
ok  	trash/five	0.101s
invalid value "c=2" for flag -vet: -vet argument cannot contain equal signs
usage: go test [build/test flags] [packages] [build/test flags & test binary flags]
Run 'go help test' and 'go help testflag' for details.

What would you like done?
This came out of development on #45963 [CL 334873]. It was discovered that go test -vet=all, actually works today. This is because unlike what the docs say -vet simply passes the list of "checks", with - prefixes, to go vet as flag arguments.

-vet list
Configure the invocation of "go vet" during "go test"
to use the comma-separated list of vet checks.
If list is empty, "go test" runs "go vet" with a curated list of
checks believed to be always worth addressing.
If list is "off", "go test" does not run "go vet" at all.

This was is an intended feature and seems quite brittle. As such, we should pin -vet to the documented interface, or define what "flags" we accept and update the the documentation. If we are not expanding the definition, we should ignore or error on all the deprecated and non-check name flags: -V, -source, -c, -printfuncs, and -printf.funcs(anything with a dot). (This is very much a blocklist, since we want to allow new checks to be added over time.)

@matloob per owners

FWIW, the go vet subcommand currently scrapes the flags here:
https://github.com/golang/go/blob/3e48c0381fd1beb78e993e940c3b46ca9898ce6d/src/cmd/go/internal/vet/vetflag.go#L81-L98
Running go tool vet -flags locally, I see that it actually has a fair amount of structure in the Usage field. Perhaps we should only forward flags whose Usage string is of the form enable %s analysis?

I don't think we should allow configuration of flags like -c and -v in go test -vet. If users want that much control, they can run go vet separately from go test.

Sweet, I too do not see the benefit in having -vet be a generic way to pass arbitrary flags, so I have struck the following section from the description: (persisted for historical purposes)

Otherwise, there are three main problematic cases.
distinguished
This may be resolved in CL 334873, but basically we should really not be accepting distinguished values and other things in the list of checks: e.g. -vet=off,anything.
deprecated
Because the contract that -vet provides is "run these checks", it is really confusing how -vet=v runs more linters than -vet="" (or not passing -vet). Since the list of flags labelled as no effect (deprecated) is finite and (hopefully) fixed, we can could ignore or error if any are passed.
value
If we are committing to allowing full configuration of vet, which may well be a bad idea, things like -c, takes values as input and should be able to be configured. This could be something like -vet=asmdecl,c=3,atomic, which is disabled today, by the failure to parse flag values containing =s. -vet=c3 would also be fine and is quite coreutils.
Also worth noting are deprecated check flags like -compositewhitelist, and their non-deprecated alternatives, -composites.whitelist, but that should work with the -c fix: -vet=asmdecl,composites.whitelist=false,atomic.
four
The -V flag causes output to be very long and unreadable, since it is runs for every package that is compiled for testing. Even if we allow arbitrary flags, I support ignoring this one explicitly.

Perhaps we should only allow flags whose Usage string is of the form enable %s analysis?

I have some concerns about the complexity of needing to keep these two components in sync, but if there is a clean way to do that, or somehow share the canonical list of vet checks: I am game.

@colin-sitehost: Somewhat tangential/unrelated to the main issue. But it could lead to a separate issue in which go test isn't following documented behavior.
go help test documents that:

If go vet finds any problems, go test reports those and does not run the test binary.

However, In this issue description, the output you saw for go test -vet=all . was:
# trash/five
./main.go:7:8: using r before checking for errors
FAIL	trash/five [build failed]
testing: warning: no tests to run
PASS
ok  	trash/five	0.101s

So if the test binary did run (indicated by the PASS ok trash/five part) despite the vet failure, then go test didn't work as documented.
Can you confirm the actual output you saw/are seeing? I haven't been able to reproduce on macOS.

My working directory contains the files from the play link above.
// main.go

package main

import "net/http"

func main() {
	r, err := http.Get("example")
	defer r.Body.Close()
	if err != nil {
		panic(err)
	}
	_ = r
}

// main_test.go

package main

However, now I cannot reproduce it, so I have moved the old text from the description to not confuse the issue further:
# trash/five
./main.go:7:8: using r before checking for errors
FAIL	trash/five [build failed]
testing: warning: no tests to run
PASS
ok  	trash/five	0.101s

I have some concerns about the complexity of needing to keep these two components in sync, but if there is a clean way to do that, or somehow share the canonical list of vet checks: I am game.

I can think of at least two such ways.
One is to write a go:generate script that updates a map or function, and then verify that that map or function is up to date in a unit test. (That's the approach I used for #18682.)
Another is to invoke the vet tool once at run-time before running tests, as is currently done in go vet. But that only seems preferable if the vet tool itself can be specified at run-time, which is certainly true for go vet today but I think not for go test.

@zpavlinovic, we currently propagate -vet=a,b,c as -a -b -c, yes. What I think we should do instead is not filtering, but validation: go test should fail outright if any of the -vet parameters does not name a valid (or, perhaps, a once-valid) analyzer flag.

One is to write a go:generate script that updates a map or function, and then verify that that map or function is up to date in a unit test. (That's the approach I used for #18682.)

This is then probably the most robust way going forward.

https://github.com/golang/go/issues/35487 suggests having an exported list of analyzers available somewhere. This would be robust (but it does mean initializing all of the vet packages just to get their names).

Should we then block this issue until #35487 is resolved?

I don't think we need to block it on #35487. We can already scrape go tool vet -flags for Usage matching ^enable .* analysis$ or ^deprecated alias for -.*$ to get a list of the supported analysis flags.
That issue seems to be asking for a way to list the analyses used by default by go test and go vet, which are a subset of the analyses supported by the vet tool itself — and cmd/go already knows that subset anyway.

Ok, so the plan forward is to rely on go tool vet -flags to get the list of supported analysis flags.


[1.16.1] Game still crashes when breaking grass

Crash Report
TT version: 1.0.11
Fabric <IP_ADDRESS>

UPDATE: It wasn't related to the mod.


forward, alias, mailing list

Hi want to create aliases for every email.
<EMAIL_ADDRESS>=><EMAIL_ADDRESS>Is it possible to have multiple alias ?
<EMAIL_ADDRESS>=><EMAIL_ADDRESS>I also want to be able to create mailing list, for example :
<EMAIL_ADDRESS>=><EMAIL_ADDRESS><EMAIL_ADDRESS>Is it possible to forward to multiple mail ? If yes, should I use one line by forward are is there a sweeter syntax ?

Just try in the virtual file. I think it's out of the box in postfix.

http://www.postfix.org/VIRTUAL_README.html#forwarding

It work. Thanks ;)


feat: add patterns fallback

This pr add a setup option patterns_fallback which is false by default. When it is set to ture and all patterns fail to match, project.nvim will change the directory to current buffer's location. vim-rooter also support this kind of setting
see also #56

@ahmedkhalf Any thought on the fallback behavior?

Here's the non-intrusive workaround I'using before project.nvim got an option to fallback to non-project directory:
require'project_nvim'.setup { manual_mode = true }

local fix_project_root = function()
  local prj = require'project_nvim.project'
  local root = prj.get_project_root()
  if root then
    prj.on_buf_enter()
  else
    vim.cmd('lcd ' .. vim.fn.fnameescape(vim.fn.expand('%:p:h')))
  end
end
vim.api.nvim_create_user_command('ProjectRoot', fix_project_root, { force = true})
vim.cmd('autocmd BufEnter * ProjectRoot')

Thanks for your sharing. Your workaround is a bit overhead when switch buffers in different project very often as it would call get_project_root twice if root could be found.
This inspires me that I want to add a cache in project.nvim which map each buffer to it's root and I thinks it could have better performance.

The option could be called autochdir (bc it does exactly what autochdir does) and it seems more reasonable to specify it in the detection_methods list:
{
  -- Manual mode doesn't automatically change your root directory, so you have
  -- the option to manually do so using `:ProjectRoot` command.
  manual_mode = false,

  -- Methods of detecting the root directory. **"lsp"** uses the native neovim
  -- lsp, while **"pattern"** uses vim-rooter like glob pattern matching. Here
  -- order matters: if one is not detected, the other is used as fallback. You
  -- can also delete or rearangne the detection methods.
  detection_methods = { "lsp", "pattern", "autochdir" },


Start using issues and GitHub automated project boards! 🔥

Its great for your GitHub history, its great for tracking progress, it lets people know what needs done and what stage the project is at.

Hey! We are using a TODO.md file in the platform project, which is a vertical kanban board. Since this is a small project, it seems to be an adequate to use that.
And personally I find it to be more efficient, as I don't have to go to the GitHub to tick off a task. I'll probably add a TODO.md to this repository sometime soon.

Okay great! It was just a suggestion so that people looking at the repo can help out easier.

Okay great! It was just a suggestion so that people looking at the repo can help out easier.

Yes, we like to be as welcoming to contributors. Thank you for pointing it out. I'll keep it opened until we add a TODO.md file.


Widen "oneOf" argument to "Iterable" from "Seq"

Hi maintainers,
For convenience, we would like to use the oneOf combinator on sets in our tests. So we have widened the argument to Iterable from Seq and added a test. After merging, the following snippet should compile.
val set: Set[A] = ???
Gen.oneOf(set)

Background. Currently, the oneOf combinator is restricted to Seq. To use sets, there are currently two workarounds. First, we could convert it to a sequence. Second, we could use the Gen.pick[T] combinator. The workarounds are shown below.
val set: Set[A] = ???

// Workaround 1
Gen.oneOf(set.toSeq)

// Workaround 2
Gen.pick(1, set).map(_.head)

However, both of these workarounds are inconvenient if the oneOf combinator could be widened to accept Iterable.
Additionally, we noticed that the following combinators also accept Iterable, so we believe that this change should make the API more uniform.

Gen.someOf[T]
Gen.atLeastOne[T]

As a final note, the Iterable trait should be compatible with the Scala 2.13 collections work. :)

Seems like an oversight that was never caught.  I'm surprised it never came up before.
This is  a binary compatibility change.  It will require an override in MiMa. Something like:
--- project/MimaSettings.scala
+++ project/MimaSettings.scala
@@ -12,9 +12,14 @@ object MimaSettings {
       removedPrivateMethods.map(exclude[DirectMissingMethodProblem](_)) ++
       newMethods.map(exclude[ReversedMissingMethodProblem](_)) ++
       removedPrivateClasses.map(exclude[MissingClassProblem](_)) ++
+      changedMethods.map(exclude[IncompatibleMethTypeProblem](_)) ++
       otherProblems
   )

+  private def changedMethods = Seq(
+    "org.scalacheck.Gen.oneOf"
+  )
+
   private def newMethods = Seq(
   )

Thanks for the patch @ashawley! I have not used MiMa before, so that may have taken me a while to resolve. I squashed the patch into the current commit. Hopefully the build passes now.

Wow! The previous build seems to have ran into an extremely rare flaky test.
[info] ! Gen.frequency 3: Exception raised on property evaluation.
[info] > ARG_0: 0
[info] > Exception: java.lang.IllegalArgumentException: no items with positive weights

The test samples a number n from [0, 100000] uniformly and attempts to prove the property Gen.frequency(List.fill(n)((1, const(0))): _*) { _ == 0 } . However, for n == 0, Gen.frequency throws an IllegalArgumentException.
I believe the odds of encountering this error are 1 / 1000 (assuming that 100 samples are generated for each invocation of forAll). I have split the test into two test cases: n == 0 and n in [1, 100000].
Looks like we get to submit a new feature and a bug fix in the same PR. :)

Hi @ashawley and @Philippus , I have addressed the comments in the first round of reviews. Is there anything else we need to do before merging? :)

LGTM.  But @rickynils will have the final word on this.

This seems fine. But that MiMa change shouldn't be there, since this actually is a binary incompatible change, and we shouldn't merge this until the major version number has been bumped. @ashawley Or am I wrong?

Yeah, I was thinking it would have to wait for the next major version, but we could probably use function overloading to keep oneOf(xs: Seq) and have it call oneOf(xs: Iterable).


"Select" and "Start" cannot be used to quit RetroArch.

"Select" and "Start" cannot be used to quit RetroArch. Even with Xbox Mode disabled it does not work. Other hotkeys together with "Select" work strangely enough.
I have tried all the settings but nothing has helped. "Confirm quit" is enabled.
It works on the stock firmware however.

Sometimes shortly after starting a rom I get the correct confirm message to appear.

I believe your problem might be your current Retroarch settings. I see you
have "Hotkey enable" set to the 'select' key (109). That means all your
hotkeys will be combos by default ("select" + "some-other-key").
On top of that, you have the "quit controller combo". So, you're mapping
"select" to 2 different things.
If you use select as a hotkey enabler for other things, I'd keep "select"
as "hotkey enabler", remove the "quit (controller combo)" option and set
the "start" key as "Quit".
In any case, even with your current problematic double mapping, pressing
select and start precisely together simultaneously should work to quit the
game. (I've double checked your configuration on my device here).
I hope this helps.
Cheers,
E.
Eduardo Patricio, PhD
Sound Designer / Lecturer at Bydgoszcz Music Academy
https://linktr.ee/eduardopatricio
On Sat, Jul 1, 2023 at 2:08 AM DieHardMan5x @.***>
wrote:

"Select" and "Start" cannot be used to quit RetroArch. Even with Xbox Mode
disabled it does not work. Other hotkeys together with "Select" work
strangely enough.
I have tried all the settings but nothing has helped. "Confirm quit" is
enabled.
It works on the stock firmware however.
[image: Screenshot_20230701-014702_RetroArch (AArch64)]
https://user-images.githubusercontent.com/74651322/250214967-ec3465e2-c901-46fa-a80a-dffcfcdd3b25.png
[image: Screenshot_20230701-014533_RetroArch (AArch64)]
https://user-images.githubusercontent.com/74651322/250214970-47643c7e-c105-404b-87e1-343c849a7618.png
[image: Screenshot_20230701-014643_RetroArch (AArch64)]
https://user-images.githubusercontent.com/74651322/250214971-3f2fb6b1-79d6-4373-ac7d-114ec1a75ac3.png
[image: Screenshot_20230701-014554_RetroArch (AArch64)]
https://user-images.githubusercontent.com/74651322/250214973-6d5ad965-400c-4e22-b6ac-cadc4a73bb9e.png
Sometimes shortly after starting a rom I get the correct confirm message
to appear.
[image: Screenshot_20230701-015230_RetroArch (AArch64)]
https://user-images.githubusercontent.com/74651322/250214974-cdc5a900-b047-4b45-a8f2-6ac46ae7e625.png
—
Reply to this email directly, view it on GitHub
https://github.com/TheGammaSqueeze/GammaOS/issues/26, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA46DXYXI6VHIFDAVP74RLXN5TBVANCNFSM6AAAAAAZ2NSQUE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for the help, if I use "Start" as a hotkey for "Quit" then everything works fine. There my memory played a trick on me, the issue can be closed.


Save audio edited by wavesurfer equalizer example

I've looked through the documentation as well as the issues, and can't see anywhere that talks about saving an audio edited by wavesurfer equalizer.
Is there currently a built-in way to do this?
What I'm looking for in the end is to:
load an wav
edit it with the equalizer
press a Save button and save the already edited wav file.

Hey did you ever solve this?

Same here, is there a solution to that?


fix MIRI_BE_RUSTC value during sysroot build

@hyd-dev pointed out that MIRI_BE_RUSTC is set to an incorrect value during the xargo sysroot build. This fixes that.

@bors r+

:pushpin: Commit 6834944fd321deeb412838e9c8fedfb717b4f67c has been approved by RalfJung

:hourglass: Testing commit 6834944fd321deeb412838e9c8fedfb717b4f67c with merge e289cce75932e0674ae6584cfbe1ff23a9fe5959...

:broken_heart: Test failed - checks-actions

macOS taking longer than 500ms to wake up a thread...
@bors retry

:hourglass: Testing commit 6834944fd321deeb412838e9c8fedfb717b4f67c with merge 74ffda2dd7edfaba5dfc3d9d2499b46c966b15c3...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 74ffda2dd7edfaba5dfc3d9d2499b46c966b15c3 to master...


[TW#14021] Deep sleep and flash

Hi there,
Whenever the SoC comes out of deep sleep, does it access the flash ? Even if using a wake up stub? Is there anyway not to access the flash before exiting the wake up stub?
Thanks

If you have set a custom wake stub, then flash will only be accessed once you return from the wake stub.


Add .gitignore file

Running the doctests as
$ python -v doctests.py

generates multiple byte-code compiled files which should be ignored by the version control.
PS : I can add the full version of the file (which we should) if said to.

Thanks! But another contributor already submitted a .gitignore pull request (sorry I was slow to respond).


SPARKTA-193 SPARKTA-197 Added zinc profile and issue when a policy is…

SPARKTA-193 SPARKTA-197 Added zinc profile and issue when a policy is stopped in cluster mode

LGTM +1

LGTM +1


Keyboard Shortcut Support Issue

Describe the bug
The shortcuts is not supported completely. (like Control+C)
To Reproduce

ssh xxx@xxx
if ssh is waiting for response, Control-C will not work,

Expected behavior
Control-C works
Desktop (please complete the following information):

OS: Windows 10 Pro

Hi @KevinZonda ! thanks for your tests and for your feedback.
Effectively there is an issue due to a missing implementation.
when inputing a command that is not part of the orbsh (orbital shell) commands, it try to find a executable or a shell script in the OS (thus the underlying shell).
However, the part of code that execute an os command is not complete : the input stream is not PIPED at all
that's what should be done in order to fix this issue.
the concerned method is:
project OrbitalShell-Kernel, file Component/CommandLine/Processor/CommandLineProcessor.cs , line 577 :
        public int ShellExec(
            CommandEvaluationContext context,
            string comPath,
            string args,
            string workingDirectory,
            out string output,
            bool waitForExit = true,
            bool isStreamsEchoEnabled = true,
            bool isOutputCaptureEnabled = true,
            bool mergeErrorStreamIntoOutput = true
            )

if you are considering to fix this, please remember to assign this ticket to your user.
if you wish to push your results, we will integrate your work after opening a Pull Request and so we will merge


Add a license?

Would you be willing to add a license to this code so everyone knows how they're allowed to use it?

Done! It's under MIT now.


fixed user profile issue on signup issue#766

What is the change?
Fixed user profile issue
Related issue?
close: #766
How was it tested?
Remove this line and tell us how the code was tested.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Did you lint your code before making the Pull Request?
[] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
Before:

After:
https://user-images.githubusercontent.com/68139755/116409282-519d1b00-a851-11eb-9af4-68541cfd082c.mp4

I like you work, would you like to be a maintainer at ALPHAVIO for our next project ?

I like you work, would you like to be a maintainer at ALPHAVIO for our next project ?

Sure, would be very happy to become a maintainer 🙂


Offer advanced configuration mode

play.r-l.o currently offers two "knobs": debug vs. release and stable vs. nightly. There's a variety of other things that are useful to experiment with, so it might be nice to optionally expose them (e.g. requiring toggling an "advanced configuration" checkbox under the settings menu):

debug-assertions: off/default/on
opt-level: 0/1/2/3 (rather than just debug/release)
other -C options like target-cpu and target-feature

Maybe even free-form input to supply arbitrary arguments to rustc.

This is similar to #32 isn't it? @ranma42 stated he implemented such changes too.


Allow overriding the compilation date/time

This is to simplify the process of generating repeatable ghostfat images from tests.
Supporting this will help automate validation that the resulting image files are unchanged.

All macros are now have the prefix COMPILE_, and short names.


Remove requirement for passing server when using rpc macro

This PR was made after discussions with @cheatfate about the rpc macro's dependency on passing an RpcServer object around in order to automatically register it.
The rational is that by passing a server to bind to, you're potentially breaking the separation of concerns in submodules which shouldn't need to know how the server side is set up, or worse, requiring a global simply so that you can satisfy the automatic server.register call inside rpc. This inhibits writing thread safe code and obstructs modularisation of RPCs to different server instances.
RPCs registered to multiple servers allows:

Multiple RPC servers on a single thread, or use multiple threads without worrying about a dependency on globals or threadvars.
Balancing workload for high CPU or RPCs called with high frequency across different internal servers, allowing smarter management with limited resources.

To address this, I've split rpc into three macros:

The original rpc is now called registerRpc to explicitly show it is doing the extra work of registering an RPC to a particular server.
rpc that simply creates the procedure without registering
rpc that creates the procedure with a generated name, and passes this name back to you so you can register it with any path you wish, without worrying about proc name clashes.

Additionally, to help support these new mechanisms, register has been updated to have three variants:

Register using vararg path names
srv.register("a.b", "b.c")
Register using a symbol
srv.register(procName)
Register using an array of symbols
srv.register([ab, bc, d])

This is currently a work in progress and will breaks tests for now.
I've added some examples at the bottom of servertypes.nim to show how the calls are used.

This PR has already been incorporated in @cheatfate's PR #13, but is easier to see the macro directly here.

I don't understand the motivation here. What's wrong with having the RCP procs registered on a particular server instance? You can again create as many server instances as you want and you can create helper procs that register a particular set of procs to a particular server.
This API makes you jump through hoops for the common case of having one server handling all of the RPC procs.

@zah
You can create multiple server instances, but you can only do so after you've attached it to an RpcServer instance.
So, in order to register an RPC to mutliple servers, you'd have to do this:
passedRpcServerInstance.rpc("myrpc"):
  # ...
anotherRpcServer.add("myrpc", rpcMyRpc)

As such, you have to have a global passed around because the RPC procs are exported, so you can't do this for example:
proc addRpcSubset*(server: RpcServer) =
  server.rpc("rpc1"):
    ## ...
  server.rpc("rpc2"):
    ## ...

@cheatfate concern was that by having to pass around the RpcServer object, we'd have to provide global RpcServer instances, which hurts more when implementing threading, etc. and also means it's more tying of modules together, as you have to import the module where the global RpcServer is defined, or else have all your RPCs in one module with the server definition.
Allowing the rpc's to be created without registering simplifies dependencies.
The original RPC macro is still there as registerRpc, and this covers the most simple case as you mentioned.
server.registerRpc("myRpc"):
  # ...

Currently in order to support invoking rpc inside a proc all that's required is removing the * from the proc.
Doesn't it make sense to offer more choice with the API though? If people want to declare RPCs and manually attach them to server, there is no way to do this currently - you must pass an RpcServer object to take advantage of the automatic parameter marshalling.

Closed in favour of not-exported the generated rpc procs, allowing creating RPCs in proc scope.


Mount Internal Storage as Mass Storage(USB drive)

This is very useful feature when copy a lot of files

it's already added while you try to backup or restore your boot.img.bak


Latest build gives Error 500 when creating tag from UI

GitLab 6.6.0.pre 98fe8fb
When using the GitLab UI to create a new tag "v2.0.2" from "HEAD", I get a 500 error, but the tag is nevertheless created.  The error happens in Event.create_ref_event.
The problem seems to be with commit 8587e3a357add7371b2286f3ab642c9ea8f58e2e
Parameters: {"project_id"=>"influencer-marketing/outlook-addin", "id"=>"v2.0.2a"}
Completed 500 Internal Server Error in 619ms
NoMethodError (undefined method `commit' for #<Gitlab::Git::Tag:0x00000004a40c78>):
app/models/event.rb:63:in `create_ref_event'
app/controllers/projects/tags_controller.rb:28:in `destroy'
app/controllers/application_controller.rb:57:in `set_current_user_for_thread'

Thanks for the issue report but we only support issues for the latest stable version of GitLab. I'm closing this issue but if you still experience this problem in the latest stable version, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.


I can give you all the api and all the code, contact me with Email！

I can give you all the api and all the code, contact me with Email！

Hey could you share it?


Json should also show squiggly lines for MSSQL

(Tried on VSCode Prisma insider plugin version 4.0.46)
Since Json isn't supported by MSSQL, the VSCode plugin should ideally show squiggly lines whenever using this type so that makes it easier to anticipate.
prisma generate already shouts so we're good there.

What version were you using @thebiglabasky? (4.0.46 is not a valid version, it should be something starting with 10).
With the current Insider (10.0.88) it already shows red squiggly lines.