Compare & Contrast Darviz with Barista https://www.uni-muenster.de/PRIA/Barista/

As a graphical tool for Deep Learning Could You Compare the Features and Limitations of Darviz vs. the Barista project for Cafee out of Muenster

@laefsky the quick point would be that Barista is meant as a graphical tool only for the Caffe library
The deep learning IDE that we designed is library agnostic. It acts as graphical front ending tool for Caffe, Keras, Tensorflow, and PyTorch.
You can find more information here: https://dataplatform.cloud.ibm.com/docs/content/analyze-data/ml-canvas-nnd-intro.html


Y value no longer overwritten

Previously, the y value would simply get overwritten when using a non-standard vertical alignment, making it impossible to offset anything bottom or center aligned.

@kenning please provide a test case or an example of what this fixes

closing in favor of #595

Released in v0.5.0


Removed .v extension from verilog and added to v

The .v extension was used by Verilog and not Vlang. I removed this from verilog.yaml and added to v.yaml

Verilog having precedence over V is intended since it is more widely used.
However, you can mark V to take precedence over Verilog in your settings file:
{
    "*.v": {
        "filetype": "v"
    }
}


kubeadm: revisit the "Network setup" section post-feedback

In a early note explain that there could be multiple default gateways on a host.
Do not have 1 note, 1 warning, then other note.
Leave the warning that the "custom IP" setup is not recommended at the end of the section.

follow up on https://github.com/kubernetes/website/pull/43872#pullrequestreview-1744902982

/sig cluster-lifecycle
/assign @sftim
PTAL for LGTM/approve


Feature: Cache icons

Describe your Idea
Everytime you GET /:id/icon or /:id/banner, a request is sent to discord and this slows the response time massively.

fixed by #19


Added torrent magnet links to downloads page

Torrent icon for downloads page is missing.
Hashes are same, not changed.
New PGP signed hashes.txt should be created with torrent hashes.

Monero GUI magnet link: magnet:?xt=urn:btih:706beb780e3e8a4e1c7a3a76328a37bb125e1ae1&dn=MoneroGUI-<IP_ADDRESS>-Oxygen-Orion&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce
Monero CLI magnet link: magnet:?xt=urn:btih:ebe3bb8119d02ed05fa8c699fd11c964f6aab32f&dn=MoneroCLI-<IP_ADDRESS>-Oxygen%20Orion&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce
If something missing tell me so i can (try) fix.
Closes #1629

The link doesn't appear on the mobile website

@erciccione am i missing something? What is the reason for don't? Verification and maintaining quite easy.

This would have to be done by the core team, otherwise it's a mess every time we update new versions and the torrent stays outdated.

@HardenedSteel What erciccione meant with styling is that this looks broken on the website, missing icon and also wrong position.

Also just to clarify, would this be a torrent for all operating systems?

@selsta Wrong position because there's no icon for torrent, also yes it's torrent for all operating systems.


Change click event to mousedown as event was triggering twice

Well, this problem appears only on the page with more than one calendar and if one of them with inline mode.
Like on demo page https://wakirin.github.io/Lightpick/
That is happened because for inline mode the listener for document click is always alive.
Also, replace the event click with the event mousedown doesn't help here.
So, I don't see any reason for PR.
Thanks.

Actually click and mousedown also changes the style behaviour. Bootstrap, Foundation etc...
With click there is no border and input is not focused:

With mousedown border is visible and input has focus therefore you can write date manually:


Incorrect latest version published on NPM

Description:
6.0.0-beta version of the diff package has been published as the latest version on npm. This seems to be a mistake as beta versions are typically not intended to be the latest stable release.
Details:

Package Name: diff
Current Latest Version on npm: 6.0.0-beta
Expected Latest Version: Should be the latest stable version, which is typically not a beta release.

Steps to Reproduce:

Visit the npm package page for diff.
Observe that 6.0.0-beta is listed as the latest version.

Expected Behavior:
The latest stable version should be published as the latest version on npm, not a beta release.

Resolved by pushing 6.0.0 - and I've learned about tagging releases, for next time!


[Bug] snarkOS 1.3.15 crash

🐛 Bug Report

(Write your description here)
snarkOS 1.3.15 crash after 1 day work
Steps to Reproduce

Step 1...
Step 2...
Step 3...

sync from zero
(code=exited, status=134)
SIGABRT
Expected Behavior

(Write what you expected to happen here)
Your Environment

 1.3.15

 1.54.0

 Ubuntu 20.04.2 LTS

Thank you for reporting this issue. Did you perchance save the logs when this happened? I'm assuming you were running a miner (--is-miner) with the default configuration?

node mode (without --is-miner)
Welcome to Aleo! We thank you for running a network node and supporting privacy.
Starting a client node on testnet1.
Sep 17 07:04:01.446  INFO snarkos: Loading storage at '~/.snarkOS/snarkos_testnet1'...
Sep 17 07:04:01.447 TRACE snarkos_storage::storage::async_adapter: received storage request: Canon()
Sep 17 07:04:01.447  INFO snarkos: Storage is ready
Sep 17 07:04:01.447 DEBUG snarkos: Loading Aleo parameters...
Sep 17 07:04:01.571  INFO snarkos: Loaded Aleo parameters
Sep 17 07:04:01.609  INFO snarkos: Loading Ledger
Sep 17 07:04:01.609 TRACE snarkos_storage::storage::async_adapter: received storage request: GetLedgerDigests()
Sep 17 07:04:01.938 TRACE snarkos_storage::storage::async_adapter: received storage request: GetCommitments()
Sep 17 07:04:02.488 TRACE snarkos_storage::storage::async_adapter: received storage request: GetSerialNumbers()
Sep 17 07:04:03.042 TRACE snarkos_storage::storage::async_adapter: received storage request: GetMemos()
Sep 17 07:04:03.546  INFO snarkos: Initializing Ledger
Sep 17 07:04:13.072  INFO snarkos: Loaded Ledger
Sep 17 07:04:13.073 TRACE snarkos_storage::storage::async_adapter: received storage request: Canon()
Sep 17 07:04:13.073 TRACE snarkos_storage::storage::async_adapter: received storage request: Canon()
Sep 17 07:04:13.073 TRACE snarkos_storage::storage::async_adapter: received storage request: GetBlockDigestTree(7470f24eea85e296b1cac1f94da99c3ec2fff6dd059302c462affb95074c7fa4)
Sep 17 07:04:13.083 DEBUG snarkos_network::node: Initializing metrics
Sep 17 07:04:23.556 TRACE snarkos_storage::storage::async_adapter: received storage request: Canon()
Sep 17 07:04:23.556 DEBUG snarkos_consensus::consensus::inner::commit: Attempting to canonize the descendants of block at height 137634.
Sep 17 07:04:23.556  INFO snarkos_network::inbound::inbound: Initializing listener for node (ce32b8eeff0079f6)
Sep 17 07:04:23.556  INFO snarkos_network::inbound::inbound: Listening for nodes at <IP_ADDRESS>:4131
Sep 17 07:04:23.556  INFO snarkos_network::node: Updating peers
Sep 17 07:04:23.556  INFO snarkos_network::peers::peers: Connected to 0 peers

This was fixed by #1159, release planned for today.


transfers: verify TEL and WEB reoccurring transfers are rejected

Just verifying the errors returned match what we expect.
Issue: https://github.com/moov-io/paygate/issues/164

Codecov Report

Merging #165 into master will decrease coverage by 3.48%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
- Coverage   56.35%   52.86%   -3.49%
==========================================
  Files          27       27
  Lines        3700     3700
==========================================
- Hits         2085     1956     -129
- Misses       1198     1344     +146
+ Partials      417      400      -17

Impacted Files
Coverage Δ

accounts.go
10.95% <0%> (-69.87%)
:arrow_down:

internal/database/mysql.go
31.25% <0%> (-42.5%)
:arrow_down:

ofac.go
38.65% <0%> (-35.3%)
:arrow_down:

file_transfer_configs.go
55.67% <0%> (-1.04%)
: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 f152f4b...540fe9a. Read the comment docs.


Met the bug "frozen class" when configured the telemetry for backend

I met the bug "frozen class" when configured the telemetry for backend. The version of SkyWalking is 8.1.0, CentOS7 and jdk 1.8.

My configuration was according to the docs (https://github.com/apache/skywalking/blob/35264e6171b7a5c675d4fdf42645dae4caa5a31c/docs/en/setup/backend/backend-telemetry.md), I don't know where is the problem?

Try the latest.


Parse url to state in ui-route 1.x for angular 1.x

Hi,  I found this comment  - "Nope, can't think of a way to do this, sorry (although it'll be possible in the new 1.0 version we're working on)." in https://github.com/angular-ui/ui-router/issues/2166
This feature has already been implemented?

This should do the trick:
$state.get().filter(state => state.$$state().url.exec(currentUrl));

$$state() allows you to access the internal state, which has a UrlMatcher on it
https://ui-router.github.io/docs/latest/classes/state.state-1.html#url
https://ui-router.github.io/docs/latest/classes/url.urlmatcher.html#exec

@christopherthielen Is it safe to access the internal state? If so, that would mean that "internal" API is locked down, correct? (or rather, it will be >= 1.0.0 and < 2.0.0, as per semantic versioning)
eslint-plugin-angular /w eslint-config-angular is warning me that "Using $$-prefixed Angular objects/methods are not recommended"  (rule name is angular/no-private-call), which generally makes sense assuming that $$-prefixed objects/methods are generally private. Is this the case here? (i.e. is it private?)
Does it make sense to have a way to get states from urls, using a public method, rather than private/internal one?
Thanks

@mattbrunetti we make no guarantees about internal API.  They can change at any time, regardless of semver.  That said, I think the $$state().url is not likely to change any time soon.

public method
Yes, but it's not high on the list of priorities

@graingert thanks! Your $urlService.match approach worked to match all my routes, including nested ones.
The UrlMatcher.exec approach above was only able to match top level routes (having a root-relative url).


Fail cylc validate on improper periodicity

Currently the workflow misses tasks if CSET_INCREMENTAL_OUTPUT is enabled, and the workflow duration is not an integer multiple of the output period. This is documented, but is easy to overlook, and it would be better if it caused cylc validate to fail.
This can be done by asserting within jinja, as shown in this example.

No longer an issue as of #765.


Consume remote jenkins library and remove local library from this repo

Is your feature request related to a problem? Please describe
Since the we are in process of migrating the jenkins libraries, the jenkinsFiles in build and any other repositories should consume the remote library now.
Example:
lib = library(identifier<EMAIL_ADDRESS>retriever: modernSCM([
    $class: 'GitSCMSource',
    remote: 'https://github.com/opensearch-project/opensearch-build-libraries.git',
]))

Describe the solution you'd like
Consume remote libraries one by one and then remove the old code base from here.
Describe alternatives you've considered
No response
Acceptance Criteria

Below jenkins file should consume remote libraries instead of local:
All the upstream libraries should be removed from this repo to avoid duplicity.

[x] check-for-build.jenkinsfile
[x] cross-cluster-replication/perf-test.jenkinsfile
[x] opensearch-dashboards/integ-test.jenkinsfile
[x] promotion/promote-docker-ecr.jenkinsfile
[x] data-prepper/release-data-prepper-all-artifacts.jenkinsfile
[x] opensearch-maven-release/maven-sign-release.jenkinsfile
[x] promotion/promote-yum-repos.jenkinsfile
[ ] docker/docker-build.jenkinsfile
[x] opensearch-ruby/opensearch-ruby.jenkinsfile
[x] release-notes-check/release-notes-check.jenkinsfile
[x] docker/docker-copy.jenkinsfile
[x] opensearch/bwc-test.jenkinsfile
[x] release-tag/release-tag.jenkinsfile
[x] docker/docker-scan.jenkinsfile
[x] opensearch/distribution-build.jenkinsfile
[x] rpm-validation/rpm-validation.jenkinsfile
[x] gradle/gradle-check.jenkinsfile
[x] opensearch/integ-test.jenkinsfile
[x] sign-artifacts/sign-standalone-artifacts.jenkinsfile
[x] opensearch-dashboards/bwc-test.jenkinsfile
[x] opensearch/perf-test.jenkinsfile
[ ] vulnerability-scan/whitesource-scan.jenkinsfile
[x] opensearch-dashboards/distribution-build.jenkinsfile
[x] promotion/promote-artifacts.jenkinsfile

We have moved to remote libs now!


Feat: Add toE8s to TokenAmountV2

Motivation
Support formatting e8s for tokens that have different decimals than 8.
Changes

Add method toE8s to TokenAmountV2.

Tests

Add tests for new method.

Todos

[x] Add entry to changelog (if necessary).

@dskloetd please review


Build go binaries without QEMU

Go already can cross-build easily for other architectures, so using QEMU is quite a bit slower.
Here I've changed the Dockerfile to use the --platform arg for FROM and tell Go what ARCH to build for.
I've also switched the build to use buildx bake which will run all the builds in parallel.  Bake doesn't work directly with a Dockerfile, so I created a quick docker-compose.yaml file for it to use.
This builds all the images in about 2 minutes.
Also, there seems to be a bug with calling '${GITHUB_SHA::8}'  maybe you want to remove the ::8 but I didn't want to change it, not sure what it was there for.

Introducing the docker-compose will add a little bit complexity for those who build manually. So keep it simple, though it will waste a little time.

It will still build as before without compose with the updated Dockerfile.  Just a lot faster.


catch when a new PR would not introduce any changes and stop before reaching out to GitHub

For some reason, GitHub's API errors out with an authentication error (which makes no sense at all) when you attempt to open a PR against a branch that does not introduce any changes to the branch being merged into.
Harmony should check for this situation before reaching out to GitHub so it can provide a more user-friendly error.

I've now got harmony outputting a better error message when GitHub fails to create a PR due to there being no changes on the branch so I am going to close this issue as no longer worth doing inside of harmony.


Blobrunner64.vm Fails Due to Checksum mismatch

What's the problem?
This is the error message that I receive:

I did a sha256 on the file and got the following result, which confirms the mismatch:

Thank you for your help with this issue btw!
Steps to Reproduce

Run the install.ps1 file after a few system restarts, it will have an issue running blob runner and state that the download failed due to a checksum mismatch.

Environment
-Virtualization software: VIrtual Box
-VM OS version: 10.0.19045
-VM Powershell Version 5.1.19041.1682
-VM Chocolatey version: 2.2.2
-VM Boxstarter version: 3.0.3
Additional Information
No response
Detected by test suite
No

Hello @Rebeccad316! Thank you for the report.

I am seeing that in your first screenshot, it looks like the download for blobrunner64 may have been blocked based on the comment: Unhandled Exception: System.IO.IOException: Operation did not complete successfully because the file contains a virus or potentially unwanted software

Do you by chance still have Windows Defender running or not fully disabled?
When I attempt to download blobrunner64, I do get an issue that "this file may contain a virus or potentially unwanted software" (as seen in the screenshot below).

The sha256 checksum that you ran for blobrunner in your second screenshot is for the 32 bit version of the program, which is called blobrunner as opposed to blobrunner64, which matches the checksum here: https://github.com/mandiant/VM-Packages/blob/main/packages/blobrunner.vm/tools/chocolateyinstall.ps1#L8

Downloading blobrunner64 and running a sha256 checksum on it, I do get the proper checksum as noted here: https://github.com/mandiant/VM-Packages/blob/main/packages/blobrunner64.vm/tools/chocolateyinstall.ps1#L8

@Rebeccad316 has @emtuls' answer help resolving the problem? can we close this issue?

Hello Ana,
Yes the issue can be closed. I was able to get a proper checksum thanks to
emtuls remarks.
Thank you again for your help,
-Rebeca
On Mon, Feb 5, 2024, 8:44 AM Ana María Martínez Gómez <
@.***> wrote:

@Rebeccad316 https://github.com/Rebeccad316 has @emtuls
https://github.com/emtuls' answer help resolving the problem? can we
close this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/mandiant/VM-Packages/issues/874#issuecomment-1927045523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMONQVKDYAW43NFL6XLDKZTYSDO45AVCNFSM6AAAAABCO3FHGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRXGA2DKNJSGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Bug: cant get defineExpose data which nested in component

I have the component named Collapse and child component named CollapseItem
and the CollapseItem has the defineExpose
// CollapseItem.vue
<script setup lang="ts" >
const isActive = computed(() =>
  collapse?.activeNames.value.includes(props.name),
)
defineExpose({
  isActive,
})

Describe the bug

// I register `collapse-item` in the global
import {config,mount} from '@vue/test-utils'
import {Collapse,CollapseItem} from 'xxx'
config.global.stubs = {
	CollapseItem,
}
const wrapper = mount(Collapse,{
	props: {
		activeNames: ['1']
	},
	slots: {
		default:`
          <collapse-item name="1" title="title1">111</collapse-item>
          <collapse-item name="2" disabled>222</collapse-item>
        `,
	}
})
const vm = wrapper.vm
const collapseWrapper = wrapper.findComponent(OCollapse)
const collapseItemWrappers = collapseWrapper.findAllComponents(
  OCollapseItem,
) as VueWrapper<CollapseItemInstance>[]

// BUG there is fail, `isActive` is not in vm
expect(collapseItemWrappers[0].vm.isActive).toBe(true)

the child component CollapseItem is just get props

To Reproduce

Expected behavior

Related information:

@vue/test-utils version: ^2.1.0
Vue version: ^3.2.41
node version: v16.14.2
npm (or yarn) version: 8.15.0
pnpm version: 7.13.4

Additional context

Hi @priority3
Can you make a small online repro so we can take a look? https://stackblitz.com/edit/vitest-dev-vitest-ledp6h?file=package.json&initialPath=vitest

Hi @priority3
Can you make a small online repro so we can take a look? stackblitz.com/edit/vitest-dev-vitest-ledp6h?file=package.json&initialPath=__vitest__

oh, thanks for your reply,I had found that maybe this is my bad in coding by test

Hi @priority3
Can you make a small online repro so we can take a look? stackblitz.com/edit/vitest-dev-vitest-ledp6h?file=package.json&initialPath=__vitest__

oh, thanks for your reply,I had found that maybe this is my bad in coding by test

@priority3 What did you do to fix/change/workaround this, as I have hit the same issue that doing:
defineExpose({ videoRef })

and then using:
wrapper.vm.videoRef

No longer works

I think I know what's going on: there is a breaking change in Vue core v3.2.45, and we need to release a new version of VTU to work around it (see #1858 ).
You can stay on v3.2.44 if you are encountering this issue with VTU v2.2.1

Hi @priority3
Can you make a small online repro so we can take a look? stackblitz.com/edit/vitest-dev-vitest-ledp6h?file=package.json&initialPath=__vitest__

oh, thanks for your reply,I had found that maybe this is my bad in coding by test

@priority3 What did you do to fix/change/workaround this, as I have hit the same issue that doing:
defineExpose({ videoRef })

and then using:
wrapper.vm.videoRef

No longer works

@spacedawwwg , it's strange that I make the mini repo , but it's work fine.🤔

@priority3 Your repro is accurate: it fails if you use Vue 3.2.45 😉

@priority3 Your repro is accurate: it fails if you use Vue 3.2.45 😉

oh, I applied the corresponding version of vue(^3.2.44) and vtu(^2.2.1), but same error, let me find the way to reproduce it.🤒

We released VTU v2.2.2 which should help with people encountering an issue with defineExpose and Vue v3.2.45


Align Punk and Blockie

This PR aligns the elements to the middle with flex, this seems a lot cleaner to me than the previous pixel calculations.
The Punk image used to be a little bit bigger, the Blockie and the Punk should be the same size imho, this is how we show it on app.buidlguidl.com as well.

Rebased and resent here:
https://github.com/scaffold-eth/punk-wallet/pull/61


browser (documentation): dialogs and states (ask, qnaDoc)

Added documentation for the allTags, contributor, and login dialogs. Also for the ask and qnaDoc states.
NOTE: these changes are updates to JS comments only. (Adding comments to the HTML caused issues with the unit tests in a previous commit/PR https://github.com/marklogic/marklogic-samplestack/pull/556. Avoiding that here.)
This can replace https://github.com/marklogic/marklogic-samplestack/pull/556

Please go ahead with the check-in Thanks


Refactor to remove STRLEN() calls

I have added a new structure to store key (int)/value (string) pairs for use in static lookup tables (eg event names, regexp character classes, special keywords, highlighting). This structure embeds the length of the string which allows removal of calls to STRLEN() when performing the lookup comparisons.
In addition to factoring out calls to STRLEN(), I have added a simple circular FILO caching mechanism to some lookup functions with the goal to speed them up.
To test the effectiveness of the caching I added some counters to the function event_name2nr() in autocmd.c. Running ./vim autocmd.c on my HP-UX build without the cache the main lookup loop was executed 35182 times. With the cache, the cache loop was executed 5796 times and the main lookup loop was executed 282 times (total 6078). This is a reduction of 29104 executions.

I think I now know how you cam rebase this PR:
git remote add upstream https://github.com/vim/vim.git
git fetch upstream
git rebase upstream/master


Rt with infection feedback

This PR:

[x] Creates the InfectionsWithFeedback latent module.
[x] Adds the new module pyrenew.datautils for common data management operations.
[x] Adds the tutorial extending_pyrenew.qmd
[x] Corrects the order of outputs from the sample_infections_with_feedback function.
[x] Adds tests modules for InfectionsWithFeedback and pyrenew.datautils.

DRAFT --- STILL WORKING ON IT ---
@dylanhmorris, 219e710 fixes the failing tests. I had to introduce two changes:

Make sure the output from latent.Infections.sample() is at least 1 dimension (link).
Pad the sampled I0 within model.RtInfectionsRenewalModel.sample() to match the generation interval (link).

This introduced a couple of other changes:

It seems it solved a bug part of the "ghost outbreak." In the case of the infections function, before your changes, the conv scanner was using jnp.dot() to multiply an array with a scalar. Compare these two images, this is what we have in main:

versus the PR

Ping to @dylanhmorris @damonbayer and @AFg6K7h4fhy2. This is ready!

The website was not rendering b/c scalars 60dfec4 required feedback to be arrays, not scalar. So I introduced a couple of changes that should make the code more robust:

-[x] Uses jax.numpy.atleast_1d() for DeterministicRV.sample() (so scalars are coerced into 1d arrays)
-[x] Uses jax.numpy.atleast_1d() for DistributionalRV.sample() (so scalars are coerced into 1d arrays)

cc @dylanhmorris

Update: needs conflicts resolved @damonbayer. Can you do and request re-review from me?


feat(rust_indexer): Add support for communicating with the analyzer driver

This PR adds support to the Rust indexer to communicate with the analyzer driver. This includes support within the indexer library and a new binary to continuously process compilation units.

You probably want to setup the git commit hooks (from https://www.kythe.io/contributing/) so you can get the lint warnings earlier.

Since this is a fatal error, shouldn't the indexer simply die, which will be detected by the proxy?

On Jul 15, 2021 at 21:42,  <Jay Sachs @.***)>  wrote:
@jaysachs  commented on this pull request.
In  kythe/rust/indexer/src/bin/proxy/main.rs (https://github.com/kythe/kythe/pull/4985#discussion_r670960974):

path::{Path, PathBuf}, +}; +use tempdir::TempDir; + +fn main() ->  Result<()>  { + let mut file_provider = ProxyFileProvider::new(); + let mut kythe_writer = ProxyWriter::new(); + let mut indexer = KytheIndexer::new(&mut kythe_writer); + + // Request and process + loop { + let unit = request_compilation_unit()?; + // Retrieve the save_analysis file + let temp_dir = TempDir::new("rust_indexer").context("Couldn't create temporary directory")?; + let temp_path = PathBuf::new().join(temp_dir.path()); + write_analysis_to_directory(&unit,  &temp_path,  &mut file_provider)?;

So if this fails  &  returns (or the  TempDir::new) we don't write "done" back to the proxy, and so the conversation will be out of sync.
—
You are receiving this because you authored the thread.
Reply to this email directly,   view it on GitHub (https://github.com/kythe/kythe/pull/4985#pullrequestreview-708001593), or   unsubscribe (https://github.com/notifications/unsubscribe-auth/APPKRXLTKTTIOWY23HSZTEDTX62CVANCNFSM5AMPV4DA).


[CHALLENGE SUBMISSION] Challenge 7 quema del diablo in PowerShell Core

Please provide the following information for your submission:
What is your name? (First, Last)
Olivier Miossec
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/omiossec/25-days-of-serverless-omc/tree/master/7-12
What Challenge is this for? (Challenge number between 1 and 25)
7
(Optional) Anything else we should know? e.g., language used, location, blog post?
PowerShell, Paris (France), https://dev.to/omiossec

From all of us on the Cloud Advocacy team at Microsoft, thank you @omiossec for creating this issue!
Have a Happy Holiday season!

We checked out your repository. We're thrilled to say your solution is now listed in our Hall of Fame
Thank you for your contributions!
This issue is now resolved! 🎉


Seems to stuck in "Fetching sprite image"

Just tried the link "https://harveyslash.github.io/TSNE-Embedding-Visualisation/" and found that it is stuck in the "Fetching sprite image ..." stage. Any hint or suggestion?

It takes a while to download. The file size is quite large (about 90 mb)
i just tested it on browser and it works


Add payment method types

Add the ability to set the payment method types in the settings

This can be controlled from within the Stripe dashboard:
https://stripe.com/docs/payments/payment-methods/overview


Add time locks to the Vault

Feature Description
The user should be able to add time locks to the Vault. This means that the bitcoin in the Vault is not spendable even if you have all the keys unless the specified amount of time has passed.
**Pre-requisites/ dependencies
-Designs
-Research
-Discussion with a Senior
**Task Break Down
-TASK 1
-TASK 2
**Test Cases
**Design
**Flow
**ERD

Being done as part of Miniscript implementation, closing as outdated


What is meant by SWOT analysis?

Is it for the project or the factors affecting the project?

SWOT is a strategic planning tool used to evaluate the strengths, weaknesses, opportunities, and threats to a project.
The SWOT analysis is an important part of the project planning process:

Strengths: attributes of the organisation that help achieve the project objective.
Weaknesses: attributes of the organisation that stop achievement of the project objective.
Opportunities: external conditions that help achieve the project objective.
Threats: external conditions that could damage the project.

Here's an example


add:Kshitij Shrivastava

Description
Added new dev profile
Related Issues
#308
Changes Proposed

Added a new "idevkshitij" json file with profile details.
Added the new filename in "ProfileList.json" array.

Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@idevkshitij Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and Star the repo to help us grow even further!


Use dynamic addresses in libvirt

Why is this PR needed?
Existing terraform configuration for libvirt assigs fixed addresses to instances. This prevents multiple clusters to be deployed on the same network, as described in https://github.com/SUSE/avant-garde/issues/1297
What does this PR do?
Modifies terraform files to use addresses dynamically assigned by the network using dhcp.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

@davidcassany the changes are quite straightforward: instead of assigning a fixed ip address with the cirdhost function the address dynamically assigned by libvirt is used.
This PR should run in the kvm pipeline  https://ci.suse.de/job/caasp-jobs/job/v4/job/pr/job/test-libvirt/view/change-requests/job/PR-1042/

libvirt tests keep failing for this PR. The observed sympton is that cloud init fails in some nodes.
In testrunner's output we can see this message:
2020-04-17 10:34:20 ERROR]
Error: error executing "/tmp/terraform_1078826367.sh": Process exited with status 1
2020-04-17 10:34:20 ERROR] Error: error executing "/tmp/terraform_1078826367.sh": Process exited with status 1

Unfortunately, the message doesn't indicate which node failed, so every node must be checked. Using the ip address from tfout.json  the following command is used to identifie the nodes:
ssh -i id_shared sles@<ip address> cloud-init status
status: error

When looking at the '/var/log/cloud-init.log` in the failed node(s) we can see this message:
cloudinit.util.ProcessExecutionError: Unexpected error while running command.
Command: ['/var/lib/cloud/instance/scripts/runcmd']
Exit code: 106

The failed script /var/lib/cloud/instances/scripts/runcmd  is:
#!/bin/sh
'zypper' '-n' 'install' 'kernel-default' '-kernel-default-base' 'ca-certificates-suse'

Also from /var/log/cloud-init-output.log we find the following messages which are not shown in the nodes that complete the cloud-init successfully:
Repository 'basesystem_pool' is invalid.
[basesystem_pool|http://download.suse.de/ibs/SUSE/Products/SLE-Module-Basesystem/15-SP1/x86_64/product/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'basesystem_pool' because of the above error.

Notice that the url for the repo is the same in the nodes which complete the cloud-init successfully.

In order to validate if the repository is reachable at the moment of the zypper update, the following command was added to the cloud-init: curl -v http://download.suse.de/ibs/SUSE/Products/SLE-Module-Basesystem/15-SP1/x86_64/product/repodata/repomd.xml
As can be seen below, even when the curl command successfully retrieves the content from the repository, the zypper command fails:

click to see full output
* TCP_NODELAY set
* Connected to download.suse.de (<IP_ADDRESS>) port 80 (#0)
> GET /ibs/SUSE/Products/SLE-Module-Basesystem/15-SP1/x86_64/product/repodata/repomd.xml HTTP/1.1
> Host: download.suse.de
> User-Agent: curl/7.60.0
> Accept: */*
>
< HTTP/1.1 200 OK
< date: Fri, 17 Apr 2020 13:53:13 GMT
< server: Apache/2.4.41 (Linux/SUSE)
< last-modified: Sat, 25 May 2019 19:04:04 GMT
< etag: "239b-589bafa8cb100"
< accept-ranges: bytes
< content-length: 9115
< content-type: text/xml
<
{ [3810 bytes data]
<?xml version="1.0" encoding="UTF-8"?>
<repomd xmlns="http://linux.duke.edu/metadata/repo" xmlns:rpm="http://linux.duke.edu/metadata/rpm">
  <revision>1558811030</revision>
  <tags>
    <repo>obsproduct://build.suse.de/SUSE:SLE-15-SP1:GA/sle-module-basesystem/15.1/x86_64</repo>
  </tags>
  <data type="primary">
    <location href="repodata/d2d1c47b7f3f0329b27581e1c5363cb49bf7c0ef137ced0ac5e9291e2db7d989-primary.xml.gz"/>
    <checksum type="sha256">d2d1c47b7f3f0329b27581e1c5363cb49bf7c0ef137ced0ac5e9291e2db7d989</checksum>
    <timestamp>1558811030</timestamp>
    <size>1393683</size>
    <open-size>10046555</open-size>
    <open-checksum type="sha256">332131a7325407ccffdec721bcb59a74a83fbdb5532d365b239bc1a3f4d5f2a5</open-checksum>
  </data>
     .
     .
     .
</repomd>

Retrieving repository 'basesystem_pool' metadata [.error]
Repository 'basesystem_pool' is invalid.
[basesystem_pool|http://download.suse.de/ibs/SUSE/Products/SLE-Module-Basesystem/15-SP1/x86_64/product/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.

Probably unrelated, but the cloud-init includes the following boot commands:
bootcmd:
  - ip link set dev eth0 mtu 1400
  # Hostnames from DHCP - otherwise localhost will be used
  - /usr/bin/sed -ie "s#DHCLIENT_SET_HOSTNAME=\"no\"#DHCLIENT_SET_HOSTNAME=\"yes\"#" /etc/sysconfig/network/dhcp
  - netconfig update -f

In all the nodes, the DHCLIENT_SET_HOSTNAME is set to 'YES', however, in all the failing nodes the actual value of the hosname is localhost while in the other nodes is set properly from dhcp.

Probably unrelated, but the cloud-init includes the following boot commands:
bootcmd:
  - ip link set dev eth0 mtu 1400
  # Hostnames from DHCP - otherwise localhost will be used
  - /usr/bin/sed -ie "s#DHCLIENT_SET_HOSTNAME=\"no\"#DHCLIENT_SET_HOSTNAME=\"yes\"#" /etc/sysconfig/network/dhcp
  - netconfig update -f

In all the nodes, the DHCLIENT_SET_HOSTNAME is set to 'YES', however, in all the failing nodes the actual value of the hosname is localhost while in the other nodes is set properly from dhcp.

I see not direct relation to the issue we are facing here, however I am pretty convinced that the DHCLIENT_SET_HOSTNAME configuration has no effect with the current setup. Libvirt DHCP server does not know which hostname should be providing for each client, thus it just provides the hostname announced by the client, which is localhost. Libvirt is not configured to provide dynamic hostnames, so this DHCLIENT_SET_HOSTNAME doesn't make much sense here IMHO.
As far as I know libvirt cannot be configured to provide dynamic hostnames by using the standard network XML config file. However it has the possibility to add additional namespace on network configuration to by pass options to the underlying dnsmasq service (pure bypass no validation at all). I am trying to figure out how to force dnsmasq to provide dynamic hostnames.

I see not direct relation to the issue we are facing here, however I am pretty convinced that the DHCLIENT_SET_HOSTNAME configuration has no effect with the current setup

This is wrong, libvirt is capable to do so. Adding a small sleep broke some race condition and hostname is properly set. Looks like there is a race condition between the setup of the client hostname from DHCP (or some other network related stuff) and clout-init.

What is this waiting for ?


Occasionally Ingress Controller introduces significant delays in process ingress events

Describe the bug
Occasionally, when we modify the Ingress resource it takes to the order tens of minutes to update the Application Gateway configuration through ARM.
To Reproduce
Start a Kubernetes service. Expose it through the Application Gateway by creating an Ingress resource. Scale the service up or down, or remove the Ingress resource completely and observe the time it takes to apply this configuration on the Application Gateway. Most of the time the update would go through within a matter of seconds, but occasionally it will take to order tens of minutes to get applied.
Ingress Controller details

Output of kubectl describe pod <ingress controller> . The  pod name can be obtained by running helm list.
Output of `kubectl logs .
will add the logs here shortly.
Any Azure support tickets associated with this issue.

This issue could be related to:
https://github.com/Azure/AKS/issues/522

This is somewhat related to the resync period. It happens when the informer misses events.

This is somewhat related to the resync period. It happens when the informer misses events.

@njzhangyifei why would the informer miss events?

Looks like the work around mentioned in this issue should resolve this problem till it fixed in AKS itself:
https://github.com/Azure/AKS/issues/676

@akshaysngupta could you take this on? This can be an extension of your helm work for enabling RBAC.


Clear trajectory buffer on E-stop

Hi, thanks for making fanuc_driver_exp public, it is very helpful!
I ran into issue #4 here and tried to solve it myself. This change only responds to emergency-stop buttons, not other errors. I'm still quite new to Fanuc and Karel etc so I wanted to limit my changes.
I also added ACC66 to ros_movesm.ls because the robot motion was too jerky for us.
My e-stop handler routine is just a copy of the stop-request handling code, but since that referred to a local variable in a function, I made that a global variable so my new function could set it. That doesn't necessarily seem like good software engineering to me, but again I'm pretty new to Karel.
If you have suggestions how to do it better, I can test them on the Fanuc in our lab if that's helpful.
Thanks again!

If you have suggestions how to do it better, I can test them on the Fanuc in our lab if that's helpful.

Thanks for the offer. For now, I would be interested to know what model robot you have in your lab.

Btw @hersh: none of the commits you've made are contributed to your github account. Not sure whether you'd want to fix that?

Thanks for mentioning. I was using my work email when doing this. I appreciate your comments, hopefully I'll have time to address them soon.

@hersh: I've pushed some commits. These address the few comments I had.
Could you check the attribution of your commits? It'd be ok if you squash everything into a single commit and force push.

I'm sorry for changing your copy of ros_movesm btw (removed the ACC66). As you didn't use a branch I had to push to your master.

Thanks for doing all the work for me! I don't care about the attribution, I'm ready to leave it as is. :)
If it causes trouble for you, let me know and I'll fix it.
I'm surprised you had permissions to push to my "master", but I'm glad you fixed the problems. :)
Thanks a bunch.

I will also add that this does not seem to be a total solution to the problem. Many times it does seem to clear the queued motion and sit still when I re-start the Fanuc program, but occasionally it starts moving again anyway. Maybe there are different places where trajectories would be stored? I don't know what else to try.
We have a Fanuc R1000iA-80F arm with the R30iB controller.

@hersh wrote:

I'm surprised you had permissions to push to my "master", but I'm glad you fixed the problems. :)

Allowing changes to a pull request branch created from a fork.

Thanks for doing all the work for me! I don't care about the attribution, I'm ready to leave it as is. :)

Ok.

I will also add that this does not seem to be a total solution to the problem. Many times it does seem to clear the queued motion and sit still when I re-start the Fanuc program, but occasionally it starts moving again anyway.

Yes, I still have to do some checks with real hw. The list is really the only place incoming trajectories are stored, but ros_movesm also caches one point. I'll need to verify the interaction between ROS_TRAJ and ros_movesm in case of e-stops and programs being paused.
I'd also like to make this more generic, so it will clear the list upon any error.

@hersh wrote:

Many times it does seem to clear the queued motion and sit still when I re-start the Fanuc program

I just want to make sure: you write "restart the Fanuc program". Are you actually restarting things, or unpausing? The former should always clear the list (as the list ctor is invoked), the latter is a situation handled by the additions in this PR, so could perhaps need something more.

I'm going to merge this PR as it is now.
We'll likely want to clear the buffer on any error, as I wrote in my earlier comments, but for now this is already an improvement.
Thanks for the contribution @hersh. Much appreciated.
And my apologies for the poor performance of the driver. Things are unfortunately rather limited (although #12 is interesting).


Dropships history page

Dolores 2.0 has an export feature for the past shop/catalog sales so hit me up, when you need something.
Also @Gedili the db should store the entity id (item, room or crew) along the entity type, not just ItemDesignId. At least for shop/catalog sales and IAP promotions.
If you need help on retrieving the promotion information (IAP bonus), hit me up on Discord.

Done in 9db42184b5126d94ad01ff50b6c3bd2f8cffea05


Add megaphone icon

Preview

"microphone"?

I think @mittalyashu means megaphone :p

Yeah, while submitting PR, I also got confused there 😅.

@mittalyashu
Maybe try to make handle a bit bigger.
On 100% scale the handle looks a bit small.

Like this

100%

@mittalyashu what do you think?


Repeated line?

https://github.com/slamdata/purescript-halogen/blob/master/examples/driver-io/src/Main.purs#L22
Sorry it's the first Halogen example I've looked at, but I don't understand why the Monadic IO.query function is repeated 3x.

It's just part of the illustration of using the IO record to listen to and send messages to a component. Note above the querying a subscription is set up to log whenever a message is received. Toggling the button on and off via the query results in the messages from the button being observed and logged in the console.

Ahh, Thanks. I thought it was part of the subscription, rather than the functional equivalent of sending a toggle event.


[Bug]: importing react-idle-timer causes SyntaxError

Version
System:
    OS: Linux 6.9 Arch Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
    Memory: 10.94 GB / 19.29 GB
    Container: Yes
    Shell: 3.7.1 - /bin/fish
  Browsers:
    Chromium: 126.0.6478.126
  npmPackages:
    @rsbuild/core: 1.0.0-alpha.4 => 1.0.0-alpha.4
    @rsbuild/plugin-react: 1.0.0-alpha.4 => 1.0.0-alpha.4

Details
Using react-idle-timer in a react project causes SyntaxError:
vendors-node_modules…ack_c-32d00f.js:288
 Uncaught  SyntaxError: Unexpected token ';' (at vendors-node_modules…32d00f.js:288:21525)

Reproduce link
https://codesandbox.io/p/devbox/wqrg9x
Reproduce Steps

Create a new react ts project using pnpm create rsbuild@latest
Add 'react-idle-timer' as a dependency: pnpm i react-idle-timer
Modify the App component to use idle timer:

import { withIdleTimer } from "react-idle-timer";
import './App.css';

const App = () => {
 return (

Rsbuild with React

Start building amazing things with Rsbuild.

 );
};

export default withIdleTimer(App);

Run the dev server: pnpm run dev
Observe the syntax error message in Chrome DevTools

Same issue

Same here. Happens after upgrading rsbuild to latest version

This should related to: https://github.com/web-infra-dev/rspack/issues/7049
@ahabhgk cc

Fixed by Rspack, https://github.com/web-infra-dev/rsbuild/releases/tag/v1.0.0-alpha.6

Thanks so much @chenjiahan !!!

Issue1 is fixed, but i still got this issue @@


Failed to solve the sub-problem ... Failed because:flex-rigid case failed all backtracking attempts

I'm getting a strange "failed to solve the sub-problem" error.
(* Taken from [metatheory/attic/norm.fst].

Still open.
The trouble seems to be unifying the types of the indices within a nested pattern.
This works:
let path_same_repr v d f x r z p_1 p_2 () =
  match p_1 with
  | Refl _ ->
    (match p_2 with
     | Refl _ -> admit()
     | _ -> admit())
  | _ -> admit()

but,
match p1, p2 with
| Refl _, Refl _ -> admit()
| _ -> admit()

does not.

This is similar to #682, resulting because of F* not being able to fully infer the type of the scrutinee when typechecking the patterns. Adding the original example (adapted to latest F*) there.


Seems to be broken on Ubuntu 16.04

Due to it using an init script vs systemd.
FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service teamcity-server: host"}

I don't know enough about TeamCity to write a unit file for it, I was just trying to get it running locally to evaluate it.

Hello. Thank you for a feedback. For now I have only implementation for SysVint and since Ubuntu 16.04 is using Systemd, it's not working. I'll prepare a fix soon.

What OS is this known working on? I can just spin up a VM on that to get
going, the Docker options for team city aren’t working out so well for me.
--
Jim B
On September 27, 2017 at 3:45:14 AM, Mateusz Trojak (
<EMAIL_ADDRESS>wrote:

Hello. Thank you for a feedback. For now I have only implementation for
SysVint and since Ubuntu 16.04 is using Systemd, it's not working. I'll
prepare a fix soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/matisku/ansible-teamcity-server/issues/11#issuecomment-332438152,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD4FnQ_HmMeK-SsXVAK_ILtuWB9oDl9Oks5smf0JgaJpZM4PlS0d
.

https://galaxy.ansible.com/matisku/teamcity-server/ Ubuntu Trusty

Done https://github.com/matisku/ansible-teamcity-server/pull/13


Escape key should close the popups

For example it doesn't for Login popup

@anqaka as we discussed over chat, it would be better if you care about this one ;)

@szafran89 I'll try to make modals accessible, I cannot make assignment  for now


Add a progress bar for ToDos

Add a progress bar for ToDos and show how many percent of them have been marked as done.
Round off percentage to 0 decimals, i.e, 54.1 % should be shown as 54%, 69.9% should be shown as 69%, 70% should be shown as 70%.
progress bar should be circular, and should look something like this on the right-hand side above the labels.

Can you assign this to me @sanskaromar

Sure, go agead @manav-06

@manav-06 Are you still doing it?

It'll be done by today. Sorry for the delay. Was busy in icpc work

Hi, @sanskaromar should I keep it in bottom left. If the page is scrolled it doesn't cover any other component. But in top right it will go over the labels

@manav-06 Yes, the bottom left would be fine 👍

@sanskaromar please review #27

@manav-06 Great Work 🔥


Latest release does not include a built version of the code

https://github.com/TinkurLab/monorepo-pr-labeler-action/releases/tag/4.1.2

Thanks and sorry. The build step needs to be added to CI so this doesn't happen.


Time to first byte?

Suppose we want to load-test an API which uses server-sent events (SSE). Is it possible to measure the time-to-first-byte using Goose?

Can you provide some examples of how you’re using SSE and what metrics you’d want to measure? What technologies are you using?

Hmmm, I can try and get more specific if you need, but one example would be load testing an API like ChatGPT, which uses SSE so that you can start to see the response streaming back as it is generated, rather than simply staring at a blank page for a long time before the entire response is complete.
In these types of use cases, time-to-first-token (essentially time-to-first-byte) is the interesting metric, as that represents the latency between asking a query and when the user can begin to receive a response. This metric is often what dictates how responsive a streaming LLM API feels to a user.
https://www.databricks.com/blog/llm-inference-performance-engineering-best-practices says more about this if you go to the "Important Metrics for LLM Serving" heading.
So, the question then is: can goose be used to load-test and measure a time-to-first-byte as a proxy for time-to-first-token?
Does that help clarify?

That’s very helpful, yes. I’ll find some time to test and see what can be done. I expect it will take some code changes/additions to be useful.


fix docstring typo: valdiation to validation

Fixed typo in _fft_helper docstring

I see that other helper functions keep the stackoverflow references. These might give some hindsight on the implementation of the function, and guide new users who are browsing the source code for the first time, such as me.
Is there a trend towards removing these stackoverflow references from other helper functions in SciPy?
I am of the opinion of keeping these and other references in the documentation. Either as a reference or as a comment in the code.

References are of course fine and valuable but this has no relevance to FFTs or other properties of the original function. It is not even cited but only mentions the stride trick. If you look at the implementation you will probably go to NumPy documentation anyways or search on SO.
We had the same discussion #7833 about these type of references, coincidentally, again about strides.

I understand the argument and have removed the References sections pointing to stackoverflow.
I searched the scipy code repository for stackoverflow answers and these are, at best, inline comments.

Nice. Thank you @daguiam


3.0 update: Globalization and localization

Ryan to do this.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
Content: Globalization and localization in ASP.NET Core
Content Source: aspnetcore/fundamentals/localization.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@Rick-Anderson can I participate on this while I added almost the localization features if not all in 3.0.0 :)

@hishamco Can you provide a PR with the 3.0 updates? You might want to duplicate the entire document like this:
::: moniker range=">= aspnetcore-3.0"
copy of existing doc which you update for 3.0
::: moniker-end
::: moniker range="< aspnetcore-3.0"
original document
::: moniker-end

::: moniker range=">= aspnetcore-3.0"
copy of existing doc which you update for 3.0
::: moniker-end

Sure, I already know the monikers stuff :)

FYI: I wrote a related blog post http://hishambinateya.com/what-is-new-in-localization-in-asp.net-core-3.0

This guide is great for application localization.
Is there any build-in way to localize a razor component library as stand alone ? (i.e. all the resx files should be inside the library itself, etc...).
I read a few guides already and they all target only localization an application.

There's a built in support for that with the help of ResourcesLocationAttribute

Thanks. I'll look into that.
Do you know of any guides/example that can help with this specific scenario ?
The desired result is to have built-in resx files for the library for common languages, and still allowing to override specific values/add new languages by the consumer of the library also through localization.

The current docs mentioning that also you can check aspnet/entropy repo

@casee these are examples from the source
https://github.com/aspnet/Extensions/tree/master/src/Localization/Localization/test/Microsoft.Extensions.Localization.RootNamespace.Tests
https://github.com/aspnet/AspNetCore/tree/master/src/Middleware/Localization/testassets
They are absolutely will help you

I think it's the time to start on this one
@Rick-Anderson shall I start with modifying the current code to target 3.0, after that we can write about the new stuff that have been added

@Rick-Anderson shall I start with modifying the current code to target 3.0,

Sure. Just remember
::: moniker range=">= aspnetcore-3.0"
copy of existing doc which you update for 3.0
::: moniker-end
::: moniker range="< aspnetcore-3.0"
original document
::: moniker-end

Don't worry about the monikers, I already worked with them before :)
the PR is coming 🚀 🚀 🚀

@Rick-Anderson I will create another PR to talk about the Content-Language header, one more thing there's a minor change in LogLevel when the culture is unsupported shall we point to this?

there's a minor change in LogLevel when the culture is unsupported shall we point to this?

Sure

Ok, I will did that in my 2nd PR


"octaveFull" fails to build

Issue description
The octaveFull package fails to build with:
/nix/store/9kxhc2f3j5lcyh00zcrifvfly33n5m4r-binutils-2.27/bin/ld: cannot find -ltiff
/nix/store/9kxhc2f3j5lcyh00zcrifvfly33n5m4r-binutils-2.27/bin/ld: cannot find -llzma
/nix/store/9kxhc2f3j5lcyh00zcrifvfly33n5m4r-binutils-2.27/bin/ld: cannot find -ljpeg

Seems like some libraries are simply missing. Found while building portaudio's reverse dependencies.
Steps to reproduce
nix-build '<nixpkgs>' -A octaveFull

Technical details
Fails on NixOS and Gentoo hosting Nix.
nix-env (Nix) 1.11.4
nixpkgs "17.03pre95922.13491f9"

First failing build: https://hydra.nixos.org/build/43282962
Did maybe https://github.com/NixOS/nixpkgs/pull/20227 break it?

Doesn't this package just build fine now?
https://hydra.nixos.org/build/51591799

Yes, apparently it builds on unstable, 17.03 and 16.09.


Yaniv - semantics on installtion guidlines

Installing the Spark development environment

Spark directory (instead of spark, capital S)
cd into Spark before adding remote, and both NVM, and NPM modules installation.
Config file extensions are .js (instead of .json)

yes the system is running , but unfortunately without initial data.
thereofre there are issues showing the client interface (all lists, such as camps are empty).
Update on pull request #483 the creation of the spark MySQL default-user


Allow specifying profiles to cargo rustc

This should allow compiling the specified target in the various profiles that
are available to it, e.g. bench or test in addition to the standard
dev.
Closes #2120

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

r? @brson

@bors r+

:pushpin: Commit 71ff274 has been approved by brson

:hourglass: Testing commit 71ff274 with merge 58cc3a2...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


"No Text+ found in media pool" even when it is

Hello! Let me just start by saying I've tested this plugin extensively and on the small transcription model is far superior to the default subtitles in everything except the timings. Really good job!
The issue im having is when im trying to use it to subtitle multiple tracks  (one at a time) with different subtitles templates. Its very finicky if its gonna detect the Text+ in the folder or not. My request is if it would be possible to add a way for us to select which text+ we want to use with a drop down menu, similar to how the Snapcaptions plugin does it instead of dragging it to the media pool.
Thank you so much

Thanks for the feedback. I'm going to add this in the next update :)

This is fixed now if you download the latest update

This is fixed now if you download the latest update

you absolutely beautiful person.
Downloaded it and did a quick test, its flawless.
So much easier than the previous method.
10/10


Case sensitivity inconsistent between Route registration and Middleware assignment

The following issue was discovered using Laravel 5.0 and  has not been tested with any other version of the framework
Expected behavior: Middleware and Routes use the same case-sensitivity when referencing controller actions. Case sensitive is probably the ideal solution
Current behavior: Controller actions in middleware registration are case sensitive, while Controller actions in Route registration are not.
Reproducibility: In the following example, users may access the routes as normal despite the controller action being lower-case. However, they will encounter the auth middleware which should not have been applied due to the except clause during middleware registration.
Given the following example, one would expect either of the following:

Controller action not found exception when visiting milestone/{id}
Middleware auth is not applied to the ShowMilestone action

//routes.php:
//note that "show" is not capitalized. When registering routes, case sensitivity does not mater
Route::get('milestone/{id}', "DatasourceController@showMilestone");
Route::resource('datasources', 'DatasourceController'); //DatasourceController manages a resource. I've omitted the usual CRUD methods for brevity, however

//DatasourceController.php
class DatasourceController extends Controller{
    public function __construct()
    {
        //note that "show" is not capitalized. When registering middleware, case sensitivity matters.
        //As a result, the auth middleware is applied to showMilestone when it appears the coder omitted it
        $this->middleware('auth',['except' => ['showMilestone']]);
    }

    public function ShowMilestone($id)
    {
        //code here
    }
}

As you can imagine, this gotcha caused a fair bit of pain/time waste, and I was not able to find any reference to it in the documentation (but of course, I could be mistaken).

My apologies, I just realized that the 5.1 branch. Is there any way I can move this to the appropriate branch, or do I need to recreate it? (is it even necessary to do so?)

http://php.net/manual/en/functions.user-defined.php says:

Note: Function names are case-insensitive, though it is usually good form to call functions as they appear in their declaration.

If that's the case then, shouldn't middleware assignments follow the same convention as route actions do?

We ARE case sensitive.


Iscroll inside Iscroll

Situation I have a one main div holding a series of small divs, (think widgets on a dash board). Some of the small divs need Iscroll to scroll the information. The large div or page also has Iscroll. When I scroll using touch or mouse wheel over a small div the, it scroll but the scroll is passed through to large div behind, so both scroll. How can I stop this?

mark

It would be incredibly useful to get this fixed. breams solution works OK to prevent the parent scrolling while scrolling a child scroller, but it would be nice if once you get to the top of a child scroller, the parent automatically starts scrolling up again (likewise with the bottom)

Thanks @jasokant, it worked great!
It would be really nice to have this fixed, with the functionality @nickizzle mentioned

This is the solution I came up with in the end. @fgilio you may find this useful. In this example, innerScroll and outerScroll are both iScrolls. innerScroll is inside outerScroll:
innerScroll.on('scrollStart', function() {
if ((this.y < 0 && this.directionY == -1) || (this.y > this.maxScrollY) && this.directionY == 1) {
outerScroll.disable();
}
});
innerScroll['js-terms-scroll'].on('scrollEnd', function() {
outerScroll.enable();
});

Thanks @nickizzle, that's pretty useful!!

Hey Guys,
how could be this fiddle be achieved with iScroll5?
http://jsfiddle.net/khaledalyawad/4p7t8ymp/
I am having problems to implement the solution of @nickizzle
THX!

@nickizzle i don't know how you become this code working for iscroll. Iscroll doesn't use native scroll, it change position of content inside parent container via transform. I can realize only @breams code


change the input data order

First, Love the library! Thanks for all the hard work!
my issue is:

Data count less than data required for the strategy  HammerPattern
Data count less than data required for the strategy  HammerPatternUnconfirmed
Data count less than data required for the strategy  TweezerBottom

Current
current situation is that we need to create input for pattern that need 2 days, and create another for the one with the 3 days, and kind of.
input2Days = {
   open: [
               data-of-1-days-back,  // for example 4.12.2019
               today,                // for example 5.12.2019
   ],
   close: ......
}
input3Days = {
   open: [
               data-of-2-days-back,  // for example 3.12.2019
               data-of-1-days-back,  // for example 4.12.2019
               today,                // for example 5.12.2019
   ],
   close: ......
}

how can i check all the patterns in the same input?
Expected
think to create it more generic way.
in that way i will build input as long as max pattern need,
when we build it with first value is the latest value (today)
and the other one is yesterday, and the third is 2 days back, ....
and send it for checking.
for example if i will check the input for 5 last days,
every pattern

the one that needs 2 days back like PiercingLine,
and the one that needs 3 days back like EveningStar)
and even the one that need 5 days back like HammerPattern
and like that..
will take it's own needs for checking.

for example if i gave input
input = {
  open: [
             today,                // for example 5.12.2019
             data-of-1-days-back,  // for example 4.12.2019
             data-of-2-days-back,  // for example 3.12.2019
             data-of-3-days-back,  // for example 2.12.2019
             data-of-4-days-back], // for example 1.12.2019
   ],
   close: ......
}

pattern that need 2 days will take the first #1 and second #2 parameters from the array.
pattern that need 3 days will take the first #1 and second #2 and third #3  parameters from the array.
in that way- we can create one input object for all the patterns.

@iofirag It works the way you expect. Did you check this file?
If you still face this issue, can you send a sample data?

yes, i see,
https://github.com/anandanand84/technicalindicators/blob/master/src/candlestick/CandlestickFinder.ts#L66
so just for understand,
if i set [5/12/19(data), 4/12/19(data), 3/12/19(data), and vice versa..]
so i dont need to set reversedInput = true ?
(i a little bit confuse about reversedInput field)

oldest data is always last. If you give oldest data first you need to say reversedInput as true

got it!. thanks 👍


An openmm issue when trying to run generate_new.py

Traceback (most recent call last):
File "generate_new.py", line 307, in
aar, rmsd, attend_logits = model.generate(batch, dir_name)
File "./models/PD.py", line 371, in generate
to_pdb(label_X, batch['amino_acid'], batch['res_idx'], batch['amino_acid_batch'], self.generate_id, batch['protein_filename'], target_path, original=True)
File "./models/PD.py", line 543, in to_pdb
openmm_relax(path)
File "./utils/relax.py", line 74, in openmm_relax
simulation.minimizeEnergy(tolerance)
File "~/envs/PocketGen/lib/python3.8/site-packages/openmm/app/simulation.py", line 143, in minimizeEnergy
mm.LocalEnergyMinimizer.minimize(self.context, tolerance, maxIterations, reporter)
File "~/envs/PocketGen/lib/python3.8/site-packages/openmm/openmm.py", line 7009, in minimize
tolerance = tolerance.value_in_unit(unit.kilojoules_per_mole/unit.nanometer)
File "~/envs/PocketGen/lib/python3.8/site-packages/openmm/unit/quantity.py", line 626, in value_in_unit
val = self.in_units_of(unit)
File "~/envs/PocketGen/lib/python3.8/site-packages/openmm/unit/quantity.py", line 662, in in_units_of
raise TypeError('Unit "%s" is not compatible with Unit "%s".' % (self.unit, other_unit))
TypeError: Unit "kilocalorie/mole" is not compatible with Unit "kilojoule/(nanometer*mole)".

I reinstall openmm to match the version in pocketgen.yaml and the error is gone.


[Question] There is a way to perform a full backup (not a incremental)? What happens when reach retain number?

Question
I have 2 scenarios:
Scenario 1)
A bucket on s3 that store daily backups from my volumes with retain=30, that backups are executed every day at 00:00H;
Q1: When longhorn performs the 31st backup, what happens with the others?
Scenario 2)
Another bucket on s3 that store a backup that is executed only one  time per month on Sundays;
Q2: I want to know if there is a way to have infinite retain for this backup;
Q3: I Would like that specific backup don't perform an incremental backup, but a full one. For example, My MySQL has 10GB of data, by the end of the year, I would like to have 12 Full backups each one with 10GB.
Thanks!
Environment:

Longhorn version: 1.1.0
Kubernetes version:
Node config

OS type and version
CPU per node:
Memory per node:
Disk type
Network bandwidth and latency between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):

Additional context
Add any other context about the problem here.

Q1: When longhorn performs the 31st backup, what happens with the others?

https://github.com/longhorn/longhorn/issues/2191 might help to answer this question.

Scenario 2)
Another bucket on s3 that store a backup that is executed only one time per month on Sundays;
Q2: I want to know if there is a way to have infinite retain for this backup;

Currently, longhorn restricts the MaxRecurringJobRetain to 50.
https://github.com/longhorn/longhorn/issues/1016

Q3: I Would like that specific backup don't perform an incremental backup, but a full one. For example, My MySQL has 10GB of data, by the end of the year, I would like to have 12 Full backups each one with 10GB.

Longhorn only supports incremental for snapshots and backups. Do you mind you share the reason why incremental backup doesn't work for you? Would Disaster Recovery Volumes works better for your case?

Thanks!
Answering your question: With your explication, incremental backup works for me now.
You may close this issue.


IMDB in mxnet only unroll 1 step but other frameworks unroll 150 step.

That's why mxnet is very fast in your benchmark. my code is here:
def create_symbol():
    # https://mxnet.incubator.apache.org/api/python/rnn.html
    data = mx.symbol.Variable('data')
    embedded_step = mx.symbol.Embedding(data=data, input_dim=MAXFEATURES, output_dim=EMBEDSIZE)
    gru_cell = mx.rnn.GRUCell(num_hidden=NUMHIDDEN)
    # Initialize its hidden and memory states.
    # 'begin_state' method takes an initialization function, and uses 'zeros' by default.
    begin_state = gru_cell.begin_state()
    # Call the cell to get the output of one time step for a batch.
    output, states = gru_cell.unroll(length=MAXLEN, inputs=embedded_step, merge_outputs=False)
    # output, states = gru_cell(embedded_step, begin_state) ***WRONG***
    # FC out
    fc1 = mx.symbol.FullyConnected(data=output[-1], num_hidden=2)
    # Label
    input_y = mx.symbol.Variable('softmax_label')
    m = mx.symbol.SoftmaxOutput(data=fc1, label=input_y, name="softmax")
    return m

Thanks for the spot! Updated


feat(update readme): added introduction on readme, and some screenshots

Fixes Issue

Closes #74
Added some screenshots and a basic introduction to the readme

will need to change the screenshots, as the project progresses

Aadarsh images are not getting displayed. Fix them.

Aadarsh images are not getting displayed. Fix them.

Will change them to links, after they have been added to the repo


refactor: use pre 3.10 style annotations for ConfigDict

Change Summary
Rewrite pydantic.ConfigDict with pre 3.10 style annotations (e.g using typing.Union instead of |)
Related issue number
Fixes #8134
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[ ] Tests pass on CI
[x] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @sydney-runkle

Not sure if file-level # ruff: noqa: ... is the best way to suppress the linter errors, but I'm sure that we can't set project-wide setting to ignore typing upgrades since I saw that a lot of function signatures use |-style annotations by grepping the files.
please review

@sydney-runkle
I'm afraid it's not possible to use ConfigDict as annotation because of the circular import between it and pydantic/_internal/_generate_schema.py, which resolves the type annotations. I've tried a few things and I either got an error saying that there's no _GenerateSchema (which is imported by ConfigDict if TYPE_CHECKING) or that the model is incomplete and I should rebuild it

@waterfountain1996,
Ah, that makes sense. I'll go ahead and close this PR then. Thanks for looking into this thoroughly!! 🌟


Error: 0x80070006 in Ubuntu LTS

I recently installed Ubuntu LTS for my Windows 10 laptop. Whenever I try to open it, it says Error: 0x80070006, within the Ubuntu window. If I press any key, the Ubuntu window automatically closes. I have no idea why that's happening. I used to have Ubuntu LTS before, but never got that error. This is the first time it's happening. Can someone please help me with that?

Please resubmit following the template and include detailed logs of the wsl.exe launch leading to the error.


Update riscv-gnu-toolchain for more efficient submodule checkout

The current upstream riscv-gnu-toolchain repo has been updated to remove the need for --recursive option when cloning the repo.  The build system fetches code as required. See here: https://github.com/riscv/riscv-gnu-toolchain
I assume would also apply to having the toolchain as a submodule, so perhaps our fork should try to incorporate these updates from upstream.

riscv-gnu-toolchain is updated to 12


Update ygnmi

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

605 of 141072 (0.43%)  changed or added relevant lines in 19 files are covered.
290728 unchanged lines in 17 files lost coverage.
Overall coverage decreased (-0.3%) to 2.178%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

gnmi/oc/enum.go
8
20
40.0%

gnmi/oc/union.go
0
16
0.0%

gnmi/oc/ocpath/ocpath.go
32
124
25.81%

gnmi/oc/bgpgue/bgpgue-0.go
43
421
10.21%

gnmi/oc/keychain/keychain-0.go
0
595
0.0%

gnmi/oc/structs-0.go
60
659
9.1%

gnmi/oc/definedsets/definedsets-0.go
0
685
0.0%

gnmi/oc/lacp/lacp-0.go
0
736
0.0%

gnmi/oc/lldp/lldp-0.go
8
1289
0.62%

gnmi/oc/acl/acl-0.go
0
2910
0.0%

Files with Coverage Reduction
New Missed Lines
%

bgp/gobgp.go
21
90.59%

gnmi/oc/ocpath/ocpath.go
145
37.46%

gnmi/oc/union.go
626
0.83%

gnmi/oc/bgpgue/bgpgue-0.go
635
13.93%

gnmi/oc/enum.go
901
15.38%

gnmi/oc/keychain/keychain-0.go
942
0%

gnmi/oc/definedsets/definedsets-0.go
980
0%

gnmi/oc/lacp/lacp-0.go
1461
0%

gnmi/oc/lldp/lldp-0.go
2436
0.69%

gnmi/oc/acl/acl-0.go
5184
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
13393

Relevant Lines:
615002

💛  - Coveralls


libfs: fix RemoteStatus.ExtraFileNameAndSize

Make it behave like ExtraFileName
It was reported on irc and traced the problem to this

Ping.

whoops, sorry! LGTM :thumbsup:


added <IP_ADDRESS>/18 to public-ip-list.md

how to check:
# whois <IP_ADDRESS>
<...>
% Information related to '<IP_ADDRESS>/18AS200350'

route:          <IP_ADDRESS>/18
origin:         AS200350
mnt-by:         mnt-ru-yandexcloud-1
created:        2022-04-27T13:12:56Z
last-modified:  2022-04-27T13:12:56Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.113.2 (ABERDEEN)

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes: added missing network to documentation

dupe. after sorting I found that.

Все готово!
Commit: f94586820f4a0dad0ba16b060a73ab79cb8c6837
Проверьте результат: RU.
Check the result: EN.


Expected the primary data returned by the serializer for a queryRecord response to be a single object but instead it was an array

I am using newest production releases:
"ember-cli": "^2.6.0"
”ember”: "v2.6.0"
"ember-data": "^2.6.0"
"ember-cli-mirage": "^0.2.0"

Using the store.queryRecord() method in a route:
import Ember from 'ember';
export default Ember.Route.extend({
  model() {
    return this.store.queryRecord('user', {username: 'MODO'}); // 25, MODO
  }
});

I get this error:
Error: Assertion Failed: Expected the primary data returned by the serializer for a `queryRecord` response to be a single object but instead it was an array.

Replacing the store.queryRecord()  method with the store.findRecord() method:
    return this.store.findRecord('user', '25'); // 25, MODO

Then everything works fine!?
Is this a problem with Mirage?
With Ember Data?
Or, is it me who have misunderstood something?

What does your mirage/config.js look like for this route?

@samselikoff - Thank you for returning to me on this issue.
This is the content of my mirage/config.js:
export default function() {

  this.get('/users');
  this.get('users/:id');

};

Yes, I am speculating which one of those two route definitions is serving this.store.queryRecord()  and which one is serving this.store.findRecord() ?
Am I missing one of more definitions? Do I need additional route definitions to support query parameters like filter, sort and page?

I'm pretty sure queryRecord expects an array response. Can you paste in your console.log response to this request? Also, what adapter are you using? Do you have a Mirage serializer specified?

I am completely default in relation to Mirage 0.2.0.
This is the content of  my app\adapters\application.js file:
import DS from 'ember-data';

export default DS.JSONAPIAdapter.extend({
});

I have no adapter definitions in my mirage folder.
This is the content of  my mirage/serializers/application.js file:
import { JSONAPISerializer } from 'ember-cli-mirage';

export default JSONAPISerializer.extend({
});

This is my console.log response:
DEBUG: -------------------------------
ember.debug.js:6529DEBUG: Ember      : 2.6.0
ember.debug.js:6529DEBUG: Ember Data : 2.6.0
ember.debug.js:6529DEBUG: jQuery     : 2.2.4
ember.debug.js:6529DEBUG: -------------------------------
server.js:66 Successful request: GET /login-users
server.js:77 Object {data: Array[1]}
ember.debug.js:27773 Error while processing route: user Assertion Failed: Expected the primary data returned by the serializer for a `queryRecord` response to be a single object but instead it was an array.
The returned model is an array with all three instances/objects of the user model - not only the single instance/object username=MODO requested.

Looks like queryRecord expects a single object in response (instead of an array), so you'll need to do something like
this.get('/users', (schema, request) => {
    return schema.users.where(u => u.username === request.queryParams.username)[0];
});

Does that make sense?

Yes, your response definitely makes sense, thank you!
My problem is, that in my application I use all of the methods store.findAll('myModel'), store.query('myModel', {x: 'a', y: 'b'}) and store.queryRecord('myModel', {x: 'a', y: 'b', z: 'c'}).
In addition, in my application the mix of query parameters varies. You example is hardcoded with one specific query parameter?
How do I setup Mirage to distinguish between those three scenarios, where store.findAll() and store.query() expects an array and store.queryRecord() expects an object?
I guess, I will have to get rid of using store.queryRecord(), and instead extract the single returned object from the returned array, like this
  model() {
    return that.store.query('myModel', {x: 'a', y: 'b', z: 'b'})
    .then(function(myModelArray) {
      return myModelArray.get('firstObject');
    });
  }

Supported in mirage/config.js by:
  this.get('/my-models', (schema, request) => {
    return schema.myModels.where(request.queryParams);
  });

Yes, I think this makes the most sense. Looking at the docs for DS.Store it says

Note: the primary use case for store.queryRecord is when a single record is queried and the id is not kown beforehand. In all other cases store.query and using the first item of the array is likely the preferred way:

so I think what you said is correct.


Access-Control-Allow-Origin  origin documentation seems wrong

Request type

[] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[ x] Correction or update

Details
The MDN Documentations states that:
 <origin> Specifies an origin. Only a single origin can be specified.

I don't think this is correct as the spec here:
https://www.w3.org/TR/cors/#access-control-allow-origin-response-header
Indicates:
Access-Control-Allow-Origin = "Access-Control-Allow-Origin" ":" origin-list-or-null | "*"

origin-list-or-null is:
origin-list-or-null = %x6E %x75 %x6C %x6C / origin-list
origin-list         = serialized-origin *( SP serialized-origin )
serialized-origin   = scheme "://" host [ ":" port ]
; , ,  from RFC 3986
This allows for a space separated list of origins.

Yes, but in the spec  it also says

In practice the origin-list-or-null production is more constrained. Rather than allowing a space-separated list of origins, it is either a single origin or the string "null".

I think that is why the MDN docs are written as they are.

Indeed you are right. Do you have any insight on how it is implemented in Firefox?

I don't, I'm afraid. You could maybe try asking on the dev-platform list (https://lists.mozilla.org/listinfo/dev-platform)

Thanks for your answers.


[Alert] Introduce new component

[x] I have followed (at least) the PR section of the contributing guide.

Closes #18094
Closes #18750
Features:

customizable start icon via Alert.startIcon (or no icon at all!)
customizable close icon via Alert.closeIcon (or no close icon at all!)
customizable description for text via AlertContent.variant === text | container

I have a problem with a test failure in packages/material-ui/src/styles/createPalette.test.js:681:14 and I cannot figure out why. Can anyone please take a look, maybe I missed something?

@r3dm1ke Is the fail related to the new colors in the palette? What if we handle it in another effort?

I only had a few short minutes to spend, but I was able to get some more boilerplate in place.
notes:

Regarding the usages of className={clsx(classes.root, className)}, I'm not sure how to tell which components need it or not - so I added it everywhere and verified that it does work on all components.  @oliviertassinari your guidance here would be helpful.
I have little-to-no idea how we would want to manage the position of elements.  For now, as a hack, I just used absolute positioning - but I think we should come up with something better.  @oliviertassinari your guidance here would be helpful.  I would love to use CSS Grid here (as I see you would too).  It's absolutely ready for prime time and this would be a very appropriate place to use it.
I am not sure which convention to use with Typography as it pertains to AlertTitle so I just copied from DialogTitle and used <Typography component="h2" variant="h6">.  @oliviertassinari your guidance would be helpful here.
I'm not sure if it's actually appropriate that AlertDescription is wrapped with a Typography the way AlertTitle is.
I (had to?) add @material-ui/icons to the lab package.  If there was a better/different way to do this please let me know.
Same goes for the way Typography was imported in AlertTitle and AlertDescription.  I'm not entirely sure if it's better to just do ../../../../Typography or import directly (like I did) from @material-ui/core
should I have used @ignore on the classes props?

It's coming along!

Sweet :)

Using it everywhere sounds great.
My main concern with the usage of CSS Grid is around, does the majority of the developers have enough knowledge of it to be able to easily apply customization? I think that it would be great to try flexbox out first. I will see what I can find to help.
The usage of the Typography sounds great. I'm wondering about the right element to use, maybe it should be a div?
Using the Typography sounds good too.
We don't use the icons package in the core to avoid the circular dependency and to keep the installation size minimal. I think that we should apply the same approach to the other icons we use in the core.
Import from the public package.
In doubt, apply the same approach to the other components, the components should be highly consistent.

cool - I removed AlertIcon in https://github.com/mui-org/material-ui/pull/18702/commits/bb5d4c666aaa3ec197d95de5f6fc0f94768422df and instead used a startIcon API just like Button.  I think it's a great improvement.  It's actually much simpler this way and also has a new feature: the alert will now work just as well without an icon - which is cool.  We don't need any "hasIcon" prop or anything.

in https://github.com/mui-org/material-ui/pull/18702/commits/1d3d0532ec3afe27ebc353853455cc39ee1a78ce I did a similar treatment for the AlertClose.  Now, the onClose functionality for that Close button works, as well as the new feature that the icon is customizable (but defaults to <Close /> if none is provided).

in https://github.com/mui-org/material-ui/pull/18702/commits/1b50dd10543e537a2e8922ef379fe8739506d3da I addressed a functionality concern about wrapping in Typography for the contents of the alert.  I changed the name to AlertContent to align with CardContent, DialogContent, and StepContent and also to signify that it's not just a description, necessairly since (now) someone can pass whatever they want in by specifying a variant of container on AlertContent (the default is text).

In https://github.com/mui-org/material-ui/pull/18702/commits/82b6c922ed8d55c28eae513d5700be7f45c03251 I was able to spend some time with this after work today and fix some things with the styling.  Here's where it's at currently.  @oliviertassinari is there a design spec anywhere for this (from a material design perspective)?  I wasn't able to find one.
with everything:

with no actions:

with no startIcon:

with no closeIcon or Title:

just the title:

I added some initial coloring support:

There is an issue with coloring the buttons in AlertActions, though. Should we do it, or the user  should provide the colors to the buttons himself?

It looks, great guys 😍.
We had an internal discussion with @mbrookes around how we could approach the API on this component and the others. Basically, the root of the concern is on, how close to the underlying DOM node should the components be? Should we have 1. one component with many props or 2. multiple components with a few props.

pros:

More opinionated around how it displays, less question to ask, less room for mistake
Less code to read and to write
Each prop gives a strong signal on what the node is about and how it should be displayed, it can make the core logic simpler.

pros:

allow more flexibility
simpler to customize and override and it removes a layer of hidden logic.

Historically, we have been going with 2. as the default or in doubt, and go with 1. when its pros of out weight the pros of 2.
It seems that @dimitropoulos had a first-hand experience of the pros of 1. when moving to ditch the AlertIcon and AlertClose components. It makes sense and goes into @mbrookes that advocates for more 1.
Now, I still think that we should stick to 2. as much as we can. For the text input component, we had to build a TextField component on top of the lower components for simplicity.
In the case of the Alert, I would propose that we keep the current break down of components, I believe most people will use the Alert along. I think that the AlertTitle, AlertDescription, AlertActions are better designed for the long tail of the use cases. What do you guys think?

I think that the AlertTitle, AlertDescription, AlertActions are better designed for the long tail of the use cases.

Do AltertTitle and AlertDescription add enough value to exist as standalone components, being just a thin wrapper around Typography? Your suggestion to just use Typography directly gives the developer more control of the styling (absent an alert component to follow in the MD spec).

Good questions, I don't know.

I use material for personal projects and at work because I think that the experience, as with Dialog, of just typing <DiT + Enter and getting the title to be a superior experience than the experience of having to remember that the dialog title is a <Typography component="h2" variant="h6">
.
This is something I quite like about the library.  It's not like, though, I would be upset with a title prop, if the opposite were to exist.  I just think you hit the situation where you want to eventually put something else in there and having it just be an inlined component is easier with that use case because what you provide as children more closely match what's actually going to be rendered.  It feels less magical while still being pretty easy to use and work with.

Is there a rule against doing both?  To pick on title... why not allow a title prop that will literally just inject an AlertTitle component for you?  I realize this may be undesirable to some people but just to put it out there..

For another example of why there's a time and a place for each approach (and we don't have to go all-or-nothing on either one!) consider the close icon and start icon... it just seemed like reinventing the wheel to make an AlertIcon component.  Also... the current positioning model would have to totally change to use absolute position to float the Icon to the left and position it correctly.  I would say that for the icons themselves, it makes sense to just have a startIcon prop and a onClose prop (paired with an optional closeIcon prop).
One of the reasons I changed it is because I referenced the API of a couple of the examples, for example AntD:

    <Alert
      message="Success Tips"
      description="Detailed description and advice about successful copywriting."
      type="success"
      showIcon
    />
    <Alert
      message="Informational Notes"
      description="Additional description and information about copywriting."
      type="info"
      showIcon
    />
    <Alert
      message="Warning"
      description="This is a warning notice about copywriting."
      type="warning"
      showIcon
    />
    <Alert
      message="Error"
      description="This is an error message about copywriting."
      type="error"
      showIcon
    />

it's just.. so so easy to use.. You don't have to fuss with any additional imports or anything.  You simply just interact with a few simple props and boom.. it's all ready to go.
I'll also note that I really like the idea of the showIcon prop automatically handling which icon actually ends up being rendered with the option to (still) provide a custom icon.

Also.. there are use cases that seem legitimate that go outside the scope of what we would probably enjoy maintaining for AlertIcon.  For example, including an image (or svg):

I think that the experience, as with Dialog, of just typing <DiT + Enter and getting the title to be a superior experience than the experience of having to remember that the dialog title is a <Typography component="h2" variant="h6">

That's a fair point, and nothing to stop someone using Typography instead if they want a different appearance.

Is there a rule against doing both? To pick on title... why not allow a title prop that will literally just inject an AlertTitle

Funnily enough, I suggested the same thing when we were discussing it. The one downside I can think of is that when you give someone choice about how to do something, it leads to cognitive overhead in understanding the tradeoffs (if any), in order to decide which to use – Grid or Box for layout? Modal, or Popper, or Popover?
Other than that, no strong objection - and we could make it clear in the docs that they are alternate but functionally identical APIs. @oliviertassinari may have other opinions?

it just seemed like reinventing the wheel to make an AlertIcon component

Not disagreeing, but Stepper has a StepIcon component that is used internally in StepLabel (or can be overridden with the StepIconComponent prop). StepIcon is also part of the public API (although we don't have any examples of how you would use it). Stepper might be slightly over-engineered though, but I didn't dig into it with a critical eye – it's a complex component!
SpeedDial also has the SpeedDialIcon component, but it has to be supplied to the SpeedDial via the  icon prop, rather than being used internally. This could possibly be reworked to follow convention if the component gets moved to core.

I'll also note that I really like the idea of the showIcon prop automatically handling which icon actually ends up being rendered

We could possibly import the default icons (as internal icons), and allow the icon prop to optionally accept either a string ( 'success' | 'info' | 'warning' | 'error' ) or an actual icon component.

Just to chip in my 5 cents: I am in favour of having AlertTitle, AlertDescription and even AlertIcon. If we move everything into one component and pass content via props, the component would be way too big, logic way too complex and it will be harder to unit test. By having dedicated components for every aspect of the alert, we let user decide what exactly does he need and he can later write his own component that will pass props to Alert[Title, Description, etc.]. Alternatively, we could keep all these components and make an AlertBase component, very much like in TextField/InputBase.
Also, I have thought about passing the color to the buttons in AlertActions and it does not look viable. I think it is better to let user color the buttons himself, because they most likely will have different color based on context (e.g. delete button will most likely be error color, send button may be success or primary, etc).

Given that only one of the eleven Alert benchmark examples in the associated issue has buttons, I was going to question whether Alert should have them, as they seem to belong more in the domain of the Dialog. However, when checking the MD dialog guidelines for a suitable citation as to why, I noticed a reference to the banner component:
https://material.io/components/banners/banners.html
This seems to be as close as the MD spec has to an Alert, but without the fairly standard colors and icons seen in most other implementations.
How should we apply this here?

That's true.  Since making AlertContent have a variant="container" mode, if the user really wants buttons they can add them (and style them) themselves.

I'll just highlight what AntD does, which is sorta a middleground approach.  They don't have an explicit action button section, but you can optionally provide text to be used instead of a close button.  That makes sense, I think, because (if you think about it) most of the time what will semantically happen when you click an action button is somewhat similar to a dismiss or close button.

re the lack of a spec for this component:
@oliviertassinari @mbrookes according to https://youtu.be/E23IWqE4nac?t=351 the material design team is supposed to be accessible to us in some way to answer exactly-this-kind-of-question.  Is that the case? They seem to be calling out this project in particular as one they will be helping.  If so can we maybe take that avenue on getting questions answered about the buttons (and, for that matter, overall styling questions like @r3dm1ke's questions about whether there should be elevation/paper/dropshadow on the component or not)?

https://material.io/components/banners/banners.html
This seems to be as close as the MD spec has to an Alert, but without the fairly standard colors and icons seen in most other implementations.
How should we apply this here?

In the discussion for the issue related to this component, there was a suggestion to have a variant prop, which way be 'text' | 'outlined' | 'filled' | 'banner'.

@r3dm1ke Ah, thanks, missed that. What is text variant in this instance? (No background color or outline?)
To answer the other question you asked there, yes, this should be a controlled component (open prop).

@mbrookes the text variant should be something like the secondary alert from here, as suggested by @oliviertassinari

Okay, thanks. Not totally convinced by the prop name, but we can come back to it.

I'll also note that I really like the idea of the showIcon prop automatically handling which icon actually ends up being rendered

We could possibly import the default icons (as internal icons), and allow the icon prop to optionally accept either a string ( 'success' | 'info' | 'warning' | 'error' ) or an actual icon component.

This sounds great!
Regarding the API, I think that we can always change it later on before we move the component in the core. I personally think that we have an acceptable tradeoff, the most common use case requires a single component, it's not bloated by the long tail of rendering a title or actions, so 👍 from my part.

The good news:

I was able to implement the default icons thing! yay!  You can still provide a custom icon if you want.

The bad news:
I think we are blocked by https://github.com/mui-org/material-ui/issues/13875 for one thing because I just picked colors somewhat randomly, and for another thing because it would be really really really nice if you could pass the type (i.e. severity or whatever) to the Buttons in the AlertActions component.

Since the additional colors are now merged into master, I have hooked up the component to use them. And I found out that the text is not contrastive enough as it is (especially at warning):

This may be fixed by using the main color as the background, and contrastText color for the text color:

What do you think?

wow great stuff!!! I really was hoping to get to that this weekend but it didn't end up happening.
They're both kinda tough for their own reasons.. huh.  @oliviertassinari @r3dm1ke did you see what I said above about asking someone from the actual material-design team?  They claim they want to help, and I would tend to believe them saying that.  https://github.com/mui-org/material-ui/pull/18702#issuecomment-566491127

Nice :). I'm pushing it one step further.

Ant solves it by using dark text on the light background:

For the customized snackbars example, orange[500] for warning gives better contrast than amber[500]:

I have tried to push further the effort. There are two points I'm wondering about:

I have removed the onClose prop, but I'm wondering if we shouldn't add it back. On one hand, this enables tree shaking, on the other, it requires more imports and manual translation of the close action.
The variant and color props are marked as @ignored during the TypeScript conversion. I don't understand why.

I have removed the onClose prop, but I'm wondering if we shouldn't add it back. On one hand, this enables tree shaking, on the other, it requires more imports and manual translation of the close action.

It's not quite ready yet, but I'm inclined to show you a sneak-peek of a little project I've been working on as a result of this PR: https://github.com/dimitropoulos/react-ui-roundup#Alert (or you can (pretty much) the same thing with a few more features at https://react-ui-roundup.dimitrimitropoulos.com).  If you look at all of the Alert components, you'll see that onClose functionality is pretty standard equipment.  It'd be great to keep it in there.  If there are build size issues (i.e related to the tree shaking) perhaps we can loop back on this in another iteration.  It is in the lab, after all.

The variant and color props are marked as @ignored during the TypeScript conversion. I don't understand why.

This is almost definitely a mistake.  If marked as such by me, it was done so in ignorance.

If you look at all of the Alert components, you'll see that onClose functionality is pretty standard equipment.

@dimitropoulos Thanks for the benchmark! Yeah, I like the idea. I think that @mbrookes would support the prop too.

This is almost definitely a mistake. If marked as such by me, it was done so in ignorance.

I suspect an issue with the TypeScript to prop types generation script.

@dimitropoulos To answer your question regarding getting feedback from the Material Design team. I could find the following, I think that we are on the right track with the default text variant (that matt might want to rename):

https://admin.google.com/ac/accountchooser?continue=https://admin.google.com/ac/devices/list?category%3Dmobile

https://console.firebase.google.com/project/react-swipeable-views-395e4/hosting/main

https://developers.google.com/maps/documentation/roads/intro
We have been in contact with the Material Design team (personally did 2 calls and one on physical meeting so far). However, I wouldn't expect to receive specific guidance on this matter. At least, I would be positively surprised if we do.

My first thought was that, if in doubt, we should go with the simplest API first (type), and add the color and/or icon props later based on demand; however those particular props are pretty ubiquitous, so I'm not so sure it makes sense to omit them.
My only other niggle is with the prop name type. We've avoided it in the past as an overloaded term. severity is the best alternative I can think of.

for what it's worth: I, too, feel that severity is the next-best choice.  I can understand the desire to stay away from type.

Does it mean we have found a common understanding under this approach:
type (that determines the icon and the default color) + color (that can override the color from type) + icon (that can override the icon from type) + iconMapping (that can extend the scope of the type supported) props could work.
?

looking like we're pretty close to a minimally viable component for the lab!  is there anything else here we have in mind to do? @oliviertassinari @r3dm1ke @mbrookes?

I think that we are good to go. @mbrookes has uncovered an interesting topic on title vs Tooltip usage, but it's leaking from the Alert to the TablePagination and Autocomplete. I don't think that it should block this pull request.

Thank you everybody for your time!
We will likely have a couple of follow-up pull requests, one step at the time :).

woooohoooo!  awesome!  I'm more than happy to help with any followup work so please @oliviertassinari feel free to ping/assign me.

@dimitropoulos Thanks! GitHub has this concept of code owner: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners. It's something that we have never used yet. However, I think that it would be interesting to experiment. Would you be interested in being the code owner of the Alert component? @mbrookes What do you think

I didn't know about that feature. Worth trying!

Awesome, let's experiment! I will handle this in my next batch of small changes (probably Sunday).