.gitignore: .aider* -> .aider.* to preserve .aiderignore by default.

When asking questions or reporting issues, it is very helpful if you can include:
Starting aider with model gpt-4

Loading aider:
  remember to use /help for a list of commands

Aider v0.23.0
VSCode terminal detected, pretty output has been disabled.
Add .aider* to .gitignore (recommended)? n
Model: gpt-4 using diff edit format
Git repo: .git with 16,518 files
Warning: For large repos, consider using an .aiderignore file to ignore irrelevant files/dirs.
Repo-map: using 1024 tokens
Added Dockerfile to the chat.

I'm not sure I understand what you're trying to ask/suggest/report?

I'd like to keep .aiderignore because it prevents a large repo from causing aider to freeze. This needs to be checked in so that others can use aider as well. However your rule prevents this because .aider* will ignore .aiderignore. To solve this I added .aider.* so that just the other files are ignored.

You just need to manually manage/edit the .gitignore file for your project. You don't need to change aider.

I did edit the .gitignore manually. The bug is that aider keeps bugging me to add the pattern exactly as it's hardcoded in the project. So simplest solution seems to be to change the hardcoded pattern.

Once you've added .aiderignore to .gitignore it doesn't matter if .aider.* is in .gitignore after that. The .aiderignore file is already part of git.
tmp$ mkdir ignore
tmp$ cd ignore
tmp/ignore$ echo one > .aiderignore
tmp/ignore$ git init
Initialized empty Git repository in /Users/gauthier/tmp/ignore/.git/
tmp/ignore$ git add .aiderignore
tmp/ignore$ gc -m initial
[main (root-commit) 951a16e] initial
 1 file changed, 1 insertion(+)
 create mode 100644 .aiderignore
tmp/ignore$ echo .aiderignore > .gitignore
tmp/ignore$ echo two >> .aiderignore
tmp/ignore$ git status
On branch main
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   .aiderignore

no changes added to commit (use "git add" and/or "git commit -a")
tmp/ignore$ gc -a -m .aiderignore
[main 486233c] .aiderignore
1 file changed, 1 insertion(+)

Okay, but why-by-default try to exclude the .aiderignore file? All the rest make sense. You don't want to add in the chat logs.
Let me give you an example:
In my current project, we migrated an EC2 instance to docker and we over-included files to make it work. Aider just halts.
I struggled a little to add the aiderignore because the tool just wanted to revert it. However by default, my front end is passing no auto commit, so I might have a different default experience than you.
But anyway, just wanted to help a small friction point I experienced. Its up to you to accept the PR or not, since it's your project. Great job. My bill to openai went up a ton too but it's def worth it!!

Okay this is a good work around, I can just control .gitignore myself I guess. Thanks for showing me the '!'

Thanks, this works perfectly.


Readthedocs builds are broken

The readthedocs build for astroplan has been broken for ~ a month:
https://readthedocs.org/projects/astroplan/builds/
https://readthedocs.org/projects/astroplan/builds/4264804/
Looks like it's just the PDF build and the HTML build is OK?
I don't have time to investigate.
@bsipocz or @bmorris3 - maybe you do?

I don't understand what the failure is. I hate to put another thing on @bsipocz's long list – but maybe she's our best hope.

Honestly I have no idea what's the problem. However photutils seems to have the same or very similar issue for the pdf builds. https://github.com/astropy/photutils/issues/393

I just wanted to add that this issue is unrelated to https://github.com/astropy/photutils/issues/393.  They are independent bugs in the docs.


Update readme for linked list 3 solutions in cpp

Here the solutions of  1. Reverse Linked Lists   2.Delete Duplicate Values  3.Find Merge point.   in CPP.   I have also updated the README.md .

Your README is not updated with the latest one.

I was assigned the Reverse Linked List question too. But the cpp solution link is already there , added by somebody else. Please advice what to do

Add whatever is not there.

@adityabisoi  Do I have to make a separate PR for the cpp solutions of the Linked List Easy - 3 problems? Only my README.md file is merged. Please clarify.

Please add the latest README. Also, mention your issue number here so that I can see the one which has been assigned to you.

@adityabisoi . I have updated README.md and added the ISSUE no. (#36) .Please confirm this.

Reverse a linked list and print in reverse are two different problems.

I have added the code of Reverse Linked list . I have not done Print in Reverse. They are the same code.
Do I have to make a new PR with the updated Readme and the 3 solutions .?

But, your folder suggests something else Linked Lists/Print in Reverse/solution.cpp

By mistake ,  I had initially given the name Print in Reverse ,  then I changed it to Reverse Linked List. The file contains solution of 3 problems only , Reverse Linked List , Delete duplicate values and Find Merge Point.
Shall I delete the Print in Reverse File from this PR , then will the  other 3 solutions be present  already?
Since I am new here , please guide what to do.

Closing this PR. Firstly, pull latest changes from this repo. Then, add your files to the respective problem folder, and simply add links in README if already not present. Then, make a new PR. Got it?

Yes , I am adding the files to the respective program code and making a new PR .
README file already has the links , do I need to update it again? Or simply I'll make add the 3 program solutions in their own folders and make a new PR?

Only add solutions then


Broken avatar

Hello.
My avatar is broken (empty URL), but I have avatar on GitHub and I have Gravatar.
I had no avatar on GitHub or Gravatar at time of sign up, but since then I've added them.

:-(

...to gravatar?
On Fri, 11 Sep 2015 04:21 Vanav<EMAIL_ADDRESS>wrote:

:-(
—
Reply to this email directly or view it on GitHub
https://github.com/jsbin/jsbin/issues/2479#issuecomment-139441880.

I've set email in settings, and now avatar is shown from Gravatar.


npm WARN deprecated request

Describe the bug
A warning shows up while bootstrapping the OpenSlide docker images.
How to Reproduce
Steps to reproduce the behavior:

Go to 'OpenSlides/docker'
'./build.sh all'
See error:

Step 7/19 : RUN npm install -g @angular/cli@^10
 ---> Running in fb6dae780f73
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported

Expected behavior
System information

OpenSlides-Version: 3.2

That's Angulars internals. Matters very little.

Ok, I see. Thanks.


New wrap for pcre2

I built a wrap for pcre2. I used a new repository (not based on https://github.com/mesonbuild/pcre/tree/8.37) because pcre2 has a revised API and it is considered a different package in most linux distributions.
From http://mesonbuild.com/Wrap-review-guidelines.html I see I need to submit a merge request, but I don't know where should I submit it, as it is a new repository: https://github.com/zeehio/pcre2
Thanks for your time

[x] project() has version string
[x] project() has license string
[x] if new project, master has tagged commit as only commit
[x] if new branch, it is branched from master
[x] contains a readme.txt
[x] contains an upstream.wrap file
[x] download link points to authoritative upstream location
[x] wrap repository contains only build system files
[ ] merge request is pointed to correct target branch (not master)
[x] wrap works
[x] repo does not have useless top level directory (i.e. libfoobar-1.0.0)

I created a PCRE2 repository. Please create a MR against that one with your changes. Thanks.


About page fails with a 500 error

Current Behavior
When you click on the about page on a server that isn't running the gateway service, you get three 500 error popups, and then the page gets redirected to "Something went wrong".
Expected Behavior
For the about page to load properly
Browser
Chrome
Steps To Reproduce
No response
Additional Details
Taking a quick look, matybe it's linked to the gateaway health check?
Priority
High

I cannot reproduce this locally. Is this still occurring in the latest version (1.6)?

Yes is does with version 1.6

Can you please send me the error report. This should be available for v1.6.1


[Enhancement]: Add support for editing Slurm's cgroup configuration

The current slurmctld_ops module in the slurmctld charm supports editing the cluster cgroup configuration, however, we don't support it here yet. This functionality should be added so that we can drop slurm_ops in-place of slurmctld_ops

Necessary PR merged on slurmutils to support editing the cgroup.conf file: https://github.com/charmed-hpc/slurmutils/pull/19


doc: update CODEOWNERS

Add the "other" owner

https://github.com/opea-project/GenAIComps/pull/586

https://github.com/opea-project/GenAIExamples/pull/711

closing for #711


Fix the issue of admin command lack of some show and list subcommands

Coverage decreased (-0.4%) to 67.251% when pulling 11c0dfbd8d92dacd85b7e77b2c8059d21888404f on cli-fix into 516439e0f4f3c9bf9ed03ea3a6998b20f2c63014 on master.


Add type annotations to date utils file

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #5912   👈

This comment was auto-generated by Graphite.

/retest-required

If you want to fix integration test failure, rebase on #5905


Setting bucket_id permission causes 500

I'm setting the following permissions:
{
  "bucket_id": {
    "_eq" : "documents"
  }
}

And uploading a file like this:
    const { fileMetadata, error } = await nhost.storage.upload({
      file,
      bucketId: "documents",
    });

The request is sent with the documents header like this:
x-nhost-bucket-id: documents

I've also created a bucket called documents with the same data as the default default.
Server logs:
time="2022-06-24T12:00:59Z" level=error msg="call completed with some errors" client_ip=<IP_ADDRESS> errors="[problem processing request: problem initializing file metadata: Message: check constraint of an insert/update permission has failed, Locations: []]" latency_time=18.060584ms method=POST status_code=500 url=/v1/files

It seems to me that in hasura console you need to go to data -> <databases> -> storage -> buckets -> permissions and add the user role with insert/update permissions

I can't reproduce with the latest version. All is good. I've also updated the docs with information about permissions here: https://docs.nhost.io/platform/storage#permissions


forTemplate() issue in Forms.php caused by template storage location error

The forTemplate() function Forms.php provides a fallback form if the correct one cant be found. This has issues with Userforms 4.x and any template that follows that structure because UserForm.ss is in Layouts (where it should be) and Form.ss is in forms. The result is a situation where both are found as valid by the templating system, Forms.ss first and then UserForms.ss as a layout. This is highly ambiguous and unpredictable. See my issue https://github.com/silverstripe/silverstripe-userforms/issues/483 for more details
The upshot is that I believe the framework Forms.ss should be moved to a new Layout directory. I have done this and of course it is correctly found as might be expected. I have matched this move by moving all other instances of Form.ss in my templates to Layout. All is well. This was in framework 3.4 but should be Ok in all releases that suit UserForms 4.x

Will be addressed with https://github.com/silverstripe/silverstripe-framework/issues/5604


Dev

good to go

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

1 out of 2 committers have signed the CLA.

[x] 2Wdavidcunliffe
[ ] root

root seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.
Have you signed the CLA already but the status is still pending? Recheck it.


Organization of a February 2024 OGC API - Coverages Virtual Code Sprint

The SWG discussed today that there would be interest in hosting a 3 days virtual code sprint for OGC API - Coverages in February 2024, tentatively the week of the 12th.
The effort would continue the good implementation momentum from Testbed 19 GDC API Technology Integration Experiments, and provide validation for the latest OGC API - Coverages candidate standard, which we hope will be in the Request for Comments period at that time.

cc. @ghobona @tomkralidis @pebau @pomakis

The OGC API - Coverages Virtual Code Sprint would have to be before 26 February to avoid clashing with the next Joint OGC ASF OSGeo Code Sprint.

@ghobona Yes this is why we picked the week of the 12th.

@jerstlouis I have just connected you with OGC's Event Manager via email so that the dates can be checked for calendar conflicts.

@jerstlouis Here is a example announcement from the OGC API - Processes Virtual Code Sprint https://www.ogc.org/press-release/developers-invited-to-the-2023-ogc-api-processes-virtual-code-sprint/

Thanks a lot @ghobona we'll start with that.
Hoping to make progress on some of the other SWG Event Organizer items as well today.

The Press Release has been announced. https://www.ogc.org/press-release/developers-invited-to-the-february-2024-ogc-api-coverages-virtual-code-sprint/

LinkedIn post https://www.linkedin.com/feed/update/urn:li:activity:7158122139424874496?utm_source=share&utm_medium=member_desktop

Another LinkedIn post https://www.linkedin.com/posts/open-geospatial-consortium_ogcapi-webapi-standard-activity-7158144876532944896-uIyB?utm_source=share&utm_medium=member_desktop

@jerstlouis I tried to add myself to the wiki page here, but I don't have write permissions on this repo. Not sure if anyone else who is not a committer here, tried to register.


feat: AT_EMPTY_PATH for fchownat on Linux/Android

What does this PR do
Picks up #1128
Closes #1128 Closes #1029
Enable the AT_EMPTY_PATH flag for fchownat() on Linux/Android
Checklist:

[x] I have read CONTRIBUTING.md
[x] I have written necessary tests and rustdoc comments
[x] A change log has been added if this PR modifies nix's API

This is a rare case of an API change in Nix where we can help users migrate. What about defining some deprecated constants like this?
impl FchownatFlags {
     #[deprecated]
    pub const FollowSymlink = FchownatFlags::empty();
    #[deprecated]
    pub const NoFollowSymlink = FchownatFlags::AT_SYMLINK_NOFOLLOW;
}

Done

Well, fixing imports is so painful, I really hope Nix never do
use xxx

but directly use the items when needed.


🐛 Fix #125 - Focus not trapped in form

This fixes #125.
TODO: Tests.

See this comment for a note on tests

Looks good!


[FLINK-26232][tests][JUnit5 migration] Module:flink-avro

What is the purpose of the change
Update the flink-formats/flink-avro module to AssertJ and JUnit 5 following the JUnit 5 Migration Guide
The migration of this module isn't fully finished -- notably those that depend on test base classes outside this module, which I either left untouched or just did the AssertJ changes if they could be done independently.
Brief change log

Removed dependences on JUnit 4, JUnit 5 Assertions and Hamcrest where possible.

Verifying this change
This change is a code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? no

Thanks for the review, let me know if you have any advice for the next step: would it be better to start migrating the base classes so in order to "finish" flink-avro, or to attack the "low-hanging" fruit in other modules?

@RyanSkraba I'd focus on low-hanging fruits for now (i.e., where we can migrate an entire module at once); the core module such as flink-runtime will likely have to migrated piece-by-piece.

@flinkbot run azure
In my local environment, failed to compile AvroTypeExractionTest.


Add Auto GPS for User Location

Map now pans to user location if available
Search now uses user location as origin unless PAC input is provided, alert window will only pop if both options are unavailable.
Added infowindow for user's current location

demo: https://jtan-sps-summer20.appspot.com/

Since the other PR has been closed, do merge and deploy when you can 👍

Demo is now up!


How to get the supplementary materials

I can't find the supplementary materials of this CVPR2019 paper in project website.
When to release it?
Thanks!

We are right now working on the supplementary video for some modifications. The plan is to release it within few days. I will update it in the project page and here as soon as it is done.

You find the supplementary video here: https://youtu.be/6wPQaJBgreE


Problems with optionals and array in triggers

Hello,
Here is the examples :
[*] (yes|No) [*]
% are you young
* <star>== yes => good
* <star>== No => bad

*
% are you young
- ok, i leave

If i reply "yes" or "yes i am" it replies ok i leave
It should say good !!
Any solution ?
Second problem :
! array nombre = un deux trois...
! sub un = 1
! sub deux = 2
.....

+ [*] # [*]
% how many arms do i have
* <star>==2=> good
- bad answer

+ *
% how many arms do i have
- ok i leave

I say : you have four arms my friend
It replies : ok i leave (should be : bad answer)
Sometimes it work, and sometimes no !!!
Is there any problem ?
Thanks Noah

Both of these test cases were due to a bug in how %previous triggers were being sorted. (I think the bug also affects the JavaScript version and possibly the Go one as well, and now that I know the fix I can apply it to those versions soon too).
Upgrade your version of rivescript-python to v1.14.3 for the fixed version:
      .   .
     .:...::      RiveScript Interpreter (Python)
    .::   ::.     Library Version: v1.14.3
 ..:;;. ' .;;:..
    .  '''  .     Type '/quit' to quit.
     :;,:,;:      Type '/help' for more options.
     :     :

Using the RiveScript bot found in: tmp
Type a message to the bot and press Return to send it.

You> LOL
Bot> ok, I leave
You> Ask me 2
Bot> How many arms do I have?
You> 1
Bot> bad answer
You> Ask me 2
Bot> How many arms do I have?
You> Un
Bot> bad answer
You> Ask me 2
Bot> How many arms do I have?
You> 2
Bot> good
You> Ask me 2
Bot> How many arms do I have?
You> Deux
Bot> good
You> Ask me 2
Bot> How many arms do I have?
You> lol
Bot> ok i leave

good, thanks Noah


how to debug the code

i build autoclip successfully  with command below
bazel build -c opt --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/autoflip:run_autoflip
and i could run the demo
but , how could i debug it ?
VSCode or any other IDE avaliable ?

"bazel-bin/mediapipe/examples/desktop/autoflip/run_autoflip" is a binary. So, you can do debugging with gdb, valgrind, and so on.
Moreover, for debugging, you'd better to rebuild "run_autoflip" with the debug mode by replacing -c opt with -c debug. So the build command should be the following:
bazel build -c debug --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/autoflip:run_autoflip

"bazel-bin/mediapipe/examples/desktop/autoflip/run_autoflip" is a binary. So, you can do debugging with gdb, valgrind, and so on.
Moreover, for debugging, you'd better to rebuild "run_autoflip" with the debug mode by replacing -c opt with -c debug. So the build command should be the following:
bazel build -c debug --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/autoflip:run_autoflip

is there a ide for debug ?  command looks like inefficient

You can generate Xcode project from Mediapipe.tulsi, and import all source files into the project(By default the project only contains subset of source files). Then you can debug it as normal ios project, breakpoints, step by step execute, etc.

You can generate Xcode project from Mediapipe.tulsi, and import all source files into the project(By default the project only contains subset of source files). Then you can debug it as normal ios project, breakpoints, step by step execute, etc.

@aaaron7  hxg?

You probably can use gdb to debug the code. I am sorry that there is no ide debugging support yet.


progress or sliderMove events are not fully triggered

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/p/sandbox/mg9ssk?file=%2Findex.html
Bug description
Since I need to know the progress of the slide, I first tried to use events such as progress and sliderMove. But I noticed that events only fire at the moment while the user’s mouse button is pressed on the slide, when the button is released and the slide is still in motion, the event no longer fires and the progress value, for example 0.8, suddenly changes to 1, making it impossible to use the value for smooth rendering of the style. For example. I also tried other Events but no results. If this is not a bug or flaw, then tell me , please, how to solve this problem.

Expected Behavior
changing value throughout the slide animation
Actual Behavior
the value change stops after the user releases the button, but the slide animation continues
Swiper version
11.0.5
Platform/Target and Browser Versions
Windows 10
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

This is how css transitions work. Try using cssMode


Enable full input from Cube files, including densities

I would like to introduce the option to have input from Cube files essentially everywhere where input from XSF is possible. The reason is mainly that Cube is the standard output format for 3D maps (potentials and densities) from FHI-AIMS. While FHI-AIMS has the option to switch the output into XSF too, this has problems of its own. As pointed out by @NikoOinonen during the discussion of PR #179 , Cube cannot be used for densities now, because there is an issue with a scaling factor. Moreover, I know about an issue with how an origin of the coordinate system is chosen, which is treated in our code differently for Cube as compared to XSF. This latter problem, the one with the coordinates, does not make the results literally wrong (probably), but it is a pain to identify positions in the resulting images with the original positions of atoms in the input atomic structure. These issues are quite important to me as I have been mostly using FHI-AIMS for DFT recently and the imperfect support of the Cube format by ppafm really hampers my work.

@mondracek Are you working on this? It would also make my life easier if I could load electron densities from cube files. I could also try to fix this if you are busy.

Which issues specifically is this blocked by?

Hi guys!
I have tried to use FHI-AIMS cube files in the past for density overlaps (If I understood thats what Martin is trying) and I got a lot of noise (like an oscillation if you look at df profiles along the z axis). My best guess was that, because at the center of the atoms in AIMS there is no density (zero) it looks like a bunch on widen dirac deltas that become oscillations under the fourier transform of the integral (If I remember right, it was quite ago). We though on fit this area out since it is not necessary all that much, but never got to actually do it.
Just in case any of this info could come useful


Bump minimum version for SQL Tools and Kusto packages

The 2.0.0 packages upgrade the SQL Tools and Kusto services to net8.0 and also add a rollForward property to help with SDK updates in the future.

@corivera Thank you for the PR!


FR: allow to export multiple job as a json file

@s-r-x it would be nice to be able to export multiple jobs as a JSON file. Thanks!

@weilinzung added in 0.17.0


Type aliasing for model contract column data_type

resolves #8007
Problem
Currently contracts data_types must use the correct type for their warehouse, instead of using the built in type aliasing.
Solution
For model dictionaries provided by the provider context, convert the column data_type using  the "translate_types" method.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

This causes test breakage in the adapter repos (mostly for test_constraints.py), at first glance mainly because of SQL in which statements such as "id integer not null" are replaced by "id int not null" because the TYPE_LABELS in the base Column class change INTEGER to INT (and STRING to TEXT).
@jtcohen6 @graciegoheen Just want to verify that this is something we actually want to have happen.

Note: currently it looks like string => text and integer => int are the only data types changed.

Opened a new issue in dbt-labs/docs.getdbt.com: https://github.com/dbt-labs/docs.getdbt.com/issues/4241


Add a new gateway - Komerci (Rede)

I developed a new gateway driver for Komerci (Rede).
Komerci is the solution for e-commerce from Rede (former Redecard). Rede is a Brazilian acquirer. This is responsible for the authentication, authorization and capture the card data in the Rede environment.
How I get this driver listed here: https://github.com/thephpleague/omnipay ?
The repository of this gateway is:
https://github.com/byjg/omnipay-komerci/
Thank you.

You get the driver listed by submitting a PR for this package.  Update the README.md file with the name and link to your new gateway driver.

Thank you, I created the PR right now.


navio_adc: add driver for Navio2 ADC -

Hello,
This is my first attempt to make a Navio2 ADC driver for #7211 . Documentation is available here for Navio2.
Currently I'm having troubles getting sensors to see the adc driver:
[user@mhome px4]$ ./src/firmware/posix/px4 .
commands file: .
18446744073709551267 WARNING: setRealtimeSched failed (not run as root?)

______  __   __    ___
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

pxh> uorb start
pxh> navio_adc start
INFO  [navio_adc] NavioADC::ctor
INFO  [navio_adc] init done
pxh> sensors start
ERROR [sensors] no ADC found: /dev/adc0 (9)
ERROR [sensors] no barometer found on /dev/baro0 (9)
pxh> list_devices
INFO  [drivers__device] PX4 Devices:
INFO  [drivers__device]    /dev/adc0
INFO  [drivers__device] DF Devices:
pxh> list_files
INFO  [drivers__device] Files:
pxh>

I see sensors use DevMgr to get a handle DevHandle. Have I inherited the wrong class (VDev) ?
Any pointers are appreciated, ping @bkueng
This is WIP, I added the driver to SITL only for dry-testing.

Yes - the POSIX drivers should (counter-intuitively) base off https://github.com/PX4/Firmware/tree/master/src/platforms/posix/drivers and be implemented in DriverFramework: https://github.com/PX4/DriverFramework
We will consolidate that with the NuttX drivers, but that hasn't happened yet.

Thank you, @LorenzMeier .
Should I target DriverFramework instead? That would require creating a wrapper for ... nothing.
I have successfully tested this driver with a 3DR power module (sold by Emlid):
param set BAT_CNT_V_VOLT 0.001
#param set BAT_V_DIV 10.9176300578
param set BAT_V_DIV 10.8645533141
param set BAT_N_CELLS 4
param set BAT_CAPACITY 6200

param set BAT_CNT_V_CURR 0.001
param set BAT_A_PER_V 15.391030303

# no load
pxh> listener battery_status

TOPIC: battery_status #1
timestamp: 21757481
voltage_v:  15.1318
voltage_filtered_v:  15.1386
current_a:   0.0000
current_filtered_a:   0.0000
discharged_mah:   0.0006
remaining:   0.5129
scale:   1.0965
cell_count: 4
connected: True
warning: 0

pxh> navio_adc test
INFO  [navio_adc] chan: 0; value: 5222
INFO  [navio_adc] chan: 1; value: 36
INFO  [navio_adc] chan: 10; value: 1384
INFO  [navio_adc] chan: 255; value: 0
INFO  [navio_adc] chan: 4; value: 20
INFO  [navio_adc] chan: 5; value: 32

# load
pxh> commander arm
pxh> listener battery_status

TOPIC: battery_status #1
timestamp: 207425495
voltage_v:  14.8916
voltage_filtered_v:  14.9058
current_a:   0.1231
current_filtered_a:   0.1813
discharged_mah:   0.5273
remaining:   0.6545
scale:   1.0666
cell_count: 4
connected: True
warning: 0

Ready for review from my POV.

This looks good. Could you also add the required startup script adjustments so that it all works for a standard setup out of the box?

@LorenzMeier thank you, I've amended the commit & force pushed.

What about battery voltage params? They are not in the startup script, are they?

You are right, I added them now.

CI is failing on formatting. Please run make format.

Fixing now

@mhkabir done


Add documentation for classes in shared firmware folder (e.g. Linear Interpolation Class)

Documentation Request
Description:
Currently limited documentation for the linear interpolation class and other code within the firmware/shared folder. Adding documentation for these components might make it easier for new team members to understand them.
Proposal:

Create code documentation for the linear interpolation class.
Document other components within the firmware/shared folder to improve clarity.

#365 adds documentation for all of the Mappers. The other firmware/shared components are mostly peripherals and that structure is documented at https://macformula.github.io/racecar/firmware/architecture/, so I will consider #365 to close this issue.


Arrow button styling at top of picker looks odd and overlaps text

Describe the bug
Arrow buttons overlap Day text.
To Reproduce
Steps to reproduce the behavior:
load the Datepicker component and render it in your app.
Expected behavior
The arrow buttons do not overlap and collide with other text in the picker.
Screenshots

Desktop (please complete the following information):

OS: Mac OSX Catalina
Browser Chrome
Version latest

Other:
Just not sure if this is just the way the component is styled now or if I need to adjust styling somehow - it currently looks odd in my opinion.

On second thought - this is not a big deal for my use case so I'm closing - sorry for opening the issue.


Update WebSocketClient.ts

Keep WebSocket alive.

Fixed with https://github.com/bennycode/coinbase-pro-node/pull/377

Fixed with https://github.com/bennycode/coinbase-pro-node/pull/377


Canonical Links for republished blog posts

We often copy blog posts from other sources, but to do so without messing up the SEO results, we need to add a canonical link to point to the original content source.
There's a Yoast plugin option that would allow for this: https://yoast.com/help/canonical-urls-in-wordpress-seo/

Moved to foundation/issues

Moved to foundation/issues


skips 2 images on autorotate, plus nav buttons work intermittently

Hello, firstly, thanks for the plugin, it is just what I was looking for.
I have a few issues:
I am initializing the plugin with the following settings:
autoRotate:4000,speed:500,visible: 1, overflow:true, imageWideClass:"wide-image",itemEqualHeight:true,infinite:true
1st problem:
When the carousel animates, it moves to the next image, then immediately starts animating to the image after that.  Clicking next or previous moves 2 images at once.
This only happens when infinite is set to true.
2nd problem
The next and prev buttons stop working after a while.  If you click next several times, the prev button stops working.  It seems to be quite random, sometimes you can click through many images before it stops working, others after only 2 or three.
Thanks for any help you may be able to provide!

i think that development of this script is dead but i report anyway. Same problem also for me and the autorotation doesn't stop when all elments are visible


[W-10854481] - Allow ACH payment method option

[Technical Design Review] W-10854481 - NPSP
Changes
Updated "Recurring Donations" LWC to add a new Boolean property called "allowACHPaymentMethod" exposed to the Experience Builder as "Allow ACH payment method" with the default value equals to "true".
Work Closed
W-10854481

@gerardorodriguezsf We normally don't merge PRs without additional logic, is there another Work Item that uses this new property?

@gerardorodriguezsf We normally don't merge PRs without additional logic, is there another Work Item that uses this new property?

@lparrott Yes Luke, this is defined here W-11125193
Please let me know if you have questions.

@gerardorodriguezsf We normally don't merge PRs without additional logic, is there another Work Item that uses this new property?

@lparrott Yes Luke, this is defined here W-11125193 Please let me know if you have questions.

Great, let's get that work done before we review then, you can just use the same branch.


Toolbars: add some specs for rendering.

Some rendering specs for https://github.com/ManageIQ/manageiq/pull/4853
@skateman : ping, feel free to add more ;-)
@jzigmund : if you are working on specs, please, rebase on top of this

@martinpovolny please fix the rubocop issues :)

Spec looks good, ok to merge.


preview for collapsed cells in diff view

Testing #226663
Could we show the first line of the cell as we do for collapsed cells in the notebook editor? With a large amount of collapsed cells, it is pretty hard to know where I am in the notebook. Doing this for markdown cells could be especially effective.

As we haven't had enough upvotes on this feature request I'm closing this as not planned.


Any plans to implement undo?

Hey @mallanza!
I have no plans for it yet. However, I like the idea and will try to implement it at some point.


fix: regenerate graphql bindings and fix pipeline to verify them

Fixes https://github.com/nhost/nhost/issues/2374 and it ensures that won't happen again.

Any eta on this one? I know it has only been like 3 days but I am deploying my run services quite often and every time I have to think about the custom domain ;)


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/autoscaling-wg-leads
/assign knative-sandbox/autoscaling-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps

min k8s version is v1.24, so the e2e tests for v1.23 aren't necessary anymore

e2e tests are passing for v1.24+, overriding to skip the failures on the unsupported v1.23
/override "KinD e2e tests"
/override "kubeadm e2e tests"

/override "e2e tests (1.23.6)"
/override "e2e tests (v1.23.6)"


add link to FM-12 in synop2bufr practical session

For users to consult/review accordingly.

Included in https://github.com/wmo-im/wis2box-training/pull/102.


Implement metering and duration in ios and android

I removed the file:// part. I'm not sure if this needs to be added back somewhere. Maybe it does before it's returning in the promise?

Looks good! I'll merge it!


Fixes so the endpoint will work

Mostly cleaning up items that made it not compile and adding the season id to new games.

Looks good to me.


Add function to convert c8::natural to unsigned long long

Add function to convert c8::natural to unsigned long long, where the natural number will fit. Throw an overflow exception if it does not

Resolved.


The "Preview" installed on my computer without my approval

Suggested new feature or improvement
The short version is don't install random crap if I didn't solicit for it in the first place!

Scenario
I ran updates on Win10 on my work PC and this app appeared/installed all on it's own.
Additional details
If I didn't want it, don't install it, this isn't rocket science...
I had to use the winget uninstall to remove it because I didn't need it for my daily business workflow and speak with authority that this app will NOT be randomly be dumped onto people's computers

Duplicate of #1615


other: Don't expose the superset_db and superset_cache to the host machine

SUMMARY
Don't expose the superset_db and superset_cache to host machine as it is not necessary.
TEST PLAN
Run docker-compose up and still functions as expected.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12810 (43e425d) into master (32f2c45) will decrease coverage by 16.08%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #12810       +/-   ##
===========================================
- Coverage   67.01%   50.92%   -16.09%
===========================================
  Files        1022      477      -545
  Lines       50102    17157    -32945
  Branches     5191     4438      -753
===========================================
- Hits        33574     8737    -24837
+ Misses      16397     8420     -7977
+ Partials      131        0      -131

Flag
Coverage Δ

cypress
50.92% <ø> (ø)

javascript
?

python
?

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

Impacted Files
Coverage Δ

...uperset-frontend/src/dashboard/util/dnd-reorder.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...rset-frontend/src/dashboard/util/getEmptyLayout.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/resizable/ResizableHandle.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/nativeFilters/ScopingTree.tsx
6.25% <0.00%> (-93.75%)
:arrow_down:

.../src/dashboard/util/getFilterScopeFromNodesTree.js
0.00% <0.00%> (-93.48%)
:arrow_down:

...set-frontend/src/views/CRUD/alert/ExecutionLog.tsx
11.76% <0.00%> (-88.24%)
:arrow_down:

...src/dashboard/components/gridComponents/Header.jsx
10.52% <0.00%> (-86.85%)
:arrow_down:

superset-frontend/src/components/IconTooltip.tsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...rc/dashboard/components/gridComponents/Divider.jsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...perset-frontend/src/views/CRUD/welcome/Welcome.tsx
2.94% <0.00%> (-85.95%)
:arrow_down:

... and 877 more

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 32f2c45...43e425d. Read the comment docs.

Codecov Report

Merging #12810 (43e425d) into master (32f2c45) will decrease coverage by 16.08%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #12810       +/-   ##
===========================================
- Coverage   67.01%   50.92%   -16.09%
===========================================
  Files        1022      477      -545
  Lines       50102    17157    -32945
  Branches     5191     4438      -753
===========================================
- Hits        33574     8737    -24837
+ Misses      16397     8420     -7977
+ Partials      131        0      -131

Flag
Coverage Δ

cypress
50.92% <ø> (ø)

javascript
?

python
?

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

Impacted Files
Coverage Δ

...uperset-frontend/src/dashboard/util/dnd-reorder.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...rset-frontend/src/dashboard/util/getEmptyLayout.js
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/resizable/ResizableHandle.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

...dashboard/components/nativeFilters/ScopingTree.tsx
6.25% <0.00%> (-93.75%)
:arrow_down:

.../src/dashboard/util/getFilterScopeFromNodesTree.js
0.00% <0.00%> (-93.48%)
:arrow_down:

...set-frontend/src/views/CRUD/alert/ExecutionLog.tsx
11.76% <0.00%> (-88.24%)
:arrow_down:

...src/dashboard/components/gridComponents/Header.jsx
10.52% <0.00%> (-86.85%)
:arrow_down:

superset-frontend/src/components/IconTooltip.tsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...rc/dashboard/components/gridComponents/Divider.jsx
13.33% <0.00%> (-86.67%)
:arrow_down:

...perset-frontend/src/views/CRUD/welcome/Welcome.tsx
2.94% <0.00%> (-85.95%)
:arrow_down:

... and 877 more

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 32f2c45...43e425d. Read the comment docs.

Thank you for the contribution, but I don't agree with not exposing redis and PG (mainly PG) since this is very handy for running tests and debugging locally

I understand from a developers perspective, to clarify a bit more from my perspective as a user:
When installing Superset I had a personal PSQL container running on my machine that I wanted to visualize using superset. It is exposed to my host machine on port 5432. Then using the quick installation guide with docker-compose up did not work because it also tries to bind to the 5432 port.

Thank you for the contribution, but I don't agree with not exposing redis and PG (mainly PG) since this is very handy for running tests and debugging locally

I understand from a developers perspective, to clarify a bit more from my perspective as a user:
When installing Superset I had a personal PSQL container running on my machine that I wanted to visualize using superset. It is exposed to my host machine on port 5432. Then using the quick installation guide with docker-compose up did not work because it also tries to bind to the 5432 port.

I'll also have to agree that the default exposed ports from Docker containers should probably not interfere with the default host ports. Many developers works on multiple projects, not just Superset. Maybe we can export them to some non-standard ports instead?

I'll also have to agree that the default exposed ports from Docker containers should probably not interfere with the default host ports. Many developers works on multiple projects, not just Superset. Maybe we can export them to some non-standard ports instead?

+1 to moving the ports to non-standard ports.

+1 to moving the ports to non-standard ports.

These values are configurable via https://github.com/apache/superset/blob/61e56b5027da6d6417b8d275a93a2cf7b4a03d1b/docker/.env
Maybe we can update docs with a section for changing the redis and db port if necessary

These values are configurable via https://github.com/apache/superset/blob/61e56b5027da6d6417b8d275a93a2cf7b4a03d1b/docker/.env
Maybe we can update docs with a section for changing the redis and db port if necessary

I definitely would like to keep postgres exposed in my local machine, but I +1 the suggestion to move to a different port!

I definitely would like to keep postgres exposed in my local machine, but I +1 the suggestion to move to a different port!

Any suggestion for the non-standard ports?
I still feel like the docker-compose logic should support a users' use-case in the first place and developers' use-case secondary, as it's the default way to install Superset.

@HeNKiEeEeE   I would recommend exposing to 16379 and 15432 to keep things simple:
diff --git a/docker-compose.yml b/docker-compose.yml
index 733ad3ea5..72bc5f988 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -33,7 +33,7 @@ services:
     container_name: superset_cache
     restart: unless-stopped
     ports:
-      - "<IP_ADDRESS>:6379:6379"
+      - "<IP_ADDRESS>:16379:6379"
     volumes:
       - redis:/data

@@ -43,7 +43,7 @@ services:
     container_name: superset_db
     restart: unless-stopped
     ports:
-      - "<IP_ADDRESS>:5432:5432"
+      - "<IP_ADDRESS>:15432:5432"
     volumes:
       - db_home:/var/lib/postgresql/data

This looks like this is now supported by using docker-compose-non-dev.yml

Shouldn't it be docker-compose-dev.yml tho? ^^

non-dev doesn't volume mount the code, hence it's not for developing superset. It's also not suitable for prod, so non-dev makes the most sense :)

non-dev doesn't volume mount the code, hence it's not for developing superset. It's also not suitable for prod, so non-dev makes the most sense :)

Completely agree, I meant reversing functionality as well, so docker-compose.yml would contain the non-dev logic and docker-compose-dev.yml to contain the developers logic. User first kinda thing. I'm happy either way, just a suggestion.


fixed bugs in test_tsfresh

Reference Issues/PRs

What does this implement/fix? Explain your changes.
Now all tests in test_tsfresh.py should pass.

I am not sure about the necessity of "test_ratio_beyond_r_sigma_nan_case". The "nan_case" tests are causing us troubles because Polar's behavior has changed. I do not want to add a when pl.len() >= 1 for every feature we add. If user gets an error because they are calling std / sum / abs / any Polars expression on a null (empty) column, Polars now will throw errors instead of returning nan.
Updated Polar's plugin version and all the packages.
Fixed other tests where the names of columns do not match, but outputs are correct.

Any other comments?

Ciao tq, thank you very much for the PR. Will try to review this ASAP. Not super expert on this branch of the codebase.

Ciao tq, thank you very much for the PR. Will try to review this ASAP. Not super expert on this branch of the codebase.

Passed all tears. Tears of joy 🥹

OK here I am. Just two things before approving:

Did you run linters/formatters etc?
I see in the first commit that you commented out some tests (am I right?). Could you briefly explain why?

Then we're ready to go. Thank you very much.

I explained in my commit's comment, here is short version: the "nan_case" tests are unnecessary in my opinion. This occurs when some feature is called on a null series ( completely empty). In that case let Polars throw the user an error. If we really want to handle that case, we will need to write a pl.when(input.len() == 0).then().otherwise()... which in my opinion is quite pointless and redundant

Ciao tq, sorry for getting back late. One last question: I saw you added the rust-toolchain file. Should we keep it pinned with 2024-04-15? If so, I will just run a round of linter + formatter and merge :)

Adding the toolchain file helped me solve some issues regarding package updates (polars rs and faer)
My local run didn't cause any problems so I guess it will be fine. Let it spin and take a look?

Adding the toolchain file helped me solve some issues regarding package updates (polars rs and faer)
My local run didn't cause any problems so I guess it will be fine. Let it spin and take a look?

Yes, sorry if I wasn't clear. I wonder why you used nightly-2024-04-15 but it makes sense. It's rust 1.79 but "frozen" at that date. Will merge PR. We can switch to stable when it's released (I read June 13th).


Adding jax.nn.activations.log_cosh

Would you accept new activation functions such as log_cosh ?
Tensorflow/keras/pytorch all have it.
The implementation is not trivial (though simple enough) if one wants to have good numerical precision.
If you'd accept it i'll open a PR
def log_cosh(x):
    sgn_x = -2 * jnp.signbit(x.real) + 1
    x = x * sgn_x
    return x + jnp.log1p(jnp.exp(-2.0 * x)) - jnp.log(2.0)

Keras version: https://www.tensorflow.org/api_docs/python/tf/keras/losses/log_cosh (N.B. it appears to be a loss function?)
I couldn't see a PyTorch version?

There was no follow-up on this issue; closing. Feel free to reopen if you think this function would be of general interest, although I'm not seeing such an activation function in PyTorch or TF.


[HTML & NextJS page examples - White theme] Update components to align to grid

Follow on to: carbon-design-system/carbon-for-ibm-dotcom#6732
The components displayed in the NextJS and HTML template pages do not align with the grid.
https://ibmdotcom-web-components-html-staging.mybluemix.net/
https://ibmdotcom-nextjs-staging.mybluemix.net/
Lead space
The description and the edge of the button group should be aligned with the grid. Right now, they overhang the edge of the column.

Compare to specs:

Vertical Table of Contents
The ToC should overhang the edge of the left-most column, with the text aligned to the edge of the grid and the line selector element hanging outside the column.

Compare with spec:

Content block media
Header, body copy, and image should align with the column edge, currently they are floating inside the column. The text elements for the aside link list should align with the edge of the column, with the horizontal rule hanging over the edge of the column.

Compare to WC Storybook preview:

Callout quote
The Paragraph, Source, Copy 1, and Copy 2, and CTA text should align with the edge of the column. The beginning quotation mark and the horizontal rule should overhang the column.

Compare with specs:

Content group pictogram
The header, body, and pictograms should align to the edge of the column, but are currently floating in the middle of the column. The description header, description copy, and CTA should also align to the edge of the column.

Compare to spec:

Card section
The section title should align with the edge of the left-most column in the grid. For the cards, the card header, body copy, and CTA should align with the left-most column that the card sits in, with the card body overhanging the grid. This should be true for each of the cards in the section.

Compare to specs:

Content group banner
The group title should align with the edge of the grid - right now it is floating to the right within the column. The aside element should also have the text aligned to the column, with the vertical rule overhanging to the left.

See spec:

Card section carousel
The section title should align with the edge of the left-most column in the grid. For the cards, the card header, body copy, and CTA should align with the left-most column that the card sits in, with the card body overhanging the grid. This should be true for each of the cards in the section.

Compare to specs:

CTA Section
The section header, body, button, and secondary subsection should align with the edge of the column. The second subsection should also align with the edge of the column.

See spec:

seperated out issues being seen in storybook here: #8933, #8932, #8931, #8930, #8929


No results in "identify" menu

No results in "identify" when search by kinopoisk ID

Emby version: 4.7.11
.Net version: it's debian linux installation, there is no global .net installation

Sorry, find "kinopoisk id" in "identify" section, but forgot to enable it's as metadata provider in libraries %)


replaces deprecated findById with findByPk

Assignee Tasks

[x] added unit tests (or none needed)
[x] written relevant docs (or none needed)
[x] referenced any relevant issues (or none exist)

Sequelize v5 no longer supports the Model.findById method: it's been replaced by findByPk. We were still using findById in the deserializeUser function, which threw an error when a user signed in.

Huh. Never realized that findById didn't automatically use the PK for a model. Or maybe it did, and this is just a better name for the same method? Either way, looks good to me. 👍


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 1.10.105 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: stop processing ticks until all gltfs are different of loading state when the scene is loading (tick_number < 3)

Apply ADR spec

Codecov Report
Attention: 105 lines in your changes are missing coverage. Please review.

Comparison is base (80de428) 14.68% compared to head (701b8f6) 14.62%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
- Coverage   14.68%   14.62%   -0.07%
==========================================
  Files          97       98       +1
  Lines       11573    11648      +75
==========================================
+ Hits         1700     1703       +3
- Misses       9873     9945      +72

Files
Coverage Δ

...land-godot-lib/src/godot_classes/dcl_scene_node.rs
72.00% <100.00%> (+1.16%)
:arrow_up:

...traland-godot-lib/src/scene_runner/update_scene.rs
0.00% <0.00%> (ø)

...-lib/src/scene_runner/components/gltf_container.rs
0.00% <0.00%> (ø)

...-godot-lib/src/godot_classes/dcl_gltf_container.rs
3.77% <3.77%> (ø)

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


🐞 Type error when use forwardRef in typescript

Description
I have some code like that:

It has an type error on ref
Type 'ForwardedRef<HTMLDivElement>' is not assignable to type 'Ref<"div"> | undefined'.
  Type '(instance: HTMLDivElement | null) => void' is not assignable to type 'Ref<"div"> | undefined'.
    Type '(instance: HTMLDivElement | null) => void' is not assignable to type '(instance: "div" | null) => void'.
      Types of parameters 'instance' and 'instance' are incompatible.
        Type '"div" | null' is not assignable to type 'HTMLDivElement | null'.
          Type 'string' is not assignable to type 'HTMLDivElement'.ts(2322)
index.d.ts(134, 9): The expected type comes from property 'ref' which is declared here on type 'IntrinsicAttributes & Omit<HTMLAttributes<HTMLDivElement> & Partial<{}>, "className" | "ref"> & extraType & RefAttributes<...>'

Did i missed some thing?
Reproduction
No response
System Informations
@master/style-element.react: "^1.1.4
typescript: 4.5.5

@z22919456  Just replace HTMLElement with 'div', and it works.

@BenSeage  Thank for your help


Update UXD mint and tag

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: 7kbnvuGBxxj8AG9qp8Scn56muWGaRaFqxg1FsRp3PaFT
Token Name: UXD Stablcoin
Token Symbol: UXD
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token: https://uxd.fi
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

added in https://github.com/solana-labs/token-list/pull/1498/files

added in https://github.com/solana-labs/token-list/pull/1498/files

Sorry not sure I understood the comment now that I look back at it, I don't see any update?

done as #14466 14466


Property 'on' does not exist on type 'ListenLiveClient' since 3.4

Since upgrading to 3.4 we receive the following typescript warning: Property 'on' does not exist on type 'ListenLiveClient'.ts(2339). Worked fine with 3.3.x and before.
Code is basically the the live audio example from the readme, see https://stackblitz.com/edit/vitejs-vite-rxpylf?file=src%2Fmain.ts

I can't see how it's possible. All the tests and examples work. I'll look into it immediately

Not sure either sadly, thanks for investigating :)

The import is wrong. See #311.

I am still getting this error in 3.5.
error TS2576: Property 'on' does not exist on type 'ListenLiveClient'. Did you mean to access the static member 'ListenLiveClient.on' instead?

@lukeocodes it's back again, we're getting error TS2339: Property 'on' does not exist on type 'ListenLiveClient'. all over again :(
would be great if you could add some basic typescript checks to avoid such issues in the future.

@lukeocodes it's back again, we're getting error TS2339: Property 'on' does not exist on type 'ListenLiveClient'. all over again :(

It would be helpful if you could provide details about your TypeScript version, an example of how you're using it (the code, not a screenshot), details about your OS/environment and anything else that may help.
As for this comment;

would be great if you could add some basic typescript checks to avoid such issues in the future.

TypeScript is inheriently type safe. If there was an issue here when building with our TS settings, it would fail to build. If there was an issue here with the code, our live examples/ would also throw errors. My thinking is that this is environment related and we need to be stricter with defining our types.

Adding @types/node did the trick for me.

same here

Ahh I think we need to move @types/node from devDeps to deps. Thanks, both! We'll cut a release ASAP


Add a car example to demos

Hope this car demo using revolute joints and apply torque can be of some use

This is great!


Memory increases for each use

Before starting the YPImagePicker from my app, I'm around 40MB of used memory (real device).

After starting the picker/camera the memory goes up a couple of MBs.
When I dismiss the picker, the used memory is still at the increased amount.
After using filters, the memory goes up around 50MB more.
When I dismiss the picker, the used memory is still at around 150MB.

So, after opening, using some filters, dismissing a couple of times, the used memory is easily at 500MB.
Can you please look at this?

@theolof
Thanks for such a detailed explanation.
The picker will always use quite a lot of resources since tapping into the camera library and filters
are memory usages but it should let go of them as soon as it's over.
This looks like an issue then, thanks for the eagle eye !
I am going to look at this into more detail :)
Cheers,

@theolof by the way have you found a way to add the Swedish translations?

@theolof
I have found an issue in the example project. The picker's callback was creating a retain cycle so that the picker would still live in memory after being dismissed.
I don't know if you were dismissing the picker that way in your app, but adding [unowed picker] will break this retain cycle and allow for the whole hierarchy to be released (Library / Photo/ Video / Filters ...)
func showPicker() {

    let picker = YPImagePicker()
    picker.showsVideo = true
    picker.videoCompression = AVAssetExportPreset640x480

    // `unowned` is Mandatory since it would create a retain cycle otherwise :)
    picker.didSelectImage = { [unowned picker] img in
        self.imageView.image = img
        picker.dismiss(animated: true, completion: nil)
    }

    present(picker, animated: true, completion: nil)
}

Before 10 subsequent launch would take up around 300MB in memory and with the fix it goes down to around 70MB. (Starting memory being around 70MB)
Let me know if that helps :)
Have a fantastic day!

@theolof any updates?

Thanks, it fixes the problem.

@theolof  Awesome ! Thanks :)


Aoaf 544 disabled package information

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


Need an override for Stackdriver metric prefix

The Stackdriver exporter has a MetricPrefix field that's intended to be used in the metric name (docs), but it seems to be used as an override for DisplayName (source).
The metric prefix seems to always be custom.googleapis.com/opencensus (source).
I suspect this is a bug, not an intended behavior. Is it possible to change it? I could contribute the fix, if it's acceptable.
@fabxc

/cc @songy23

@jkohen I think this is intended. The MetricPrefix field is only for overriding the prefix of DisplayName at first. For metric name, the prefix custom.googleapis.com/ is necessary since the Stackdriver exporter uploads metrics as custom metrics. Stackdriver backend will return an error if the metric name doesn't start with custom.googleapis.com/. You can send a PR to override the opencensus/ namespace though (we already did that for Prometheus exporter).

Related maybe: https://github.com/census-ecosystem/opencensus-go-exporter-stackdriver/issues/22

Yang Song, it's not true that you can't override the custom.googleapis.com
prefix. For instance, external.googleapis.com/prometheus/ is also
acceptable, and the list will continue to expand to accommodate cases like
the one Ramon linked to. I think MetricPrefix should override the entire
thing.
I don't really understand the use case for overridding DisplayName. Can you
expand on that? And do you disagree that the documentation for MetricPrefix
is misleading?
PS: OC should be using external.googleapis.com/opencensus by default (but
that's a separate issue).
On Wed, Jul 18, 2018 at 12:47 PM Ramon Nogueira<EMAIL_ADDRESS>wrote:

Related maybe: census-ecosystem/opencensus-go-exporter-stackdriver#22
https://github.com/census-ecosystem/opencensus-go-exporter-stackdriver/issues/22
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/census-instrumentation/opencensus-go/issues/836#issuecomment-405998964,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG0TaG4nrgLqkAn2QJ6cagFoxZgw7JPGks5uH2aEgaJpZM4VUzFk
.

it's not true that you can't override the custom.googleapis.com
prefix. For instance, external.googleapis.com/prometheus/ is also
acceptable,

That's not true. Currently if you upload some metrics starting with external.googleapis.com/opencensus to Stackdriver, you will get a Permission_Denied error. Stackdriver documentation said:

All user-defined custom metric types have the DNS name custom.googleapis.com.

I don't really understand the use case for overridding DisplayName. Can you
expand on that? And do you disagree that the documentation for MetricPrefix
is misleading?

This is brought up by https://github.com/census-instrumentation/opencensus-go/issues/582 and fixed in https://github.com/census-instrumentation/opencensus-go/pull/583. Agree that documentation is misleading, it should be "MetricPrefix overrides the OpenCensus prefix of the display name of a metric." instead.

PS: OC should be using external.googleapis.com/opencensus by default (but
that's a separate issue).

There's an ongoing discussion about defining default OC metrics in Stackdriver, and @ramonza is leading that. However as I mentioned earlier, for now all the metrics need to be under custom.googleapis.com.

It is not true that all metrics need to be under custom.googleapis.com, see the Stackdriver documentation. I believe Create should work for MetricDescriptor, I'll file a documentation bug.
The list of prefixes will continue to expand. It'd be sad to end up with two more "metric prefix" fields: one to modify DisplayName, one to replace opencensus, and one to replace custom.googleapis.com
I still find changing the prefix of DisplayName a very marginal use case, and to be honest it seems hacky to use the display name to group metrics this way. It's sad MetricPrefix is used for that, because "metric" != "metric descriptor documentation".

I see your point here. Sorry the "external metrics list" concept is totally new to me, and I didn't realize you can put any custom metrics under "external.googleapis.com". If you're confident that all your metrics (probably including all the gRPC metrics) should be under some other systems (e.g Prometheus, Agent), I'm fine with prefixing the metric name with them.

I still find changing the prefix of DisplayName a very marginal use case, and to be honest it seems hacky to use the display name to group metrics this way.

This is brought up by an external user, though I'm not sure about their use case.

It'd be sad to end up with two more "metric prefix" fields: one to modify DisplayName, one to replace opencensus, and one to replace custom.googleapis.com

Unfortunately, for backwards-compatibility, we need to add another "metric prefix" field, since users can put any arbitrary prefix the current "MetricPrefix" field. Changing the behavior of the existing "MetricPrefix" field may break their application.

Just an aside but in future let's have all Stackdriver discussion on the Stackdriver repo here: https://github.com/census-ecosystem/opencensus-go-exporter-stackdriver/
We are scheduled to remove the legacy embedded Stackdriver exporter that lives here soon. This issue will probably need to be closed and moved over as well.

Moved this discussion to related issues on the Stackdriver repo.


Update documentation after repository split.

📖  CC @xu-cheng @UniqMartin

Done! Needs some minor adjustments.

Thanks @UniqMartin! All addressed and merging.


1.13.x: set GOMAXPROCS to the CPU quota in pachd and the worker

Backport of #5971.

Travis passing, so I'm merging this.


Question: Support for front-end frameworks other than React?

I just stumbled across Reflex and it looks pretty cool. Apologies if that's a beginner's question but I couldn't find this in the docs:
Is there's anything specific about React that makes it the preferred (or maybe even only supported/supportable) choice of libraries? What about...

SolidJS
Vue.js
Svelte

or others?

Hello, React has the most libraries and biggest ecosystem that's why we chose it. Would be interested to hear advantages of the other frameworks you listed. Libraries like svelte are nice for coding ergonomics but the user doesn't see this at the end of the day because its just compiled code

React-native would be nice then can do PWAs with reflex :)

I have used React-Native in the past for cross-platform app development so that would be interesting, but for the web, nowadays I would probably choose SolidJS for performance, lack of virtual DOM and "coding ergonomics"... but I'm not a web dev by profession, so I might be missing other promising front-end libraries.
@Alek99 When I was looking at the docs, it was not clear to me, but it sounds like Reflex is hardwired to React (as in, it won't ever support anything else), is that true?

@chrisgeli Currently we do use React, but our base compiler should be able to compile down to any other framework with a few tweaks. It would be great to make reflex more modular so we compile down to different frontend frameworks.

closing this for now, but this is something we can revisit in the future.


Delete ec2 profile should report error if the profile could not be deleted

Broadly we need to make sure that the user is notified of errors. Definitely a larger issue here.

@TristanWright This was fixed by #466?

yes it was, closing


WIP - Widget cells

@maartenbreddels Isn't it crazy? :P Widgets are so cool

@maartenbreddels Isn't it crazy? :P Widgets are so cool

Love it :)
To add to our conversation, we could maybe use the renderer trait for having a render widget (a Union of String and Widget), and add an 'editor' trait (surprised we don't have that already).
type is just an alias for setting with the renderer and editor.

I do think having the widget model in the sheet data (cell value) is the right direction

I agree, they should only have numerical/string values. For instance, you want to be able to jslink a row of column vector to a bqplot scatter's x trait.

So it makes sense to put the widget model in the data

You just said not to do this above right?

and the renderer creates a view of the widget.

Indeed, it makes sense to broaden the scope of the 'renderer' trait (allow for more than Unicode), or to register a Widget as a renderer (by name).

I agree, they should only have numerical/string values. For instance, you want to be able to jslink a row of column vector to a bqplot scatter's x trait.

I think you misread. I'm actually saying that putting the widget model in the sheet data would be the way to go.
And those are the reasons why I think that:

In Handsontable, we can see the data as being the model of the table, and the renderers are kind of the view creators. So it makes sense to put the widget model in the data, and the renderer creates a view of the widget.
Also, it is a lot faster this way, as the sheet data is not rerendered every widget value update. This makes widgets interactions a lot smoother.

I think you misread.

I did :)
Ok, thinking about it, I think the two approaches are almost orthogonal. In one case, the Cell.value is a widget, the type/renderer is of 'widget' type, which is what you are suggesting now.
What I proposed, is to have the Cell.value be a number/string/whatever, and have a renderer or editor that creates/uses a widget for rendering or editing a value. I don't think one or the other solution is better, I can see use cases for both.
For instance, when displaying an image, you would want the Image widget itself to be the value (your solution would suffice). However, for rendering a progress bar for instance, you may want to use the Progressbar widget only for rendering, while some other process sets the value (which is numerical), and maybe the editor is a FloatSlider widget.
Writing this down I think in 80% of cases what you and Sylvain suggest is probably what we want, and is the most straightforward to implement.

... and is the most straightforward to implement.

Exactly, the thing is that having the renderer as a widget, and the value being numerical/string, you need to implement the logic for linking the value to the widget. You also need one widget per value in the case of a Cell range, and you need to link them all.
Not only it's harder to implement, but it's also slower. If you have a FloatSlider linked to a numerical value, every time you update the slider value, it triggers the float value change, it triggers the change of data, and the entire rendering of the table.
Whereas in the case of having the widget model as the value, ipywidgets deals with the widget update, not need to render the table.
It's not assumptions, I tried both options. And it's faster.
So, at the end of the day: easier to implement and faster :)

However, for rendering a progress bar for instance, you may want to use the Progressbar widget only for rendering, while some other process sets the value (which is numerical), and maybe the editor is a FloatSlider widget

I'm trying to think of a better use case than this. Like having a bqplot widget, and when you click on it you have a FloatSlider appearing that changes one scale. But this can be achieved having the bqplot widget in one cell, the slider in another, and using the calculation function from easy.py

Yes, there won't be many use cases for (lets call it) 'option 2' (having an editor/renderer for a widget with non-widget value).
In case we want it in the future, for reference, one idea could also be:

register an editor with Handsontable, say 'jupyter-widgets/FloatSlider', which would need
model name/package/version
optionally view name/package/version (it can take those from the model)
default parameters
the name of the value trait (for instance 'value', in the case of a FloatSlider).

The editor would then create the model (with the default parameters), set the value trait, create a view. Once the editing is done, the widget can be destroyed.

So, at the end of the day: easier to implement and faster :)

You already had me at 'Exactly' :), i'm on board!

Not only it's harder to implement, but it's also slower. If you have a FloatSlider linked to a numerical value, every time you update the slider value, it triggers the float value change, it triggers the change of data, and the entire rendering of the table.

Also, for future reference, this assumes the widget does not change size/layout. In case it does, we should (I think) rerender the table. I think we can do without first, it could be solved listening to resize events.

Actually, there is an issue concerning the size of the widget. Handsontable uses what is called a ghost table for performing a pre-rendering of the table in order to know the size of each cell before creating the real table with the correct sizing.
The problem is that it calls the rendering function synchronously (see this code), while the creation of the widget view is asynchronous. So it cannot know what is the size of the widget before rendering the whole table.
A workaround that we thought of with @SylvainCorlay would be to synchronously create a div element that has the CSS classes of the widget and its layout (avaible in the widget model). See this comment.
In the long term, I think we should open a PR upstream for support of asynchronous rendering functions.

Can't we solve all issues by listening to phosphorjs 'resize' and 'after-show' events, and rerender the table after that?
Or would that trigger the recreation of the view again?

Or would that trigger the recreation of the view again?

Actually I have a workaround for that too. Otherwise multiple views are created by Handsontable. See this line.

Can't we solve all issues by listening to phosphorjs 'resize' and 'after-show' events, and rerender the table after that?

Maybe, let's try :)

In the long term, I think we should open a PR upstream for support of asynchronous rendering functions.

I think that would be the cleanest approach.

Actually I have a workaround for that too. Otherwise multiple views are created by Handsontable. See this line.

Could this be buggy? Idea, set value to a FloatSlider widget, then change it to a Button, I guess that the FloatSlider will continue to show? If not, why not? :)
In any case, such an approach is a good idea; we should try to create views only when necessary.

Could this be buggy? Idea, set value to a FloatSlider widget, then change it to a Button, I guess that the FloatSlider will continue to show? If not, why not? :)

Yes, I thought about this use case too. I guess the slider will stay there and the button won't be rendered. It's not a good workaround.
I cannot think of a better one though... Do you have ideas?
We need to check that there is not already a view for this exact widget model inside of the td element.

First 'dirty' idea:

in SheetView.on_data_change create a matrix (list of lists) that tracks all widgets, say this.widget_grid all with null values (previous views should be destroyed).
In SheetView.render, make this.hot._widget_view = this so that we can have a reference to the SheetView in the renderer.
In the renderer, check of existence of instace._widget_view, and if instace._widget_view.widget_grid[row][col] is null, create a new view.
If the view exists, check if the model is the value model (if not, destroy view).

I recommend writing some unittest for this!

I have a working version. Changing the widget value works fine, the styling looks good.

@maartenbreddels rebased and working :)


https://github.com/spyder-ide/qtpy/issues/348

started a discussion  to compare qtpy, a new python module that seems to do the same as Qt.py
it has pyqt6 and pyside6 support, which address this issue https://github.com/mottosso/Qt.py/issues/367 requesting it to be added to Qt.py
so far most tools on github in games & VFX industry still use Qt.py
so updating Qt.py would be ofcourse preffered.
It'd be great to know also how compatible they are, and what's involved in swapping from 1 to the other.

A new module?
https://github.com/spyder-ide/qtpy/issues/69
Originally, qtpy modified the PyQt namespace, which was fine for standalone applications but less fine for embedded ones like Maya, where other applications depend on PyQt in addition to the ones that were using Qt.py.
Today, I'm not sure, although the goals of both projects seem consistent so I'd imagine so. Qt.py members are also a lowest-common-denominator, meaning an application written with it would run using PyQt4 as well, which would continue to be true for PyQt6 also.
PR is welcome, even though it seems somewhat premature given all of VFX is still on Qt 5.

 By contrast, QtPy was originally focused on scientific applications, which is still its primary userbase, though nowadays it sees a fairly broad cross-section of uses in general-purpose programs.

Originally, qtpy modified the PyQt namespace, which was fine for standalone applications but less fine for embedded ones like Maya, where other applications depend on PyQt in addition to the ones that were using Qt.py.

This was indeed true, though we recently (a couple releases ago) removed the last instance where the namespace was monkeypatched.

Qt.py members are also a lowest-common-denominator, meaning an application written with it would run using PyQt4 as well,

As you imply, this is also, in general, an objective of QtPy, though we alias compatible objects that change names between bindings or Qt versions to further improve intra-version compatibility byond a strict LCD. In the recent QtPy 2.0 we dropped support for Qt4, since it and its bindings have been EOL for 6 1/2 years now and were broken (at least without heavy third-party patching) on modern, supported Python versions, we were no longer able to fully CI-test it, and few or no actively maintained projects were still using it. However, existing applications written against QtPy will still work just fine, since it was already abstracting those differences, unless they depended on something that was Qt4-only.

which would continue to be true for PyQt6 also.

We quickly ran into a bunch of thorny conceptual and practical issues trying to bridge the APIs across multiple decades of Qt/binding releases, from bleeding-edge to long-obsolete, which led us to drop support for running against long-EOL, non-LTS Qt releases earlier than 5.9 (and even then, that raises a number of practical difficulties vs. only supporting 5.12+, but we make do). Since user code properly written against Qt.py will still work running on a newer binding, and even currently 5.12 is the oldest version required by the current + 3 guidance of the VFX reference platform, it seems prudent to drop support at runtime for older versions (or at the very least, <5.6) when adding CY2024 support—but that's ultimately up to you, of course.

it seemed new since the earliest release on their github was from 2021, and I never heard about it.

Just to make sure we're all clear, this is just the earliest release tagged with GitHub's new(-ish) Releases feature (which many projects don't use at all, and others sporadically). Per the more canonical sources (Git tags, PyPI releases, Changelog, etc.), you can see that our first official release as an independent package under the name QtPy was March 1 2015, and as mentioned in our Readme, QtPy's history actually extends back to 2011, as it was itself the result of the pyqode.qt, qtconsole.qt_loaders, spyderlib.qt and qlueviz qt-helpers projects all joining forces (the first two mentioned separately in the @mottosso Qt.py Readme, and all long-obsolete and abandoned in favor of QtPy).
Interestingly, the Qt.py Readme states that 0.2.6, which is the first Git tag, was the first release of Qt.py in June 2016, but the earliest PyPI release is 0.2.1 in May 2016—merely a curiosity of historical interest, but I figured it was worth mentioning. To be honest, past a certain point (which both of our projects are), I'm not sure the longevity of the project makes much of a practical difference compared to how actively each is maintained, and all the other factors involved.

GitHub's new(-ish) Releases feature

C'mon. 😅

https://github.blog/2013-07-02-release-your-software/

I found this out by using a new(-ish) feature called "Google".

Still newer than QtPy; that's why I said "-ish" XD


[style][修改struct描述]

:tada: This PR is included in version 2.23.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make Query{Func,Type,Var}::def non optional

query.h
struct QueryType {
......
  Usr usr;
  optional<Def> def;  ///  `Def def` makes it more similar with IndexType

while indexer.h
struct IndexType {
...
  Usr usr;
  IndexVarId id;

Actually I wanted to go the opposite direction, indexer.h should have def be optional.

Why?

Because if we accidentally use a def that is not valid it will crash instead of giving bad data.

Add a 32-bit timestamp to QueryLocation (by taking 4 bytes from   QueryFileId path;)
When .callers .instances .derived are scanned, remove invalid IDs

I'm fine if we do that logic using Maybe, so the checks happen implicitly.

The issue is how to remove weak references (the pointed Query* may be removed or re-used) in .callers .instances .derived. I want to remove optional<Def> def in callers so that they do not need to check if a Query object is stale (these if (var->def) checks are bad). The logic can be coded in ToQueryLocation.

echo 'int a;' > a.cc; echo > b.cc;
Copy int a; to b.cc
Delete int a; from a.cc

In this scenario the the VarDefDefinitionData of int a; will be nullopt though it shouldn't. If we want to make this work, optonal<Def> def; -> std::vector<Def> def;, but I hope there could be a better solution.

template <typename F>
struct VarDefDefinitionData {
  std::string detailed_name;
  NTString hover;
  NTString comments;

  Maybe<Use> spell;  // id,kind refer to semantic parent
  Maybe<Use> extent; // id,kind refer to lexical parent
...
};

struct QueryVar {
...
  std::forward_list<Def> def;  /// we should make it a singly linked list to support "transient odr violation" (variable moving/copying without deleting the old one first)
};

Close via f24b5a36fcc18f367ef41852179b62b6f404fc4a
But the merge logic hasn't been done


Failed to host the dotnet Web API Project

System.MissingMethodException:“Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection Microsoft.Extensions.Hosting.HostApplicationBuilder.get_Services()'.”

I cannot reproduce, using https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?view=aspnetcore-8.0&tabs=visual-studio as sample.
I however had to add ASPNETCORE_PREVENTHOSTINGSTARTUP=1 to prevent the following exception:
crit: Microsoft.AspNetCore.Hosting.Diagnostics[11]
      Hosting startup assembly exception
      System.InvalidOperationException: Startup assembly  failed to execute. See the inner exception for more details.
       ---> System.ArgumentException: The value cannot be an empty string. (Parameter 'assemblyName')
         at System.ArgumentException.ThrowNullOrEmptyException(String argument, String paramName)
         at System.Reflection.AssemblyName..ctor(String assemblyName)
         at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.ExecuteHostingStartups()
         --- End of inner exception stack trace ---

Output with the .NET Core runtime:
$ ASPNETCORE_PREVENTHOSTINGSTARTUP=1 /p/projects/OPENSOURCE/TodoApi/EzDotnet/build/samples/cli/ezdotnet.exe /p/projects/OPENSOURCE/TodoApi/EzDotn
et/build/CoreCLR/libcoreclrhost.dll /p/projects/OPENSOURCE/TodoApi/bin/Release/net8.0/win-x64/TodoApi.dll Program Entry
Handle: 00007ffab6490000
calling clrInit, pwd: P:\projects\OPENSOURCE\TodoApi\bin\Release\net8.0\win-x64, asm: P:/projects/OPENSOURCE/TodoApi/bin/Release/net8.0/win-x64/To
doApi.dll
[clrInit]:
calling runMethod, handle:<PHONE_NUMBER>
[runMethod]:
[runMethod]: Loading 'P:/projects/OPENSOURCE/TodoApi/bin/Release/net8.0/win-x64/TodoApi.dll', then running Entry in Program,TodoApi
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: P:\projects\OPENSOURCE\TodoApi\bin\Release\net8.0\win-x64
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
      Failed to determine the https port for redirect.

Well... Without inject services, it can work.
Did you add some service into the web app builder?
for example add this code before builder.Build();  : builder.Services.AddControllers();

Sorry, My Problem. It can work now.

Ok i reproduced it.
It's related to missing APP_CONTEXT properties that need to be set from native code, namely:

APP_CONTEXT_BASE_DIRECTORY
APP_PATHS

And possibly a few others. AspNet Core uses reflection to load further assemblies, and that code will fail if those aren't set.
This is also relevant for self contained apps.
I'll wrap up a fix shortly :)

I pushed a fix. let me know if it fixes the problem

Thanks for your help!
inject services can work now.
But I found new problem: It still failed to host AspNet Core Project when I add this log package in my dotnet project:

I reproduced it, but from what i'm reading you shouldn't use the .Abstractions package (I didn't go in depth but, from what I understood, it doesn't contain concrete types)
I fixed it by installing:

Microsoft.Extensions.Logging
Microsoft.Extensions.DependencyInjection

As to why this is necessary, i'm not completely sure yet.

My project use SignalR, Add Microsoft.Extensions.Logging, Microsoft.Extensions.DependencyInjection still not work...😥
PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="8.0.8"
PackageReference Include="Microsoft.AspNetCore.SignalR.Client.Core" Version="8.0.8"
PackageReference Include="Microsoft.AspNetCore.SignalR.Common" Version="8.0.8"
PackageReference Include="Microsoft.AspNetCore.SignalR.Protocols.Json" Version="8.0.8"
I am not sure If It's caused by EzDotnet.

Could you provide a stack trace? Or some more information? Or even better a repro project?

ezdotnet.exe "E:\git\cpp\EzDotnet\x64\Debug\coreclrhost.dll" "E:\codes\ConsoleApp1\PluginDemo\bin\Debug\net8.0\PluginDemo.dll" "Traffic.Monitor" "Entry"
Uploading PluginDemo.zip…
Handle: 00007FFE70FD0000
calling clrInit, pwd: E:\git\cpp\EzDotnet\samples\cli\Debug, asm: E:\codes\ConsoleApp1\PluginDemo\bin\Debug\net8.0\PluginDemo.dll
[clrInit]:
[initHostFxr]: host_path: E:\codes\ConsoleApp1\PluginDemo\bin\Debug\net8.0
calling runMethod, handle:<PHONE_NUMBER>
[runMethod]:
[runMethod]: Loading 'E:\codes\ConsoleApp1\PluginDemo\bin\Debug\net8.0\PluginDemo.dll', then running Entry in Traffic.Monitor,PluginDemo
Unhandled exception. System.AggregateException: One or more errors occurred. (Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection Microsoft.Extensions.DependencyInjection.LoggingServiceCollectionExtensions.AddLogging(Microsoft.Extensions.DependencyInjection.IServiceCollection)'.)
---> System.MissingMethodException: Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection Microsoft.Extensions.DependencyInjection.LoggingServiceCollectionExtensions.AddLogging(Microsoft.Extensions.DependencyInjection.IServiceCollection)'.
at Microsoft.AspNetCore.SignalR.Client.HubConnectionBuilder..ctor()
at PluginDemo.Program.Go(String[] args) in E:\codes\ConsoleApp1\PluginDemo\Program.cs:line 14
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait()
at Traffic.Monitor.Entry(IntPtr args, Int32 sizeBytes) in E:\codes\ConsoleApp1\PluginDemo\Monitor.cs:line 9

Thanks for the sample. Just fyi, I'm currently not at home and it will take a while before I can take a look at it.
I'll let you know as soon as I have the chance to check it out.

I'm looking at it.
I haven't figured it out yet but I suspect it might be related to the way hostpolicy is getting initialized.
If you set COREHOST_TRACE=1 and COREHOST_TRACE_VERBOSITY=4 and then run both

ezdotnet (which throws the exception)
the published app's exe (which works)

you can see the differences in dependency resolution.
by comparing the 2 I see that, in the working case, the deps file (PluginDemo.deps.json) is loaded early and hostpolicy is initialized in apphost mode.
In ezdotnet, it's initialized as libhost and the deps json is considered later on.
This difference is likely due to me using hostfxr_initialize_for_runtime_config rather than hostfxr_initialize_for_dotnet_command_line.
According to the docs:

hostfxr_initialize_for_dotnet_command_line - this is the initialize for an application. The API is a bit more complicated as it allows for command line parsing as well. Eventually we might want to add another "initialize app" API without the command line support.
hostfxr_initialize_for_runtime_config - this is the initialize for a component (naming is not ideal, but can't be changed anymore).

So it seems that I'll have to try with the dotnet command line API to simulate an invocation from "dotnet run"
For what it's worth, I took a quick look at the .NET source code and indeed there's a variable called is_app which is set differently depending on how the runtime was initialized.

Thanks to @vitek-karas for the help, and pointing out about get_function_pointer_fn.
The issue is that load_assembly_and_get_function_pointer_fn performs an additional assembly load, on top of the one already loaded for the first Assembly Load Context (ALC).
The second assembly load is always assumed to be of "component" (library) type, which is why some dependencies are missing.
get_function_pointer_fn is .NET 5+ only, so we'd be breaking support for .NET Core 3, but it will do for now.
We can eventually come back to .NET Core 3 later if the need arises.

@Zhao-Michael I can successfully run the sample with the latest changes. Can you try again and let me know?

It works!
Thanks for your great job!
Please give me more time to do more test!
Hope no more bugs are found~ 😄


Unable to destroy test db after using this library.

Everything was working fine, after install this lib my django test CI  failed. Test database is not destroying and raising
I am 100% sure, session is used by drf-api-logger.
django.db.utils.OperationalError: database "test_betrics_db" is being accessed by other users DETAIL:  There is 1 other session using the database.

Hi @pawan-betrics,
Can you please share some info related to your test cases?

`Creating test database for alias 'default'...
Found 15 test(s).
System check identified no issues (0 silenced).
...............
Ran 15 tests in 9.951s
OK
Destroying test database for alias 'default'...
DRF API LOGGER EXCEPTION: relation "drf_api_logs" does not exist
LINE 1: INSERT INTO "drf_api_logs" ("added_on", "api", "headers", "b...`
I get only this from CI terminal

Like Why Test cases using  drf_api_logs models ?

Hi @pawan-betrics
I have identified the issue, soon It'll be fixed

Okay  Great

@vishalanandl177 any follow-up on this issue?

Hi @pawan-betrics & @3cp.
Thanks for pointing out the issue but I'm not able to replicate the same issue. I tested in EC2 and K8s PODs.
Ca you please let me know the scenario and the system arch where you are facing the same issue?

Closing due to inactivity.


Retry attempted on already attempted host

Bug description
On receiving 503 service unavailable error response from an upstream server which is down, istio retries the request to the same endpoint as per istio’s default retry behavior.
So calls are getting retried to the same server three times, which is not be required.
[ ] Docs
[ ] Installation
[ ] Networking
[X] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Istio should not retry to an already attempted host
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)

This behaviour is seen inspite of the host predicate set to envoy.retry_host_predicates.previous_hosts
"route": {            "cluster": "outbound|8080||upstream-service.foo.svc.cluster.local",            "timeout": "0s",            "retry_policy": {             "retry_on": "connect-failure,refused-stream,unavailable,cancelled,resource-exhausted,retriable-status-codes",             "num_retries": 2,             "retry_host_predicate": [              {               "name": "envoy.retry_host_predicates.previous_hosts"              }             ],             "host_selection_retry_max_attempts": "5",             "retriable_status_codes": [              503             ]            },            "max_grpc_timeout": "0s"           },           "decorator": {            "operation": "upstream-service.foo.svc.cluster.local:8080/*"           },

This behaviour is seen inspite of the host predicate set to envoy.retry_host_predicates.previous_hosts
"route": {            "cluster": "outbound|8080||upstream-service.foo.svc.cluster.local",            "timeout": "0s",            "retry_policy": {             "retry_on": "connect-failure,refused-stream,unavailable,cancelled,resource-exhausted,retriable-status-codes",             "num_retries": 2,             "retry_host_predicate": [              {               "name": "envoy.retry_host_predicates.previous_hosts"              }             ],             "host_selection_retry_max_attempts": "5",             "retriable_status_codes": [              503             ]            },            "max_grpc_timeout": "0s"           },           "decorator": {            "operation": "upstream-service.foo.svc.cluster.local:8080/*"           },

How many endpoints does the service has?

this might be the same as https://github.com/istio/istio/issues/24512, although looks like this is not weighted cluster


All apps built with twine-app-builder seem to have the same app ID

Hello,
All apps built with twine-app-builder seem to have the same app ID, which results in one app writing over the other when another is installed. On Windows, they are all installed in the same directory (%AppData%\Local\test_electron_forge), so for example, if you have installed app A, and then install app B, app B overwrites app A in the test_electron_forge folder.
I think this could be fixed by adding appId to package.json in github.com/lazerwalker/electron-wrapper-template, and allowing users to set the appId individually so that created apps have different IDs, but I am not too familiar with Electron so I might be wrong on this point.

Argh, good catch! That fix sounds exactly right.
Thanks!


conda is deleted while installing Miniconda

The conda program in non-root conda environments is a symlink to the root environment's conda. The root conda is deleted during the installation of Miniconda.

The conda commands conda and activate both rely on  the conda python package. For those commands to work in the non-root environment, the package would have to be moved as well. However, the package is for python 3.6, whereas the non-root python version might not be 3.6.
Closing this issue for now. If conda is required, it can be installed with pip.


[snarky-rs] refactor Constants to take advantage of KimchiCurve

ping @mrmr1993  @fabrizio-m

urr, have some problem making this work due to https://github.com/o1-labs/proof-systems/pull/796, might have to revert that  one


docs: add template for new tasks

Description
Adds an additional template to track issues / tasks in GitHub; the template includes a description, user-stories, and acceptance criteria along with a brief description of each. Input would be appreciated on want to include and if/how we want to use this template going forward.
Other Changes

Removed cLabs specific links

Tested
N/A
How others should test
N/A
Related issues
#1091

This should be used instead of the default empty issue template. Epics would have users stories and issues will have acceptance criteria.


ParseNumber method bug

Describe the bug
Parsing number method is not working correctly. It removes digits from phone body like dial code.
Package version
intl_phone_number_input: ^0.7.0+2
Flutter version
Flutter (Channel stable, 2.5.1, on macOS 11.4 20F71 darwin-x64, locale en-TR)
To Reproduce
PhoneNumber _number = await PhoneNumber.getRegionInfoFromPhoneNumber("+15417543010", 'US');
print(_number.phoneNumber);
flutter: +15417543010
print(_number.parseNumber());
flutter: +54754300 //(all 1 digits are removed instead first one)
Expected behavior
print(_number.parseNumber());
flutter: +5417543010
Targeted platforms (please complete the following information):
iOS

I also got this issue, I used another package to fix it


Boolean parameters are generated into strings

If I define a boolean parameter in an operation, the generated code converts the boolean to a string.
Take for instance,
    }, {
      "name": "stream",
      "in": "query",
      "description": "1/True/true or 0/False/false, return stream. Default false",
      "type": "string",
      "default": "false"
    }, {

Generated code,
Stream *string

I wasn't sure whether I am suppose to expect a bool or a string in the generated code.

the spec here says that it's a string. the type says string