Problem using browser-fs-access in jest

Hi There,
I'm using jest for testing and having trouble with importing the browser-fs-access library.
    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    <root>/node_modules/browser-fs-access/dist/index.js:2
    export { fileOpen } from "./file-open.mjs";
    ^^^^^^

    SyntaxError: Unexpected token 'export'

This seems to be a common issue, documented here: https://github.com/facebook/jest/issues/2550, however, the common solutions don't work.
I tried to use the following configuration parameter to account for presence of mjs files but still getting the same error. Any thoughts on how to allow jest to successfully compile browser-fs-access?
 "transformIgnorePatterns": [
   "node_modules/(?!browser-fs-access).+(js|jsx|mjs|ts)$"
 ]

Sorry, I'm not familiar with Jest, but https://github.com/facebook/jest/issues/2550#issuecomment-810144368 is the right place to ask your question.

To my great shame, I had to resort to bundling this package to commonjs.
https://github.com/steveruizok/browser-fs-access

I’m not really into bundling, but I know there’s a way to publish several builds in the same package.json. If you know how this works, maybe I could ask you to contribute this back, so others can profit and you don’t have to keep your fork in sync as new stuff gets added?!

Happy to do so! The fork uses esbuild to bundle into ESM and CJS modules, which I think is what you're describing too. The only modifications were replacing your slick for await loops with regular loops because esbuild can't parse those yet.

Awesome, thanks a ton! I have created https://github.com/GoogleChromeLabs/browser-fs-access/issues/82 to track this.

It appears that the transformIgnorePatterns workaround is still needed. Am I missing something? package.json doesn't seem to reference the cjs version anywhere.

We may want to revisit bundling. It looks like microbundle is the current go-to option. I have opened https://github.com/GoogleChromeLabs/browser-fs-access/issues/94 to track this. If you have time, feel free to work on a PR that fixes this, but else, I'll also eventually get to it, but need to deal with things that popped up during my recent time off.


Complete Training Example

I am quite newbie to DDPM and can't find a complete , end to end example for running the code with sample data. Is there any tutorial or a sample script ?

Try this one: Tutorial

Try this one: Tutorial

404 error

It seems that one doesn't work, try these links

https://huggingface.co/blog/annotated-diffusion [theory + Implementation]
https://magic-with-latents.github.io/latent/blog.html [theory]


Typescript support

Is your feature request related to a problem? Please describe.
We are trying to migrate our current portffolio from Javascript to Typscript component by component and we found the next issue related to this package:
<html>TS7016: Could not find a declaration file for module 'react-syntax-highlighter'. '/home/luisalaguna/Projects/portfolio/frontend2.0/node_modules/react-syntax-highlighter/dist/cjs/index.js' implicitly has an 'any' type.<br/>Try `npm i --save-dev @types/react-syntax-highlighter` if it exists or add a new declaration (.d.ts) file containing `declare module 'react-syntax-highlighter';`

Describe the solution you'd like
It should have a minimal typscript support.
Describe alternatives you've considered
There is this unoficcial alternative, but i don't think it is updated.
Additional context
We are trying to migrate our current portffolio from Javascript to Typscript component by component and we found the next issue related to this package:

I have the same problem and as suggested I run this command:
npm i --save-dev @types/react-syntax-highlighter
I don't know if that's the correct approach, but it worked for me

It seems there updated this package, i will check it later.


feat: implement metrics

partially addresses #12
also updates documentation to address #8

Hey @kjappelbaum
This looks amazing!
Please rebase over my latest commit to master - I've moved testing to Github Actions.
Then, we should be able to see run results here.
If we won't, we'll close this one and you'll open a new PR.
Also, please fix the single issue CodeFactor found (an extra space after the = in line 91 of metrics.py:

Codecov Report

Merging #19 (1909187) into master (bc9c050) will decrease coverage by 0.59%.
The diff coverage is 83.33%.

@@             Coverage Diff             @@
##            master      #19      +/-   ##
===========================================
- Coverage   100.00%   99.40%   -0.60%
===========================================
  Files            2        3       +1
  Lines          322      334      +12
  Branches        50       54       +4
===========================================
+ Hits           322      332      +10
- Misses           0        1       +1
- Partials         0        1       +1

Impacted Files
Coverage Δ

pulearn/bagging.py
100.00% <ø> (ø)

pulearn/elkanoto.py
100.00% <ø> (ø)

pulearn/metrics.py
83.33% <83.33%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Hey @kjappelbaum
Few issues here:

Commit-wise, please rebase your whole PR into a single commit, that lies AFTER the current head of master.

Note I've ammended the latest commit (to hopefully enable the linting job to leave annotations on PRs from forks), so you will have to rebase carefully. I suggest you simply realign your master with my master (will probably require git reset --hard origin/master on your master; just make sure all your work is also backed-up outside the repo's folder), then checkout a new metrics-new branch and just using a simple file system copy-paste to override all the latest files with your changed files (and ONLY with your changed files). Then just stage everything into a single commit with the combined PR description you have here as the commit message.

Test coverage is kept to a 100% on pulearn but your codes bring it down to 99.4% (because of a 83.33% coverage on metrics.py). Please bring it back up to a 100%.

You have many linting errors. Either run flake8 yourself, or checkout the linting anotations here (if my latest commit will indeed fix the issue.

Just a little more effort! Thank you for contributing! <3


License missing

Hi,
could you specify a License for this project, so I know whether I can use it for professional projects?
Kindly yours,
Tobias

Added the MIT license


move env-creation, and cache it ?

Especially when iterating locally on some files, it appeared to me that the conda step was one of the longes, even if env.yml did not change.
Wold it be possible to change the process to cache the env building part ? Something along:

Copy env.yml
create env.
remove env.yml
...
Copy the repository at the end.

Potentially using the hash of env.yml content for caching purposes.
No pressure, just thinking.

I think there are two important questions here:

What kind of machinery would need to be implemented to allow for this? E.g., is there a relatively foolproof and miminal-delta way of ensuring that caches are rebuilt only when they should be, and are always rebuilt when they should be.
How often do people update the non-buildfile content of the repo (aka, change code without changing the underlying environment)? My guess is that the answer here is "very often", so perhaps something like this would help save a lot of time waiting.

@Carreau I think this would be great if we could make it happen. The problems with this are:

What all do you copy? Especially with postBuild, it could refer to any other files in the repo
How do we do structure this in the software so it's maintainable as we move and add more buildpacks? This is especially important since BuildPacks are composable.
Can this go wrong with various buildpacks? The R one probably is just going to be an 'install.R' script that is arbitrary R code. I don't think we can cache that.

so I think this would be great, we'll just have to be very careful when doing it.

We should be able do this with environment.yml no problem. With requirements.txt it will usually work, but requirements.txt can have relative path references, e.g.:
# requirements.txt
ipython
-e . # install the current package!
-r docs/requirements.txt # multi-layer requirements!

I don't think conda can have local references, so it should have an easier time. We could try to check for this in requirements.txt, but it might be tricky.
As for how to do this in a composable way for buildpacks, we already have this separation for build_scripts and assembly_scripts, where build_scripts are run before adding the repo and assembly_scripts are run after. Buildpacks could do the same thing, either by including requirements.txt or environment.yml in build_scripts, or by declaring an explicit multi-stage assemble.

I ran into this in our workshop yesterday where builds were relatively expensive (a couple of minutes), and I did the following:

trigger build to show what we were doing,
create binder badge and add it to the readme
click binder badge link, and feel silly watching it build again just for the markdown change

I don't think we can do this for postBuild, but I think that's much less critical.
I'm going to have a look at this for conda at least, since that's where most of the more expensive installs are going to be.

another thought here: in the short term we could capture this purely with documentation. E.g. add a section to the docs like:
Decoupling your environment from the written content
If your environment takes a long time to build, you may wish to de-couple it from the content
that is inside the environment. For example, just because you fix a type-o in your code doesn't
mean you want to re-trigger a 3 hour build process.
For this case, we recommend using two repositories. One repository to contain your content
(e.g. Jupyter Notebooks, R scripts, etc), the other to define your environment (e.g. containing
an environment.yml file). In this case, make sure to include a line in your "environment"
repository's postBuild file that fetches the latest version of your content. In this way, you can
modify the content without re-building the environment each time.

I would be extremely hesitant to recommend that workflow to anyone, since
it sounds like a temporary workaround we'll be stuck with forever. Also
there's no guarantee that we can make that it will not actually trigger a
build process, so it might be all for nought.
From the design docs, we want each image to accurately and fully capture a
git commit. This might mean we can never really fully separate environment
from contents, since often those are indistinguishable. There might be
specific subsets where we can optimize this (such as requirements.txt that
doesn't reference anything local, or an environment.yml file that's
similar), so we should open specific issues about those.
On Tue, Apr 24, 2018 at 4:36 PM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

another thought here: in the short term we could capture this purely with
documentation. E.g. add a section to the docs like:
Decoupling your environment from the written content
If your environment takes a long time to build, you may wish to de-couple
it from the content
that is inside the environment. For example, just because you fix a type-o
in your code doesn't
mean you want to re-trigger a 3 hour build process.
For this case, we recommend using two repositories. One repository to
contain your content
(e.g. Jupyter Notebooks, R scripts, etc), the other to define your
environment (e.g. containing
an environment.yml file). In this case, make sure to include a line in
your "environment"
repository's postBuild file that fetches the latest version of your
content. In this way, you can
modify the content without re-building the environment each time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/repo2docker/issues/115#issuecomment-384113384,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB23ontNEaFOjoSR0biupi2qK2SDRR-ks5tr7bngaJpZM4QE8ah
.

--
Yuvi Panda T
http://yuvi.in/blog

what if in that language we explicitly say something like "this is a hacky solution that may break in the future, but may solve your problem now"? I'm mostly just trying to give people a friendly suggestion as opposed to an "official workflow"

In this case, make sure to include a line in your "environment"
repository's postBuild file that fetches the latest version of your content.

This means we won't actually solve any problems. postBuild is only run on
build time, so this freezes the content repo as it at the time the
'environment' repo was built. Any changes to the postBuild to try to
trigger a rebuild will rebuild the whole environment too, so you haven't
solved any problems.
If you want to avoid rebuilds, point to a commit hash or master. I think
that's good long term practice too, so perhaps we should put that instead
in our docs?
On Tue, Apr 24, 2018 at 5:25 PM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

what if in that language we explicitly say something like "this is a hacky
solution that may break in the future, but may solve your problem now"? I'm
mostly just trying to give people a friendly suggestion as opposed to an
"official workflow"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/repo2docker/issues/115#issuecomment-384121653,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB23pNp6gSFYEkI-KWGTJo6Xa5zsRsGks5tr8J6gaJpZM4QE8ah
.

--
Yuvi Panda T
http://yuvi.in/blog

ah that's a good point - I got confused about which file I thought could be used to solve this :-)
What I meant to say was that we could do this with preStart (#196) ...since that code would be run every time a session started, it could be used to decouple the two

@betatim's work in PRs like https://github.com/jupyter/repo2docker/pull/716 and @minrk's work in https://github.com/jupyter/repo2docker/pull/743 fix this I think.


Multi-Core link

Does the link.py support multi core link?

Please do not abuse the issues system with random questions. :(

Have you understood my question?

Do you understand that github issues are a bug reporting system, not a technical support forum?

Thank you


language

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
[Description of the issue]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
i am a persian developer .there is many developers like me . but this project dosnt support persian language so good . please improve this ability

Thank you for contributing!
We require the issue template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests. Please open a new issue and fill out the template for us.
Thanks for understanding and meeting us half way :grinning:


Official support for development backend

Feature Description
~Allow an on/off for configured file-system registered backend.~
Allow for a development backend configuration.
Describe the solution you'd like
A ~toggle~ visual identifier at the top of the page when:

~file-system is registered (or local-backend)~
dev-backend (optional) exists with same requirements as backend
process.env.NODE_ENV === 'development'

The way it would work
Once the ~toggle~ config exists it would default to the devopment backend. Gives a visual signal that you are going to the development backend (TBD).
Thoughts
Describe alternatives you've considered
Was mentioned to have a new configuration section. ~I don't think this is needed when a simple identification is all that is needed and a sub section can be applied to the config under backend for a fs backend that requires more config or options netlify-cms requires.~
After discussion, this makes more sense, because there should not be a difference between a dev backend and a production backend other than it's own config. The configuration would serve the purpose of allowing the cms to use the dev backend when in development (process.env.NODE_ENV === 'development') mode.
The development backend could be any backend configuration (file-system, github dev branch, or other) and it would have it's own requirement for an api endpoint.
Additional context
This solution solves the need for having to worry about supporting just one fs backend solution, but anyone could just add their own and it would be supported. There is also no need to worry about the api solution, since it would be handled by the registered library solution (backend) and project configuration.
Note: A default development backend config allows for a no code solution that will be the first step to #2335

I have changed my initial thoughts on this and agree that having a default dev backend configuration can be a simple solution to the development workflow rather than requiring to use code to change out the backend by extending the CMS. Although, the change would not take away the ability to extend the power of being able to extend the backend config using code if so desired. This solution gives the non technical user the ability to configure an alternative backend to be used during the development stage (without requiring any code).


Variable case sensitivity option

Description
Provides the user the ability to specify the case sensitivity of the calculation engine by passing a bool into the CalculationEngine constructor similar to how caching and optimization are controlled.
The default behavior is maintained by electing to be case insensitive by default.
Fixes #35 related to performance when forcing case insensitive evaluations.
Testing

Updated all existing tests to ensure functionality remained intact
Added two tests to verify correctly cased version of variable was selected in all modes.
Added two tests to ensure that when only mixed case variable is defined engine operated as expected in all modes.

Benchmarking
Jace.NET Benchmark Application

--------------------
Function: 2+3*7/23
Number Of Tests: 1,000,000

Interpreted Mode:
Total duration: 00:00:01.6416091
Interpreted Mode(Case Sensitive):
Total duration: 00:00:00.7719340
Compiled Mode:
Total duration: 00:00:01.3015149
Compiled Mode(Case Sensitive):
Total duration: 00:00:00.6403131
--------------------
Function: (var1 + var2 * 3)/(2+3) - something
Number Of Tests: 1,000,000

Interpreted Mode:
Total duration: 00:00:07.2805178
Interpreted Mode(Case Sensitive):
Total duration: 00:00:05.6568951
Compiled Mode:
Total duration: 00:00:06.2263400
Compiled Mode(Case Sensitive):
Total duration: 00:00:04.4839689
--------------------
Random Generated Functions: 10,000
Number Of Variables Of Each Function: 3
Number Of Executions For Each Function: 1,000
Total Number Of Executions: 10,000,000
Parallel: True

Interpreted Mode:
Total duration: 00:00:31.7136317
Interpreted Mode(Case Sensitive):
Total duration: 00:00:23.6118180
Compiled Mode:
Total duration: 00:00:32.5888003
Compiled Mode(Case Sensitive):
Total duration: 00:00:24.7407965
Press enter to exit...

Test 1:
    Interpreted: 52.98% Speed up when operating as case sensitive
    Compiled: 50.80% Speed up when operating as case sensitive
Test 2:
    Interpreted: 22.3% Speed up when operating as case sensitive
    Compiled: 27.98% Speed up when operating as case sensitive
Test 3:
    Interpreted: 25.55% Speed up when operating as case sensitive
    Compiled: 24.08% Speed up when operating as case sensitive

This is awesome, thanks @vandersmissenc !!
@pieterderycke Would it be possible to get a point release out including these changes soon? I'd prefer to keep working off of the official nuget packages if possible.

I plan to release a new update to Jace in the coming weeks. This feature will be part of it. Thanks for the pull. I look this evening into it.


imageCache: avoid pendingImage memleak

It is possible that pendingImage listener was not removed from the pendingImage:
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/painting/image_cache.dart#L431
because the pendingImages list was emptied in the meantime:
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/painting/image_cache.dart#L197
This is a proposal to fix the issue:
#93535
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[ ] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] All existing and new tests are passing.

@michalkucharczyk  Can you please sign the CLA (see https://github.com/flutter/flutter/pull/93543/checks?check_run_id=4189933190 for help)?
Also, it looks like this change is breaking a lot of tests. Can you take a look at those?
Lastly, this change is also missing tests to ensure that we never regress this. Can you please add some? Thanks!

(triage) Hi @michalkucharczyk would you like to continue with this change?

I will not continue with this PR. I think this approach is not correct, refer to: https://github.com/flutter/flutter/issues/93535#issuecomment-975568605


[azure-cli-ml] Update version to 1.13.0

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/j-so/azure-cli-extensions.git@jenns/azml_1_13_0#subdirectory=src/$EXT&egg=$EXT"

The error is with checksum in aks-preview. This PR does not touch that section at all.

/azp run


Please fix dependencies description in README.rst

README.rst says it depends on 'responses', but only tests depend on 'responses'.
'tox' is also only required optionally. README.rst should be clear about this.

Thanks for the feedback. I have modified the README. Hopefully it is clearer now.


Add Kerbal heatshield from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of xdthegreat, to add Kerbal heatshield to CKAN.
Mod details:
name = /mod/1925/Kerbal%20heatshield
author = xdthegreat
abstract = A heatshield for EVA kerbals
license = CC-BY-SA 2.0
Homepage = https://forum.kerbalspaceprogram.com/index.php?/topic/177240-14x-kerbal-heatshield/
description = A heatshield for kerbals. Useful for collecting EVA reports inthe  upper atmosphere, or for incinerating kerbals.
Please direct questions about this pull request to xdthegreat.

This was added in #6686.


Migrate to setup.cfg

TIL: https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files
(Thanks https://gitlab.com/librespacefoundation/satnogs/satnogs-client/!)

Closed in #613


move to es2015 modules

Coverage increased (+0.07%) to 92.965% when pulling 5866f1fe7f8e019cdfbadf7356103c1a55c729b1 on es2015-modules into 727cc6d705c6c916ea89ee4ef0d16a6779b404ca on master.

Coverage increased (+0.07%) to 92.965% when pulling 3a9d3d2b5771b78ecc180cd3e9c31e978017bb55 on es2015-modules into 727cc6d705c6c916ea89ee4ef0d16a6779b404ca on master.


Add Laravel 6, 7 and 8 support

Fixed push method and test
Removed composer.lock

In MedianTest.php I had to disable PHPStan on a couple of lines due to the inconsistencies between the Laravel versions.


Renaming before next deployment

Tests pass, and @ericdill is
databroker -> dataportal
muggler -> muxer

Looks good


[Bug]: Embedding request is sent regardless of entry acceptance

What happened?
If an insertion has an ID which is already in the DB, the insertion would be skipped, but API request for generating embedding is still in place causing wasted time, traffic and money.
Also there is logging to stderr (with duplications) for skipped entries.
Versions
Chroma 0.4.18
Python 3.10.13
macOS 12.7.1
OpenAI

Hey @azhuchkov, this is expected behaviour. The embeddings happen before any data modifications on the client side, and the client does not know whether the IDs to add exist or not.
Chroma will eventually support server-side embeddings, which will tackle this very problem. For now, the way to solve your problem is to use upsert, which will overwrite any existing entries.


Fix for #36 - message_precedence_codes - different enums for C and D1

Updated values for this field in rev C test files to use the rev C enum mappings:
Routine to Reserved_0
Immediate to Emergency
FlashOverride to Flash
Bumped version number in build.sbt
Reserved_0 causes a validation error. Added this as an expected validation error in the test case.
https://github.com/DFDLSchemas/mil-std-2045/issues/36

This looks great.
Squash together into 1 commit, rebase on top of latest dev (I think. I am not sure why but github thinks you have conflicting changes in build.sbt) then force push back to this branch.
Then it can be merged (ideally rebased) from here onto the dev branch. You don't have to wait for me to do this. I've already completed review.
Send me a Teams messages when this is done so I can update to this.


Update connect-from-azure.md

The service principal does not need full contributor rights on the subscription itself. Documentation needs to clarify that it's possible to assign contributor rights to the resources (i.e. resource group) for the service principal to perform actions. Ideally we will apply the principle of least privilege when granting permissions.

Hi @juliakm - Is this a PR you can review? (It looks like the metadata needs to be updated for author.) Note that "resource" has a misspelling.
Thanks!

@ktoliver - I don't have ability to approve the PR. I believe @mijacobs does, or will know who can approve.

Any updates on this? Thanks!

@juliakm or @N-Usha , can one of you take a look at this PR and approve it?

I think that the current text is correct because active directory applications are tied to a subscription (Article: assign a role to the application). I'll confirm this with the product team.


In CNS page: filter by location- hide locations with no Monitors

Is your feature request related to a problem? Please describe.
In the CNS page, when filtering by location, I can see all locations within the facility. This is not useful since only a few of these facilities may have 5-para monitors deployed in.
Describe the solution you'd like
https://care.coronasafe.in/facility/0c95c7f0-e1d2-4aff-83fa-933cef60d3a8/cns

[ ] In the filter by location option, remove all locations with no monitors registered. Every monitor registered is linked to a bed within a location (https://care.coronasafe.in/facility/b87b1396-631b-4306-bf33-3022bec0a5a5/assets/3297fee3-3872-4a3a-99ab-367876458267/configure)

[ ] Disable the filter by location option if only 1 location has monitors deployed

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I would like to work on this issue

@rithviknishad May I contribute to this issue?

@bodhish Keeping the issue open since BE has to be reviewed/merged yet (at the moment, FE changes would make no difference).

Missed that while checking the PR;


Fixed nightly build failure in cache tests

Cache tests fail when the jenkins server run them with --master flag. This will fix the error by removing the flag. Further investigation is needed to know why it fails with the flag it's being tracked in #2203.
Signed-off-by: Raza Jafri<EMAIL_ADDRESS>

no, I don't want to check by removing master here... figure out what is wrong or just revert the change.

no, I don't want to check by removing master here... figure out what is wrong or just revert the change.
it would be confusing to run this test differently then the rest of the tests.

reverting until I narrow down this problem https://github.com/NVIDIA/spark-rapids/pull/2208

note changes were reverted in https://github.com/NVIDIA/spark-rapids/pull/2208/files

This will be ready after #2227 is merged

build


added code of conduct to the project

Overview
PR Checklist

[ ] Related to Abstract designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

Description

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

Hey @jivthesh, thanks for sending this! We haven't decided on a particular code of conduct for this repository so we can't accept this PR just yet. To be honest we aren't actively seeking open source contributions on it, as we're still working on overhauling large parts of what's exported here frequently enough to strongly inconvenience anybody trying to use it.
If you're interested in workin on Codecademy open source things (which is wonderful!), you might enjoy some of our other open sourced frontend repos:

https://github.com/Codecademy/mock-react-redux
https://github.com/Codecademy/console-fail-test
https://github.com/Codecademy/40Phaser

Also! It looks like you've been sending equivalent PRs to other repos that don't yet have code of conduct files. That's great and I really admire your initiative in pushing for a more inclusive open source world. Thank you! 💖


alvr crash when reopen the alvr app immediately after exiting  on quest

The carsh message indicates the ANDROID_CONTEXT have not been released when app exiting, the asset assert!(previous.is_none()) is failed!
It seems like we never call release_android_context

Thanks for the report. This is low priority for now. It's going to be a bit hard to handle this bug.


Activity view hover comes and goes without moving mouse

When I click on the GH view (when it has not yet loaded in the session), I get the hover come and go many times:

//cc @Tyriar

Seems the activity on the entry is causing the problem here.

It is because, I am listening to mouse leave event on the container and hiding it. But when there is activity on the container, we update the activity by hiding and showing it. This is causing the mouse leave event whenever badge is hidden and mouse hover event whenever badge is shown.
Fixed it, by hiding the hover only when mouse leave event target is the container. This fixes the flickering of the hover when the activity is getting updated.
One loose end which is not covered in this fix is following:
https://user-images.githubusercontent.com/10746682/209936043-a86f7617-a401-4d0e-bb00-df918ff03b3b.mp4
Hover appears at the end because the badge is shown that triggers mouse over event. It seems the root cause here is hover getting hidden by the hover widget when clicking on the activity bar icon.

So the original issue still reproduces for me, what was fixed?

On Windows it's hiding on click for me which seems fine.

Before, the hover keeps reappearing whenever the activity is updated. So before as soon as you click the hover disappear and appear because activity is updated and it might also flickers if the activity keeps updating.
This is fixed now. But due to the following limitation hover reappear at the end.

Hover appears at the end because the badge is shown that triggers mouse over event. It seems the root cause here is hover getting hidden by the hover widget when clicking on the activity bar icon.

Ok, I think it is better from what I recall compared to how it was.


ObserverSpy swallows errors

Describe the bug
A clear and concise description of what the bug is.
When an error is thrown unexpectedly, the error method on the ObserverSpy catches it and basically "hides" it from the user.
And by that making debugging an unexpected error much more difficult.
To Reproduce
Steps to reproduce the behavior:

throw an error in an observable
See no trace of it in the logs

Expected behavior
We should be able to configure the observer spy (on creation or via subscribeSpyTo) to flag whether an error is expected or not.
The default should be that the error is not expected and should be re-thrown so it would be shown in the console.

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Nvidia GPU support?

Hi,
Does anyone know if it's at all possible to install the nvidia drivers + nvidia-container-runtime such that I might be able to use the GPU from docker containers?
It seems there's some old stuff in the rancher repos:

https://github.com/rancher/os-services/tree/master/n
https://github.com/rancher/os/issues/1637

But it's quite hard to figure out how much of that is still relevant since some comments suggests "runtime isn't required anymore, the nvidia gpu support is baked into Docker 19.03"
So if anyone could point me in the right direction I'd be grateful.
Thanks in advance.

@PrplHaz4 Based on https://github.com/burmilla/os/issues/6#issuecomment-726827495 you might have some useful feedback to this one?

Hi,
Does anyone know if it's at all possible to install the nvidia drivers + nvidia-container-runtime such that I might be able to use the GPU from docker containers?

This would be a really hard task to do it in a professionally usable way.
Putting my Linux kernel maintainer hat on:

proprietary drivers (especially those from Nvidia, who spend a great deal of work into code obfuscation!) can never be stable.
there're just too many factors influencing binary compatibility (no, the wrappers provided as source code DO NOT solve that problem) - the binaries need to fit exactly to specific kernel versions and configurations / builds.
the linux kernel's driver APIs are by definition internals of the kernel, they change very frequently (with virtually each version) and never have been supposed to support anything near to binary compatiblity. This is not just about data structures and function prototypes, but also higher level semantics. Drivers just need to be developed along with the kernel itself.
the nvidia drivers tend to bypass fundamental subsystems and there is no documentation whatsoever
their modules (even with their "gpl-condome") are still a piece of the kernel itself, therefore Nvidia breaks the Kernel's License (GPL), thus using them is at least leggally very doubtful
kernel modules and userland need to fit exactly to each other, for containers that means you need the SAME driver package version (and the SAME cpu arch) in both host and container.
trying to add these binaries to an highly customized distro like rancheros/burmilla is a complicated job, that has to be repeated with each new driver version, as well as each new kernel version. anyone bored enough to spend weeks and month of spare time on that ?
the driver is magnitudes bigger than the whole operating system -- no way to audit that.
NVidia has always been that way, since 25 years. They (at least the GPU branch) always have been hostile to the kernel community and the design decisions. No indication that they will change within the next 25 years.
DONT BUY NVIDIA. Period.

It seems there's some old stuff in the rancher repos:

https://github.com/rancher/os-services/tree/master/n
rancher#1637

Obviously, nobody managed to come up with something practically useful.
(Assuming we're talking about professional environments, not child toys :p)

But it's quite hard to figure out how much of that is still relevant since some comments suggests "runtime isn't required anymore, the nvidia gpu support is baked into Docker 19.03"

Just had a look at the source code. All they added is calling some external binary (closed-source and untrusted) that
does some whatever vodoo to dig holes into the container isolation, so the workloads can access this proprietary,
non-standard gpu driver. And the code comments make clear that this is just a dirty hack that doesn't belong there.
Use on your own risk.
All the problems I've mentioned above remain unsolved.
Don't trust a tainted kernel. It's broken and compromised.
--mtx

Since I only needed it for a HW transcoding in my homelab setting with Jellyfin I ended up running the GPU in a separate VM with arch linux and forwarding the ffmpeg commands using https://github.com/joshuaboniface/rffmpeg.
I'm not interested in philosophical debates about not buying nvidia since in many cases it's your only choice, fx AI/ML, so I'm closing this issue.
If anyone comes up with a solution please feel free to reopen.


Doc Feedback: This doc is not up to date

Location : https://apim.docs.wso2.com/en/latest/deploy-and-publish/deploy-on-gateway/deploy-api/deploy-through-multiple-api-gateways/

@bhathiya , can you please confirm whether the entire page is outdated or whether only a certain section is outdated.

We need to validate the entire doc.

Bhathiya mentioned today that Rashmin has started looking into this issue.

@rashm1n, please confirm whether this issue can be closed.

@Mariangela I don't see any updates on the page.

@rashm1n , please send your fix to the 4.0.0 branch as well, so that your change will appear in the latest APIM 4.0.0 docs.

@Mariangela . Ack. Will send a fix.

@rashm1n , please address the comments that I have added in [1]
[1] https://github.com/wso2/docs-apim/pull/4369

@rashm1n , pls note the following

Step 1 width heigh ratio is not correct. Only define the width as a percentage to avoid image distortion.
-- No 8 second image
-- No9 image
-- No 10 second image

Step 2 image is too large

@Mariangela issues have been fixed.

Some images are shrunk horizontally. Please check.

Some images are shrunk horizontally. Please check.

@bhathiya the changes are not yet merged. This certain issue was fixed in the last commit.

@bhathiya , please confirm if we can close this issue.

+1.


CI: label a pull request breaksapi if there are changes on the wasm source code but no changes to the spec_version

https://github.com/paritytech/scripts/commit/370a02d2c6cc6404ad9154ecb0c8b1ed72214614


Update scalafmt-cli_2.13, scalafmt-core to 3.8.0

About this PR
📦 Updates

org.scalameta:scalafmt-cli_2.13
org.scalameta:scalafmt-core

from 3.7.17 to 3.8.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (3.7.17).
You might want to review and update them manually.
website/docs/reference/cli-options.md
website/docs/reference/scala-command/cli-options.md
website/docs/reference/scala-command/runner-specification.md
website/docs/release_notes.md

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:n:3

Closing this, we'll bump to the next scalafmt version.


How to add comments in ef core code first?

I want to add some comments on field and when update database this comments can be add in db via create script, how can I do it?

Putting this on the backlog for built-in support. See also #10258, which is about making it easier to flow information from the model into Migrations,.

This looks like a duplicate of #15037?

Thanks @Muppets. Closing this as a duplicate.


Fixed priceTax attribute not updating.

When calling Cart::setTax() or setTaxRate on the CartItem object, the
new priceTax is not updated to reflect the new tax rate. The total()
method then does not have the correct total.

@denisrpriebe I wrote a test just to see if this was the case, though my tests pass just fine when toggling between Tax rates. I get the right total on the CartItem and Cart.
Can you give a detailed example where this would fail, with tests to back this up?

Thanks @peterquentin This was indeed something I forgot to ask. Would be nice if we have a test that would show what this PR actually fixes.

@peterquentin @Crinsane I should have some time later next week to write a test. Thanks.


[BUG] Legend position covered by chart itself?

Expected Behavior
Chart and legend not colliding.
Current Behavior
Chart and legend are colliding. Resulting in some data points being hidden behind legend.

Possible Solution
I understand there is an option to put the legend in the bottom and left and right, but I would like to keep it on top
Steps to Reproduce (for bugs)

Create a chart?

Context
Environment

Chart.js version: 2.7.1
Browser name and version: Chrome / Opera
Link to your project: N/A

Duplicate of #4790


Invalid prop style of type array supplied to Text , expected Number

Description
I am trying to create a common component for all buttons in my react-native app. I have created base set of styles and pass styles are props to override default when required.
But while overriding text, it is giving me warning "Invalid prop style of type array supplied to Text , expected Number".
This however works fine in case of view. Ideally this should work right?
Reproduction
<Text style={[styles.caption,this.props.style]}>{caption.toUpperCase()}</Text>
const styles = StyleSheet.create({
  "caption": {
    "fontSize": 18,
    "color": "white"
  }
});

Additional Information

React Native version: 0.38.1
Platform: ios
Operating System: MAc

I don't think this is a problem in new versions of RN. Can you check on RN 0.42 and re-open the issue if it is still a problem? Also, can you include the entire code snippet that will cause the error to happen?

I've the same problem with RN 0.42. Can you please re-open the issue?

I havent tried it yet as was occupied in other projects. Will open the issue based on your feedback @lihue

Had the same issue. Try doing this to avoid the error:
<Text style={{...styles.caption, ...this.props.style}}>{caption.toUpperCase()}
It's complaining about receiving an array.. so why not pass it a merged object of both styles?


Side Drag slide menu

I would like to have the slide menu only draged by edges instead of the whole content page

ionic has the setting for edge drag....
How do I implement this.
BTW. I love this package!!!
Sincerely,
txs

Hi @txs i'm not sure if this issue was open by mistake (since its the same as the https://github.com/meteoric/meteor-ionic/issues/134) :) But to help you out quickly, did you took a look at this and this - dragger? You can just set up "draggable" element that will listen for swipe. As @nickw told you meteoric is using snap.js for all of this. Let me know if you need any help :)

Thanks... I think I'll find another package for the floating slide menu.... thanks for the help out
Sincerely,
Andy

I came back to use this mend  do you know how to apply the effect  like material  design...  The hover menu or perspective page view

Hey! Well you have a lot of options there :) there is https://github.com/zachsoft/Ionic-Material package (requires bower or play around with raw CSS) or you can one of many meteor packages from atmosphere just search for material.

Any updates on this? Or if someone can tell me how to apply snap.js options on the meteoric sideMenu??

Here's where snap.js gets initialized: https://github.com/meteoric/meteor-ionic/blob/master/components/ionSideMenuContainer/ionSideMenuContainer.js#L14-L36
You can't currently pass any other options to it, but that should be pretty trivial to implement if you'd like to submit a PR. Alternatively you might be able to grab the element out of the DOM and apply options retroactively - not sure if snap.js supports that or not though.

I actually write my own so that the side drag is possible!
On Sat, Aug 29, 2015 at 2:38 AM, Nick Wientge<EMAIL_ADDRESS>wrote:

Here's where snap.js gets initialized:
https://github.com/meteoric/meteor-ionic/blob/master/components/ionSideMenuContainer/ionSideMenuContainer.js#L14-L36
You can't currently pass any other options to it, but that should be
pretty trivial to implement if you'd like to submit a PR. Alternatively you
might be able to grab the element out of the DOM and apply options
retroactively - not sure if snap.js supports that or not though.
—
Reply to this email directly or view it on GitHub
https://github.com/meteoric/meteor-ionic/issues/135#issuecomment-135856397
.

It worked @nickw, thanks.


Implement std::thread-like wrappers around Furi Thread APIs

Rebased on current main.

Force-pushed to fix thread memory freeing and add Builder::enable_heap_trace.

Force-pushed to add logging around the thread waiter logic.

Force-pushed to bump the pinned nightly to one where Arc::into_inner is stabilized.

Force-pushed to use sys::c_string!() instead of manually crafting the log messages for the thread waiter.


[BugFix] enhance analyse for percentile_approx

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Problem Summary(Required) ：
some wrong sql like below will make be crash, so add check in analyse
mysql> select percentile_approx(2.25,'abc');
ERROR 1064 (HY000): Internal error: std::get: wrong index for variant
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 9 / 13 (69.23%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/FunctionAnalyzer.java
9
13
69.23%
[155, 156, 171, 172]

[FE PR Coverage Check]
:disappointed: fail : 9 / 13 (69.23%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/FunctionAnalyzer.java
9
13
69.23%
[155, 156, 171, 172]

[FE PR Coverage Check]
:disappointed: fail : 9 / 13 (69.23%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/FunctionAnalyzer.java
9
13
69.23%
[155, 156, 171, 172]

[FE PR Coverage Check]
:disappointed: fail : 9 / 13 (69.23%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/FunctionAnalyzer.java
9
13
69.23%
[155, 156, 171, 172]

[FE PR Coverage Check]
:heart_eyes: pass : 9 / 9 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/FunctionAnalyzer.java
9
9
100.00%
[]

@Mergifyio backport branch-3.0


Performance test

Closes https://github.com/api3dao/signed-api/issues/40
Rationale
Used https://pool.nodary.io/ as an API and created a small script that uses all endpoints from https://pool.nodary.io/<AIRNODE> and treats them as different dAPIs.
There are ~25 different Airnodes, each has ~100 beacons giving an upper limit of ~2500 for perf test. I immediately noticed I am rate limited so I deployed a bunch of cloud workers to avoid sending requests from a single URL (which worked).
Results overview

For our expected load want to use:

Signed API => cpu=512, mem=1024
Airnode feed => cpu=2048, mem=4096

The cost of logging is negligible.
Both services are CPU bound.
I noticed Signed API latency issues (requests taking seconds to complete) but it was caused by network roundtrips because I deployed the services in US.
Logs were quite usable.

Details
I deployed everything on us-east-1 or us-east-2 with one exception at the end when I debugged the latency issues of Signed API.
~2500 dAPIs across 25 triggers each with 60s fetchInterval
cpu=256, mem=512, logLevel=debug
Airnode feed

Signed API

cpu=512, mem=1024, logLevel=debug
Airnode feed

Signed API

cpu=512, mem=1024, logLevel=warn
Airnode feed

Signed API

cpu=1024, mem=2048, logLevel=warn
Airnode feed

Signed API

The stats are looking OK on this machines, but Signed API is slow, requests take ~5s, response size is ~1MB. Half of requests fail with 502 error.
cpu=2048, mem=4096, logLevel=warn
Airnode feed

Signed API

"Only" 1/4 of requests fail with 502, it seems the bottleneck is somewhere else. I also redeployed using logLevel debug and the results were similar - so the cost of logging is negligible.
399 dAPIs across 4 triggers each with 60s fetchInterval
cpu=2048, mem=4096, logLevel=debug
Airnode feed

Signed API

All request successful, response time is ~200ms (but ~120 is inherent latency).
cpu=256, mem=512, logLevel=debug
Airnode feed

Signed API

1/4 requests fail, some requests take ~500ms and some ~5s. Probably depends on whether the machine is processing something or not.
cpu=512, mem=1024, logLevel=debug
Airnode feed

Signed API

30 request, delay between them 1s:

Success: 29, error: 1
Min time:<PHONE_NUMBER>851074
Max time: 4470.1671669483185
Average time: 2168.4711624145507 (this is not nice)

399 dAPIs across 4 triggers each with 1s fetchInterval
cpu=512, mem=1024, logLevel=debug
Airnode feed

Signed API

Request stats:

Success: 29, Fail: 1
Min time:<PHONE_NUMBER>970917
Max time: 3341.9595420360565
Average time: 1702.8893277486166

cpu=2048, mem=4096, logLevel=debug
Airnode feed

Signed API

Weaker machines were causing 100% CPU in Airnode feed. Request stats:

Success: 30, Fail: 0
Min time:<PHONE_NUMBER>188904
Max time: 2912.6059169769287
Average time: 1079.9902278343836 (this is not nice)

cpu=8192, mem=16384, logLevel=debug
Signed API

Redeployed just the Signed API to see if bigger machine helps. Stats:

Success: 30, Fail: 0
Min time:<PHONE_NUMBER>124451
Max time: 1726.8410420417786
Average time: 1054.997409717242

Debugging the Signed API latency
From AWS logs the server spends ~50ms processing the query. I run smaller Airnode feed (40 dAPIs) decreased the response payload to 15kb (from 180kb) and request times were stable, around ~180ms which was expected. I suspected this is all caused by a combination of network distance and response payload.
I confirmed the hypothesis by deploying Signed API (512cpu, 1024mem) on Europe. This should not be an issue in prod, because we will use CDN over the signed API. Stats:

Success: 30, Fail: 0
Min time: 98.72512499988079
Max time: 2730.293709002435
Median time:<PHONE_NUMBER>0142622
Average time:<PHONE_NUMBER>672915

I ran the script a bit longer and out of 2000 calls only 2 failed. The singed API CPU and memory was stable

Thanks, interesting data. It's surprising that CPU is that much of a bottleneck for Airnode (though the number of triggers is a bit low). Fortunately, Airnode can be scaled linearly by simply deploying more of them (and the same applies to signed APIs, API providers deploying their own distributes the load in a natural way, and we can put ours behind a sort of a load balancer). We must find out the limits of a single instance first though.

For our expected load

I'm not sure what you refer to as the expected load. I would look at the following.

25 Airnodes, 300 Beacons each, one trigger per Beacon, 1s fetch interval (APIs don't support batching and ideal specs)

25 Airnodes, 300 Beacons each, one trigger per 100 Beacons, 1s fetch interval (APIs are nicely batchable and ideal specs)

25 Airnodes, 300 Beacons each, one trigger per Beacon, 5s fetch interval (APIs don't support batching and relaxed specs)

25 Airnodes, 300 Beacons each, one trigger per 100 Beacons, 5s fetch interval (APIs are nicely batchable and relaxed specs)

We should have headroom in both the number of Airnodes and the number of Beacons per Airnode, 100 Beacons is potentially on the low side. Similarly, 25 triggers is not necessarily the upper limit. Even the best machine configuration will probably fail to perform well in the most pessimistic scenario, in which case we can adjust the specs.

It's not clear to me what you mean by a dAPI, Airnode and signed API only cares about Beacons

I mean beacons

Context update
The bottleneck mentioned in this comment is signed data verification, which takes 2-3ms. That doesn't scale with the number of API calls we want signed API to handle.
We discussed possible options internally, but in the meantime I continued doing performance tests with the verification in Signed API removed (which has good performance).
Because the Signed API is currently without authentication and signed data verification, there is not much point in stress testing it in current state (although the added auth should be lightweight and the result should have similar perf). We agreed to wrap up the performance test and focus on different Airnode feed scenarios. So here are the results.
Results
Airnode feed (cpu=2048, mem=4096), 300 beacons, 1s fetchInterval, no batching

Smaller machine results in 100% CPU. As a note, the target signed API without verification (cpu=1024, mem=2048) was 12% cpu, 6% mem. This scaled linearly with the number of Airnode feeds deployed.
Airnode feed (cpu=1024, mem=2048), 300 beacons, 5s fetchInterval, no batching

I also tried to deploy cpu=512, mem=1024 but the result was 100% cpu (and it never went down).
Airnode feed (cpu=1024, mem=2048), 100 beacons, 1s fetchInterval, no batching

Airnode feed (cpu=512, mem=1024), 100 beacons, 5s fetchInterval, no batching

Airnode feed (cpu=1024, mem=2048), 300 beacons, 1s fetchInterval, batched per 100 (3 triggers)

As a note, increase to 400 beacons ends up with 100% CPU. I also did a similar test with 300 beacons yesterday with not so optimal Signed API (larger responses and that had 100% CPU as well).
Airnode feed (cpu=1024, mem=2048), 100 beacons, 1s fetchInterval, batched per 100 (1 triggers)

Airnode feed (cpu=1024, mem=2048), 100 beacons, 1s fetchInterval, batched per 100 (1 triggers)

Final notes

I used Signed API (cpu=2048, mem=4096) as a data source for Airnode feed with no batching and 300 requests per second. The Signed data served large responses (300 signed datas) was killed with fatal error and restarted shortly by AWS. FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory. I updated the machine to (cpu=2048, mem=16384) and it failed with a different error Error: write ENOBUFS for which I found limited information.
When scaling the machine with higher memory it's very important to set --max-old-space-size (node heap size) and set it to ~70% of the host machine memory. The default limit of node is 4GB making larger host machine useless.


Remove bintray warning

Overview
Removes distracting bintray warning.
Demo
Before:
$ ./scripts/console api-server './sbt'
Starting vagrant_postgres_1
[info] Loading project definition from /opt/raster-foundry/app-backend/project
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
Missing bintray credentials /root/.bintray/.credentials. Some bintray features depend on this.
[info] Set current project to rf-backend (in build file:/opt/raster-foundry/app-backend/)
root >

After:
$ ./scripts/console api-server './sbt'
[info] Loading project definition from /opt/raster-foundry/app-backend/project
[info] Set current project to rf-backend (in build file:/opt/raster-foundry/app-backend/)
root >

Notes
Controversial storing empty credentials in the repo. What if we ever need to use real ones?
I think the reduction in noise is worth it.
Testing Instructions

Check out this branch.
Open the sbt console. Ensure you don't see any bintray messages.

Also tagging @hectcastro who may have relevant opinions / alternatives

Thanks for taking a look!


ionic iOS app stuck on Splash screen

Hi,
I have created my ionic v6 mobile app installing  cordova-plugin-ionic-webview and when I try to run the app on my device, the app getting stuck on splash screen and no errors are logging. After I remove the plugin and retry it, it works fine. But my app couldn't submit to AppStore due to the UIWebView issue.

Update splash screen plugin using the link https://ionicframework.com/docs/native/splash-screen
This fixed same issue for me.

This fixed same issue for me.

hi,
I tried this and still having same issue

I have solved the issue by running the below commands to my project directory:
npm install
sudo gem install cocoapods
pod repo update
ionic cordova platform add<EMAIL_ADDRESS>cordova plugin update cordova-plugin-ionic-webview@latest
then I add the following to my config.xml under ios platform
<feature name="CDVWKWebViewEngine">
<param name="ios-package" value="CDVWKWebViewEngine" />
</feature>
<preference name="CordovaWebViewEngine" value="CDVWKWebViewEngine" />

do not add
the again in project directory,
ionic cordova prepare ios
cordova build ios

@prabhashibuddhima
I did follow the above steps but still, my screen was stuck on the splash screen.
Can you please share any other solutions?
Thanks

I'm facing the same problem here, and even after do all the steps metioned by @prabhashibuddhima. stucked on splashscreen

i am facing same issue. tried everything , none of them work. did anyone solve it?

@Hassan-Shahriar-1 I have same issue, do you have any fix worked for your issue?

If you have this Issue using Firebase Authentication, this will probably fix it:
https://youtu.be/U7RvTTF9dnk?t=2182
https://stackoverflow.com/questions/71062347/how-to-write-authguard-in-ionic-angular-with-angularfire7-that-works-on-ios
In your app.module.ts
change:
provideAuth(() => getAuth()),
to:
   provideAuth(() => {       if (Capacitor.isNativePlatform()) {         return initializeAuth(getApp(), {           persistence: indexedDBLocalPersistence,         });       } else {         return getAuth();       }     }),


allow to load pretrained weights when the include_top variable is False

This merge request is related to the bug #278
The class initialization is failed when called using from_pretrained(..,  include_top=False) function or when the number of classes is not equal to 1000, i.e. from_pretrained(.., num_classes=100).
This pull request allow to load the pre-trained weights even when the number of classes is not equal to 1000 or when the top classifier is ignored.
_fc.weight and _fc.bias will only be loaded when include_top=True and num_classes=1000 (default values)

Why hasn't this been merged yet? A simple solution to a problem affecting many users.


linux-intel: replace CAN config with KERNEL_FEATURES

Yocto has KERNEL_FEATURES that enables CAN in the kernel. Use it to
decrease maintanance work.
Signed-off-by: Oleksandr Kravchuk<EMAIL_ADDRESS>

CONFIG_CAN_LEDS

those options are there, except CONFIG_CAN_LEDS, which we can enable if it is needed :poodle:

CONFIG_CAN_LEDS

those options are there, except CONFIG_CAN_LEDS, which we can enable if it is needed 🐩

So perhaps we shall enable this in meta-pelux so we are compatible with what we have provided earlier?
Please confirm that these configs are set to y and not m:
CONFIG_CAN_CALC_BITTIMING=y
CONFIG_CAN_PEAK_PCIEC=y

Here is can config's content:
# platform and USB devices
CONFIG_CAN=m
CONFIG_CAN_VCAN=m
CONFIG_CAN_CALC_BITTIMING=y
CONFIG_CAN_SJA1000=m
CONFIG_CAN_SJA1000_PLATFORM=m
CONFIG_CAN_C_CAN=m
CONFIG_CAN_C_CAN_PLATFORM=m
CONFIG_CAN_CC770=m
CONFIG_CAN_CC770_PLATFORM=m
CONFIG_CAN_SOFTING=m
CONFIG_CAN_SLCAN=m
CONFIG_CAN_IFI_CANFD=m
CONFIG_CAN_M_CAN=m
CONFIG_CAN_EMS_USB=m
CONFIG_CAN_ESD_USB2=m
CONFIG_CAN_GS_USB=m
CONFIG_CAN_KVASER_USB=m
CONFIG_CAN_PEAK_USB=m
CONFIG_CAN_8DEV_USB=m
# x86 PCH
#CONFIG_PCH_CAN=m
# drivers for ISA/PCI cards
CONFIG_CAN_C_CAN_PCI=m
# Philips/NXP SJA1000 based PCI(e)
CONFIG_CAN_EMS_PCI=m
CONFIG_CAN_PEAK_PCI=m
CONFIG_CAN_PEAK_PCIEC=m
CONFIG_CAN_KVASER_PCI=m
CONFIG_CAN_PLX_PCI=m
# SPI bus devices
CONFIG_CAN_MCP251X=m

@JEderonn CONFIG_CAN_LEDS is apparently not there because it is deprecated:

https://lkml.org/lkml/2019/6/24/242
https://lore.kernel.org/patchwork/patch/1050531/


Some node-exporter graphs have no data probably due to AppArmor denials

Bug Description

To Reproduce
With MAAS provider, deploy the grafana-agent charm onto another charm, and relate it to COS.
Environment
$ snap info grafana-agent
...
services:
  grafana-agent: simple, enabled, active
snap-id:      T1u01xKcraA4IpWHpIGNU2nAOom9qG7i
tracking:     latest/edge
refresh-date: today at 11:55 UTC
channels:
  latest/stable:    0.34.3 2023-07-19 (13) 264MB -
  latest/candidate: 0.34.3 2023-07-19 (13) 264MB -
  latest/beta:      0.34.3 2023-07-19 (13) 264MB -
  latest/edge:      0.35.4 2023-08-15 (16) 282MB -
installed:          0.35.4            (16) 282MB -

Relevant log output
Oct 26 12:11:57 up-snail kernel: audit: type=1400 audit(1698322317.541:1674): apparmor="DENIED" operation="open" profile="snap.grafana-agent.grafana-agent" name="/proc/spl/kstat/zfs/" pid=104040 comm="agent" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Oct 26 12:11:57 up-snail kernel: audit: type=1400 audit(1698322317.541:1675): apparmor="DENIED" operation="open" profile="snap.grafana-agent.grafana-agent" name="/sys/fs/btrfs/" pid=104040 comm="agent" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Oct 26 12:11:57 up-snail kernel: audit: type=1107 audit(1698322317.545:1676): pid=1053 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" member="ListSeats" mask="send" name="org.freedesktop.login1" pid=104040 label="snap.grafana-agent.grafana-agent" peer_pid=1064 peer_label="unconfined"
Oct 26 12:11:57 up-snail kernel: audit: type=1107 audit(1698322317.549:1677): pid=1053 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.systemd1" pid=104040 label="snap.grafana-agent.grafana-agent" peer_pid=1 peer_label="unconfined"
Oct 26 12:11:57 up-snail kernel: audit: type=1107 audit(1698322317.549:1678): pid=1053 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="ListUnits" mask="send" name="org.freedesktop.systemd1" pid=104040 label="snap.grafana-agent.grafana-agent" peer_pid=1 peer_label="unconfined"
Oct 26 12:11:57 up-snail kernel: audit: type=1400 audit(1698322317.593:1679): apparmor="DENIED" operation="open" profile="snap.grafana-agent.grafana-agent" name="/proc/sys/kernel/threads-max" pid=104040 comm="agent" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Additional context
No response

By running the binary outside of the confined context (calling /snap/grafana-agent/16/agent -config.expand-env -config.file /etc/grafana-agent.yaml on the host without snapd), I got the following working just for testing:

Processes State
PIDs Number and Limit

Systemd Sockets
Systemd Units States

We have the same problem. The logs are full of permission denied errors: https://pastebin.canonical.com/p/tg6vNpDP6K/

A user mentioned ( https://chat.charmhub.io/charmhub/pl/mwhz1e1c37rdpbbfbzd19bqi3c ) that reverting to stable/latest fixed the issue. @sed-i @Abuelodelanada any ideas ?

Hi @cbartz, I am still seeing these DENIED in both cases. However, the issue I had (i.e. missing info that I needed for my use case) is not happening in latest/stable. I don't think the info that was missing, in my specific case, was due to the DENIEDs thou

Will likely be fixed with #52.


Can't get language server after build

Hey team,
I am trying to use this vscode-azurearmtools, but I can't get language server after run the build. I cloned your repo and ran script but some warning showed as below.

Looks like it doesn't get into the package process. In this case, is there are any prerequisite steps I need to do before getting language server or any steps I miss from there?

@v-tsun This is due to current licensing restrictions on the language server, which uses code from VS (see https://github.com/microsoft/vscode-azurearmtools#license).  Due to that, packaging with the language server is restricted.
What are you trying to do?  If it's just a matter of making changes to use on your own machine, or to submit PRs, the easiest solution is to use the azureResourceManagerTools.languageServer.path to point to the language server from an existing installation of the extension (e.g. /.vscode/extensions/msazurermtools.azurerm-vscode-tools-0.14.0/languageServer).
If that isn't sufficient, let me know what you're trying to accomplish and let me see how I can help.  Thanks.

@StephenWeatherford We are from AzureStack Team and we are trying the ARMtools extension against AzureStack ARM. As AzureStack supports only a subset of Resource providers and older api versions, we may need some changes in the extension. We will likely get in touch with you if we figure out any issues that would need your inputs. At this moment @v-tsun  is just exploring this extension. Thanks for your quick response here!

Sure thing, feel free to contact directly. Closing for now.

@v-tsun BTW, this extension does not current sign in to Azure, it just edits ARM templates off-line, so not sure AzureStack makes any difference, unless there are different versions of the schemas.


Weird 'maybe uninitialized' warning on gcc

[ 60%] Building CXX object CMakeFiles/mgcpp_test.dir/test/fft_test.cpp.o
In file included from /home/msca8h/projects/mgcpp/include/mgcpp/operations/mult.hpp:68:0,
                 from /home/msca8h/projects/mgcpp/include/mgcpp/expressions/dmat_dmat_mult.tpp:10,
                 from /home/msca8h/projects/mgcpp/include/mgcpp/expressions/dmat_dmat_mult.hpp:49,
                 from /home/msca8h/projects/mgcpp/test/blaslv3_expression_test.cpp:10:
/home/msca8h/projects/mgcpp/include/mgcpp/operations/mult.tpp: In member function ‘virtual void mult_expr_scalar_dmat_mult_Test::TestBody()’:
/home/msca8h/projects/mgcpp/include/mgcpp/operations/mult.tpp:125:14: warning: ‘<anonymous>’ may be used uninitialized in this function [-Wmaybe-uninitialized]
         auto casted_scalar = MatrixType(scalar);
              ^~~~~~~~~~~~~
/home/msca8h/projects/mgcpp/test/blaslv3_expression_test.cpp:101:27: note: ‘<anonymous>’ was declared here
         auto expr = 7.0 * A_mat;
                           ^~~~~
In file included from /home/msca8h/projects/mgcpp/include/mgcpp/operations/mult.hpp:68:0,
                 from /home/msca8h/projects/mgcpp/include/mgcpp/expressions/dmat_dmat_mult.tpp:10,
                 from /home/msca8h/projects/mgcpp/include/mgcpp/expressions/dmat_dmat_mult.hpp:49,
                 from /home/msca8h/projects/mgcpp/test/blaslv3_expression_test.cpp:10:
/home/msca8h/projects/mgcpp/include/mgcpp/operations/mult.tpp:125:14: warning: ‘<anonymous>’ may be used uninitialized in this function [-Wmaybe-uninitialized]
         auto casted_scalar = MatrixType(scalar);
              ^~~~~~~~~~~~~
/home/msca8h/projects/mgcpp/test/blaslv3_expression_test.cpp:149:43: note: ‘<anonymous>’ was declared here
         auto expr = mgcpp::mult(7.0, A_mat);
                                           ^
[ 62%] Linking CXX executable mgcpp_test
[100%] Built target mgcpp_test

gcc-7
gcc is complaining about maybe uninitialized values.
clang seems to have no problem about it.
hum...

I highly suspect this to be a false gcc false positive
gcc seems to have issues with maybe-uninitialized

Adding -Wno-maybe-uninitialized seems to be a temporary workaround.

@mujjingun Guess well have to live with it until a release version


New file added

What the program do ?
----Print a line
In what programming language it is written?
Php

This pull request do not contains files in specific folders. Please fix it and reopen


[MAUI][ANDROID] TabHostView Text Colors Don't Change Switching Light/Dark Mode

Platform (please complete the following information):
OS: [Android]
Device: Tab Active 3 [Android API Level 31]
Sdk Version: Min: 30 Target: 34
MAUI: [NET 8.0][8.0.91]
I notice the text colors for selected and unselected tabs aren't switching when the dark/light mode changes. The background color changes and the segmentedoutlinecolor changes. Something isn't working right with the text colors though when switching dark/light mode.
This issue was introduced after the fix for this issue (https://github.com/roubachof/Sharpnado.Tabs/issues/127#)
I'm currently on sharpnado.tabs 3.1.1
To Reproduce
Steps to reproduce the behavior:
- Create an app with the Tabs control
- In the Resources/Styles/Styles.xaml, add styling for the various tab components with AppThemeBindings for light and dark modes
- Run the app and navigate to the page with the tab control
- Then, from the notification tray, change the theme from light to dark or vice versa.
- Dismiss the notification tray after the theme has switched so you are back in the app.
- You'll notice as you switch the dark/light mode, the text colors in the tabhostview aren't changing

Styles used in my Style.xaml file: (of course change the color StaticResources to match your colors)
 <Style TargetType="sho:TabHostView" x:Key="TabHostView">
        <Setter Property="BackgroundColor" Value="{AppThemeBinding Light={StaticResource LightBackground02}, Dark={StaticResource DarkBackground02}}" />
        <Setter Property="SegmentedOutlineColor" Value="{AppThemeBinding Light={StaticResource Gray950}, Dark={StaticResource Gray200}}" />
        <Setter Property="CornerRadius" Value="10" />
        <Setter Property="TabType" Value="Fixed" />
        <Setter Property="IsSegmented" Value="True" />
        <Setter Property="Orientation" Value="Horizontal" />
        <Setter Property="SegmentedHasSeparator" Value="True" />
    </Style>

    <Style TargetType="sho:UnderlinedTabItem" x:Key="UnderlinedTabItem">
        <Setter Property="SelectedTabColor" Value="{AppThemeBinding Light={StaticResource Primary}, Dark={StaticResource PrimaryLight}}" />
        <Setter Property="UnselectedLabelColor" Value="{AppThemeBinding Light={StaticResource LightSecondaryText}, Dark={StaticResource DarkSecondaryText}}" />
    </Style>

    <Style TargetType="sho:BadgeView" x:Key="BadgeView">
        <Setter Property="Background" Value="{StaticResource Secondary}"></Setter>
    </Style>

Expected Behavior: Tab text colors change to their respective dark/light theme color

Look like a good first issue to me 😄

I tried to fix that, but no idea why the property changed is not triggered on the tab item's property...

It was working before 3.1.0/3.1.1.

Oh cause we switched to .net 8 maybe
Le jeu. 24 oct. 2024, 14:25, sk1llsh0t @.***> a écrit :

It was working before 3.1.0/3.1.1.
—
Reply to this email directly, view it on GitHub
https://github.com/roubachof/Sharpnado.Tabs/issues/131#issuecomment-2435154211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAERXJ2EA67W747F7J2MJMDZ5DRNFAVCNFSM6AAAAABQOW3VCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGE2TIMRRGE
.
You are receiving this because you commented.Message ID:
@.***>

I believe I know what is happening. Right now, you have an OnPropertiesChanged override that is handling all the property changes. It uses a switch statement to know which property changed and take the appropriate action. In my experience moving our app from xamarin forms to maui (.net 8.0), this no longer works consistently. Some properties it will fire for but others, not.
The way to do it is when instantiating the bindableproperty, there is a parameter for onpropertychanged which you can define a callback for. if you pass the method in through that parameter directly to the bindableproperty, it will work.
This is definitely a bug in maui that has not been addressed yet apparently. Give that a try and see if it starts working again.

In the Resources/Styles/Styles.xaml, add styling for the various tab components with AppThemeBindings for light and dark modes

Does this work at all for you? Whenever I try to style the tabs via Styles.xaml I get a strange exception (with 3.1.0 and 3.2.0 on Android):
System.NullReferenceException: Object reference not set to an instance of an object.
  at at Sharpnado.Tabs.TabHostView.UpdateTabType()
  at at Sharpnado.Tabs.TabHostView.OnPropertyChanged(String propertyName)

it does work for me. the repro project i have posted above uses styles.xaml (https://github.com/sk1llsh0t/TabVmBindingRepro)

So basically, you eliminate this method (https://github.com/roubachof/Sharpnado.Tabs/blob/07f3072e2496bd6c76e6b3e7250c61767524ff69/Tabs/Tabs/UnderlinedTabItemBase.cs#L39)
Then, you modify your bindableproperties to handle the property change.
Example:
'''
public static readonly BindableProperty SelectedTabColorProperty = BindableProperty.Create(
nameof(SelectedTabColor),
typeof(Color),
typeof(TabItem),
Colors.Magenta,
propertyChanged: OnPropertyChanged   // add this line to all your bindable properties
);
private static void OnPropertyChanged(BindableObject bindable, object oldValue, object newValue)
{
// Same logic from the old OnPropertyChanged but you'll need to look at the BindableObject to know what is changing
}
'''

nope. Already tried what you suggested unfortunately

Looks like maybe it is a MAUI issue with appthemebindings.
https://github.com/CommunityToolkit/Maui/issues/1994
https://github.com/dotnet/maui/issues/24444
Possible resolve commit:
https://github.com/dotnet/maui/pull/24465
I guess they broke it going from net6 to net8 since this was all working in 3.0.1 but broke in 3.1.0. So hopefully in a future release, this gets fixed.

The issue was introduced in this commit: (https://github.com/roubachof/Sharpnado.Tabs/commit/c60990f72d523c38df60776d7a0004fff791256d)
In the TabHostView class, the frame control was changed to a border. Changing it back to a frame makes the app theme colors work again.
To figure it out, i grabbed the previous good commit, and started adding each changed code section 1 at a time until it broke. Since the border was the last thing i thought would break something like this, it was the last remaining thing to check. Anyway, there you go.

Does this work at all for you? Whenever I try to style the tabs via Styles.xaml I get a strange exception (with 3.1.0 and 3.2.0 on Android):
System.NullReferenceException: Object reference not set to an instance of an object.
  at at Sharpnado.Tabs.TabHostView.UpdateTabType()
  at at Sharpnado.Tabs.TabHostView.OnPropertyChanged(String propertyName)

FYI: I managed to reproduce it with the sample app and opened issue #138 for it.

@sk1llsh0t nice job !
I will fix #138 and see what's what

Any update on this one?

I won't have any time on this one. I guess you are very close to find the issue after your recent findings:)

Meaning: if you find the issue I will make a new package ASAP

My opinion is something is broken in the border control that isn't allowing the property events to fire on child elements when dark/light mode changes. The only solution I can come up with is to revert the border back to a frame. Unfortunately, the frame control is flagged as obsolete in .net 9. It is possible that the maui folks need to take a look at this issue in the border control.
Anyway, i have a forked branch where i've reverted the border back to a frame. if you are ok with that, i can submit a pull request. This can be a temporary solution until the border is fixed.
Let me know.
Let me know i

I don't have any more time to give to this much less wait on Microsoft to come up with a fix to their border control. I may wait until .Net 9 is released to see if that fixes it. Otherwise, without the ability to switch the app theming colors correctly, I may need to roll my own tabview or something.
You've done great work with this control. It is just a shame that something out of your control is causing this breaking issue.

as a matter of fact you could intercept the Theme change event and set the color accordingly until MS fixes the issue.

One other thing i noticed, if i set IsSegmented=False (no border), the colors work. then if i add the border around the tabhostview, the colors continue to work. So it looks like the issue is not there if xaml is used.


Fix spelling and make some links HTTPS in README

Hi and thanks a lot for QPDF!
I'd like to offer some spelling corrections for the README. I also made links HTTPS where possible.

@mb720 I really appreciate this! I'll have to remove cyrpto from my spelling checker dictionary. I have a lot trouble typing that word. Usually I type crytpo. Anyway, thnaks! :-)


exception:EXC_BAD_INSTRUCTION

My environment  is:
macos(10.15), clion 2019, clang++
I don't know much about c++. I wrote a simple program, but it crashed：
#include <stdio.h>
#include "epanet2.h"
int  main(int argc, char *argv[]){
  ENopen("example.inp","rtp.txt","");
  return 0;
}

Error message:Exception: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
The final problem is located at input3.c:1175
strcpy(parser->Tok[0], parser->Tok[1]);

It happened detected source and destination buffer overlap
how to fix??

it may help to post the example network you're dealing with - so someone can replicate this behavior.

it may help to post the example network you're dealing with - so someone can replicate this behavior.

ok ,is the example network

Thanks - there does seem to be an issue here.
https://github.com/OpenWaterAnalytics/EPANET/blob/c16c861789f2aa93b7446d08b7a365916c479d2f/src/input3.c#L1174-L1175
... this line offends the latest strcpy implementation in Clang because we are trying to copy a character string into a location that might overlap. The Tok array is just a set of pointers to the original parsed line, and so there would be a problem depending on the token string lengths.
I can confirm that the implementation in GCC 8.3 does not check for this potential overlap, and so that would not show up on the tests, and might be a workaround if needed.
But - I don't think that this copy operation is necessary. Tok[0] is never referenced again for this tokenized line. This same overlap could happen again here, where there's a comment about saving for error reporting, but I can't see where that would ever be reported:
https://github.com/OpenWaterAnalytics/EPANET/blob/c16c861789f2aa93b7446d08b7a365916c479d2f/src/input3.c#L1825-L1828
Unless I'm missing something, I think these lines are safe to remove.

Is this a C++ thing? I does not fail with the GUI or VB

no, I think it's just a "c library implementation" thing. GCC works fine, but Clang checks for overlaps.
http://demin.ws/blog/english/2011/07/14/strcpy-on-overlapped-strings/

Thanks, I have not noticed the compiler problem.  I changed ”strcpy” to ”strncpy” to solve this problem temporarily, but I don't know what the consequences will be (

The offending line is a carryover from the v2.0 (circa 2000) code. I agree with @samhatchett that with the new method used for reporting errors in an input file it is no longer needed. If there are no objections I will submit a PR that removes the line.

This issue has been resolved via PR #565 .

strncpy also doesn't allow overlap, in my experience. I hacked my code with this solution, but this should not be used in production code:
#undef strcpy
char *mystrcpy(void *dest, void *source)
{
size_t sourceLen = strlen(source);
memcpy(dest, source, sourceLen);
((char)dest + sourceLen) = '\0'; //null terminate
return dest;
}
#define strcpy mystrcpy
But then I deleted that and used this instead:
void *deleteChar(char *p)
{
while (*p) {
*p++ = p[1];
}
*p = '\0';
}
Ref: https://github.com/tallpeak/anagram/blob/master/anagramsrt.c


Print list of valid team names when team not found

When attempting to sign in to a team, this PR provides a more informative list of valid team options to choose from in the event that the user's selected team could not be found.

Thanks, will take a few days before it'll show up in matterircd, I'm going to do some other vendor updates too

No worries, thanks for the bridge!


epic: esl-footnotes

Cumulative PR that includes: PR #769 and PR #772

:tada: This PR is included in version 3.13.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Updated Readme.md to reflect the renaming from Artemis to Teku

PR Description
Updated Readme.md to reflect the renaming from Artemis to Teku
Fixed Issue(s)
Artemis was used in place of Teku which also caused the following issues

Broken CI Link
Broken License Link
Broken GitHub link in the instructions

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


Get-DbaBackupHistory - Add option to ignore copy_only backups

Is this a feature OR bug:
Feature
Currently Get-DbaBackupHistory includes copy_only backups by default. This causes an issue when the output is piped into Restore-DbaBackup as it grabs the copy_only one as the most recent and then doesn't pick up logs/etc as it's a new Recovery Fork
Proposing we add an IgnoreCopyOnly switch to the function which appends is_copy_only=0 to the sql query.

OHHH good idea! Yes please.


Add link to AppNeta TraceView hook

Add link for AppNeta TraceView hook.

Added in master due to merge conflict


Deprecate blobstorage

Description
This PR removes MinIo and kfaka-to-blob from the Helm Chart
Fixes #1519
Type of change
Please delete options that are not relevant.

[x] Chore: dependency
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Deployed

Checklist:

[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding changes to the changelog (if needed).

Changelog changes

Codecov Report

Merging #1520 (a40e143) into main (becacc0) will decrease coverage by 0.05%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1520      +/-   ##
==========================================
- Coverage   11.15%   11.11%   -0.05%
==========================================
  Files          31       31
  Lines        9842     9842
==========================================
- Hits         1098     1094       -4
- Misses       8687     8690       +3
- Partials       57       58       +1

see 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[gui error report] Error

👉 Please describe what you were doing when this error happened.
Specifications

OS: darwin
IPFS Desktop Version: 0.20.2
Electron Version: 17.1.0
Chrome Version: 98.0.4758.102

Error
Error
    at errorTemplate (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:78:49)
    at loadWindow (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:115:26)
    at module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:120:3)
    at startIpfsWithLogs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:158:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:174:17)
    at async startIpfs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:46:17)
    at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:114:3)
    at async run (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/index.js:83:5)

@LordWilliamsr sadly this error is not very informative – are you able to tell us more what happened?

I have commented in #2040


DOC: add versionadded specifications to docstrings

We already use the .. versionadded:: directive in the tutorial docs to indicate that a certain feature is only present starting from a specific pandas version.
But I propose that we also start to do this in the docstrings, when adding a new function/method or adding a new keyword to an existing function/method:

When developing a package depending on pandas, you typically are using latest pandas but want to support also certain older versions. When using a certain method/function/keyword functionality, the easiest place to see if this is available is the docstring.
Or, you also typically look at the stable docs even when using a maybe older pandas version and see functions/keywords that don't yet exist for your version.
This is also how it is done in numpy:

example of new method: http://docs.scipy.org/doc/numpy-dev/reference/generated/numpy.nanmean.html
example of new keyword: http://docs.scipy.org/doc/numpy-dev/reference/generated/numpy.percentile.html

So if we agree on this, some todo's:

[ ] add guidelines to the developer docs on how to add this (and start asking for this when reviewing PRs)
[ ] - optional - add this retrospectively to eg the new features of 0.16.0/1

@jreback @shoyer @sinhrks @TomAugspurger
Any objections to this?
It would look something like this: https://github.com/jorisvandenbossche/pandas/commit/274826e1f9efa9ded3794f1f818101302a33cc40

:+1:

lgtm

Nice, will do.

Agreed, seems like a good idea.


Link the logo in the maintenance tab to the web site.

Add also a link to the banner in the about tab.


UX issue when trying to use user assigned managed identity.

Docs say set 'AZURE_CLIENT_ID'. If I only do that, I get this error:
Incomplete environment configuration. These variables are set: AZURE_CLIENT_ID
That is because it tries to use EnvironmentConfig first.
I'd like to see the docs updated to say you must disable EnvironmentConfig with exclude_environment_credential=True if you want to use user assigned managed identity.

Or detect that user has only set AZURE_CLIENT_ID and assume they want to use user assigned MI

Can confirm this was a major pain in the ass for me to figure out when using Azure Container Apps (assignment at the app, then assignment at the container revision,  then adding the environment variables).


[Bug] V2.0 Beta6 italian language not available

Hi, I'm trying to run the beta 6 but I get the following issues:
custom_components.smart_irrigation.calcmodules.localize
Source: custom_components/smart_irrigation/calcmodules/localize.py:30
Couldn't load translations language file for it
And also
Error setting up entry Smart Irrigation for smart_irrigation
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 388, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smart_irrigation/init.py", line 105, in async_setup_entry
await store.set_up_factory_defaults()
File "/config/custom_components/smart_irrigation/store.py", line 226, in set_up_factory_defaults
await self.async_factory_default_modules()
File "/config/custom_components/smart_irrigation/store.py", line 250, in async_factory_default_modules
inst = m(self.hass, {})
^^^^^^^^^^^^^^^^
File "/config/custom_components/smart_irrigation/calcmodules/static/init.py", line 21, in init
super().init(name="Static", description=localize("calcmodules.static.description",hass.config.language)+".", config=config, schema=SCHEMA)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
Thank you very much for your awesome work!

looks like the second issue is caused by the first. Let me investigate and create a new build for this.

@apocaliss92 here it is: https://github.com/jeroenterheerdt/HAsmartirrigation/releases/tag/v2023.8.0-beta7, let me know if this helps! Thanks for catching this!

The language missing one is gone but I still have this
Error setting up entry Smart Irrigation for smart_irrigation
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 388, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/smart_irrigation/init.py", line 105, in async_setup_entry
await store.set_up_factory_defaults()
File "/config/custom_components/smart_irrigation/store.py", line 226, in set_up_factory_defaults
await self.async_factory_default_modules()
File "/config/custom_components/smart_irrigation/store.py", line 257, in async_factory_default_modules
**{MODULE_ID: 0, MODULE_NAME: "PyETO", MODULE_DESCRIPTION:localize("calcmodules.pyeto.description",self.hass.config.language)+".",
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
TypeError: unsupported operand type(s) for +: 'dict' and 'str'

ok, let's try that again: [v2023.8.0-beta8](https://github.com/jeroenterheerdt/HAsmartirrigation/releases/tag/v2023.8.0-beta8

No errors anymore! Thanks :) just one question, will be there the possibility again to specify the sensors as before? I cannot find a way to do it

Nevermind I just found the new wiki page, thanks again!


Removing a Tag in a TagGroup with disabled Tags crashes the page

Provide a general summary of the issue here
When combining two features of TagGroup - disabledKeys and onRemove - it's possible to crash the browser tab when removing a Tag.
This only seems to happen when there are at least two disabled Tags in the collection.
I'm able to reproduce in at least two ways:

Remove all non-disabled Tags from a collection (ctrl-a + backspace), leaving only disabled Tags remaining.
Remove the last Tag from the end of a collection where the (at least) two previous Tags are disabled.

It works fine when:

There is only one disabled Tag.
There is only one disabled Tag between the removed Tag and the next focusable Tag.

🤔 Expected Behavior?
The page should not crash and the next or previous non-disabled Tag should receive focus. If there are no remaining focusable Tags, the TagGroup or TagList should receive focus.
😯 Current Behavior
The page crashes.
💁 Possible Solution
At a guess, I would say that perhaps the TagGroup is struggling to find a valid target to move focus to when the element is removed.
🔦 Context
No response
🖥 Steps to Reproduce
https://codesandbox.io/p/sandbox/exciting-hooks-6lhjcm
Delete the final tag 'Watermelon' to crash the tab.
Version
react-aria-components 1.2.1
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
Windows
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Yep, found the issue, I've created a PR to fix it. Thanks for reporting it

Amazing! Thanks for the quick fix 🚀


Frontend version tag not synchronized with backend

Not sure if you intend the version tags to be in sync with each other, but if so, then they are currently diverging:
https://github.com/deepsense-ai/seahorse/blob/96d790251beb307eb68892fc94f1f273730a9cff/frontend/package.json#L3

It will be in sync now.


Automatically release Docker images to GHCR

Hi there,
this adds a recipe derived from [1] to the CI configuration. It should build and publish Docker images when there are tags pushed to the repository.
With kind regards,
Andreas.
[1] https://github.com/docker/build-push-action/blob/master/docs/advanced/tags-labels.md

Shouldn't we then also document the availability of pre-build docker images inside the README?

If it will work out well, I will surely document it.

I've added a note with 67821567.

If [all] will work out well...

Just for the records: Currently, I don't believe a latest tag will be set. I wanted to check first if this action will work in general.


Fix YAML indentation consistency

What this PR does / why we need it: Fix YAML indentation consistensy
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

@posquit0 This probably affects the file https://github.com/Kong/kubernetes-ingress-controller/blob/master/deploy/single/all-in-one-postgres.yaml.
Could you use the ./hack/build-single-manifests.sh script to update that file as well?
Thanks!

I did! 👍


🧑💻: Enhance the E-Mail section with borders using css.

:red_circle: Enhance the E-Mail section with borders using css.
:red_circle: I think if the E-Mail section had border-bottom in every text item so it would have better UI and also it is not aligned properly. I would also like to make it responsive.
Please Assign me this issue with the label of GSSOC'24
Screenshots 📷
Before:

After:

:white_check_mark: To be Mentioned while taking the issue :

Full name : Nandini Agrawal
What is your participant role?  GSSOC'24.

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

i don't think, addition of 1 line makes the ui looks good 🙂

Sir, but I think little little changes can make more and more difference in UI of website.
Please Assign me this issue with the level and label of GSSOC'24

@agrwal697 ok go ahead.


improvements to github crawler

added PRs to github crawler (per issue #15)
Refactor to simplify

Approved. I'm not familiar with the github API or object model, but your usage of that, as well as the vectara API, look good to me. One thing to consider (and it's larger in scope than this specific PR) is to add timestamp fields that are numeric (e.g. number of epoch seconds) whenever you have created_at or updated_at metadata fields. That way the user can do date range based filtering by defining the fields as filter attributes. But that's a nice to have, and not a blocker for this PR.