Slow Run Async Method

We have updated our neo4j version to v4 and changed all of the return types of methods to Task and made all of them asynchronous,
now we are dealing with huge decrease of speed in running queries.

Neo4j version or client version? Or indeed both? Are you using bolt? Do you have an example?

Yes I am using bolt and neo4j version 4.1.1.
I am usin asp.net mvc, for authenticate sample code
protected override bool AuthorizeCore(HttpContextBase httpContext)
{
if(string.IsNullOrEmpty(httpContext.User.Identity.Name))
return false;
if (allowedroles == null)
return false;
        if (allowedroles != null && allowedroles.Count() > 0)
        {
            var hasRoleTask = Task.Run(()=>_roles.CheckInRolesOfUser(httpContext.User.Identity.Name, allowedroles));//.Wait(TimeSpan.FromMinutes(1));
            if (hasRoleTask.Result)
            {
                return true;
            }
            return false;
        }
        }

and so neo4j cypher code :
    public async Task<bool> CheckInRolesOfUser(string userName, string[] roleTitle)
    {
        var q = client.Cypher
            .Match("(user:User)-[r:USER_HAS_ROLE]-(role:Role)")
            .Where("user.UserName = $userName").WithParam("userName", userName)
            .AndWhere("role.Title IN $roleTitle").WithParam("roleTitle", roleTitle)
            .With("distinct count(role) as cnt");

        var count = await q.Return(cnt => cnt.As<int>()).ResultsAsync;

        if (count.SingleOrDefault() > 0)
            return true;
        return false;
    }

I've done some testing, and I've run 1,000,000 queries using the <IP_ADDRESS> and 4.0.0 drivers and largely I'm not seeing a

huge decrease in speed

It's worth noting that I was doing some heavy processing at the end of the 4.0.0 run - hence the increase in the chart. The averages are pretty similar:

and a difference of 50-60ms over 1000 queries equates to 0.06ms per query - which could be accounted for by CPU blips, me doing more things etc.
The range of values is not that different either:

Test wise, it wasn't complex, merely running MATCH (m:Movie) RETURN m - in C#:
var results = await client.Cypher.Match("(m:Movie)").Return(m => m.As<Movie>()).ResultsAsync;
var list = results.ToList();

The ToList() will execute and pull down the entire resultset each time.
This was executed 1000 times, with the total MS elapsed being stored, with each of those runs, being run 1000 times per driver.
All timings were done after the client had connected, and only covered the execution of the query.

OK, I'm going to close this for now, obviously feel free to reopen if you have new stuff for me to consider!


npm run build-minified error

Getting the following error when using npm run build-minified:
ERROR in ./src/browser/components/main.jsx
Module parse failed: /Applications/MAMP/htdocs/node_modules/fb-sleep-stats/src/browser/components/main.jsx Line 34: Unexpected token <
You may need an appropriate loader to handle this file type.
|     render() {
|         var isAuthenticated = this.state.isAuthenticated;
|         var loginButton =
|         return (
|
@ ./src/browser/main.js 1:0-32
any idea?

Im stuck at the same stage, getting this error..
Output filename not configured.
npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build-minified"
npm ERR! node v4.3.1
npm ERR! npm  v2.14.12
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build-minified: webpack --progress --optimize-minimize
npm ERR! Exit status 255
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-minified script 'webpack --progress --optimize-minimize'.
npm ERR! This is most likely a problem with the fb-sleep-stats package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     webpack --progress --optimize-minimize
npm ERR! You can get their info via:
npm ERR!     npm owner ls fb-sleep-stats
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Theden/npm-debug.log
MacBook-Pro:~ Theden$

same

What version are you running. This has been developed on Node 4. I'm pretty sure it also works on 0.12.

MacBook-Pro:~ Theden$ node -v
v4.3.1
MacBook-Pro:~ Theden$

Kevins-MacBook-Pro-2:fb-sleep-stats Kevin$ node -v
v5.6.0

MacBook-Pro:fb-sleep-stats oskar$ node -v
v4.0.0

$ cat npm-debug.log  0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli   '/usr/local/bin/npm', 1 verbose cli   'run', 1 verbose cli   'build-minified' ] 2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild-minified', 'build-minified', 'postbuild-minified' ] 5 info prebuild-minified<EMAIL_ADDRESS>6 info build-minified<EMAIL_ADDRESS>7 verbose unsafe-perm in lifecycle true 8 info<EMAIL_ADDRESS>Failed to exec build-minified script 9 verbose stack Error<EMAIL_ADDRESS>build-minified: webpack --progress --optimize-minimize9 verbose stack Exit status 1 9 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:214:16) 9 verbose stack     at emitTwo (events.js:87:13) 9 verbose stack     at EventEmitter.emit (events.js:172:7) 9 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14) 9 verbose stack     at emitTwo (events.js:87:13) 9 verbose stack     at ChildProcess.emit (events.js:172:7) 9 verbose stack     at maybeClose (internal/child_process.js:817:16) 9 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 10 verbose pkgid<EMAIL_ADDRESS>11 verbose cwd /Users/oskar/fb-sleep-stats 12 error Darwin 15.0.0 13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build-minified" 14 error node v4.0.0 15 error npm  v2.14.2 16 error code ELIFECYCLE 17 error<EMAIL_ADDRESS>build-minified:webpack --progress --optimize-minimize 17 error Exit status 1 18 error Failed at the<EMAIL_ADDRESS>build-minified script 'webpack --progress --optimize-minimize'. 18 error This is most likely a problem with the fb-sleep-stats package, 18 error not with npm itself. 18 error Tell the author that this fails on your system: 18 error     webpack --progress --optimize-minimize 18 error You can get their info via: 18 error     npm owner ls fb-sleep-stats 18 error There is likely additional logging output above. 19 verbose exit [ 1, true ]

a trailing tab had made its way into my configuration, all fixed now

How did you manage to fix it exactly ?

Did you have any errors when running npm install ?

removed everything including node and re-installed. Now it works. Likely it was a security problem with my company's network.


fix(#423): resolve setting dark theme

Resolve #423

@JayKan looks good to me, can you rebase this PR with the latest code?

awesome! thanks a lot @JayKan 👍


Fix Curl Code Generator for Multipart Form File

fixes #2224
Description
This PR fixes the issue #2224.
To resolve this issue i searched in httpsnippet code to understant how the lib expectes the file. Like the image below we should map a fileName property instead of value for files

Before:

After:

Contribution Checklist:

[X] The pull request only addresses one issue or adds one feature.
[X] The pull request does not introduce any breaking changes
[X] I have added screenshots or gifs to help explain the change if applicable.
[X] I have read the contribution guidelines.
[X] Create an issue and link to the pull request.

Closing this PR as another PR that resolves the issue has already been merged. Thank you for taking the time to work on this, @leoferreiralima!


change registry for node-exporter and prometheus

Host node-exporter and prometheus on PAI's registry.

Coverage increased (+13.5%) to 65.11% when pulling d1c071ad7ee6027e0c04fd482ce525f626a4aee9 on hao/change_registry_of_node-exporter_prometheus into b8ec5687887b25bdcfb4a66f56676cdfe2458ad2 on master.


Fix #139

First of all, Storybook has it's on zoom controls and these do not change the scale property of the chart. So using these will break almost everything. This PR do not fix this issue.
This PR fixes the following issue: after changing the scale property of the chart, movement and drop of nodes won't properly reflect the position of the cursor as these do not calculate with the scale property.
What this PR does?

Sets the scale for the Draggable component used by nodes, to allow the react-draggable library to calculate with the scale property. Also uses delta for node movements, instead offset.
On drop, calculates using the scale property. I've also changed the order of operations a bit, as offset and position are totally different things and cannot be calculated in a single step.

I tried it and it works. 👍


Have the dependency between decorator and index be more explicit

I have a particular use case of this module where I need to support running AMD-ification via babel on this module in order to have the code work in my environment. That process (using the babel plugin transform-es2015-modules-amd) works, but then the AMD-ified decorator.js tries to require the file "./" which blows up. The fix is quite simple - to specify that "./" is actually referring to "./index".

Coverage remained the same at 94.821% when pulling 32f584907195529cf6d7eb35e64143f70802a028 on lidawang:lw-fix-cyclical-dependency-amd into d7e67f59905335a3c9338fbd4c652e9d55cfeaa3 on jasonslyvia:master.

fair point

released 2.0.4


Simple Firewall Configuration

This is an attempt to improve on https://github.com/splunk/ansible-role-for-splunk/pull/114 striving for simplicity while also maintaining future portability for people who want to add more ports or decrease the current port pool. The changes at a glance are:

New port format to specify protocol for modularity
Inferring of FW type: defaults to UFW and if RHEL uses Firewalld
Added default firewall ports per group var
Checks to see if firewall package is installed and service is running and enabled
Using Firewalld Services instead of ephemeral commands
Handlers for reloading firewalls and merged into single yaml file

Hopefully this is something that will be more useful. Comments appreciated - maybe we can move the init definition of splunk_firewall_ports to group_vars/all.yml but that's just an aesthetic choice I think.

@arcsector Thanks for creating this PR. I've wanted this for some time.
I was going through this, and I have a few thoughts. The group_vars for Indexers, Heavy Forwarders and search heads have a lot of things in common. How about we put the common ones in full.yml? That way we can avoid duplicate declarations.
In general, I wanted to add some vars that disable the web interface for IDX and HF as the default, as well as splunktcp for SH. I'm not sure if this will complicate things even more or not, but what are your thoughts?
Side note. Can you please for your repo directly from this one instead of the one from @zyphermonkey? This will prevent conflicts, and will be easier to be in sync with this upstream repo.

I was going through this, and I have a few thoughts. The group_vars for Indexers, Heavy Forwarders and search heads have a lot of things in common. How about we put the common ones in full.yml? That way we can avoid duplicate declarations.

I have the common ones in defaults/main.yml, where the splunk_firewall_ports var is initialized - this will be applied to all other systems that have this in common (license, deploy, shdeployer, idx manager), then the only repeats are in the group_vars for the cluster components.

In general, I wanted to add some vars that disable the web interface for IDX and HF as the default, as well as splunktcp for SH. I'm not sure if this will complicate things even more or not, but what are your thoughts?

I would like to do that, but I feel like that should be a separate PR which adds that config not just in the firewall config but also in web.conf. Also note I don't have splunktcpin opened for the SHC.

Side note. Can you please for your repo directly from this one instead of the one from @zyphermonkey? This will prevent conflicts, and will be easier to be in sync with this upstream repo.

Will do.

In my estimation Firewalld services are much more useful in terms of their overall introspection capabilities as well as their ease of modification and legibility. In addition, services are the best-practice in firewalld for things that are supposed to be associated with a given process.
Say for example we're not just installing splunk on here, but also mysql. I can have a service file for splunk and then one for mysql which identify each port as being associated with that application, which i can then make modifications to or disable/enable independently of one another. A more targeted approach for extensible environments with a lot of firewall configs.

Why aren't we just using the idempotent firewall module? Trying to manage XML templates doesn't add anything and just makes maintenance more complicated.

As @arcsector said. Although using the firewall plugin would may seem to be the simpler way, but when configuring multiple ports for a specific application, the recommended method from the OS side is services.
Also, running the firewall-cmd command is a lot slower, and running it multiple time every time slows down the playbook, which is slow enough as it is.
Any experienced sys-admin would know exactly where to look and what to look for.


E2EE API v5: How to list cards?

Hi, I'm trying to debug why my app is getting errors retrieving cards. I cannot view card data on the dashboard. I tried the latest CLI and there does not seem to be a way to interact with the cards service. Is there any supported way to view card data short of writing my own program?

Hi, Max. For now, card management is only possible through our APIs and SDKs. We're aware of the need and will make it possible at some point.

@cardoso Ok thanks. Through the API is there a way to list all card identifiers? Or is it assumed that I am storing my UUIDs in an external system and relying on that to enumerate the cards stored in the virgil cards service?

@maxogden for now, you'd have to store all identities to list all cards, but this is not the most common use-case, so in general we don't assume you're storing identities.  We're currently working on an admin-level API to list all cards.
Can you be more specific about the errors you mentioned? Perhaps I can help.


Fixing the antialiasing of pixel images in image picker

Fixes https://github.com/Microsoft/pxt-arcade/issues/80

Ignore that build failure


Proposed update to Azure Synapse Links for SQL Server 2022 instructions

I was in the 'Ask the Experts' meeting for Synapse and they said that you no longer have to create the expected schema in advance. I asked the question because I have been able to do it without creating the schemas.
With this in mind, I suspect the below sentence about creating the expected schema can be removed now. Probably a good idea to double check first:
"You also need to create a schema if your expected schema is not available in target Synapse SQL database."

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

ID: e6048145-f276-6bc0-d27e-a1fc0134d7d9
Version Independent ID: 1a575901-2a65-f94c-0d81-a806454cdaaf
Content: Create Azure Synapse Link for SQL Server 2022 (Preview) - Azure Synapse Analytics
Content Source: articles/synapse-analytics/synapse-link/connect-synapse-link-sql-server-2022.md
Service: synapse-analytics
Sub-service: synapse-link
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

#assign:@SnehaGunda

@kevchant Thank you for pointing out. I confirmed with our team and submitted a PR above to delete that line.

#please-close


Don't build RockDB?

oxrocksdb-sys currently builds rocksdb from scratch (as far as I can tell), which dominates the build times for the projects in which we are using oxigraph. Instead it would be preferable if it can detect and use an already built version of rocksdb provided by the system.
As I've seen that oxrocksdb-sys is forked from librocksdb-sys, which already had some code in place to use a system-provided version, I'm wondering what the reasoning for doing so was. I'd also be interesting to know whether there are any plans to move to "upstream" librocksdb-sys and whether that is something that I could possibly help out with?

Instead it would be preferable if it can detect and use an already built version of rocksdb provided by the system.

Yes, that would be much better indeed.

As I've seen that oxrocksdb-sys is forked from librocksdb-sys, which already had some code in place to use a system-provided version, I'm wondering what the reasoning for doing so was.

I wanted to customized the C RocksDB bindings to be able to expose to C/Rust some transaction related functions and better error values than just a plain strings. See this directory. This make stuff like detection of transaction conflicts much easier on the Rust side (no need to use hugly string comparisons).
I would love to reuse directly librocksdb-sys but for building these customized bindings I need to link to the C++ code so to simplify the build step I just choose to fork the sys library and tweak it. But if there is a clean way to do otherwise, it would be much better.

Thanks for answering so swiftly and providing some context!

I wanted to customized the C RocksDB bindings to be able to expose to C/Rust some transaction related functions and better error values than just a plain strings. See this directory.

I see - that makes sense. I'm not the biggest C/C++ buff, but from what I can tell that is something that actually needs to be compiled into the library, so with that change it actually makes sense not to use a precompiled version of the library.

0.4.0-alpha.1 adds the rocksdb-pkg-config feature that uses pkg-config to link with an existing rocksdb binary


[Suggestion] Widget support

Original issue 94 created by patrick.conwell on 2011-08-04T15:33:04.000Z:
Pretty self-explanatory, I think it would be nice to have a home screen widget that displays the code.
To be a bit more specific, I would like to be able to click "add widget", then "Select account", then have a 4x1 widget that shows the code for selected account.
(Sorry if this is not the appropriate place for suggestions. I couldn't find anywhere else to post this.)

Here we are, years later, still no widget. Oh well, I guess that means it's time to migrate to Authy.

and.. another year later still no widget, can someone tell me google's definition of short-term?

Comment order got screwed up, so copying this from the first comment:
--
Not related to this product. Please reopen in https://github.com/google/google-authenticator-android if applicable.
--
That said, I think it' pretty clear (though I'm not on that team, so I have no info outside of this public info) that it was on their roadmap, but maybe not so much on their current one.

Has there been any progress on this in the last couple years?

google/google-authenticator-android#10


Why drv NULL needs a double pointer?

As we can see in 6a7755ef1

This is because a pointer arg is passed by value, not reference, so the change doesn't survive the scope of the function.
See http://stackoverflow.com/questions/16299394/c-assign-pointer-to-null

@naveedhd @bit-pirate FYI and as a reference for us.


extension Eject all disks

Description
When using Eject All i get a message that a disk I don't have mounted, cannot be ejected. I thinks it is always the same ID. When unmounting the usual way through finder, all is fine.
Steps To Reproduce
MBA 2022 M2 MacOS 14.4
Current Behaviour
error

Expected Behaviour
no error

This issue is not related to the API or extensions. Could you please use the Send Feedback command inside Raycast or use the #help or #bugs channel in our Slack Community 😊


Add Java 9

https://docs.oracle.com/javase/9/whatsnew/toc.htm#JSNEW-GUID-C23AFD78-C777-460B-8ACE-58BE5EA681F6
http://openjdk.java.net/projects/jdk9/
Although, I don't see it on pkgsrc atm

Oracle jre/jdk 9 have been uploaded to http://packages.nanobox.io/2017/11/base/


Validate required headers

Validate that every CSV in an upload has all the headers required for that file, and not any extraneous ones.
Pivotal story: 90225820

LGTM


Prepended user name may introduce special characters

....which are invalid for OpenShift project names
For instance my user name is<EMAIL_ADDRESS>

fixed 3e33b823286c19890cb9b67249478523ee639b53


feat(AlgebraicGeometry/EllipticCurve/DivisionPolynomial): compute degrees of division polynomials

[x] depends on: #10814
[ ] depends on: #10843

I merged master in this branch; please merge if it looks good.

Starting working on the new approach again ...

This condenses the eight natDegree/coeff_even/odd_preΨ'_even/odd lemmas, but I think we still can't avoid the natDegree/coeff_preΨ'_add_* lemmas in the proof of natDegree_coeff_preΨ'? Maybe I'm missing something...

See my latest commit for more details.

Pushed another commit and I think you can handle the rest! Getting back to my own PRs ...

@Multramate Have you tried to clean up the rest of my branch? If not, I'll try to see if I can golf the subsequent computations today.

@Multramate Have you tried to clean up the rest of my branch? If not, I'll try to see if I can golf the subsequent computations today.

Thanks for waiting! This is now ready to be reviewed again.

Thanks!
bors merge


[EDN] Missing SUM_STS register?

Description
In EDN doc it is written that:

To ensure that the most recently enabled EDN will get next priority for physical entropy, poll the BOOT_INST_ACK field in the SUM_STS register before enabling the following EDN.

However, it seems that the SUM_STS register is not documented, and I cannot find it either in the RTL code (I'm a SW guy, so I may have missed it :-))
It is also documented in the test plan @ csrng_commands
Does this register still exist? If not, what is the recommended way to ensure enabling the second EDN is done at the right time?

@moidx for visibility and guidance.

I think this feature got dropped for Earlgrey because on that chip only one EDN instance (u_edn0) needs boot-time entropy. The other EDN instance (u_edn1) is not used during boot, according to the current ROM code (rom_start.S and test_rom_start.S).
@msfschaffner / @alphan please correct me if that's wrong, but I think for Earlgrey / Discrete no action (other than updating the doc; see below) is required here.
Now for Integrated, I think the necessary information can be extracted from the MAIN_SM_STATE CSR. In boot mode, the FSM will go Idle -> BootLoadIns -> BootLoadGen -> BootInsAckWait and pause in that state until CSRNG has acknowledged the Instantiate command for boot mode. When that has happened, it will go BootCaptGenCnt -> BootSendGenCmd -> BootGenAckWait and pause in that state until CSRNG has acknowledged the Generate command for boot mode. When that has happened, it will go BootPulse -> BootDone. So SW can poll the MAIN_SM_STATE CSR and as soon as its value is 'past' BootInsAckWait, CSRNG has acknowledged the Instantiate command for boot mode. This CSR can be accessed through the DIF with
https://github.com/lowRISC/opentitan/blob/9b65162cae65aa75c90ba268034971a4b364b888/sw/device/lib/dif/dif_edn.h?plain=1#L328-L329
Note that the returned state value has no numeric ordering; the encoding is defined here:
https://github.com/lowRISC/opentitan/blob/f6c35d8ded24c338c3e3a3cfa7dd1d64da3e2e86/hw/ip/edn/rtl/edn_pkg.sv?plain=1#L29-L49
@rivos-eblot If this solution works for current SW needs, I'll update the EDN doc accordingly and suggest we create an issue to implement a DIF function that handles this.

@andreaskurth  I guess it could work. In this case, MAIN_SM_STATE should no longer being called a debug register I believe, since it may be required for regular use. This qualifier is why I was not really sure we could use it as a replacement for SUM_STS.
I guess that fixing the doc should also address #17654 (see https://opentitan.org/book/hw/ip/edn/index.html#example-topology). Despite being documented as an example, it makes things a bit confusing as it seems that doing sequential EDN initialization at boot time is required.

I can confirm that in boot mode the expectation is that only EDN0 will be used. The ROM_EXT will have to switch the entropy blocks to continuous mode before enabling EDN1.  This is because software may be required to run KAT tests on the entropy_src conditioner and csrng before enabling FIPS mode of operation.  FIPS mode of operation is only needed before we start using entropy in crypto operations (e.g. keygen).

@andreaskurth agreed, no RTL change is needed for discrete. The DIF solution sounds good to me - I would however update the docs as @rivos-eblot suggested and modify the description of the MAIN_SM_STATE register so that it does not sound like it's used for debug only.


libudev is no longer on CI for some reason

wtf:
https://github.com/tosc-rs/mnemos/actions/runs/11203664817/job/31141248431#step:5:305

oh this is because more stuff depends on crowtty, which needs libudev. derp.


Page flashes when navigating between tree entries

Search terms

flashing, rendering, tree, navigation
Expected Behavior
Selecting a different entry in the navigation sidebar does not cause a visible re-render of the tree
Actual Behavior
Selecting a different entry in the navigation sidebar causes a visible re-render of the tree
Steps to reproduce the bug

This can be reproduced on the official Typedoc API page: https://typedoc.org/api/index.html
In Chrome and Firefox. It is less noticeable on more powerful devices, but quite apparent on low-end and midrange devices.
This impacts the user experience.
Screencast from 2024-01-29.webm
The same thing happens with Typedoc versions from 0.25.1 (tested locally). It is not reproducible with 0.25.0.
I'd appreciate any help on this, or any input on possible config changes to improve it :)
Environment

Typedoc version: 0.25.7
TypeScript version: 5.2.2
Node.js version: v18
OS: Ubuntu

0.25.0 wrote the entire navigation tree to every page in the generated docs. For large projects, this could mean your generated docs being several gigabytes in size rather than 100mb, so 0.25.1 changed it.
We could hide the entire page until the navigation loads, with a <noscript> override to not hide it, which is what the default-modern-theme does...

This is due to the deferred loading of the main.js script and changing state of folders / accordions based on local storage state. It existed before the new navigation effort as well.

Well that was a bit of an adventure I'd rather not repeat... people who think frontend is fun are insane.
I first tried just hiding the page body until the navigation loaded like DMT. This is mostly fine, but really sucks on slow network connections (firefox's regular 2G throttle setting) since it results in a 3-10 second slower page load when loading without a cache than TypeDoc's current method.
I played around with the different throttle options and delays and the best tradeoff that I arrived at is to:

With an inline script, hide the entire page (use an inline script rather than in main.js because otherwise the page might load enough to render for a split second, then hide itself)
In the same script, set a 500ms timeout. If the navigation hasn't loaded within this time, then it almost certainly isn't cached, and is taking some time to load, so show the page to avoid making people on really slow connections wait longer than they absolutely have to.
When the navigation loads and has been rendered to the page, show the page if it hasn't already been shown.

Yeah.. That is a little bit of a pain, but comes with the territory of adding dynamic elements to a static site. It sounds like things are robust enough. Can you mark this new inline script with an id so that it can be queried easily.
The DMT likely needs to provide a custom solution still, but I'll take a look at getting it closer to what you have come up with.

@Gerrit0 thanks a lot for your efforts, really appreciate it! 😃  From my perspective, this change improved the UX quite a bit.


Video freezed when seek continuously for some time

When i seek video randomly for some time video player stops playing video it is freezed. I am playing .m3u8 video from online api.

can u add a demo video for reference


Array out of bound

Please use the search functionality before reporting an issue. Also take a look at the closed issues!
Issue description:
Steps to reproduce:

Version (make sure you are on the latest version before reporting):
Forge:
Mekanism:
Other relevant version:
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
[gist/pastebin/etc link here]

Need some actual details.


nixos/prometheus-sabnzbd-exporter: use LoadCredential for apiKeyFile

Description of changes
This PR adds an abstraction for using systemd's LoadCredential to grant the service access to supplied credential files. Especially for users of nixops and/or those who want to specify multiple servers to monitor, using this module will be much more straight forward, as they won't have to deal with credential file permissions themselves. The improvements should be backwards compatible.
See the discussion on my previous PR for more details.
Maintainer ping: @WilliButz
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg test prometheus-exporters.sabnzbd


[For Review Purpose Only-Do not Merge] Add Barebones Parser for Glibc Importer

This PR addresses #1362.
Parser has been added in order to review the parser for GLIBC Importer.
@TG1999 and @pombredanne please have a look.

Please Specify what version range should be passed

First draft for importer published.

@harsh098 closing this PR, feel free to open this once it's ready for review


Add the KFP v2 example and update the tutorial

What do these changes do?

Add the KFP v2 benchmark test.
Update the tutorial.

Related issue number
Fixes #1586

Hi @sighingnow, I tested the kfp v1 and kfp v2 again and reduced the affect of file cache, pulling image and scheduling etc. I think the current result is more convincing. Could you please take another review? Thanks.

I think the current result is more convincing. Could you please take another review? Thanks.

Merged.


Improve home page

Current home page:

Aim:

make home page less wordy.
Include an image.

Remove the headers. Include cantered image under the nav bar keep the what is cardiomyopathy text.

Done


test: add performance test

It looks fairly flaky to commit it as a test. I am gonna close it and keep it as a reference in case we decide to land this.


Error when pulling images from remote hosts with Registry:2.3 & Docker 1.10

Hi,
Since docker upgrade to 1.10, I can't no more pull images from remote docker hosts.

When trying to pull an image in my private registry from local docker, it's OK
When trying to pull an image in my private registry from remote docker hosts, it stays with message "retrying in X seconds" and never succeed to pull my images

Registry configuration:
version: '2'

services:
    registry:
        restart: always
        image: registry:2
        container_name: registry
        environment:
            REGISTRY_STORAGE: s3
            REGISTRY_STORAGE_S3_REGION: eu-west-1
            REGISTRY_STORAGE_S3_BUCKET: XXXXXXXXX
            REGISTRY_STORAGE_S3_ACCESSKEY: XXXXXXXXXX
            REGISTRY_STORAGE_S3_SECRETKEY: XXXXXXXXXXX
            REGISTRY_HTTP_TLS_CERTIFICATE: /conf/domain.crt
            REGISTRY_HTTP_TLS_KEY: /conf/domain.key
            REGISTRY_AUTH: htpasswd
            REGISTRY_AUTH_HTPASSWD_PATH: /conf/auth
            REGISTRY_AUTH_HTPASSWD_REALM: Registry Realm
        ports:
            - "5000:5000"
        volumes:
            - /etc/docker-registry:/conf

Docker server running Registry:
docker info
Containers: 15
 Running: 10
 Paused: 0
 Stopped: 5
Images: 448
Server Version: 1.10.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 561
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 14.72 GiB

docker remote host:
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 7
Server Version: 1.10.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 130
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.16.0-60-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.33 GiB

Error when pulling images from remote host:
docker pull docker-1:5000/jenkins-slave
Using default tag: latest
latest: Pulling from jenkins-slave
d4bce7fd68df: Retrying in 5 seconds
a3ed95caeb02: Retrying in 5 seconds
816152842605: Retrying in 5 seconds

docker logs registry:
<IP_ADDRESS> - - [15/Feb/2016:17:28:33 +0000] "GET /v2/jenkins-slave/blobs/sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4 HTTP/1.1" 307 344 "" "docker/1.10.1 go/go1.5.3 git-commit/9e83765 kernel/3.16.0-60-generic os/linux arch/amd64"
time="2016-02-15T17:28:34Z" level=info msg="response completed" go.version=go1.5.3 http.request.host="docker-1:5000" http.request.id=278ef888-7440-490c-ac45-ef1f72ce955b http.request.method=GET http.request.remoteaddr="<IP_ADDRESS>:49500" http.request.uri="/v2/jenkins-slave/blobs/sha256:d4bce7fd68df2e8bb04e317e7cb7899e981159a4da89339e38c8bf30e6c318f0" http.request.useragent="docker/1.10.1 go/go1.5.3 git-commit/9e83765 kernel/3.16.0-60-generic os/linux arch/amd64" http.response.contenttype="application/octet-stream" http.response.duration=471.622036ms http.response.status=307 http.response.written=338 instance.id=34fa54fc-9cba-4f0c-93d3-205b1a57de4c version=v2.3.0
<IP_ADDRESS> - - [15/Feb/2016:17:28:33 +0000] "GET /v2/jenkins-slave/blobs/sha256:d4bce7fd68df2e8bb04e317e7cb7899e981159a4da89339e38c8bf30e6c318f0 HTTP/1.1" 307 338 "" "docker/1.10.1 go/go1.5.3 git-commit/9e83765 kernel/3.16.0-60-generic os/linux arch/amd64"
time="2016-02-15T17:28:34Z" level=info msg="response completed" go.version=go1.5.3 http.request.host="docker-1:5000" http.request.id=65ff470f-718b-4d6f-a826-3c093a69e693 http.request.method=GET http.request.remoteaddr="<IP_ADDRESS>:49501" http.request.uri="/v2/jenkins-slave/blobs/sha256:816152842605fe3ede1dc7c47f33e641f74cb4ae0d5c51a6c19cc8d85da934f3" http.request.useragent="docker/1.10.1 go/go1.5.3 git-commit/9e83765 kernel/3.16.0-60-generic os/linux arch/amd64" http.response.contenttype="application/octet-stream" http.response.duration=545.94185ms http.response.status=307 http.response.written=340 instance.id=34fa54fc-9cba-4f0c-93d3-205b1a57de4c version=v2.3.0

Can you copy your docker daemon logs?

Docker daemon logs:
Feb 15 18:17:04 docker-1 docker[807]: time="2016-02-15T18:17:04.088644060Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 18:17:04 docker-1 docker[807]: time="2016-02-15T18:17:04.088671730Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 19:17:02 docker-1 docker[807]: time="2016-02-15T19:17:02.196443384Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 19:17:02 docker-1 docker[807]: time="2016-02-15T19:17:02.196473207Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 20:17:02 docker-1 docker[807]: time="2016-02-15T20:17:02.039462683Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 20:17:02 docker-1 docker[807]: time="2016-02-15T20:17:02.039495163Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 21:17:02 docker-1 docker[807]: time="2016-02-15T21:17:02.434577006Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 21:17:02 docker-1 docker[807]: time="2016-02-15T21:17:02.434605710Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 22:17:01 docker-1 docker[807]: time="2016-02-15T22:17:01.964408939Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
Feb 15 22:17:01 docker-1 docker[807]: time="2016-02-15T22:17:01.964436258Z" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"

@jmlrt none of this is showing any pull attempt.
Suggestion:

stop the docker daemon
enable debug mode on the daemon (add -D to the default launch arguments)
start docker
tail -f your daemon logs
try to pull, and reproduce the problem
copy the resulting logs

Hi @dmp42,
My Docker server is used for production environment.
I can't find a window to restart it with debug mode for now.
I'll do it & post logs when I can


GitHub actions are failint

There appears to be something wrong with the GitHub actions setup for getting things stamped.

fatal: No names found, cannot describe anything.

I added the fetch-depth thing to no avail but then I realized there are 2 of them. I'm going to try --always in the stamp script which should make it work no matter what (even if it's tagged wrong, which would be bad but would be educational)

I think the GH Actions is not fetching the tags locally. I think its doing a shallow clone of the SHA but without any branches/tags in the cloned repo.

Do you want to try adding fetch-depth:0 to the checkout?
https://github.com/actions/checkout#Fetch-all-history-for-all-tags-and-branches
Alternatively we could try a post-checkout fetch of the tags or unshallow the clone?

Here is the result of adding fetch-depth:0
https://github.com/bazelbuild/bazel-watcher/runs/2167896165?check_suite_focus=true
But it doesn't look like it showed up on the npm side
https://www.npmjs.com/package/@bazel/ibazel
Thanks for helping me get this closer!

For better or worse, I hade made it only publish to npm if it was the result of creating a new GH release
https://github.com/bazelbuild/bazel-watcher/blob/master/.github/workflows/release.yaml#L116

You could remove that condition, or try to create a formal GH release (not just a tag and manually running it)

That condition corresponds with the condition to upload the assets to the real GH release
https://github.com/bazelbuild/bazel-watcher/blob/master/.github/workflows/release.yaml#L63

Let's try doing a full release! https://github.com/bazelbuild/bazel-watcher/actions/runs/677723048

That looks VERY promising! Now to figure out how to allow a service account to deploy when you have two factor turned on... this'll be fun...

I think this is the one https://github.com/bazelbuild/bazel-watcher/actions/runs/677790605

I sort of had the idea that this would fix it

but apparently not? Maybe NPM has some latency between that setting being changed and taking effect. I'll try a release again later.

I don’t think you want 2fa on the publishing token at all. Option 1?
https://github.com/bazelbuild/bazel-watcher/pull/456#discussion_r565758390

If I pick option 1 that will disable the requirement that MFA be turned on for manual pushes which means that someone who guesses my password alone would be able to publish. Option 2 seems like the correct one since we are using automation tokens and those automation tokens are not bound to MFA?

As a quick test I tried releasing v0.15.5 with MFA completely disabled. It is now reenabled.
Lessons learned from this test:

It doesn't matter what the setting is, which means it is probably a setting that comes from the @bazel organization.
I have no idea who owns the @bazel organization so I can ask them to change this setting 😦

Have you tried the steps I put here? https://github.com/bazelbuild/bazel-watcher/pull/456#discussion_r565758390
I think you need a new explicit token for automation.

Yes, I have generated an auth token.

Did I miss a step in that?

Since I don't have a good way to validate the kind of token behind that, I'm going to try generating a new automation token and see what happens.

I think that might have been it! Thanks so much @joeljeske for all your hard work on this. I really appreciate it.


Hide fields on drop-down change

I am trobling to hide fields on  drop-down change with the condition
I tried with code
this.form.OptionsCategoryId.changeSelect2(e => {
var id = this.form.OptionsCategoryId.value
if (id == 1) {
// hide some fields
}
else {
//hide some field
}
        });

but it gives error like:

Message: Uncaught Element has no widget of type 'Serenity.IntegerEditor'! If you have recently changed editor type of a property in a form class, or changed data type in row (which also changes editor type) your script side Form definition might be out of date. Make sure your project builds successfully and transform T4 templates

2  Element has no widget of type 'Serenity.IntegerEditor'! If you have recently changed editor type of a property in a form class, or changed data type in row (which also changes editor type) your script side Form definition might be out of date. Make sure your project builds successfully and transform T4 templates
Please help me
I'm new for serenity
thanks in advance

@volkanceylan Please help me

Try using  var id = Q.toId(this.form.OptionsCategoryId.value);
For debugging you can also try use console.log(`${someVariable}`); to see what your variable values are.

@edwardch
Thanks for replay
but it gives the same above error(see above error)
When I click on the Add / Edit button at that time it comes
I think it unable to generate serenity code.

Did you transform T4 templates?

@edwardch
No, I don't do anything,
but when I build solution then Output window's show
Unhandled Exception: System.ComponentModel.Win32Exception: The system cannot find the file specified
1>   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
1>   at System.Diagnostics.Process.Start()
1>   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
1>   at Serenity.CodeGenerator.TSTypeLister.List()
1>   at Serenity.CodeGenerator.Program.<>c__DisplayClass0_1.b__1()
1>   at Serenity.CodeGenerator.Program.Main(String[] args)
1>C:\Dhanraj\Projects\IEPGlobalContacts\IEPGlobalContacts\IEPGlobalContacts.Web\IEPGlobalContacts.Web.csproj(95,5): warning MSB3073: The command "dotnet sergen mvct" exited with code -532462766.
1>IEPGlobalContacts.Web -> C:\Dhanraj\Projects\IEPGlobalContacts\IEPGlobalContacts\IEPGlobalContacts.Web\bin\Debug\netcoreapp2.2\IEPGlobalContacts.Web.dll
1>IEPGlobalContacts.Web -> C:\Dhanraj\Projects\IEPGlobalContacts\IEPGlobalContacts\IEPGlobalContacts.Web\bin\Debug\netcoreapp2.2\IEPGlobalContacts.Web.Views.dll
1>
1>Unhandled Exception: System.ComponentModel.Win32Exception: The system cannot find the file specified
1>   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
1>   at System.Diagnostics.Process.Start()
1>   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
1>   at Serenity.CodeGenerator.TSTypeLister.List()
1>   at Serenity.CodeGenerator.Program.<>c__DisplayClass0_1.b__1()
1>   at Serenity.CodeGenerator.Program.Main(String[] args)
1>C:\Dhanraj\Projects\IEPGlobalContacts\IEPGlobalContacts\IEPGlobalContacts.Web\IEPGlobalContacts.Web.csproj(102,5): warning MSB3073: The command "dotnet sergen servertypings" exited with code -532462766.
1>Done building project "IEPGlobalContacts.Web.csproj".
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

@volkanceylan @edwardch  Please help me for how to transfer t4 template

If you're using .NET Core they should run for you, but if not you can go to your menu: Build > Transform All T4 Templates
Read your error message carefully and make sure your lookup script keys are right.

@edwardch I'm using .NET Core 2.2

@edwardch @volkanceylan After the building project  I'm not able to transfer T4 template
I'm using .Net core 2.2
It gives a warning like - The command "dotnet sergen servertypings" exited with code -532462766.

Please help me
I'm new for serenity
Thanks in advance

I had solved this issue
I missed some npm installation

I had solved this issue
I missed some npm installation

please guide me on missing npm installations, I am also facing same issue.


Allow disabling using nether portals

SAH already supports disabling nether portals, do we want to specifically disable lighting portals? @wingzero54

I took a look at the code for it here and it looks like it would allow players to use portals to travel back to the overworld from the nether instead of completely disabling them

Method below prevents portals being used under any circumstance if its a nether portal


Implement django filter on Lobby List view

Goal: The lobbies list page lists all lobbies with no specific organization. To make lobby searches more efficient, we want to implement advanced filtering capabilities where users can choose to display only lobbies with certain games, players, or match start times. We've done the research for what we need to do in order to have the filter appear on the view. We need to now decide which attributes we want to allow users to filter in their search.
Deliverables:

Pull Request

possible mini-steps:

create filters.py with LobbyFilter class
identify which attributes we want to allow filters for
for each attribute:

identify the lookup expressions we want
add it to Meta.fields

add function to views.py
add filters to HTML template

forked a matches/lobby-django-filters branch for the issue.
I've come up with a possible list of mini-steps for this issue:

create filters.py with LobbyFilter class
identify which attributes we want to allow filters for
for each attribute:

identify the lookup expressions we want
add it to Meta.fields

add function to views.py
add filters to HTML template

I've also put this in the summary.
feel free to add to/detract from/cross-off things that are done

pushed filters.py with skeleton LobbyFilter class

added function to views.py

added filter to HTML and requirements.
page and filter work now; we just need more filter fields

Added a fixture called lobby-fixture.json with more realistic names

added lobby_name and max_players filters

PR #257 requested and needs to be reviewed

Closing Comment:
PR is merged and task is finished.
We added three different filters (that can be used in conjunction with each other) that allow users to search for lobbies that contain the queries the users type in.

Issue Score: Excellent
Comments:
Logical selection of filters and well implemented!


Add No/Yes text next to MRRC toggle

Default state of toggle is off, and text is "No". If user turns toggle on, text changes to "Yes", and toggle/text responds accordingly thereafter.

Looks good!


chore: remove HTTP App Routing Images

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Remove the images for HTTP App Routing feature, which is deprecated.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall First build on robbiezhang-remove-http-app-routing-images at 60.702%

Totals

Change from base Build<PHONE_NUMBER>:
60.7%

Covered Lines:
2578

Relevant Lines:
4247

💛  - Coveralls


brickstudy labs _resolve dates for castor

Dates need to change to DD-MM-YYYY

Dates changed, still two samples of one participant.


Add formatting

Add workflow and config for formatting

Note that this can't be merged until the FREDKBOT_GITHUB_TOKEN has been set up


Headnum=1 ?

Thanks for your code which helps me a lot. After read your implementation, I found that the head num for attention module is set to 1 for every Transformer module. How did you know that heas num should be set to 1. I can not find any discription about this in the original article.

Hi @hkzhang91
I was also confused by this, so I simply set it to 1 to fit the number of parameters. However, you can now refer to the official repo, where they set to 8.

Hi @hkzhang91
I was also confused by this, so I simply set it to 1 to fit the number of parameters. But indeed, they did not mention it in the paper, however, you can now refer to the official repo, where they set it to 8.

Thanks


Cannot SSH to app service

Repro steps:

Action: appService.StartSsh
Error type: Error
Error Message: Unable to establish connection to application: App is started, but port is unreachable
Version: 0.16.1
OS: linux
Product: Visual Studio Code
Product Version: 1.40.1
Language: en

Call Stack
TunnelProxy.<anonymous> extension.bundle.js:157:99743
a extension.bundle.js:157:95441

Hi @songpr
Is this consistently happening?  Could you try connecting to SSH via the Portal?

Closing as dupe of https://github.com/microsoft/vscode-azureappservice/issues/1011


Code formatting

Here to make progress tracking and help easier.
Description will be added once I think the feature is mergeable
TODO: Add TODO

Will fix Travis tomorrow

Will do! I had a busy weekend but hopefully will get some time this evening.
On Mon, Mar 27, 2017 at 3:33 AM Rubén<EMAIL_ADDRESS>wrote:

@RabsRincon commented on this pull request.
In static/editor.js
https://github.com/mattgodbolt/compiler-explorer/pull/346#discussion_r108115163
:

@@ -350,6 +408,19 @@ define(function (require) {
}
};

Editor.prototype.handleThinkingGear = function (doShow, tooltipText) {

Let me know when you do!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mattgodbolt/compiler-explorer/pull/346#discussion_r108115163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmsdenVG_Ni28aTReMPBtSZyu-Bm3Kjks5rp3RegaJpZM4Mo56H
.

I love how this is going! Some thoughts, and I know you probably know these already but...

We need to handle errors. I pulled locally and on my laptop I don't have lang-format installed. There's no feedback that something went wrong.
I love the little "working" icon :)
This uses the same shortcut as your lookup assembly patch I think (ctrl-F9)
We need to work on the configuration side; I'd be happy to take this part of the code once the release is out.

Again: great work! Thanks!

PR closed, this branch is now hosted here as https://github.com/mattgodbolt/compiler-explorer/tree/format_tools


Support zooming in/out on the welcome screen

By default, the simulator welcome screen targets the lowest common denominator in regards to screen size. It does this to ensure it displays in its entirety, even on tiny 768p resolutions for example.
However, this leaves people with 4k displays like myself with a really small welcome screen window.
The proposal here is for zooming in/out to work in the welcome screen like it does for device skins.
Depending on your display resolution, these settings will have an upper limit of whatever can fit on the screen. So if you pick the huge setting, which is for example 2560x1440 (not real) and you have a display of 640x480, it will pick a size that will fill as much of the available screen area in that 640x480.

will be implemented in the next commit.


Problems with 1se lambda

Hello,
Great job with Robyn.
I did notice some irregularities and over regularization with some datasets.  I was able to trace it back to extraordinary high lamdas in the ridge regressions.
The 1se lamda is producing an average model across all pareto's at .25, when I compare it to lambda.min, has a fit of .95.

Decomp for 1se:

Decomp for min:

Perhaps giving the user the option to pick min or 1se  would be nice.  Also providing a max lambda option would be nice.
Thanks

Hi, this is very valuable insight! Thanks for digging deep into Robyn!
As you've probably seen in glmnet's documentation, we're using lambda.1se because it's the recommended default setting. Are you using your own /real data? The huge fitting difference surprises me to be honest. But also very interesting to see.
I believe it makes sense to implement a custom regularization tuner as you recommended. What's your thought behind the lambda.max? I'm thinking about a tuner between 0-1 / lambda.min to lambda.1se

Hello, my only thought to a max lambda would be, if the user knows a lambda from past models which they do not want to exceed.  But I think min - 1se would be sufficient

I noticed that you're probably still using the older 2.0 version, right? FYI Robyn is updated to 3.0 last week. Please check the new readme to see details. However the 3.0 will also have this lambda issue.
Regarding lambda, currently Robyn is just using the automatically generated lambdas from glmnet by default. But there's actually a ridge_lambda() function that can generate the lambda sequence for self-cross-validation. We'll consider how to do this best, because we want to avoid unnecessary friction and potential source of human bias  during the modelling process. I'll let you know once we have a solution.

Hi! In version 3.5 onwards, we are picking the best performing lambda as a new hyper-parameter added into nevergrad optimization. Please update and check this new feat; should be good enough to stop this particular issue.

Closing this ticket now. Let us know if you need further help


 vim_components.search_count() not working

search_count() util has regressed and not working anymore.

maybe you use it inside a component. it return a function so you need call it first and use that return function inside your component

Can you provide a minimal config? Here is what I am doing,
    local function getSearchCount()
        local vim_components_exits, vim_components = pcall(require, "windline.components.vim")
        if vim_components_exits then
            local search_count = vim_components.search_count()
            return search_count
        end

        return ""
    end

    local default = {
        active = {
            basic.section_a,
            basic.section_b,
            basic.section_c,
            { getSearchCount(), { 'cyan', 'NormalBg' } },
            basic.divider,
            basic.section_x,
            basic.section_y,
            basic.section_z,
        }
    }

    windline.setup({
        statuslines = {
            default
    })

that function above working on my machine
the example on airline is working too
https://github.com/windwp/windline.nvim/blob/master/lua/wlsample/airline.lua#L242C7-L242C67

Strange this exact same config doesn't work for me!


center tooltip on mouse

https://github.com/Caged/d3-tip/issues/53

http://stackoverflow.com/questions/32973634/move-tooltip-along-with-cursor-on-mouseover

@spiermar
Created PR #157 for this. The tooltip follows the mouse pointer.
Please review.
I feel few more enhancements can be made for tooltip - can move it to appear on the left if it exceeds the flamegraph border (if the mouse pointer is at extreme right).
I will try to add that shortly. Please share your thoughts.


update protobuf version

Looks like the reason we pin to <3.20 is for compatibility with TensorFlow: https://github.com/tensorflow/tensorflow/blob/b59935d3b349e752eed4729606e5d64a17e48015/tensorflow/tools/pip_package/setup.py#L105

Looks like the reason we pin to <3.20 is for compatibility with TensorFlow: https://github.com/tensorflow/tensorflow/blob/b59935d3b349e752eed4729606e5d64a17e48015/tensorflow/tools/pip_package/setup.py#L105

FYI @connorcoley @ipendlet @FanwangW we use TF in some of the examples

Is this a reason to separate out the examples into their own repo? Seems like a complex dependency to have when it's not essential for many use cases

Is this a reason (or an excuse) to separate out the examples into their own repo? Seems like a complex dependency to have when it's not essential for many use cases

That wouldn't fix the issue; if until TF supports protobuf>=3.20 we won't be able to use TF and ord-schema in the same interpreter since both require the proto libraries. I think our choices are (1) pin to whatever version of protobuf TF supports so that people can use TF, or (2) upgrade protobuf and declare that ord-schema cannot be used with TF.

I think it's not worth it to lose the support of TF because of version updating. We can just keep the current version and wait for TF to support protobug>=3.20.


Barcelona/Synthetics 2023 changes

Barcelona/Synthetics 2023 changes

@b1stern here is the pr, please review it and merge if it looks ok, thanks


Fix up some spelling errors

Codecov Report

Merging #130 into master will not change coverage.
The diff coverage is 25.00%.

@@           Coverage Diff           @@
##           master     #130   +/-   ##
=======================================
  Coverage   50.49%   50.49%
=======================================
  Files          31       31
  Lines        1909     1909
=======================================
  Hits          964      964
  Misses        874      874
  Partials       71       71

Impacted Files
Coverage Δ

internal/pkg/config/keystore.go
0.00% <0.00%> (ø)

internal/pkg/dacctl/workflow_impl/session.go
49.69% <0.00%> (ø)

cmd/dacctl/main.go
86.36% <100.00%> (ø)

Continue to review full report at Codecov.

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


Embed playwright dependency

Right now it's a separate thing we have to install.
Reference: https://www.meziantou.net/distributing-applications-that-depend-on-microsoft-playwright.htm

Closed via 6b903ebdfca14406608c2c44d6b48869abc5269a


MaterialDesignThemes.MahApps.FlyoutAssist not accessible via Xaml

Hi,
I'm not able to reference the FlyoutAssist introduced in #121 .
You can reproduce the issue with this Repo

Windos 10 Pro x64
Visual Studio 2015 Community
my packages.config
<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="MahApps.Metro" version="<IP_ADDRESS>" targetFramework="net452" />
  <package id="MaterialDesignColors" version="1.1.3" targetFramework="net452" />
  <package id="MaterialDesignThemes" version="<IP_ADDRESS>7" targetFramework="net452" />
  <package id="MaterialDesignThemes.MahApps" version="0.0.6" targetFramework="net452" />
</packages>

Is there something i'm doing wrong or missing?

I can reproduce this bug. My own use of FlyoutAssist is from code and not XAML so i've never encountered the problem.
It can be fixed by adding MaterialDesignThemes.MahApps to the XAML namespace but i am not sure if @ButchersBoy wants it that way. I could not make it work just using clr-namespace.
I'll submit a PR and we'll see how it goes.

Merged, thanks @mgnslndh

confirmed fixed with 0.07


boards: intel_s1000_crb: print short filename in board image script

Print just the basename of the Input and Output filenames
when creating the board specific image for Intel S1000 CRB

Codecov Report

Merging #13240 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13240   +/-   ##
=======================================
  Coverage   48.75%   48.75%
=======================================
  Files         319      319
  Lines       46871    46871
  Branches    10835    10835
=======================================
  Hits        22850    22850
  Misses      19394    19394
  Partials     4627     4627

Continue to review full report at Codecov.

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


Organize AL-Go repository

main branch in https://github.com/microsoft/AL-GO is the "working" branch, i.e. the latest code
main branch always deploys to preview branches in AL-Go-PTE, AL-Go-AppSource and AL-Go-Actions
setup end2end testing to be run after completed CI in main branch
setup continuous deployment to preview from main
only allow fork PR's against main
setup github pages for deployment of documentation, scenarios, workshop etc. (investigate whether we can have preview and main)
have readme.md point to github pages
change aka.ms links to point to github pages
when creating a release, we should create a release branch called release/v2.1 or like and then deploying from release branch v2.1 to AL-Go-PTE@main, AL-Go-PTE@version, AL-Go-AppSource@main, AL-Go-AppSource@version, AL-Go-Actions@version (and also to preview to ensure that preview is not older)
setup CODEOWNERS, CI/CD process etc.
Ensure that deploy can only be called form the right branch to the right version

My primary concern (and reason for release branches) is the documentation, workshops etc.
but maybe we can just use GitHub pages for that, then a release branch might not be needed.
Agree with releaenotes - let's get that updated and not approve any PR's which hasn't
For PowerShell functionality that should be available in scripts like the deliverto - I have put those in BcContainerHelper for now.
Reason for BcContainerHelper is that it is my only shipping vehicle for things like this.
I think BcContainerHelper needs to evolve into a BC module (like the AZ module), consisting of:
bc.auth
bc.nuget
bc.admincenterapi
bc.containerhelper

and then functionality like this would be clear in one of these modules.
These modules should be PS7 compatible, which would mean that we can switch a number of our runners to use linux instead of windows to save money (the build job which runs containers won't be able to change yet)
but for now - I would just place it in BcContainerHelper, where there already is a function for pushing to NuGet (without using the nuget.exe)


Replacing the FiatShamirRng with Merlin?

Currently Marlin includes its own FiatShamirRng which uses chacha20 and a generic Digest function (instantiated with I think blake2s).
Would you be interested in a PR that replaces it with Merlin?
In contrast to the existing implementation, this provides more secure prover randomness generation, allows binding Marlin proofs to arbitrary structured application data rather than just a single domain separator string, or to transcripts of other proof protocols, and potentially makes the implementation slightly cleaner (although the FiatShamirRng API is already pretty reasonable).  It also simplifies the (cryptographic) dependencies, as rather than relying on the security of both chacha20 and blake2s (or some other hash function), the security relies only on keccak-f/1600.
I would be happy to create a PR for this change but only if it's one that you'd actually want.

At minimum some Rng and rand could become RngCore and rand_core in both marlin and poly_commit, which simplifies reading the code.
I think merlin has stayed rand_core 0.4 (rand 0.6) so doing this doubles the rand dependencies, although merlin's own rand dependencies could be upgraded.
I do not understand all the code of course, but it appears marlin only use FiatShamirRng for actual Fiat-Shamir transforms, aka challenges, never on anything using system randomness.  Right now, merlin's challenge methods have no RngCore implementation.  Also, merlin's TranscriptRng incorporates system randomness, which makes it unsuitable.
I do think merlin's challenge methods could replace your own RngCore, but this would become some larger change across at least both marlin and poly-commit.  It's possible you've some direct Rng usages around that'd benefit from being instantiated with merlin's .build_rng().finalize(rng) etc., but maybe more in poly-commit, not sure.
I believe strobe-rs removed all the Vec usage and now works without std, so you could use STROBE directly.  Also, one could define some STROBERng that maybe works to merlin's TranscriptRng, but starts from an arbitrary STROBE state without the system randomness.  At first blush such a STROBERng looks like the minimal change.

@hdevalence Thanks for bringing up this issue. Yes, currently I'm not too happy with our custom hand-written framework for generating FS randomness, but the reason we haven't switched away is that we want to write a R1CS gadget for the marlin verifier, and it's not clear to me how to me how to write a constraint system with custom SNARK-friendky hashes for Merlin.
Maybe if one could abstract away the changes behind a trait or something, it would be easier?

@burdges yes, I should minimize the dependency down to rand_core. Do you want to open a separate issue for that? If not, I can do that. Thanks!

Sure:  https://github.com/scipr-lab/marlin/pull/6 https://github.com/scipr-lab/poly-commit/pull/2
Afaik, anyone using merlin or strobe-rs uses an extension trait anyways, even when only doing trivial stuff:  https://github.com/w3f/schnorrkel/blob/master/src/context.rs#L46
If you abstract enough for SNARK-friendky hashes then would you still use RngCore (Rng) the same way between marlin and poly-commit?  Or would you need some interface that constrains the amount of output?  You cannot constrain the amount of output needed in poly-commit maybe, so maybe not an issue?

@Pratyush Wanting to be able to write an R1CS gadget for the Marlin verifier is a good reason not to use Merlin, because Merlin is designed only for the "machine model" and isn't intended to be used in R1CS.  It would be nice to have an R1CS-friendly Merlin-ish construction for exactly this kind of case but it doesn't exist as a drop-in right now, so it's not useful for this issue.


Make SimpleBuilder listen on <IP_ADDRESS>

This PR:
For convenience, we usually prefer to run the SimpleBuilder in a Docker environment. Listening only to localhost makes the Builder API inaccessible from outside the docker container. Although I think this change is unreasonable for HotShot, it is currently the most suitable option.
This PR does not:

introduce any risk since the change is under the testing feature

Since we already added a Config to take in a port, why don't we add host there and take it in? If we use default when not provided, there would still not be any changes required on the dev-node. On the other hand, we could just add a Url param, and change builder_port param on dev-node to builder_url. Not sure which is better.

If anyone sees a url in the configuration, I think the first thought is that this application will be going to access some other services to fetch back the data. No one would expect that this url is what we listening on.
And if anyone sees a port in the configuration, I think the most reasonable thought of this would be this application is going to run a server on this port.
Since the SimpleBuilder here is provided to be used as a server, we should not limit its listening address.

If anyone sees a url in the configuration, I think the first thought is that this application will be going to access some other services to fetch back the data. No one would expect that this url is what we listen on. And if anyone sees a port in the configuration, I think the most reasonable thought of this would be that this application is going to run a server on this port. Since the SimpleBuilder here is provided to be used as a server, we should not limit its listening address.

Yea, you are probably right about the expectation of url. I can still see potential issues w/ hard-coding a server to bind to all network devices. You often need to assign a server to a specific IP. And adding this to configuration only adds the possibility of doing that, it doesn't prevent anyone from binding to <IP_ADDRESS>.  If we make <IP_ADDRESS> the default it's really the same as you have here but w/ some future proofing.


<EMAIL_ADDRESS>

@pinker13 I'm closing this because I believe that it was opened by mistake. Please let me know if that is not the case.


Feature Request: config popup win postion

Checklist

[X] I have read the README.
[X] The feature would be useful to more users than just me.

Feature Requested
It may be more ergonomic to place the popup at the top right, like vscode.

On a large screen this makes it more natural to look at the input and match results without having to look away too much (and twist your neck), perhaps adding a configuration option to select the location of the pop-up window
Relevant Screenshot
No response

implemented as option 👍


msid: interpret a stream id '-' as 'no stream'

WIP. This should trigger ontrack with a track and empty streams but currently does not since receiverList iterates over streams

Codecov Report

Merging #46 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
+ Coverage   93.25%   93.26%   +0.01%
==========================================
  Files           1        1
  Lines         815      817       +2
==========================================
+ Hits          760      762       +2
  Misses         55       55

Impacted Files
Coverage Δ

rtcpeerconnection.js
93.26% <100%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

published as 1.2.2


Add posthog analytics for downloads

We want to capture how many user clicks on the download button in the future.
Probably something of the sort:
import { usePostHog } from 'posthog-js/react'

export default function DownloadButton() {
  const posthog = usePostHog()

  const handleClick = () => {
    // Capture the event
    posthog.capture('download_button_clicked', {
      // You can add additional properties if needed
      button_location: 'landing_page',
      file_type: 'pdf'
    })

    // Your download logic here
  }

  return (
    <button onClick={handleClick}>
      Download
    </button>
  )
}

You'll have to use your own posthog key, if it works on ur end we can assume will work in landing page.

working on this


Checked by default

Hi guys,
I was wondering if there is an option to make every checkboxes checked by default ? If not, could you help me to find a way to do the job ?
Thanks !

Hi @eeynard,
Whether or not a checkbox is checked is determined by whether or not its associated value is contained in the selection array. If you want every checkbox to be checked initially, then you could for example bind a copy of the options array to the selection attribute in the controller's initializer:
// controller.js
import Ember from 'ember';

export default Ember.Controller.extend({
  options: ['a', 'b', 'c'],

  init() {
    // Set the selection property to be a copy of the options array
    this.set('selection', this.get('options').slice());
  }
});

<!-- template.hbs -->
{{multiselect-checkboxes options=options selection=selection}}

Does that help? If not, please explain your use case in a bit more detail and perhaps I can give a more specific answer.

Yes I saw that by digging in your code. But I was struggling with the fact that I am using a filtered PromiseArray as options, something like this :
let filterPromise = Ember.RSVP.filter(objects, object => {
       ...
});

return DS.PromiseArray.create({
    promise: filterPromise
});

My problem was that I wanted to initialize the selection array with the filtered objects fetched from the Promise. But after a few headaches, I just realized that I could use the unfiltered array of objects since it does not matter if there are extra objects in the selection array.
I had a pretty bad time explaining myself here so excuse me if you don't understand everything but I am no longer blocked so I close the issue !
Thank you for your fast answer :smiley:


Wasted Demon tweaks

@GitWither Wanted you to review these changes since the horns change the look of the demon a bit - I think for the better, but wanted to get your opinions first.


New package: HumanReadableFormatter v0.1.0

Registering package: HumanReadableFormatter
Repository: https://github.com/chayandatta/HumanReadableFormatter.jl
Created by: @chayandatta
Version: v0.1.0
Commit: 5e8db5c1ad6045fc2964bad95b55c089c285ae0f
Git reference: HEAD
Description: Humane Units and make them Readable
Release notes:

First version of HumanReadableFormatter.jl

How is this different from https://github.com/IainNZ/Humanize.jl?


Successfully added a back-to-top button and changed the background co…

Solved issue #19 successfully

Solved issue #19 and resolved the conflicts successfully

Please, star the repo.


ActionView::Template::Error occurs when trying to render a template file with a partial

Describe the bug
The following error occurred when trying to render a template with partial as in render template: 'articles/xxx', assigns: { xxx: }.
ActionView::Template::Error
Missing partial lookbook/articles/_article with {:locale=>[:en], :formats=>[:html], :variants=>[], :handlers=>[:raw, :erb, :html, :builder, :ruby, :jbuilder]}.

Missing partial lookbook/articles/_article with {:locale=>[:en], :formats=>[:html], :variants=>[], :handlers=>[:raw, :erb, :html, :builder, :ruby, :jbuilder]}.

Searched in:
  * "/path/to/xxxx/projects/personal/LookBookSample2/test/components/previews"
  * "/path/to/xxxx/projects/personal/LookBookSample2/app/views"
  * "/path/to/xxxx/projects/personal/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/views"
  * "/path/to/xxxx/projects/personal/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/templates"
  * "/path/to/xxxx/projects/personal/LookBookSample2/app/views"
  * "/path/to/xxxx/projects/personal/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/view_component-3.7.0/app/views"
  * "/path/to/xxxx/projects/personal/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/views"
  * "/path/to/xxxx/projects/personal/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/turbo-rails-1.5.0/app/views"
  * "/path/to/xxxx/projects/personal/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionmailbox-7.1.2/app/views"

I think the problem is that it has a lookbook namespace instead of articles/_articles.
I tried to read the actionview/actionpack code based on stacktrace to create a PR if possible, but I got to the point where I thought the problem might be around the initialization of the lookup_context.
However, the initialization process is so complex that I could not figure out where to fix it, so I created an issue.
To Reproduce

bin/rails generate scaffold Article title:string body:text

# app/views/articles/show.html.erb

    <% if notice.present? %>

<%= notice %>

    <% end %>

    <%= render @article %>

    <%= link_to "Edit this article", edit_article_path(@article), class: "mt-2 rounded-lg py-3 px-5 bg-gray-100 inline-block font-medium" %>

      <%= button_to "Destroy this article", article_path(@article), method: :delete, class: "mt-2 rounded-lg py-3 px-5 bg-gray-100 font-medium" %>

    <%= link_to "Back to articles", articles_path, class: "ml-2 rounded-lg py-3 px-5 bg-gray-100 inline-block font-medium" %>

# test/components/previews/articles/show_preview.rb
class Articles::ShowPreview < Lookbook::Preview
  def default
    article = Article.new(id: 1, title: 'title', body: 'beody')
    render template: 'articles/show', assigns: { article: }
  end
end

See error http://localhost:3000/lookbook/inspect/articles/show/default

Expected behavior
When redering a partial, it should look for articles/_articles instead of under the lookbook directory, such as lookbook/articles/_articles.
Screenshots

Full stack trace

/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/path_set.rb:42:in `find'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/lookup_context.rb:131:in `find'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/partial_renderer.rb:264:in `find_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/partial_renderer.rb:231:in `render'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/object_renderer.rb:16:in `render_object_with_partial'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/object_renderer.rb:21:in `render_object_derive_partial'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/renderer.rb:96:in `render_partial_to_object'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/renderer.rb:55:in `render_partial'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/helpers/rendering_helper.rb:44:in `render'
/path/to/xxxx/LookBookSample2/app/views/articles/show.html.erb:7:in `_app_views_articles_show_html_erb___1326443331578832732_26220'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/base.rb:264:in `public_send'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/base.rb:264:in `_run'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/template.rb:261:in `block in render'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications.rb:208:in `instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/template.rb:549:in `instrument_render_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/template.rb:249:in `render'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/template_renderer.rb:66:in `block (2 levels) in render_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications.rb:206:in `block in instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications.rb:206:in `instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/template_renderer.rb:60:in `block in render_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/template_renderer.rb:80:in `render_with_layout'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/template_renderer.rb:59:in `render_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/template_renderer.rb:11:in `render'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/renderer.rb:63:in `render_template_to_object'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/renderer/renderer.rb:31:in `render_to_object'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/rendering.rb:135:in `block in _render_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/base.rb:291:in `in_rendering_context'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/rendering.rb:134:in `_render_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/streaming.rb:256:in `_render_template'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/rendering.rb:121:in `render_to_body'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/rendering.rb:158:in `render_to_body'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/renderers.rb:141:in `render_to_body'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/rendering.rb:45:in `render_to_string'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/rendering.rb:147:in `render_to_string'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/lib/lookbook/preview_controller_actions.rb:24:in `render_scenario_to_string'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/base.rb:224:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/rendering.rb:165:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/callbacks.rb:259:in `block in process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/callbacks.rb:110:in `run_callbacks'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/callbacks.rb:258:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/rescue.rb:25:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/instrumentation.rb:74:in `block in process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications.rb:206:in `block in instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications.rb:206:in `instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/instrumentation.rb:73:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/params_wrapper.rb:261:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activerecord-7.1.2/lib/active_record/railties/controller_runtime.rb:32:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/base.rb:160:in `process'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/rendering.rb:40:in `process'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/controllers/concerns/lookbook/targetable_concern.rb:99:in `block in inspector_data'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/controllers/concerns/lookbook/targetable_concern.rb:98:in `map'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/controllers/concerns/lookbook/targetable_concern.rb:98:in `inspector_data'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/controllers/concerns/lookbook/with_panels_concern.rb:18:in `block in main_panels'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/controllers/concerns/lookbook/with_panels_concern.rb:17:in `map'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/controllers/concerns/lookbook/with_panels_concern.rb:17:in `main_panels'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/lookbook-2.2.0/app/controllers/lookbook/inspector_controller.rb:14:in `show'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/base.rb:224:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/rendering.rb:165:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/callbacks.rb:259:in `block in process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/callbacks.rb:110:in `run_callbacks'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/callbacks.rb:258:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/rescue.rb:25:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/instrumentation.rb:74:in `block in process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications.rb:206:in `block in instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/notifications.rb:206:in `instrument'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/instrumentation.rb:73:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal/params_wrapper.rb:261:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activerecord-7.1.2/lib/active_record/railties/controller_runtime.rb:32:in `process_action'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/abstract_controller/base.rb:160:in `process'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionview-7.1.2/lib/action_view/rendering.rb:40:in `process'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal.rb:227:in `dispatch'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_controller/metal.rb:309:in `dispatch'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/routing/route_set.rb:32:in `serve'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:51:in `block in serve'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:131:in `block in find_routes'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:124:in `each'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:124:in `find_routes'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:32:in `serve'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/routing/route_set.rb:882:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/engine.rb:529:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/railtie.rb:226:in `public_send'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/railtie.rb:226:in `method_missing'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/routing/mapper.rb:22:in `block in <class:Constraints>'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/routing/mapper.rb:51:in `serve'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:51:in `block in serve'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:131:in `block in find_routes'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:124:in `each'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:124:in `find_routes'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/journey/router.rb:32:in `serve'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/routing/route_set.rb:882:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/static.rb:25:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/static.rb:161:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/tempfile_reaper.rb:20:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/etag.rb:29:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/conditional_get.rb:31:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/head.rb:15:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/http/permissions_policy.rb:36:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/http/content_security_policy.rb:33:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-session-2.0.0/lib/rack/session/abstract/id.rb:272:in `context'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-session-2.0.0/lib/rack/session/abstract/id.rb:266:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/cookies.rb:689:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activerecord-7.1.2/lib/active_record/migration.rb:654:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/callbacks.rb:101:in `run_callbacks'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/callbacks.rb:28:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/executor.rb:14:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/actionable_exceptions.rb:16:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/debug_exceptions.rb:29:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/web-console-4.2.1/lib/web_console/middleware.rb:132:in `call_app'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/web-console-4.2.1/lib/web_console/middleware.rb:28:in `block in call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/web-console-4.2.1/lib/web_console/middleware.rb:17:in `catch'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/web-console-4.2.1/lib/web_console/middleware.rb:17:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/rack/logger.rb:37:in `call_app'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/rack/logger.rb:24:in `block in call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/tagged_logging.rb:135:in `block in tagged'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/tagged_logging.rb:39:in `tagged'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/tagged_logging.rb:135:in `tagged'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/broadcast_logger.rb:240:in `method_missing'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/rack/logger.rb:24:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/sprockets-rails-3.4.2/lib/sprockets/rails/quiet_assets.rb:13:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/remote_ip.rb:92:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/request_id.rb:28:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/method_override.rb:28:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/runtime.rb:24:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.2/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/server_timing.rb:59:in `block in call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/server_timing.rb:24:in `collect_events'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/server_timing.rb:58:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/executor.rb:14:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/static.rb:25:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/rack-3.0.8/lib/rack/sendfile.rb:114:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/host_authorization.rb:141:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/railties-7.1.2/lib/rails/engine.rb:529:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/configuration.rb:272:in `call'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/request.rb:100:in `block in handle_request'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/thread_pool.rb:378:in `with_force_shutdown'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/request.rb:99:in `handle_request'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/server.rb:443:in `process_client'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/server.rb:241:in `block in run'
/path/to/xxxx/LookBookSample2/vendor/bundle/ruby/3.2.0/gems/puma-6.4.0/lib/puma/thread_pool.rb:155:in `block in spawn_thread'

Version numbers
Please complete the following information:
Lookbook: 2.2.0
ViewComponent: -
Rails: 7.1.2
Ruby: 3.2.1p31
Additional context
The following is a sample project that is actually in error.
https://github.com/vividmuimui/LookBookSample/tree/report-issue
https://github.com/vividmuimui/LookBookSample/blob/report-issue/test/components/previews/articles/show_preview.rb

Hey @mpg-takahiro-koyama,
I had a similar issue recently and opened PR #606. I checked it with your case and it seems fine.
You can follow these steps in case you want to reproduce it:

Install the lookbook version from my PR.

gem "lookbook", github: "liram11/lookbook", branch: "fix-partial-rendering"

Set the preview_disable_action_view_partial_prefixes Lookbook parameter to true in your Rails config:

#./config/environments/development.rb
config.lookbook.preview_disable_action_view_partial_prefixes = true

Open the preview.

And thanks for the detailed report.

@liram11
Thank you for the guidance! I followed the steps you outlined and I was able to display lookbook without any errors.

Cool, thanks for double-checking it 👍

The PR #606 that addressed this issue has been merged, and I have confirmed that it works correctly in the main branch. Therefore, I am closing this issue.
@liram11 Thank you! 😄

@mpg-takahiro-koyama I've just released v2.3.0 that contains @liram11's fix for this issue. Thanks for reporting it and for confirming the fix works for you!


CMake cleanup

cmake: Use VULKAN_HEADERS_REGISTRY_DIRECTORY
cmake: Allow add_subdirectory workflow
closes https://github.com/KhronosGroup/Vulkan-ExtensionLayer/pull/156

CI Vulkan-ExtensionLayer build queued with queue ID 1819.

CI Vulkan-ExtensionLayer build # 253 running.

CI Vulkan-ExtensionLayer build queued with queue ID 1836.

CI Vulkan-ExtensionLayer build # 254 running.

CI Vulkan-ExtensionLayer build # 254 passed.


Figma File - Typo

In the Figma file of the Hero icons, there is a typo on single chevrons, they're listed as cheveron instead of chevron.

Fixed! Thanks for the note!