The key argument must be one if type string, TypedArray or DataView

Information

Version: 5.32.1
Type: Issue/Story

Description
I'm using a S3 Multer + Multipart file combo, it works in 5.25.1. But for some reason, it stopped working when I updated my project to latest version
Example
Config that stopped working at latest (5.32.1)
 multer: {
    storage: multerS3({
      s3: s3,
      bucket: 'my-cdn',
      key: function(req: Express.Request, file: any, cb: Function) {
        const uuid = uuidv4();
        cb(null, `tmp/${uuid}/${file.originalname}`);
      }
    })
  },

:tada: This issue has been resolved in version 5.33.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[22.11] awsebcli: fix up, requests and future dependencies

(cherry picked from commit 4fbe3e450bb2b8a0d3cbc99d634f080ca8d57cef)
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Perhaps the requests part isn't needed, but it should do no harm.

Surely because of PR #211514

@vcunat yep that would do that. I'm usually following master not release branches. Thank you either way


Accessing server response data

Please take a look at this straightforward code:
$result = Request::sendMessage(['chat_id' => $chatId, 'text' => $message]); $response = $result->getResult(); echo $response->message_id;
This results to the following error:

PHP Fatal Error 'yii\base\ErrorException' with message 'Cannot access protected property Longman\TelegramBot\Entities\Message::$message_id'

How is it possible to access server response data?
Thanks so much.
P.S.: Did not help: https://github.com/akalongman/php-telegram-bot/issues/161

$response->getMessageId() is what you want to use.
You always have to get values using appropriate getter functions.
You can print_r the result to see what data is available.

Thanks so much @jacklul
I didn't think that its required to use a separate getter for each property, but it worked well, thanks.
I'm still unable to get objects inside the response object, for example there is Longman\TelegramBot\Entities\Chat Object inside the response and there is no getChat() method.
How is it possible to get that objects?

getResult() will return Chat object, in that case you just use appropriate getters for Chat object like getFrom().

Hey please explain with an example, i'm not following

$result = Request::sendXXX(); will send the request type of XXX
$result->getResult(); will contain the object you just sent if $result->isOk() is true
So if you sendMessage it will contain sent Message object and it's id in the current chat (for reference in future editing)

How about accessing it before we actually send it ?

That wouldn't make sense, all data for the request will be provided by you in array, so before sending that's all you will have. Extra fields like messages Id will be returned by Telegram after sending, this data can't be 'predicted'.

You can access by:
$telegram = new \Longman\TelegramBot\Telegram($token, 'testname');
$r = new \Longman\TelegramBot\Request($telegram);
$response = $r::getMe();
if($response->isOk())
{
    //$response->reflect() is data array
    echo $response->reflect()['result']['username'];
}

@redflasher Where do you get that code from? Have you implemented some custom functionality into your library?

@noplanman I just try use all public methods of Entity class, that is base class for ServerResponse.
It isn't my library, i just use this lib.

What is the point of that array when you can call getResult()  on response and get response object following Telegram API docs?

@redflasher Just wondering where you get the reflect() method from. And also the Request class can't be instantiated like that. Did you test that code and does it work for you? :thinking:

@noplanman I just add "longman/telegram-bot": "*", into composer.json some days ago and thats all.
And in vendor/longman/telegram-bot/src/Entities/Entity.php
finded
... public function reflect($object = null) ....
Its work for me.
Now it look like:
`
// Create Telegram API object
$telegram = new \Longman\TelegramBot\Telegram($token, 'testname');
        $r = new \Longman\TelegramBot\Request($telegram);

        $response = $r::getMe();

        if($response->isOk())
        {
            $model->name = $response->reflect()['result']['username'];`

Ah, you must have an old version of the library then!
The reflect method got removed in this commit: https://github.com/php-telegram-bot/core/commit/6009277bc1fb7704175b8143420f9445413efcce
Could you check what version you have in Telegram.php please?

"longman/telegram-bot": "*"

This is a back practice, you should define the minimum version required and bump it when you use features of newer releases.


Make groups use the Router's callable resolver

This PR makes the RouteGroup's use the Routers callable resolver instead of using the one in the App class.
This would avoid situations where setting a new callable resolver in the App class after the router has been created, would cause to have different resolvers for routes and groups.

Coverage remained the same at 96.118% when pulling 2eb4f80ec84374daa5ca97a216e983123f5ac38a on mnlg:improvement/group-callable-resolver into 0ce13ef555a1ac4b01153cad64874acb826eeb11 on slimphp:4.x.

Can you add tests please.

#2555 implements this and test coverage has been implemented there as well. Follow issue there.


specify files / directories relative to .dir-locals.el?

I have specified cmake-ide-cmakelists-dir and cmake-ide-build-dir as relative paths, relative to the location of my .dir-locals.el file:
Project structure:
project/
+---- .dir-locals.el
+---- src/
      +---- CMakeLists.txt
      +---- .build/
            +---- debug/
            +---- release/

.dir-locals.el:
((nil . (
  (cmake-ide-cmakelists-dir . "src")
  (cmake-ide-build-dir . "src/.build/debug")
)))

It seems this doesn't work, and cmake-ide requires an absolute path. Is this correct?
Rationale for relative paths:

Multiple colleagues use emacs, and as such would like the checked-in version of .dir-locals.el to work regardless of where they check out the source tree

Allowing relative paths means using git worktree to have multiple branches of the same project checked out in your source tree at the same time will work

How can I specify relative paths in my .dir-locals.el please?

It seems as if cmake-ide-cmakelists-dir is the culprit here.
If I don't set that variable, then cmake-ide--locate-cmakelists-impl will run and find the top-most CMakeLists.txt
As such, is there any reason why I would want to have cmake-ide-cmakelists-dir set?
What does that give me that cmake-ide--locate-cmakelists-impl doesn't?

The only reason to set cmake-ide-cmakelists-dir is to support weird projects (I had one) in which the CMakeLists.txt isn't at the top of the directory tree. It shouldn't normally be used.

OK, thanks Atila.
I'll close this.
On a somewhat related topic, what is the cmake-ide-project-dir useful for?
Thanks again

I can't remember what cmake-ide-project-dir is for right now :P

Ha, fair enough!
As far as I can tell (I'm new to emacs/lisp) it's something to do with irony
(when (... (featurep 'irony) ...))
  (irony-cdb-json-add-compile-commands-path (cmake-ide--locate-project-dir) ...))

No matter, I'll figure it out.
You project is very well structured and easy to read, so it's really helping me learn lisp, so thanks for that! :)


Problem when running some models with cuda

Issue description
Models keep generating dummy result when running with cuda
Expected Behavior
Models stop generating dummy output like running as cpu or vulkan.
Actual Behavior
Models keep generating dummy result.
Steps to reproduce
I use this Qwen2 1.5B model download from here
Running with gpu is auto or cuda
const llama = await getLlama({gpu: 'cuda'})

My Environment

Dependency
Version

Operating System
Windows 10

CPU
AMD Ryzen 7 3700X

GPU
RTX4090, RTX3080

Node.js version
v20.11.1

Typescript version
5.5.2

node-llama-cpp version
3.0.0-beta.36

Additional Context
Here is example I running using https://github.com/withcatai/node-llama-cpp/releases/download/v3.0.0-beta.36/node-llama-cpp-electron-example.Windows.3.0.0-beta.36.x64.exe

These models run normally with 'vulkan', 'cpu', 'metal'
Relevant Features Used

[ ] Metal support
[X] CUDA support
[ ] Grammar

Are you willing to resolve this issue by submitting a Pull Request?
Yes, I have the time, but I don't know how to start. I would need guidance.

There seems to be an issue with Qwen models when using CUDA.
I've seen some suggestions to try other quantizations of a Qwen model since some may still work with CUDA, but I couldn't get any of the quantizations of the model you linked to work with CUDA.
I've done some tests and can confirm this is an issue with llama.cpp and is not something specific to node-llama-cpp.
I'll make it easier to disable the use of CUDA (or any other compute layer you want), so you can force node-llama-cpp to not use it when you know there's an issue with it with a model you want to use.

Try to use IQ quants with cuda.

@giladgd Thank you for your feedback. I found that there is a suggestion of using FlashAttention to solve this problem. How can I enable it in node-llama-cpp?

@bqhuyy I've released a new beta version that allows you to enable flash attention like this:
import {fileURLToPath} from "url";
import path from "path";
import {getLlama, LlamaChatSession} from "node-llama-cpp";

const __dirname = path.dirname(fileURLToPath(import.meta.url));

const llama = await getLlama();
const model = await llama.loadModel({
    modelPath: path.join(__dirname, "models", "dolphin-2.1-mistral-7b.Q4_K_M.gguf"),
    defaultContextFlashAttention: true // it's best to enable it via this setting
});

// you can also pass {flashAttention: true} here to enable it for only this context
const context = await model.createContext();

Let me know if you were able to use any Qwen models with CUDA without flash attention, because if it's impossible to use Qwen models with CUDA without flash attention, then I'll make flash attention enabled by default for Qwen models when CUDA is used.
I haven't enabled flash attention by default for all models since it's still considered experimental, so it may not work well with all models, by if Qwen is unusable without it then it's better to have it enabled by default in this case.

@giladgd
You can use Flash attention with Qwen2 as workaround for this bug, but it will work only with Cuda 12. With Cuda 11, FlashAttention will not change anything.

I found some Qwen2 models that worked on CUDA 12 without flash attention, so since enabling flash attention for Qwen2 models is not always necessary, I won't make it the default because it is still considered experimental.
I'm closing this issue for now since defaultContextFlashAttention: true seems to solve this issue, and I'll make sure to mention using flash attention as a fix for this issue in the documentation of version 3.


Getting junk value like "OK" for redis get command

Problem:
I am getting junk values like "OK" for redis get call.
This issue reproduces often over a particular period of time irrespective of the keys trying to obtain through get command.
I'm Using :
Redis version 2.8
Jedis client 2.5.1 to connect Redis

@rajasuba are you sure you're not sharing your Jedis instance across threads?
In addition to that, I'd recommend if this is happening with latest Jedis 2.8.x version.

@marcosnils I am sure that i am not sharing my jedis instance across threads. And here is a sample snippet like how i am returning my instance to the pool after execution of each thread.
//Returning redis connection
JedisPool jpool = getPool(host, port, password, database);
if (jpool != null) {
try {
if (connection.isNotBroken())
jpool.returnResource(connection);
else
jpool.returnBrokenResource(connection);
} catch (Exception e) {
    }

}

@rajasuba try updating to latest Jedis version and use try-with-resources or jedis.close() instead of returnXXX methods.

@marcosnils :+1:  And between i am not aware of "try-with-resources". Can you help me to know about this?

@rajasuba https://github.com/xetorthio/jedis/wiki/Getting-started#using-jedis-in-a-multithreaded-environment

@marcosnils :+1:

Does the above issue got fixed in any of recent Jedis updates ? If yes, is there any release notes regarding this jedis issue fix? Kindly help me.

@rajasuba. Are you still experiencing this error after the proposed fixes?

@marcosnils Just curious to know about how migrating to the latest Jedis version could fix this issue :)

@rajasuba. A lot has been improved from Jedis 2.5 to 2.8. Can you please at least try to see if the problem persista by upgrading the library and using Jedis.close() as mentioned before? This is the first time that I've seen this kind of issue. So I'm positive that the problem probably comes from your code.
It's hard to provide assistance with so little information and an irreproducible issue

@marcosnils Thank you so much for sharing your knowledge and experience with me. Sure, I'll upgrade Jedis to its latest version and try to see if the problem persists. :+1:

@rajasuba did you notice any improvements?

This is normally occurred when using flawed connection (you may indicate that cause it throws JedisConnectionException). You're encouraged to discard flawed connection and recreate the connection.
This issue is idle for two months, closing.

This was never again reproducible !! 👎


Make quantization rounding bias choice sign agnostic

Kicked off AWCY to test if this has any impact on compression.

Oh, yeah, it does. I should include that in the commit message.
   PSNR | PSNR Cb | PSNR Cr | PSNR HVS |    SSIM | MS SSIM | CIEDE 2000
-0.0644 |  0.2224 |  0.0987 |  -0.0933 | -0.0733 | -0.0626 |    -0.0091


SDF -> WoT: Refactor mapping functions

This PR refactors the existing mappings of individual fields to get a more accurate impression of the code covered by tests.

Codecov Report

Merging #10 (278925a) into main (e91dbc2) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          216       226   +10
=========================================
+ Hits           216       226   +10

Impacted Files
Coverage Δ

converter/sdf_to_wot.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Voltage Open Wire Functions Fix

… to parse through the open wire variable for each minion.

@SijWoo can you review this when you get a chance?


Avoid using important in style sheets

https://uxengineer.com/css-specificity-avoid-important-css/
If there are situations where it is conflicting then we should consider fixing conflicts.
Origin: https://github.com/opensearch-project/oui/pull/131/

Currently present in 73! files. I think this is something we can work on incrementally, as there is some risk to attempting to fix these.

Currently present in 73! files. I think this is something we can work on incrementally, as there is some risk to attempting to fix these.

Completely agree. I think it would probably be possible to break these down into smaller issues.
Additionally, I think it would be nice to understand why important is used. For example, when I was working on breadcrumbs, I needed to use it to override the color of links to a custom color, which otherwise wouldn't be possible.


Become a CNCF project?

What
We find this project very useful and well-made, and we think it could be adopted by many more. When we consider adopting and/or contributing to new projects, it's a big plus if the project is a CNCF project. Others might think alike, and I would therefore suggest becoming a CNCF project.
How
If there is an interest in this, I found the following getting started resources:

https://github.com/cncf/toc/blob/main/process/project_proposals.md
https://github.com/cncf/toc/blob/main/process/sandbox.md

Thank you for the suggestion.
To be honest, I'm not 100% sure if CNCF welcomes this because they have HNC.
This project was started because we found some fundamental problems in the design of HNC,
and we didn't have time to help HNC improve. Accurate and HNC are very similar in their
goals, but the design is different.
We are open to contributing our OSS projects to CNCF or the Linux Foundation,
but do not want to spend time arguing the value of projects compared to existing
projects.


Updated StackExchange.Redis package to RTM

[Fixes #121] Redis is not supported for .netCore, any plans?
@muratg @Tratcher

:shipit:


audiogen_app.py

A Gradio web UI for the new AudioGen module.
Forked from musicgen_app.py and removed some parts that I think are not relevant for AudioGen.
Confirmed it works.

Just signed the contributor license agreement, looking forward to feedback!
Also, please let me know if I need to modify anything. One thing I wasn't sure about was whether AudioGen supports Multi Band Diffusion (Looking at the code I kind of assumed it doesn't but maybe I'm wrong), so just took that out of the UI. Let me know if this needs to be supported as well.

BTW here's what it looks like in action: https://twitter.com/cocktailpeanut/status/1687565351721005056

Works for me also, you are amazing @cocktailpeanut

Thanks for your contribution!
The MBD model is not available for AudioGen for now and using the one trained on MusicGen may not be optimal. Can you remove the use of MBD from the app ?
Another nice addition could be to have text prompt examples to get started similarly to the MusicGen demo, e.g. adding:
gr.Examples(
  fn=predict_full,
  examples=[
      [
          "Typing on a typewriter",
      ],
      [
          "The siren of an emergency vehicle sounds",
      ],
      [
          "A duck quacking as birds chirp and a pigeon cooing",
      ],
      [
          "Thundering sounds while rain pours",
      ],
  ],
  inputs=[text],
  outputs=[output]
)


Reduce Dependabot updates frequency to weekly

Reduces Dependabot updates frequency so it runs weekly on Monday (default) at 10:30 (some time in the day rather than before everyone is in, in the hopes to spread who picks these up a little more).
This change of frequency shouldn't affect when Dependabot raises security updates (according to this bit of Dependabot's documentation)
Closes #3349

Cheers for the quick review 😄

Shall we see if it works then roll out to the other repos we configured? https://github.com/alphagov/govuk-frontend/issues/2960

I think I'll quickly make an extra PR on those so it's easier to judge the impact of changing to weekly (otherwise we'd still have daily ones popping up, even though they seem slightly less frequent on the design-system and docs repo... but it may just be an impression).


Fix argmax_channel method and add preqs in scala mnist tutorial (#7101)

@madjam @javelinjs @Ldpe2G
Are you sure this is correct?
The scala package should convert names to camel cases I think?

@piiswrong  we did not convert the names to camel cases and just use  original names.


edge probability in Binomial distributions

Summary:
The edge case in Binomial distributions.
Description:
In most applied modeling, we are using Binomial_logit in the likelihood and the probability will never be 0. However, in certain models, we may encounter exact zero or one probability in a Binomial distribution.
As expected,  0 ~ binomial(1,  1) leads to log(0).
However, it seems Stan also cannot handle  1 ~ binomial(1,  1), which indeed should be computed as log 1 in log prob.
Reproducible Steps:
log_model='
data {
}
parameters {
  real<upper=0>  beta;
}
model {
 1~binomial(1,  exp(beta*0));
}
'
// running in R:
log_fit=stan(model_code =log_model, data=list())

Current Output:
Log probability evaluates to log(0), i.e. negative infinity.
Stan can't start sampling from this initial value.

Likewise, when encountered in generated quantities, binomial_lpmf(1| 1,1)  returns NaN.
Expected Output:
binomial_lpmf(1 | 1, 1 ) = 0;
Current Version:
v2.23.0

Thanks @yao-yl
I am transferring this to Math as this is where the code lives and will be fixed.

That is the usual edge case for binomial.
It can cause a lot of trouble for us, because when a logistic regression runs into inv_logit(a) == 1 or inv_logit(a) = 0, it's because the log odds a are too large and inv_logit(a) rounds to , or ais too small (large and negative) so thatinv_logit(a)` underflows to 0.
But maybe that should be inv_logit throwing the error.  Also, we should really throw errors on inv_logit underflow or rounding to 1---we should not try to nudge inv_logit(a) just above 0 or just below 1.  Our attempts to do things like that to smooth over the same kinds of issues as led to this issue have led to discontinuous functions and really bad behavior near boundaries.
We also have the same issue with normal, etc.  What happens when sigma -> 0?  should we allow normal(1 | 1, 0) to be 1 (it's now a discrete distribution) or +infinity (as the limit of normal density as sigma -> 0 and y -> mu?  Or should it be an error?  I would argue in that case, it should be an error.

Hi Bob, I think the normal case is a different situation. sigma=0 shifts from a continuous pdf to a discrete pmf. Arguably how to handle discrete measure and continuous measure together remains a general challenge in probabilistic programming lanaguage.
In binomial distribution, binomial_lpmf(1 | 1, 1 ) = 0, or exp(binomial_lpmf(1 | 1, 1 )) = 1,  is well defined, and in agreement with the limit  binomial_lpmf(1 | 1, p ) ->  0 when p -> 1.

I am relatively sure that the BetaBinomial distribution / cdfs should be checked as well. I am not confident enough to raise another issue for that, but if someone is picking this up, then this would be a bonus thing to do.

I started a pull for this: https://github.com/stan-dev/math/pull/1988


Fix the readme's example

As written it tries to compare a tuple to a number:
julia> @test autodiff(f1, Active(1.0)) ≈ 2.0
Error During Test at REPL[236]:1
  Test threw exception
  Expression: autodiff(f1, Active(1.0)) ≈ 2.0
  MethodError: no method matching isapprox(::Tuple{Float64}, ::Float64)

Thanks! Yeah we changed the API for that a while back and clearly didn't update the readme.


Allow logging nanmeans as well.

Since Cognexa/cxflow#150, it is impossible to write nanmeans to CSV training progress (only means are allowed).
This PR provides support for nanmeans as well which is crucial for many variables.

+1 for the tests

I modified the streams subject to @FloopCZ's suggestion.


Test merge permissions

Summary
Changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.01%) to 92.891%

Files with Coverage Reduction
New Missed Lines
%

src/routes/transactions/entities/tests/human-description.builder.ts
1
90.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
7070

Relevant Lines:
7323

💛  - Coveralls


tests fail to compile (dependencies not declared)

[info] Compiling 1 Scala source to /Users/tisue/sbt-launcher-package/target/test-classes...
[error] /Users/tisue/sbt-launcher-package/src/test/scala/RunnerTest.scala:3: object tools is not a member of package scala
[error] import scala.tools.nsc.io._
[error]              ^
[error] /Users/tisue/sbt-launcher-package/src/test/scala/RunnerTest.scala:4: object specs is not a member of package org
[error] import org.specs._
[error]            ^

and so on, and it makes sense because these dependencies are not declared in the build.
note that the current .travis.yml does not compile or run the tests.

Fixed in 88b8386d154a739c538c79f79e877f7d6f8c70dc


Change Creator Message Back to Tooltip

It did work better in the tooltip. You were right, @AeroScripts ...

Add this to the bottom of the tooltip, take away logic to hide when grouped. It should always show.
{rt4} Creator of GogoLoot

Works!


Configure Renovate to preverse semver ranges in package.json

Closes https://github.com/web-platform-tests/wpt-pr-bot/pull/92.
Closes https://github.com/web-platform-tests/wpt-pr-bot/pull/99.

This is the alternative to https://github.com/web-platform-tests/wpt-pr-bot/pull/92, but I don't know how to test that it works other than by merging it.


Prepare technical documents for Deep AQAtik project

Since Deep AQAtik project is progressing, we need to document our works and plans for it.
Following are some related infos:

AQAvit Meeting on Jun. 2, 2021: video, slides (may need download to display properly)
General plan and other related ideas: issue https://github.com/adoptium/aqa-test-tools/issues/355
Data Collection Pipeline: Issue https://github.com/adoptium/aqa-test-tools/issues/412

Feel free to add more resources to this issue. Thanks.

FYI @jabrena @smlambert @llxia Thanks.

Hi @LongyuZhang, @smlambert
I am going to review the current documentation.
What repository is the best place to locate the documentation and diagrams?
Juan Antonio

Hi @jabrena Thanks for the help!
I am thinking about creating a new folder technicalDocuments under MachineLearningPrototype folder, and then in README, add a section to introduce the link to this folder. @smlambert @llxia Could you have other suggestions? Thanks.

@LongyuZhang - I had mentioned to @jabrena to utilize the doc directory to add/organize documentation in subfolders under that... but I am not opposed to your suggestion or other ways to organize it.  (we can also put it somewhere and decide to move it later if we decide a different organization is better).

@smlambert I did not notice the doc folder before. It is a good idea to put the documentation in the doc folder. Thanks.

Hi,
I have just uploaded the docs in the path.
https://github.com/adoptium/aqa-test-tools/pull/453/files
This week, I will collect the path for the different components and I will run the components in isolation.
Cheers


Admin details

Pls can you drop the admin details for your work. This a wonderful concept and I want to adopt it for my school project if u don't mind.

Happy to help you out.
I just added new .sql file "mcchstexam.sql" in the project folder. Use it instead of the old old one. The username is 'Admin' and the password 'admin'

Thanks I really appreciate. I will try it out and give you feedback

When I get to the admin page nothing works, (the manage department, manage questions etc) none of dem is working pls help me out on these

I fix the issue.
download and update this file from the project folder  assets/js/main.js

It worked thanks. Pls can you give me the format to add student and questions using excel.

Pls what the format for adding students?

When you add multiple courses for exam it doesn't reflect in the student dashboard during d exams


is there still a way to deploy this project on cloudflare?

As said by last issues, this project can not be deployed because of deprectaion (node and wrangler V1). Is the a way to deploy this project anyway?
by the way, thx for your work.

im getting this too

Today I'm stucked with the deployment of this project all day, there were too many compatibility issues, perhaps it would be faster to rewrite it with new technology.

Thank you @kxxoling, while I still plan to rewrite this repo as well, I can’t promise anything, so I will at least link yours till then.

Okey, I have almost complete rewrite a new status page with Vike + React + TypeScript + wrangler@latest + Better DX/UX I need: https://github.com/yunsii/cf-worker-status-page-pro
And I will migrate it to Next.js with Cloudflare Pages laterly.


special character in file name

In my case, gist file extension is ".scala".
So, I write below in my post.
{% gist jungbin-kim/acc54d54af4ff954105338534636526a Kakao-coding-test-#1.scala %}
However, it generates
https://gist.github.com/jungbin-kim/acc54d54af4ff954105338534636526a.js?file=Kakao-coding-test-
I think it miss special character like '#'
I expect like below
https://gist.github.com/jungbin-kim/acc54d54af4ff954105338534636526a?file=Kakao-coding-test-#1.scala
It might be involved at this line.
https://github.com/jekyll/jekyll-gist/blob/6ab6a20c293e02f0f5cc51a2ba8ed3f933d88c9a/lib/jekyll-gist/gist_tag.rb#L59
Thank you

The actual url is https://gist.github.com/jungbin-kim/acc54d54af4ff954105338534636526a?file=Kakao-coding-test-#file-kakao-coding-test-1-scala
https://github.com/jekyll/jekyll-gist/blob/6ab6a20c293e02f0f5cc51a2ba8ed3f933d88c9a/lib/jekyll-gist/gist_tag.rb#L60
We need to sanitize filename by stripping special characters

It looks like GitHub just strips octothorps when creating ids. I guess we should strip them as well when creating the URL.


Current State of Project

Wanted to check and see how this project is progressing.  Is it working to your expectations?  Has it been deployed in production?
I had posted an issue with the Spring Cloud team at one point looking for something like this for UI.

Thanks for the interest! We are still using it in our development.  It hasn't been put into production yet, but it's going that way.  We haven't had any issues within our development so far, but it hasn't been stress tested yet, so if you take it further, I'd love to hear about it!  What are your specific concerns?

Thanks for the quick response.  I will keep you posted on how it works on our end.  We had seriously thought about the Node version of Composure, I like Spring and didn't want to leave the ecosystem.


File added to volume directory in the DockerFile doesn't exist if added after volume is created.

Description of Problem:
I add a file to a volume in my dockerfile after creating the volume. Upon running a container with the image I created, the files added after the volume was created are missing, where the files before are there.
 Here's the box:
https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box
I installed docker and docker composer and nsenter.
How to reproduce:
I have a docker file with the contents here:
FROM nginx
RUN rm /var/log/nginx/*.log
RUN touch /var/log/nginx/beforevolume.txt
VOLUME /var/log/nginx/
RUN touch /var/log/nginx/aftervolume.txt
CMD ls -larh /var/log/nginx

I build it with this command:
docker build --tag "my_nginx_data" .

When it runs, I see this output:
vagrant@vagrant-ubuntu-trusty-64:/vagrant/home/docker/nginx$ docker run --rm my_nginx_data
total 8.0K
-rw-r--r--  1 root root    0 Jul  3 05:37 beforevolume.txt
drwxr-xr-x 10 root root 4.0K Jul  3 05:37 ..
drwxr-xr-x  2 root root 4.0K Jul  3 19:12 .

Expected Behavior:
What happened to the "aftervolume.txt"? I expected to see them both there. I'm not mapping the volume to a host directory.

This is expected behavior. See https://docs.docker.com/userguide/dockervolumes/

Changes to a data volume will not be included when you update an image.

Also dup of #13117 and #14122

I totally missed that each line in the Dockerfile is updating the image. My understanding was that updating the image came when you rebuilt the whole thing creating a new image. However, with the way the layering works, I'm guessing that there is no difference?
When I build it I see this output:
Sending build context to Docker daemon 2.048 kB
Sending build context to Docker daemon
Step 0 : FROM nginx
 ---> 319d2015d149
Step 1 : RUN rm /var/log/nginx/*.log
 ---> Running in fb3507657296
 ---> 627d83c567e4
Removing intermediate container fb3507657296
Step 2 : RUN touch /var/log/nginx/beforevolume.txt
 ---> Running in 6029a371bac2
 ---> afde50603c7d
Removing intermediate container 6029a371bac2
Step 3 : VOLUME /var/log/nginx/
 ---> Running in 9905cd836755
 ---> c6b3528e497d
Removing intermediate container 9905cd836755
Step 4 : RUN touch /var/log/nginx/aftervolume.txt
 ---> Running in de1b86a47546
 ---> ffb593c78f4c
Removing intermediate container de1b86a47546
Step 5 : CMD ls -larh /var/log/nginx
 ---> Running in cbacbfb06ff7
 ---> b7b871f58ed2
Removing intermediate container cbacbfb06ff7
Successfully built b7b871f58ed2

In my thinking the image wasn't created until the last line. Is it just bad practice to do anything to volumes when you are writing a Dockerfile?

@phemmer is correct, this is expected behavior (but it is confusing if you're not aware of it). Basically, adding a VOLUME declaration to your Dockerfile, makes everything inside the volume's path "immutable", because a (new) volume is created for each build step after that.
Each build step is running in a new container, and committed as a new ("intermediate") image / layer.
If you really need a path to be a volume, it's best to move the VOLUME instruction to the end of your Dockerfile or, alternatively, don't use VOLUME, but specify the volume at run time, using the -v/--volume option.
I'm going to close this issue for the reasons mentioned above, but feel free to comment her after I've closed it.


Restarting DFT calculation from DF electron density

Assume I have the electron density represented as the expansion coefficients under an DF auxiliary basis (which come from machine learning prediction). Although the kinetic energy cannot be evaluated without an AO basis, theoretically the Kohn-Sham effective potential has no kinetic term and should be able to be constructed from DF density (assume we are using PBE). Then we might restart the DFT from this effective potential.
Is this possible in pyscf? And if so, may I have some hints on how to do this?

The XC potential can be computed with https://github.com/pyscf/pyscf/blob/14d88828cd1f18f1e5358da1445355bde55322a1/pyscf/dft/numint.py#L557, where rho is the electron density on the grid. The Coulomb potential may be computed with 3 center 2 electron integrals, mol.intor( 'int3c2e' ).

@fishjojo Thanks for your reply! Since I am new to pyscf, may I ask for a bit more detailed instruction? Do I have to hack the source code to do this, or I can simply overwrite some functions?


protobuf mismatch between C++/Python for 1.66.1

What version of gRPC and what language are you using?
1.66.1, C++ and Python
What operating system (Linux, Windows,...) and version?
Windows
What runtime / compiler are you using (e.g. python version or version of gcc)
MSVC 17.11, Python 3.12.4
What did you do?
Our C++ build uses GRPC 1.66.1. The protobuf version for that tag is 5.27.2 (from third_party/protobuf/CMakeLists.txt -> protobuf_VERSION_STRING).
pip install of grpcio and grpcio-tools version 1.66.1 will install protobuf version 5.28.0.
This results in the following Python warning:
[...\Lib\site-packages\google\protobuf\runtime_version.py:112](file:///.../Lib/site-packages/google/protobuf/runtime_version.py#line=111): UserWarning: Protobuf gencode version 5.27.2 is older than the runtime version 5.28.0 at Feature.proto. Please avoid checked-in Protobuf gencode that can be obsolete.
What did you expect to see?
I would expect to see that these versions match and no warning is generated.
What did you see instead?
The warning
Anything else we should know about your project / environment?

@XuanWang-Amos

Hi, grpc_tools have a fixed dependency on protobuf version, currently it's 5.27.2, we'll update Protobuf version in our next release.
You can also find more details and our recommendation here: https://github.com/grpc/grpc/issues/37609#issuecomment-2341657936


fix: Add enumerated values for fontFamily/fontEdge

Adds the following allowed values for fontFamily and fontEdge:
            "enum": [
                "monospaced_serif",
                "proportional_serif",
                "monospaced_sanserif",
                "proportional_sanserif",
                "smallcaps",
                "cursive",
                "casual",
                null
            ]

and
            "enum": [
                "none",
                "raised",
                "depressed",
                "uniform",
                "drop_shadow_left",
                "drop_shadow_right",
                null
            ]

:tada: This PR is included in version 0.17.1-next.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.18.0-proposed.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.17.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Overhaul Effect signs

Update Effect signs to make them dynamically accept all valid types of Effects, like Night vision etc.
Experiment will making as little hardcoded as possible.

Now "heal" and "gamemode" effects signs have hardcoded logic.
Otherwise the second line can be used to specify any PotionEffectType, "Resistance" can be shortened to "Resist" to allow for limitted characters, for example "DAMAGE_RESIST" is valid.
The 3rd line will be in the format of "(amplifier):(duration)".
Final example:
[pa]
effect
damage_resist
5:1000


Refactor PriorityQueue ==.

Motivation:
The new implementation doesn't convert lhs and rhs to arrays, thereby saving 2 allocations.
Modifications:
Changed the body of priority queue ==.
Result:
The comparison will be faster and use less memory.

@swift-nio-bot test this please

De nada. Sorry I was dragging my feet with this lol.


tBTC dapp, redemption - error at step 5, gas required exceeds allowance (8000029) or always failing transaction

Description:
Everything goes smoothly in the redemption process, until step 5:
I can see this error (screenshot below)
"gas required exceeds allowance (8000029) or always failing transaction"
while tBTC bot sends notification on successful transaction
https://ropsten.etherscan.io/tx/0x81efec088375eddcaf51da221f74a0f0271410af81bbee50c7210c6816fe2702
15 minutes passed and there's no indication of testBTC transaction on my wallet, while there's less tBTC on my ETH wallet.
Steps to reproduce the behavior:

Go to tBTC dapp redemption process
Successfully pass steps 1-4
See error at step 5

Expected behavior:
Receiving testnetBTC transaction on my wallet.
Environment details:
OS: macOS Mojave 10.14.6 (18G5033)
Web Browser: Google Chrome, 83.0.4103.106 (Official Build) (64-bit)
Wallet: Metamask (Chrome extension), Version 8.0.4
Screenshots

If you get a chance to reproduce this, could you send us the URL on the tBTC dApp where you saw this?

@Shadowfiend sure, will try to, but might not encounter this anymore, since only got 4 more 0.01 deposits to redeem

I got this error but at step 4/5.
The url was
https://dapp.test.tbtc.network/deposit/0x20135a85181b4fbA0E77a9A098e9C626f2614B9d/prove
Log file: dapp.test.tbtc.network-1595646308746.log
Screenshot: Annotation 2020-07-25 040445
My environment:
Google Chrome 84.0.4147.89 (Official Build) (64-bit)
MetaMask Chrome Extension 8.0.5
Windows 10 Pro 64-bit 1909 build 18363.959

I managed to complete the process by refreshing the page at
 https://dapp.test.tbtc.network/deposit/0x20135a85181b4fbA0E77a9A098e9C626f2614B9d/prove
and I minted the 0.49975 testnet tBTC.

My apologies, my previous two comments were in relation to the deposit process, and I just realised this issue was opened for the redemption process.
However I can confirm that I am now getting the same error as the orginal posted issue, on step 5 of the redemption process. I get the error on both tBTCs that I am trying to redeem. The urls that that the errors appear on are:
https://dapp.test.tbtc.network/deposit/0x1F4A3bf58c60bD9e6d5C3Cf7d0bC7Ce90b70078F/redemption/prove
https://dapp.test.tbtc.network/deposit/0xc87D9da83f0A32bE4802e6CE9346a42ce48686b4/redemption/prove
The app just hangs on this page, the error messages don't show in the app for me, but I can see them in the console log:
MetaMask - RPC Error: gas required exceeds allowance (8000000) or always failing transaction {code: -32000, message: "gas required exceeds allowance (8000000) or always failing transaction"}
Uncaught (in promise) {code: -32000, message: "gas required exceeds allowance (8000000) or always failing transaction"}
Log file:
dapp.test.tbtc.network-1595812772493.log
My environment:
Google Chrome 84.0.4147.89 (Official Build) (64-bit)
MetaMask Chrome Extension 8.0.5
Windows 10 Pro 64-bit 1909 build 18363.959

This is doubly intriguing because I don't see the issue. If you get a Metamask popup, could you go ahead and submit it and then share the log + a link to the Metamask transaction?

A MetaMask popup does indeed appear, I submitted it for the url:
https://dapp.test.tbtc.network/deposit/0x1F4A3bf58c60bD9e6d5C3Cf7d0bC7Ce90b70078F/redemption/prove
However the error message didn't appear this time, the page just hangs at step 5/6 (I waited over 2 hours and nothing appeared).
Transaction ID:
0xcb2f66ad2129821bb30641f3a88c1084e8d2d691937cfa0757fa94b4ad686afb
Console log file:
dapp.test.tbtc.network-1595912505652.log

I revisited the url:
https://dapp.test.tbtc.network/deposit/0x1F4A3bf58c60bD9e6d5C3Cf7d0bC7Ce90b70078F/redemption/prove
and it instantly went to step 6 'Redemption Complete' and I have received the testnet bitcoin back.
For the other tBTC that I've been trying to redeem, with the url:
https://dapp.test.tbtc.network/deposit/0xc87D9da83f0A32bE4802e6CE9346a42ce48686b4/redemption/prove
it remains stuck at step 5 of the redemption process, and this time the metamask popup didn't appear.
Console log file:
dapp.test.tbtc.network-1595968086470.log
Dapp error log file (changed to .txt file so that github would accept it):
tbtc-dapp-console-log-1595968120722.json.txt


Convert JQuery to vanilla JS/DOM API

Fixes #2.
The JQuery definitely worked when I wrote this script, so I assumed reddit must have been using it; but if it was, it's not any more.
@kindaro, could you please test this new version (https://github.com/acarapetis/mathjax-for-reddit/raw/remove-jquery/mathjax_for_reddit.user.js) and let me know how it goes?

Works for me!

LaTeX gets rendered.
Only a bounded number of errors appear on the browser console.

@acarapetis   So how do you feel about merging this?

@kindaro Merged, I'll update the links on /r/math tonight.


feat(ui): settings screen revamp

Revamp Settings Screen with new theme
https://user-images.githubusercontent.com/19255438/209341100-c1882a33-0c58-46ef-ba2b-760fbc772a3f.mov

Good start @HunnySajid.  Could you make the username and avatar inputs look better for long urls, etc.  Also the save and toggle buttons don't look good.  I'm not sure how to improve them, or what to replace them with but could you take a shot at making them look more professional?

Hey @2byrds
Instead of image url, I have added an image uploader component. Now user can upload or change image instead of pasting url. Also converted the toggle into buttons.
What do you think about it?
https://user-images.githubusercontent.com/19255438/211221562-f11fea54-319f-4b44-9b13-e89f58c3d4ac.mov

Looks like a great start @HunnySajid . We'll need to add an issue for cropping images so they aren't stretched.


Base64-encode BinaryT tag values for the Zipkin V2 API

utf8 will error when passed an actual binary (non-utf8) value.
Follow-up for #19

Admittedly, I’m not actually sure what the purpose of binary tag values is 🤷♂


error with pydantic==2.0

🐛 Bug
Installed napari 0.4.17 via conda-forge, upon calling napari in the console an error with pydantic occurred within the evented_model class.
Switching to pydantic 1.10.0 fixed this issue.
To Reproduce
Steps to reproduce the behavior:

% micromamba create -n napari napari
(napari) % napari
Traceback (most recent call last):
File "/Users//micromamba/envs/napari/bin/napari", line 6, in
from napari.main import main
File "/Users/markuszehner/micromamba/envs/napari/lib/python3.10/site-packages/napari/main.py", line 16, in
from .utils.translations import trans
File "/Users/markuszehner/micromamba/envs/napari/lib/python3.10/site-packages/napari/utils/init.py", line 2, in
from .colormaps import Colormap
File "/Users/markuszehner/micromamba/envs/napari/lib/python3.10/site-packages/napari/utils/colormaps/init.py", line 2, in
from .colormap import Colormap
File "/Users/markuszehner/micromamba/envs/napari/lib/python3.10/site-packages/napari/utils/colormaps/colormap.py", line 9, in
from ..events import EventedModel
File "/Users/markuszehner/micromamba/envs/napari/lib/python3.10/site-packages/napari/utils/events/init.py", line 15, in
from .evented_model import EventedModel
File "/Users/markuszehner/micromamba/envs/napari/lib/python3.10/site-packages/napari/utils/events/evented_model.py", line 66, in
class EventedMetaclass(main.ModelMetaclass):
File "/Users/markuszehner/micromamba/envs/napari/lib/python3.10/site-packages/pydantic/_migration.py", line 289, in wrapper
raise AttributeError(f'module {name!r} has no attribute {name!r}')
AttributeError: module 'pydantic._migration' has no attribute 'ModelMetaclass'

Expected behavior
Opening of the viewer.
Environment

Please copy and paste the information at napari info option in help menubar here:
Napari did not open.

Any other relevant information:
Works with pydantic 1.10.0

Additional context
installed with micromamba on ARM M1.

Yes, this is "fixed" in the upcoming 0.4.18 release in that we forbid pydantic>=2 for that release. We also hope to push an update to the 0.4.17 recipe to pin pydantic to <2 for that release. In future releases obviously we will try to migrate to support both pydantic 1 and 2. Thanks for the report, and I'm glad you already know the workaround for you! 😊

This is fixed now @MarkusZehner, by @jaimergp in conda-forge/conda-forge-repodata-patches-feedstock#477! 🥳

Downgrading to pydantic < 2 now raises a TypeError: issubclass() arg 1 must be a class, which seems to be related to npe2. Downgrading it to npe2-0.4.0 solved it for me.

@macromeer Can you clarify, you want to use napari 0.4.19 but with pydantic < 2 ? and that gives an error?

Yes, error of OP as well as mine can be reproduced following this: https://github.com/royerlab/aydin?tab=readme-ov-file#installation-of-aydin-in-conda
Am Montag, 11. März 2024 um 22:06, Peter Sobolewski @.***(mailto:Am Montag, 11. März 2024 um 22:06, Peter Sobolewski < schrieb:

@.***(https://github.com/macromeer) Can you clarify, you want to use napari 0.4.19 but with pydantic < 2 ? and that gives an error?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@macromeer I think we're going to need more info, because I don't see pydantic in the aydin dependencies. I also can't install it due to conflicting pins.
Assuming you installed everything via pip like those instructions, can you post the output of:
napari --info and
pip show pydantic ?

napari --info

napari: 0.4.15
Platform: Linux-6.5.0-21-generic-x86_64-with-glibc2.35
System: Ubuntu 22.04.3 LTS
Python: 3.9.18 | packaged by conda-forge | (main, Dec 23 2023, 16:33:10)  [GCC 12.3.0]
Qt: 5.15.2
PyQt5: 5.15.10
NumPy: 1.26.4
SciPy: 1.12.0
Dask: 2024.2.1
VisPy: 0.14.1

pip show pydantic

Name: pydantic
Version: 1.10.0
Summary: Data validation and settings management using python type hints
Home-page: https://github.com/pydantic/pydantic
Author: Samuel Colvin
Author-email<EMAIL_ADDRESS>License: MIT
Location: /opt/miniforge3/envs/aydin_env/lib/python3.9/site-packages
Requires: typing-extensions
Required-by: napari, npe2

But unfortunately, downgrading both does not work anyways, I get <class 'TypeError'> unhashable type: 'Color'

Napari 0.4.15 is old and may be incompatible with some more recent releases of packages.
Could you update napari to 0.4.19?

Indeed, unfortunately we can't afford to support old versions of napari at this time, as we struggle to maintain even the main version.
However, this does give me an idea, which is that maybe with each release we should produce a locked conda environment with all dependencies pinned, so that each version can be run long into the future with the correct dependencies for its release.
In the meantime @macromeer, if you need napari 0.4.15 specifically, you could use pypi-timemachine to install napari and dependencies from the date that napari 0.4.15 was released (Mar 11 2022).

Napari 0.4.15 is old and may be incompatible with some more recent releases of packages.
Could you update napari to 0.4.19?

Aydin doesn't seem to be actively maintained, and aydin 0.1.15 requires napari==0.4.15, so I am kind of stuck with that version and its dependencies.

Indeed, unfortunately we can't afford to support old versions of napari at this time, as we struggle to maintain even the main version.
However, this does give me an idea, which is that maybe with each release we should produce a locked conda environment with all dependencies pinned, so that each version can be run long into the future with the correct dependencies for its release.
In the meantime @macromeer, if you need napari 0.4.15 specifically, you could use pypi-timemachine to install napari and dependencies from the date that napari 0.4.15 was released (Mar 11 2022).

Thanks, I will try that!

Unfortunately, we provide constraints since 0.4.18, But I think that adding conda constraints may also be a good idea.

For 0.4.18 a user should use constraints from this directory https://github.com/napari/napari/tree/v0.4.18/resources/constraints

I guess in general, it's <repo root>/tree/<tag>/resources/constraints?

yes


Fixed CLI command for deactivate tenant

Fixed CLI command for deactivate tenant

@dinithis Thanks for the fix! It seems like the merge process fails with the below error:
Falling back to patching base and 3-way merge...
Auto-merging service-stubs/org.apache.stratos.cloud.controller.service.stub/src/main/resources/CloudControllerService.wsdl
CONFLICT (content): Merge conflict in service-stubs/org.apache.stratos.cloud.controller.service.stub/src/main/resources/CloudControllerService.wsdl
Auto-merging components/org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/util/converter/ObjectConverter.java
Auto-merging components/org.apache.stratos.cloud.controller/src/main/java/org/apache/stratos/cloud/controller/services/impl/CloudControllerServiceImpl.java
Auto-merging components/org.apache.stratos.cli/src/main/java/org/apache/stratos/cli/RestCommandLineService.java
Failed to merge in the changes.
Patch failed at 0009 Updating kubernetes host definition and adding private and public ip addresses

Thanks for the fix @dinithis! I have now merged this to 4.1.0-beta-deployment-policy-fix branch.


before commands not executing

Any before commands I have specified, like a cd into a directory, don't seem to be executed anymore. I'm basically taking an example that works with terminitor and attempting to get it running under consular.

which core are you using?

If you are using consular-osx, i've fixed it here: https://github.com/achiu/consular-osx/commit/8f993563e43acc88ac059ab9d00369ceb1404c21. Let me know if this works for you. If not feel free to reopen the ticket.

Works like a charm. Thanks!


Azure Auth with Managed Identities How To has bad links

Describe the issue
The links to the official documentation appear out of date, at least for ACA
URL of the docs
https://docs.dapr.io/developing-applications/integrations/azure/azure-authentication/howto-mi/
Expected content
Links to the correct MSFT docs
Screenshots

Additional context
The web archive link shows something significantly different than today.

@KashMoneyMillionaire - Can you add more details here. Which links do you consider out of date what do you expect they should reference?

#4071 appears to fix this, thanks!


Appending to association updates all already existing rows

Considering these structs:
type Prospect struct {
	gorm.Model
	Name           string
	EmailAddresses []Email `gorm:"ForeignKey:ProspectId;AssociationForeignKey:ID"`
}

type Email struct {
	gorm.Model
	ProspectId uint `sql:"index"`
	Email      string
	Default    bool
}

When i append another email to a prospect with this piece of code:
res := env.DB().Model(&p).Association("EmailAddresses").Append(models.Email{
		Email<EMAIL_ADDRESS>		Default:    false,
	})

For all the already existing email rows an update query gets called to update the 'updated_at' row. This seems like a bug or is this expected behaviour?

Hi @Sef1995
It is expected behaviour.


Does USBX support multiple device type switching?

The processor used in my project is STM32F105RBT6. I transplanted ThreadX and USBX for development. I want to know if USBX supports multiple device type switching. For example, USB is a normal USB device when it is working normally. When firmware update is required, enter USB DFU mode?

Host recognized device is actually from what device reported (descriptors), if your application start different USB framework on different triggers, host will see different devices.
So yes, USBX supports multiple device type switching.

I know this situation, I mean, for example, the currently running USB class is CDC. After receiving the command, can it be converted to HID through some operations without resetting the system?

@xiaocq2001  how can i send a multiple audio isochrone packet in host app ?

@BlueShark7 Not sure what you mean for multiple audio isochrones packet, do you mean the usage of host audio class APIs?

@xiaocq2001 yess i want to write to audio interface

@BlueShark7 sorry to reply late, can you create another issue to discuss since it's another topic, thanks.


[PRM-985] Removed breadcrumbs from IndexView

Added new commit for adding welsh messages + defaulted the error template to show back link


Catkin build not supported !!

Describe the bug
While building the package using catkin build, i am getting eror related to ecl.h missing. Can anyone please tel me why px4 Firmware still does not support catkin environment.

It's a build system error that needs to be fixed. Once fixed we need a very simple catkin build test in our CI system (http://ci.px4.io:8080/blue/organizations/jenkins/Firmware/activity) to ensure it stays working.

Duplicate https://github.com/PX4/Firmware/issues/9554


Text Editor Improvement

Issue Type: Feature Request
I want to use the feature available in many other IDEs where i can hold ALT and highlight text vertically.
Azure Data Studio version: azuredatastudio 1.3.9 (cacf0777c747046af6839de3688d709b10ef9fca, 2019-01-14T23:30:09.442Z)
OS version: Windows_NT x64 10.0.16299

Hi Brady, we inherit this behavior from VS Code where you can hold shift+alt to select text vertically. Let us know if this meets your ask.

@MadMonkeyMan please try using Shift-Alt for box select as @yualan noted.  Thanks!

That worked
Get Outlook for Androidhttps://aka.ms/ghei36

From: Karl Burtram<EMAIL_ADDRESS>Sent: Monday, February 25, 2019 3:44:23 PM
To: Microsoft/azuredatastudio
Cc: Brady Smith; Mention
Subject: Re: [Microsoft/azuredatastudio] Text Editor Improvement (#3872)
Closed #3872https://github.com/Microsoft/azuredatastudio/issues/3872.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/azuredatastudio/issues/3872#event-2163102998, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVCVmiVI4-L60fhZKe-IPB01wfUVMwe6ks5vRFk3gaJpZM4ac65G.


Laravel route locale middleware not working with model binding

Laravel Version: 8.12.3
PHP Version: 7.4
Database Driver & Version: Mysql 5.7

Description:
I use this guide: https://mydnic.be/post/how-to-build-an-efficient-and-seo-friendly-multilingual-architecture-in-laravel-v2
I have these routes and middleware:
$locale = request()->segment(1);

Route::middleware('localized')->prefix($locale)->group(function() {
     Route::get('/contacts', 'ContactController@index');
     Route::get('/page/{page}', 'PageController@index');
});

And middleware localized from Kernel.php -> routeMiddleware:
public function handle(Request $request, Closure $next)
{
    if (!array_key_exists($request->segment(1), config('translatable.locales'))) {
        $segments = $request->segments();

        $segments = Arr::prepend($segments, config('app.fallback_locale'));

        if($request->session()->has('language')) {
            $segments[0] = session('language');
        }

        return redirect()->to(implode('/', $segments));
    }

    return $next($request);
}

When I access to: site.test/contacts he redirect me on locale: site.com/en/contacts
When I access to  site.test/page/test I got 404 not found, If I access to: site.com/en/page/test then page working. Problem with redirect on locale with route model binding.
In Controller Page I have:
public function index(Page $page)
{
    return view('page', compact('page'));
}

In translatable.php:
'locales' => [
    'de' => 'Deutsch',
    'en' => 'English',
],

In AppServiceProvider:
public function boot()
{
    if(array_key_exists(request()->segment(1), config('translatable.locales'))) {
        app()->setLocale(request()->segment(1));
    }
}

You can't use the request global in a routes file.


Update README.md

Copy edited (e.g. ref. http://en.wikipedia.org/wiki/Bash_(Unix_shell)).

Hi @PeterMortensen, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

This is still waiting on author, ping @PeterMortensen.

Been over a week with no update from author; closing.


[New Feature] Broker support AliyunOss

Is your feature request related to a problem? Please describe.
Broker support AliyunOss
Describe the solution you'd like
Broker support AliyunOss
Describe alternatives you've considered
Broker support AliyunOss

you can use load with s3


set_background_color error on windows machine

Running any function from visuals (set_background_color, FixationDot, etc) on windows results in the following error:
Traceback (most recent call last):
  File "C:\Experiments\mbagheri\aud_att_int_SAMPLE\aud_att_int.py", line 35, in <module>
    ec.set_background_color([0.2] * 3)
  File "C:\Experiments\mbagheri\aud_att_int_SAMPLE\expyfun\_experiment_controller.py", line 540, in set_background_color
    Rectangle(self, pos=[0, 0, 2.1, 2.1], fill_color=color).draw()
  File "C:\Experiments\mbagheri\aud_att_int_SAMPLE\expyfun\visual\_visual.py", line 476, in __init__
    line_loop=True)
  File "C:\Experiments\mbagheri\aud_att_int_SAMPLE\expyfun\visual\_visual.py", line 191, in __init__
    _check_log(vertex, gl.glGetShaderInfoLog)
  File "C:\Experiments\mbagheri\aud_att_int_SAMPLE\expyfun\visual\_visual.py", line 172, in _check_log
    raise RuntimeError(message)
RuntimeError: No errors.

Updating pyglet didn't help. Any ideas?

Can you try downgrading pyglet? @drammock ran tests a few days ago on
windows and they passed, so I suspect there is a regression in a dependency

@Eric89GXL FYI this is happening on the laptop we use for task practice during MEG capping.  I'm suspecting an expyfun issue, not a pyglet one.  One notable irregularity was that the machine had no expyfun config file set up.  I'm trying now to see if I can reproduce on windows on my laptop.

reproduced on my laptop:
from expyfun import ExperimentController

kwargs = dict(exp_name='test', session='test', participant='test',
              output_dir=None, version='796be20')

with ExperimentController(**kwargs) as ec:
    ec.set_background_color([0.2] * 3)
    ec.wait_secs(1.5)

2016-07-26 01:29:22,040 - INFO    - Expyfun: Setting up Pyglet audio
2016-07-26 01:29:22,118 - INFO    - Expyfun: Setting up screen
2016-07-26 01:29:22,338 - EXP     - Expyfun: Set screen visibility True
2016-07-26 01:29:22,509 - INFO    - Expyfun: Initializing dummy triggering mode
2016-07-26 01:29:22,525 - INFO    - Expyfun: Initialization complete
2016-07-26 01:29:22,525 - EXP     - Expyfun: Subject: test
2016-07-26 01:29:22,525 - EXP     - Expyfun: Session: test
2016-07-26 01:29:22,650 - EXP     - Expyfun: Audio stopped and reset.
Traceback (most recent call last):
  File "D:\Desktop\test\test.py", line 9, in <module>
    ec.set_background_color([0.2] * 3)
  File "D:\Desktop\test\expyfun\_experiment_controller.py", line 540, in set_background_color
    Rectangle(self, pos=[0, 0, 2.1, 2.1], fill_color=color).draw()
  File "D:\Desktop\test\expyfun\visual\_visual.py", line 476, in __init__
    line_loop=True)
  File "D:\Desktop\test\expyfun\visual\_visual.py", line 191, in __init__
    _check_log(vertex, gl.glGetShaderInfoLog)
  File "D:\Desktop\test\expyfun\visual\_visual.py", line 172, in _check_log
    raise RuntimeError(message)
RuntimeError: No errors.

Not positive, but it looks like the _get_log function here is expected to return None (or an empty string?) when there are no errors, but on my laptop and the training laptop, it is returning 'no errors'.  Creating PR now...

That machine doesn't need a configuration file, the defaults should be
fine.
We never had that problem before, I wonder why it's happening now. Didn't
happen on Marlo, right?
In any case, I agree it should be fine to check for the no error message


auth: Add credential service

This pull request covers the following:

Splits the index.d.ts file which allows to substitute the typings (i.e., index.d.ts import for credentials will map to src/credential.d.ts or src/credential/index.d.ts depending on if auto-generated types are toggled).

Note: This might introduce the duplicate "callable" bug in the documentation web-page

Refactors credential.ts to be a separate service outside of auth
Extracted the credentials related component of auth/*.spec.ts into new unit test folder credential/*.spec.ts
Adds documentation for auto-generated typings, as part of #992

Thanks for the feedback. I re-attempted this using a simpler approach instead of introducing an entirely new service for credentials. Right now I'm just mapping the functions from the original property credential in FirebaseNamespace to another file in credential.


blog/hetzner-with-coolify/

My move from Vercel to Coolify on Hetzner
https://hayes.software/blog/hetzner-with-coolify/

It works!


my phone doesn't boot anymore

i accidentally disconnected the device and now pushing power button doesn't work anymore, is there a way to boot again?

put out battery connector & put on again


Apply nuget packaging through github

Currently the nuget package is being updated manually. Publish from github, that pushes to nuget.

Yaml is working to automatically push when versioning is updated in the project file. This issue can be closed.


NAME1

Closing Issue/Referencing Issue
issue reference (#)
Changes Made In Pull Request

https://www.codechef.com/problems/NAME1

Inactive Repo


Frontend 183 public view - Home Page Improvements for BHPA

Replaced color palettes with a text color scheme for improved consistency and readability.
Resized CarrouselHero height dynamically based on screen height for a better user experience.
Combined 'Learn More' and 'About Us' into a single page and renamed 'SpreadWord' to 'Get Involved' for better organization and user understanding.
Changed background color of forgetpump Outlined Button and Partners and CardLinkSection components for better visual appeal.
Added ScrollToTop button for easier navigation.
Removed Home link from navbar and added link to main page on logo click for better navigation flow.
Redesigned Footer for improved usability.

Ticket number: 183

These are some console log error in the chrome browser. Please look at it and fix it so there's no more error message. The error doesn't affect display but it can later lead to problems with missing elements.
react-jsx-dev-runtime.development.js:87 Warning: Each child in a list should have a unique "key" prop.
Check the render method of Navbar. See https://reactjs.org/link/warning-keys for more information.
at List (http://localhost:3000/static/js/bundle.js:38010:82)
at Navbar (http://localhost:3000/static/js/bundle.js:9719:86)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-jsx-dev-runtime.development.js:87
error @ react-jsx-dev-runtime.development.js:61
validateExplicitKey @ react-jsx-dev-runtime.development.js:1078
validateChildKeys @ react-jsx-dev-runtime.development.js:1105
jsxWithValidation @ react-jsx-dev-runtime.development.js:1276
(anonymous) @ Navbar.js:179
Navbar @ Navbar.js:137
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:86 Warning: React does not recognize the marginTop prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase margintop instead. If you accidentally passed it from a parent component, remove it from the DOM element.
at header
at http://localhost:3000/static/js/bundle.js:18210:66
at Paper (http://localhost:3000/static/js/bundle.js:40327:83)
at http://localhost:3000/static/js/bundle.js:18210:66
at AppBar (http://localhost:3000/static/js/bundle.js:24277:83)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Navbar (http://localhost:3000/static/js/bundle.js:9719:86)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
validateProperty$1 @ react-dom.development.js:3757
warnUnknownProperties @ react-dom.development.js:3803
validateProperties$2 @ react-dom.development.js:3827
validatePropertiesInDevelopment @ react-dom.development.js:9541
setInitialProperties @ react-dom.development.js:9830
finalizeInitialChildren @ react-dom.development.js:10950
completeWork @ react-dom.development.js:22193
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-jsx-dev-runtime.development.js:87 Warning: Each child in a list should have a unique "key" prop.
Check the render method of CardLinksSection. See https://reactjs.org/link/warning-keys for more information.
at AnimatedBox (http://localhost:3000/static/js/bundle.js:8307:5)
at CardLinksSection
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Container (http://localhost:3000/static/js/bundle.js:52007:19)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at Home
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-jsx-dev-runtime.development.js:87
error @ react-jsx-dev-runtime.development.js:61
validateExplicitKey @ react-jsx-dev-runtime.development.js:1078
validateChildKeys @ react-jsx-dev-runtime.development.js:1105
jsxWithValidation @ react-jsx-dev-runtime.development.js:1276
CardLinksSection @ CardLinksSection.js:63
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:86 Warning:  is using incorrect casing. Use PascalCase for React components, or lowercase for HTML elements.
at Grid
at http://localhost:3000/static/js/bundle.js:18210:66
at CardLinksSection
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Container (http://localhost:3000/static/js/bundle.js:52007:19)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at Home
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
createElement @ react-dom.development.js:9761
createInstance @ react-dom.development.js:10941
completeWork @ react-dom.development.js:22187
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:86 Warning: The tag  is unrecognized in this browser. If you meant to render a React component, start its name with an uppercase letter.
at Grid
at http://localhost:3000/static/js/bundle.js:18210:66
at CardLinksSection
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Container (http://localhost:3000/static/js/bundle.js:52007:19)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at Home
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
createElement @ react-dom.development.js:9816
createInstance @ react-dom.development.js:10941
completeWork @ react-dom.development.js:22187
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:86 Warning: Received true for a non-boolean attribute container.
If you want to write it to the DOM, pass a string instead: container="true" or container={value.toString()}.
at Grid
at http://localhost:3000/static/js/bundle.js:18210:66
at CardLinksSection
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Container (http://localhost:3000/static/js/bundle.js:52007:19)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at Home
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
validateProperty$1 @ react-dom.development.js:3765
warnUnknownProperties @ react-dom.development.js:3803
validateProperties$2 @ react-dom.development.js:3827
validatePropertiesInDevelopment @ react-dom.development.js:9541
setInitialProperties @ react-dom.development.js:9830
finalizeInitialChildren @ react-dom.development.js:10950
completeWork @ react-dom.development.js:22193
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-jsx-dev-runtime.development.js:87 Warning: Each child in a list should have a unique "key" prop.
Check the render method of CardBenefitsSection. See https://reactjs.org/link/warning-keys for more information.
at Typography (http://localhost:3000/static/js/bundle.js:48851:87)
at CardBenefitsSection (http://localhost:3000/static/js/bundle.js:10597:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Container (http://localhost:3000/static/js/bundle.js:52007:19)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at Home
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-jsx-dev-runtime.development.js:87
error @ react-jsx-dev-runtime.development.js:61
validateExplicitKey @ react-jsx-dev-runtime.development.js:1078
validateChildKeys @ react-jsx-dev-runtime.development.js:1105
jsxWithValidation @ react-jsx-dev-runtime.development.js:1266
(anonymous) @ CardBenefitsSection.js:57
CardBenefitsSection @ CardBenefitsSection.js:25
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-jsx-dev-runtime.development.js:87 Warning: Failed prop type: The prop direction of Grid can only be used together with the container prop.
at Grid (http://localhost:3000/static/js/bundle.js:33842:87)
at Footer (http://localhost:3000/static/js/bundle.js:9018:82)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-jsx-dev-runtime.development.js:87
error @ react-jsx-dev-runtime.development.js:61
checkPropTypes @ react-jsx-dev-runtime.development.js:631
validatePropTypes @ react-jsx-dev-runtime.development.js:1164
jsxWithValidation @ react-jsx-dev-runtime.development.js:1284
Footer @ Footer.js:70
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-jsx-dev-runtime.development.js:87 Warning: Failed prop type: Invalid prop light of type string supplied to ForwardRef(Divider), expected boolean.
at Divider (http://localhost:3000/static/js/bundle.js:30866:82)
at Footer (http://localhost:3000/static/js/bundle.js:9018:82)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-jsx-dev-runtime.development.js:87
error @ react-jsx-dev-runtime.development.js:61
checkPropTypes @ react-jsx-dev-runtime.development.js:631
validatePropTypes @ react-jsx-dev-runtime.development.js:1164
jsxWithValidation @ react-jsx-dev-runtime.development.js:1284
Footer @ Footer.js:291
renderWithHooks @ react-dom.development.js:16305
mountIndeterminateComponent @ react-dom.development.js:20074
beginWork @ react-dom.development.js:21587
beginWork$1 @ react-dom.development.js:27426
performUnitOfWork @ react-dom.development.js:26557
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performConcurrentWorkOnRoot @ react-dom.development.js:25738
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:86 Warning: React does not recognize the focusVisible prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase focusvisible instead. If you accidentally passed it from a parent component, remove it from the DOM element.
at a
at LinkWithRef (http://localhost:3000/static/js/bundle.js:196420:7)
at http://localhost:3000/static/js/bundle.js:18210:66
at ButtonBase (http://localhost:3000/static/js/bundle.js:26602:82)
at http://localhost:3000/static/js/bundle.js:18210:66
at ListItemButton (http://localhost:3000/static/js/bundle.js:36588:83)
at li
at http://localhost:3000/static/js/bundle.js:18210:66
at ListItem (http://localhost:3000/static/js/bundle.js:37433:83)
at ul
at http://localhost:3000/static/js/bundle.js:18210:66
at List (http://localhost:3000/static/js/bundle.js:38010:82)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Paper (http://localhost:3000/static/js/bundle.js:40327:83)
at http://localhost:3000/static/js/bundle.js:18210:66
at Transition (http://localhost:3000/static/js/bundle.js:198406:30)
at Slide (http://localhost:3000/static/js/bundle.js:43117:77)
at FocusTrap (http://localhost:3000/static/js/bundle.js:21044:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Portal (http://localhost:3000/static/js/bundle.js:22390:5)
at ModalUnstyled (http://localhost:3000/static/js/bundle.js:21599:7)
at Modal (http://localhost:3000/static/js/bundle.js:39166:82)
at http://localhost:3000/static/js/bundle.js:18210:66
at Drawer (http://localhost:3000/static/js/bundle.js:31163:83)
at nav
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Navbar (http://localhost:3000/static/js/bundle.js:9719:86)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
validateProperty$1 @ react-dom.development.js:3757
warnUnknownProperties @ react-dom.development.js:3803
validateProperties$2 @ react-dom.development.js:3827
validatePropertiesInDevelopment @ react-dom.development.js:9541
setInitialProperties @ react-dom.development.js:9830
finalizeInitialChildren @ react-dom.development.js:10950
completeWork @ react-dom.development.js:22193
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performSyncWorkOnRoot @ react-dom.development.js:26085
flushSyncCallbacks @ react-dom.development.js:12042
commitRootImpl @ react-dom.development.js:26959
commitRoot @ react-dom.development.js:26682
finishConcurrentRender @ react-dom.development.js:25981
performConcurrentWorkOnRoot @ react-dom.development.js:25809
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
react-dom.development.js:86 Warning: React does not recognize the disablePadding prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase disablepadding instead. If you accidentally passed it from a parent component, remove it from the DOM element.
at button
at http://localhost:3000/static/js/bundle.js:18210:66
at ButtonBase (http://localhost:3000/static/js/bundle.js:26602:82)
at http://localhost:3000/static/js/bundle.js:18210:66
at Button (http://localhost:3000/static/js/bundle.js:27815:59)
at span
at http://localhost:3000/static/js/bundle.js:18210:66
at Typography (http://localhost:3000/static/js/bundle.js:48851:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at ListItemText (http://localhost:3000/static/js/bundle.js:37122:82)
at a
at LinkWithRef (http://localhost:3000/static/js/bundle.js:196420:7)
at http://localhost:3000/static/js/bundle.js:18210:66
at ButtonBase (http://localhost:3000/static/js/bundle.js:26602:82)
at http://localhost:3000/static/js/bundle.js:18210:66
at ListItemButton (http://localhost:3000/static/js/bundle.js:36588:83)
at ul
at http://localhost:3000/static/js/bundle.js:18210:66
at List (http://localhost:3000/static/js/bundle.js:38010:82)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Paper (http://localhost:3000/static/js/bundle.js:40327:83)
at http://localhost:3000/static/js/bundle.js:18210:66
at Transition (http://localhost:3000/static/js/bundle.js:198406:30)
at Slide (http://localhost:3000/static/js/bundle.js:43117:77)
at FocusTrap (http://localhost:3000/static/js/bundle.js:21044:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Portal (http://localhost:3000/static/js/bundle.js:22390:5)
at ModalUnstyled (http://localhost:3000/static/js/bundle.js:21599:7)
at Modal (http://localhost:3000/static/js/bundle.js:39166:82)
at http://localhost:3000/static/js/bundle.js:18210:66
at Drawer (http://localhost:3000/static/js/bundle.js:31163:83)
at nav
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Navbar (http://localhost:3000/static/js/bundle.js:9719:86)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Stack (http://localhost:3000/static/js/bundle.js:43497:87)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at InnerThemeProvider (http://localhost:3000/static/js/bundle.js:52082:70)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:51497:5)
at ThemeProvider (http://localhost:3000/static/js/bundle.js:52101:5)
at PublicContainer
at RenderedRoute (http://localhost:3000/static/js/bundle.js:197620:5)
at Routes (http://localhost:3000/static/js/bundle.js:198043:5)
at Router (http://localhost:3000/static/js/bundle.js:197981:15)
at BrowserRouter (http://localhost:3000/static/js/bundle.js:196328:5)
at div
at http://localhost:3000/static/js/bundle.js:18210:66
at Box (http://localhost:3000/static/js/bundle.js:52804:72)
at App
at Provider (http://localhost:3000/static/js/bundle.js:193898:5)
printWarning @ react-dom.development.js:86
error @ react-dom.development.js:60
validateProperty$1 @ react-dom.development.js:3757
warnUnknownProperties @ react-dom.development.js:3803
validateProperties$2 @ react-dom.development.js:3827
validatePropertiesInDevelopment @ react-dom.development.js:9541
setInitialProperties @ react-dom.development.js:9830
finalizeInitialChildren @ react-dom.development.js:10950
completeWork @ react-dom.development.js:22193
completeUnitOfWork @ react-dom.development.js:26596
performUnitOfWork @ react-dom.development.js:26568
workLoopSync @ react-dom.development.js:26466
renderRootSync @ react-dom.development.js:26434
performSyncWorkOnRoot @ react-dom.development.js:26085
flushSyncCallbacks @ react-dom.development.js:12042
commitRootImpl @ react-dom.development.js:26959
commitRoot @ react-dom.development.js:26682
finishConcurrentRender @ react-dom.development.js:25981
performConcurrentWorkOnRoot @ react-dom.development.js:25809
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533

It's not displaying these error messages in my console. Maybe I'll see them after the merge. Let me merge first