Clarification on GHSA-chcr-x7hc-8fp8

Is there an aspect of GHSA-chcr-x7hc-8fp8 that is specific to devise-two-factor, or is it just that it has no built in mechanism to counter brute force attacks?
If it's the latter I wonder if the security advisory could be withdrawn (while keeping the readme update) as that feels out of scope of this library and having it as an advisory results in any use of this library being flagged by security monitors with the only course of action to ignore it (which for me comes with a bunch of paper work that has to be carried throughout the applications lifecycle).

+1 to this
tagging @bsedat to hear your thoughts whenever you have a sec!

There is nothing specific to devise-two-factor. The purpose of the CVE and GHSA is to make sure users are aware that they need to implement mitigations for the risk.
Apologies for the paperwork. I'd like to learn more about it. What workflows are flagging the advisory?

Any consumer of the GitHub Advisory Database, which are most of the big players - so dependabot:

And tools like osv-detector and osv-scanner which use https://osv.dev/ which aggregates from GHADB among other sources:
❯ osv-detector .
Loaded the following OSV databases:
  RubyGems (802 vulnerabilities, including withdrawn - last updated Tue, 16 Jan 2024 17:31:37 GMT)

Gemfile.lock: found 225 packages
  Using db RubyGems (802 vulnerabilities, including withdrawn - last updated Tue, 16 Jan 2024 17:31:37 GMT)

<EMAIL_ADDRESS>is affected by the following vulnerabilities:
    GHSA-chcr-x7hc-8fp8: Devise-Two-Factor vulnerable to brute force attacks (https://github.com/advisories/GHSA-chcr-x7hc-8fp8)

  1 known vulnerability found in Gemfile.lock

Those are the tools I use at my work, though I would assume other tools like synk would also be flagging this

Thank you for the information. I'll bring it internally and discuss with the team - removing or disabling the devise-two-factor gem like bundler-audit suggests would be would be worse for security overall.
More of my thoughts for additional clarity: devise-two-factor doesn't natively protect against brute force attacks but applications using it for 2FA still have a better security posture than ones without. A attacker would need knowledge of the existing username, password, and get lucky with a collision. Without a 2FA solution like devise-two-factor the user account would already have been compromised with the known username/password.

For anyone using bundler-audit, you can ignore this CVE using the "ignore" syntax like this: bundle-audit check --ignore CVE-2024-0227.

@bsedat any update on this? I appreciate what you're trying to do with this but it's not really a good fit with how advisories work.
Personally I think the update on the readme about this is really the way to go.

Hi everyone,
Thanks for your patience. We're going to be moving forward by retracting the CVE and GHSA. The underlying issue is out of scope for the project and a problem with the underlying protocol but we'd still like to communicate the issue to make sure it gets addressed at the application level. I'll report here once that process is done.
I'm sorry for the inconvenience this caused!

I'm going to resolve this since the advisory has now been withdrawn


Exclude mediaont-api.idl from at least whatwg/idl/

See https://github.com/web-platform-tests/wpt/pull/11874#discussion_r201253411.
This spec does use IDL, but I doubt very much that it will ever be implemented by any browser.

No problem. Now removed from whatwg/idl.

Thanks @tidoust!


Update style guide

@samtstern While working on #711 the auto formatting was doing everything alphabetically which makes no sense with ConstraintLayout since constraintBottom_... would end up first and constraintTop_... would end up last. This PR updates the style guide so that everything is ordered the following way (including android:layout... and android:padding...):

left
right
top
bottom

Oh and I also made the style guide add a space to the end of a tag since that seems to be the convention.

Thanks for this!  Just FYI I want to leave this until after version 2.0 since it touches a lot of files and is just cosmetic.

@samtstern yup, makes sense!

@samtstern Ok, merged from master!

Gonna merge this one into master since it has no functional changes.


Correct publish action on every CI build

Right now on every CI build we have a publish gem action. Maybe we will try to run this action on specific branch or only for commit to main?

Only for tags, I think


SplitLayout: It's not possible to configure individual pane's width

Closed with https://github.com/grafana/scenes/pull/496


Remove deprecated controller.service.name from nginx-ingress

Fixes EKS-CI https://github.com/epinio/epinio/issues/2162
Test-run https://github.com/epinio/epinio/actions/runs/4598909150/jobs/8123617902

Codecov Report
Patch coverage has no change and project coverage change: -25.25 :warning:

Comparison is base (73cd17e) 33.80% compared to head (083a90f) 8.56%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #2181       +/-   ##
==========================================
- Coverage   33.80%   8.56%   -25.25%
==========================================
  Files         182      95       -87
  Lines       15184   10684     -4500
==========================================
- Hits         5133     915     -4218
- Misses       9356    9714      +358
+ Partials      695      55      -640

Flag
Coverage Δ

acceptance-api
?

acceptance-cli
?

unittests
8.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 141 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


HeroAvatar: never save images from images service

Describe the bug
In https://github.com/opencollective/opencollective-frontend/blob/00688a2801eedf22d8d45c88199f5a3cf56ec72e/components/collective-page/hero/HeroAvatar.js#L215, the component happens to sometimes save the URL from the image service (https://images.opencollective.com/...).
Expected behavior
We should never save images from the image service, the URL that goes there must be a raw URL (collective.image).

Also maybe on a slightly related note; I see that the function upload(file) has been marked deprecated; but the comment moved to lib/file-upload.js` seems not correct. I cannot find such file. :thinking:
https://github.com/opencollective/opencollective-frontend/blob/bfc6a07cea4a22fc23b07555bd9e97de3c970100/lib/api.js#L44-L49

I just did a pull request removing the imageUrl from getting saved. I am wondering it's simple as removing part of the condition right? :thinking: Is there anything else you can think that needs to be done here?

@SudharakaP Nope that should do it :slightly_smiling_face:


New gem release including Capybara 2.5 support?

I'm using the gem available in https://rubygems.org and the latest changes to support the deprecation of default_wait_time are not in there yet.
Is is possible to generate another gem with those improvements?
Thanks

Just released siteprism 2.8 which includes the fix :)


Add support for ordering menu items and specifying external links

Adds support for the isExternal and asLastNode parameters of NavigationExtensions.AddNavigationNode by adding -First and -External switch parameters. Excluding the switches preserves current behavior (new items are added to the end of the collection and not marked external).

Hi @casselc, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Thanks!


Hyperlink to #legacy-api on npmjs.com is broken

The various links to "the legacy API" section at the npmjs.com documentation are broken.
There is no id/name defined at that section for this to link to.

Oh, wait. Are they all broken?
Just also found:
Hyperlinks point to: .../express-validator#sanitization-chain-api
id in HTML is actually: #user-content-sanitization-chain-api
I'd be happy to fix these up (it would be my first open-source contribution!) but I presume I need permissions to edit that npmjs.com page?

Are you unable to navigate? I see the anchor IDs don't match the links, but they all work for me:

Also we can't change them only on npm, it generates that from the project's README.md file, which works just fine on GitHub.

It seems that they work in Chrome but not Safari on macOS, my iPhone or iPad (all running latest versions).

@jen729w it might make sense to report this on https://github.com/npm/www/issues.


Make it possible to turn the foreign key constraints off?

I'm trying to write some integration tests for my system. I'm using Effort for keeping my persistence context in memory. However, since the data model of my system is huge and there are lots of consistency contraints on many tables, I have to prepare much more data than I need for the test case just to satisfy foreign key contraints. Thus I'd like to turn the foreign key check off. I'm aware this makes my in-memory model less consistent with the real model, but in most test cases taking responsibility for this will be better than struggling with making the model just work.
Or maybe there is already some way to do it?

Hello @azsdaja ,
At first sight, it could maybe be possible to do such a request.
I cannot promise it yet but I will certainly take more time to investigate it this week before assigning this task to my developer if that's possible.
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Hello @azsdaja ,
We started this request but my developer asked me if you could provide him a sample project.
The reason for this project is to make sure we will support your case since:

We can do something on Effort side about constraint
We cannot do anything on EntityFramework side when they are validating the constraint

So we want to make sure the code we will develop will work on your scenario

Thanks for taking my request into consideration. I'll attach a snippet tomorrow.

Hello @azsdaja
Since our last conversation, we haven't heard from you.
Would it be possible to provide ys a sample project?
Looking forward to hearing from you,
Jon

Sorry for delay, I was busy unfortunately. But I'm still interested in this issue. I'm hoping to provide the project tomorrow. Otherwise feel free to close the issue and if I have the project later, I'll reopen it.
Thank you.

Awesome!
Don't worry, we all have unexpected tasks along our way!
We will leave it open for another week!
Looking forward to hearing from you,
Jon

Finally I found some time for it. Here it is. The data hierarchy is basic, but it presents the problem.

Awesome,
We will look at it ;)

Has any progress been made on this?  I'm guessing no.

I figured out a workaround.  Entity Framework provides the ability to ignore database models in its OnModelCreating method via the ModelBuilder.
public class SampleDbContext : DbContext
{
    private readonly SampleDbContextTestConfiguration_IncludedTypeCollection _testConfiguration = null;

    // .. other constructors

    // new constructor used only for testing purposes
    // use InternalsVisibleTo assembly attribute to access this constructor in tests
    internal SampleDbContext(DbConnection dbConnection, SampleDbContextTestConfiguration_IncludedTypeCollection configuration)
        : base(dbConnection, false)
    {
        if (!IsInMemoryDatabase(dbConnection))
            throw new InvalidOperationException("Expected database connection to in-memory database supplied by Effort!");

        _testConfiguration = configuration ?? throw new ArgumentNullException(nameof(configuration));
    }

    // ... all your DbSet properties

    protected override void OnModelCreating(DbModelBuilder modelBuilder)
    {
        // ... other model configurations

        IgnoreDatabaseModelsForTesting(modelBuilder);
    }

    private void IgnoreDatabaseModelsForTesting(DbModelBuilder modelBuilder)
    {
        if (_testConfiguration == null)
            return;

        // use reflection to retrieve all database model types referenced by the context
        // likely need to do something different for your database context unless all database models inherit from a base type
        var dbModelTypeCollection = typeof(SampleDbContext).Assembly.GetTypes()
            .Where(t => typeof(DbModelBase).IsAssignableFrom(t) && !t.IsAbstract)
            .ToArray();

        // ignore all database models except for the ones included in the configuration
        // foreign key constraints will still be enforced across the included database model types
        modelBuilder.Ignore(dbModelTypeCollection.Except(includedTypeCollection));
    }
}

// new type to provide fluent interface for specifying database model types
public class SampleDbContextTestConfiguration_IncludedTypeCollection : IEnumerable<Type>
{
    private readonly ImmutableHashSet<Type> _allowedTypeCollection;

    public SampleDbContextTestConfiguration_IncludedTypeCollection()
    {
        _allowedTypeCollection = ImmutableHashSet<Type>.Empty;
    }

    private SampleDbContextTestConfiguration_IncludedTypeCollection(ImmutableHashSet<Type> typeCollection)
    {
        _allowedTypeCollection = typeCollection ?? throw new ArgumentNullException(nameof(typeCollection));
    }

    public SampleDbContextTestConfiguration_IncludedTypeCollection IncludingDbModel<T>() where T : class, DbModelBase
    {
        return new SampleDbContextTestConfiguration_IncludedTypeCollection(_allowedTypeCollection.Add(typeof(T)));
    }

    public IEnumerator<Type> GetEnumerator() => _allowedTypeCollection.GetEnumerator();
    IEnumerator IEnumerable.GetEnumerator() => GetEnumerator();
}

Ran into a snag related to model caching.  Implementing IDbModelCacheKeyProvider on the DbContext did the trick.  I've modified the sample above accordingly.


Enable saving Notes in Vetting Worksheet

In the Vetting Worksheet view, I tried to enter a note at the top but got an error message saying "Note did not save. Please try again."

This functionality works properly in the production code, so there is something that the code doesn't like in the new code.

Finally figured it out. I disabled the user data and had its restoration at the bottom of the todo list. It should be working now.

excellent, Andy! thank you :-) ==> Dan

On Apr 15, 2021, at 2:41 PM, Andy Situ @.***> wrote:
Finally figured it out. I disabled the user data and had its restoration at the bottom of the todo list. It should be working now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/dandahle/Catalyst-AppVetting/issues/228#issuecomment-820748329, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQDU4OPT7SIUSRROPHEYVTTI5MPPANCNFSM4Z2DZQ6A.


after i format document,the user stats broken...

is possible to format it without make it broken.?

I made some changes, but was unable to replicate the issue. What do you mean by "format" it?
Additionally, I visited your repo's demo and everything seemed to be working fine.
Could you post the changes you made that break it?

format the code,user stats broken.

I was able to replicate this; for some reason, it appears that when using VSCode/ium's Format Document, an extra  closing is added, closing the div.row inside the main content sooner than expected.
I have no idea why that happens though, and I'm not sure if there's something that can be done to fix it. I'm open to suggestions.

That is not the bug with this repo, that issue is actually caused by VSCode formatter. After replicating your issue, I found out that In the process of formatting the document VSCode is moving <div id="stats" outside from <div class="row" in which <div id="main" exists, which was causing the main element to cover the whole available width. You can fix it by removing extra closing div tag, reformatting the document and moving <div id="stats" inside the <div class="row" element.
This should fix the issue you are facing.

oh thanks


Bug: XSS Vulnerability

LAZO is vulnerable to XSS. For an example, follow this link (It doesn't do anything evil):
http://lazojs.org/?field="><script>alert(1)%3B<%2Fscript>
I believe XSS could also be achieved via using crafted cookie content, as cookie data is also serialized into server responses. Is it possible to remove query string parameter data, and cookie data from the serialized server response?

Thanks. The cookie data should be removed and we should be sanitizing the
query parameters.
On Tue, Apr 7, 2015 at 11:18 AM, Adam<EMAIL_ADDRESS>wrote:

LAZO is vulnerable to XSS. For an example, follow this link (It doesn't do
anything evil):
http://lazojs.org/?field="><script>alert(1)%3B<%2Fscript>
I believe XSS could also be achieved via using crafted cookie content, as
cookie data is also serialized into server responses. Is it possible to
remove query string parameter data, and cookie data from the serialized
server response?
—
Reply to this email directly or view it on GitHub
https://github.com/lazojs/lazo/issues/228.

@adam-26 Can you please send email to<EMAIL_ADDRESS>Thanks, Jason

Fixed in v1.2.4 and v2.0.15-alpha. Query and path parameter values are now encoded in the first page load. The values are decoded during client initialization.


Finalize README

In this PR I did the following:

fix #1

Very nice work, Damiano!

tHANKS @PietrH AND @RCinbo; i IWLL MERGE NOW;


Macro names and parameters should not be visible

Description
Macro name and parameters are not visible in the rendered PDF file, but only in the HTML version.
This problem seems to arise for all paper using the standard class for the TheoretiCS journal (https://theoretics.episciences.org/)

If this can not be changed on arXiv's end, the editors of TheoretiCS would be interested in how to change the class file to avoid the issue.
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
Other
Internal issue ID
141f2647-0033-4042-a40c-815bb7f16acc
Paper URL
https://browse.arxiv.org/html/2212.12802v2
Browser
Chrome/<IP_ADDRESS>
Device Type
Desktop

@rasmus-pagh it's not about changing the original class file per se. Instead, one would need a new binding (a .cls.ltxml file) contributed to the LaTeXML project, so that the macros receive appropriate support.

Thanks for the quick reply! The journal is nonprofit, open access, and run by volunteers so I am not sure if there are resources for them to create a mapping file. On the other hand it is potentially not too complicated in which case I might be able to help.

Right, it's either their team, some of their authors, or us (the latexml team) that eventually has to spend some time and contribute a mapping file.
We have some last resort fallbacks in place in latexml, where an unknown class may receive partial support, but only when the frontmatter macros defined by the class file match exactly the standard names (and the usual argument signatures). If \ThCSauthor was exposed as the regular \author, the fallback support would have kicked in.
But if you'd like high quality markup, someone has to write a dedicated mapping file.


idam-1049/fix email query params encoding

Description

fix email query params encoding of & between params

FIDC Update Required:

[ ] applications (AM)
[ ] agents (AM)
[x] scripts (AM)
[ ] auth trees (AM)
[ ] connectors / mappings / scheduled recons (IDM)
[ ] cors (AM/IDM)
[ ] access config (IDM)
[ ] custom endpoints / scheduled scripts or tasks (IDM)
[ ] managed-objects (IDM)
[ ] password-policy (IDM)
[ ] services (AM)
[ ] internal-roles (IDM)

:-(


Automatic start schedule standup meeting on irc

Due to certain task people are busy sometime so there is a high chance to start the standup meeting on our schedule time (3PM IST) manually.
It would be great if this can be automated i mean on working days it should start at 3 PM IST and ends max 3:15 PM IST if nobody respond.

There are two options for implementing this, one is to use https://github.com/Gandi/hubot-cron-events with 0 0 15 ? * MON,TUE,WED,THU,FRI * as the cron and write an event listener that will start the standup.
Although, I presume, we might not want to start the standup someday and it might send unnecessary pings on the IRC.
We can also use a message scheduler like https://github.com/matsukaz/hubot-schedule to send a reminder on the IRC to start the standup.
Which would be the better option?

I like the second option.. Let's see what the others think, @minishift/minishift-dev

Closing this as we decided it would be too noisy!


Updating app path for great win.

Moving app working path to /static-server as running it from / is tre mal.

Already tested on dev branch & image. Merging.


I ask question again - for what is good such framework/technology?

Versions

nuxt:
node:

Reproduction

Install standard hello world example.
Run ab -c 500 -n 2000 http://localhost:3000/
Get 250 requests per second. It is good result?
I ask question again - for what is good such framework/technology?
Only for blog?
This is ApacheBench, Version 2.3 <$Revision: 1879490 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)
Completed 200 requests
Completed 400 requests
Completed 600 requests
Completed 800 requests
Completed 1000 requests
Completed 1200 requests
Completed 1400 requests
Completed 1600 requests
Completed 1800 requests
Completed 2000 requests
Finished 2000 requests
Server Software:
Server Hostname:        localhost
Server Port:            3000
Document Path:          /
Document Length:        1367 bytes
Concurrency Level:      500
Time taken for tests:   7.812 seconds
Complete requests:      2000
Failed requests:        0
Total transferred:      3178000 bytes
HTML transferred:       2734000 bytes
Requests per second:    256.01 [#/sec] (mean)
Time per request:       1953.034 [ms] (mean)
Time per request:       3.906 [ms] (mean, across all concurrent requests)
Transfer rate:          397.27 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0   13   6.6     13      26
Processing:    69 1930  54.6   1947    2000
Waiting:        5 1016 497.7   1011    1922
Total:         69 1943  55.4   1963    2000
Percentage of the requests served within a certain time (ms)
50%   1963
66%   1968
75%   1970
80%   1971
90%   1978
95%   1982
98%   1985
99%   1986
100%   2000 (longest request)

Additional Details

Steps to reproduce
What is Expected?
What is actually happening?

Duplicate of https://github.com/nuxt/nuxt.js/issues/9022


Instant loses precision

The easiest way to reproduce this is as follows:
var x = Instant.FromUtc(2020, 7, 2, 0, 0).PlusTicks(1333333);
var y = x.ToDateTimeUtc();
var z = x.ToDateTimeOffset();

var aaa = conn.QuerySingle<Instant>("SELECT @x", new { x }); //2020-07-02 00:00:00.133
var bbb = conn.QuerySingle<Instant>("SELECT @y", new { y }); //2020-07-02 00:00:00.133
var zzz = conn.QuerySingle<Instant>("SELECT @z", new { z }); //2020-07-02 00:00:00.1333333

So precision is being lost somewhere in the round trip.
var xxx = conn.QuerySingle<Instant>(@"
    DECLARE @x datetime2 = '2020-07-02 00:00:00.1333333' SELECT @x"); //2020-07-02 00:00:00.1333333

So precision is being lost when it's sent over to the database, but works fine when reading.

The easiest way to reproduce this is as follows:
var x = Instant.FromUtc(2020, 7, 2, 0, 0).PlusTicks(1333333);
var y = x.ToDateTimeUtc();
var z = x.ToDateTimeOffset();

var aaa = conn.QuerySingle<Instant>("SELECT @x", new { x }); //2020-07-02 00:00:00.133
var bbb = conn.QuerySingle<Instant>("SELECT @y", new { y }); //2020-07-02 00:00:00.133
var zzz = conn.QuerySingle<Instant>("SELECT @z", new { z }); //2020-07-02 00:00:00.1333333

The issue here is that InstantHandler needs to call
parameter.DbType = DbType.DateTime2

It looks like Dapper + Microsoft.Data.SqlClient causes this issue.

This might be due to the SqlParameter Precision and Scale properties.

Warning
Data may be truncated if the Scale property is not explicitly specified and the data on the server does not fit in scale 0 (the default).
For the DateTime2 type, scale 0 (the default) will be passed as datetime2(7). There is currently no way to send a parameter as datetime2(0). Scales 1-7 work as expected. This problem applies to DateTimeOffset and Time as well.

...Precision and Scale are required for output parameters...

https://docs.microsoft.com/en-us/dotnet/api/system.data.sqlclient.sqlparameter.scale?view=dotnet-plat-ext-5.0#System_Data_SqlClient_SqlParameter_Scale


Cf #27 - Added the possibility to do multi tenancy from the request

Ref #27

Yo @boblefrag :)
I changed the unit tests for them to pass with a Site (overriden for a custom .get_current method).
Let me know if this PR looks good to you. As you said, there's a small incompatibility backward, so I upgraded to 2.X version.
Thanks for your help


pass $c along to events

I was having a weird issue that I can't get the current page from an event. this should be an easy fix.

Where are you trying to extend the event? if you do it right in the on_start event, then $c isn't set yet, (you can't get it using Page::getCurrentPage()).
there are several ways to get around it, make your own $c (using the request library), or just use an event that is triggered later.

the on_page_output event.
how would you get around it?
anyway, seems like something easy to implement in the core.

this is how it is done in the core:
`		$req = Request::get();
if ($req->getRequestCollectionPath() != '') {
if (ENABLE_LEGACY_CONTROLLER_URLS) {
$c = Page::getByPath($req->getRequestCollectionPath(), false);
} else {
$c = $req->getRequestedPage();
}
} else {
$c = Page::getByID($req->getRequestCollectionID(), false);
}
	$req = Request::get();
	$req->setCurrentPage($c);`

In the on_page_output event you should have access to the collection object though...
Im not sure, I would have to test it.


local network issues when using Storage Explorer

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.26.1
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20221018.5
Platform
Linux (snap)
OS Version
Ubuntu 22.04
Bug Description
This might be the same as https://github.com/microsoft/AzureStorageExplorer/issues/1099, but I'm not quite sure.
Situation: I have a 300Mbps internet connection at home, use LAN cable to the modem. I tried to copy a lot of folders within an Azure storage account (Data Lake Gen 2)using ASE on my laptop. I don't think this downloads and uploads the files to my local network, because my sent/received traffic stays low.
As soon as I start such a transfer, my girlfriend's laptop's VPN connection (she was also working from home) dies. As soon as I kill Storage Explorer, it comes up again. Saw some name lookup error at some point, so think DNS resolution was impacted. Meanwhile I did not seem to experience network issues; did a speedtest from my machine (fast.com) while the transfer was running, still hit +250Mbps and around my max upload speed (20Mbps), latency was normal too.
When I browsed to the azure portal with the transfer running, it worked okay, however when I clicked through to the blobs I tried to copy, the listing did not work. It proposed to run some kind of diagnostics, some checks passed, others failed (screenshot below). The transfer in Storage Explorer did also seem to hang. Since cancel takes some time, I just killed ASE and removed the target folders. I restarted it and tried again, same error.
Did not really think it would work, but I have a VirtualBox with Windows on the same machine, installed ASE in there, ran the same copy operation, completed without any hangs or causing network problems. -> I thought this worked but must have been a coincidence, have the slow/hanging transfers +impact on network there as well (although it seems slightly faster but could be wrong)
Steps to Reproduce
Not sure if this is very useful, since I'm not sure this happens every time or depends on external factors.

Launch ASE, copy a lot of folders (~around 400) within a storage account using copy and paste (ADLS Gen 2)
The transfer does not seem to progress and you may experience network issues.

Actual Experience
Experiencing network issues when copying using ASE. On second thought, I don't think it's actually related to connection speed cf. https://github.com/microsoft/AzureStorageExplorer/issues/1099, cause I now did the same on my company WiFi and that only has 15Mbps down/up. Wondering how the copy works now, does it launch separate requests (too many simultaneous?) for every blob?
My company probably has a better (managed) switch, so maybe that has an impact?
Tried playing around with bandwidth limit, maximum concurrency... did not seem to have an impact.
If you can provide any instructions to trace down the cause (commands I can execute, log files that can help) I'd appreciate! Not sure if I can always reproduce, could e.g. also depend on external factors but willing to try.
Expected Experience
Additional Context
Screenshot of what I get in the azure portal while trying such a transfer:

Experimented some more, seems that the "File Concurrency" under Settings can help to solve this. What's the default? It starts a copy operation for every individual file, all simultaneously? I put it to 4 and I got transfer speeds over 500Mbps and no issues

@matthiasdg AzCopy probably isn't opening a connection for every individual file right away, but it is for probably a large number of them. You can also try tweaking the Network Concurrency setting. Others have had success in similar situations after using "Adjust Dynamically" or a custom value.

Closing due to lack of response. If you still have this issue, please open a new issue instead.


Defer connect to jms in startBundle

Fixes #26175
Please add a meaningful description for your change here

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

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] 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.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

I now believe this is somewhat red herring. Direct runner simply is not efficient:
cron run 473: actual number of records 35990 smaller than expected: 100000.
cron run 475: actual number of records 26030 smaller than expected: 100000.
cron run 478: actual number of records 42390 smaller than expected: 100000.
cron run 479: actual number of records 39350 smaller than expected: 100000.
cron run 481: actual number of records 23190 smaller than expected: 100000.
with this change: actual number of records 51990 smaller than expected: 100000.
Defer the connections into startBundle seems help a little bit so I intend to preserve the change, but also decrease the number of record and see.

Run Java_Jms_IO_Direct PreCommit

Run Java_Jms_IO_Direct PreCommit

Run Java_Jms_IO_Direct PreCommit

Jenkins not triggering. Ran spotlessApply locally. Test succeeded locally:
Package	Tests	Failures	Ignored	Duration	Success rate
org.apache.beam.sdk.io.jms	1	0	0	31.978s	100%

R: @jrmccluskey

GitHub Action test passed but Jenkins not triggering. Merging this for now anyway as it is only scoped in JmsIOIT, and validated locally (both spotlessApply and integrationTest tasks)


Add the ability to open the MSYS2 Shell or Cygwin Shell

Either by launching a new external window or open in a new tab within the application. This will be a very useful feature for Cygwin or MSYS2 users.

Sure, noted.


Object Explorer: right-click connection while other connection is expanding causes error to show

Have 2 servers in OE, 1 of which is slow to expand (e.g. a remote Azure SQL DB)
Click on the Azure SQL DB instance to expand
Right-click on the other connection while the 1st is still expanding

Get error Failed to create Object Explorer session.

This seems pretty consistent. I would suggest not targeting for March since it's unclear when this happened, and workaround is click "OK" on error and redo what you were trying to do.

I've seen this error message in other situations too including when just connecting to a server in OE. I also have consistent repro steps that are a bit different:

Add a connection to Azure in OE (you may need to use AAD, I'm not sure)
Connect to the added connection then disconnect
Drag that connection to another server group
Click on the connection again to connect it and the error message pops up

See the referenced duplicate issue #4479 I filed for more

Another repro:

Have an AAD connection into OE (active or inactive)
Open second ADS which will have this connection too
Try to expand(connect) the connection in second ADS
Throws this error and then connects anyway.

I'm also getting this with a local SQL server instance, on first and subsequential connections:


test: fix cypress tests

Fixes our Cypress tests (we use prerecorded data so string changes in the URL break the tests).
Also remove the very verbose log of simpleGit

hm... I'm almost sure that these two spaces are being removed by 'yarn format' command. so it will probably bite us again.

hm... I'm almost sure that these two spaces are being removed by 'yarn format' command. so it will probably bite us again.

Yes. Going to look into this later or


Initial Disclaimer box issue

There is no indication to the user that they have to scroll down in order for the button to activate and they gain access to the site.
need to make it more intuitive.

Added as note in #2940 -- closing specific issue


kumocloud: IndexError during basic checkout due to bad credentials

issue is due to bad KUMO env parameters on pi4.  Error message should be cleaner.
No JSON returned from KumoCloud; check credentials?
Traceback (most recent call last):
  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/kumocloud.py", line 734, in <module>
    tc.thermostat_basic_checkout(
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/thermostat_common.py", line 1146, in thermostat_basic_checkout
    Thermostat, Zone = create_thermostat_instance(thermostat_type, zone,
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/thermostat_common.py", line 1111, in create_thermostat_instance
    Thermostat.print_all_thermostat_metadata(zone)
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/kumocloud.py", line 172, in print_all_thermostat_metadata
    self.exec_print_all_thermostat_metadata(
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/thermostat_common.py", line 63, in exec_print_all_thermostat_metadata
    return_data = func(*args)
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/kumocloud.py", line 106, in get_all_metadata
    return self.get_metadata(zone, None, debug)
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/kumocloud.py", line 154, in get_metadata
    self.serial_number = serial_num_lst[zone]
IndexError: list index out of range

root cause for error was a bad password.
root cause for confusing traceback was missing authentication validation.  Upon validation error pykumo returns empty list of units, not an exception.  I added a check for empty list as well as a check for index error later in the code, and displayed an intuitive error message.  These enhancements were made to both kumocloud and kumolocal classes.


PageContainerToolbar should have a stick on scroll option

Summary
When scrolling I want to have to toolbar stick on the top. The contents should not overlap the toolbar and the toolbar must always be visible
Examples
No response
Motivation
Usage of PageContainerToolbar for long pages is not ergonomic, because user has to scroll back to the screen top
Search keywords: PageContainer, PageContainerToolbar, stick, scroll

Wondering whether we should just provide the page header as a component instead of wrapping the MUI Container


[lit-next] Fix .gitignores to ensure src files/folders aren't ignored

Add leading slashes to ensure src folders aren't accidentally ignored.
For example, lit-element.* will ignore lit-element.js, but also src/lit-element.ts; the intention of the changes were to only ignore the generated files at the root, which requires a leading slash.

Also make sure to run "npm run ignore-sync" to sync the prettier and eslint ignore files.

@aomarks It seems to not have affected the ignore file generation, since it looks like ignore-sync just appends the folder name to nested .gitignore patterns (i.e. both lit-element.* and /lit-element.* in packages/lit-element/.gitignore result in a top-level packages/lit-element/lit-element.*.
Seems like there's a loss in semantic difference with having the leading / there, but it worked out for us in this case.
To be correct, it seems like ignore-sync should turn nested file patterns not starting with a leading / into e.g. packages/lit-element/**/lit-element.*... 🤷♂

@aomarks It seems to not have affected the ignore file generation, since it looks like ignore-sync just appends the folder name to nested .gitignore patterns (i.e. both lit-element.* and /lit-element.* in packages/lit-element/.gitignore result in a top-level packages/lit-element/lit-element.*.
Seems like there's a loss in semantic difference with having the leading / there, but it worked out for us in this case.
To be correct, it seems like ignore-sync should turn nested file patterns not starting with a leading / into e.g. packages/lit-element/**/lit-element.*... 🤷♂

Oh yeah, I filed an issue about that, and it was fixed in 3.0.1, so we just need to update the top-level package-lock I think. https://github.com/foray1010/ignore-sync/issues/302


Update to ytdl-commit-66ab08

Don't think there is anything we really need to merge this time.
Worth checking the following though:
https://github.com/ytdl-org/youtube-dl/commit/9112e668a5ea6376017718db9ff13b369d53ad7a
https://github.com/ytdl-org/youtube-dl/commit/d5ef405c5d533c85cebd205a5b7958614c7013f3
https://github.com/ytdl-org/youtube-dl/commit/1634b1d61efa36c31c86b8c64c88dc297a7af28a
https://github.com/ytdl-org/youtube-dl/commit/d9d07a95815a992bf5f876a62f25c831eb3f32ac
https://github.com/ytdl-org/youtube-dl/commit/1e8ccdd2eb77901e18feb8a9d48e62d11651cd1e
https://github.com/ytdl-org/youtube-dl/commit/b2741f2654e6ddfebc1771b5d5fadb5fd6fe3863
https://github.com/ytdl-org/youtube-dl/commit/b2ba24bb026904f3503db71f65d2b1627f08edf1
https://github.com/ytdl-org/youtube-dl/commit/44faa71b19c866b836e4433ddd3e4722ac6d282f
https://github.com/ytdl-org/youtube-dl/commit/2d2a4bc8324fc4bc5a235cbd1ee0b0769912bfd1
excluding:
https://github.com/ytdl-org/youtube-dl/commit/e7926ae9f4e5fa258696551a39295402819280c9

no need for compress and long dead other x-gzip etc.

https://github.com/ytdl-org/youtube-dl/commit/2efc8de4d2299e08e0c84d674d7fc7f3fa669487

not much point adding compress content-encoding do not want to advertise it as makes yt-dlp easier to detect.

Template

Before submitting a pull request make sure you have:

[X] At least skimmed through contributing guidelines including yt-dlp coding conventions
[X] Searched the bugtracker for similar pull requests
[X] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[X] I am the original author of this code and I am willing to release it under Unlicense
[X] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at a064f48
Summary
🔄🆙🛠

Update youtube-dl commit hash in README.md to sync with upstream. This helps maintain yt-dlp's compatibility and functionality.

yt-dlp updates
youtube-dl commit hash
Autumn maintenance

Walkthrough

Update the youtube-dl commit hash to keep yt-dlp compatible with upstream changes (link)

Just readme was updated?

Yes, the other changes were deemed unnecessary

You might like this next time, from ytdl-org/youtube-dl@d9d07a9:

add limited ! evaluation [to js_to_json()] (eg, !!0 -> false, see tests)

The other stuff is plundered from here anyhow.


Delete docker-cleanup.sh

I don't think this is used any more? Our recommendations are here: https://buildkite.com/docs/tutorials/docker-containerized-builds#adding-a-cleanup-task

Yup, nice one.


Any way to share files between distributions outside of home?

I want to share my java distribution (currently in /opt) between distributions. Is there a recommended way to share it? The way I see it, only home directory stays outside rootfs.
Only asking, not requesting a feature.
Thank you, Great work btw!

You could put a folder named opt in your home folder and then symlink it to /opt.
Then just make the symlink whenever you install a new distro.
Switching between distros should keep the symlink.

Thanks, I think this should do...

@SRGOM Pretty much what @thebitstick said. You could add the ln line to your hook script.

sudo ln -s opt /opt && sudo chmod 755 /opt

Also @SRGOM, how did you get Java to work in WSL? Doesn't work for me.

@thebitstick I haven't. I was excited for a very brief  bit when I learnt of the "-Xint" option that allows it to work partially (still broken for actual use because of internal path issues but the hanging issue doesn't occur). However, it was too slow to be of any use on my projects.


Issue with Vue monorepo

For those using Windows operating system, if configured according to config (have input & output):
DynamicPublicDirectory([

      {input: 'apps/a/src/assets/**', output: 'static/assets-a'},
      {input: 'apps/b/src/assets/**', output: 'static/assets-b'}
    ])

There will be a difference on node js window join
Fixed in version: 2.1.2

@zhixiaotong i tried fork your repo, both dev and prod environment work fine, images are fully displayed. what is the problem here?

Thx. I pushed changes to https://github.com/zhixiaotong/monorepo-assets-demo, picrtures in folder a and b dont display.

After build, preview works fine.

I have tested your repo in dev now, and it displays perfectly on browsers, chrome, safari, fireox,..

safari

This... is so strange.I am using Google Chrome.

      This... is so strange.I am using Google Chrome 130.0.6723.92.

if possible, please help me with the following:

Clear cache or open anonymous tab chrome
Run server with different port, for example: 3000

And can you tell me what operating system your computer is running?

And can you tell me what operating system your computer is running?

window11

And can you tell me what operating system your computer is running?

windows11

I just tried it on windows 10, 11 and macos and it runs stably.

I tried again, deleted the node_modules and downloaded it again, cleared the browser cache, and still got the same result.I'm confused. /(ㄒoㄒ)/~~

I tried again, deleted the node_modules and downloaded it again, cleared the browser cache, and still got the same result.I'm confused. /(ㄒoㄒ)/~~

try change port serve & open anonymous tab:

I tried again, deleted the node_modules and downloaded it again, cleared the browser cache, and still got the same result.I'm confused. /(ㄒoㄒ)/~~

try change port serve & open anonymous tab:

I also tried. I asked my colleague to help clone the repository and run it locally. His result is the same as mine.

Okay, I think there is a problem if running the code from windows. Unlike me, running the code from macos and opening on windows operating system. Maybe, join on windows works differently. I don't have windows operating system to run my library code. So I might try to come up with a fix, if it doesn't work, give me a chat connection with you, and you can help me solve this problem

Now!! Please help me version: 2.0.2

Okay, I think there is a problem if running the code from windows. Unlike me, running the code from macos and opening on windows operating system. Maybe, join on windows works differently. I don't have windows operating system to run my library code. So I might try to come up with a fix, if it doesn't work, give me a chat connection with you, and you can help me solve this problem

with pleasure

Now!! Please help me version: 2.0.2

ok

Now!! Please help me version: 2.0.2

ok

Nice!!! Both dev and build works normally.

Now!! Please help me version: 2.0.2

ok

Nice!!! Both dev and build works normally.

Thanks for reporting this issue!! Otherwise windows users will face the problem!!

Thanks for the fix, now I can use this plugin to solve the bloated problem! ^_^

@zhixiaotong LOLLL!! I have a mistake about the version, it should be 2.1.2 =))

@nguyenbatranvan Hi, here I am again. I found that if I add the base attribute to vite.config.ts, the picture cannot be displayed. Is it because the plugin does not support base now or is it a problem for me to use? Thanks.

@nguyenbatranvan Hi, here I am again. I found that if I add the base attribute to vite.config.ts, the picture cannot be displayed. Is it because the plugin does not support base now or is it a problem for me to use? Thanks.

i think it's a bug!! find a way to put base in router of 3rd party library first. i will look into this tomorrow!! thanks for reporting

Please create another issue for me, if you can. hhhh!!

Please create another issue for me, if you can. hhhh!!

ok


Prisma.JsonValue typescript bug after updating to 1.17.0

What version of Remix are you using?
1.17.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
Have a prisma schema model that uses the type 'Json' like so:
model Example {
  json Json?
}

Get data from that model and return it from a loader, and use examples in the route component like so:
export async function loader({}: LoaderArgs) {
  const examples = await db.example.findMany()

  return json({ examples })
}

export default function RouteComponent() {
  const loaderData = useLoaderData<typeof loader>()

  return (

      {JSON.stringify(loaderData.examples[0].json)}

  )
}

Expected Behavior
Expecting the type of loaderData.examples[0].json to not cause a typescript error, like it didn't before the 1.17.0 update - guessing this is something to do with the new way types are simplified by Serialize.
Actual Behavior
loaderData.examples[0].json has the following typescript error:
Type instantiation is excessively deep and possibly infinite. ts(2589)

Again this worked before 1.17.0, and when downgrading to 1.16.1 the error disappears.

Unable to reproduce. Types are simplified (or in your words, "deconstructed"), but that's by design. But I do not get any warnings or errors about infinite type instantiation neither in my editor nor when running tsc to typecheck.

We are seeing the same issue on our end.
As soon as the data returned by Prisma returns a Json field, this error shows up.
Interestingly, we don't see the issue when we try to access the data directly, but when we start looping over it, the TS error pops up:
export async function loader({}: LoaderArgs) {
  const examples = await db.example.findMany()

  return json({ examples })
}

export default function RouteComponent() {
  const loaderData = useLoaderData<typeof loader>()

  return (

      {JSON.stringify(loaderData.examples[0].json)}  // We have seen this not cause issues
      {loaderData.examples.map(example => example.id)} // This one results in the error. `.json` doesn't even have to be accessed.

  )
}

Can you reproduce within a Typescript playground? Or provide details on what the Example type looks like?

Can you reproduce within a Typescript playground? Or provide details on what the Example type looks like?

Example type doesn't seem to matter. Literally did the same as you in my above screenshots (this comment) with:
const examples = {} as Prisma.JsonValue[]

And I'm still getting the same issue. I'll have a look and see if I can reproduce within a ts playground.

Still not able to reproduce in Typescript playground
https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgKwM4QHZwL5wGZQQhwDkAAlAKYjAAeAtFAK4YD0GEAJpSQFCiRYiOE1SUAMhACG3KABEpMKTnyFi5KjQbM2VKQGMYffhhiUoeA5TgApdBgCCUKFICecSrTMZOqOE5dXAB47TAA1KQAbJkoAPkRsXhhXMGtQjAjo6wBeOFQYKGAMAHM4AB84DCYQACNzcrgaiAhIyiksCvSAeRrkSkMG9IC3BqrIyKSUtPsevoHcpABtAGlKdyK8gqLigF0AfgAuW3tMmJxeEzMLKzgAUVopcFbEXjg4YE4j-MKS15R7I7pU6UXiJXieQTwKSoVwYfT4FiGYCYOCRaSyAAUAEoXm99Jh8h4Hk9KKgjvdHmBWosdnBcjSLm8qDAmFAsGhMBikJ5Ka0-NgsaCLhDoPBuJYmJF4HhETBkVgAEoQJhmADCREgGEopmxuLg+IwhLRMnMCiUdJEYkkJvkiikQWSqQgeFR6PMsWxjNRlHgHz8uWNsjNUgAdDySagQyApGAMRjw1TKDjsvEE60Qx9BW9WKw3gA9PagoA

Here's a reproduction in Typescript playground.
Updated some config settings to match my tsconfig & was able to reproduce the error when trying to access json directly - not when looping through the data like DerJacques.

Noticed @DerJacques was using an older version of typescript and now the issue is there when looping, but not when accessing json directly, as he initially described.
Link

Thanks for the great repro-case, @dT-Nick! Just wanted to add that I re-used an old sandbox, so that's why the TS version was 4.x. Locally we're using 5.0.4. Very strange that sometimes looping is the issue, while other times accessing the attribute directly is the issue.

Thanks for the great repro-case, @dT-Nick! Just wanted to add that I re-used an old sandbox, so that's why the TS version was 4.x. Locally we're using 5.0.4. Very strange that sometimes looping is the issue, while other times accessing the attribute directly is the issue.

Yeah looks like 5.0.4 and 4.9.5 have the error when looping, but 5.1.3 has the error when accessing it directly. :shrug:

Got a prototype for the fix in this playground

can you share patch-package file for this fix i want to test it on my workflow, i get this error on 1.17 as well but using prisma includes instead of JSON wonder if it fixes that case too

I'll put up a PR in a couple hours with this fix

works

Thank you very much, @pcattori! Really appreciate your quick turnaround on this one :)


running TODO log

add uncertainty to home P_load (i.e. power draws for appliances/plug loads and pulls from the hot water tanks)
add uncertainty to weather forecasts and move weather forecasting to the purview of the homeowner MPC

shouldn't the solar irradiance calculations for PV use the angle of incidence formula (houses initialized with an azimuth and a zenith)?

change config file to markup with comments


feat: Add shared element transition

Fixes #139
Changes: Add Event Image Transitions
Screenshots for the change:

@iamareebjamal i was unable to figure out return transition.
Although i was able to find a solution
https://stackoverflow.com/questions/52874175/shared-element-transition-in-jetpack-navigation-from-recyclerview-to-detail-frag
But It doesn't seem to work

Can you please try it with navigation architecture?

@liveHarshit i'm sorry i didn't get you

@iamareebjamal resolved conflicts

I was able to implement the transition, return transition too, with architecture component method, without changing live data observation and no Picasso call back, also
in favourites and searchresult.
But the problem I am facing is a delay in transition because of custom fade & slide animation duration which is 400, and the default share element transition duration is 300.

@aman210697  share the gif ?

@liveHarshit we can also this https://github.com/lion4ik/aac-navigation-shared-elements-transition

@liveHarshit @iamareebjamal return transition are working now please review

Can you please attach gif for return transition?

Build is failing.

@liveHarshit updated

@liveHarshit any update ?

@liveHarshit updated

@liveHarshit updated

I have already provided my review.

Anything left out @iamareebjamal ?


How does node-dbus handle 64 bit numbers?

Since javascript can't really handle 64 bit numbers - wondered how node-dbus handled them.
Should the limit be 53 bits?  I was thinking node-dbus should just reject 64 bit datatypes.
http://stackoverflow.com/a/24037917/49945

Currently it just does JS math so it's not accurate. Yes, need to add run time check for range and/or use big number library  - https://github.com/sidorares/node-dbus/blob/master/lib/dbuffer.js#L191
I use bn.js in node-mysql2: https://github.com/sidorares/node-mysql2/blob/master/lib/packets/packet.js#L124-L134


feat(html): support js template and loader template

Summary

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

Very nice site update! Great work

The javascript function template has been support in https://github.com/web-infra-dev/rspack/pull/7704. Template with loaders need to be compiled by child compiler which may lead huge performance regression. We will try to find a better way to handle it, but before that you can juest use HtmlWebpackPlugin directly.


Update package.json

add redo

cmd+y is more useful than cmd+shift+z

cmd+y in Sublime is a combination of redo and repeat, where vs code doesn't have the repeat command, so it is not 100% the same.  that said, we think we should still take this change, and have a feature request in vs code to support repeat.

ideally this PR includes a when clause:
                "when": "editorTextFocus && !editorReadonly"

but I'll add that after merging the pr.


lavalink error using discord.py and java 11

Description

[NODE-na-localhost:7000] Invalid response received; this may indicate that Lavalink is not running, or is running on a port different to the one you passed to add_node. error when i run the program
Version info
Client used:
Output of java -version:
java version "11.0.9" 2020-10-20 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.9+7-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.9+7-LTS, mixed mode)

Error: Unable to access jarfile Lavalink.jar

This doesn't appear to be a Lavalink problem. It's pretty self explanatory; you're trying to start Lavalink from a directory it's not situated in.

i can fix it?

you used command cd to your project? for start the Lavalink

You are mistaken, Lavalink.jar and application.yml are both clearly in the src folder.

java -jar ./Lavalink.jar

This issue tracker is not for general troubleshooting


added to_masked_array method and masked_array property

This PR adds convienience methods to convert DataArrays to numpy masked arrays.
DataArray.to_masked_array(copy=True) returns a numpy Masked array
DataArray.masked_array returns a masked array that is a view to the DataArray.values.
closes #460

503c0d0 removed the masked_array property and added the use of pd.isnull to calculate the mask.

Looks like you still need to update the docs?

Done. I did need to update the docs.

@jhamman Looks good to me. Feel free to merge.


[SCB-471]watch mode: netty upgrade have add pong response and need to handle it

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.06%) to 87.453% when pulling d3dba85435147a83bb4e80652fc37183c2b2e46f on liubao68:edit-05 into ddacc1714817f0a0deb2e2915e71f980285a1212 on apache:master.


Improve ParquetExec and related documentation

Which issue does this PR close?
Part of #10549
Rationale for this change
While trying to make an example that uses ParquetExec, I found its documentation was sparse and could be improved
What changes are included in this PR?

Add docstrings to ParquetExec and related structs explaining more of what they do and how they work

Are these changes tested?
By existing CI
Are there any user-facing changes?
Just doc strings, no functional changes

@thinkharderdev , @tustvold, @Ted-Jiang  and  @crepererum: if you have time, could you double check that this correctly describes ParquetExec to your understanding?


[Feature Request] Video support

it would be great if the bot can stream video off a YouTube livestream or video into a discord channel

This used to be possible when Go Live was initially released. Discord has completely disabled Go Live for all bots a few days later though.

As stated, bots cannot stream video. If this changes at some point in the future, another feature request (that follows the template) can be filled out.


Bugs when surrounding HOCs that hoist statics

On the current project, we ran into mysterious bugs when placing two react-apollo graphql() HOCs in the same compose() chain. Turned out that because each was followed by a withProps() (ie compose(graphql(), withProps(), graphql(), withProps())) and graphql() uses hoist-non-react-statics to hoist statics, bugs were because graphql() was hoisting the "internal" symbol statics that recompact uses to identify other components as fellow "compactable" Recompact HOCs, so withProps() thought that graphql() was another Recompact HOC that it could condense or whatever (at least this is my understanding)
So my solution was to fork recompact to export the symbols it uses as keys for static properties (opened #95) and fork react-apollo to accept a blacklist of keys not to hoist (which can then be passed the exported recompact symbols)
However, then this week ran into the same issue using a different HOC (withNavigation() from react-navigation) which also hoists statics using hoist-non-react-statics. So hoping there's a better approach than trying to get various third-party HOCs to accept a hoist blacklist. This feels at this point like a flaw in the way recompact identifies other recompact HOCs, since it's considered best practice for HOCs to hoist statics (which to my understanding then causes bugs whenever it sits between two recompact HOCs), but not sure if there's another mechanism besides statics that recompact could use to identify other recompact HOCs?

Thank you for the detailed explanation.
Apparently, react-proxy faced a similar issue and went for a WeakMap (gaearon/react-proxy#45). Looks like a good path forward.
We'll need to provide a polyfill for older browsers, perhaps something in a similar vein to https://github.com/gaearon/react-proxy/blob/v2.0.8/src/createClassProxy.js#L33-L40 which is more lightweight than core-js's WeakMap and safer (see gaearon/react-proxy#50).
Thoughts?

@matthieuprat sure, that does look like basically the same problem faced by react-proxy
My understanding from looking over those react-proxy links is that they tried to use a WeakMap but then switched to using a list to avoid the issues encountered with core-js's WeakMap. Then there is open PR gaearon/react-proxy#62 which may provide more insight - suggests alternative WeakMap polyfills I guess. The advantage to using WeakMap is that (a) references to created HOCs (in keys of WeakMap) are weak and so can be garbage-collected (this comment says that using WeakMap "wasn't paramount in our case" for react-proxy, is recompact different?) (b) lookup time is static (this is referenced in the title of gaearon/react-proxy#62)?
Either way (WeakMap or list) the idea is to use an external module-level data structure to keep track of all recompact HOCs rather than via a static property set on the HOCs themselves, right?
So for recompact would you need two tracking WeakMaps/lists corresponding to compactable and MAPPERS_INFO symbols? So eg isMapperComponent() would lookup component in mapper-tracking data structure and instead of setting MAPPERS_INFO as static when creating class in createComponentFromMappers(), you'd register/store the created class in mapper-tracking data structure (before returning it)?

Exactly.

this comment says that using WeakMap "wasn't paramount in our case" for react-proxy, is recompact different?

Yes, I think it is, in that unlike react-proxy, recompact is intended to be used in production, which means the performance and memory requirements are not the same.
So, it's worth trying to use a WeakMap as the backing data structure if it is available and use a list as a fallback only if it is not available.
Are you interested in working on this? Otherwise, I might be able to free up some time this week to tackle this.

@matthieuprat sure I'll try and get in a PR sometime this week, thanks


Make route writable for params

With regard to path params, our docs say that a route like /users/:id

...these params are reactive strings. If you update a param, the url will be updated accordingly.

At the time of writing this issue that's not true, router.route is DeepReadonly. So before going live, we'll need to reconcile this difference.

@stackoverfloweth I'm going to use this issue to write down some thoughts around this and explore some syntax. I'm not advocating for any of these ideas. Just working out thoughts. Maybe something here will resonate with you or spark and idea.
Problem: Updating params should feel like updating state and less like routing. Binding a param from a route (like a search term, page number, etc) to some ux is common and we'd like at least some first party support for this other than just manually calling router.push or router.replace.
Reactive params object
It would be really nice in some use cases to just bind directly to a param on the route like this.
<input v-model="route.params.page" type="number" step="1">

However changing that example slightly drastically changes the use case. Users probably don't want every update:modelValue event to trigger a route push.
<input v-model="route.params.search" type="text">

There also the problem of updating multiple params at once. This could be quite common, but how do we know if this should trigger two route updates or just one?
function update() {
  route.params.entity = 'user'
  route.params.id = 'pleek91'
}

One possible solution to these is to debounce by default. If multiple param updates happens simultaneously, collect them all and then trigger a single route update. However the debounce necessary for v-modeling text is at least 500ms which IMO is to long for a default. Which kind of eliminates this in my mind other than maybe "nextTick" type debounce to account for the update() example.
I think if we go this route we should give users the ability to configure whether updating a param is a push or a replace action. I'd probably default to replace.
Route patching
It would be convenient to provide a syntax for patching the current route's params. Something that is a shortcut for effectively calling push but with the same route key. This solves the update function issue where multiple params need to be changed at once.
// set multiple values at once
route.update({
  entity: 'user',
  id: 'pleek91',
}, { replace: true })

// set an individual value
route.update('user', 'pleek91', { replace: true })

Param debouncing
It might be nice to offer a built in way of debouncing updates to an individual param.
const search = route.paramRef('search', { debounce: 1000 })

<input v-model="search" type="text">

This also might be better left to userland implementation to avoid having to support this long term.
Param freezing
Tangentially related is a complaint I've always had with reactive params. When the route changes, and a component is about to be unmounted, sometimes the params can change BEFORE the component is unmounted. And cause random errors to happen immediately before the component is torn down. I'd love to solve this somehow can cause components that are not part of the "to" to get their route frozen so that it doesn't change and then then get removed.
I'm not sure if we can solve this problem though (or even if we should).

moving to Notion
https://www.notion.so/Editable-Params-2e359e1153b24400b86b48315edd9fe6


add docs about .execute method

i'm starting to study jsreport implementation :)
would like to see some documentation about .execute method

all clear, just i don't understand it at first :)


Implement option to specify additional containers

This is required to deploy sidecar containers, e.g. logging agents/ forwarders/ firelens

Hey this looks really interesting and I'm trying to use it. How do I define the additionalContainers in serverless.yml?
This is what I got:

Seems a great enhancement to me as well.
@eddmann Could you please take a look on this?

@ferencbeutel4711 can you share working snippet of serverless.yaml ? I'm struggling for a while to get it working to pass logs to firelens

Hey, thanks for the PR! 😄, this looks like a great idea, will look to be adding it in the next release.

Hey, thanks for the PR! 😄, this looks like a great idea, will look to be adding it in the next release.

Awesome! Looking forward to using this new feature.

Thank you for the PR! 😄

Have just released this addition in the latest release, thanks again for the PR 😄 https://github.com/eddmann/serverless-fargate/releases/tag/0.0.12

Thanks for a quick release!


support tolerations and node Selector

Change Overview

This Pull Request add the support for tolerations and nodeSelector of the kanister helm chart as per issue 2707 request. I added the default empty values in the values.yaml file and added the logic for handling them in the deployment helm template.
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[x] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes: 2707

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

@fabiomarinetti can you please PR description and test plan in PR.

@viveksinghggits I added a short description in the PR. What about helm chart test? I don't see where it is covered.

I think we should add something here https://github.com/kanisterio/kanister/blob/master/pkg/testing/helm/helm_test.go
Basically we should be able to install (or dry-run) the local helm chart by setting taints and tolerations helm values and then verify that the generated/rendered deployment template has  proper fields set.
Let me know if you need some help doing this.

Hi @viveksinghggits, I took a look into the tests, I would like to launch helm install with --dry-run, anyway even though I understand how to pass this to the helmApp I don't get how/if it is used and what it is expected to return by the install function.
In fact in the helm/client.go I don't see any mention to dry-run param.
I am not very confident with go so it is probable I miss something.

Yeah, we would need to improve our helm client code as well to support --dry-run flag. we can either do that as part of this PR or another PR as well. And then we can incorporate that change in this PR.
I will discuss this in tomorrow's community call.

@fabiomarinetti in the meanwhile can you please provide a manual test plan while we're working on improving our test tools #2796


Polish the language in docstrings and README

I didn't copy the polished docstrings over to the README; let's get them to the point where we are both happy with them first, and then I can copy the result to the README.

I also note the version is 0.1.0. Should we jump straight to 1.0.0? You should use 0.1 only if you anticipate breaking changes to the API in the near future.

Yeah I also think setting the version as 1.0.0 is better.


For select filters, based on one filter selection, set other filters with corresponding values

Based on one filter selection, I am trying to set the value of other filters.
As per the doc provided below, the afterFilter function provides us new table dataset from newResult .
https://www.npmjs.com/package/react-bootstrap-table2-filter
While trying to set the corresponding filter values, I am getting stuck with below error.
Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
Hence, please help to set corresponding values for rest of the select filters.
This was mentioned in the issue #1097 and #1441
Appreciate your help.

any updates on this?? got the same error but with date filter


Meteor versions

Will this work/install with Meteor 1.1?

Hi @aadamsx, the current release wasn't published in a way that is compatible with meteor 1.1.
You can try adding the source code to your project manually though.


fix(test): fixing parallel rebuild test

Fixing test containers to run each on its own core.

bors merge


#4 move dependency installation to Docker image build-time

https://github.com/dadwalakshay/the-django-boilerplate/issues/4

Hi @dadwalakshay,
I have pushed the changes now didn't save correctly before pushing previously :)
Let me know if anything else needed.

Thanks for contributing, approved your PR.


Deprecated modifier/keyword/annotation revisited

I think this has been discussed before, but I couldn't find an issue when searching.
Proposition

An "official" part-of-the-language way of marking deprecated methods, etc., and where applicable their replacement

def deprecated foo(x, y, z) => bar(x, y, z) - or something

Motivation

I don't think I'm alone in regex-replacing renamed methods etc. - and that is a less than safe practise, but when the alternative is recompile, edit a line, recompile... temptation wins ;-)
Would therefore be super-helpful for refactorization tools

use compiler to get all locations in code which are deprecated uses
automatically replace with new name where possible (simple renamings)
otherwise: add comment with easily distinctly grep'able message where not automatically possible, making grep'ing a more straight forward job - hints about what to do / change are available at each specific edit spot.

I would rather use flags, so it does not interfere with the language:
@[Deprecated(new_name: bar)]
def foo(x, y, z)
end

Yes, however, I think now in alpha, and during beta, stage - having such a tool could be very beneficial for also the core developers. It might make reasoning about possible API changers (and even language constructs) "more honest", since it can be easy to unconsciously resist otherwise very good changes, without basis in merit, but rather in feeling of burden of changing a lot of code (for everyone) (it's good to consider how our wetware process things, just like the hardware we execute algos on :-) ). Just a thought.

I'm all in for introducing a @[Deprecated] annotation, but... what should happen? Just annotate the documentation? Or shall the compiler spit out warnings when a deprecated method/accessor/type is accessed —keeping in mind we don't like warnings, but theae warnibgs can only be avoided for a limited time.
I'd personnally like the annotation to merely accept a message, for example @[Deprecated("foo is deprecated in favor to bar and will be removed in v2.0.0")].

def foo
  {{ puts "Warning: this method is deprecated, use something else" }}
end

We've used this technique in the past with success. I don't think it's worth adding new features/syntax for this (you'll get the error every time you compile your program)

@asterite this technique is sufficient perhaps for cli related rapid development, in the long run tho' having specific annotation would enhance docs and imo provide more predictable path of sunsetting obsolete API-s.

If the documentation states deprecated then I won't even try to use it. Without the annotation, I must duplicate the message (docs + warning), or find out when trying out the method that it's actually deprecated. Either ain't nice.

Also, on a side note, as @ysbaddaden said earlier: there's only so long we can put off having warnings in the compiler. The "errors or nothing" mentality is not inherently the most helpful path to help a coder getting the job done. But having to request them specifically could be a good thing (of course I always go with -Wall).


Compile error in test_polymorphic

Hi,
I met an error when compiling the test_polymorphic.
I used clang++ on Mac OSX as shown below:

OS: Mac OS X El-Capitan
Compiler: Apple LLVM version 8.0.0 (clang-800.0.38)
Target: x86_64-apple-darwin15.6.0
Thread model: posix

The corresponding error message is as follows:
${BUILD_DIR}/include/cereal/types/memory.hpp:304:15: error: destructor called on
     non-final 'PolyDerivedLA' that has virtual functions but non-virtual destructor [-Werror,-Wdelete-non-virtual-dtor]
              t->~T();
              ^

Could you fix it?

Should be fixed on develop, let me know if it persists.


Automatically call eachrow for DataFrames

an alternative to #107
close #107

Codecov Report

Merging #109 into master will increase coverage by 0.11%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
+ Coverage   88.74%   88.86%   +0.11%
==========================================
  Files          17       18       +1
  Lines        1111     1078      -33
==========================================
- Hits          986      958      -28
+ Misses        125      120       -5

Impacted Files
Coverage Δ

src/interop/dataframes.jl
0% <0%> (ø)

src/core.jl
71.71% <0%> (-2.8%)
:arrow_down:

src/processes.jl
90.78% <100%> (-0.71%)
:arrow_down:

src/Transducers.jl
100% <100%> (ø)
:arrow_up:

src/show.jl
94.87% <0%> (-0.05%)
:arrow_down:

src/library.jl
93.5% <0%> (-0.02%)
:arrow_down:

src/dreduce.jl
100% <0%> (ø)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


⚠ Processors has degraded performance

In db7038a, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 83 ms

Resolved: Processors performance has improved in f7c9838.


[1/2] Enable  keyword  arguments for liger functional

Summary

This PR is the first step to enable the keyword arguments of liger functional #368.

Warp the Liger Operator Functions (torch.autograd.Function) with an extra layer that can take key word arguments.
For each of the liger functions, updating its unit test function test_{operator_name}.py::test_correctness_functional to reflect that keyword args can be accepted.
Next step is do apply the new op functionals in transformers/monkey_patch.py

Testing Done

Hardware Type:  A10G
[x] run make test to ensure correctness
[x] run make checkstyle to ensure code style
[x] run make test-convergence to ensure convergence

@ByronHsu I would like to split the functional revamp into two PRs. This is the first one that simply defines the kwarg functions, as well as the unit test. The next PR will try to apply these functions to monkey patch the transformers.

It looks good!

Can you create a branch in the main repo and open a new PR, so you can run CI?
We don't have to change monkey patch file because only the new cross entropy relies on functional CE and i have already fixed it.

Close this PR, pivot for #400 that is created in the main repo to run the tests.


Rouge-L in python interface?

Hi Daniel,
Kudos to the wonderful pacakge! I wonder how to use Rouge-L under the python interface, i.e. the example you shown in the tutorial. Thanks!

Hi Yanjun,
There are two versions of ROUGE, one which is a wrapper around the original Perl implementation and one which is written (by me) in Python.
For the Perl version:
from sacrerouge.metrics import Rouge
metric = Rouge(compute_rouge_l=True)
results = metric.score("The summary to score", ["The list of references"])

There are different methods for scoring depending on whether you have multiple summaries, etc. The information is here.
The Python version is basically identical, except there's a different class you use:
from sacrerouge.metrics import PythonRouge
metric = PythonRouge(compute_rouge_l=True)

It has the same scoring functions as the Perl version.
Hope this helps!


Fix bad title for our dispose method in our documentation

I made a small mistake when I added dispose method...

These still show up with Hugo in TOC, so we'll see again then :)


Suggestions on rebooking

Great project! Trying it now!
Just one advice for a new feature. If there is an existing appointment and some available slots, maybe it can compare the date and only book if a sooner time slot is available. So if I let my program run background and it won't book several times and choose a later time if the earlier ones are taken by others.
And just curious how do you figure out all those API calls since they are not public. Do you just play around the DPS website and record all those APIs from browser develop tools?
Thanks!

Thanks for explaining that for me! The case I am thinking is like this which I am not sure whether will happen. There are 3 available slots in user desired time, naming them 1, 2, 3. And I make the program run for a while so it will query the server several times.
At first time it will book the slot 1. Then at second time the slot 2 is booked by others, but the program notices slot 3 is still available so it cancels slot 1 and book slot 3. Finally at third time the slot 1 is also taken by others and the program won't do anything. So in that case the program will book the last available time slot if there is some others competing with us.
But I think most users would like to book as soon as possible in their desired time window. I don't know whether that race condition will happen. Just some thoughts.

There is also a case if you set cancelIfExist is true and you are using repl.it free plan with monitor services like cronjob and uptimerobot. The monitor service will request to repl.it and make the bot "restart" and start searching for new appointment again. It will cancel the existing appointment and go for the newer one it found based on the citeria.
The fix:

When the application done, delete the repl in repl.it and delete that entry on monitor services.
Set cancelIfExist to false

I see, that make sense. And btw, your application helps me book a close time slot. Thanks sincerely!

no problem, im glad you find the app useful :)


Update AGP to 8.3.0-beta01

This will require the installation of the Android Studio Iguana Beta build

Does that mean I can't update through the Android Studio UI flow, and have to manually download?

Yes. You can start the update flow and it'll send you to the site.
The good news is that the automatic update flow should work (it's only supposed to force a new install when upgrading from one release channel (canary/beta/stable) to another) and the Beta channel doesn't update that often.

What is the goal of this change? To get something more stable?

What is the goal of this change? To get something more stable?

To stay up to date with the latest bug fixes and security updates for a pre-release of a dependency (the dependency being AGP).
The current committed version of AGP is incompatible with currently available builds of Android Studio. The beta release of AGP that we are upgrading to is compatible with the current beta build of Android Studio Iguana.

Reminder that we made the decision to go to the Canary version of AGP last year to take advantage of bug fixes and new features that are used in our Gradle plugin.


Code changes and documentation for end-to-end demo

This PR has everything that was needed to get the DTS prototype to successfully demonstrate a JGI Data Portal -> KBase file transfer, including the generation and transmittal of a manifest.
In particular:

error handling and logging were greatly improved in order to debug lots of configuration and permissions issues
materials for a static documentation website now live in the docs/ folder, and a GitHub Action auto-publishes docs for merged PRs
DTS now performs Globus re-authentication flows where needed to access files on Guest Collections, per Globus's REST API recommendations
a Dockerfile and deployment instructions were created that allow DTS to be deployed within Spin (and presumably other Docker/Kubernetes environments)

Closes #31

Sorry about the large PR, AJ. :-) A lot of it is documentation, though, so maybe that's positive? :-)


What do you mean with NoSQL?

Hi,
Do you understand graph databases as NoSQL? Do you have the project to write something to pump data into a graph database?
Cheers

We mean ElasticSearch as NoSQL database in our case :-)


Tests failures

The tests are currently failing to pass for me, showing tons of messages similar to the one bellow:
error: line 1: Capability cannot appear before the memory model instruction
  OpCapability Shader

The full output is very large, so I've attached it here: test-log.txt
I can confirm that in tag vulkan-sdk-1.3.268.0 the tests are passing fine, but in tag vulkan-sdk-1.3.275.0 they fail with the above output.
A git bisect shows the offending commit as being ec42cb1c4150f8faa814957ddf9e115242d2a054.
System information:

OS: Arch Linux
CMake: 3.29.2
Compiler: gcc 13.2.1
Python: 3.12.3

Thank you for the reply.
No, it still does not build using the current git master, but I could find what is causing this.
The issue happens when building with GCC 13. When building with GCC 14, the tests passes fine. So, maybe some compiler bug that was fixed in GCC 14?
After I opened this issue here, the compiler in Arch Linux was updated to GCC 14, and the tests passes fine using it. GCC 13 is still available in the repositories, so I can check with both compilers. Using GCC 13 the issue happens, and with GCC 14 everything is fine.
Your CI configuration uses Ubuntu 20.04 and 22.04, which defaults to GCC 9 and GCC 11 respectively. I suspect that you cannot reproduce this issue due to not be using GCC 13.
Since this does not affect me anymore as it's currently working fine with the latest GCC 14 in Arch Linux, I will close this issue.


How can I use 2 Build hat boards on one GPIO?

How to connect 2 Build Hat boards?
How work woth python libs and ports?
How connect another boards and devices to 40-pin GPIO?
It is possible to use one power for 2 Build Hat boards?

You can not
How to use Python is outside the scope of this project
I couldn't find much with a quick search, leading me to believe that just connecting them over Ethernet would be faster
No

It is possible to connect 5 devices through Raspberry?


Consider changing font

Historically this has been reported as duplicate / double monospace font at the time of writing 13 times, this issue is not about that, this is about actually removing it as Normalize should no longer require it:
Browsers using Blink, Gecko, and WebKit reduce the size of monospace. Therefore, the monospace,monospace fix applies to Android ≤ 6, Chrome ≤ 49, Firefox ≤ 45, iOS ≤ 9, Opera 15-35, and Safari 5-9. The fix does not work for Safari ≤ 4.
Browsers using Presto and Trident treat monospace normally. Therefore, the monospace,monospace fix is not required for Edge 12-13, Internet Explorer 8-11, Opera ≤ 12.15, and Windows Phone ≤ 8.1.
Based on browser usage here: https://caniuse.com/usage-table:
Android ≤ 6: 2.01% (This is based on ≤ 5, there's no data on v6 /shrug)
Chrome ≤ 49: 1.41%
Firefox ≤ 45: 0.43%
iOS ≤ 9: 0.09%
Opera 15-35: 0.27%
Safari 5-9: 0.23%
Browser usage that is affected by this issue is pretty low, what would the threshold be for this to be considered to no longer be required by Noormalize?

thanks for the info! closing since this repo is no longer being actively maintained


Changelogging takes too much time and effort

From the today's discussion: https://colabti.org/irclogger/irclogger_log/perl6-dev?date=2019-06-27#l45
Basically, there are up to 300-400 commits to review even if rakudo is released regularly every month. Going through all of them and figuring out what's worth mentioning is a hard and time-consuming task. Here's how I did it:

During the month the bot and I would try to encourage devs to log their changes on https://github.com/rakudo/rakudo/wiki/ChangeLog-Draft
A few days before the release I'd get the list of remaining commits from the bot, and remove things that are clearly not changelog worthy, such as:

changes to the comments, tests or docs
reverted commits
most of the merge commits
most of the nqp bumps, although these are usually reviewed to see if there are any important NQP changes

Then I'd sort all of the commits into the categories
And finally I'd do a few passes over all of the commits and reword the commit messages so that they're more or less consistent

This process takes a few hours for me and honestly I'm unable to do it in one go. I've also noticed that it is also not easy for the MoarVM team, up to delaying the release sometimes because of the sheer amount of work required.
I'm interested in hearing possible solutions to the problem. That being said, I think the proposals shouldn't just shift the work on others, so in my opinion saying that any dev who does a change should then be forced to do something. Also, we should keep in mind that the changelog is something that the end user will likely see, so their interests should be taken into account.

meta label because I'm interested in implementing this change across all compiler projects. That said, if somebody creates a compiler and decides to do something else, they're free to do so.

Just to have here what I said on IRC.
Often noteworthy commits are coming int through pull requests. I would even put it this way: any significant change must be incorporated through a PR. For this reason it could make sense to include necessary data into PR comments. For example, it may look like this (from perspective of a PR template):
# Description

<!-- Provide details of your PR here -->

# META
<!-- Specify ChangeLog category; one of: Feature, Deprecation, Security, Fix, etc. -->
* ChangeLog: Fix
<!-- Reference associated GitHub issue -->
* Issue: perl6/problem-solving#53
<!-- Is this change worth mentioning in Release Info? -->
* Release Info: no

This could simplify collection of ChangeLog entries. That'd be easier for a submitter too and would encourage developers to participate in ChangeLog forming more actively.

I like the idea of using PR's mainly.  But that by itself will make things harder, as it will fill the git log output with many merge commits.  And worse, if a PR runs over a length of time, and consists of multiple commits, it becomes really hard from a git log point of view to see which commit belonged to which PR.  Or am I missing some handy tool / trick that would allow to only see merge commits and the commits that were merged grouped together ?

A PR is represented by a single commit. For example, one of mines: @969aa440. The only related problem is that what is included into git log is:
commit 969aa440c5e2ce2686b807af2ba3e5f43d845358
Merge: c5171d431 b93201f5a
Author: Vadim Belman<EMAIL_ADDRESS>Date:   Thu May 30 20:42:58 2019 -0400

    Merge pull request #2852 from vrurg/add_version_6e

    Add revision 6.e and improve multi-revision support

For this reason building a ChangeLog from PRs would involve requesting the first comment of a PR to pull out the meta information if any provided. But still it's simpler and easier than manual grepping.
Another advantage of PRs is that they could hide as many commits behind them as needed without the hassle of checking them all manually. If a commit is considered worth of individual inclusion into the ChangeLog it could be marked with the special meta. Or referenced manually on the Wiki.

@kawaii is currently working on this.


Programming Paradigms Course

I suggest Stanford Programming Paradigms course

@MohammedAttya2 thanks for the suggestion!
I think that we already are covering important paradigms (OOP, FP and RP), and those courses are MOOC, this is not.