Misleading concepts about sanitize in template syntax

In the Content security part of Template Syntax chapter, there is the content:

"{{evilTitle}}" is the interpolated evil title.

"" is the property bound evil title.

It says that, Angular will generate warnings for these two lines. However, it actually just generate warning for the second line, nothing for the first line, an example is here in http://embed.plnkr.co/kS1vNt2hT7KfOtlKT2Qu/ . (Technically that's not wrong, but misleading enough)
And for the first line, there's actually nothing about sanitize, it's just because Angular does not use a string-based template, the structure and data have been separated all the time. So the interpolation environment is not HTML-awareness, using HTML there will be same as using HTML in an iOS Label, it's the natural result to show the text as-is, without any pre-processing.
Since the interpolation context is not HTML-aware at design level (Angular is platform-agnostic), it's not accurate to say it sanitize the HTML in this condition.

@trotyl , my head started spinning, whilst trying to understand this. May I ask: which action do you suggest?

@lazaridis-com At least remove:

Angular generates warnings for these two lines as it sanitizes them

as Angular won't generate warning for one of them, it's a fact, not an opinion.


Soft Lock - Sector X Expert

There appears to be an issue where taking the warp in Sector X in expert will cause a soft lock. Soft lock has occurred in two playthroughs back to back.
Version: Beta-45-Hot-Fix
OS: Windows 10 64bit
Emulator: BizHawk, Mupen64Plus core

Should be fixed now in latest release.


Images are not reloaded when changed on disk

![100%](/path/to/image.png)

The image is not readed as image.png is changed on disk. Even if I modify the line above the image preview is not updated.

I'd expect to be able to re-load the images by typing Control-R in Marp but that's not implemented either.

We're making a clean sweep of piled up issues. This issue is duplicated of #56.


Investigate ZooKeeperRegistrationTest.testConnectionRecovery failure

https://travis-ci.org/line/armeria/builds/308873600
ZooKeeperRegistrationTest.testConnectionRecovery: FAILURE
---------------------------------------------------------
09:45:26.470 [Test worker-EventThread] ERROR org.apache.zookeeper.ClientCnxn - Caught unexpected throwable
com.linecorp.armeria.common.zookeeper.ZooKeeperException: Failed to notify ZooKeeper listener
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector.notifyChange(ZooKeeperConnector.java:192)
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector.access$600(ZooKeeperConnector.java:49)
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector$ZkWatcher.processResult(ZooKeeperConnector.java:272)
	at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:555)
	at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:506)
Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /testEndPoints
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:102)
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
	at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1535)
	at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1563)
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector.notifyChange(ZooKeeperConnector.java:160)
	... 4 common frames omitted
09:45:28.182 [Test worker-SendThread(<IP_ADDRESS>:33675)] WARN  org.apache.zookeeper.ClientCnxn - Unable to reconnect to ZooKeeper service, session 0x100029b12de0009 has expired
09:45:38.627 [Test worker-SendThread(<IP_ADDRESS>:33675)] WARN  org.apache.zookeeper.ClientCnxn - Client session timed out, have not heard from server in 6666ms for sessionid 0x100029b12de000a
09:45:38.627 [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:0] WARN  o.a.zookeeper.server.NIOServerCnxn - Unable to read additional data from client sessionid 0x100029b12de000a, likely client has closed socket
09:45:38.628 [Test worker-SendThread(<IP_ADDRESS>:33675)] WARN  org.apache.zookeeper.ClientCnxn - Client session timed out, have not heard from server in 6667ms for sessionid 0x100029b12de000b
09:45:38.628 [Test worker-SendThread(<IP_ADDRESS>:33675)] WARN  org.apache.zookeeper.ClientCnxn - Client session timed out, have not heard from server in 6668ms for sessionid 0x100029b12de000c
09:45:38.628 [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:0] WARN  o.a.zookeeper.server.NIOServerCnxn - Unable to read additional data from client sessionid 0x100029b12de000c, likely client has closed socket
09:45:38.629 [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:0] WARN  o.a.zookeeper.server.NIOServerCnxn - Unable to read additional data from client sessionid 0x100029b12de000b, likely client has closed socket
09:45:39.914 [SyncThread:0] WARN  o.a.z.server.persistence.FileTxnLog - fsync-ing the write ahead log in SyncThread:0 took 7003ms which will adversely effect operation latency. See the ZooKeeper troubleshooting guide
com.linecorp.armeria.server.zookeeper.ZooKeeperRegistrationTest > testConnectionRecovery FAILED
    org.junit.runners.model.TestTimedOutException: test timed out after 10000 milliseconds
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
        at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
        at javascalautils.concurrent.FutureImpl.ready(FutureImpl.java:244)
        at javascalautils.concurrent.FutureImpl.result(FutureImpl.java:228)
        at javascalautils.concurrent.Future.result(Future.java:395)
        at zookeeperjunit.CloseableZooKeeper.blockingConnect(CloseableZooKeeper.java:82)
        at zookeeperjunit.ZKInstanceImpl.lambda$null$18(ZKInstanceImpl.java:141)
        at zookeeperjunit.ZKInstanceImpl$$Lambda$19/2079812548.apply(Unknown Source)
        at javascalautils.Try.apply(Try.java:140)
        at javascalautils.TryCompanion.Try(TryCompanion.java:105)
        at zookeeperjunit.ZKInstanceImpl.lambda$connect$19(ZKInstanceImpl.java:141)
        at zookeeperjunit.ZKInstanceImpl$$Lambda$18/2027001369.apply(Unknown Source)
        at javascalautils.Some.lambda$map$23(Some.java:97)
        at javascalautils.Some$$Lambda$16/734860802.apply(Unknown Source)
        at javascalautils.Some.flatMap(Some.java:108)
        at javascalautils.Some.map(Some.java:97)
        at zookeeperjunit.ZKInstanceImpl.connect(ZKInstanceImpl.java:139)
        at zookeeperjunit.ZooKeeperAssert.connection(ZooKeeperAssert.java:64)
        at zookeeperjunit.ZooKeeperAssert.assertExists(ZooKeeperAssert.java:37)
        at com.linecorp.armeria.server.zookeeper.ZooKeeperRegistrationTest.lambda$testServerNodeCreateAndDelete$1(ZooKeeperRegistrationTest.java:88)
        at com.linecorp.armeria.server.zookeeper.ZooKeeperRegistrationTest$$Lambda$148/248109204.accept(Unknown Source)
        at java.lang.Iterable.forEach(Iterable.java:75)
        at com.linecorp.armeria.server.zookeeper.ZooKeeperRegistrationTest.testConnectionRecovery(ZooKeeperRegistrationTest.java:174)

ZooKeeperRegistrationTest.testConnectionRecovery: FAILURE
---------------------------------------------------------
11:38:19.044 [Test worker-EventThread] ERROR org.apache.zookeeper.ClientCnxn - Caught unexpected throwable
com.linecorp.armeria.common.zookeeper.ZooKeeperException: Failed to retrieve the data from: /testEndPoints/<IP_ADDRESS>_4004
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector.lambda$notifyChange$0(ZooKeeperConnector.java:180)
	at java.util.ArrayList.forEach(ArrayList.java:1257)
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector.notifyChange(ZooKeeperConnector.java:172)
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector.access$600(ZooKeeperConnector.java:49)
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector$ZkWatcher.processResult(ZooKeeperConnector.java:272)
	at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:555)
	at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:506)
Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /testEndPoints/<IP_ADDRESS>_4004
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:102)
	at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
	at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1215)
	at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1244)
	at com.linecorp.armeria.common.zookeeper.ZooKeeperConnector.lambda$notifyChange$0(ZooKeeperConnector.java:175)
	... 6 common frames omitted
11:38:19.044 [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:0] WARN  o.a.zookeeper.server.NIOServerCnxn - Unable to read additional data from client sessionid 0x1000012f578000b, likely client has closed socket
11:38:19.310 [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:0] WARN  o.a.zookeeper.server.NIOServerCnxn - Unable to read additional data from client sessionid 0x1000012f5780009, likely client has closed socket
com.linecorp.armeria.server.zookeeper.ZooKeeperRegistrationTest > testConnectionRecovery FAILED
    java.util.concurrent.CompletionException: java.net.BindException: Address already in use: bind
        at java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:375)
        at java.util.concurrent.CompletableFuture.join(CompletableFuture.java:1934)
        at com.linecorp.armeria.server.zookeeper.ZooKeeperRegistrationTest.startServers(ZooKeeperRegistrationTest.java:70)
        Caused by:
        java.net.BindException: Address already in use: bind

Superceded by #882


Feature request: ability to see active status and wake devices directly from "Active DHCP Leases" devices list (via WOL / Wake-on-LAN)

Testing with the latest version of OpenWRT 23.05.5 r24106-10cc5fcd00 / LuCI openwrt-23.05 branch git-24.264.56413-c7a3562, I find myself missing a very nice convenience feature found in FreshTomato's web UI: the ability to directly wake devices from the overview status devices list.
In Tomato, it looks like this:

OpenWRT's Luci interface also has a devices listing table on the homepage (admin/status/overview), under the Active DHCP Leases and Active DHCPv6 Leases sections, with a very convenient "Set Static" button:

…so I'm thinking that, from a UX perspective, it could make a lot of sense to also have a convenience "Wake" button (with explanatory tooltip with something like title="Click to wake up this device, if its network interface supports wake-on-LAN." maybe) under an extra "WOL" or "Wake-on-LAN" column
I suspect this might be a technically simpler and more elegant way to solve #4188. It would also be more convenient for users, because there would be less clicks involved, it would be accessible in one click directly from the router's home page :)

Good idea. There's luci-app-wol. That could be integrated into these device lists. Is this something you might want to undertake?

There's the small matter of penalty, however: the etherewake tool requires 5kb (at least on my arm platform).

@systemcrash: Have you progressed on it?

Is this something you might want to undertake?

I wish, but I do not have the necessary programming (and networks) knowledge, so do not block on me; I am merely making the enhancement/UX suggestion, and am grateful to whoever may implement this :)

One potential problem I find with this design is that once a device has gone to sleep, it disappears from the table because it no longer requests a lease. So... it kind of defeats the point. Thee work-around is to set very long lease times. A more robust WOL tool which caches all encountered MACs would be the way to do it. And we have one: luci-app-wol.

Personally speaking, I think the default 24-hours lease time already makes this better than nothing, especially for the "waking up family members' computers that they use every day anyway" usecase; and I wouldn't mind telling the router to have multi-days lease times instead of 24-hours (especially if there was a button to drop/reset the lease, but I don't know if that's a possibility)


Refactor  HTMLCopyAndPaste tests

Description
Refactored HTMLCopyAndPaste tests.
Closes #6164

@potatowagon  i dont know if this sorts out the issue?

I'm not sure what the goal of https://github.com/facebook/lexical/issues/6164 is because there isn't enough context, so I don't know if this solves it. It doesn't really seem like a net improvement (nor does it make things worse) to move things around in this way.

I thought so too...


Add method to list available ports

Adds method to list ports with interchange ports + interchange ports --verbose.

Here's what the output looks like for both


How use it without Express (native Node.js v9.4.0)

How use it without Express (native Node.js v9.4.0)?

Hi @pu3antasyah you'll just need to pass in the req and res objects and then continue your code within the callback. For example:
var compression = require('compression')
var http = require('http')

http.createServer(app).listen(3000)

function app (req, res) {
  compression(req, res, function (err) {
    // handle err, maybe
    // put your normal server code here
  })
}

I hope this helps!


Possible solution of Too many requests?

Hello,
is someone getting "Too Many Requests" in Firefox too? I can browse many posts in browser and still works. Is there some hidden feature in web UI maybe? I have seen some special requests in Firefox:
POST https://graph.instagram.com/logging_client_events
POST https://www.instagram.com/logging/falco
But I'm no programmer, I don't unterstand that JS code. Could maybe someone of you check, when the FF sends these requests and if these requests maybe inform IG server about real client? Maybe you could send these requests too to fake real client and IG will then thing the instaloader is normal Firefox?
Thank you for your work!
Regards.

Hmmm, the problem 429 Too Many Requests is in iphone requests. If I replace orig_url = self._iphone_struct['image_versions2']['candidates'][0]['url'] in structures.py on line 243 with orig_url = self._full_metadata['display_url'] I can now download images.
Now it's failing 429 on sidecar.


[dev] PIP 27: Add checklist in github pull request template

Motivation
With the increase of contributions, more and more features are
added pretty quickly. However these features are not documented.
And there is no checklist for contributors to check when
contributing a feature.
Changes
This PIP is proposing to improve the github pull request template
by adding a checklist for contributors to check. It also help
improve the review process.

It seems like adding tests for a new feature is required but documentation is optional. Is it correct?
If yes, can you explain the intention? Reviewers need to know what cases they can accept the PR without documentation.

Is it correct? If yes, can you explain the intention?

yes that's correct. because not every code change requires documentation. e.g. most of code changes don't require documentation, e.g. bug fixes, and tasks for a large features. If a change is changing any item under "Does this pull request potentially affect one of the following parts", this change is most likely required to have related documentation change.

because not every code change requires documentation. Most of code changes don't require documentation, e.g. bug fixes, and tasks for a large features.

If a change is changing any item under "Does this pull request potentially affect one of the following parts", this change is most likely required to have related documentation change.

Thanks for the clarification. I understand the policy and I'm fine with it. However, the questions in Documentation section might be confusing a little if that is the policy.

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

These questions imply that you can say "yes, but it's not documented". There would be cases we accept as exceptions so it's a valid answer, but I'm not sure we should show such a option.

However, the questions in Documentation section might be confusing a little if that is the policy.

The purpose of this is to improve PR for both contributors and reviewers. It doesn’t target at setting down an enforcement. Reviewers can use that as a guide to comment.

These questions imply that you can say "yes, but it's not documented". There would be cases we accept as exceptions so it's a valid answer, but I'm not sure we should show such a option.

In this, the contributor can explain why it is not documented. The reviewer can ask if the contributor doesn’t say in the description. Again, the purpose of this template is aiming at improving review process rather than setting a fixed set of options for contributors and reviewers. Hope that make sense.

@maskit I updated the template to address your comments

add a visible checkbox for passing CI checks
add more instructions in the documentation section for "not applicable" and "not documented"

Can you take a look again and let me know what is your thoughts?


Mine does not have a "Frequency Sync" button ?

I wanted to use this to sync the frequencies of the two devices (a ham rig and my SDR receiver).
In the screenshots it shows a "Frequency Sync" button. Mine does not display that. I have version 2.1.
Thanks,
Charlie KB8CR

Hey,
Which Operating System are you running? wich version?

I was using it on Raspberry Pi with Raspbian Buster
Charlie
From: Simone Marzona<EMAIL_ADDRESS>Reply-To: Marzona/rig-remote<EMAIL_ADDRESS>Date: Monday, July 13, 2020 at 4:56 PM
To: Marzona/rig-remote<EMAIL_ADDRESS>Cc: Charlie Rubenstein<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Marzona/rig-remote] Mine does not have a "Frequency Sync" button ? (#102)
Hey,
Which Operating System are you running? wich version?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


chore: promote react-spring to version 0.0.14

this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

react-spring
Changes in version 0.0.14
Chores

release 0.0.14 (jenkins-x-bot)
add variables (jenkins-x-bot)

Other Changes
These commits did not use Conventional Commits formatted messages:

debug wolfi (iMckify)

[jx-info] Hi, we've detected that the pipelines in this repository are using a syntax that will soon be deprecated.
We'll continue to update you through PRs as we progress. Please check #8589 for further information.

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

Needs approval from an approver in each of these files:

OWNERS

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


update file versions to 220

files of version 210 do not exist on the ftp server

thank you very much!


Deno support

Hey,
I saw in issue #129 @brandonkal ported runtypes to Deno:
https://github.com/brandonkal/runtypes
Could this be upstreamed? The big problem is renaming imports to .ts, not sure if this is feasible. An alternative might be to package a single-file bundle without any imports.
This would also make runtypes work in the browser.

I believe I opened another issue about this.
There were other issues getting the port to work besides changing imports such as ignoring some TypeScript issues.
That needs to be figured out before I'd make a PR here so if you want to speed this along, I would suggest OP make a PR against my fork figuring out why Deno required a few more ts-ignore comments and adding Deno-specific tests.
Because deno requires different imports, it would mean essentially duplicating all files in the repo or maintaining two master branches to maintain Deno + Node compat. For now it makes sense to maintain a separate repo fork as that makes tracking changes simple.

Yes, I can fix the issues properly vs. ignoring them, however, first I'd like to check if changing the imports to use a .ts suffix is even acceptable to the maintainers.

Until TypeScript itself accepts a proposal and merges in support for using that extension ESM imports and all the various bundlers follow suit we have to maintain two implementations. I am sure @pelotom  doesn't want to drop Node support anytime soon. This project is perfect for Deno because it has no node module dependencies. But for the foreseeable future this is where we are at.

Since there are now a couple of repos like Runtypes that I'd like to use, I created
https://stupid-extensions.com
Basically, just prepend to any URL to replace import './foo' in responses with import './foo.ts' (or .js):
This repo basically almost works out of the box, with one single error:
error TS2349: This expression is not callable.
  Type 'never' has no call signatures.

► https://stupid-extensions.com/raw.githubusercontent.com/pelotom/runtypes/master/src/show.ts:65:9

65   throw Error('impossible');

Fixed in PR https://github.com/pelotom/runtypes/pull/138.
Meanwhile importable as
import * as runtypes from 'https://stupid-extensions.com/raw.githubusercontent.com/jakajancar/runtypes/master/src/index.ts'

@jeremyBanks @jakajancar @yuhr I would like to see Deno runtime support merged in here.
I just updated my Deno fork for v6.0.0. You can see the changes required here: https://github.com/brandonkal/runtypes/commits/deno-v6
Much cleaner than what was required before. First of course is using extensions for imports and in the second commit on the branch you can see all the other changes required. Deno is isolatedModules by default and that was the bulk of it to get it to compile.
Also note that I was able to get most tests to pass when executed in Deno this time around with my jest-compat lib (an extension of expect). PRs to make https://x.kite.run/lib/testutils.ts more complete here would be appreciated. There were a few tests I disabled which will probably work with a toMatchObject method for Deno.

Great work! So the barrier against merging it here is due to incompatibility of the testing framework?

Yes, jest is tied to node so it doesn't run in the Deno runtime. I'm not aware of a testing framework designed for both.

For the meantime, couldn't two testing frameworks be used separately?

It may be worth considering to refactor the tests to use Deno.test. You can then use dnt to run the test suite on Node, too. That way, you have a single code base, double test coverage (one per platform) and massively improve testing speed while you're developing for Deno.

Until then, we can actually directly use the main library (not a fork) via https://esm.sh like so:
import rt from "https://esm.sh/runtypes"; // don't forget to add a version
const {
  Array,
  Boolean,
  Literal,
  Number,
  Record,
  String,
  Tuple,
  Union,
} = rt;

const Vector = Tuple(Number, Number, Number);

console.log(Vector.validate('not a vector')))

I ported this library some time ago: https://github.com/sant123/runtypes
All tests are passing and is ready to use. I'd highly appreciate your feedback.

Amazing! Thank you, I'll use that for now.
In the long run, it would make a lot sense to unify the code bases again so that they do not diverge. If a bug is discovered and fixed here, you'll always need to sync up the repos manually. That is far from ideal. Having independent code prevents me from transferring the trust I have in the Node version to the Deno version.
Do you think you could look into dnt or deno2node and PR against this original project if you manage to produce the same build output?

That's something I could definitely do, however just want to make sure the maintainers of this repository are interested in that. Also want to highly the port doesn't support legacy decorators, this is intended since them will be deprecated when decorators proposal gets released and don't want to have code broken for the legacy stuff. So I prefer to support them when the are done.

From my experience of using Deno for years, it seems to have become mature for Deno to work with npm modules, as described in the official documentation. Back in the origin of Deno it was aimed to put Node.js stuff out of scope, but things changed. Now I feel like it's sufficient to use CDNs or npm: specifier to use this library in Deno.
I understand people might be facing some uncomfortable experience as KnorpelSenf wrote above. But what I'm afraid of is, the versions already published on https://deno.land/x/runtypes is not the same as the ones on https://www.npmjs.com/package/runtypes?activeTab=versions, and furthermore, I guess the official (npm) versions published prior to some point of time that we would set up Webhooks wouldn't be available on deno.land/x. These inconsistencies could rather cause unexpected experience for existing users. A possible plan is to announce a “turning point” of the version history, e.g. from v7 we're going to be a Deno-first library and previous versions are not officially supported on Deno, ...but actually I'm in doubt if it's really worth it.
That said, I'd love to migrate the codebase to Deno-first and transpiling for Node.js using dnt. Publishing to registries is just optional (though I think nest.land is okay for us).

Being the author of a number of Deno-first libs, I can only encourage you to do the transition. Everything is just so much faster and simpler and easier and nicer.
What's your reason to avoid deno.land/x?

I'm curious if having the inconsistencies I wrote above sounds good to you (and others). Just I haven't heard of libraries that have such history.
Another concern is, I'm not sure if it's possible to freely call the Webhooks endpoint to publish from multiple repositories, as currently it's been used by sant123/runtypes. I couldn't find any helpful documentation about what will happen in this case, but I don't think it's allowed as it would cause catastrophic situation, so probably we need to contact with the support, if we really want to do this.
Someone might suggest publishing under another name that isn't occupied, like deno-runtypes, but I never liked this style of UX ever. Why does it require me to type deno- to specify this Deno-first library published on deno.land in my Deno code? Because the canonical name runtypes is already used by someone. Blah. It's way better not to publish then.

Publish the same version of the library under the same tag for all plattforms. It doesn't matter if many old versions are missing for Deno, it's more important that the more recent version has the same name on GitHub, /x, and npm.
It will be possible to communicate with @sant123 as well as the Deno team and make sure that this repo will contain the official build and that it will be the single source of truth for all plattforms. I'm sure they'll all be cooperative :)

@KnorpelSenf I’m open for this to give ownership for the name in deno.land/x and the project (the fork) itself if is required. Just let me know in how can I help.

Thank you! I guess now it's upon @yuhr to decide how to move forward :)


SEY model from experimental data and LHC rectellipse chamber

Added Two new modules - SEY model based on experimental data. Also the new chamber -rectellipse - it's just the extension of ellipse chamber class -which is general shape for any chamber in LHC.
Example of using that is in /testing/tests_buildup/MB_6.5TeV_UnscrubbedCu/.
The experimental data from R.Cimino of scrubbed and fully scrubbed LHC Copper is also added there.

Merged on dedicated branch.


feature: NoTrailingCommaInSinglelineFixer - Introduction

Currently there is no fixer to enforce no trailing , in a single of short array destruction in one line, nor  a rule for no trailing , in single line of group imports.
Other fixes are; it is now single rule with options and all fixing is done in same matter (no longer a priority case).

Coverage decreased (-0.02%) to 92.894% when pulling 949c26125572a16995360cce27613da32aa07d75 on SpacePossum:main_feature_NoTrailingCommaInSinglelineFixer into b3cc7ef69fd67b9b2c156329a3e820667a0c800a on FriendsOfPHP:master.

Thank you @SpacePossum.

Thanks all reviewers and @julienfalque for merging :D  :dancers:


Checkstyle error in 7.5.1: Must specify at least one of 'file' or nested 'fileset' or 'path'.

Using template from https://github.com/sevntu-checkstyle/checkstyle-samples I tried to check java code with embedded Checkstyle gradle plugin and got an error. See my fork at https://github.com/Prikalel/checkstyle-samples (where I just solved insecure protocol issue and upgrade gradle up to 7.5.1).
Expected Behavior
Checkstyle should work with 7.5.1 version of gradle. Or you should have a section in docs, where the way to pass 'file' or nested 'fileset' or 'path' to checkstyle is specified.
Current Behavior
> Task :checkstyleMain FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':checkstyleMain'.
> A failure occurred while executing org.gradle.api.plugins.quality.internal.CheckstyleAction
   > Must specify at least one of 'file' or nested 'fileset' or 'path'.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
3 actionable tasks: 3 executed

Context

Which version did this stop working with? Which version do you know it works?
It works fine with gradle 7.4.2.
How has this issue affected you? What are you trying to accomplish?
I'm trying to use Checkstyle with the most recent gradle version, but I can not find any resources (or documentation) on that error.

Steps to Reproduce

Clone https://github.com/sevntu-checkstyle/checkstyle-samples and navigate to gradle-project folder.
Now run ./gradlew check, as you see all is fine:

> Task :checkstyleMain
[ant:checkstyle] [ERROR] /home/alex/Загрузки/checkstyle-samples/gradle-project/src/main/resources/messages.properties:1: Файл не заканчивается пустой строкой. [NewlineAtEndOfFile]
[ant:checkstyle] [ERROR] /home/alex/Загрузки/checkstyle-samples/gradle-project/src/main/java/com/github/sevntu/checkstyle/Sample.java:6:17: Method declares to return Boolean and returns null. [ReturnNullInsteadOfBoolean]
Checkstyle rule violations were found. See the report at: file:///home/alex/Загрузки/checkstyle-samples/gradle-project/build/reports/checkstyle/main.html
Checkstyle files with violations: 2
Checkstyle violations by severity: [error:2]

BUILD SUCCESSFUL in 883ms
4 actionable tasks: 4 executed

Upgrade gradle: ./gradlew wrapper --gradle-version 7.5.1
Run the same command again: ./gradlew clean check and now you get the error:

> Task :checkstyleMain FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':checkstyleMain'.
> A failure occurred while executing org.gradle.api.plugins.quality.internal.CheckstyleAction
   > Must specify at least one of 'file' or nested 'fileset' or 'path'.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 523ms
4 actionable tasks: 4 executed

Your Environment
Build scan URL:
https://gradle.com/s/ynitpaqmrntdc

Thanks for the reporting @Prikalel
However I wasn't able to reproduce the issue with STR you provided. Could you make sure that STR are correct?

And I tried it on another Debian 11 machine with fresh java-17 installed using gradle-wrapper and got the same error: https://gradle.com/s/2fxragbaqmst2

@Prikalel I'm tried to reproduce at exactly same environment that you are using. It's behaves correctly.
Are you sure that you don't have any not committed changes in your local repo?

@Prikalel What we would ask you is use the following template with a Gradle GitHub action set up to showcase your problem: https://github.com/gradle/gradle-issue-reproducer

))
Finally, I realized that this issue is a duplicate of https://github.com/checkstyle/checkstyle/issues/12057 (https://github.com/gradle/gradle/issues/21524).
My path of all gradle projects is
/home/alex/Документы/**

So when I moved project folder from /home/alex/Документы/gradle-issue-22073-reproducer to just /home/alex/gradle-issue-22073-reproducer it started to work properly, so I guess I can not reproduce this issue with https://github.com/gradle/gradle-issue-reproducer.


Add Support for DIDCommv3 Coordinate Mediation

Overview
Veramo has already implemented DIDComm v2 Coordinate Mediation. With the recently released DIDComm v3 Specification for Coordinate Mediation, the work already done in this PR will need to be updated.
Solution
Would you be open to contributions to transfer the existing implementation to v3?
Resources

DIDComm v3 Coordinate Mediation Specification
Veramo DIDComm v2 Mediation Issue

We're always open to contributions and would love a PR implementing v3 of this protocol.

Sounds good. Did I need to set up any specific permissions to push my branch up? I am following the contribution guidelines branding off main but am getting a permission denied (403).

@mirceanis thanks for the clarification. The makes sense.


About SAM data

Can you explain the inclusion relationship between cap23k and sam9k in file sharegpt4v_mix665k_cap23k_coco-ap9k_lcs3k_sam9k_div2k.json?
Also, can you also provide a separate copy of SAM data included in file  sharegpt4v_mix665k_cap23k_coco-ap9k_lcs3k_sam9k_div2k.json? Because the SAM data is too large, even for the 000000~000050.tar used in your paper.

Can you explain the inclusion relationship between cap23k and sam9k in file sharegpt4v_mix665k_cap23k_coco-ap9k_lcs3k_sam9k_div2k.json?
Also, can you also provide a separate copy of SAM data included in file sharegpt4v_mix665k_cap23k_coco-ap9k_lcs3k_sam9k_div2k.json? Because the SAM data is too large, even for the 000000~000050.tar used in your paper.

Thanks for your feedback. We have already uploaded sam9k images. You can download it following this doc


[brnahc-2.0][fix](jdbc catalog) Fix ClassLoader Scope in JdbcExecutor Initialization

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


goroutine leak in WIT around SQL package (OSIO#2478)

add missing defer rows.close() (and move another one
after the error checking)
Signed-off-by: Xavier Coulon<EMAIL_ADDRESS>

Ike Plugins (test-keeper)
Thank you @xcoulon for this contribution!

It appears that no tests have been added or updated in this PR.
Automated tests give us confidence in shipping reliable software. Please add some as part of this change.
If you are an admin and you are sure that no test is needed then you can use the command /ok-without-tests as a comment to make the status green.
For more information please head over to official documentation. You can find there how to configure the plugin - for example exclude certain file types so if PR contains only them it won't be checked.

/ok-without-tests

@xcoulon snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1985-1

Codecov Report

Merging #1985 into master will decrease coverage by 0.05%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #1985      +/-   ##
==========================================
- Coverage    64.7%   64.65%   -0.06%
==========================================
  Files         147      147
  Lines       13824    13825       +1
==========================================
- Hits         8945     8938       -7
- Misses       4045     4053       +8
  Partials      834      834

Impacted Files
Coverage Δ

workitem/link/link_repository.go
72.07% <0%> (ø)
:arrow_up:

space/space.go
65.14% <100%> (+0.14%)
:arrow_up:

remoteworkitem/jira.go
75% <0%> (-25%)
:arrow_down:

remoteworkitem/scheduler.go
53.65% <0%> (-7.32%)
:arrow_down:

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 44c5616...46ee302. Read the comment docs.


Crash while building the docs

I'm working on packaging Magic-Wormhole for GNU Guix.
I tried building the docs like this: make -C docs man. It fails like this:
make: Entering directory '/tmp/guix-build-magic-wormhole-0.11.2.drv-0/magic-wormhole-0.11.2/docs'
Running Sphinx v1.7.7
setup.py:20: DeprecationWarning: 'U' mode is deprecated
  long_description=open('README.md', 'rU').read(),
/gnu/store/b7fqhszxl02g6pfm3vw6b3cjz472qrly-python-3.7.0/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown distribution option: 'long_description_content_type'
  warnings.warn(msg)

Configuration error:
There is a programable error in your configuration file:

Traceback (most recent call last):
  File "/gnu/store/q6qyrgr41lqzbray6944l1rs7i6b83kp-python-sphinx-1.7.7/lib/python3.7/site-packages/sphinx/config.py", line 161, in __init__
    execfile_(filename, config)
  File "/gnu/store/q6qyrgr41lqzbray6944l1rs7i6b83kp-python-sphinx-1.7.7/lib/python3.7/site-packages/sphinx/util/pycompat.py", line 150, in execfile_
    exec_(code, _globals)
  File "conf.py", line 70, in <module>
    version, release = _get_versions()
  File "conf.py", line 67, in _get_versions
    short = ".".join(v.split(".")[:2])
TypeError: a bytes-like object is required, not 'str'

make: *** [Makefile:20: man] Error 2
make: Leaving directory '/tmp/guix-build-magic-wormhole-0.11.2.drv-0/magic-wormhole-0.11.2/docs'

Do you have advice?

This package is built with Python 3.7.0.

It looks like I was using py2.7 when I wrote that conf.py, and it uses subprocess to run setup.py --version to inject a version number into the docs, and the particular way it's using subprocess is not portable between py2 and py3. I think have a portable approach in versioneer, we should copy that into here.
In the meantime, using a sphinx that's built against py2.7 might work better.


Updated MD5 hashing to SHA224

Updating a weak cypher identified by OSD Operator Threat Model Analysis.

/hold

Codecov Report

Merging #119 (25e6bcb) into master (33ade6e) will increase coverage by 1.95%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   38.12%   40.07%   +1.95%
==========================================
  Files          14       14
  Lines         703      791      +88
==========================================
+ Hits          268      317      +49
- Misses        402      441      +39
  Partials       33       33

Impacted Files
Coverage Δ

pkg/utils/secrets.go
66.66% <100.00%> (+6.66%)
:arrow_up:

pkg/localmetrics/localmetrics.go
30.30% <0.00%> (-2.46%)
:arrow_down:

pkg/apis/apis.go
100.00% <0.00%> (ø)

cmd/manager/main.go
0.00% <0.00%> (ø)

pkg/utils/clientwrapper.go
0.00% <0.00%> (ø)

pkg/controller/controller.go
0.00% <0.00%> (ø)

pkg/apis/addtoscheme_deadmanssnitch_v1alpha1.go
100.00% <0.00%> (ø)

pkg/controller/add_deadmanssnitchintegration.go
100.00% <0.00%> (ø)

...snitch/v1alpha1/deadmanssnitchintegration_types.go
100.00% <0.00%> (ø)

pkg/dmsclient/dmsclient.go
4.87% <0.00%> (+0.33%)
:arrow_up:

... and 5 more

@jewzaam I should've added it earlier and has now been updated. If you'd rather see the tests removed entirely, I can do that if that's preferred.

@jewzaam I should've added it earlier and has now been updated. If you'd rather see the tests removed entirely, I can do that if that's preferred.

Thanks for the description update.
But, I don't see where pkg/util/secrets is used so my question is can it simply be deleted and remove md5 dependency from the repo?


Use SHA256 to sign packages instead of default SHA1

Related to:

https://github.com/k3s-io/k3s/issues/5588

I tested this out by building and running the centos8 container here and then installed the rpm with dnf in a centos:stream9 container and didn't get any complaints about the signature.

For good measure, I also installed it in a centos:stream8 container for good measure and also didn't have any problem:

I could be wrong, but I don't believe you need to force v3 signatures on EL8/9 as they both ship with yum4 out of box (yum 4 is a symlink to dnf 3).
# ls -l `which yum`
lrwxrwxrwx. 1 root root 5 Mar 24 09:08 /usr/bin/yum -> dnf-3

I could be wrong, but I don't believe you need to force v3 signatures on EL8/9 as they both ship with yum4 out of box

The problem is not the yum version that it ships with, the problem is that the rpm macros on EL8 still don't use the correct signing algs by default. So you have to override the macros to get the signatures that the same distro wants to use when installing packages.


AR Filing - support for dev work

In order to support Hanlun with his AR Filing work, the following is required:

[ ] Determine who has the permissions to make modifications to the build.
[ ] Understand the specific permissions required for these changes.
[ ] Gain insight into how the AR-reminder job is set up and runs, as this knowledge is crucial for both development and providing operations support.

the Ops team, including Hanlun should have permissions and access.
if you don't have permissions, let us know what is needed


Test using Maven semantics

Our integration test (scripted) and local testing (via publishLocal) both use Ivy semantics (latest-wins), which is different from the Maven semantics (nearest-wins).
I've been bitten by this twice now:

https://github.com/sbt/sbt/issues/2598 NoClassDefFoundError: sbt/internal/util/ConsoleOut$
https://github.com/sbt/sbt/issues/3378 java.lang.NoSuchMethodError: sbt.package$.fileToRichFile(Ljava/io/File;)Lsbt/io/RichFile;

We need to get off publishLocal and switch over to using Maven resolution in our integration tests.

Potential idea. Add
  maven-local

to [repositories]. This will make artifacts in ~/.m2/repository available to sbt out of the box.


[good first issue]: Agent uses older Chrome version

Is there an existing issue for this?

[X] I have searched the existing issues

What is the current behavior?
Updated the Chrome driver however the agent seems to pick up the older version.
What is the expected behavior?
NA
Steps To Reproduce
https://testsigma.com/docs/agent/update-drivers-manually/
Version
Testsigma Community Edition

Hi is this issue still open
If so can it be assigned to me


Offline mode for examples doesn't work

Following the steps in the offline section of Getting Started, I cloned the latest version of this repo and ran the react-router project.
Steps to Reproduce

Install example dependencies and run dev script
Open up Chrome dev tools and navigate to Application
Select registered service worker
Click "offline"
Perform a normal refresh

Expected
App loads, including favicon.svg which is defined in includeAssets.
Actual
App doesn't load as several assets cannot be retrieved by the service worker
Recording: https://share.zight.com/WnupkQK6
As an aside, I'm also experiencing the same issue on a net new project.

Offline support will not work in dev, you must build and test it using preview script in a chromium based browser.

You can run the examples  script and follow the wizard: pnpm run examples.

Offline support will not work in dev, you must build and test it using preview script in a chromium based browser.

Is this still the case when devOptions.enabled = true?
I ran the start-preview script and got the following error:

I'm assuming I'm missing some more steps there. Could you point me in the right direction?

You must build the repo first, from root run:
pnpm install && pnpm run build.
You can run the pwa in dev node to test he web manifest and custom sw when using injectManifest strategy. To enable pwa in dev, configure:
devOoptions. enabled = true.
To test anu example offline, you must build the example and use the preview script from the example folder:
pnpm run build && pnpm run preview.
Or you can run the examples script from root folder:
pnpm run examples

Oh, lovely! Sorry I misunderstood what enabling devOptions would get for me.
I can confirm that the example does work offline when the running through preview. Thanks for the help 🙏


As A Developer

As a developer, we are developing this program to help business owners to have a better management system and estimate their profit margin per day. This will also remove or at least reduce the money theft that happens in restaurants, by knowing how much is ordered per table and what the profit should be.

#4 #5 #6 #7 #8 #9


Add print styles

📝Changed routes:

/[slug]
/

(view full size)
(view full size)

Commit bcfab6a01b7b22a3989ab776d4d96286115d522e (https://workshops-git-hc-39-print.hackclub.dev).

omg yay!


Cannot start the app on windows 10

Describe the bug
After updated to the last version, I cannot start outlook on the destop. I reinstalled. But still cannot open or start the software
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Windows Version

(eg. Windows 10 x64 1803)

Additional context and log file
Add any other context about the problem here
Also upload the most recent log file located in C:\Program Files (x86)\Outlook on the Desktop\logs

Can you please attach the logs?  Also check your event viewer for any errors related to the app and post them here please.

Can you please attach the logs? Also check your event viewer for any errors related to the app and post them here please.

Please guide me to find the logs and event viewers. I do not know where they are.
Thanks,


Upmerge v1.8.x into master

@nathanielmanistaatgoogle It is, for the most part, but there is a natural conflict resolution due to version bump on both branches, but changing the build file to what's on master (which was strictly newer), and regenerating the projects resolved everything.
I inspected the effective delta visually and it seems it's fine and everything is there; I don't know why last time git had messed up there.


Kubectl 1.26+ does not properly work with our Google authentication in CI currently

We cannot use the newest version(s) of Kubectl and Helm in our CI, because our Cluster version doesn't support the gke-gcloud-auth-plugin yet


Support anonymous code

Create and compile code without saving. Is this possible?

done https://github.com/Pravdomil/arduino.tmbundle/commit/9cc9f073f26302253aa53afb759983736366853e


Does vscode support TODO list?

VSCode Version: 1.18.1
OS Version: Ubuntu 16.04

I mean a source code that commented with special some mark, for example in python we could have a comment like: # TODO: need to get EmailAddress object from user object. Then we could have a have a special command that list all of them and we could jump to that file and line.
This would be useful when we have some unclear idea or a problem that we couldn't fix right away, and we want to make a note about it. We could jump to another problem and when we ready we could just jump right back for it.
I think jetbrains support this feature.
Oh and # NOTE:

https://marketplace.visualstudio.com/items?itemName=wayou.vscode-todo-highlight

Not so helpful, as list all todos not working for python. In my case it only list the todo in javascript. It list all todos in output panel; to jump to the file, we have to alt+click to follow link and alt+click not working on my ubuntu.
It would be helpful if todos have it's own panel.

So, you have 2 other problems:

You did not read the extension description
use "todohighlight.include" property to include "**/*.py"
cannot follow link on Ubuntu

Ok, it's ctrl+alt+click to follow link on ubuntu #34710
I just think about todos own panel.


Portability on Solaris

portability.h breaks on Solaris/SmartOS/Illumos as it assumes !(OSX || Linux) => BSD.
Solaris does not have sys/endian.h.
The patch below fixes this. I am using the macros {BE|LE}_IN{16|32|64} from Solaris' sys/byteorder.h which are a bit slower but can deal with unaligned access as the values might be read from a network buffer and not be guaranteed to be aligned on word boundaries.
--- /home/majid/portability.h.dist  Fri Sep 11 11:56:21 2015
+++ /home/majid/portability.h       Fri Sep 11 12:04:04 2015
@@ -29,6 +29,20 @@
 #  define le64toh(x) OSSwapLittleToHostInt64(x)
 #elif defined(__linux__)
 #  include <endian.h>
+#elif defined(sun) /* Solaris */
+#  include <sys/byteorder.h>
+#  define htobe16(x) BE_16(x)
+#  define htole16(x) LE_16(x)
+#  define be16toh(x) BE_IN16(x)
+#  define le16toh(x) LE_IN16(x)
+#  define htobe32(x) BE_32(x)
+#  define htole32(x) LE_32(x)
+#  define be32toh(x) BE_IN32(x)
+#  define le32toh(x) LE_IN32(x)
+#  define htobe64(x) BE_64(x)
+#  define htole64(x) LE_64(x)
+#  define be64toh(x) BE_IN64(x)
+#  define le64toh(x) LE_IN64(x)
 #else // *BSD
 #  include <sys/endian.h>
 #endif

@fazalmajid Thank you for the diff.  I will merge it soon.

Fixed in #16.
@fazalmajid Sorry for the long delay!


[instrumentation] consider dropping Instrumentation#disable()

Description

[!IMPORTANT]
Do not start working on implementation yet. This is a feature-request that's pending maintainer feedback for open questions.
Researching feasibility of this request and feedback is encouraged. If you do, please post your findings as a comment on this issue.

Every OpenTelemetry instrumentation has a disable() functionality that allows users to call it to unwrap the library it's instrumenting on runtime.
<EMAIL_ADDRESS>introduced a change via https://github.com/nodejs/import-in-the-middle/pull/153 which broke that functionality for ESM users. Since that version was released, we've not received a single report that this functionality is broken - which leads me to believe that this feature is of negligible value to our end-users, all while introducing additional complexity, points-of-failure and maintainance overhead to our @opentelemetry/instrumentation-* packages and third-party instrumentations.
Internally this feature seems to be mainly intended for testing - we make extensive use of it though our projects in integration tests.
I propose we deprecate the functionality, make Instrumentation#disable() optional and then gradually phase out use of it in our instrumentations and tests before eventually removing it altogether.
Possible ways to move forward
Before moving forward, we (@open-telemetry/javascript-maintainers) will have to find out if this is the path we want to go. If the answer is yes we need to:

[ ] create a follow-up type:research issue to determine if removing disable from tests is even feasible. I suggest we use @opentelemetry/instrumentation-http for this kind of experiment as it is the most feature-rich instrumentation.

we may have to split tests that rely on wrapping with different options to different test files, which mocha will execute in different processes, which could make unwrap functionality unnecessary while reducing the amount of code-changes needed to accomplish the task.

If the outcome of this research is that it is feasible, we should:

[ ] create a follow-up type:feature issue to deprecate Instrumentation#disable() and make it optional in the interface.

Doing so will break @opentelemetry/instrumentation registerInstrumentations() (old instrumentation may be used with the latest @opentelemetry/instrumentation version, but instrumentations that depend on the latest version will not work with older versions of registerInstrumentations().

[ ] create create a type:feature-tracking follow-up for this repository (https://github.com/open-telemetry/opentelemetry-js) to remove the usages of disable() from tests
[ ] create create a type:feature-tracking follow-up for this repository (https://github.com/open-telemetry/opentelemetry-js) to remove the usages of disable() from tests

Additional Resources

import-in-the-middle PR that introduced the behavior that broke disable on ESM: https://github.com/nodejs/import-in-the-middle/pull/153
PR to skip ESM disable tests in @opentelemetry/instrumentation: #5153
<please comment with links to any additional context and I'll add it here - I know that we talked about this somewhere else before but could not find the specific thread>

we may have to split tests that rely on wrapping with different options to different test files, which mocha will execute in different processes

Nope. Mocha runs the separate test files in the same process.

example
% pwd
/Users/trentm/tm/opentelemetry-js9/experimental/packages/opentelemetry-instrumentation-http

% ls test/*.test.ts
test/a.test.ts test/b.test.ts

% cat test/a.test.ts
describe('a test', () => {
  it('should show its PID', async () => {
    console.log('pid is', process.pid);
  });
});

% cat test/b.test.ts
describe('b test', () => {
  it('should show its PID', async () => {
    console.log('pid is', process.pid);
  });
});

% npx mocha test/*.test.ts

  a test
pid is 95618
    ✔ should show its PID

  b test
pid is 95618
    ✔ should show its PID

  2 passing (2ms)

I (now vaguely) recall this being a source of surprises in some of the tests: a test suite that is enabling/disabling repeatedly or a test suite that is enabling instrumentation in separate test files is sometimes getting multiple wrapping/monkey-patching of the module.

I removed the

we may have to split tests that rely on wrapping with different options to different test files, which mocha will execute in different processes

Nope. Mocha runs the separate test files in the same process.
example
% pwd
/Users/trentm/tm/opentelemetry-js9/experimental/packages/opentelemetry-instrumentation-http

% ls test/*.test.ts
test/a.test.ts test/b.test.ts

% cat test/a.test.ts
describe('a test', () => {
  it('should show its PID', async () => {
    console.log('pid is', process.pid);
  });
});

% cat test/b.test.ts
describe('b test', () => {
  it('should show its PID', async () => {
    console.log('pid is', process.pid);
  });
});

% npx mocha test/*.test.ts

  a test
pid is 95618
    ✔ should show its PID

  b test
pid is 95618
    ✔ should show its PID

  2 passing (2ms)

I (now vaguely) recall this being a source of surprises in some of the tests: a test suite that is enabling/disabling repeatedly or a test suite that is enabling instrumentation in separate test files is sometimes getting multiple wrapping/monkey-patching of the module.

Mhm, I see - that's a bummer :/
For some reason I thought that was the case - thanks for the correction - I crossed that comment out in the issue above.

Funnily enough I think I need this feature now. My service hosts two express/http instances, and I only want to instrument one of them. Seems like disable() would be one way to do that?

Funnily enough I think I need this feature now. My service hosts two express/http instances, and I only want to instrument one of them. Seems like disable() would be one way to do that?

Hmm, I don't think that'd work with disable(), unfortuantely. It would just unwrap both instances, I think what you'd want is to not wrap them in the first place or some kind of filter or to suppress telemetry for the other instance. 🤔 Suppressing tracing for certain calls can be done via suppressTracing() from @opentelemetry/core.


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-datafactory-factory
Module Details
AVM Resource module for Data Factory
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
No response
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

I would like to take ownership for this

Thanks @asishr14 for reaching out and for your interest, AVM specifications mandate that the owner needs to be a Microsoft FTE to ensure long term maintainability and support by Microsoft.

Hi @asishr14,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

Hi,
I agree and confirm all the pages described. However, I would like to have
a collaborator for the Bicep Module. Please let me know if that is possible.
On Fri, Jan 26, 2024 at 9:27 PM Bilal Amjad @.***>
wrote:

Hi @asishr14 https://github.com/asishr14,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what
module ownership means:

Team Definitions & RACI
https://azure.github.io/Azure-Verified-Modules/specs/shared/team-definitions
Shared Specification (Bicep & Terraform)
https://azure.github.io/Azure-Verified-Modules/specs/shared
Module Support
https://azure.github.io/Azure-Verified-Modules/help-support/module-support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence
below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS
AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/Azure-Verified-Modules/issues/526#issuecomment-1912920534,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADA5RB6763CXD4GOHLKH3JLYQRQ2ZAVCNFSM6AAAAABB4T7EOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSHEZDANJTGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Thank you,
Asish R.

Hello - I'm interested in the development of this module via Terraform as an owner. Thanks!

Hi @Karni-G,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

@asishr14 - I see you are requesting for Bicep one. Could you please check the looking for owners section(https://github.com/orgs/Azure/projects/529) ? This one is specifically for TF. Also if you do not see in the list, you can propose one.

@PmeshramPM : Sorry for the confusion. I am requesting for the TF module only. As the document (Shared Specification (Bicep & Terraform)) to accept for both TF & Bicep, I wanted to confirm that i will be only owning TF and NOT the Bicep.

Hi @asishr14,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

@PmeshramPM Pankaj Meshram FTE : Sorry for the confusion. I am requesting for the TF module only. As the document (Shared Specification (Bicep & Terraform)) to accept for both TF & Bicep, I wanted to confirm that i will be only owning TF and NOT the Bicep.

Yes, this will only be for TF, you don't necessarily need to develop and own the Bicep equivalent unless you want to.

Hello - I'm interested in the development of this module via Terraform as an owner. Thanks!

@Karni-G since @asishr14 reached out first so we've assigned him as the owner, you can work with them as co-owner and contributor on this module if you'd like to and @asishr14 is ok with that

Hello - I'm interested in the development of this module via Terraform as an owner. Thanks!

@Karni-G since @asishr14 reached out first so we've assigned him as the owner, you can work with them as co-owner and contributor on this module if you'd like to and @asishr14 is ok with that

@Karni-G open to collaborate. Please feel free to reach out.

Hello - I'm interested in the development of this module via Terraform as an owner. Thanks!

@Karni-G since @asishr14 reached out first so we've assigned him as the owner, you can work with them as co-owner and contributor on this module if you'd like to and @asishr14 is ok with that

@Karni-G open to collaborate. Please feel free to reach out.

Will contact you Asish

@mbilalamjad : i created a separate repo for the module from the template and working on it over there, is there anything i need to do on this issue?

Hey @asishr14, sounds good, just if you could leave an update here, could be as detailed or as short as you like, this would make the bot happy, and I can remove the needs attention label from it which gets added after 3 weeks of inactivity on the module proposal till the module is published into the Hashi Corp registry and this proposal is closed at that time.

Hey @mbilalamjad, i would like to update the module ownership to my work git account where i have access to Azure Org, so i will be contributing from that account only. Here is my work git ID - @asishr .

Hey @mbilalamjad Bilal Amjad FTE, i would like to update the module ownership to my work git account where i have access to Azure Org, so i will be contributing from that account only. Here is my work git ID - @asishr Asish Racha FTE .

Requesting @prjelesi to advise on this change

HI @asishr,
please proceed with development, I will update index page.

Repo created and first commit added.

Repo created and first commit added.

@asishr14, can you please provide a link to the repository? It's supposed to be created with this URL: https://github.com/Azure/terraform-azurerm-avm-res-datafactory-factory but this doesn't exist. Thanks!

Hi, The repo I created with that name, got archived and I didn't got a chance to work on it. Let me know if there's anything else I can share.On Aug 12, 2024 12:51, Máté Barabás @.> wrote:Repo created and first commit @., can you please provide a link to the repository? It's supposed to be created with this URL: https://github.com/Azure/terraform-azurerm-avm-res-datafactory-factory but this doesn't exist. Thanks!—Reply to this email directly, view it on GitHub or unsubscribe.You are receiving this email because you were assigned.Triage notifications on the go with GitHub Mobile for iOS or Android.

Repo unarchived

Changes updated to forked repo

Minor updates pushed

Pending standardization

Hi @Karni-G, are you still intrested in development of this module?? I am not able to spend enough time on this, i have base standard template implemented.

Hi @asishr  , I'm struggling with bandwidth at the moment so I won't be able to support it actively. However, if you can find another contributor, I can guide them with the information about ADF and associated resources.


WIP: Bisect kubedns bugs

Trying to figure out where #4014 was caused.

test-me-please

test-me-please

test-me-please

test-me-please


updating the README with more info on plugin resource specification

first attempt at making the docs better.
working in progress

whoops. merged this one by accident, but I agree we should consolidate. will have another pass at this in a separate PR.


Added new sample

Change map view background

@singhgag Can you update the branch?

Also, I think its clever that you initialized an empty map with just a spatial reference so that the customized grids would be noticeable, I'd like to stay with this spirit but I feel like there should be some data on the map to make it look like a map. How about we add a MapImageLayer for just this sublayer showing the continents: http://sampleserver6.arcgisonline.com/arcgis/rest/services/WorldTimeZones/MapServer/2
Hopefully that'll keep enough of the background grid visible to be noticeable when you change settings.

The service won't let me hide sublayers, because Single Fused Map Cache: true. So I added the layer as is. Also updated the branch to resolve the conflicts.


Audio

I'm not sure this is of any interest to you, but I've implemented an Initial basic TurtleAudio class and use it with Turtle to explore  some sonification.
If you don't have time or interest no thing. I'm more of a supercolider guy, but I wanted to learn a bit about the web audio apis.
I have one issue at the moment and that is creating (suspending and resuming) the initial AudioContext. I've tried beginning with LSystem (where it's passed on in from Turtle to TurtleAudio), but that's wrong. There always appears to be one extra initial AudioContext running. I was hoping that the dispose methods would get me there. Any insight as to where (probably 'createScene'?) I should be setting up and stop starting would be appreciated!
Thanks and regards,
Mark
PS:  I did a bunch of sonifications with supercollider:
https://github.com/poetaster/supercollider-lsystems https://poetaster.de/sc-ls/ which go me going on this.

This is super cool! When I try it locally - the entire composition goes wooosh - much faster than https://poetaster.de/sc-ls/ - do I need to change something to make it sound similar?
btw, this could be great priming source to https://huggingface.co/spaces/facebook/MusicGen - this one is trance with deep bass :)
https://github.com/anvaka/lsystem/assets/225407/a917ea75-791f-4445-a3ff-71017b75da70
Just check this one out

This is super cool! When I try it locally - the entire composition goes wooosh - much faster than https://poetaster.de/sc-ls/ - do I need to change something to make it sound similar?

Do you mean the super collider files or the initial browser based sketch here? The SC files all set the clock rate:
	// up the rate a bit
	TempoClock.default = TempoClock.new(1);

Which is the global rate.  If it's too fast in SC, set  TempoClock.new(0.5); for instance.
For the web version, I still have to build instruments, this is just an initial sketch to get started. And I couldn't get rid of the doubled AudioCtx (which means you always have a background hum).

btw, this could be great priming source to https://huggingface.co/spaces/facebook/MusicGen - this one is trance with deep bass :)
tmpudhgxcyf.mp4
Just check this one out

Hah! What I was going for is automagic Ragas (the India Carnatic Music System). But that is very suitable material for Trance, for sure! I haven't looked at MusicGen yet, but I've built my own neural net instruments before. I'll go have a look ! The approach here is kinda primitive but has the advantage that the rules for generating more or less complex images runs parallel to the production of the music, so you get generative audiovisuals from simple rules.
It might interest you, if you hadn't already seen it, here's another approach to algo composition in the browser: https://alexcrist.github.io/scaler/

Ah, one more thing, I hadn't gotten the drawing and audio generation running in parallel in SC because of factors like the number of generations leading to really long audio tracks, but also cause I just got caught up in the musical bits. Some of the audio is generated with so few generations that the resulting image would be 'paltry'. But that's the fun of it all.

I'm very far from audio generation and audio APIs, but this looks very interesting. Still trying to understand your change here - I see you've got 2 oscillators,  there is updateWave() and setChord() (doesn't seem to be used).
If I read it correctly, this is the core of how audio is generated:
    this.turtleAudio.freq1 = this.turtleAudio.freq1 + (distance * n[0]) ;
    if ( this.turtleAudio.freq1 > 1000 )
      this.turtleAudio.freq1 = 138.5
    this.turtleAudio.updateFreq1();

Sorry for the naive question: how this frequency update translates to sound?

Sorry for the naive question: how this frequency update translates to sound?

Not at all naive, it's still naive code :) here the previous frequency is modified by first vectors motion * distance. So, you just get a rising, falling frequency (or no change) with movement. In my supercollider patches I did this with the primitives, which is more difficult (still) here.
I use +-fxy and so on directly in the sc context. Here I had just started playing with freq up down with angle and motion changes. I had started to test picking notes from ascending/descending scales, but had only started. The background instance was driving me batty. One can also introduce all kinds of heuristics as a product of changes.
One could think of lots of variations, but in principle you always have directed motion in patterns. like chords played in alternating fifths chords up and down.
In the sc context I also use different instruments. Here we only have a sawtooth and a sinus wave osc.

I helps sometimes to have the right starting point. Try:
  // P. Bourke after Saupe
axiom: VZFFF
rules:
  V -> [+++W][---W]YV
  W -> +X[-W]Z
  X -> -W[+X]Z
  Y -> YZ
  Z -> [-FcFF][+FdFF]F

color: green
depth:10
direction: [0, 1, 0]
angle: 20
actions:
  c => setColor('lightgreen')
  d => setColor('lime')

It's different drawing to the left or right.

Sigh, sorry for so much content. I've had to revert to attaching the AudioContext to window. But even then calling suspend/resume is flaky as 'dispose' doesn't seem to be called on completion of rendering. So even with only one global audio context exists, one can't reliably turn it on and off. I'm looking at building this differently.

One more note. I was going at this from the 'lowest' level. It might make more sense to look at using https://tonejs.github.io/ which already has a number of instrument models and ADSR (volume envelopes) and so on ....

Sooo, I've begun with tone.js: https://github.com/poetaster/lsystem/tree/tonejs
The big issue here is how to get createScene / LSystem to draw in the audio context.
		const loop = new Tone.Pattern(((time, note) => {
			synth.triggerAttackRelease(note, "16n", time);

			// Draw.schedule takes a callback and a time to invoke the callback
			Tone.Draw.schedule(() => {
				// the callback synced to the animation frame at the given time
				const noteElement = document.querySelector("#"+note);
				noteElement.classList.add("active");
				setTimeout(() => {
					noteElement.classList.remove("active");
				}, 100);
			}, time);
		}), ["C4", "E4", "G4", "B4", "D5"]).start(0);

This simple example shows directly turning on an off an element class to animate. I'm wondering what the best way is to implement a callback in 'createScene' so that the raf takes place on demand?

Sorry I'm not familiar with tone.js. Do I understand correctly that you are trying to have one animation frame to be executed only after the note has done playing?

The duration of the entire animation has to 'make sense' in terms of the musical time. That means, not frame to note per se, but that the the rate at which frames are drawn depends on the duration of the sounds that are made while that move/draw/rotate effect a change in the sequence of tones/notes/sounds. You can speed up the rate at which sounds are made, but if you link the drawing directly to sound, you have to give one precedence. If you let the drawing determine the rate of change, as is seen with this pull, it's a really fast 'blip'. If you defer frame rendering to a queue that depends on the duration of the sounds for each 'tick' of system, the drawing 'follows' the sound. But just have a look at:
https://tonejs.github.io/examples/animationSync
The main point with tone.js is that it has a bunch of primitives that make it much easier for you to grok, without my mucking about with 'realy' primitive basics. Instuments, sequences, patterns,  a Transport. What I was doing here was with real primitives. But in the end, I'll have to add a ton of layers anyway, and tone does that quiet well, though it's a bit heavy.  I'll just try to get this to a point where it's easier for you. Sorry for noise to signal ratio!

Man am I long winded.
It would certainly also be possible to just do as I've done in this context with  calls in Turtle.js to play like  conga.triggerAttack(pitch, time, Math.random()*0.5 + 0.5);  if you slow the frame rate down.

This is a first take with the synth triggering still taking place in Turtle.js  but using actual instruments.... https://github.com/poetaster/lsystem/tree/tonejs
I'm going to close this PR since, even if I return to a simplified method, it'll look completely different.
If you have a chance take a look at that other branch for an idea of how Tone.js can be used. I need to brood on this for a while since it's a a LOT more finicky than working with supercollider (or pd or c++ :)


Laravel 5.5 Vuetified Real Time Starter App

Laravel 5.5 is just around the corner and Building SPA has never been so Easy With Vue JS.
Everyone Has Always Had Trouble Setting Up Their Own First Real Time App
Instead of Experimenting your Set up...
Ive Already Done it , and Put it all in One Piece...
This Starter App is Compose of Laravel 5.5 , Laravel Passport , Laravel Echo Server , Laravel Echo, Vue , Vue Router, Vuetify. Perfect for SPA Realtime Application...
Using Our Favorite Frameworks.
Very Easy to Install , and If Your Using VSCode , The Bonus is You Get Very Specific Linting and Auto Fix Error Code.
In the Future Ill Add a way to Customize and Save State of the Vuetify Components in the Back end.
Thats the Purpose of the Vuetified Service Provider...
But If You Like if Please Star and Share :)
https://github.com/codeitlikemiley/vuetified

This isn't a issue, you should create a PR adding this to the list rather than making an issue.

@codeitlikemiley Please create a PR if this is still relevant


LFS-535: Solve concurrency issues when uploading somatic variant files as CSVs in bulk

Jira link.
Allows the upload of multiple files at once, or one at a time with multiples selected.

To test: no combination of switching subject/tumor names, uploading single files vs uploading all, or clicking things out of order should break anything.

Can we disable UPLOAD ALL bttn once all files are uploaded?

Selectin this (4 files, 2 with incorrect name format):

Would result in this:

It would be nice if the other file with the wrong name  format was mentioned.
However, selecting this ( first file with incorrect format, and 4 with correct):

Results in this:

Can we disable UPLOAD ALL bttn once all files are uploaded?

@sashaandjic This has already been done in the last commit, you might not have the latest code.

It would be nice if the other file with the wrong name format was mentioned.

Agreed. Looks like the way we set and display the error needs some rework.

The last commit introduced the following problem. I was trying to upload 3 files: 2 with proper format and 1 with a wrong one. Because one of them had a wrong format, I can no longer upload the other two.

I had no issues uploading multiple files of a different format at the same time. I was also able to rename subjects for some of them without any issue.
The problems reported above can be logged separately.

The last commit introduced the following issue. I was trying to upload 3 files: 2 with proper format and 1 with a wrong one. Because one of them had a wrong format, the UPLOAD ALL was disabled. I can upload each one separately.

I confirm. @OrdiNeu I don't see we need to disable the "upload all" button on error, but maybe I'm missing something.

How should we treat this situation?
In the Variant Upload form I upload the same file 2 times.
The Variant Upload knows and displays the message stating that there is another version of the file.
Then I go to the Somatic Variants form and upload the same file one more time.
Should Variant Upload form be aware of the third version? Right now it isn't.

How should we treat this situation?
In the Variant Upload form I upload the same file 2 times.
The Variant Upload knows and displays the message stating that there is another version of the file.
Then I go to the Somatic Variants form and upload the same file one more time.
Should Variant Upload form be aware of the third version? Right now it isn't.

The "versions" that the variant uploader is reporting are files with the same name (not overwritten by a subsequent upload) currently in use anywhere in the database. TBH I find this confusing myself, and "versions of this file" is definitely not the best wording for it as it can be misinterpreted. It should be reworked as a separate task together with the question that @sdumitriu raised above about what files we should be counted (and what message should be displayed).

@sashaandjic

However, selecting this ( first file with incorrect format, and 4 with correct):

This should be fixed in cfe0a0c :heavy_check_mark:
@sashaandjic

The last commit introduced the following issue. I was trying to upload 3 files: 2 with proper format and 1 with a wrong one. Because one of them had a wrong format, the UPLOAD ALL was disabled. I can upload each one separately.

This should be fixed in cfe0a0c :heavy_check_mark:


added fix for encoding and decoding phantom data

This change fixes #114.
I was running into the same issue, and noticed that PhantomData's implementation of encode was just returning Ok, even though it was not actually emitting anything. This caused the outputted JSON to have an invalid syntax.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks!


Order Status Kanban

Coverage decreased (-0.7%) to 75.407% when pulling a88adbb336c0d13395959c38c8483d9548ac20bc on jackyruslymoonlay:master into 1e90ea4f5bdce28a0087a57bc7da1c9118d2f073 on danliris:master.


⚠ ClamAV has degraded performance

In 324d8f7, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 71 ms

Resolved: ClamAV performance has improved in f1e6b70 after 535 days, 17 hours, 5 minutes.


Implement skeletons for AbsolutePath and RelativePath

Closes #100

@ljiazh3ng here's the skeletons for AbsolutePath and RelativePath!
Sorry for stealing the work from you 😅 , I need the type to implement the next parts of CorrectionEngine. The rest of the implementation is yours!


Port most of the compass framework

This merge brings over a good portion of the compass framework.  It also:

renames compass to polaris nearly everywhere (but leaves encompass rather than changing it to enpolaris ;-))
renames "MPAS cores" to "components" in the code and documentation
refers to "E3SM components" rather than "MPAS models"
changes compass run to polaris serial in anticipation of polaris run being the default, task-parallel approach in the near future
Updates to mpas_tools 0.18.0 to fix an issue with reading SciColorVis colormaps
Adds a bare-bones ocean component with the cosine bell test case
Adds a chunk of documentation for both the User's and Developer's Guides in MyST format

Checklist

[x] User's Guide has been updated
[x] Developer's Guide has been updated
[x] Documentation has been built locally and changes look as expected
[x] Testing comment in the PR documents testing used to verify the changes
[x] New tests have been added to a test suite

Testing
I have build the documentation locally.  While there are many complaints about missing sphinx redirects (because of missing documentation yet to be ported), it builds and has no other errors I noticed.
I have built conda and spack environments on Chrysalis using ./configure_polaris_env.py and have used it to successfully run both cosine bell test cases (QU and Icos).
 Would you be willing to review it in some capacity?  Perhaps a minimum might be to run the configure script, similarly to what I did above (building the spack env takes many hours), build the docs locally, and see if you can also run the cosine bell.  Anything more substantial would be up to you.  There are bound to be errors in both the docs and the code port but it is so many files (71 currently) that you can't hope to look over even a small fraction of them.

@xylar I'd be happy to review!

The mache branch I was testing with got merged, so now the instructions would be:
SCRATCH=/lcrc/group/e3sm/${USER}
./configure_polaris_envs.py \
    --conda ~/mambaforge/  \
    --env_name polaris_test  \
    --update_spack  \
    --mache_fork E3SM-Project/mache  \
    --mache_branch main  \
    --recreate  \
    --spack $SCRATCH/spack_test  \
    --tmpdir $SCRATCH/spack_temp
    ```

@xylar I have pushed a few commits that make the cosine bell case a bit more suitable as an "ideal" test case, as we discussed. Please edit or request edits as needed. I confirmed that the diffs introduced by the initial state for the cosine bell case are similar to those in https://github.com/MPAS-Dev/compass/pull/519.

@cbegeman, your additions look great to me!  I just want to run the tests one last time to do my due diligence.

I reran my tests on Chrysalis with @cbegeman's 4 new commits and everything looks great!


Flutter 2.5 Scrolling Bug with PageView

When a pageview is use inside a scrolling widget, I'm not able to scroll horizontally with the page view.
Only in Flutter Web
Steps to Reproduce

code sample
class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(),
        body: SingleChildScrollView(
          child: SizedBox(
            height: 200,
            child: PageView.builder(
              itemBuilder: (context, index) => Container(
                child: Text('$index'),
                color: (index == 0) ? Colors.red : Colors.blue,
              ),
              itemCount: 2,
            ),
          ),
        ),
      ),
    );
  }
}

Expected results:
Be able to change page when dragging the page.
It works for mobile but not on the web.
Actual results:
Nothing happen, no error, no log

Logs

[√] Flutter (Channel stable, 2.5.0, on Microsoft Windows [version 10.0.19043.1202], locale fr-CA)
    • Flutter version 2.5.0 at C:\dev\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4cc385b4b8 (13 hours ago), 2021-09-07 23:01:49 -0700
    • Engine revision f0826da7ef
    • Dart version 2.14.0

This bug apparently occurs on ListView too when scrollDirection is set to Axis.horizontal.

Hi @wer-mathurin as per this comment, a breaking change was made with regards to the behaviour on desktop. Can you follow the link the comment and see if the fix works for you?
Thank you

i've updated to 2.5.0 stable this morning and faced scrolling issue on desktop debug build..
The issue is very clear. Scrolling just doesn't work at all. Tested on m1 macbook air Big Sur 11.5.2. Is it my own problem? I got no way to figure out. I downgraded to 2.2.3 stable, and all the things work perfect now [:
No single error or message in console. No single one, just don't work both horizontal and vertical scroll. Hope this comment reach to the team! [:

@exitist as I stated in my comment above, there is a breaking change in the behaviour of scrollables on desktop. Kindly follow the directions in the link below and see if it fixes your issue. Thank you
https://flutter.dev/docs/release/breaking-changes/default-scroll-behavior-drag

@danagbemava-nc you're right, it's a breaking change scrollables behaviour on desktop. when I tried running the web on mobile, the dragging feature comes back. However I spotted weird logs when using nested scrollables. Here's a sample code of my app
PageView(
  controller: _pageController,
  onPageChanged: _onPageChanged,
  children: [
     CustomScrollView(
        slivers: [
           SliverToBoxAdapter(ListView), // horizontal
           SliverToBoxAdapter(ListView), // horizontal
           SliverToBoxAdapter(ListView), // horizontal
         ],
      ),
      CustomScrollView(
         slivers: [
            SliverToBoxAdapter(ListView), // horizontal
            SliverToBoxAdapter(ListView), // horizontal
         ],
      ),
...

Now say I'm on the first page of the PageView, it works normally. But when moving to the next page and scroll the page, here's the log
Launching lib/main.dart on Chrome in debug mode...
This app is linked to the debug service: ws://<IP_ADDRESS>:40789/_TSo5xl7SPE%3D/ws
Debug service listening on ws://<IP_ADDRESS>:40789/_TSo5xl7SPE=/ws
💪 Running with sound null safety 💪
Connecting to VM Service at ws://<IP_ADDRESS>:40789/_TSo5xl7SPE=/ws
[log] _TransformedPointerDownEvent#285cc(position: Offset(476.0, 923.0))

════════ Exception caught by animation library ═════════════════════════════════
The following assertion was thrown while notifying status listeners for AnimationController:
The provided ScrollController is currently attached to more than one ScrollPosition.

The Scrollbar requires a single ScrollPosition in order to be painted.

When the scrollbar is interactive, the associated Scrollable widgets must have unique ScrollControllers. The provided ScrollController must be unique to a Scrollable widget.

When the exception was thrown, this was the stack
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 251:49      throw_
packages/flutter/src/widgets/scrollbar.dart 1315:9                                <fn>
packages/flutter/src/widgets/scrollbar.dart 1338:14                               [_debugCheckHasValidScrollPosition]
packages/flutter/src/widgets/scrollbar.dart 1257:14                               [_validateInteractions]
packages/flutter/src/animation/listener_helpers.dart 233:27                       notifyStatusListeners
packages/flutter/src/animation/animation_controller.dart 814:7                    [_checkStatusChanged]
packages/flutter/src/animation/animation_controller.dart 748:5                    [_startSimulation]
packages/flutter/src/animation/animation_controller.dart 611:12                   [_animateToInternal]
packages/flutter/src/animation/animation_controller.dart 462:12                   forward
packages/flutter/src/widgets/scrollbar.dart 1567:46                               [_handleScrollNotification]
packages/flutter/src/widgets/notification_listener.dart 206:27                    [_dispatch]
packages/flutter/src/widgets/notification_listener.dart 122:19                    visitAncestor
packages/flutter/src/widgets/scroll_notification.dart 31:18                       visitAncestor
packages/flutter/src/widgets/framework.dart 4133:39                               visitAncestorElements
packages/flutter/src/widgets/notification_listener.dart 138:13                    dispatch
packages/flutter/src/widgets/scroll_activity.dart 94:90                           dispatchScrollUpdateNotification
packages/flutter/src/widgets/scroll_position.dart 899:5                           didUpdateScrollPositionBy
packages/flutter/src/widgets/scroll_position_with_single_context.dart 221:7       pointerScroll
packages/flutter/src/widgets/scrollable.dart 718:16                               [_handlePointerScroll]
packages/flutter/src/gestures/pointer_signal_resolver.dart 199:7                  resolve
packages/flutter/src/gestures/binding.dart 446:29                                 handleEvent
packages/flutter/src/gestures/binding.dart 420:14                                 dispatchEvent
packages/flutter/src/rendering/binding.dart 278:11                                dispatchEvent
packages/flutter/src/gestures/binding.dart 374:7                                  [_handlePointerEventImmediately]
packages/flutter/src/gestures/binding.dart 338:5                                  handlePointerEvent
packages/flutter/src/gestures/binding.dart 296:7                                  [_flushPointerEventQueue]
packages/flutter/src/gestures/binding.dart 279:32                                 [_handlePointerDataPacket]
lib/_engine/engine/platform_dispatcher.dart 1018:13                               invoke1
lib/_engine/engine/platform_dispatcher.dart 182:5                                 invokeOnPointerDataPacket
lib/_engine/engine/pointer_binding.dart 130:39                                    [_onPointerData]
lib/_engine/engine/pointer_binding.dart 307:14                                    [_handleWheelEvent]
lib/_engine/engine/pointer_binding.dart 571:7                                     <fn>
lib/_engine/engine/pointer_binding.dart 288:87                                    <fn>
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 334:14  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 339:39  dcall
The AnimationController notifying status listeners was: AnimationController#e29ad(▶ 0.000)
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by animation library ═════════════════════════════════
The provided ScrollController is currently attached to more than one ScrollPosition.
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by animation library ═════════════════════════════════
The provided ScrollController is currently attached to more than one ScrollPosition.
════════════════════════════════════════════════════════════════════════════════

To prevent these logs showing up, I decided to add ScrollController to each CustomScrollViews. Nonetheless, the app runs normally. I just have no idea what actually causes the error logs showing up.

On my side after applying the general guidance of the migration guide, everything run as before.   Since @iandis have a different bug.  Maybe this can be a better idea to create it own bug to track it properly?

@wer-mathurin, you're right.
@iandis since you seem to be experiencing a different issue, kindly open a new issue and feel free to tag me.
Closing based on this comment


Update the default renderingBaseURL

This fixes the default renderingBaseURL so that it works with nested
routes.
Closes #177

Coverage remained the same at 97.51% when pulling<PHONE_NUMBER>64a5c49d50400330fbabd85213f0ae on rb into afdd9a86c86215b20a656fe79ac634508c551d8c on major.


Remove plasma-readonly.dappchains.com override

It's no longer necessary.

https://github.com/loomnetwork/loom-js/pull/309


clients: update test client to support modifying test builder

Gives user's the ability to customize their test builder within test cases when more advanced configuration is needed

/cc @kononovn


query typo

= = to ==

@mattiasborg82 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


did my own version of mergesort. Tested multiple times.

This merge sort is easy to follow. The comments are helpful.


[LTS] Kestrel considers Connection: keep-alive, upgrade as non-upgrade request

Original issue: https://github.com/aspnet/KestrelHttpServer/issues/1170.
We'll need to fix this in both 1.1.0 and 1.0.2 versions of Kestrel.

Make sure to bump Hosting dependency to 1.0.1 once  https://github.com/aspnet/Hosting/issues/873  is in.

This patch is approved, please ensure it is merged into the correct branch and building as part of the patch train.

 A request with Connection: keep-alive, upgrade to Kestrel 1.0.1 gets a MessageBody type of ForRemainingData, which is expected.
@anurse Did you repro the original issue on Kestrel 1.0.1? Do you know up to what version Firefox was sending Connection: keep-alive, upgrade? Latest version sends Connection: Upgrade.

I did not repro the original issue on 1.0.1, but neither did I try to repro it :). @BrennanConroy had the original repro. If the behavior is already correct in 1.0.1, I don't see a need to port the fix.

I can check tomorrow

Derp 😄 Let's see what happens here - it's easy to not check something in 😄

So 1.0.1 worked because it didn't even check for "upgrade" and by default returns a ForRemainingData, you can see this change https://github.com/aspnet/KestrelHttpServer/commit/73656f6503688b6eb47ed7a5e93b3db76cbb2280 is when it "broke"
So 1.0.2 can probably stay as is.

Alright I'm gonna close this then.

Cool. Could we port the test over so we ensure that the behavior is never regressed?

Agreed, @cesarbs could you port the test? Also the labels on this bug :)

The tests added in #1178 were mostly unit tests that make ensure Kestrel's properly interprets the header in it's internal data structures.
We need a new test verifying that it's possible to read all the data sent by the client over the upgraded connection given a Connection: keep-alive, upgrade  request. This test could be merged into 1.0.* and dev.

@halter73 Yep, this one should do: https://github.com/aspnet/KestrelHttpServer/pull/1178/files#diff-91e1a141d6812899520ca7d9e201e647R294

👍 It looks like that should pass in 1.0.*. A functional test might be nice too.

Ok so we're not fixing any product code, but we're just updating tests?

@Eilon Correct.

Ok, I'll remove it from my OneNote tracking page. Thanks!

Removing the patch-approved label...


New Project - Basic Calculator [GSSoC'23]

Describe the project you want to add with tech stack
I want to add a project Basic Calculator. The tech stack is - HTML, CSS and JavaScript.
Screenshots (optional)

Hi there! I'm excited to contribute to this project for GSSOC'23, Please assign it to me.

Hi mentors ,I have made the basic calculator using html ,css , js. I want  to contribute to this projects.Please assign it to me.

I AM VERY EXCITED TO CONTRIBUTE ON THIS ISSUE,PLEASE MENTORS ASSIGN THIS ISSUE TO ME.


[Feature Request]:  Hover Enhancement of button

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
User Engagement
Use Case
user attention
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

reupload the screenshot, it is not visible

If you are talking about explore now button then an animation is being added to it in another issue.

its added but not visible after even hover we have zoom it to see as the border is very thin.

its added but not visible after even hover we have zoom it to see as the border is very thin.

sure go ahead just make sure no conflicts with #397


fix: Widget QA Items GRO-722

This PR is a series of small updates based on QA feedback. Here's the before/after:

before

after

In terms of the code this is nearly all visual stuff but there is ONE behavior change: the editorial widget no longer rotates through its items as the day goes by. I thought this rotation was a good idea because it would make the widget feel fresh but I failed to consider that each item has a date associated with it.
If you have the large editorial version installed then it starts the day like this:
* Article A / Dec 4
* Article B / Dec 3
* Article C / Dec 2
* Article D / Dec 1

Newest article on top and then in descending order. As these things rotate you end up with things like this:
* Article C / Dec 2
* Article D / Dec 1
* Article A / Dec 4
* Article B / Dec 3

So two rotations have happened and now the order is out of wack. Better to just update less often (once a day) and keep the order consistent.
https://artsyproduct.atlassian.net/browse/GRO-722
/cc @artsy/grow-devs @brainbicycle @kathytafel

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against e485b734ab6f67e35532550178d1522553de742d


Allow custom timeout for retry function

Add a field in config.json to configure the timeout for retryFunction: https://github.com/claabs/epicgames-freegames-node/blob/8211720629c6033b24db340abddff2dbcaba6f6b/src/common/puppeteer.ts#L122
The problem linked to this request:

+1 vote for this feature enhancement.
I am running epicgames-freegames-node docker container on Synology NAS (218+) and was frequently running into 15000ms timeout limit: browser launch did not work after 15000ms.
I expected I was having some sort of compatibility issue with the NAS environment...
Turns out, other Docker containers with high CPU prioritity running in parallel were messing drastically with epicgames-freegames-node.
This was not so obvious, since when the system is "idling" at 30-50% CPU usage with other Dockers active. The expectation was, this would be plenty of resources left, but this is not the case... It was enough to mess with epicgames-freegames-node.
Higher timeout value could do the trick.

Added browserLaunchTimeout and browserLaunchRetryAttempts.