ATS 10 vs 9 perf top in production

These are numbers from 2 Ireland hosts, not the busiest time of the day.  They are both getting around 850-870 rps.  ATS 10 is doing 69 rps per cpu percentage and ATS 9 is doing 130 rps per cpu percentage.
ATS 10
  13.91%  traffic_server                                           [.]
ATS 10
   2.01%  libcrypto.so.1.1                                         [.] bn_mul_mont
   1.74%  libcrypto.so.1.1                                         [.] rsaz_1024_sqr_avx2
   1.20%  [kernel]                                                 [k] do_syscall_64
   1.04%  libjemalloc.so.2                                         [.] free
   1.04%  libwaflz.so                                              [.] ns_waflz::ac::find
   0.96%  libc-2.28.so                                             [.] __memmove_avx_unaligned_erms
   0.81%  traffic_server                                           [.] huffman_decode
   0.69%  libc-2.28.so                                             [.] tolower
   0.54%  libjemalloc.so.2                                         [.] malloc
   0.52%  libpcre2-8.so.0.11.2                                     [.] pcre2_match_8
   0.48%  libcrypto.so.1.1                                         [.] rsaz_1024_mul_avx2
   0.46%  libcrypto.so.1.1                                         [.] sha256_block_data_order_avx2
   0.46%  libcrypto.so.1.1                                         [.] bn_sqr8x_internal
   0.45%  traffic_server                                           [.] mime_hdr_field_find
   0.44%  libwaflz.so                                              [.] ns_waflz::waf::process_rule_part

ATS 9
   1.68%  libcrypto.so.1.1                                         [.] bn_mul_mont
   1.60%  libpcre.so.1.2.13                                        [.] pcre_exec
   1.44%  libcrypto.so.1.1                                         [.] rsaz_1024_sqr_avx2
   1.01%  [kernel]                                                 [k] do_syscall_64
   0.91%  libc-2.28.so                                             [.] __memmove_avx_unaligned_erms
   0.91%  libjemalloc.so.2                                         [.] free
   0.88%  libwaflz.so                                              [.] ns_waflz::ac::find
   0.82%  libpcre.so.1.2.13                                        [.] match
   0.78%  libpcre2-8.so.0.7.1                                      [.] pcre2_match_8
   0.74%  traffic_server                                           [.] huffman_decode
   0.65%  libc-2.28.so                                             [.] __strncasecmp_l_avx
   0.58%  libc-2.28.so                                             [.] tolower
   0.49%  traffic_server                                           [.] _mime_hdr_field_list_search_by_string
   0.44%  libjemalloc.so.2                                         [.] malloc
   0.42%  libcrypto.so.1.1                                         [.] sha256_block_data_order_avx2

Are all the (likely inlined) calls to ink_get_hrtime() in EThread::execute_regular() in Yahoo ATS 9?
It seems iffy that clock_gettime() is avoiding the kernel call/thunk in RedHat 8.  Looks like the COARSE clock is needed ( https://docs.redhat.com/en/documentation/red_hat_enterprise_linux_for_real_time/8/html/optimizing_rhel_8_for_real_time_for_low_latency_operation/assembly_application-timestamping_optimizing-rhel8-for-real-time-for-low-latency-operation#assembly_application-timestamping_optimizing-RHEL8-for-real-time-for-low-latency-operation ).  But I don't know why this would affect one YCPI proxy and not another.
Looks like you can select the (potentially not in userspace) clock type with a config, proxy.config.system_clock .  (Definitely a contender for most dubiously useful ATS config variable.)  So maybe double check it's consistent between the two proxies running ATS 10?

Recommend not assigning this to me.  Unless you want to be lower priority than binge-watching Fear The Walking Dead.


💡 [FEATURE] - Create Home Section

Description:
The home section serves as the main landing page for our project, and it's essential to make it engaging and attractive. This issue focuses on creating the Home.jsx component in the components folder and designing it to captivate visitors.
Steps to Contribute:

Create Home.jsx: Develop the Home.jsx component in the components folder.
Design the Home Page: Design the home page with captivating visuals, informative content, and an inviting layout.
Content Creation: Populate the home section with valuable content that highlights our project's purpose, features, and benefits.
Visual Appeal: Apply suitable styles and visual elements to enhance the overall appeal of the home section.

By contributing to this issue, you'll help create a compelling first impression for visitors to our project.
Your creative input in designing the home section is greatly appreciated! Let's make our project's home page stand out.

I would like to work on this issue
Would highly appreciate it if you assign me

Hello @Pinaka-Pani-18 , I would love to work on this. I will style it with Tailwind and make it responsive as well. But it would be easier if you tell me what features you are looking forward to have in the home section.

I would like to work on this issue
Would highly appreciate it if you assign me

I've assigned you, @rohits-web03, to the issue. You can start working on it.

Hello @Pinaka-Pani-18 , I would love to work on this. I will style it with Tailwind and make it responsive as well. But it would be easier if you tell me what features you are looking forward to have in the home section.

@akash0708, I have assigned you to another issue. You can work on that one.

Hi @akash0708 any update ?

@Pinaka-Pani-18 I have started working on it
I have thought of dividing the home section into the following sub-sections:

Hero Section
How to get started?
Highly rated projects(based on some sort of metric which I have not decided yet...can be stars or number of contributors)
FAQs
Social Media Links(for Hacktoberfest-Projects-Hub)

Do let me know your suggestions

Also suggest an image for the hero section
I will try to complete this by day after tomorrow for sure

@Pinaka-Pani-18 I have started working on it
I have thought of dividing the home section into the following sub-sections:
* Hero Section

* How to get started?

* Highly rated projects(based on some sort of metric which I have not decided yet...can be stars or number of contributors)

* FAQs

* Social Media Links(for Hacktoberfest-Projects-Hub)

What you think?
Do let me know your suggestions

Great idea. Proceed with the project theme, FAQs, and 'Get Started' subsection based on this below statement
"The Hacktoberfest Projects Hub primarily serves the purpose of manually adding projects. This is essential because numerous resources utilize the GitHub API to retrieve Hacktoberfest-related projects. Therefore, project maintainers or open-source project contributors can easily add their projects to this website, making it more accessible to potential Hacktoberfest contributors."

Also suggest an image for the hero section
I will try to complete this by day after tomorrow for sure

For images, you can use references from Google or take inspiration from other projects that align with our theme. Later, we can raise other issues related to professional images.

Sorry for the inconvienece @rohits-web03, this repo has been excluded from Hacktoberfest, but I'm not sure of the reason. I suspect it might have been reported. As a result, I have created the same project here. I'll create an issue there, and you can comment on it and make the necessary changes. Afterward, you can create a PR.


Mouse cursor must be exactly 32x32 on Windows

Godot version:
Godot 3.0.2
OS/device including version:
Windows 7 x64
Issue description:
The code for Input.set_custom_mouse_cursor calls OS_Windows::set_custom_mouse_cursor() internally, which only checks whether the given cursor's width and height are below 256 pixels. It then calls SetCursor.
On Windows, SetCursor() seems to fail for any texture that isn't exactly 32x32:

Type:Error
Description:
Time: 0:00:01:0503
C Error: Condition ' texture->get_width() != 32 || texture->get_height() != 32 ' is true.
C Source: platform\windows\os_windows.cpp:1895
C Function: OS_Windows::set_custom_mouse_cursor

This needs to be checked for on Windows if true and needs the corresponding docs to be updated.
Reported on Discord by user Paco.
Steps to reproduce:
Try setting a custom cursor on Windows to any texture that isn't exactly 32x32.

Already fixed in master with this PR https://github.com/godotengine/godot/pull/18002

Ah, thaks. Duplicate of https://github.com/godotengine/godot/issues/17992 then.


TLOCK performance

#4621

add new method get_transports_for_list

tested with utility program, 3400 items, TLOCK = 5000 entries,


add conceal for \item

It would be great to add the conceal below
("\\item" @punctuation.special @conceal (#set! conceal "○"))

which module is better?

I agree, thanks for the suggestion! I'm not sure which is best... let's put it in delim for now.


Asus aura support

Test Asus build with support for AuraSDK v3
List any issues that this PR fixes:
Fixes: #546
This pull request proposes the following changes:

Add a new device Asus, this aims to support all devices that falls under the AuraSDK
Modifies Strix Flare device to have more LEDs to be accessed

Known issues/To do:

Test Test Test!
Link to an Asus driver installer

Hello,
thanks it works great !
But the light is sync with my mouse, can I add another just for aura or sync with another key ?
Thank you

I've compiled the source of this branch and it loaded the first time.
next step was going to device and select preferred keyboard Strix Flare.
Then when I tried to change the preferred language into Italian it crashed and I'm not able to start it again.

Tried also to delete the build folder. can you give me some hint of where it stores the settings so I can clear and start from scratch to be able to reproduce the issue?
Maybe I can help testing with my Claymore.
Also, can you provide me the link of the latest Asus SDK I have to install?
I did a previous integration of my claymore and it works great (only problem I had to compile only in x86 since the dlls were x86)
I know about nothing of windows programming and C#, I'm more a nodejs / c++ dev, but maybe I can help testing
Thanks

Hey! Asus Claymore owner here!
I get this error: Exception thrown: 'System.InvalidCastException' in Aurora.exe
when doing this cast:

https://github.com/kekkokk/Aurora/tree/asus-aura-support
Started integrating support for ROG Claymore keyboard which seems to be a bit different (Its recognised as a keyboard but if you try to cast to keyboard the program explodes).
I noticed that in async mode, when pressing lots of keys the app crashes saying "the connection with the mainboard was lost" but the keyboard keys are super responsive. (I have a strix mb with rgb ram and strix VGA so I'm testing everything).
In not async mode it worked without a single crash but the keyboard response time is much higher. I can see the visual feedback lag when I press a key.
Let me know what do you think
That first claymore integration is with the numpad on the right only. (since it can be swapped).

I keep getting AccessViolationException in the foreach Device.Lights
Is this happening to you too?

@kekkokk
Hey, I don't have too much time to look into the Claymore issue :(. AccessViolationException seems to be happening internally from the API. I'm not sure how to keep it from complaining. I'm waiting for Asus to expose more of the API or release a nice update. (Or till I have more time to investigate)

Claymore is not a problem anymore, I wrapped it in it's own object. The access violation exceptions occurs only when threaded so It might be a concurrency issue.I think the only solution here is to wait for each device until it has applied the colors and skip the job if another update comes when busy during apply. I'm looking into it. seems to happen also in RGB.net which is the new implementation in the dev branch. At the moment seems that the bottleneck is the Vga (asus strix 1080) which takes up to 57 ms to apply. another interesting thing is that I made a little project which applies the colors every 33 ms (30fps) at every device and it works perfectly.
Playground
The same code applied in aurora is quite laggy, so I need to study how threads are handled inside aurora (again, I'm new in c#)
Hope to find a reliable solution

(I don't have github email enabled for some reason, so I didn't see your reply)
My threaded approach should be waiting per device, but not for all devices. Which is an interesting idea. I have a Pugio Mouse which decides to deadlock internally and make each call 3seconds long, which is why I made the async approach...


Add info about OS non-determinism to FAQs

This PR adds to the docs useful information in the FAQs about training deterministic XGBoost models with the same data in different Operating Systems.

Actually the result might be different on different hardware/compiler/stdlib/os


Remember scroll position?

Maybe we should remember the scroll position so the next time you open the box it's at the same place.

That sounds pretty cool. I'll add it to first minor release after v1.0.0

I think we would also want to reset the scroll position to the top when filtering or choices are updated.

Fixed in #38


Do not ignore all hidden files by default.

Ignoring all hidden files by default is a rather radical solution to prevent hidden utility files to be committed accidentally. It can potentially prevent important files such as .travis.yml and .htaccess from being committed without anyone realizing this until it's too late.
I propose to remove this line from the default .gitignore file, or to replace it with more explicit directives.

Thanks - fixed in v1.8.3


Allow history to be filtered by task

I'd love for history to get a few more options, maybe also a date-range instead of a count-based limit. Ideally, --search should check all (or most) fields and every field should be searchable on its own via dedicated parameter. What do you think?

Looks good to me, and I'm not opposed to adding more search options.


Please don't remove old version from bintray

All is in the title.
I used to 1.5 but it is not available in bintray. There is only the last version 2.1 and this version breaks code

:+1:
Now when I try to add your lib I received a gradle error
Error:(112, 13) Failed to resolve: com.lapism:searchview:2.1

and I cannot try eg. 2.0.4 right now :disappointed:

Sorry for that, I accidentally removed whole repository and I need to do everything again.

@lapism ok
@sosite You can use version from bintray if you add following code in your top build.gradle
allprojects {
    repositories {
        jcenter()
        mavenCentral()
        maven {
            url 'https://dl.bintray.com/lapism/maven'
        }
    }
}

Oh, I did not know this way. I know those repositories are on jCenter still but I do not have them in my private maven, so I am not able to update it. I already contacted Bintray so it should be fixed ASAP.

And change to version 2.x, it is better :)

For now 2.0.4 seems to be available. I am waiting 2.1.
I have updated my code with this version when it was available.

I will write here after Bintray version will be allowed.

2.1.1 available

It's ok for me.

And do not worry, I am not going to change anything anytime soon ( like names of methods, etc.).


Unblock the device rename feature

Current develop version hides the button to confirm the rename, this merely makes that button visible again. We should also migrate to device actions for this since it's using the old device job and UI.

Type
Bug fix
Context
https://ledgerhq.atlassian.net/browse/LL-5670
Parts of the app affected / Test plan

easy to validate but miss a LL ticket on our side.

What do you mean we miss a ticket @gre ? I linked to a task when I created the pr 🤔
Do you want me to explain in more detail in the task or?

Seriously just merge this

This is a ghost task from 2.26, it has been here for literally two months, the potential of breaking anything with it is zero while it does fix the current bug of not being able to edit the name because the button is hidden. I don't understand why it keeps getting left behind really cc @gre

yes. we'll do a pass on all ongoing PR as soon as we have a buffer in our pipeline.


dispatcher: set queues in Run

Otherwise it's possible to call stop before run and leave them unclosed.

Current coverage is 55.33% (diff: 100%)

Merging #1506 into master will decrease coverage by 0.06%

@@             master      #1506   diff @@
==========================================
  Files            82         82
  Lines         12914      12914
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           7154       7146     -8
- Misses         4776       4779     +3
- Partials        984        989     +5

Powered by Codecov. Last update 31f6a0d...309939c

LGTM, I guess
Not sure I understand why we would call Stop before Run. Isn't that an error?

@aaronlehmann Oh, it's pretty possible, because dispatcher is not recreated. So, on follower nodes it will always be like that.

Oh, okay. In that case we don't want to create the queues until Run anyway.


[FLINK-25810][connector/kinesis]Adding Kinesis data streams  sql uber-jar and end to end test.

What is the purpose of the change
This pull request adds SQL uber-jar for KinesisStreams table api and a respective end to end test to test it.
Brief change log

Created new shading module flink-sql-connector-aws-kinesis-data-streams that shades flink-connector-kinesis-data-streams and required dependencies.
Created flink-end-to-end-kinesis-tests module to add a new end to end test that depend on the new sql connector.

Verifying this change
This change added tests and can be verified as follows:

Added KinesisDataStreamsTableApiIT end to end test for the new sql connector.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): yes
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive):no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper:no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@vahmed-hamdy There are no documentation updates. Is this coming in a different PR?

Thanks @vahmed-hamdy, merged.
I also manually tested and found a couple of issues, unrelated to this change that I will raise Jiras for:

Invalid credential provider configuration does not fail the job. Job ends up spinning.
Sink does not react to cancellation signal. Interrupt is retried and job gets stuck in cancelling


Days of Buffering is meaningless when budget contains large one-time spends

Age of Money: 92 days (fairly accurate)
Days of Buffering: 23 days (probably "correct", but completely misleading)
I recently got married (weddings are expensive), paid off my wife's student loans, and went on a honeymoon. All of that was basically a large chunk of money that I saved up for and budgeted.
I don't know exactly how the Days of Buffering calculation works, but it seems to be assuming that my future spending will be similar to my past spending, which in my case, is highly unlikely to be true. Unfortunately, this makes the Days of Buffering metric mostly useless for me.
Is there any way to fix this? Will the one-time spends "fall off" the radar at some point, making the calculation useful again?

 The math for DOB is to take your average spending of the last 30 days so once you get 30 days out you should see the numbers drop.
Not too sure how we could handle this right now and I'm also not too sure it's something we're going to change. Rest assured that your DOB will definitely make more sense after ~a month

Like any metric, DOB is good at measuring some things, and bad at others. Giving the ability to exclude specific transactions from the average would allow you 'fix' this, but then people could just go in and ignore anything that they wanted and get the number to say all kinds of crazy things.
I think honestly the best approach for this is to wait the 30 days and let it reset with more average spending. We might be able to make the calculation more able to understand what "average" means in the future to ignore these outliers automatically, but then to me that feels like the number is even more removed from anything you can measure.
I'll go ahead and close this issue because we don't have plans to change anything specific with this calculation yet. If you want to discuss further, please feel free to post a thread on the YNAB forums which will let more YNAB users contribute to how they think it should work.


Require Ruby 2.4

Update gem requirements so Ruby 2.4.0 is the minimum.
Remove the Ruby version warning.
Update documentation.
Update changelog and version for 0.12.0.

supersedes #143


enable Gradle wrapper validation

https://blog.gradle.org/gradle-wrapper-checksum-verification-github-action

@carl-mastrangelo

@sullis  Thanks for the PR.  So far I have been the one upgrading the deps / gradle due to our custom dep locking, so I think the value add of this validation is somewhat diminished. I value fast CI completion, so if this validation ends up slowing down the PR lifecycle too much I'll will likely revert this.


how could someone make library code available without using a cdn

Hi there,
Excellent framework and REPL library. I'm an enthusiastic user of Vue. I'm authoring a library of vue components to be used in many projects in my company. I'm using the "@vue/repl" to create a documentation page where de lib components are loaded and presented with live examples. Below is a draft of such a page.

I also intend to use this playground to do incremental development of the components watching the behavior on the documentation page as I enhance the actual lib component. In that use case, I don't want to use the imports map to point to library code in a repository while developing locally. That's because the publish code is not the one I want to import the components. I want to import the component's local version. But I don't know how to do that.
I created a WPlaygroung component and imaged I could create some global scope for every REPL with the lib code
<script setup>
import { Repl } from "@vue/repl";
import CodeMirror from "@vue/repl/codemirror-editor";
import<EMAIL_ADDRESS>defineProps({
   exampleCode: {
     type: String,
     default: null,
   },
});
</script>
<template>
  <Repl :editor="CodeMirror" />
</template>

Can you help me figure out a way to inject the library components and functions in the REPL scope without using a CDN but referencing the local code I'm working on?
Thanks a lot,
JM

我也遇到这个问题了，不引用cdn时，尝试引入第三方包组件时，抛出default错误

local

Try to package the esm format in full, and then add the esm link in importmap. If you want to do incremental development of the components, Maybe  you can listen for changes in  and package it in real time and server it

我也遇到这个问题了，不引用cdn时，尝试引入第三方包组件时，抛出default错误

请问有解决方案了吗

给一个最小还原的repo

我大概明白您的想法，我查看了此仓库的源代码，它通过的正则替换来生成一个静态的html，并将它作为预览的ifream，

Refer to https://github.com/vuejs/repl/issues/234#issuecomment-2127354755


Optimize error reporting via bigtable::internal::RpcUtils<>

Many of the APIs are implemented like this (pseudo-code, with Table::Apply as example):
std::string error_message = "Table::Apply(" + table_name() + ")";
RpcUtils::Blah(..., error_message.c_str());

the problem is that this allocates a string to report error messages, but the string goes unused in most calls as there are no errors.  We did this because there was no other way to provide an indication to the user about what table or instance had the problem otherwise.  With the introduction of the MetadataUpdatePolicy we can do better.  We can say:
RpcUtils::Blah(... metadata_update_policy, ..., "Table::Apply" /* received as char const* */);

The metadata_update_policy object has the name of the target table (or instance, or project) embedded in it.  We can create a meaningful error message without having to allocate a string in each call.

@roopak-qlogic I just noticed that this bug was assigned to you.  Sorry, but I finished the implementation this afternoon.  Take a look and if it looks good to you we can merge my version, but if you have a better one we will use your version.

yesterday, I just started to understand issue and code.
No Implementation started, so your version is good to go.


Allowing for keyless unit testing.

Sorry again, the throwing was only if it returned a null.  The throws should be removed and the signals just checked for null.

Sorry again, the throwing was only if it returned a null. The throws should be removed and the signals just checked for null.

All good @johnml1135 ! Please check again.

I merged it into my gherkin testing branch.


Use @react-native-communty/cli-plugin-metro project to bundling, and remove custom code in CLI and related packages

I created @rnx-kit/metro-service from code in @react-native-community/cli to give us immediate access to calling Metro programmatically.
Check with @react-native-community/cli devs -- grabbou specifically -- about factoring out the code that talks to metro.

Still need to remove the custom code I added (copied) from @rnc community project. Now that it's all wrapped up and exposed through CLI, we should use that instead.

For future reference<EMAIL_ADDRESS>is equivalent to<EMAIL_ADDRESS>

headsup: things have been moving around -> https://github.com/facebook/react-native/pull/38795


DARIA BRAAF rollout omnibus thread

Starting an omnibus thread for spinning up a new instance of DARIA for our friends down the road -- want to make sure we have a place to put anything that arises as we go through this process with them.
@NerdyGirl537 if there's anything we need to get out ahead of please post in this thread! Any timeframe would also be killer. Thanks much!

Is this for BRAAF rather than RRF or both funds? Should we edit the issue subject just to keep things clean in case RRF wants it?

oh, yeah, this is braaf. Editing to reflect

@lwaldsc @colinxfleming I just sent a note to Toby.  Last time I heard from her, she told me she was waiting for Tannis (another board member) to get back from vacation. I'll let you know when I hear from her.

Per #1214 this is game on! @NerdyGirl537 do they have a start date? When would they like to start entering data?

@colinxfleming Needing you to confirm you are good with 9/25 or if we need to push it to Oct.

I'm good to flip the switch so they can start entering data on or around 9/25, though I might be out of pocket for much of that week due to a potential trip.
Someone who isn't me should probably spin up this server in question so that this knowledge isn't completely siloed in my head, I'll coordinate that with the rest of the team.
@alisonnjones this'll be another $7/m on our heroku bill. Are there any admin concerns or paperwork we need to handle before spinning them up a server? We should consider their official billing start-date to be 10/1 for simplicity (and because we can do data entry on the free server).

Yes, we need them to sign a contract and speak with our legal team before anything goes live. @NerdyGirl537 please let me know when we need to send them contract so that we're good to go with the 9/25 start date/timeline. the 10/1 billing start date sounds good to me. @colinxfleming  do you remember if you connected BAF with Emily? How does that invoicing work for BAF?

@alisonnjones send any time.  They are excited and ready to get started. Let's check that one off as an easy kill.

I don't remember where the BAF process left with Emily. I assume they paid up but I was well off the board at the point at which they'd have cut a check. (Procedure as spelled out in the contract is pretty much 'Cut an annual check at the beginning of the new FY'.)
@alisonnjones and @NerdyGirl537 please keep this thread posted on progress to getting legal squared away. Thanks much for dunking on that.

Spun up a working version via new pushbutton method in #1251

AFAIK we've got paperwork, they've got a server, and the remaining stuff is them doing the transition. @NerdyGirl537 can you post the status of that and close if there are no next steps for engineering?

The site is live. I've sent a note to Tannis about the data import but no joy. On my task list for this week to check in with them.

AFAIK this is all resolved so I'm closing. We can create new tickets if things pop up again.


Impossible to run

I'm trying to run on ubuntu server arm with ubuntu-desktop installed.
I've installed docker and docker compose.
Done npm upgrade but when I start a lab it appears the following error

Hi @gferrara8596, unfortunately we actually do not support arm platform.


Fix lint errors

There were some lint errors introduced by my previous PR, this PR rectifies them.

Thanks

@Raynos Thanks for merging.


Use cosmiconfig for configuration discovery

It would be awesome if sass-lint used cosmiconfig for configuration discovery.
A short summary of what it does:
Find and load a configuration object from
- a package.json property (anywhere down the file tree)
- a JSON or YAML "rc file" (anywhere down the file tree)
- a .config.js CommonJS module (anywhere down the file tree)
- a CLI --config argument

It supports rc files with optional file-type extension, e.g. .sasslintrc.yml or .sasslintrc.json and, as mentioned, it can also read configuration from the package.json file - an option which gains more and more interest lately.
And:

Additionally, all of these search locations are configurable: you can customize filenames or turn off any location.

Thanks @thasmo we'll take a look at it

PostCSS announced it is going to introduce a common PostCSS config using cosmiconfig.

I plan on looking at this for our 1.9 release, 1.8 should hopefully be landing soon, just a few PR's to get merged in. 1.9 will hopefully be all about supporting other config formats and a more robust ability to extend configs above the existing config-file option we've improved for 1.8.
👍

Any news about this feature?
I'd love to ditch that yaml file and migrate my config into package.json.


Enum FetchType import is not generated

Hi,
when i use FetchType.LAZY, the import for this enum (javax.persistence.FetchType) is not generated.

I think it's not fixed.
Import of CascadeType also not generated.

Hi @neorevx ,
Please confirm with v2.7.2 .
If still not fixed then attach the JPA Modeler file.

It's fixed. :D
Thank you!


Able to mint more than the amount of NFT's available

Bascially Title.
The counter is always at x/11 NFT's available, so i'm able to keep minting even though there are no more NFT's. How is this even possible using the candy machine and what could be a potential fix?

This is on the devnet btw, could that have something to do with it?


Upload the powervs image to S3 cloud object storage

This pull request has following changes:

adding upload subcommand implementation
uploading the image to s3 bucket
creating a s3 resource

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

Needs approval from an approver in each of these files:

OWNERS

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

/assign @mkumatag

@bkhadars please add the relevant information in the description field and remove TODO from the commit name

/cc @bpradipt

@mkumatag I have made the changes as suggested in the latest merge.. please have a check

@bkhadars any plans to add unit tests ?

@bkhadars any plans to add unit tests ?

@bkhadars any plans to add unit tests ?

Yes @bpradipt will add unit testcases in next version, this is the intial code..

/cc @bpradipt
/cc @mkumatag pushed the changes suggested in the latest commit

/hold

/lgtm

/lgtm

/unhold

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bkhadars, mkumatag
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mkumatag]

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


make logging more verbose

This makes it so that we can still see the same errors from the Cloud
Run dashboard (instead of being forced to look into the Stackdriver
logs), because Cloud Run by default only shows STDERR/STDOUT logs.
This addresses #183

/lgtm


Fresh install throws a deprecation warning due to manually loading the engine

What did you do?

Installed a fresh version of view_component-contrib
Generated a new component
Ran tests

What did you expect to happen?
Nothing specific?
What actually happened?
Got
DEPRECATION WARNING: Manually loading the engine is deprecated and will be removed from ViewComponent 3.0.0 (remove `require "view_component/engine"`) (called from require at /Users/moroz/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32)

Additional context
Seems like the solution would be to avoid adding require "view_component/engine" to config/application.rb. Removed the line: tests pass, warning went away
https://github.com/budu/view_component-contrib/blob/9459f01014e8e9f4d3d977340c7a967eec526300/app/templates/install/template.rb#L6
Environment
Ruby Version:
ruby 3.2.0 (2022-12-25 revision a528908271) [x86_64-darwin22]
Framework Version (Rails, whatever):
ruby Rails 7.1.0.alpha @ 717d53edcce8fc0d7a757ed92ec867afb71a9ec8
View Component Contrib Version: 0.1.2

Thanks for the report!
Fixed.


⚠ Bofrost.lu has degraded performance

In 28d791e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1046 ms

Resolved: Bofrost.lu performance has improved in 80d190d.


Crypto simd

Motivation
(Write your motivation for proposed changes here.)
add avx512f for sha3
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update or suggest changes to the docs at https://developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

This is only for Draft


fix: transaction calls on the reth-provider should not generate a hash by default

When calling the transaction methods by default, it should not compute the tx hash (TransactionSigned) as this dramatically slows down the response when using it and means it computes the hash even if you do not need to use it; you have the .hash() method on the TransactionSignedNoHash to do this.
(was not sure where i run cargo fmt as i did that and a lot of file changes so just assumed the CI may do it let me know if not)

found due to migrating to the provider and it made the results slower > https://github.com/joshstevens19/reth-indexer/pull/15

@mattsse ready to merge


Add LE root certificates to Glide

Task/Issue URL: https://app.asana.com/0/0/1199598987755231/f
Tech Design URL:
CC:
Description:
We need to add the LE root certificates to Glide so that fetchinf favicons don't fail in old devices (API <= 25) when LE starts issuing certificates with its own self-signed cert chain

created custom okHttp and added LE root certs to its SSL socket factory

registered custom okHttp as GlideUrl extension to handle fetches

Steps to test this PR:
API <= 25

Install app from develop
Navigate to https://valid-isrgrootx1.letsencrypt.org/
Verify in logcat that glide throws CertPathValidatorException when trying to fetch site favicon

API <= 25

Install app from this branch
Verify Registering OkHttp-based ModelLoader for GlideUrl message appears in logcat
Navigate to https://valid-isrgrootx1.letsencrypt.org/
Verify in logcat that glide does not throw CertPathValidatorException
Verify in logcat that TabDataRepository updates the favicon

API > 25

Install app from this branch
Verify Registering OkHttp-based ModelLoader for GlideUrl message does NOT appear in logcat
Navigate to https://valid-isrgrootx1.letsencrypt.org/
Verify in logcat that glide does not throw CertPathValidatorException
Verify in logcat that TabDataRepository updates the favicon

Internal references:
Software Engineering Expectations
Technical Design Template

@aitorvs pinging here for a marker https://letsencrypt.org/2020/12/21/extending-android-compatibility.html


[FEAT] check directory tree extension

please check if is possible to extend the existing directory tree with extra infos.
This would open a way to show the real name off an app even if the directory is only the guid (Qlik Sense for Windows)
It would be also great to give different icons / overlay for published apps / objects,...

We currently show the real name of the Application, which is passed to ApplicationDirectory ( ID and Name ) The Name will shown in Tree and the id is used to load scripts.
Icons this should be possible, there are out some custom icon sets for a tree depends on the project you open ( or file endings / types ).


Unable to eval multiple items in a row, key presses are inadvertently sent through to the game.

🐞 bug report
Describe the bug

When evaluating multiple items in a row after eval'ing the first item each subsequent item requires multiple key-presses of the eval function (ctrl-d or ctrl-q for maps) in order for the eval to be initiated.  In the interim key presses are sent-through to the game which inadvertently activate skills/flasks.
To Reproduce

Eval any item then eval another item within 1-2s.
Expected behavior

Previous to the latest version this behavior was not present, each ctrl-d or ctrl-q was caught by the tool and an eval was always initiated.
Screenshots

🌍  Your Environment

OS:  e.g. Win7 x64
Version:  e.g. 0.6.9 portable
PoE:  e.g. Steam 3.10.0/e English

With the latest version and disabling keyboard support in the main settings has resolved this issue.


type operators and, or are not working right in polymorphic contexts

type Bar<A> = Foo and A

always gives None, even if the A passed in is a record. I didn't test this with or, but I suspect it is equally ignorant with variants in polymorphic context.

That is expected behaviour – these are just syntactic operators, not full-blown union and intersection types (which would introduce exponential complexity into the type system).


Revise if the conda folder is needed

Is this folder necessary to generate the pyCapsid package in conda?
Check with Colin. Generate issues as needed for lab folks.

The conda folder is part of the github conda build procedure. However it can be moved as long as the relevant line in https://github.com/luquelab/pyCapsid/blob/main/.github/workflows/conda-custom.yml is also changed.


rv planet unit bug!!!

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 69.62%. Comparing base (9dd3d18) to head (64889cc).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #83   +/-   ##
=======================================
  Coverage   69.62%   69.62%
=======================================
  Files          12       12
  Lines         859      859
=======================================
  Hits          598      598
  Misses        261      261

Flag
Coverage Δ

unittests
69.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Every shell command is executed multiple times

Node version:
1.3.6
ShellJS version (the most recent version/Github branch you see the bug on):
0.6.0
Operating system:
Linux (no idea what type, uname -v gives me this: #1 SMP Mon Aug 10 09:44:54 EDT 2015)
Description of the bug:
Hi guys, I'm new to all this, but I ran into a problem. Every command I send to the shell via the shelljs is executed multiple times (random number, usually around 5-10). It works fine on my local enviroment (MacBook pro), but when I try it on the production server, it's always acting up like this.
Every command I tried is executed multiple times (git pull, echo, gulp, copy, etc...)
Any ideas what I'm doing wrong? Thx
Example ShellJS command to reproduce the error:
require('shelljs/global');

console.log("Test");
exec("echo whatever");

ShellJS command output on my machine:
Test
whatever
whatever
whatever
whatever
whatever
whatever
whatever
whatever

Quick update: using execSync module works (outputting all commands just once).

@Ruskyj Would you be able to use a more recent version of node? I've seen things like this before on node v0.10. If you use node v4+ that should be a workaround

@nfischer Unfortunatelly, I don't think so. It took 2 weeks just to get NodeJS on that machine installed. Corporate processes BS...
I fixed it by using execSync for now. But thx for the info, I'll keep that in mind for my future projects. Btw, this info should probably be mentioned in documentation as well.

@Ruskyj

Nodejs is really old: 0.10.42

Yeah, that makes more sense. I've seen something similar to this before (although it always seemed to work correctly for the most part).
Unfortunately, we recently dropped support for v0.10 for future development. Since we're getting ready to release v0.7, we probably won't be able to focus on this issue. If you can figure out a fix, please feel free to submit a PR.

It's ok, I completely understand, 0.10 is from the stone age.
I might look into that if I ran into further problems.
Thx for your time ;)


Platform enablement request: Please add s390x to the supported platforms.

We have no plans to release a ChefDK for this platform and likely won't ever as ChefDK is targeted at developer workstations primarily. We do support s390x arch for chef-client https://downloads.chef.io/chef/13.3.42#el


Fixed known html entity error and new custom dependency error

Fixes:

https://github.com/omahajs/generator-omaha/issues/4
https://github.com/omahajs/generator-omaha/issues/5

 Fix new plugin ESLint error

 Fix plugin generator scaffolding HTML entities

Coverage remained the same at 100.0% when pulling 6c11ca45715cc217a10956a3342f01942c369fcc on bugfix/plugin-eslint-error-and-html-entities into b9b187e4fd8a7608d471df754ec05703c0878f01 on master.

Coverage remained the same at 100.0% when pulling 6c11ca45715cc217a10956a3342f01942c369fcc on bugfix/plugin-eslint-error-and-html-entities into b9b187e4fd8a7608d471df754ec05703c0878f01 on master.


[SDLe][Intel-Mllib][Klocwork] Static Code Analysis Issues

1534: Null pointer 'std::setprecision(0)' that comes from line 571 will be dereferenced at line 571.
OAP/oap-mllib/mllib-dal/src/main/native/service.h:571 | printNumericTables()
Code: NPD.GEN.MUST | Severity: Critical(1) | Support Level: Klocwork Certified(1) | State: New | Status: Analyze | Taxonomy: C and C++ | Reference: none | Owner: unowned
1760: 'totalCost' might be used uninitialized in this function. OAP/oap-mllib/mllib-dal/src/main/native/KMeansDALImpl.cpp:225 | Java_org_apache_spark_ml_clustering_KMeansDALImpl_cKMeansDAL ComputeWithInitCenters()Code: UNINIT.STACK.MIGHT | Severity: Critical(1) | Support Level: Klocwork Certified(1) | State: New | Status: Analyze | Taxonomy: C and C++ | Reference: none | Owner: unowned |

Both issues can be ignored.

It’s the only way to use setprecision.
algorithmFPType is a typedef type, there is no initialized value since the type maybe changed.


tests/blutooth/tester: ASSERTION FAIL due to Recursive spinlock when running bt tester on qemu-cortex-m3

Describe the bug
When running Bluetooth Tester(tests/bluetooth/tester) for AutoPTS testing on Qemu-cortex-m3, there is ASSERTION FAIL due to Recursive spinlock while processing the events.
To Reproduce
Steps to reproduce the behavior:

Running autoptsserver running on Windows
Build image
$ cd tests/bluetooth/tester
$ mkdir build; cd build
$ cmake -DBOARD=qemu_cortex_m3 -DCONF_FILE=qemu.conf ..
$ make
Use autopts to run the test. ex:
$ ./autoptsclient-zephyr.py "c:\Users\Tester\Documents\Profile Tuning Suite\autopts\autopts.pqw6" /home/tester/working/zephyr/workspace/zephyr/tests/bluetooth/tester/build/zephyr/zephyr.elf -i <IP_ADDRESS> -l <IP_ADDRESS>  -c GAP/BROB/BCST/BV-01-C --debug
Test will fail with BTP_TIMEOUT
Check the iut-zephyr.log

Expected behavior
No crash or assertion
Impact
Test fails
Screenshots or console output
Output from iut-zephyr.log:
[00:00:00.250,162]  bt_hci_core.process_events: count 2
[00:00:00.250,165]  bt_hci_core.process_events: ev->state 4
[00:00:00.250,166]  bt_hci_core.send_cmd: calling net_buf_get
[00:00:00.250,228]  bt_hci_core.send_cmd: calling sem_take_wait
[00:00:00.250,230]  bt_hci_core.send_cmd: Sending command 0x1009 (buf 0x20005200) to driver
[00:00:00.250,245]  bt_hci_core.bt_send: buf 0x20005200 len 3 type 0
[00:00:00.250,272]  bt_hci_core.process_events: ev->state 0
[00:00:00.250,278]  bt_conn.bt_conn_prepare_events:
[00:00:00.250,282]  bt_hci_core.hci_tx_thread: Calling k_poll with 2 events
[00:00:00.251,492]  bt_hci_core.bt_buf_get_cmd_complete: sent_cmd 0x20005200
[00:00:00.251,888]  bt_hci_core.hci_cmd_complete: opcode 0x1009
[00:00:00.251,896]  bt_hci_core.hci_cmd_done: opcode 0x1009 status 0x00 buf 0x20005200
[00:00:00.251,917]  bt_hci_core.bt_hci_cmd_send_sync: opcode 0x1009 status 0x00
[00:00:00.251,938]  bt_hci_core.read_bdaddr_complete: status 0
[00:00:00.252,025]  bt_hci_core.bt_hci_cmd_create: opcode 0x1002 param_len 0
[00:00:00.252,032]  bt_hci_core.bt_hci_cmd_create: buf 0x20005200
[00:00:00.252,036]  bt_hci_core.bt_hci_cmd_send_sync: buf 0x20005200 opcode 0x1002 len 3
[00:00:00.252,085]  bt_hci_core.process_events: count 2
[00:00:00.252,090]  bt_hci_core.process_events: ev->state 4
[00:00:00.252,094]  bt_hci_core.send_cmd: calling net_buf_get
[00:00:00.252,098]  bt_hci_core.send_cmd: calling sem_take_wait
[00:00:00.252,101]  bt_hci_core.send_cmd: Sending command 0x1002 (buf 0x20005200) to driver
[00:00:00.252,106]  bt_hci_core.bt_send: buf 0x20005200 len 3 type 0
[00:00:00.252,162]  bt_hci_core.process_events: ev->state 0
[00:00:00.252,170]  bt_conn.bt_conn_prepare_events:
[00:00:00.252,193]  bt_hci_core.hci_tx_thread: Calling k_poll with 2 events
ASSERTION FAIL [z_spin_lock_valid(l)] @ /home/tester/working/zephyr/workspace/zephyr/include/spinlock.h:66
Recursive spinlock
[00:00:00.257,828]  bt_hci_core.bt_buf_get_cmd_complete: sent_cmd 0x20005200
***** HARD FAULT *****
Fault escalation (see below)
***** Hardware exception *****
Current thread ID = 0x20002848
Faulting instruction address = 0x3bfc
Fatal fault in essential thread! Spinning...
qemu-system-arm: terminating on signal 15 from pid 29649 (python)
Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.9.5
Commit: b75115a49ef20d6131752b79aeda94e9a476f380

This looks similar to https://github.com/zephyrproject-rtos/zephyr/issues/13411 and https://github.com/zephyrproject-rtos/zephyr/issues/13289

I tried with the latest tip (b710177) and still was able to reproduce the issue.
Attacahed the log files.
iut-zephyr.log

@bluespring - alas I still don't have that test rig set up.  Almost certainly this is a bug introduced during the spinlockification series.  Can you try reverting each of those in sequence and tell me which patch broke it?  You can start with that HEAD (b710177 -- but probably not current master due to the giant renaming patch that went in) and try sequentially reverting:
8a3d57b6cc kernel/userspace: Spinlockification
b29fb220b1 kernel/timer: Spinlockify
f582b55dd6 kernel/pipe: Spinlockify
d27d4e6af2 kernel/sched: Remove remaining irq_lock use
be03dbd4c7 kernel/msg_q: Spinlockify
f0933d0ded kernel/stack: Spinlockify
9eeb6b8779 kernel/mbox: Spinlockify
7df0216d1e kernel/mutex: Spinlockify
603ea42764 kernel/queue: Spinlockify
c0bdcbaaf8 kernel/mem_slab: Spinlockify
e456d0f7dd kernel/thread: Spinlockify
84b47a9290 kernel/mempool: Spinlockify
f2b1a4bb64 kernel/poll: Spinlockify
1bf9bd04b1 kernel: Add _unlocked() variant to context switch primitives
da37a53a54 kernel/k_sem: Spinlockify
ec554f44d9 kernel: Split reschdule & pend into irq/spin lock versions
fb505b3cfd spinlock: Support ztest mocking
04382b9a2a kernel/mem_domain: Spinlockify
32a29d2805 kernel/atomic_c: Spinlockify
a37a981b21 kernel/work_q: Spinlockify

(I should point out: doing a git bisect will cut that work by about 2-3x, but requires a little study & setup if you haven't done it the first time)

@andyross Thanks for the git bisect tips. It was very useful command.
It looks like the issue didn't cause by the commits you listed.
Instead, From the testing, it caused by this commit:
commit 7367b84f8e6e496babff0e34df53ae9a39d910f5
Author: Andy Ross<EMAIL_ADDRESS>Date:   Wed Jan 30 12:27:43 2019 -0800

    kernel/spinlock: Augment runtime validation

    There was an existing validation layer in the spinlock implementation,
    but it was only enabled when both SMP and CONFIG_DEBUG were enabled,
    which meant that nothing was using it.  Replace it with a more
    elaborate framework that ensures that every lock taken is not already
    taken by the current CPU and is released on the same CPU by the same
    thread.

    This catches the much more common goof of locking a spinlock
    recursively, which would "work" on uniprocessor setups but have the
    side effect of releasing the lock prematurely at the end of the inner
    lock.  We've done that in two spots already.

    Note that this patch causes k_spinlock_t to have non-zero size on
    builds with CONFIG_ASSERT, so expect a little data and code size
    increase.  Worth it IMHO.

    Signed-off-by: Andy Ross<EMAIL_ADDRESS>
:040000<PHONE_NUMBER>a1a59623fd0c2b113bc04c1deeb21d4e0256 c9af6cefac23dda58cf0e9a6f70d48d172dedf30 M	include

And this is the git bisect report:
[tester@localhost zephyr]$ git bisect log
git bisect start
# good: [fe7f1e17deb0e019123ab96beba40acdb762f47e] Bluetooth: Take advantage of net_buf_pull_mem()
git bisect good fe7f1e17deb0e019123ab96beba40acdb762f47e
# bad: [31503a868b889413ed27180e8799188802fedca1] arch: xtensa: dts: Move HAS_DTS to arch level
git bisect bad 31503a868b889413ed27180e8799188802fedca1
# bad: [e526a2b80a2eaeef4aa30514ae5760d7ce005f17] host-gcc: exclude -lgcc to fix -mx32 [qemu_]x86_64 regression
git bisect bad e526a2b80a2eaeef4aa30514ae5760d7ce005f17
# good: [003bdb5fb65aa4f20f27edca88c270e4b2299b94] led_strip: lpd880x: Add Device Tree support
git bisect good 003bdb5fb65aa4f20f27edca88c270e4b2299b94
# good: [31b3941d88c4fa01704d93f0f9dfa1588fbe2b0a] ext: hal: atmel: sam: re-add missing header symbols following HAL import
git bisect good 31b3941d88c4fa01704d93f0f9dfa1588fbe2b0a
# bad: [e2b62b411be5f6c93a66c4474529f7e238858f3d] samples: openamp: Update sample to OpenAMP v2018.10 release
git bisect bad e2b62b411be5f6c93a66c4474529f7e238858f3d
# good: [5bb07d61d0163f5f8cb837a2a957c604ddc470fe] CODEOWNERS: add myself as maintainer for west commands
git bisect good 5bb07d61d0163f5f8cb837a2a957c604ddc470fe
# good: [a7342daedc945c0cc57affcb619013b6329c2482] boards: rv32m1_vega: fix the location of the YAML file
git bisect good a7342daedc945c0cc57affcb619013b6329c2482
# bad: [8b583acf23dd25ea771857c61a0723d17945f3aa] kernel/timeout: Fix another recursive spinlock()
git bisect bad 8b583acf23dd25ea771857c61a0723d17945f3aa
# bad: [7367b84f8e6e496babff0e34df53ae9a39d910f5] kernel/spinlock: Augment runtime validation
git bisect bad 7367b84f8e6e496babff0e34df53ae9a39d910f5
# good: [732cfac519ee7822b0d19eba5ef946f30649204d] samples: mesh: removed bug which is cause of divide by zero exception
git bisect good 732cfac519ee7822b0d19eba5ef946f30649204d
# first bad commit: [7367b84f8e6e496babff0e34df53ae9a39d910f5] kernel/spinlock: Augment runtime validation

Huh, well that's interesting.  So, obviously that's not the patch that introduced the bug, that's the patch that introduced the assertion that caught the bug. :)  But this is actually in the tree before the spinlockification series, and before that there were vanishingly few spinlocks being held anywhere...
I'll get you a patch tomorrow to try that will give use some better idea of where the failure is happening.  But barring that I may need to bug you for instructions on duplicating this test setup.

OK, try this when you get a chance. It will log the file/line location of the failed spinlock, as well as the location where it was already acquired.  Just pull and cherry pick the first commit in pull request #14286

Hi @andyross
This is the output with #14286
***** Booting Zephyr OS v1.14.0-rc1-1023-gaf5c44ca29ed *****
[00:00:00.000,000] <dbg> bt_hci_core.bt_hci_driver_register: Registered H:4
ASSERTION FAIL [z_spin_lock_valid(l)] @ ../../../../include/spinlock.h:86
	Recursive spinlock @/home/tester/working/zephyr/zephyr/kernel/timeout.c:110 (taken at /home/tester/working/zephyr/zephyr/kernel/timeout.c:144)
***** HARD FAULT *****
  Fault escalation (see below)
***** Hardware exception *****
Current thread ID = 0x200028cc
Faulting instruction address = 0x3c08
Fatal fault in essential thread! Spinning...
qemu-system-arm: terminating on signal 15 from pid 13147 (python)

Another similar error but different source line:
[00:00:01.540,000] <dbg> bt_hci_core.hci_cmd_status: opcode 0x2025
[00:00:01.540,000] <dbg> bt_hci_core.hci_cmd_done: opcode 0x2025 status 0x00 buf 0x200052c8
[00:00:01.540,000] <dbg> bt_hci_core.process_events: ev->state 0
[00:00:01.540,000] <dbg> bt_conn.bt_conn_prepare_events:
[00:00:01.540,000] <dbg> bt_hci_core.hci_tx_thread: Calling k_poll with 2 events
[00:00:01.540,000] <dbg> bt_hci_core.bt_hci_cmd_send_sync: opcode 0x2025 status 0x00
[00:00:01.540,000] <dbg> bt_l2cap.bt_l2cap_le_fixed_chan_register: CID 0x0005
[00:00:01.540,000] <dbg> bt_hci_ecc.emulate_le_p256_public_key_cmd:
[00:00:01.560,000] <dbg> bt_hci_core.bt_recv: buf 0x20005394 len 68
[00:00:01.560,000] <dbg> bt_hci_core.hci_event: event 0x3e
[00:00:01.560,000] <dbg> bt_hci_core.hci_le_meta_event: subevent 0x08
[00:00:01.560,000] <dbg> bt_hci_core.le_pkey_complete: status: 0x0
[00:00:01.560,000] <dbg> bt_smp.bt_smp_pkey_ready:
[00:00:01.560,000] <inf> kernel: ecc stack :	unused 232	usage 868 / 1100 (78 %)
[00:00:01.560,000] <dbg> bt_l2cap.bt_l2cap_server_register: PSM 0x0080
ASSERTION FAIL [z_spin_lock_valid(l)] @ ../../../../include/spinlock.h:86
	Recursive spinlock @/home/tester/working/zephyr/zephyr/kernel/timeout.c:110 (taken at /home/tester/working/zephyr/zephyr/kernel/timeout.c:152)
***** HARD FAULT *****
  Fault escalation (see below)
***** Hardware exception *****
Current thread ID = 0x200028cc
Faulting instruction address = 0x3c08
Fatal fault in essential thread! Spinning...
qemu-system-arm: terminating on signal 15 from pid 13147 (python)

OK, those have me confused.  Both of those "parent" spots are quite clearly non-reentrant.  You can follow the execution by reading source and see that the process is guaranteed to exit the lock before trying to swap or otherwise being interrupted.  This "can't happen", basically.
I first got scared that maybe something in the BT layer was registering a nonmaskable interrupt and trying to call into zephyr out of it), but a quick check shows that's not the case (the nRF hardware has one of those for the radio, but it's carefully segregated from the kernel).
So I'm going to go with "probably stack overflow" as my best guess.  Some of the stacks in that app when I build it are indeed kinda small.  Can you add the following to to your default.conf and see if they change behavior:
CONFIG_ISR_STACK_SIZE=4096
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_IDLE_STACK_SIZE=4096
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
CONFIG_OFFLOAD_WORKQUEUE_STACK_SIZE=4096
CONFIG_BT_HCI_TX_STACK_SIZE=4096
CONFIG_BT_RX_STACK_SIZE=4096
CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=4096

Another possibility is that maybe something is wrong with the validation layer, or the code is using a corrupt spinlock struct or something.  What happens if you set CONFIG_ASSERT=n?  Do you get correct behavior or a crash further along?

Hi @andyross,
Even after increasing the stack size to your suggested value, the same assertion still occurred.
But, when I disabled the assert with CONFIG_ASSERT=n, it was running fine (at least what I read from the logs) and tests started to pass. I am going to run more tests overnight and update the result in the morning.

It went well with overnight testing and no crash or exception occurred during the test.

Well... that may speak to priority I guess if we believe it to be a problem in the validation layer.  I'm still at a loss as to the root cause.  Overnight I did realize there's an edge case where if a thread takes a spinlock and then aborts itself, it will then swap away with the spinlock held and with strange validation metadata still sitting in there for other threads to trip on.  But (1) that doesn't match the line numbers above, neither of which are in a critical section that can abort and (2) would be really weird.  Let me stare at the code some more.

If you get a chance, can you pull with #13800 and test with that?  It includes one other validation patch that doesn't seem to match the issue above, but... who knows, might catch something going wrong earlier.  I added the new patch to that one and rebased it, so it should be current.

I tested with new patch and here is the output. I don't see any new information, I guess.
***** Booting Zephyr OS v1.14.0-rc1-1012-g82ad69dac908 *****
[00:00:00.000,000] <dbg> bt_hci_core.bt_hci_driver_register: Registered H:4
ASSERTION FAIL [z_spin_lock_valid(l)] @ ../../../../include/spinlock.h:86
	Recursive spinlock @/home/tester/working/zephyr/zephyr/kernel/timeout.c:110 (taken at /home/tester/working/zephyr/zephyr/kernel/timeout.c:144)
***** HARD FAULT *****
  Fault escalation (see below)
***** Hardware exception *****
Current thread ID = 0x200028cc
Faulting instruction address = 0x3c08
Fatal fault in essential thread! Spinning...

Reprioritized this to low, given that it seems to be an artifact of the spinlock validation layer, doesn't produce a failure in actual code (and frankly a recursive spinlock on a uniprocessor architecture is not, in fact, a failure case -- it works, we just don't like it because the same code will deadlock in SMP).

#14520 is plausibly another symptom of the same issue

@andyross @bluespring is this still an issue?

Yes, it is still reproducible.


App Shortcut Error

When starting an app shortcut, I get either a "permission denied" error or "app not installed" error, depending on the phone.  I think the intent target class needs to be updated to com.google.androidbrowserhelper.trusted.LauncherActivity
https://github.com/GoogleChromeLabs/svgomg-twa/blob/a3296efcdbc64819126c290186f45569dad7a317/app/build.gradle#L150

@rayankans would you know what may be happening?

I'm not sure, I'm unable to repro. @PEConn Do you know what the right target class should be?

I think @dwaring87  is correct, although I'm surprised @rayankans is unable to reproduce.
@rayankans are you creating the app with svgomg-twa or with llama-pack? (It looks like both of them have this error in though).
The targetClass here needs to match up with an Activity in AndroidManifest, and in both svgomg-twa and llama-pack, this is com.google.androidbrowserhelper.trusted.LauncherActivity.

According to @andreban's comment here, this should have been updated to com.google.androidbrowserhelper.trusted.LauncherActivity after the migration to androix.browser-1.2.0.

#92 should fixes the demo code. @dwaring87 Could you try changing this in your app and let us know if it fixes the issue?

@andreban updating the target class does fix the issue for me.


Expanding the frequency range below 18MHz

I kindly request to extend the receiving frequency range limit below 18MHz. Within the 17MHz band, there are several stations that are very well received by the Quansheng. Recently, I also received communications on 16MHz. This simple change would cost 0 bytes of memory and would bring a lot of joy :D
Sample video:
https://k5.ct8.pl/tp-downloads/VID_20240322_102554.mp4

Hi,
With or without Si4732 mod ?
According to the datasheet, BK4819 cover only 18 MHz ~ 660 MHz and 840 MHz ~1300 MHz.
Armel F4HWN.

Hello,
My firmware is open source, of course :)
The firmware source code is available on this repo ;)
Regards,
Armel F4HWN.

I actually overlooked that, now I have a problem with compilation. It seems to be successful, but I don't see the resulting .bin file. Where can I find it?

As usual, in compiled-firmware directory.
Armel F4HWN

Strange issue, the compiled-firmware folder is created but it only contains a single file named firmware.ld. The .bin files are missing. What could be the problem?

I don't know. I'm under MacOS.
Armel F4HWN.

Same problem here, I built with docker and only firmware.ld in present compiled-firmware directory
Missing firmware file.

Maye be take a look at compile-with-docker.bat windows script.
I saw this code
@echo off
docker build -t uvk5 .
docker run --rm -v %CD%\compiled-firmware:/app/compiled-firmware uvk5 /bin/bash -c "cd /app && make clean && make && cp firmware* compiled-firmware/"
pause

Change it by this one, and test again...
@echo off
docker build -t uvk5 .
docker run --rm -v %CD%\compiled-firmware:/app/compiled-firmware uvk5 /bin/bash -c "cd /app && make clean && make && cp f4hwn* compiled-firmware/"
pause

Note I change firmware* by f4hwn* ...
Armel F4HWN.

Thank you @armel
I can confirm that your sugestion change firmware* by f4hwn* in compile-with-docker.bat solved the building issue. I was able to succesfully build f4hwn.packed.bin with my small change (reverse battery symbol) and the file is still 4 bytes smaller then the one on the github directory. Thanks.
I think @zylka5 can now try to build his version

It's working now! I used the new v2.5 source code and didn't have to change anything. Thank you for your help!

Ok, nice.
It's because I patched the compile-with-docker.bat that you're using under Windows.
I close this issue.
Armel F4HWN.


Sync version of ycmd-goto

I'm trying to adapt ycmd-goto into my workflow; for this I'd like the following:

navigate to definition in sync
if it can't be done, raise an error or return nil

The point is that if I can detect that ycmd-goto was unsuccessful, I can forward the request to some other mechanism (like TAGS).
The problem currently is that the request is async, so the return result of ycmd-goto doesn't matter, and the failure is simply signaled as a message.
Thinking about it, does it make sense for ycmd-goto to be async at all? Suppose the user called it, and by being async we leave Emacs unblocked for say 0.5s. Can the user do anything useful at that time? Moreover, ycmd-goto will likely change the buffer on completion, so even if the user does a forward-line in that 0.5s time frame, following that the current buffer will change without any further user input. Not a great UX, imo.

ycmd-goto returns a deferred object. I bet you can get what you want like this:
(defun goto-with-fallback ()
  (deferred:$
    (ycmd-goto)
    (deferred:nextc it
      (lambda (response)
          (if (...response isn't what you want...) (...do the fallback...)))))))

Or whatever. You can learn more at https://github.com/kiwanami/emacs-deferred.
Regarding the greatness or lack thereof of the UX, you'd perhaps be shocked as the whining I get when I make things synchronous. You're the first to complain about too much async behavior. Now that you know about deferred, though, perhaps you can cope.

Thanks for the pointer, this code worked for me in the end:
(and (bound-and-true-p ycmd-mode)
     (let ((inhibit-message t))
       (deferred:sync!
           (ycmd-goto))))


First page title in navigation displays twice

Like, the title implies, the first nav item displays twice. In this case, it's the About page. I've attached a snippit below.

I've tried it with a brand new jekyll site and it does the same thing.

Hi!
It is strange indeed. However, it does not appear to look like the type on strap default theme.
Do you have a link to the code, or can you post a snippet of the html you are using for the navbar?
I have seen this behaviour on another github page, I don't know if it is related.
The demo site seems to be working:
https://sylhare.github.io/Type-on-Strap/

Sorry, I've been running it locally as I'm still working on it. I'll try deploying it to a github page and see if it works.

Ok,
So my guess is that you would have two pages called "about" in your repository that's why it appears twice.
But if you upload it at some point and the issue is still there, let me know so I can check it up quickly :wink:

I just checked, and that was the problem. It might have to do with me downloading the template off of http://jekyllthemes.org/

Thanks!

Cool ;)


Error: invalid netflow version (10)

When trying to run stress test for vflow getting errors like:
invalid netflow version (10)

No traffic was parsed and send to kafka cluster.
vflow and strees builded from v0.5.0 version.
OS: ubuntu 18.04
Java: openjdk version "10.0.1" 2018-04-17
go version: go version go1.10.3 linux/amd64

@gedOHub The stress test doesn't support netflow; it looks you send ipfix stress data to netflow port per error message.


Finish Repo Migration

fix import paths
probably switch stuff over to sigs.k8s.io/service-catalog

fix travis badge in the README

may expand as I find more stuff that was broken

Everything seems to be working now.


Medial distribution  Stay on the Launch page,   iOS。

Medial distribution  Stay on the Launch page,   iOS。
Channel stable, v1.7.8

I had the same problem

@YelenaLemon Can you please provide more details, what do you mean exactly?

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of ' flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.


Add build informations to KubeArmor

We want to include build informations (branch, sha sum) to KubeArmor build process.
We can inspire from Discovery-engine building process here and here

Hello please, could I work on this?

Hi @Chinwendu20 , of course.

Please could you give me more context about the build process that you are referring to?

In discovery engine, we include build informations into the compiled binary. We would like to have the same informations included in KubeArmor.

Hey @Chinwendu20, here is the specific code line in the discovery-engine that you can use.

Duplicate of #1055 . Closing this one.


Operations using Math.toRadians/ use Degrees as input.

Added the ability to perform operations using degrees too(for trigonometric functions).
Await your suggestions.
Thank You!

Yup. I updated the code as you mentioned.
Please advice.
Thanks
Anurag.


mock.instances[0] is returning mockConstructor {} instead of actual object

Do you want to request a feature or report a bug?
report a bug
What is the current behavior?
repl.it demo: https://repl.it/FuQO/0
let MyMock = jest.fn();
MyMock.mockImplementation(() => ({
  name: 'test',
}));

describe('some tests', () => {
  it('run the instances check', () => {
    let newMock = new MyMock();
    expect(MyMock.mock.instances.length).toBe(1);
    expect(MyMock.mock.instances[0]).toBe(newMock);
  });
});

    - Expected
    + Received

    -Object {
    -  "name": "test",
    -}
    +mockConstructor {}

What is the expected behavior? (Copied from API docs)
// had a `name` property whose value was set to 'test'
expect(someMockFunction.mock.instances[0].name).toEqual('test'); // success

More Info
This API is documented but tests only run with empty functions. I have written tests here which are failing due to this bug.
https://github.com/facebook/jest/compare/master...vibhavsinha:master
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

jest: v19.0.0
node: v6.9.1
yarn: 0.20.3
OS: Ubuntu 16.10 Linux 4.8.0-37-generic GNU/Linux

This is expected. Mocking works by subclassing things in Jest.

@cpojer can you please point to any code example that shows how to do this?

Here's my work around for manually mocking ES6 classes.
It also work with functions. It does not align with Jest documentation
let MyMock = jest.fn();
MyMock.mockImplementation(function() {
  this.name = 'test'
  this.foo = jest.fn(() => {
    return 'bar'
  })
});

describe('some tests', () => {
  it('run the instances check', () => {
    let newMock = new MyMock();
    newMock.foo()
    expect(MyMock.mock.instances.length).toBe(1);
    expect(MyMock.mock.instances[0]).toBe(newMock);
    expect(MyMock.mock.instances[0].foo).toHaveBeenCalled()
  });
});

@cpojer is there anyway to get clarification on this? The way the documentation is written, it makes it seem like it would work via the way the question is asked. Instead, adjust it as @tinyroy mentioned achieves the desired results. Anyway for a blog post, or by adding what @tinyroy did to the documentation? Super helpful.
For now, the documentation just has the example of exporting and then importing every method, which is what I was doing, but it's much cleaner to be able to do the method mentioned here. I.E., heres an example exporting:
// __mocks__/sound-player.js
export const mockPlaySoundFile = jest.fn();
const mock = jest.fn().mockImplementation(() => {
  return {playSoundFile: mockPlaySoundFile};
});
// sound-player-consumer.test.js
export default mock;

import SoundPlayer, {mockPlaySoundFile} from './sound-player';
test('We can check if the consumer called a method on the class instance', () => {
  const soundPlayerConsumer = new SoundPlayerConsumer();
  const coolSoundFileName = 'song.mp3';
  soundPlayerConsumer.playSomethingCool();
  expect(mockPlaySoundFile).toHaveBeenCalledWith(coolSoundFileName);
});

This method of exporting and import doesn't scale well.

Hi guys,
If you would like to pass typescript class as mocked class, this is my typescript version of @tinyroy 's workaround.
The mock (./mocks/PluginManager.ts)
class PluginManagerMockImpl {
    run = jest.fn(() => {
        console.log("I am mocked");
    })
}

export const PluginManager = jest.fn().mockImplementation(PluginManagerMockImpl as any);

The test (./TestClass.test.ts)):
    test("will run", async () => {
        const pluginManager = new (PluginManager as any)()
        pluginManager.run();
        const pluginManagerMock = mocked(PluginManager);
        const runMocked = mocked(pluginManagerMock.mock.instances[0].run);
        expect(runMocked).toBeCalledTimes(1);
    });


Custom build in Mageia 8 fail

youtube-dl-gui
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/Threads/Download.py", line 146, in run
    self.download()
  File "/usr/lib/python3.8/site-packages/Threads/Download.py", line 123, in download
    ydl.download([self.url])
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 2068, in download
    res = self.extract_info(
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 808, in extract_info
    return self.__extract_info(url, ie, download, extra_info, process)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 847, in __extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 881, in process_ie_result
    return self.process_video_result(ie_result, download=download)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 1692, in process_video_result
    self.process_info(new_info)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 1970, in process_info
    partial_success = dl(fname, new_info)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 1915, in dl
    return fd.download(name, info)
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/common.py", line 366, in download
    return self.real_download(filename, info_dict)
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/dash.py", line 48, in real_download
    success, frag_content = self._download_fragment(ctx, fragment_url, info_dict)
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/fragment.py", line 104, in _download_fragment
    success = ctx['dl'].download(fragment_filename, fragment_info_dict)
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/common.py", line 366, in download
    return self.real_download(filename, info_dict)
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/http.py", line 352, in real_download
    return download()
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/http.py", line 301, in download
    self._hook_progress({
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/common.py", line 374, in _hook_progress
    ph(status)
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/fragment.py", line 246, in frag_progress_hook
    self._hook_progress(state)
  File "/usr/lib/python3.8/site-packages/youtube_dl/downloader/common.py", line 374, in _hook_progress
    ph(status)
  File "/usr/lib/python3.8/site-packages/Threads/Download.py", line 55, in hook
    self.bytes = self.format_bytes(li.get("total_bytes", "unknown"))
  File "/usr/lib/python3.8/site-packages/Threads/Download.py", line 183, in format_bytes
    _bytes = float(_bytes)
ValueError: could not convert string to float: 'unknown'
Abortado (`core' generado)

Fixed used system python3-youtube-dl package

@katnatek Thanks
I will check the conversion of _bytes to manager the Exception


[aon_timer, rtl/doc] No wakeup signalled on watchdog bite if it occurs before bark

aon_timer has a top-level signal wkup_req_o which is asserted on either the wakeup timer triggering or the watchdog bark triggering. The watchdog bite does not inherently assert this signal, it only asserts aon_timer_rst_req_o.
Provided the bark is configured to occur before the bite this should be no issue. First a wakeup will occur and assuming the bark is ignored, the bite will happen with wkup_req_o still asserted and now with aon_timer_rst_req_o too.
If the bite is configured to occur first you will only get aon_timer_rst_req_o.
I don't think this is a big issue as bark before bite is the sane configuration and signalling aon_timer_rst_req_o without wkup_req_o may have the desired effect (a chip reset) anyway?
The only action here may be to clarify this behaviour in the documentation. P1 as we need to discuss and agree no RTL change is needed here for M2.5.1
@msfschaffner @matutem any thoughts?

If I understand correctly, your concern is that there is a case where a bite may be triggered by aon_timer_rst_req_o while wkup_req_o is still asserted. In that case we should just assert, and wkup_req_o should be inconsequential. I see no need to clarify or change this, since it is what should be expected when the CPU disables or otherwise doesn't handle the wakeup interrupt.
If that is the case, the only item is to make sure we have tests that triggers this condition.

It's the other scenario, where we assert aon_timer_rst_req_o without first asserting wkup_req_o.  Though we should ensure it's documented properly at the block level should it prove to be a problem for future uses of the block.

Got it. There should be no problem: during low power the pwrmgr slow fsm will exit from low power due to a wakeup or a reset request. And if it is due to a reset it won't trigger a wakeup interrupt (if enabled).
Notice when entering low power we don't reset aon domains (specifically aon_timer and sysrst_ctrl), so when waking up from low power due to a reset the reset request persists, and pwrmgr will take the reset right after waking up, at which point it will reset aon domains.

@GregAC this seems all clear from my side. If you agree, could you close it?

I checked https://opentitan.org/book/hw/ip/aon_timer/index.html#aon-watchdog-timer mentions the bite reset request "is independent of the IRQ sent as part of the watchdog bark". Do you think this needs further clarification? If so, any suggestions?


"@prefresh/vite" fails when using "jsxFactory" other than "h" from "preact"

Problem
Emotion users need to be able to use a custom jsxFactory, when using one of the core features of emotion css prop.
When making this change (click to view)
Switching from the suggested:
  esbuild: {
    jsxFactory: `h`,
    jsxFragment: `Fragment`,
    jsxInject: `import { h, Fragment } from "preact";`,
  },

To:
  esbuild: {
    jsxFactory: `jsx`,
    jsxInject: `import { jsx } from "@emotion/react";`,
  },

The "@prefresh/vite" fails with the following error message:

I'm new to vite, so sorry for not being able to provide you w/ a more useful debug msg

Cannot read property '__e' of undefined

I guess it's related to optimizeDeps (vite config), you might want to avoid having that active for this one as currently you have some kind of circular import going on. Options being undefined feels like that atleast.

I guess it's related to optimizeDeps (vite config)

To be transparent, the following is everything I use in the vite.config.ts:
Click to view
import prefresh from "@prefresh/vite"
import { defineConfig } from "vite"
/**
 * @see https://vitejs.dev/config
 */
export default defineConfig({
  plugins: [
    (prefresh as any)()
  ],
  esbuild: {
    jsxFactory: `jsx`,
    jsxInject: `import { jsx } from "@emotion/react";`,
  },
  resolve: {
    alias: {
      react: `preact/compat`,
      "react-dom/test-utils": `preact/test-utils`,
      "react-dom": `preact/compat`,
    },
  },
})

As I understand, you assume, I am also using optimizeDeps options. I'm not.
Could you please clarify what would you like me to test to assist you w/ finding the resolution?

Try https://vitejs.dev/config/#dep-optimization-options:
exclude: ['preact/compat', 'preact', '@prefresh/core']

@JoviDeCroock thank you for your help so far.
Please be informed, I tried the suggested change, adding the following to the config:
  optimizeDeps: {
    exclude: [`preact/compat`, `preact`, `@prefresh/core`],
  },

it didn't help, failing w/ a similar message:
Cannot read property '__H' of undefined

Then, I tried to exclude other two dependencies that are added by @prefresh:
  optimizeDeps: {
    exclude: [
      `preact/compat`,
      `preact`,
      `@prefresh/core`,
      `@prefresh/vite`,
      `@prefresh/utils`,
    ],
  },

But it fails in the same way.
Making sure that there are absolutely no deps related to react and preact in the node_modules/.vite/* also doesn't help:
  optimizeDeps: {
    exclude: [
      `react`,
      `preact/compat`,
      `preact`,
      `preact-render-to-string`,
      `@prefresh/core`,
      `@prefresh/vite`,
      `@prefresh/utils`,
    ],
  },

Mind adding preact/hooks as well? Gonna check it out in a bit, not at my computer atm

@JoviDeCroock just did, sorry to inform, it's the same error.
Thank you for taking a look. Please let me know, if I could assist in any other way.

Well my last guess would be to add @emotion/core

Here to chime in, I think I'm running into this same bug, and it happens specifically when I try to use suspense; it seems to work otherwise.
I tried to make a standalone reproduction, but I could only reproduce it in my project. Here's the branch, with the code minimized as much as I could.
It uses pnpm. Running pnpm i; pnpm run dev should work, and open the dev server to localhost:3000
Files of relevance:

https://github.com/itsMapleLeaf/anigreen/blob/82f40b57e9428eda781a899d7904d317673b468b/web/vite.config.ts
https://github.com/itsMapleLeaf/anigreen/blob/83a94ee3f1b0a89fb26863c34fc37afdd953fc7d/web/src/main.tsx
https://github.com/itsMapleLeaf/anigreen/blob/83a94ee3f1b0a89fb26863c34fc37afdd953fc7d/web/src/app/WatchingPage.tsx

Findings:

Works without suspense usage
Works when WatchingPage is inlined in main.tsx instead of imported
Works when removing  prefresh() preset from the config
Changing the esbuild jsx config has no effect

@itsMapleLeaf that one is def the optimizeDeps issue, it's not inherent to Prefresh. The issue is that vite will optimize preact in preact/compat which leaves prefresh/core (uses preact) with another preact version or a weird import-state. Can't quite tell which one applies

I see, and the "Cannot read __H of undefined" now shows up when I try to add the exclusions, as mentioned earlier:
	optimizeDeps: {
		exclude: [
			"react",
			"react-dom",
			"preact",
			"preact/compat",
			"preact/hooks",
			"@prefresh/core",
			"@prefresh/vite/runtime",
			"@prefresh/vite/utils",
		],
	},

So it sounds like an issue with Vite that can/should be fixed on their end?

Btw, as crazy as it sounds, the following addition ended up working.
If you add more deps to the exclusion, vite/esbuild stops working properly throwing different errors related to the exports of the pkgs.
  optimizeDeps: {
    exclude: [
      `@prefresh/vite/runtime`,
      `@prefresh/vite/utils`,
    ],
  },

I'll be closing it, as I don't have any issues w/ the above.


we can't use istioctl 1.5.0 to enabling policy enforcement

Bug description
we download istio 1.5.0 and  use command "istioctl manifest apply --set values.global.disablePolicyChecks=false --set values.pilot.policy.enabled=true" to initialize。when all istio contrainer was running and i use command "kubectl -n istio-system get cm istio -o<EMAIL_ADDRESS>| grep disablePolicyChecks" to check disablePolicyChecks it's output true。
we downgrade istio version to 1.4.6 use the same command, it's output "disablePolicyChecks:false"
like this:
https://github.com/istio/istio/issues/19139#issue-527400476
i think this bug is fixed by 1.4.x, but it reappears in the new version(1.5.0)

I hit the same issue, it seems like the disablePolicyChecks configuration is now only respected when value.policy.mixer.enabled (mixer, not pilot) is set to true. The following config snippet works for me:
spec:
  profile: demo
  values:
    global:
      disablePolicyChecks: false
    mixer:
      policy:
        enabled: true

I follow your  suggest to reset istio 1.5.0 and use command "istioctl manifest apply --set values.global.disablePolicyChecks=false --set values.mixer.policy.enabled=true"  to initialize. it's works，thank you!

but I think we must give up the "mixer policy" because istio official said: "The mixer policy is deprecated in Istio 1.5 and not recommended for production usage." https://istio.io/docs/tasks/policy-enforcement/enabling-policy/

I've not had luck with a custom Mixer adapter on 1.5. It's not clear to me what the depracation means - whether to expect everything to work as before, until 1.7, or whether there are extra steps to re-enable mixer in 1.5.
My use is nowhere near production yet, so I think I'll explore an envoy filter instead.

@charypar I think re-enable mixer in 1.5 is not a good idea, may be 1.6 or 1.7 istio will provide some new api to fix it.
If you want to try envoy lyft/ratelimit, there is some other issues may be can help you: https://github.com/istio/istio/issues/22068

Does anyone run into issue with
istioctl manifest apply --set values.global.disablePolicyChecks=false --set values.mixer.policy.enabled=true on version 1.5.0?
Mine got locked into perpetual UNAVAILABLE:Cluster not available with every request at the ingress gateway. Tried uninstalling Istio multiple times with istioctl. No luck. If I reinstall Istio without --set values.mixer.policy.enabled=true, the ingress gateway works, but then I can never set values.global.disablePolicyChecks to false.

I believe the original issue has been addressed and fixed. Mixer is indeed deprecated, and 1.7 is the final release. Closing. Feel free to reopen if there is still an issue.


[HelpDot] Auto focus search

Details

Fixed Issues
$ https://expensify.slack.com/archives/C02QSAC6BJ8/p1698240549496289
PROPOSAL: N.A.
Tests

cd docs && npm run createDocsRoutes && bundle exec jekyll serve --livereload --safe
Click search icon
Verify that the input auto focuses.

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos
https://github.com/Expensify/App/assets/29673073/381302a0-c73b-4c99-9903-211555228bf2
https://github.com/Expensify/App/assets/29673073/7701e213-3e10-4a01-8ab4-801eb77bf918

deploy expensify workflow will fail because it doesn't have permission to my fork.
reference of this know issue - https://expensify.slack.com/archives/C02QSAC6BJ8/p1698763372012109

@francoisl nice catch haha

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Not an emergency, the failed action was expected since Cloudflare doesn't have access to Rushat's fork.

It doesn't work when deployed. I tried clearing cache, incognito.
Will revert it once I find an actual fix :)
https://github.com/Expensify/App/assets/29673073/b2d42cfd-547c-484b-87ef-cf69d5199f74

Oh, interesting. It seems to work for me.
https://github.com/Expensify/App/assets/2229301/6dd83671-f03b-4da1-af6c-27d36603e14c

that's great!
im still getting the old script, it's possible that cloudflare has cached it in my region's CDN.

Anyway, we can mark this as fixed :)

🚀 Deployed to staging by https://github.com/francoisl in version: 1.3.99-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.99-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/francoisl in version: 1.4.0-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅