trng extension covers very narrow range of applications

Reading current spec gave me impression that trng design is very x86 like magical being that "just is through the space, time and universe". It's tightly coupled to the core, always enabled, is fast enough to not require scheduler intervention, can't be reset/power cycled to recover from dead state (just freeze or throw an BSOD and wait until user restarts) and of course the only medium to talko to it, is our ISE.

The main ISA-level interface consists of a single pseudoinstruction, pollentropy that returns a 32/64-bit
value in a CPU register. It is invoked in Machine Mode (which may be the only mode) as follows

We specifically recommend against busy-loop polling on this instruction as it may have relatively low bandwidth.
Even though no specific interrupt sequence is specified, it is required that the wfi (wait for interrupt) instruction is available. Cores which implement mentropy must not raise an Illegal
Instruction Exception when executing wfi unless required to do so by the Timeout Wait bit of the
mstatus register, as detailed in Section <IP_ADDRESS> of the Privileged ISA Manual

I'm not sure how that wfi polling in M mode is supposed to work. Especially considering the fact that the specification doesn't define any M mode "rng ready" interrupt signal. Waiting for a random M mode interrupts is going to make polling time very non deterministic (BTW, isn't typical unix-like OS doing all of its periodic and peripheral interrupts in S mode only?).
About actual use cases in microcontrollers.
Let's consider TRNG like the one in stm32h7 [1] (claimed to be "AIS-31 tested")
Their design is of course an dedicated memory mapped peripheral as that's the only thing possible with ARM. But speculating what could change when they ported to RISC-V, that would be the addition of "bypass to rvk" configuration option and an extra fifo to the core.
The peripheral itself can take care of the err/rdy interrupts, conditioning and low level configuration.
There is significant problem with spec state machine when covering the bypassed peripheral

after reset the entire peripheral is clock gated

The core start first. Does it fall into infinite BIST or a Schrödinger state machine (DEAD if read now)?

it can be (AHB) clock gated at any time

Power saving. Does it fall into infinite BIST, instant DEAD or a Schrödinger state machine?

it has dedicated clock source that also needs to be configured

4 sources and the designated clock needs time to startup. Does it fall into infinite BIST, or a Schrödinger state machine?

that clock can also be shutdown

Power saving.
Does it fall into infinite BIST, instant DEAD or a Schrödinger state machine?

there is an official "enable" config bit that starts the analog sampling and conditioning

Here goes the actual BIST, WAIT and ES16

clearing that "enable" bit shuts down analog section

It's an officially mentioned (in 34.3.8) way of reducing power usage.
Does it fall into infinite BIST, instant DEAD or a Schrödinger state machine?

generated data can still be read after the analog section was shut down

The same thing can happen to the rvk bypass fifo. Probably a few ES16 and then what? Fall into infinite BIST, instant DEAD or a Schrödinger state machine?
About non recoverable DEAD state
Is the non recoverable DEAD state some legal requirement?

Implementations do not need to implement DEAD as it may not require an end-user notification;

That sounds like a weird freeze (that's a best case) when a thread polls for a random data that never comes. A corner case that's going to waste a 'few' man hours to debug. And even if it's known there is no clear way of knowing when to consider a fatal error.
There are definitely fatal enough cases where DEAD state is applicable, but can return to normal operation after intervention.

peripheral unconfigured or deconfigured for power saving
clock loss (switch to another one / restart)
errors requiring power cycling of analog section

STM's trng actually requires explicit actions to recover from seed errors (34.3.7, flag clear + dumping of the data).

an immediate lock-down may be a more appropriate response in dedicated security devices.

I think that sec-lockdowns should be at least configurable or/and have another SEC-DEAD state. Especialy since "manufacturer that know better" situations are so common. There are many applications that can't simply lock-down because of minor statistical issue.
About poll noise.
Is it really mandatory to have a standard but yet "custom" csr to read "raw noise" on every single core?
Isn't it supposed to be purely custom thing or even available only through memory mapped peripheral registers (undocumented registers or fuse blown after verification)?
[1] https://www.st.com/resource/en/reference_manual/dm00314099-stm32h742-stm32h743753-and-stm32h750-value-line-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

Hi @jnk0le
Thanks for all of your questions! I'll try and answer them, though @mjosaarinen might be able to give you better answers too.

Reading current spec gave me impression that trng design

To be extremely clear, we have not designed a TRNG. There is nothing in the specification about how a manufacturer should generate entropy.
The design is an interface to an entropy source. This is important, because it means a lot of your questions (I think, if I understand them correctly) are actually for the manufacturer to decide upon.
For the sake of my answers, I'll try and talk about three things:

A TRNG, built by a device manufacturer, in hardware, which is available through the ISA entropy source interface.
The entropy source interface (ES), meaning the mentropy, mnoise CSRs, plus pseudo instructions.
The software which uses this interface.

It's [...], always enabled, is fast enough to not require scheduler intervention, can't be reset/power cycled to recover from dead state (just freeze or throw an BSOD and wait until user restarts) and of course the only medium to talko to it, is our ISE.

The ES is always available and never blocks, yes. But that does not mean that the TRNG is always on from a power/energy point of view. Also, it's hard to know what you mean by "fast". The interface is non-blocking, but that doesn't mean that you'll get a very large amount of continually available entropy from it. It just means the instruction will return immediately, with likely either a WAIT or ES16 status code.
The expectation is that the TRNG tries to keep a buffer of entropy samples full. When the buffer is full, the TRNG can be "turned off" (whatever that means for the implementation) to save energy. When the buffer is sampled, the TRNG wakes up again and tries to keep it full.

I'm not sure how that wfi polling in M mode is supposed to work. Especially considering the fact that the specification doesn't define any M mode "rng ready" interrupt signal. Waiting for a random M mode interrupts is going to make polling time very non deterministic (BTW, isn't typical unix-like OS doing all of its periodic and peripheral interrupts in S mode only?).

The expectation is that the ES would be sampled by software periodically, as part of a regular / periodic interrupt routine, and the sample (if it was valid) would then be added to a software managed entropy pool. Hence, we don't define an M-mode interrupt.
About unix-like OS's doing things like periodic interrupts in S-mode only, that's something we can to look into for sure. Markku has talked to some of the Linux random number interface folks, but he can tell you about that better than I can.
About all of your questions about a concrete implementation. I can't answer them all, and they are all very valid questions, but I don't think any of them are insurmountable? They are almost all within the remit of the manufacturer to solve. I really like that you walked through the STM documentation and tried to map the behaviour onto our specification, I think that's a great exercise.
Remember, there can be certain amount of extra vendor / device specific management of the TRNG hardware outside of our defined ES interface. This might include some early post-power-on code to turn on the peripheral clock via a memory mapped interface etc. Just dropping in this AHB peripheral and expecting it to work with this new interface is not going to work. I'd expect the peripheral to have some "always on" section which can dynamically turn itself off and on depending on the need to generate more samples or not. So, I don't yet see a problem with reset behaviour and the state machine?

Does it fall into infinite BIST, instant DEAD or a Schrödinger state machine?

All of these questions are really for the implementer. Generally though, our expectation is that "there's no coming back from the DEAD". If you know your TRNG hardware is going to recover at some point in the future, that should be a BIST or WAIT state. Exactly which will depend on the implementation, but I'd expect that post power-cycle, you would have to enter BIST.

Is the non recoverable DEAD state some legal requirement?

Yes, the interface needs to be able to report an unrecoverable error. Generally speaking, the ES interface is designed to fit with FIPS/AIS certification schemes, meaning that it must be able to report all of the information those standards require.

Implementations do not need to implement DEAD as it may not require an end-user notification;

That sounds like a weird freeze (that's a best case) when a thread polls for a random data that never comes. A corner case > that's going to waste a 'few' man hours to debug. And even if it's known there is no clear way of knowing when to consider a fatal error.

I agree. And unfortunately, we can't rule out people implementing this badly. This might be bettered by changing the language in the spec?

There are definitely fatal enough cases where DEAD state is applicable, but can return to normal operation after intervention.

We're getting into semantics now, but I would not call a case fatal if it is recoverable. In our spec, fatal is a one way trip. For these cases, WAIT or BIST would be more sensible indicators.

I think that sec-lockdowns should be at least configurable or/and have another SEC-DEAD state. Especialy since "manufacturer that know better" situations are so common. There are many applications that can't simply lock-down because of minor statistical issue.

Being able to indicate a security lockdown might be useful. The DEAD state should not be used to indicate minor (read, frequently occurring and recoverable) statistical issues. If a TRNG needs to transition between BIST/WAIT/ES16 because of the occasional statistical error, that is handled in the current spec.

Is it really mandatory to have a standard but yet "custom" csr to read "raw noise" on every single core?
Isn't it supposed to be purely custom thing or even available only through memory mapped peripheral registers (undocumented registers or fuse blown after verification)?

The rationale is that everyone was going to need this interface in one form or another, so we should standardise as much of it as possible to ensure it is implemented safely (i.e. always report BIST when in noise test mode) but still give people enough flexibility. Otherwise, everyone has a different implementation, and the likelihood of a security critical mistake increases. It may be that this interface is disabled after manufacturing by some, yes.
It would be reasonable to argue this is too much a "manufacturer specific thing" to try and standardise at all. We went the other way, especially because you must have this sort of interface for FIPS/AIS certification.
Ultimately, the ES interface allows you to express the behaviour of a terrible TRNG implementation. This is necessary, because this might reflect a good TRNG implementation which has been damaged or attacked. However, just because this behaviour is expressible, doesn't mean it is likely or the intended average case behaviour.
Whew. Okay, I hope that brings some clarity? Please do keep asking, it's good for everyone involved.
Thanks,
Ben

Also - " trng extension covers very narrow range of applications"
This is very much by design. We didn't want to get into the situation RDRAND is in, where people now expect lots and lots of random bits very cheaply for non-cryptographic purposes. Hence this proposal is an Entropy Source for cryptography, not a random number source for anything else.

I'll close this.
We've already worked through the kernel interface issues and If there is a need for a non-fips non-cryptographic random, it can be proposed later. Furthermore, if a vendor wants to introduce a security vulnerability where one can cheat the FIPS online statistical tests by doing them again, the vendor is on her own as that will not pass FIPS certification.
As noted, if a vendor wants to implement these or other security vulnerabilities, or introduce power problems rather than solve them, that's not really our problem. They're also free to tightly couple it, or arrange CSR access in a looser way. I can tell you that the reference implementation is not tightly coupled, nor is always on as claimed by the commentator.

The raw noise source is required for FIPS 140-3 / SP 800-90B certification. Lack of it is the main reason why the Intel RDRAND can't really be used cryptographic modules.
Also you may find it instructive to look at how AMD's cryptographic coprocessor provides an entropy source interface, but additionally builds a DRBG on top of it, and makes it available via the ISA.
The idea with RISC-V is that users can build their own DRBGs using AES and SHA instructions. By comparison, Intel's implementation of RDRAND covers very few cryptographic applications, since it is not FIPS compliant and practically limited by its AES-128 security level.
It's a polling interface, hence doesn't block. It is supposed to be polled by the OS (or relevant cryptographic runtime in microcontrollers). See the Appendix or https://ia.cr/2020/866 for further rationale.

"trng design" was a bit misworded, right.
I agree that some transitions can be automatized (and things handled) in dedicated IP but the main point still is that the spec state machine severely lacks an "you are not going to get anything until taking {implementation specific} actions" state where that implementation specific action might be an initialization of the peripheral (e.g. rare race condition bug might leave some clocks/peripherals unititialized).
It can be also a catch all, for an:

Implementations do not need to implement DEAD as it may not require an end-user notification;

That allows for a quick detection and logging of the "this should never happen" situations.
Otherwise what is the alternative for defensive programming (except peripheral specific interface)?

"happy debugging in production"?
wait for watchdog violation? Periodic sampling avoids it. How to know the cause of violation afterwards?
make a custom watchdog from a timer and measure time the core is in BIST state? Quite complex as for something that's not going to be tested properly.


doc: Add missing return statement

Added a missing return statement in the EmptyNote component under "Importing Server Actions from Client Components".

Signed the CLA

Signed the CLA.


Migrate to React from Angular

It's gonna be a whole rewrite of UI.
Syndesis UI has proved it could be achieved incrementally. Learn from them and bake into a plan.

Hi @riccardo-forina, we created an Epic here for AtlasMap React migration. Could you review those and comment if you see anything? The toolchain concern #1197 is the most unclear thing from my POV.

Substantially complete - UI tests will be handled by separate issues.


Setting related.toLower = true changes param display

I was playing with related content indices and I set this in my config.toml:
[related]
includeNewer = true
threshold = 0
toLower = true

[[related.indices]]
  name  = "series"
  weight = 200

[[related.indices]]
  name = "topic"
  weight = 200

[[related.indices]]
  name = "title"
  weight = 150

[[related.indices]]
  name  = "kicker"
  weight = 100

[[related.indices]]
  name  = "authors"
  weight = 100

When I did so, the authors became lower case on my pages, presumably because the data underlying the slice was mutated.
What version of Hugo are you using (hugo version)?
Hugo Static Site Generator v0.69.0/extended darwin/amd64 BuildDate: unknown

Title does not lowercase. Without looking at the code, my guess is this because authors is a slice of strings and title is just a string.

Wow, very fast. Thanks!


CI: Update installation in docs-related workflow

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

What does this PR do?
Needed for https://github.com/Lightning-AI/lightning-bolts/pull/833.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@Borda Please have a look when you get a chance!

Closing this in favour of #50.


Enhancement: Separate Light/Dark Mode for Excalidraw WebView

I would appreciate the ability to set a distinct light/dark mode for the Excalidraw webview, independent of the main UI settings. Currently, the webview inherits the mode from the overall UI and makes it so the images you have look inverted, and having a dedicated setting for the webview would enhance personalization options.

Hello @The-Ducktor. That will be a great suggestion. We plan to update this feature in future versions.

Hello @The-Ducktor .
The new version of Excalidraw has been released, which include the feature of set a distinct light/dark mode for the Excalidraw webview.
You can download the new version via in-program updates or manually download here: https://github.com/chocoford/ExcalidrawZ/releases/tag/v0.4.3

Tried it works perfectly


chore: addressed feedback on security assessment

Description
Addressed feedback based on https://github.com/AM-git-hub/tag-security/blob/main/assessments/projects/openfga/self-assessment.md

Closing in favor of https://github.com/openfga/openfga/pull/1456


Implement a returnUrl service to allow users to return to pages that require login

Self explanatory:
ReturnUrl.set({ name: $state.current.name, params: $stateParams }) from a controller that requires the user to log in
ReturnUrl.return() right after signin/signup

This has been resolved in the 0.4.0 branch. #487
This PR can be closed.


[DF-362] ensure internal user properties are not rendered on user page

When on the /dashboard/users page or the /dashboard/users/[id] page, user properties with the Internal resourceType should not be rendered.
From SyncLinear.com | DF-362

/bounty $100

/attempt #580 can I be assigned? @chandlercraig

/attempt #580
Can I be assigned?


How can I import from Google Sheet?

I tried to import from Google Sheet and I did the import method like following.
Excel::import(new BooksImport(), 'https://docs.google.com/spreadsheets/d/1iF3e34ovGoDQMhmUMfmt4vN0AtXrzQj-adYiId5BrDg/edit#gid=0');
It says that "Maatwebsite\Excel\Exceptions\NoTypeDetectedException
No ReaderType or WriterType could be detected. Make sure you either pass a valid extension to the filename or pass an explicit type."
Please give me a solution on how I can be able to import from Google Sheet.

Closing as duplicate

@patrickbrouwers Could you point to the duplicate please, we are also having the need of reading a google sheet file. Right now getting: ZipArchive::getFromName(): Invalid or uninitialized Zip object
Starting import
===============

   ErrorException

  ZipArchive::getFromName(): Invalid or uninitialized Zip object

  at vendor/phpoffice/phpspreadsheet/src/PhpSpreadsheet/Reader/Xlsx.php:303
    299|         // Sadly, some 3rd party xlsx generators don't use consistent case for filenaming
    300|         //    so we need to load case-insensitively from the zip file
    301|
    302|         // Apache POI fixes
  > 303|         $contents = $archive->getFromName($fileName, 0, ZipArchive::FL_NOCASE);
    304|         if ($contents === false) {
    305|             $contents = $archive->getFromName(substr($fileName, 1), 0, ZipArchive::FL_NOCASE);
    306|         }
    307|

      +8 vendor frames
  9   app/Console/Commands/ImportRegistrants.php:48      App\Imports\RegistrantsImport::import("1zlHn9xxxxxx-xxxxx-1E5jyHs", "google", "Xlsx")

      +14 vendor frames
  24  artisan:37
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
root@e9e22e1c412f:/var/www#

Thank you!

You cant import/export directly from Drive. Make sure to store on your own server first.

Hey @patrickbrouwers thank you for replying!. Not sure if I understood completely but yeah if we just upload the xlsx into Drive the library works beautifully, however ideally we allow our clients to modify the content directly from Google Sheets so I went ahead and created a sheet and imported the original xlsx and that's when we started getting the error, looks like whatever format Google is using for its sheets the library do not support it.
Are you referring to import / export programmatically using googleclient which maybe it's possible.
Thanks.

Yes download via google api client first (https://developers.google.com/drive/api/v3/manage-downloads) and then call the import. PhpSpreadsheet is not able to use a google doc url.


Sync to master and squash form stuff.

Initial check-in of form code with history squashed.

using System;

JS has a different implementation of path parsing so I'll need to understand what you changed.

Refers to: libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs:1 in cc9fa0a. [](commit_id = cc9fa0ae8d5441b4ea54fe8213700f134623d630, deletion_comment = False)

using System;

I had a need to get a constant path out--which was inspired by what you told me about the JS implementation.  Basically resolve everything into a sequence of strings or ints.

In reply to: 551278226 [](ancestors = 551278226)

Refers to: libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs:1 in cc9fa0a. [](commit_id = cc9fa0ae8d5441b4ea54fe8213700f134623d630, deletion_comment = False)

Pull Request Test Coverage Report for Build 91822

0 of 0   changed or added relevant lines in 0 files are covered.
58 unchanged lines in 2 files lost coverage.
Overall coverage increased (+1.05%) to 76.606%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder/Adapters/TestFlow.cs
1
72.45%

/libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs
57
80.9%

Totals

Change from base Build 91684:
1.05%

Covered Lines:
5842

Relevant Lines:
7626

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

    protected Task<bool> EndCurrentActionAsync(SequenceContext sequenceContext, CancellationToken cancellationToken = default)

virtual? again, protected member implies you expect children to consume, would they ever override it?

Refers to: libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/AdaptiveDialog.cs:615 in e854b39. [](commit_id = e854b397b6cde24e9692090b5fd04952f5e51054, deletion_comment = False)

    protected Task<bool> EndCurrentActionAsync(SequenceContext sequenceContext, CancellationToken cancellationToken = default)

I didn't change this.  I'm going to leave as is and let the broader issue look at this.

In reply to: 567719936 [](ancestors = 567719936)

Refers to: libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/AdaptiveDialog.cs:615 in e854b39. [](commit_id = e854b397b6cde24e9692090b5fd04952f5e51054, deletion_comment = False)

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3


Prefer IPv4 when resolving, unless IPv6 is specifically requested

As suggested here, this amends Resolve and ResolveUDPAddr to prefer IPv4 addresses unless IPv6 is specifically requested.  As noted in the code comments, this can be particularly important when resolving "localhost" as local servers are unlikely to be listening over IPv6.

LGTM!

Thanks @oxtoacart!


Fix NotificationResponse race condition

Details
For a while, the callback for the NotificationResponse event (i.e: when a push notification is tapped) was usually not being executed. The previous code falsely assumed that the NotificationResponse callback would happen while the app was still in the background, because it is when the event occurs. It did rarely happen this way, because there was a race condition in play between these two responses to this event:

The OS natively brings the app to the foreground.
The JavaScript callback is executed.

The native OS response is almost always faster, so by the time the JS callback executes, the app is in the foreground and we skipped the callback. Instead, we'll only skip the callback for PushReceived events that happen when the app is in the foreground.
Fixed Issues
Fixes (partial) https://github.com/Expensify/Expensify/issues/158830
Tests / QA Steps

(iOS dev only) Launch the app on a physical iPhone device. (SO)
Log into the app on mobile as user A.
Log into the app on another platform as user B.
As user A, open a chat between A and a user other than B.
As user A, background the mobile app
As user B, send a message to user A.
Verify that a push notification appears for user A.
Tap on the notification. Verify that the app opens to the chat between user A and user B (a different chat than you had open when you backgrounded the app).

Tested On

[ ] Web
[ ] Mobile Web
[ ] Desktop
[x] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS
https://user-images.githubusercontent.com/47436092/123183860-52b08a00-d447-11eb-85e4-7c5bdfec74df.MP4
Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging in version: 1.0.73-4🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production in version: 1.0.74-0🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


lstm output shape problem when reshaping lstm input

I'm having trouble understanding what's going on in the following code, in which i'm reshaping the input from (batch_size, features) to (1, batch_size, features), then feeding this to an LSTM with return_sequences=True (i.e. i'm basically turning the batch into time steps).
I'm under the impression that this should output something with shape (1, time_steps, lstm_units), where batch_size == time_steps, and indeed Keras' model summary confirms this, however the actual output has shape (time_steps, time_steps, lstm_units).
Moreover the output is identical across the first dimension.

import numpy as np
import keras.backend as K
from keras.layers import Input, LSTM, Lambda
from keras.models import Model

batch_size = 2

batch_shape = (batch_size, 5)
inp = Input(batch_shape=batch_shape)
re = Lambda(lambda x: K.reshape(x, (1, batch_size, 5)))
lstm = LSTM(1, stateful=True, return_sequences=True)
out = lstm(re(inp))

model = Model(inputs=inp, outputs=out)

model.summary()

x = np.random.random(batch_shape)

y = model.predict(x, batch_size=batch_size)
print("y.shape:", y.shape)
print('y:', y, sep='\n')

This outputs:
_________________________________________________________________
Layer (type)                 Output Shape              Param #
=================================================================
input_1 (InputLayer)         (2, 5)                    0
_________________________________________________________________
lambda_1 (Lambda)            (1, 2, 5)                 0
_________________________________________________________________
lstm_1 (LSTM)                (1, 2, 1)                 28
=================================================================
Total params: 28
Trainable params: 28
Non-trainable params: 0
_________________________________________________________________

y.shape: (2, 2, 1)
y:
[[[-0.11784139]
  [-0.16627716]]

 [[-0.11784139]
  [-0.16627716]]]

As i said the output is identical across the first dimension, i.e. -0.11784139 and -0.16627716 are repeated, which seems suspicious as the input is random.
Why is this happening? Why is y.shape not (1,2,1)?

I don't understand. I tried removing the batch_size in the input shape but the result is the same.
You say the batch_size is assumed not to be change, does that mean my reshape is the problem?

Yes, I think your reshape is problematic. What prevent you to directly use a 3D input? I mean why not skip the reshape layer (reshaping a 2D input as 3D), while directly preparing your input in 3D.

Nothing is preventing me from using directly 3D input, but why is that reshape problematic? There is a conflict between the output shape communicated by Keras and the actual output shape you get based on the input shape, which I don't think there should be.

Your axis of reshape is wrong cahnge
re = Lambda(lambda x: K.reshape(x, (1, batch_size, 5)))
to
 re = Lambda(lambda x: K.reshape(x, (batch_size, 1, 5)))
Keras assume that shapes have format of (batch_size, num_timesteps, num_features/timestep)  so LSTM operates on axis 1 and not 0
Also in future try to post this questions on StackOverflow since this is not an implementation issue and not a bug of Keras

Ok, thanks.


Ganglia - Metric Name Cleanup

minor changes to GangliaReporter to make sure metric names are compatible with the ganglia spec and add an option to use short package names when reporting to ganglia.

I can't merge this, unfortunately -- maybe rebase on development?

My fault.  I'll rebase and resubmit soon.
Matt
On Nov 10, 2011, at 3:48 PM, Coda<EMAIL_ADDRESS>wrote:

I can't merge this, unfortunately -- maybe rebase on development?

Reply to this email directly or view it on GitHub:
https://github.com/codahale/metrics/pull/104#issuecomment-2700897

closing this request to replace it with correct version.


Renaming existing 'master' branches to 'main' under the elyra-ai org

Describe the issue
New repos use 'main' as their default branch instead of 'master' we should make the change as well to remain consistent.
Will require quite a few changes in the documentation, release script and our generic operator (non inclusive list, likely more)
Good candidates to test changes first (prior to the primary repo):
Both repos are archived, doesnt seem to make a lot of sense to update branch names and references in an archived repo
- [ ] https://github.com/elyra-ai/kfp-notebook
- [ ] https://github.com/elyra-ai/airflow-notebook
Primary (this) repo

[x] https://github.com/elyra-ai/elyra

Will need to contact the canvas team about making the switch

[x] https://github.com/elyra-ai/canvas
[x] https://github.com/elyra-ai/pipeline-schemas

Others

[x] https://github.com/elyra-ai/pipeline-editor - done
[x] https://github.com/elyra-ai/examples - done
[x] https://github.com/elyra-ai/community - done
[x] https://github.com/elyra-ai/elyra-package-template - No PR needed
[x] https://github.com/elyra-ai/component-library - PR open
[x] https://github.com/elyra-ai/website - PR open
[x] https://github.com/elyra-ai/pipeline-browser-extension - done
[x] https://github.com/elyra-ai/github-bot - done

Documentation

[x] configure main branch as input for latest doc version https://readthedocs.org/projects/elyra/builds/

Some repositories include files that reference raw GitHub URLs, such as this documentation topic.  Others reference the branch name itself, such as https://github.com/elyra-ai/elyra/blob/master/elyra/kfp/operator.py#L45. Many things will break if we fail to replace any of these references.

Also need to update https://readthedocs.org/dashboard/elyra/advanced/

All branches renamed, closing issue


GPU not working

Hello.
I use original Real-ESRGAN and it uses only the CPU. Although the portable version uses a GPU, it does not suit me. How do I use the GPU on the original version?
Windows 10
CPU - I5 7600K
GPU - GTX 1660TI
Python 3.7.2
CUDA 11.0
My pip-list:
1. absl-py                 1.0.0
2. addict                  2.4.0
3. basicsr                 <IP_ADDRESS>
4. cachetools              4.2.4
5. certifi                 2021.10.8
6. charset-normalizer      2.0.9
7. colorama                0.4.4
8. cycler                  0.11.0
9. dataclasses             0.6
10. facexlib                <IP_ADDRESS>
11. filterpy                1.4.5
12. fonttools               4.28.5
13. future                  0.18.2
14. gfpgan                  0.2.4
15. google-auth             2.3.3
16. google-auth-oauthlib    0.4.6
17. grpcio                  1.43.0
18. idna                    3.3
19. imageio                 2.13.5
20. importlib-metadata      4.10.0
21. kiwisolver              1.3.2
22. llvmlite                0.37.0
23. lmdb                    1.2.1
24. Markdown                3.3.6
25. matplotlib              3.5.1
26. networkx                2.6.3
27. numba                   0.54.1
28. numpy                   1.20.3
29. oauthlib                3.1.1
30. opencv-python           <IP_ADDRESS>
31. packaging               21.3
32. Pillow                  8.4.0
33. pip                     21.3.1
34. protobuf                3.19.1
35. pyasn1                  0.4.8
36. pyasn1-modules          0.2.8
37. pyparsing               3.0.6
38. python-dateutil         2.8.2
39. PyWavelets              1.2.0
40. PyYAML                  6.0
41. realesrgan              <IP_ADDRESS>        z:\2
42. requests                2.26.0
43. requests-oauthlib       1.3.0
44. rsa                     4.8
45. scikit-image            0.19.1
46. scipy                   1.7.3
47. setuptools              60.1.0
48. six                     1.16.0
49. tb-nightly              2.8.0a20211224
50. tensorboard-data-server 0.6.1
51. tensorboard-plugin-wit  1.8.0
52. tifffile                2021.11.2
53. torch                   1.10.1
54. torchvision             0.11.2
55. tqdm                    4.62.3
56. typing_extensions       4.0.1
57. urllib3                 1.26.7
58. Werkzeug                2.0.2
59. wheel                   0.37.1
60. yapf                    0.31.0
61. zipp                    3.6.0

Have you tried install PyTorch from this?
https://pytorch.org/get-started/locally/

Have you tried install PyTorch from this?

I installed the following packages:
pip3 install torch==1.10.1+cu113 torchvision==0.11.2+cu113 torchaudio===0.10.1+cu113 -f https://download.pytorch.org/whl/cu113/torch_stable.html
But I get the following error:

Error CUDA out of memory. Tried to allocate 294.00 MiB (GPU 0; 6.00 GiB total capacity; 1.79 GiB already allocated; 2.27 GiB free; 1.94 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
If you encounter CUDA out of memory, try to set --tile with a smaller number.
Testing 1 1
Traceback (most recent call last):
File "inference_realesrgan.py", line 128, in
main()
File "inference_realesrgan.py", line 103, in main
if len(img.shape) == 3 and img.shape[2] == 4:
AttributeError: 'NoneType' object has no attribute 'shape'

You are running out of memory you might want to use
--tile 265 in your command :)

You are running out of memory you might want to use
--tile 265 in your command :)

--tile disfigures the image with a grid

--tile works fine the grid issue is with -s (aka scale settings) so you cant use x4 model and set scale to 2.

I thought everything was portable (I am running into similar issue) I am in a WSL environment running conda with the same
pip3 install torch==1.10.1+cu113 torchvision==0.11.2+cu113 torchaudio===0.10.1+cu113 -f https://download.pytorch.org/whl/cu113/torch_stable.html
I am however getting
./esgran/realesrgan-ncnn-vulkan -i oh-jeez.png -o oh-jeez-upscale.png -s
2 -v
[0 llvmpipe (LLVM 12.0.0, 256 bits)]  queueC=0[1]  queueG=0[1]  queueT=0[1]
[0 llvmpipe (LLVM 12.0.0, 256 bits)]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 llvmpipe (LLVM 12.0.0, 256 bits)]  fp16-p/s/a=1/0/0  int8-p/s/a=1/0/0
[0 llvmpipe (LLVM 12.0.0, 256 bits)]  subgroup=4  basic=0  vote=0  ballot=0  shuffle=0
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.

WSL is not with GPU support tested it and it won't work cause WSL do not support Vulcan API's

sidenote that might interest you kodxana, I was able to get https://github.com/nerdyrodent/VQGAN-CLIP to work in WSL and nerdyreodent's diffusion CLIP repo led me here.

WSL is not with GPU support tested it and it won't work cause WSL do not support Vulcan API's

I'm gonna try a few more things then likely fail, give up and download the Windows binaries. If for some horrific reason those don't work I will open a new issue with log dumps 😄

sidenote that might interest you kodxana, I was able to get https://github.com/nerdyrodent/VQGAN-CLIP to work in WSL and nerdyreodent's diffusion CLIP repo led me here.

It's cause it's use VSGAN that it's using pytorch version of resergan. Only the Vulcan implementation has issues with colab and WSL.


Update README.md

I have updated the README to include which version of the specification is currently being targeted.

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


release(antelope): update snapcraft.yaml

Automated changes by create-pull-request GitHub action

closing, we should cleanup the stable branches first


docs(gcs): role Storage Object Admin is required but not mentioned

docs(gcs): Storage Object Admin is required but not mentioned
In this PR:

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

Issues reference:

https://github.com/ducktors/turborepo-remote-cache/issues/95

Checklist:

[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

[ ] Have you lint your code with pnpm lint locally prior to submission?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran build with pnpm build of your changes locally?
[ ] Have you successfully ran tests with pnpm test of your changes locally?

I force pushed to edit commit message for commitlint

@all-contributors add @Klaitos for doc

Test fails on codeclimate report. I merge manually

true


dart2js fails test language/regress_18713

class T<X> {
  final Type tType = X;
  Type get getTType => X;
}

class S<Y> {
  final Type sType = Y;
  Type get getSType => Y;
}

class TS<A, B> = T<A> with S<B>;

main() {
  var ts = new TS<int, String>();
  print(ts.sType);
  print(ts.tType);
  print(ts.getSType);
  print(ts.getTType);
}

The above code is essentially the test case tests/language/regress_18713_test.dart. The expected output is
String
int
String
int
but dart2js prints
String
int
int
int

(this is being tracked directly in .status files, so closing the redundant bug entry)


scFoundation on GEARS with pretrained model used

Hi there, thanks for the nice work!
I am trying to follow your code on perturbation prediction task.
Based on your provided code
pre_in = x.clone().reshape(num_graphs, self.num_genes+1)
x = x.reshape(num_graphs, self.num_genes+1)[:,:-1]
the last column in pre-in should be total counts. x is removed of total counts, which means that only expression values are retained in x.
However, when I look for the pretrained model to be used, the bin type in the provided one in the github is 'auto_bin'. does that mean total counts is not used in the input to get the pretrained model?
But if I would like to use it to get embedding for GEARS, what should I do with the total counts?
Also, it seems that the pre_in is directly used as input for the pretrained model. does this mean that the input data is already reformatted to have 19264 genes?

also, the 'pad_token_id': 103, 'mask_token_id': 102 are stored in the config file, while there are genes that have the same token id with them based on the csv file.

Hi,
Yes, the input format should have 19264 genes, please see our tutorial. 'auto_bin' also uses the mean total counts. the pad and mask token is processed with the gene expression values, not with the gene name, so some genes have the same token ID.

thanks for the response!
If I understand correctly, when the gene expression values are used, then the position of the genes should be important. So, does this mean every time the gene ids should be the same as what you provided in OS_scRNA_gene_index.csv to indicate the positions of those genes? For the total counts, what position ID should it have? Is it 19264?

Another related question. I found that in the GEARS tutorial, to process the input expression data and gene id. there is a gatherdata function:

I understand that the pad for expression value could be as provided in the config file, where the pad is 103. but for the gene ids, should they be ids ranging from 0 to 19264? then how could 103 is used as pad token here as well? Just correct me if I am wrong.
Many thanks!


[Bug]: The archive source does not support object storage and needs to be hidden.

ODC version
ODC433
OB version
independent
What happened?
The archive source does not support object storage and needs to be hidden.
What did you expect to happen?
。
How can we reproduce it (as minimally and precisely as possible)?
。
Anything else we need to know?
No response

Fixed In Commit cde598c983709bbebf6b34952101d749d03336aa
------
艺泽
Wed Dec 18 17:36:39 2024 +0800


Speed up github actions builds

We have introduced github actions to do some builds. While it is in testing mode only, and it does not actually do much, if we plan to support it in the long run, we need revise its performance. Currently the build takes around 1.45-2h, which is a lot; especially compared to around 30 min for the circleci.
So the idea is to investigate and see how to do parallel builds here also.

PR for this here

@ryanjbaxter we can close this one

@ryanjbaxter  this can be closed also now...


Not able to install the theme

Hi, tried installing and getting below error.  Can you please help?

D:\GDrive\hugo\sae>hugo serve
Building sites . ERROR 2018/10/23 18:09:57 Error while rendering "taxonomy" in "
": template: _default\list.html:11:4: executing "frontmenu" at <partial "nav.htm
l" .>: error calling partial: template: partials/nav.html:39:19: executing "part
ials/nav.html" at <.Paginate>: error calling Paginate: 'pager size' must be a po
sitive integer
ERROR 2018/10/23 18:09:57 Error while rendering "taxonomyTerm" in "": template:
categories\terms.html:8:4: executing "frontmenu" at <partial "nav.html" .>: erro
r calling partial: template: partials/nav.html:39:19: executing "partials/nav.ht
ml" at <.Paginate>: error calling Paginate: 'pager size' must be a positive inte
ger
ERROR 2018/10/23 18:09:57 Error while rendering "home" in "": template: index.ht
ml:3:4: executing "frontmenu" at <partial "nav.html" .>: error calling partial:
template: partials/nav.html:39:19: executing "partials/nav.html" at <.Paginate>:
error calling Paginate: 'pager size' must be a positive integer
ERROR 2018/10/23 18:09:57 Error while rendering "taxonomyTerm" in "": template:
taxonomy\terms.html:8:4: executing "frontmenu" at <partial "nav.html" .>: error
calling partial: template: partials/nav.html:39:19: executing "partials/nav.html
" at <.Paginate>: error calling Paginate: 'pager size' must be a positive intege
r
ERROR 2018/10/23 18:09:57 Error while rendering "404" in "": template: 404.html:
6:4: executing "frontmenu" at <partial "nav.html" .>: error calling partial: tem
plate: partials/nav.html:39:19: executing "partials/nav.html" at <.Paginate>: er
ror calling Paginate: 'pager size' must be a positive integer
Total in 277 ms
Error: Error building site: logged 5 error(s)

My mistake.  It was due to some file corruption issue, hence closing the issue.
Thanks for this beautiful theme.

Can I ask what the file corruption issue was and how you got around it? I've managed to reproduce this myself.


Host '<IP_ADDRESS>' is not allowed to connect to this MySQL server

Hello, i really don't know what to do anymore so i'm writing here to get some help. Long story short, i have installed native docker on osx sierra, made a new laravel app, cloned laradock, and started apache2 + mysql + phpmyadmin. I can type localhost and see my app but whenever i try to connect to my database via sequel pro i get a the error from the title and via phpmyadmin, i get  connection refused.
I tried to ssh inside the mysql container and login as root via terminal but i get the following error:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
I tried to make another clean project, i tried to rebuild with no cache, and i even tried to start only the mysql container without anything, i am really out of ideas and maybe i'm missing something, it's my first docker experience.
Thanks!

I'm having the same issue as you. I don't know what the issue is and I've enquired about it in Gitter chat.

I just want to add that i've tried on a secondary mac and i get the same error.

@RobertCristian @ELD  have you guys tried docker volume rm mysql and rebuild the container?

@manshoor Yep, I have removed the volume and rebuilt the container several times. No luck.

hm.., when i run docker volume rm mysql i get Error response from daemon: get mysql: no such volume. But i have tried with docker-compose down which deletes everything.
my mysql config from docker-compose.yaml:
        build:
            context: ./mysql
            args:
                - MYSQL_DATABASE=homestead
                - MYSQL_USER=homestead
                - MYSQL_PASSWORD=secret
                - MYSQL_ROOT_PASSWORD=root
        volumes:
            - mysql:/var/lib/mysql
        ports:
            - "3306:3306"```

can you share your mysql logs? don't add the -d argument and see why mysql is dying.
OR
try with totally refreshing the docker by resetting it to default and pull all the images and build again.
last option would be go back to mysql 5.6

mysql_1               | 2016-11-27T18:50:04.056781Z 0 [Note] mysqld (mysqld 5.7.16) starting as process 1 ...
mysql_1               | 2016-11-27T18:50:04.059003Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql_1               | 2016-11-27T18:50:04.059052Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1               | 2016-11-27T18:50:04.059060Z 0 [Note] InnoDB: Uses event mutexes
mysql_1               | 2016-11-27T18:50:04.059066Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_1               | 2016-11-27T18:50:04.059072Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
mysql_1               | 2016-11-27T18:50:04.059078Z 0 [Note] InnoDB: Using Linux native AIO
mysql_1               | 2016-11-27T18:50:04.059251Z 0 [Note] InnoDB: Number of pools: 1
mysql_1               | 2016-11-27T18:50:04.059350Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql_1               | 2016-11-27T18:50:04.060329Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql_1               | 2016-11-27T18:50:04.065273Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_1               | 2016-11-27T18:50:04.066516Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_1               | 2016-11-27T18:50:04.078854Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
mysql_1               | 2016-11-27T18:50:04.091509Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql_1               | 2016-11-27T18:50:04.091654Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql_1               | 2016-11-27T18:50:04.143611Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql_1               | 2016-11-27T18:50:04.144295Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
mysql_1               | 2016-11-27T18:50:04.144329Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
mysql_1               | 2016-11-27T18:50:04.144535Z 0 [Note] InnoDB: Waiting for purge to start
mysql_1               | 2016-11-27T18:50:04.197161Z 0 [Note] InnoDB: 5.7.16 started; log sequence number 2533496
mysql_1               | 2016-11-27T18:50:04.197539Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql_1               | 2016-11-27T18:50:04.197753Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysql_1               | 2016-11-27T18:50:04.199251Z 0 [Note] InnoDB: Buffer pool(s) load completed at 161127 18:50:04
mysql_1               | 2016-11-27T18:50:04.201533Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
mysql_1               | 2016-11-27T18:50:04.201950Z 0 [Note] Server hostname (bind-address): '<IP_ADDRESS>'; port: 3306
mysql_1               | 2016-11-27T18:50:04.201979Z 0 [Note]   - '<IP_ADDRESS>' resolves to '<IP_ADDRESS>';
mysql_1               | 2016-11-27T18:50:04.202000Z 0 [Note] Server socket created on IP: '<IP_ADDRESS>'.
mysql_1               | 2016-11-27T18:50:04.214393Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:50:04.214454Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:50:04.214477Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:50:04.214489Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:50:04.215027Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:50:04.218167Z 0 [Note] Event Scheduler: Loaded 0 events
mysql_1               | 2016-11-27T18:50:04.218284Z 0 [Note] Execution of init_file '/etc/mysql/startup' started.
mysql_1               | 2016-11-27T18:50:04.218741Z 1 [ERROR] 1396  Operation DROP USER failed for 'homestead'@'%'
mysql_1               | 2016-11-27T18:50:04.218850Z 0 [Note] Execution of init_file '/etc/mysql/startup' ended.
mysql_1               | 2016-11-27T18:50:04.218913Z 0 [Note] mysqld: ready for connections.
mysql_1               | Version: '5.7.16'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
mysql_1               | 2016-11-27T18:51:40.052632Z 0 [Note] Giving 0 client threads a chance to die gracefully
mysql_1               | 2016-11-27T18:51:40.052702Z 0 [Note] Shutting down slave threads
mysql_1               | 2016-11-27T18:51:40.052718Z 0 [Note] Forcefully disconnecting 0 remaining clients
mysql_1               | 2016-11-27T18:51:40.052733Z 0 [Note] Event Scheduler: Purging the queue. 0 events
mysql_1               | 2016-11-27T18:51:40.052815Z 0 [Note] Binlog end
mysql_1               | 2016-11-27T18:51:40.053365Z 0 [Note] Shutting down plugin 'ngram'
mysql_1               | 2016-11-27T18:51:40.053415Z 0 [Note] Shutting down plugin 'BLACKHOLE'
mysql_1               | 2016-11-27T18:51:40.053429Z 0 [Note] Shutting down plugin 'partition'
mysql_1               | 2016-11-27T18:51:40.053439Z 0 [Note] Shutting down plugin 'ARCHIVE'
mysql_1               | 2016-11-27T18:51:40.053448Z 0 [Note] Shutting down plugin 'MEMORY'
mysql_1               | 2016-11-27T18:51:40.053456Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
mysql_1               | 2016-11-27T18:51:40.053464Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
mysql_1               | 2016-11-27T18:51:40.053473Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
mysql_1               | 2016-11-27T18:51:40.053481Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
mysql_1               | 2016-11-27T18:51:40.053490Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
mysql_1               | 2016-11-27T18:51:40.053529Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
mysql_1               | 2016-11-27T18:51:40.053539Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
mysql_1               | 2016-11-27T18:51:40.053548Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
mysql_1               | 2016-11-27T18:51:40.053556Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
mysql_1               | 2016-11-27T18:51:40.053564Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
mysql_1               | 2016-11-27T18:51:40.053571Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
mysql_1               | 2016-11-27T18:51:40.053580Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
mysql_1               | 2016-11-27T18:51:40.053587Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
mysql_1               | 2016-11-27T18:51:40.053595Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
mysql_1               | 2016-11-27T18:51:40.053603Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
mysql_1               | 2016-11-27T18:51:40.053635Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
mysql_1               | 2016-11-27T18:51:40.053645Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
mysql_1               | 2016-11-27T18:51:40.053653Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
mysql_1               | 2016-11-27T18:51:40.053662Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
mysql_1               | 2016-11-27T18:51:40.053670Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
mysql_1               | 2016-11-27T18:51:40.053678Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
mysql_1               | 2016-11-27T18:51:40.053686Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
mysql_1               | 2016-11-27T18:51:40.053694Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
mysql_1               | 2016-11-27T18:51:40.053702Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
mysql_1               | 2016-11-27T18:51:40.053709Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
mysql_1               | 2016-11-27T18:51:40.053717Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
mysql_1               | 2016-11-27T18:51:40.053751Z 0 [Note] Shutting down plugin 'INNODB_CMP'
mysql_1               | 2016-11-27T18:51:40.053761Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
mysql_1               | 2016-11-27T18:51:40.053769Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
mysql_1               | 2016-11-27T18:51:40.053777Z 0 [Note] Shutting down plugin 'INNODB_TRX'
mysql_1               | 2016-11-27T18:51:40.053785Z 0 [Note] Shutting down plugin 'InnoDB'
mysql_1               | 2016-11-27T18:51:40.053912Z 0 [Note] InnoDB: FTS optimize thread exiting.
mysql_1               | 2016-11-27T18:51:40.054038Z 0 [Note] InnoDB: Starting shutdown...
mysql_1               | 2016-11-27T18:51:40.156959Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
mysql_1               | 2016-11-27T18:51:40.157248Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 161127 18:51:40
mysql_1               | 2016-11-27T18:51:41.303846Z 0 [Note] InnoDB: Shutdown completed; log sequence number 2533524
mysql_1               | 2016-11-27T18:51:41.305578Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
mysql_1               | 2016-11-27T18:51:41.305604Z 0 [Note] Shutting down plugin 'MyISAM'
mysql_1               | 2016-11-27T18:51:41.305616Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
mysql_1               | 2016-11-27T18:51:41.305622Z 0 [Note] Shutting down plugin 'CSV'
mysql_1               | 2016-11-27T18:51:41.305628Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
mysql_1               | 2016-11-27T18:51:41.305646Z 0 [Note] Shutting down plugin 'sha256_password'
mysql_1               | 2016-11-27T18:51:41.305651Z 0 [Note] Shutting down plugin 'mysql_native_password'
mysql_1               | 2016-11-27T18:51:41.305782Z 0 [Note] Shutting down plugin 'binlog'
mysql_1               | 2016-11-27T18:51:41.306678Z 0 [Note] mysqld: Shutdown complete
mysql_1               |
mysql_1               | 2016-11-27T18:52:56.456211Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql_1               | 2016-11-27T18:52:56.457019Z 0 [Note] mysqld (mysqld 5.7.16) starting as process 1 ...
mysql_1               | 2016-11-27T18:52:56.459164Z 0 [Note] InnoDB: PUNCH HOLE support available
mysql_1               | 2016-11-27T18:52:56.459192Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1               | 2016-11-27T18:52:56.459194Z 0 [Note] InnoDB: Uses event mutexes
mysql_1               | 2016-11-27T18:52:56.459196Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mysql_1               | 2016-11-27T18:52:56.459198Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
mysql_1               | 2016-11-27T18:52:56.459199Z 0 [Note] InnoDB: Using Linux native AIO
mysql_1               | 2016-11-27T18:52:56.459435Z 0 [Note] InnoDB: Number of pools: 1
mysql_1               | 2016-11-27T18:52:56.459553Z 0 [Note] InnoDB: Using CPU crc32 instructions
mysql_1               | 2016-11-27T18:52:56.460595Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
mysql_1               | 2016-11-27T18:52:56.465638Z 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_1               | 2016-11-27T18:52:56.466835Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mysql_1               | 2016-11-27T18:52:56.478190Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
mysql_1               | 2016-11-27T18:52:56.494552Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql_1               | 2016-11-27T18:52:56.494703Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
mysql_1               | 2016-11-27T18:52:56.546024Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql_1               | 2016-11-27T18:52:56.546674Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
mysql_1               | 2016-11-27T18:52:56.546693Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
mysql_1               | 2016-11-27T18:52:56.546924Z 0 [Note] InnoDB: Waiting for purge to start
mysql_1               | 2016-11-27T18:52:56.599523Z 0 [Note] InnoDB: 5.7.16 started; log sequence number 2533524
mysql_1               | 2016-11-27T18:52:56.600039Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql_1               | 2016-11-27T18:52:56.600361Z 0 [Note] Plugin 'FEDERATED' is disabled.
mysql_1               | 2016-11-27T18:52:56.602230Z 0 [Note] InnoDB: Buffer pool(s) load completed at 161127 18:52:56
mysql_1               | 2016-11-27T18:52:56.603445Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
mysql_1               | 2016-11-27T18:52:56.603992Z 0 [Note] Server hostname (bind-address): '<IP_ADDRESS>'; port: 3306
mysql_1               | 2016-11-27T18:52:56.604018Z 0 [Note]   - '<IP_ADDRESS>' resolves to '<IP_ADDRESS>';
mysql_1               | 2016-11-27T18:52:56.604091Z 0 [Note] Server socket created on IP: '<IP_ADDRESS>'.
mysql_1               | 2016-11-27T18:52:56.619428Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:52:56.619474Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:52:56.619497Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:52:56.619506Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:52:56.620224Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
mysql_1               | 2016-11-27T18:52:56.623879Z 0 [Note] Event Scheduler: Loaded 0 events
mysql_1               | 2016-11-27T18:52:56.624051Z 0 [Note] Execution of init_file '/etc/mysql/startup' started.
mysql_1               | 2016-11-27T18:52:56.624569Z 1 [ERROR] 1396  Operation DROP USER failed for 'homestead'@'%'
mysql_1               | 2016-11-27T18:52:56.624724Z 0 [Note] Execution of init_file '/etc/mysql/startup' ended.
mysql_1               | 2016-11-27T18:52:56.624811Z 0 [Note] mysqld: ready for connections.
mysql_1               | Version: '5.7.16'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)```

ok, so what is the docker ps  says because according to this [Note] mysqld: ready for connections
in mysql container try mysql -u root -p root

Same as in my first post: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

So it looks like the MySQL root user can't be accessed with a password. If you're inside the MySQL container, you need to login as root without a password (mysql -u root). Once there, you can manually create the Homestead database and the user accordingly.
I think the issue has something to do with the startup script. It fails on dropping the user and if you modify the command to use MySQL 5.7's DROP USER IF EXISTS syntax, it fails on creating the homestead user. I'm not sure what the cause is. I'm playing around with it to troubleshoot the creation of the image so that it doesn't crash on the first startup. It seems that the startup script runs fine the second time you start the image, though.

Just to further document what I'm looking at, this line jumps out at me in the logs for the mysql container:
mysql_1               | 2016-11-27T20:46:21.614859Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.

Looks like that's why we can't log into the root user with the password. It wasn't set up with one.
Secondly, it looks like the startup script is failing:
mysql_1               | ERROR 1396 (HY000) at line 1: Operation CREATE USER failed for 'homestead'@'%'

Additionally, after building the container, this is what docker-compose ps displays:
      Name                    Command               State    Ports
------------------------------------------------------------------
laradock_mysql_1   docker-entrypoint.sh mysql ...   Exit 1

I had the same problem, try removing first line from mysql/startup ( DROP USER 'homestead';
). Worked for me.

@kamilcios That doesn't work for me. After building the image and starting up the container, the first time it still exits prematurely. Instead of failing on dropping the user, it fails on trying to create the user.
From looking into the history, I think the culprit is #437 and #438. I just can't figure out the chronology because one reverts the other but the master branch doesn't reflect a reversion. I don't understand it.

@kamilcios Could you do a PR for your fix?
@ELD I merged it by mistake the first-time so I reverted it ASAP, I then had discussion with @Mahmoudz then merged it back in. My apologies for the confusion, the mobile github site is the bane of my existence.
This seems to be creating many problems, I could remove the PR but I think it's worth trying to keep the functionality of creating custom users (if possible). That being said if a majority doesn't care about the feature, I'll definitely remove it.

@philtrep Okay, that makes sense. Yeah, it looks like a better way to go about creating users, it's just that the startup script may error out and I think when that happens, the entire MySQL server dies. I'm not positive though.
Definitely worth trying to make it work better.

This works for me. It didn't crash on the first create for me anymore which it did before.
Now phpmyadmin is complaining on first boot about not getting addrinfo. But second run it works fine.
DROP USER IF EXISTS 'MYSQL_USER'; CREATE USER 'MYSQL_USER'@'%'; CREATE DATABASE IF NOT EXISTS MYSQL_DATABASE; GRANT ALL ON MYSQL_DATABASE.* TO 'MYSQL_USER'@'%' IDENTIFIED BY 'MYSQL_PASSWORD';

created the pull request just now.

@Blaasvis 's PR is #451. I'll wait a few hours for people to review it before merging.

Resolved by #451


Rule request: informative-docs

TypeScript code being linted
/**
 * Request metadata.
 */
interface IRequestMetadata {
    /**
     * The user id
     */
    userId: string;
}

with tslint.json configuration:
{
    "rules": {
        "completed-docs": true
    }
}

Actual behavior
Many teams require all things be documented, such as with TSLint core's completed-docs. The idea of requiring code be well-documented is nice, but you end up with the above useless comments.
Expected behavior
It'd be nice to have a rule that requires the documentation for something not be equivalent to just the thing's name. If we strip out non-alphabet characters, common words such as "the" or "a", and lowercase everything, they shouldn't be the same.
Posting here instead of TSLint core, as I expect this is too opinionated for the core ruleset.

Hi, I would like to work on this if no one currently working on it. Thanks

I have a working version of this internally and will post it here soon.


Check tls not found in Catalog

I am trying to track TLS certificates but is failing to load tls check.

brand new cluster in GKE
datadog installed using helm, all defaults values
created example config to check google.com certs

===============================
Datadog Cluster Agent (v7.40.1)
===============================
...
=========
Collector
=========
...
  Loading Errors
  ==============
    tls
    ---
      Core Check Loader:
        Check tls not found in Catalog

from helm:
clusterAgent:
  confd:
    tls.yaml: |-
      instances:
        - server: https://google.com/
          name: google.com

directly from pod:
root@datadog-cluster-agent-5f8c5cb555-hft9m:/etc/datadog-agent/conf.d# cat tls.yaml
instances:
  - server: https://google.com/
    name: google.com

also from pod:
root@datadog-cluster-agent-5f8c5cb555-hft9m:/# cd /var/log/datadog/
root@datadog-cluster-agent-5f8c5cb555-hft9m:/var/log/datadog# ll
total 28
drwxrwxr-x 2 dd-agent root  4096 Nov 29 10:32 ./
drwxr-xr-x 4 root     root  4096 Nov  9 15:49 ../
-rw-rw-r-- 1 dd-agent root     0 Nov  9 15:49 .placeholder
-rw-r--r-- 1 root     root 16544 Nov 29 11:05 cluster-agent.log
root@datadog-cluster-agent-5f8c5cb555-hft9m:/var/log/datadog# grep -i tls cluster-agent.log
2022-11-29 10:32:35 UTC | CLUSTER | ERROR | (pkg/collector/scheduler.go:201 in getChecks) | Unable to load a check from instance of config 'tls': Core Check Loader: Check tls not found in Catalog
2022-11-29 10:32:35 UTC | CLUSTER | ERROR | (pkg/collector/scheduler.go:201 in getChecks) | Unable to load a check from instance of config 'tls': Core Check Loader: Check tls not found in Catalog
2022-11-29 10:32:35 UTC | CLUSTER | ERROR | (pkg/collector/scheduler.go:248 in GetChecksFromConfigs) | Unable to load the check: unable to load any check from config 'tls'
root@datadog-cluster-agent-5f8c5cb555-hft9m:/var/log/datadog#

Describe the results you expected:
get remaining cert days in TLS dashboard

hello @FlorentClarret,
thank you for your quick reply. Done: https://help.datadoghq.com/hc/requests/1019650

hello @FlorentClarret,
thank you for your quick reply.  I'm closing this issue then.

for reference, the fix was adding cluster_check: true
like:
clusterAgent:
confd:
  <INTEGRATION_NAME>.yaml: |-
    cluster_check: true
    init_config:
      - <INIT_CONFIG>
    instances:
      - <INSTANCES_CONFIG>

example:
clusterAgent:
  confd:
    tls.yaml: |-
      cluster_check: true
      instances:
        - server: https://google.com/
          name: google.com

Glad to hear that's fixed!

Hi,
I added this 'cluster_check' field, and the redisdb stopped getting spotted altogether. any workaround?


WIP:trying the new solvers

Hello! This is the PR to show how changing the API would affect poliastro.

The new API does not support callbacks as the previous one. Before it was the function called at every step, now it requires some event (something becomes zero). So for now I removed callbacks stuff.

In test_propagate_to_date_has_proper_epoch I removed cowell, because maintaining the rtol=1e-10 makes run of this test fantastically long.

In test_sample.py I had to mark two cowell tests xfail, because somehow the required precision 1e-7 is not achieved. Perhaps I'll manage to fix that at some point.

In the new API, the jac parameter is only required by some solvers, and RK45 is not one of them, so it is now used anywhere. But this is a useful function for later.

I could not manage to fix the precision problem by changing the integration method.

To my opinion, if we need to refactor and use the new API, we could say that the Cowell method is used only for perturbation stuff, and mean_motion is used for analytical gravitational orbits.

Hello! I rolled back a bit. Seems like using method='Radau' resolves all the issues. I returned tests back and removed some xfails. Seems a lot better now.

Sorry, I made the change myself :) Now you will have to git stash && git fetch origin && git merge origin/RK45vsDORPRI835 && git stash pop before you go on, otherwise you will have ugly error messages on push.

Also, it would be nice to have a precision comparison with the old solver. For example, using this snippet:
import numpy as np
from astropy import units as u

from poliastro.twobody import Orbit
from poliastro.bodies import Earth
from poliastro.twobody.propagation import cowell

np.set_printoptions(precision=20)

r0 = [-2384.46, 5729.01, 3050.46] * u.km
v0 = [-7.36138, -2.98997, 1.64354] * u.km / u.s

initial = Orbit.from_vectors(Earth, r0, v0)

def accel(t0, state, k):
    v_vec = state[3:]
    norm_v = (v_vec * v_vec).sum() ** .5
    return 1e-5 * v_vec / norm_v

final = initial.propagate(3 * u.day, method=cowell, ad=accel)
print(final.r)
print(final.v)

I get:
>>> print(final.r)
[ 13179.39566663877121754922 -13026.25123408228319021873
  -9852.66213692844394245185] km
>>> print(final.v)
[ 2.78170542314378943516  3.21596786944631274352  0.16327165546278937791] km / s

Regarding the poor performance of Radau that we discussed privately, I found an interesting plot:

(from https://ieeexplore.ieee.org/document/5641330/)
So we are not the only ones to notice a slowdown when using an implicit scheme for a non-stiff problem.

Also, before merging this:

Rebase the branch on current master: git fetch upstream && git rebase upstream/master && git push -f origin RK45vsDORPRI835
Write a brief wiki page explaining the options that we considered and their problems, so we don't forget

And then I'll hit the button. Let's see if we can accelerate this before the next release, but we will likely need https://github.com/numba/numba/issues/2952 fixed for that.

Aaaaaaaaaaaaaaand I'm merging! :tada: Thanks @nikita-astronaut!

Opened discussion to contribute this code directly to SciPy: https://github.com/scipy/scipy/pull/9290


Squirrel With A Gun

How do i inject this into the game? I cant seem to find anything on usage and placing it into directory does nothing.

just use any dll injector u find (any thats not a virus btw)


Opt-in for <select> customizability

It's necessary that control customizability be opt-in rather than on by default in order to not break compatibility with older sites and to avoid issues where capabilities of the customizable controls be limited, e.g. the customizable <select> must not escape the bounds of windows due to security concerns.
Opt-in for custom control behavior for <input> type like <input type="range"> will be done by introducing new elements, e.g. <range>, for the customizable version, while <input> will remain the same.
For <select>, since unlike <input> the parser does not prevent it from being parsed with child DOM nodes, we've proposed that it's not necessary to create a new element for it and we could instead do opt-in through an attribute like <select custom="">.
There are downsides to relying on an attribute though:

@mfreed7 pointed out that we'd need to deal with the fact that the custom attribute could be added/removed dynamically, which adds complexity.  Parsing is particularly concerning here, since the attribute would change the parsing rules for the subtree of the <select>.  Is there any scenario where a <select> could have script change it to custom when we're in the middle of parsing its subtree?

@travisleithead raised this specific concern about the dynamic case: consider a dynamically-created <select> (via document.createElement()), when the custom attribute must be set using setAttribute(). When should the transition to the custom behavior be applied? Applying it at the point of setAttribute() would be inconsistent with how other elements like <input type="range"> work when created dynamically; typically the transformation would occur when the element was appended to the DOM. But, this means that for a dynamically created <select>, the developer would have to wait until the <select> is appended to the DOM before calling attachShadow(), since attachShadow() throws for a non-custom <select>.

If we're minting new elements for all the customizable <input> types then it seems odd to do something different just for <select>.

On the other hand there are downsides to adding a new element for <select>:

What would we name it?  @mfreed7 suggested <selectmenu>, I don't have any other ideas at the moment.
@gregwhitworth pointed out that some might be opposed to a new element that is almost 1:1 with the current one but had more capabilities.

Overall, introducing a new element and thereby sidestepping the problems of dynamic opt-in seems better to me.

From the beginning I've been in favor of having new elements for the new controls as it also allows us to keep some native ones and specific needs for certain capabilities (window escape, etc). As we discussed in our explainer I'm also a fan of the built-in parts, while maybe leveraging WC parts under the hood being elements themselves as well so it is 100% apparent what is standard/ships with the UA and what is user land code.
I think this is a good discussion for WHATWG as I want to raise the open state discussion as well and that should only hang off the element that is decided here? Is there a reason this discussion should remain here @dandclark ?

From the beginning I've been in favor of having new elements for the new controls as it also allows us to keep some native ones and specific needs for certain capabilities (window escape, etc).

This would still be possible if we used an attribute.  <select custom=""> would get all the new stuff, but <select> would work the same as it does now and would not have limitations on window escape etc.  That said, at this point I'm also in favor of using new elements instead of an attribute.

I think this is a good discussion for WHATWG as I want to raise the open state discussion as well and that should only hang off the element that is decided here? Is there a reason this discussion should remain here @dandclark ?

I'm fine with moving this discussion to WHATWG.

Awesome, I'll spin up an issue for this - much appreciated.

Opened it here: https://github.com/whatwg/html/issues/5791 @dandclark can you close this out?


Missing references in initialization lists

When there is an initialization list like:
auto var = {blah, blah};

We're not emitting references to blah. Example in LLVM

Originally reported by a customer.

It looks like this was a backend issue and not an indexer issue, because we weren't surfacing precise intel correctly for external symbols. That same link works now.


Add Open Graph Image Meta Tag

I tweeted a blog post and noticed it didn't have an image in the preview.
This takes an image from the page front matter if possible, otherwise defaults to the author image. This allows for previews on twitter, discord etc to have an image.
I've tested it locally and on GitHub pages and it seems to work as intended.

Thanks @ArcaneIRE for your contribution!


[firebase_admob] Banner Ad Horizontal Positioning

Adding the ability to horizontally adjust the ads banner location by specifying an offset from the centre.
Description

This PR allows the user of firebase_admob to specify an offset in pixels from the horizontal centre of the banner using

horizontalCenterOffset

The current behaviour allows the user only to specify an anchor top or bottom with an offset from the anchor. But it doesn't allow an offset from the horizontal centre. This PR will add that ability.
The motivation behind the change is to support split screen layout for tablets where ads banner could reside on one side of the screen.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Hey @amirh & @bparrishMines,
Do you think this would be merged or there are plans that would affect this behaviour to prevent it from being merged in the future? It will be nice to have this as part of the next firebase_admob update.
Thanks,


MFA forgets return_to during setup

MFA forgets the return_to URL during setup.
STR

Enable MFA for a user but don't setup yet
Logout
Go to /oauth2/authorize...
Login
Setup MFA

I expect to be redirected back to OAuth, but I got to dashboard
Potential patch
redirection_after_mfa_setup.patch.txt

thanks a lot javi, you're the best ✨
we've deployed the patch and works well :)

Leaving this open to track the master fix. :)


Review Bruce's "How it works" page text and add/edit as needed

Seattle will host some of the text content in their CMS. Bruce will send How it works page text and Chris will review and add/edit for clarity, then resubmit to Bruce for review.

This was completed and the text added to Seattle's page hosting the FAQ


Please publish new release to pypi

Hello, I find main branch support app.start_worker, but not find in 0.2.8 release, can you publish new release to pypi?

same, trying to use from pypi


Datagrid Storybook warnings: invalid DOM nesting

What package(s) are you using?

[X] Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)

Detailed description

Describe in detail the issue you're having.

When running Storybook locally, I see console warnings across many stories.
This is not necessarily a comprehensive list. E.g.:
http://localhost:3000/?path=/story/ibm-products-components-datagrid-datagrid-canary--infinite-scroll
Warning: validateDOMNesting(...): <thead> cannot appear as a child of <div>.

Warning: validateDOMNesting(...): <div> cannot appear as a child of <table>.

Warning: validateDOMNesting(...): <tr> cannot appear as a child of <div>.

Warning: validateDOMNesting(...): <div> cannot appear as a child of <tbody>.

http://localhost:3000/?path=/story/ibm-products-components-datagrid-datagrid-canary--selectable-row
Warning: validateDOMNesting(...): <th> cannot appear as a child of <div>.

Warning: validateDOMNesting(...): <div> cannot appear as a child of <tr>.

Is this issue related to a specific component?

Yes, these all appear across multiple stories for the Datagrid

What did you expect to happen? What happened instead? What would you like to see changed?

We should not see these console warnings at all.

What browser are you working in?

Chrome, latest.

What version of the @carbon/ibm-products (or @carbon/ibm-cloud-cognitive) package are you using?

v2.11
Steps to reproduce the issue

Fork and clone @carbon/ibm-products to your local machine.
yarn to install packages.
yarn storybook to run Storybook.
Open the browser to each of the URLs listed above.
Open the browser's dev tools.
Select the "Console" tab to view the console warnings.

Fixed one instance of invalid DOM nesting with expandable rows, thinking we can take a similar approach with other instances. Essentially, any direct child of a tr is required to either be a td or th element. Then any other elements required can be inside of either the td or th.

a few got fixed with this #5716

We've been investigating TanStack Table, a third-party, open-source offering, which provides extensive data table capabilities surpassing what our Carbon Datagrid offers. It provides much more flexibility and customization. TanStack Table is headless which means it can easily be added alongside Datagrid component in your product or application. The benefits of more flexibility for product teams and less maintenance for Carbon makes it a win win. Lastly, it is available in multiple frameworks including React and Web Component so it provides an option to non-React product teams.
For these reasons, we have decided to transition from building our own custom table component to using an example-based approach with TanStack Table. Datagrid will still exist in our library for existing teams but we are announcing the deprecation* of the Datagrid component in v2.54.0 release so teams can begin to work through the transition. Details about how to use both Datagrid and TanStack together can be found here.
*Deprecation means that no new features will be added however sev 1 and sev 2 bugs will be supported.


Error: Failed to load the JS script of the agent

Hello, I get this error:
Error: Failed to load the JS script of the agent
We're on version
"@fingerprintjs/fingerprintjs-pro-angular": "1.1.0"
There is a problem with AdBlock, can you help me with solution, maybe there is a couple of ways to fix it (proxy integration it`s best but not in my case)

Hi, @bohdanKatiukha. Yes, ad blockers can disrupt API requests to Fingerprint domains. The recommended solution is using cloud proxy integrations to route all Fingerprint traffic through your domain. You can learn more here: https://dev.fingerprint.com/docs/protecting-the-javascript-agent-from-adblockers
May I ask what is preventing you from using a cloud proxy integration? Another potential solution is to work with our support team to host and continually update the JS agent script yourself. In practice, this can lead to users missing important JS Agent updates, lowering the effectiveness of visitor identification, so we do not generally recommend it.

Hi, @bohdanKatiukha! Yes, ad blockers can disrupt API requests to Fingerprint domains. The recommended solution is using cloud proxy integrations to route all Fingerprint traffic through your domain. You can learn more here: https://dev.fingerprint.com/docs/protecting-the-javascript-agent-from-adblockers你好， ！是的，广告拦截器可以中断对指纹域的 API 请求。推荐的解决方案是使用云代理集成来路由通过您的域的所有指纹流量。您可以在这里了解更多信息：https://dev.fingerprint.com/docs/protecting-the-javascript-agent-from-adblockers
May I ask what is preventing you from using a cloud proxy integration? Another potential solution is to work with our support team to host and continually update the JS agent script yourself. In practice, this can lead to users missing important JS Agent updates, lowering the effectiveness of visitor identification, so we do not generally recommend it.请问是什么阻止您使用云代理集成？另一个潜在的解决方案是与我们的支持团队合作，自行托管并不断更新 JS 代理脚本。实际上，这可能会导致用户错过重要的 JS Agent 更新，从而降低访客识别的有效性，因此我们一般不推荐这样做。
Have a nice day!祝你今天过得愉快！

it works when i prevent ad plugin, thanks.


browser.executeScript doesn't take a callback

I'm submitting a bug report

Library Version:
1.0.2

Please tell us about your environment:

Operating System:
OSX 10.12

Node Version:
7.9.0

NPM Version:
4.2.0

Browser:
Chrome

Language:
ESNext

Current behavior:
Running e2e tests from aurelia-skeleton skeleton-esnext-webpack project result in the following

Expected/desired behavior:

Clone aurelia-skeleton and use skeleton-esnext-webpack
At time of writing there are two minor blockers that need to be fixed to continue

update package.json for invalid babel-loader "next" tag

"devDependencies": {
...
  "babel-loader": "^7.0.0"
...
}

update .babelrc.js for invalid "useBuiltIns": true (I think the correct option now is "usage")

"presets": [
...
        "useBuiltIns": "usage"
...
]

npm install
npm start -- e2e

What is the expected behavior?
browser.executeScript should not cause an exception

What is the motivation / use case for changing the behavior?
With the change from browser.executeAsyncScript to browser.executeScript in #4 , it appears that a callback is not available.
Locally reverting #4 so that executeAsyncScript is used fixes the issue.  I don't know the motivation behind using executeScript so I'm hesitant to create the change in a PR.

Hey, thanks for the report. Indeed, I investigated the same problem. I'm working on a solution. For now, feel free to use version 1.0.1.


Invalid typings

"itty-router": "3.0.8"

This should be fixed in 3.0.9+, thanks to a fix by @jahands! :)
Please reopen if that's not the case!!


CSE-162 explorer slow blocks

https://issues.serokell.io/issue/CSE-162
The backend work for CSE-162. The code could be better, I need to check onApplyPageBlocksExplorer, but I presume this is a general idea?

You can see, there is a lot of repetition. I can't make types align, tried with something like this:
class BlockKey k where
    newBlocksMapF :: (SscHelpersClass ssc) => (NE (Block ssc) -> M.Map Epoch [HeaderHash])
    getKeyBlocksF :: (MonadDBRead m) => (k -> m (Maybe [HeaderHash]))
    putKeyBlocksF :: (k -> [HeaderHash] -> ExplorerOp)

instance BlockKey Epoch where
    newBlocksMapF = epochBlocksMap
    getKeyBlocksF = DB.getEpochBlocks
    putKeyBlocksF = DB.PutEpochBlocks

instance BlockKey Page where
    newBlocksMapF = pageBlocksMap
    getKeyBlocksF = DB.getPageBlocks
    putKeyBlocksF = DB.PutPageBlocks

In these functions there is a general shape that can be reused in all the project, it's in the form k -> [v]. Since the results of BListener end up in the key value database, things align nicely.
In this case it's k -> [HeaderHash], where k € {Page, Epoch}.
What we could have is:

a way to produce keys [Blund] -> [k]
a way to produce mapping from key to values [Blund] -> k -> [v]

This would be general enough for most DB operations I guess, we can add specializations (on the function above) like:

k -> v
[v]

It's just an idea, but it evolves from these functions and general functions could be moved to BListener.

@ksaric you should also merge cardano-sl-0.5-rc to master.


Importing v4.0.0 into an ES6 module breaks the JS build on IE11

[x] bug

Swiper Version: V4.0.0

Platform/Target and Browser Versions: IE11 on a Windows machine running 8.1 / 10.

What you did
import Swiper from 'swiper';

class PageProductDetail {
  constructor() {
    this.swiper = new Swiper('.swiper-container', {
        pagination: {
          el: '.swiper-pagination',
          clickable: true,
        },
        a11y: true,
      });
  }
}

export default PageProductDetail;

Expected Behavior
This simplified example above produces a working slider on every browser/machine apart from IE11 on Windows machines. The slider should work as expected on the page.
Actual Behavior
The imported Swiper library appears to break my JS bundle, breaking all JavaScript on Windows machines using IE11. I'm getting no errors in my console so I feel like something must be breaking the build. I'm using Webpack 2 and babel in this project.

Hard to understand if there are no errors. If you are using Webpack try importing UMD version instead:
import Swiper from 'swiper/dist/js/swiper.js`;

@nolimits4web Thanks for your time, this seems to have fixed the issue 👍 🙌