Exporting hangup

Issue Type: Bug
When exporting to Excel 250,000 records, sometime it works sometme not.
Azure Data Studio version: azuredatastudio 1.43.0 (b790d700898b1095d83e62f0de14678a58222520, 2023-04-10T23:12:44.872Z)
OS version: Darwin arm64 22.4.0
Restricted Mode: No
Preview Features: Enabled

System Info

Item
Value

CPUs
Apple M1 Max (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
4, 4, 4

Memory (System)
64.00GB (30.05GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

deletedb
Ale
0.0.3

sql-data-inspector
ern
0.6.0

azuredatastudio-postgresql
Mic
0.2.7

azdata-sanddance
msr
4.1.1

schema-visualization
R0t
0.8.2

@caohai is this something you looked into before?

@caohai is this something you looked into before?

@alanrenmsft No I didn't look into this one, I can take a look.

Hi @MarcosHerasme , thanks for reporting this.
I did a quick test on Windows and Mac (Intel) with following query and exported 250k/500k records to Excel and didn't see it hangs up. You can also try it out on your machine and see if exporting hangs with this query.
Do you have a lot of columns in the result? Is there any other error message or any other info you can help us repro this issue?
WITH RandomNumbers AS (
    SELECT ABS(CHECKSUM(NEWID())) AS RandomNumber
    union ALL
    SELECT ABS(CHECKSUM(NEWID())) AS RandomNumber
    FROM RandomNumbers
)
SELECT TOP 250000 RandomNumber AS RandomNumber1
FROM RandomNumbers
OPTION (MAXRECURSION 0 )

@caohai This seems like a good opportunity to add some more perf measurements in case we aren't able to repro this ourselves. That would at least let us see what part is taking a long time and could help narrow down what the issue is

@MarcosHerasme could you please try the latest insiders build? I've made some changes to the query area which might help the export scenario as well. https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main-branch
if it still doesn't work, please follow the instructions and share the logs with us.


LazyCollection::every() type inferences by PHPStan are completely broken

Laravel Version: 9.3.1
PHPStan Version: 1.4.5
Larastan Version: 1.0.3
PHP Version: 8.1

Description & Reproduction Steps:
$collection = new LazyCollection([new \stdClass]);
\PHPStan\dumpType($collection->every(...));

Expected:
Dumped type: Closure((callable(stdClass, int): bool)|stdClass|string, mixed, mixed): bool

Actual:
Dumped type: Closure((callable(int, int): bool)|int|string, mixed, mixed): bool

Though I haven't determined yet whether it is a PHPStan bug or a Laravel bug, I'll submit it as a Laravel issue for the time being.

I hope that https://github.com/laravel/framework/discussions/40889 should be resolved although it is not directly related. It is very inconvenient that Collection<Item> is not considered a subtype of Collection<ItemInterface> whereas Item[] is considered a subtype of ItemInterface[].

Related

https://github.com/laravel/framework/pull/38538 by @nunomaduro
https://github.com/laravel/framework/pull/39506 by @sebdesign

Please just attempt a PR if you want to adjust anything. No code is broken.

@driesvints I confirmed that it's not reproducible in newly cloned laravel/laravel apps, however, it actually appears in my existing app. I'll research some more.

It's very odd, looks like LazyCollection::every() specific.

wtf???

Method
Collection
LazyCollection

every()
✅
:x:

some()
:x:
:x:

map() filter()
✅
✅

A clean install solved the problem. I can't reproducd the bug anymore regardless I haven't touch directly inside vendor and prepare the same version of composer.lock as before. I have no idea what's going on. Was the cache corrupted?

Reproduced again

Confirmed that the TValue inferencing is unexpectedly replaced with TKey.

Re-published as a PHPStan issue: https://github.com/phpstan/phpstan/issues/6768


Showing unresolved import warning on a local/relative module import

Environment data

VS Code version: XXX
Extension version (available under the Extensions sidebar): XXX
OS and version: XXX
Python version (& distribution if applicable, e.g. Anaconda): XXX
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
Relevant/affected Python packages and their versions: XXX
Relevant/affected Python-related VS Code extensions and their versions: XXX
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): XXX
Value of the python.languageServer setting: XXX

Expected behaviour
XXX
Actual behaviour
XXX
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

XXX

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXXX

Thanks for the bug report, but unfortunately we need some more information from you in order to triage this issue appropriately. Please edit your opening comment by providing a filled-in copy of our issue template. Once you are done please leave a comment to that effect.


vscode-extensions.davidlday.languagetool-linter: init at 0.18.0

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 140190 run on x86_64-linux 1

1 package built:

vscode-extensions.davidlday.languagetool-linter


Environment vars not loaded from file when runme invoked with --filename flag

Hello
Let me describe the bug

Runme version

runme --version
runme version 3.9.4 (Homebrew) on 2024-11-21T22:49:56Z

Env file, named .env

export MY_VAR=SOME_VALUE

Runme playbook, named test.runme

```sh {"name":"env"}
echo "@@${MY_VAR}@@"
```

Invoking runme run with --filename doesn't read the variables from .env

runme run --all -y --filename='test.runme'
@@@@

Although runme run without --filename works OK

runme run --all -y
@@SOME_VALUE@@

The same inconsistent behaviour is happening when invoking runme tui.

OK, I've found the issue - in my ~/.bashrc I am having the line that cd into the directory where are my work projects located.
So, the new shell for me is opened inside "${HOME}/work/projects` instead of "${HOME}".
Removing this line from ~/.bashrc solved the mentioned issue with env file loading.
IMO this is a bug, and shells created by run me should force cd into playbook folder or into --chdir argument.

Thanks for reporting this issue, @eshepelyuk.
We will look into it and get back to you.


Update hybrid-azuread-join-federated-domains.md

@deosandeep : Thanks for your contribution! The author, @MarkusVi, has been notified to review your proposed change.

#sign-off


Consider moving 3DTiles/glTF class generation to CI

We generate the classes manually and have documentation as of PR #705 .
Could we benefit from having our build do this for us? (and by extension, continuous integration)
Some initial thoughts:
(+) Don't have to manually generate these classes ever again
(+) Don't have to commit the generated classes
(+) Ensures our generation code always works (and is up to date)
(-) More dependencies for cesium-native builds
(-) Slower cesium-native builds (not sure how much)

I applaud the sentiment to generate these classes during the build. Speaking selfishly, it would be a drag to have more dependencies in the cesium-native build.

Thanks @timoore. Just to clarify a few points:

The dependency we're talking about is Node.js, which is use to run the code generator.
Currently the generated files are checked into the repo, so you only need Node.js if you want to regenerate the code, which isn't too common (the 3D Tiles and glTF specs change slowly).
This issue is suggesting that we not check the generated files into the repo. Instead, we would run the generator as part of the build process. Which means that building cesium-native would require Node.js.

So if I understand your comment correctly, you're saying that you would prefer that we leave things as they are in order to avoid adding a new built-time dependency on Node.js. Do I have that right?

That's a good summary of what I thought was proposed. Node.js is probably not a big deal for Cesium folks, but it would definitely be a surprising dependency in the VSG world. For Unreal / Unity users, would that dependency be sucked in automatically during the build?

For Unreal / Unity users, would that dependency be sucked in automatically during the build?

No, it would probably just be a prerequisite. But Cesium for Unreal and Cesium for Unity users don't usually build cesium-native themselves, they just use pre-built binaries. So it's only people developing these plugins that would need to have Node.js.
In any case, I think you're convincing me that we might just want to stick with the status quo. The main motivation was to avoid having PRs with changes to a hundred generated files that we have to skip over when reviewing (and maybe verify that the committed files reflect what was generated, otherwise we'll lose any modifications next time we regenerate). Curious what @csciguy8 thinks.

I applaud the sentiment to generate these classes during the build. Speaking selfishly, it would be a drag to have more dependencies in the cesium-native build.

Well technically, Node.js is already a build dependency, whether it's something that's on CI or not. Our builds need the generated classes. The generation process needs Node.js. Generating the classes needs time and a machine to run on.
As it stands from a Devops perspective, we have maintenance issues:

When do these classes need to be generated? (how do we know they are out of sync)
Who is building these classes? (from this PR, @kring 's local machine)
For the machine that built these classes, is the generation build setup documented?
How do we verify the classes are correct? Does the reviewer have the same setup and repeatability as the machine that committed them?
Are future contributors discouraged from changing related code because of this complexity?

Don't get me wrong, I understand the motivation to keep our local builds as fast and simple as possible. I like this too.
But if we encounter these questions over and over in future PRs, it may actually be slowing us down by keeping this process manual.

I see what you're saying, but I don't think I can get worked up about it. They get regenerated when we see a need to do so because the spec or the generator changed, and having it being an intentional step to pick up spec changes isn't necessarily a bad thing. Anyone can build the classes, and it's quite repeatable, and there are even instructions for doing it in the README now. We can verify they're correct by re-running the generator itself and verifying there are no resulting changes (It would of course be concerning if differences of setup ever caused the generated code to be different, but that has not happened so far and I think it's reasonably unlikely to happen in the future). And of course we also verify by compiling cesium-native and running the test suite. I don't think the need to install Node.js and run a couple of commands should be a major impediment to changing this code for anyone that needs to.
We could get the best of both worlds with a github action or somesuch that periodically re-runs the generator from the latest spec and opens a PR if there are any changes (kind of like dependabot). I think it's hard to make a case that that's among the best things we can spend our time on right now, though.

Closing this issue.
It's been considered, and not something concerning enough to leave open.


[7.x] Added configurable key for destroy method

Currently Eloquent Model destroy() method is fetching objects from DB only by primary key.
This PR allows passing a second optional parametar to that method to specify which column to look at.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

Just write a query to delete using the key you need.

@taylorotwell ok but I wan't to fire model events as well and not need to write extra code for fetching, looping trough and then deleting model by model as this method already does that. My PR was just an extra sugar for specifying the column name.


picom: new package at 7.5

Description of package
A compton replacement.
Depends on #175.
Checklist

[x] Latest upstream version.
[x] I agree to maintain this package (required).
[x] I agree to notify KISS if I can no longer maintain this package (required).

This is a package I originally wanted, but failed to compile. Would be happy to let you maintain all of the deps required for this and to drop compton if we get picom merged.

I'm happy to maintain compton and keep both around. :+1:

okay thanks


nsp check gived "(+) Debug output: Bad Gateway"

It worked fine until earlier today, but now it throws this error everytime I run nsp check.
node v6.10.2
nsp v2.6.3

sorry about that, we had a bit of a system outage. i've got it fixed now and everything seems to be working correctly again. do let us know if you see any other issues!


Update CI-raiwidgets-pytest.yml to skip windows 3.8 tests

Description
Looks like the windows test with python 3.8 are failing most of the time with segmentation faults in workflow https://github.com/microsoft/responsible-ai-toolbox/actions/workflows/CI-raiwidgets-pytest.yml. Hence, skipping these tests unless there is a solution in place.
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #1890 (7c08580) into main (e944dc5) will decrease coverage by 6.59%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1890      +/-   ##
==========================================
- Coverage   92.44%   85.85%   -6.60%
==========================================
  Files         103       29      -74
  Lines        4830      523    -4307
==========================================
- Hits         4465      449    -4016
+ Misses        365       74     -291

Flag
Coverage Δ

unittests
85.85% <ø> (-6.60%)
:arrow_down:

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

Impacted Files
Coverage Δ

responsibleai/responsibleai/__version__.py

...ibleai/_tools/shared/state_directory_management.py

responsibleai/responsibleai/_data_validations.py

responsibleai/responsibleai/_config/__init__.py

erroranalysis/erroranalysis/_internal/utils.py

rai_core_flask/rai_core_flask/flask_helper.py

...i_core_flask/environments/public_vm_environment.py

...ai/responsibleai/_tools/causal/causal_constants.py

..._flask/environments/credentialed_vm_environment.py

...ranalysis/erroranalysis/_internal/matrix_filter.py

... and 64 more

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


readme updates!

because every project needs a real readme. :)

Wow ! The most pleasant way to tell me something was missing :9)
Much appreciated and needed, thank you for the help/contribution.

Also, you can find full and minified versions of NWXforms on S3 CDN:
https://s3.amazonaws.com/nwapi/nwxforms/nwxforms.js
https://s3.amazonaws.com/nwapi/nwxforms/nwxforms-min.js

to make easy for users to directly embed the helper in their HTML pages.


Build error after upgrade to Angular 9

I upgraded to Angular 9, and I'm now receiving an error that Ivy is turned on. If I turn Ivy off, everything works fine.

ERROR in node_modules/ng2-currency-mask/src/currency-mask.module.d.ts:1:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (ng2-currency-mask) which declares CurrencyMaskModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if
the library is expected to be compatible with Ivy.

1 export declare class CurrencyMaskModule {
                       ~~~~~~~~~~~~~~~~~~

** Angular Live Development Server is listening on localhost:4200, open your browser on https://localhost:4200/ **
95% emitting CopyPlugin
    ERROR in src/app/app.module.ts:180:5 - error TS2304: Cannot find name 'CurrencyMaskModule'.

    180     CurrencyMaskModule,
            ~~~~~~~~~~~~~~~~~~

Well, seems to be an issue with upgrading angular.

I'm with the same issue here.

Same problem here

no answer found to fix this, anyone?


Tabular Data Package (the CSV)

you've got nice CSV either here #4 or on archive.pudo.org - why not data package?

Good point. I started generating some JSON to drive the web site but didn't end up using it + there's the schema for PEPs which gives column titles etc. Should make that into a data package.

+1 :-)

@pudo did you get to do this?


🐛 Date Picker and Time Picker only saves last changed dialer

Describe the bug
Date Picker and Time Picker only saves last changed dialer.
To Reproduce
Steps to reproduce the behavior:

Go Demo Page -> Forms
Change two or more in Date or Time Picker

Expected behavior
Expect all to remain
Screenshots
None
Additional context
None

Date and Time pickers need a rework to make it look and feel native!

fix it please

@mahmunk ... I'm now sure about how I can reproduce this specific issue. I've tested both date & time widgets and they look good for me... can you check it again and/or explain the issue in more details?

@henry2man If you change more then one value it will only save the last changed value.
You can test it in the demo


Add a list of external examples and tutorials in reference documentation

External tutorials and examples are of varying quality and some are outdated. We should have a section in the refdoc pointing users to high quality external tutorials, such as the Josh Long's 8-part series.

@saturnism We are leaning towards not having this in the github repo.
Is there a better place for this, like google.dev?

Let's chat w/ Dave Holmes.  Alternatively we can also create an awesome list, or have this in https://spring.io/projects/spring-cloud-gcp ?


Infinity Wallet - A one-stop DeFi, NFT & Web3 Wallet, with first ever Web3 Browser!

Infinity Wallet
Grant category
Developer tools / services
Description
Infinity Wallet is the first non-browser-extension, all-in-one non-custodial wallet ecosystem of its kind on desktop, supporting over 170,000 users within August. Providing a one-stop solution for seamless usability of DeFi, NFTs and easy cross-border payments, with a gateway to the world of Web3/DApps directly within the wallet’s Web3 browser. Fulfilling all a user's needs, while removing the complexities of decentralized finance and enabling economic freedom for everyone globally!
From day one, we have focused on enhancing and providing the best possible user experience and lowering the barrier to entry, to allow for streamlined and secure adoption of DeFi and Web3. Providing a world-class user experience with a seamless user interface, and a full spectrum of constantly growing features and services as a one-stop hub, delivering a more curated in-wallet experience. Making Infinity Wallet the complete solution for all crypto users’ needs, while making adoption and usage of cross-border payments, DeFi and Web3 easier than ever before.
Infinity Wallet is also the first desktop platform to provide users with access to the entire Web3 and DApp space without needing to leave their wallet, with the first Web3 browser and Web3/DApp store directly within the platform (https://docs.infinitywallet.io/infinity-wallet/features-and-notable-advancements/browser-less-dapps-and-web3). Finally removing the need to ever use unintuitive browser extension wallets again! Providing a far superior, safer and more natural user experience, with a range of unique advantages/benefits for users, DApps and chains alike, while enabling easier use and adoption.
We believe Flow will make a great addition to the Infinity Wallet and will be well received by both our and the Flow ecosystem’s users, which is why we have reached out to cooperate on this integration. As a multi-chain ecosystem we look to integrate and collaborate with chains that are innovating the space, to provide users (of Web3, DApps, DeFi, NFTs, etc.) with access to all of their crypto needs. Integrating chains across our wide range of features/services and supporting their web3 ecosystems (DApps & Tokens) is a consuming task however, hence why we can only integrate/support chains that are able to collaborate with us on supporting the integration via an integration grant.
A further introduction can also be found in our docs at https://docs.infinitywallet.io/

You can download the live Infinity Wallet for desktop (with mobile in the works), supporting Windows, Linux and Mac : https://infinitywallet.io/download
Link to our information deck, which will provide further information on the Infinity Wallet and its features and future plans. https://infinitywallet.io/docs/Infinity%20Wallet%20Deck.pdf
Link to our docs which will explain more in-depth certain features and our roadmap: https://docs.infinitywallet.io/ and mobile sneak peak https://docs.infinitywallet.io/infinity-wallet/devices/mobile-wallet-sneak-peaks
Link to more information along with a video on Browser-less Web3, allowing users to use any DApp directly within the Infinity Wallet, allowing for easier DApp discoverability/adoption:  https://docs.infinitywallet.io/infinity-wallet/features-and-notable-advancements/browser-less-dapps-and-web3
Problem/Solution statement
The problem today is that while wallets are the most fundamental component required for usage and adoption of DeFi, Web3, crypto payments, a chain and its ecosystem, they are one of the least well developed applications in the crypto ecosystem. Wallets currently act mainly as an interface, serving primarily as a transaction signing layer, with very limited functionality or direct features/services/protocols (users generally have to search, find, learn and interact with many different applications and services), and are generally lacking in basic UX, while providing very unprofessional, hard to use and aesthetically poor user interfaces. This has been sufficient for the early adopters in crypto, however, for the next billion users to onboard to DeFi and Web3, a more curated and high quality user experience is required.
Infinity Wallet steps in to fill this need, as a one-stop hub for all payment, DeFi, NFT and Web3 activity. Providing a unique solution with a full spectrum of services, features and protocols in a premium platform, with a focus on delivering a seamless decentralized user experience and a user centric interface. Streamlining accessibility and lowering the barrier to entry, to allow for true adoption of DeFi, crypto payments & Web 3.0 globally.
Currently Flow greatly lacks a premium quality platform of our kind, delivering an all-in-one ecosystem that provides multiple unique services/protocols, along with a premium user interface and high end user experience that we deliver, which is generally lacking within most ecosystems today and holding back global adoption.
Additionally, as the first ever desktop Web3 browser, we bring a unique more natural user experience and value to any chain integrated when accessing DApps and Web3 (compared to browser-extensions), along with all our other unique features and services, hundreds of thousands of users and constantly growing user base.
Impact
Infinity Wallet will benefit the Flow ecosystem and holders by providing a unique all-in-one wallet & ecosystem solution on Desktop (with mobile to come in the future), with a focus on premium quality. Delivering a seamless user experience and a user-centric interface, along with access to current and a wide range of constantly growing features/services. Providing Flow  access to the many advancements we have, bringing much needed value (infrastructure, features/services and a premium quality platform) to Flow.
Infinity Wallet will allow Flow and its ecosystem to be more easily adopted and used by the general public, in a unique crypto wallet, payment solution and Web3/DApp browser built for the masses, and used already by hundreds of thousands of users worldwide for easy cross-border payments, access to DeFi, NFTs and interacting with Web3/DApps directly within their wallet. As a one-stop platform for all users to directly access all their DeFi, Web3 and crypto needs, making adoption of the Flow ecosystem as easy and intuitive as possible and boosting awareness, usage and utility.
Below are some of the key features and services that chains are already benefiting from within Infinity Wallet and that could benefit and bring value to Flow:

DeFi Wallet Solution;

Portfolio and Analytics Monitoring/Dashboard;

Instant decentralized cross-border payments;

Web3 browser and DApp store (One-click Connect to DApps, with the utmost discoverability and use of a chains’ ecosystem);

Cross-chain swap and bridge (Swap/Bridge between multiple supported chains);

NFT support to manage (view, send and receive) and trade NFTs;

Advanced Transaction History and balance/value charts;

Custom Token Importing (Allowing any token to be imported, even if not default supported);

For a more detailed look over our many current and future features/services please see our information deck available at https://infinitywallet.io/docs/Infinity Wallet Deck.pdf (pages 10-24 list core features/services and roadmap), or our docs here https://docs.infinitywallet.io/infinity-wallet/features-and-notable-advancements (detailing further information on core features/services and secondary features, as well as our roadmap)
Milestones and funding
The goal of this grant would be the complete integration of Flow into Infinity Wallet, to allow users to easily interact with Flow and its ecosystem, while also providing access to a wide range of Infinity Wallet features/services/protocols that will support and drive utility and value to Flow. To provide unparalleled ease of use and adoption of Flow and access to a vast user base of over 170,000 users within August and growing, bringing constant free marketing, awareness and adoption.
We would be requesting $160,000 in FLOW (or alternatively USDC/USDT) as a single milestone, deliverable after the live launch of FLOW within the Infinity Wallet.
The timeline for integration/development/testing would take around 8 weeks from start to live launch. While ongoing expenses (future developments/features, maintenance, live chain support, ecosystem support, ongoing operational costs, marketing, and etc.) will be covered at our own expense, providing Flow with access to constant free resources and users.
We would negate all risk for FLOW by operating via a single milestone for the grant, which would be the complete integration and live launch of FLOW in the Infinity Wallet. This expedites the process and allows us to focus on fully completing the developments and launch, before receiving any payment.
While we operate via a single milestone, you can find our internal milestones/deliverables below to give a deeper insight into our process and to help describe what to expect:
Milestone 1 -

Flow chain integration and core functions (balance tracking, send, receive, etc);
Complete transaction history with advanced information;
Integrate portfolio & analytics support;
Ability to import/remove tokens;

Milestone 2 -

Web3 Browser integration/development to allow for seamless one-click connecting to FLOW Web3 projects and DApps;
Web3/DApp Store to allow for easy discoverability and adoption of FLOW ecosystem projects;
Send/Receive NFTs;
NFT Gallery to view all NFTs;
Individual NFT viewing with stats and easy trading;

Milestone 3 -

Cross-chain swap support for FLOW (Allowing users to directly onboard to FLOW from different chains “BTC, ETH, BSC and etc” within a single click);
Contact/Address book;
Payment requests;
Desktop drag and drop QR scan;
Live Market stats;
Price Alerts;

Milestone 4 -

Internal testing of the integration;
Internal auditing of the integration developments;
Push the live release with the FLOW integration;
Support FLOW as a default chain;
Announcements across all social channels;
Creation of a custom FLOW web page on the website;
Announcement in the wallet of the integration of FLOW;

Ecosystem Support

Collaborate with FLOW ecosystem projects on direct integration into the Infinity Wallet;
Waive our usual yearly DApp fee that we would generally charge ecosystem projects (usually $5,000 a project, as an example 20 DApp integrations would usually be $100,000 in yearly fees.) to be integrated into the Infinity Wallet, we will integrate FLOW Web3 Project and DApps for free for the first year. Allowing them to be freely integrated into the Infinity Wallet Web3 Browser and DApp store, driving further awareness and growth to the Flow Ecosystem
Integrate top FLOW tokens as default supported tokens, removing the need for users to manually import tokens;

On completion we will have free ongoing development support for FLOW into future available features/services on a case by case basis, as well as the free integration into our unique user focused mobile launch. Along with continued ecosystem collaboration/support for FLOW in the Infinity Wallet.
Team
Information on our team, location, experience and goals can be found at the following link https://docs.google.com/document/d/19L9fGt241UVQlXxUtbx7BqkhCFxS6DzlFYu7svtUCi4/edit?usp=sharing
Contact Information
Contact Email<EMAIL_ADDRESS>Telegram Contact: https://t.me/aron_infinity
Note
We created this application as it seems the original application (https://github.com/onflow/developer-grants/issues/86) that we have now closed was missed along with other applicant's applications that were submitted at the same time, and we had not heard back after 1.5 months that the application was being reviewed as others had.

@InfinityWallet Thanks for opening a new issue for your proposal!  I'm going to close this one out since I've re-opened #86 to keep that as the source of truth.


Code quality fix - Dead stores should be removed.

This pull request is focused on resolving occurrences of Sonar rule
squid:S1854 - Dead stores should be removed.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1854
Please let me know if you have any questions.
Faisal Hameed

Current coverage is 93.36%

Merging #32 into master will decrease coverage by -0.18% as of b5cdb45

@@            master     #32   diff @@
======================================
  Files           80      80
  Stmts         3082    3074     -8
  Branches       285     285
  Methods          0       0
======================================
- Hit           2883    2870    -13
+ Partial         98      97     -1
- Missed         101     107     +6

Review entire Coverage Diff as of b5cdb45

Powered by Codecov. Updated on successful CI builds.

Have some concerns on the local variable init, close it now but we may continue to discuss offline. Thanks so much @faisal-hameed for your check and help!


Bluetooth: userchan: Support TCP fragmentation of HCI packets

Keep reading from the HCI socket when a packet is incomplete. The other end may not write entire packets, or TCP could fragment in the middle of a packet.
Also fix a potential infinite loop by advancing to the next packet before any continue statements.

That code is also used in native_sim for TCP hci emulation. e.g.
west build -b native_sim samples/bluetooth/peripheral
build/zephyr/zephyr.exe --bt-dev=<IP_ADDRESS>:9123

@patstew thanks for the clarification. I had completely forgotten that our userchan driver had been extended with TCP support (curiously, even though I was the assignee in the original feature PR, it got merged without my approval). Btw, I think we might want to consider renaming the driver since its name still implies that it's only about user channel sockets.

CC @vChavezB

Just added two comments on the changes. They are minor details but hope they help. Thanks for the contribution 👍  I am happy to know that other users are taking advantage of connecting Zephyr applications to other external controllers.

Looks good to me, I think you just need to await feedback from the code owners or collaborators of the project.

I'd like the stale label removed (and for someone else to review it)


Add Ninsight TX Details to bch-api

This is a specific task that is associated with this top level task
The scope of this task is to port the BITBOX.Transaction.details() function to the Ninsight library in bch-js.
Porting the code should meet the following requirements:

The code should follow the same pattern as the existing utxo() method, but should only use the POST call to the REST API. This should include api-doc documentation.
A mainnet integration test should be included. You can follow the same pattern of the utxo mainnet integration test
A testnet integration test should be included. You can follow the same pattern of the utox testnet integration test
A unit test with mocking should be included. You can follow the same pattern of the utxo unit test

Acceptance Criteria
The bounty will be paid out upon successful acceptance of a Pull Request (PR) into this repository. The PR must include the following:

Add a txDetails() method to the Ninsight class library.
The new method should include api-doc documentation.
Add mainnet integration tests
Add testnet integration tests
Add unit tests

Created Trello task

200 PSF tokens awarded for Ninsight tx-details endpoint added to bch-js. TXID:
44dfaa8fe9cc056a201c4d8108f37edbf1025d370db9f07f5b991f98acf52050


I think first you need to fix all the blocks above which the TODO section

There are too many of them in the code.
You can find them with grep -R
Next, you need to think about how to adapt it for ordinary people by analogy with React.
Regards

I read @isopen on facebook https://github.com/facebook/react/issues/12783
Became completely incomprehensible reasons why the @isopen account is locked in tdlib.
Please unblock it here so that he can write new bug reports about tdlib.
For a long time do not answer...

@isopen, if you want to write a bug report or something else about TDLib, you can always do that through @tdlib_bot.

@levlam user @isopen is now busy with work.
I tried to check the bot. He does not understand the subtleties of thought. His answers are not good enough. Your answers are better.


networkd units not supported in ign-converter

Description
There was a bug report on Matrix that networkd units in a v2 config didn't get translated to v3 by ign-converter (i.e., when our Ignition sees a v2 config and lifts it to v3 internally).
Impact
Either broken networking or the instance fails to boot? Didn't check
Environment and steps to reproduce
Expected behavior
The v2 networkd unit (either a unit file or a drop-in) should be converted to a plain file entry in v3.
Additional information

as a follow-up action, we should update our doc to reflect this breaking change (like: https://www.flatcar.org/docs/latest/provisioning/ignition/network-configuration/)

PR has been merged - and the fix should be available in the next beta / alpha release.


[AUTOPATCHER-CORE] Patched python-cryptography to address CVE-2023-49083

[AUTOPATCHER-CORE] Patched python-cryptography to address CVE-2023-49083
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=467060&view=results
buddy build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=467073&view=results

There is a PR for this on fasttrack :)
I think this PR can be closed. Once the PR is merged into fasttrack, it can be cherry picked into main


[es-dev-server] Rollup error on Mac

Mac: 10.14.16
Node: 13.6.0
Creating a new Web Component using npm init @open-wc and running gives errors on Mac.
How Do We Reproduce?
npm init @open-wc, install and then npm start, on Mac.
Expected Behavior
ES Dev Server starts and runs
Actual Behavior
Rollup throws an error:
[es-dev-server] Error: No valid exports main found for '~/rollup-bug/node_modules/@rollup/pluginutils'
[es-dev-server]     at resolveExportsTarget (internal/modules/cjs/loader.js:625:9)
[es-dev-server]     at applyExports (internal/modules/cjs/loader.js:502:14)
[es-dev-server]     at resolveExports (internal/modules/cjs/loader.js:551:12)
[es-dev-server]     at Function.Module._findPath (internal/modules/cjs/loader.js:657:22)
[es-dev-server]     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:960:27)
[es-dev-server]     at Function.Module._load (internal/modules/cjs/loader.js:855:27)
[es-dev-server]     at Module.require (internal/modules/cjs/loader.js:1033:19)
[es-dev-server]     at require (internal/modules/cjs/helpers.js:72:18)
[es-dev-server]     at Object.<anonymous> (~/rollup-bug/node_modules/@rollup/plugin-node-resolve/dist/index.js:11:19)
[es-dev-server]     at Module._compile (internal/modules/cjs/loader.js:1144:30) {
[es-dev-server]   code: 'MODULE_NOT_FOUND'

I did do some digging and there is a change between rollup/pluginutils 3.0.10 and 3.1.0:
https://github.com/rollup/plugins/commit/c5991820e01a773ceefb6c47b5a1e312c1708892#diff-25bff1ad7bb1f51c74707c56d8efd3f0
Forcibly setting rollup/pluginutils to 3.0.10 results in no error.

Thanks for filing the issue. I can't reproduce this myself, but I see that there have been a lot of changes around this are.
I updated the rollup dependencies to the latest in https://github.com/open-wc/open-wc/pull/1702, can you try again?

Having some issues in the CI, looking into that.

@LarsDenBakker pulling that PR and using the es-dev-server package runs without issue for me

@LarsDenBakker sorry, was still pointing to my modified build using older rollup, it still fails


Setuptools dependencies not resolved

Details

Project URL: http://readthedocs.org/projects/conkit
Build URL (if applicable): http://readthedocs.org/projects/conkit/builds/5215948/
Read the Docs username (if applicable): fsimkovic

Expected Result
http://readthedocs.org/projects/conkit/builds/5194902/
Actual Result
http://readthedocs.org/projects/conkit/builds/5215948/
The step python setup.py install --force does not resolve the dependencies of the required packages and thus building terminates. This worked previously and no changes to the dependencies, setup.py or conf.py file were made.

The problem lies with scikit-learn not specifying its install_requires requirements. The issue is discussed and referenced in scikit-learn/scikit-learn#4164.


Undefined name 'repo_url' in core/utils/git.py

https://github.com/giovanifss/Gitmails/blob/master/core/utils/git.py#L52
Should this be repo.url instead of repo_url?
flake8 testing of https://github.com/giovanifss/Gitmails on Python 3.6.3
$ flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics
./core/utils/git.py:52:60: F821 undefined name 'repo_url'
                Helpers.print_success("Clonning {}".format(repo_url))
                                                           ^
1     F821 undefined name 'repo_url'
1

Yeah, it should. Great catch, thanks. Also, that was a mistake in the string format in https://github.com/giovanifss/Gitmails/blob/master/core/utils/git.py#L38, there was no mask for repo_path.


Add manifest for Cargoflash.Octogo version 1.0.0

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Cargoflash/Octogo/releases/download/v1.0.0/Octogo-Installer.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 898)


fix: upgrade to version 3.1.216

from: https://github.com/jenkins-x/jx-cli

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

Needs approval from an approver in each of these files:

OWNERS

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

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
8d8ce0b3d31fb4d07da45ad8cf182095067d0db6
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
8d8ce0b3d31fb4d07da45ad8cf182095067d0db6
link
/test vault

gsm
8d8ce0b3d31fb4d07da45ad8cf182095067d0db6
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
8d8ce0b3d31fb4d07da45ad8cf182095067d0db6
link
/test vault

gsm
8d8ce0b3d31fb4d07da45ad8cf182095067d0db6
link
/test gsm

tls
8d8ce0b3d31fb4d07da45ad8cf182095067d0db6
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest


⚠ Jenkins Plugins Artifactory has degraded performance

In 915a7bd, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1327 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 92ecab3 after 12 minutes.


link style in docs: github vs yard

I just came accross this issue on yard https://github.com/lsegal/yard/issues/1017
Basically github requires this style of link [changelog](CHANGELOG.md) but yard requires this {file:CHANGELOG.md}
I changed the links in the readme to work on github in pr https://github.com/ruby-rdf/spira/pull/53
Now the link works in the github readme, but it's broken in the docs on rubygems.
If you go to the readme on rubygems and follow the link to the changelog, you'll get a not found error for changes.md
Do you think the fix provided in the issue would make sense for spira?
Or should we choose between github or yard style links?

Makes sense to me, I'll revert that link


mention h-Farm in the project Readme

mention h-Farm in the project Readme

fixed in https://github.com/Lollo003/TestRepo1/commit/1b0f591ef19bb77c8642e1422b9262ee1c82019a


Add a wiki: PinataIsland.info

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://vivapinata.fandom.com/wiki/Viva_Piñata_Wiki
Link to destination (independent) wiki: https://pinataisland.info/viva/Main_Page

Fandom has 1,000+ articles and is active, vs. 556 articles and inactive.


Zephir stubs remove slash from \Exception class when extending

If an class extends \Exception it will result the slash will be removed
Phalcon\Collection\Exception
Source

/**
 * This file is part of the Phalcon Framework.
 *
 * (c) Phalcon Team<EMAIL_ADDRESS> *
 * For the full copyright and license information, please view the LICENSE.txt
 * file that was distributed with this source code.
 */

namespace Phalcon\Collection;

use Throwable;

/**
 * Exceptions for the Collection object
 */
class Exception extends \Exception implements Throwable
{
}

Generated stubs
<?php

namespace Phalcon\Collection;

/**
 * Exceptions for the Collection object
 */
class Exception extends Exception implements \Throwable
{

}

This happens also in Phalcon\Exception
Related to https://github.com/phalcon/ide-stubs/issues/25

Fixed in the development branch. Feel free to open a new issue if the problem appears again. Thank you for the bug report.

Fixed in the development branch. Feel free to open a new issue if the problem appears again. Thank you for the bug report.


GetzOSListRealm() API function

This is a new API function.
When writing a nice FTP Client GUI for file system navigation in z/OS, one comes across the problem of "What is the z/OS realm of the filesystem path described by the current working directory".
For a unix like filesystem, the realm is of course unix and such a function is not needed.
But for a z/OS, a specialised function can make things easier.
The currrent working directory on z/OS either begins with a /, which tells us: realm is HFS.
Otherwise, it must be one of the z/OS (aka MVS) realms. But which one?
Short of doing a LIST command (which would be one way to do this), this makes use of a nice z/OS FTP server feature: When you CWD to an arbitrary path, if that path denotes a partitioned dataset, your are told that this is the case.
This means you can determine the realm of a z/OS path WITHOUT performing a LIST.
An alternative in terms of coding this would be to perform a LIST on the path and to analyze the results, perhaps by calling the dirlist parser.  But such a LIST might be huge, so that approach should be avoided.

I will add some docs in the next days.

I have some ideas to make this more "server relevant". Please stand by and don't merge.

Outstanding work! Added to wiki under API section.

Released!! https://www.nuget.org/packages/FluentFTP/35.1.0
Great work my friend and thank you a metric ton for this excellent work on supporting IBM z/OS for FluentFTP. You have my gratitude and my respect. Have a great day1


frontends/verific/verific.cc:46:11: fatal error: vhdl_file.h

Hi
I get the following error when trying to compile Yosys with ENBALE_VERIFC = 1
frontends/verific/verific.cc:46:11: fatal error: vhdl_file.h: No such file or directory
#include "vhdl_file.h"
^~~~~~~~~~~~~
compilation terminated.
Makefile:709: recipe for target 'frontends/verific/verific.o' failed
make: *** [frontends/verific/verific.o] Error 1
make: *** Waiting for unfinished jobs....

The Verific support will only work with YosysHQ version of Verific.  If you have a YosysHQ support contract, please contact us via support channels.  Combining yosys with any other version of Verific is unsupported and will result in multiple known issues.


Bump dependencies

A few minor bumps, and one major: We were several years out of date, having missed that the groupId of cucumber artifacts had changed :-)
@jdubois
I would also like to propose keeping the versions of jhipster-dependencies and -framework in both this repo as well as the generator on a SNAPSHOT -- and only change it to "real" versions just before a release. That way we don't use up quite so many minor versions which only serve to communicate changes to build/develop iterations in between "proper" releases.
Does that make sense, or have been misunderstanding your intentions here?
Cf., this depends on this generator PR.
I'll cancel Travis: it will fail because of mutually dependent changes, see here for passing tests where both generator and server-lib PRs are applied:
https://travis-ci.org/erikkemperman/generator-jhipster/builds/385069631
https://travis-ci.org/erikkemperman/jhipster/builds/385070081

OK this all makes sense to me, let's try this

I restarted all builds this morning.
Everything is green!
@erikkemperman : FYI, Spring Cloud Finchley RC2 has been released yesterday: https://spring.io/blog/2018/05/29/spring-cloud-finchley-rc2-has-been-released

Finchley.RC2 is based on Spring Boot 2.0.2.

I think we should upgrade. What do you think?

@pascalgrimaud Damn! I checked a couple of times the last few days -- including just before I pushed my branch, at that point it was something like 9 days overdue, but I didn't want to wait for it. Yeah, I'll make a new PR, we definitely want RC2 (RELEASE is scheduled for June 13, but it might get delayed as well, probably that shouldn't block JH5).
About those failing Travis builds, I checked a few logs and it seems the Yarn registry is unreliable. I noticed that before. Do we still want to default to Yarn? NPM has caught up, pretty much. In any case, maybe we should prefer the NPM registry even with Yarn client?
https://yarnpkg.com/en/docs/cli/config/

Yes let's upgrade

@jdubois Done, https://github.com/jhipster/jhipster/pull/72


Make RSS3 index data submmited on Arweave

Motivation
We realize that all data submitted on Arweave can be natively verified the ownership, thanks to the owner and signature attributes on its tx data. While RSS3 is an information distributed protocol incorporated with data ownership verification, it's nature to think about bridging the data between RSS3 and Arweave, to liberate the information flow as much as possible as well as flourish the Web3.0 ecosystem.
Proposal
Here we propose an automatic crawler to crawl the txs on Arweave, using ArQL probably. The crawler only focuses on some specific tags patterns, defined by Arweave-based applications implementation, specifically, by how the data is uploaded. Then the crawler on RSS3 side can generate the RSS3 files for each user who has been indexed and distribute it on RSS3 network. In such way, the information is generated on Arweave, but distributed on RSS3.
Roadmap
Such a "bridge crawler" is generally made up of two components: a crawler on Arweave, and the other RSS3 base stuff. For the crawler,  it shall be implemented in a centralized way at the beginning for POC purpose, but supposed to be in a decentralized way eventually, eg. like the Graph. And for the other RSS3 base stuff, we believe it would grow up along with the RSS3 protocol itself step by step.

That's a great proposal that is good for both Arweave and RSS3 in the matter of indexing. What I would add to this enhancement proposal is to use Arweave GraphQL instead of ArQL which is much faster in data retrieving.

That's a great proposal that is good for both Arweave and RSS3 in the matter of indexing. But what I would add to this enhancement proposal is to use Arweave GraphQL instead of ArQL which is much faster in data retrieving.

Thanks for your suggestion! We'd love to dig into it.


Timesheet - 19/04/2021 - Mr. K

Task 1
Landing page - HiFi Design - Responsive Design
Worked on the responsive dropdown, menus, and icons.
Proof of Work

https://www.figma.com/file/JCGeIX9fFrrpZiqE0XzH9s/Homepage?node-id=3%3A0

Time Spent
2.0 hours
Account Number
c93ee24b89991a1438b45444cf06e5bb167ed1796d54a800174def4480f98ed0

Approved

Approved


Extraction failed

Hi, this url
https://hnonline.sk/svet/2306911-zufala-doba-si-ziada-zufale-ciny-krajina-je-ochotna-za-vakciny-menit-aj-zdravotnikov
not scrapet.
Error in html-minifier. This package updated 2 years ago . Would it be better to use another minifier ?  For example minify ?

@ShepDogSk the content from hnonline.sk doesn't show entirely by default, so article-parser could not extract. The cause does not relate to html-minifier.
However I've replaced html-minifier with html-minifier-terser as better maintenance.
Feel free to reopen if needed.


Problems with Imbalanced Dataset Notebook

Hey Team,
I have recently started using creme to explore incremental learning as a part of one of my projects at my company. However, while I am trying to follow the steps mentioned in imbalanced-learning.ipynb, I am facing the following issues:-

datasets.CreditCard() - throws "AttributeError". Possible solution is to use datasets.fetch_credit_card()

counts = collections.Counter(y for _, y in X_y) throws invalid literal for int() with base 10: '1e+05' error. A possible workaround is to change line number 265 x[i] = t(x[i]) in stream.py to x[i] = t(float(x[i]))

model_selection.progressive_val_score(X_y, model, metric, print_every=15_000, show_time=True) also throws "AttributeError"

Possible solution is to use model_selection.online_score(X_y, model, metric, print_every=15_000)

while executing model_selection.online_score(X_y, model, metric, print_every=15_000) "StopIteration" pops up. I tried looking for a possible solution but I am not sure here should the changes be made in order to make it work.

Please help me out with this?
Creme version: 0.4.4
Thanks
Shaksham

Hey there! That notebook is using code that is only available on master. To make it work you have to install the latest development version. If all goes to plan we will be releasing version 0.5 somewhere during April.
Sent with GitHawk

@shaksham95, version 0.5.0 is now available :)


Packet type (bit 3) and secondary header flag (bit 4) appear to be swapped in your API?

@robamu
@JakobMeier
Hi ~ My understanding per the standard is that packet_type should correlate to bit three and sec_header_flag should correlate to bit four. However, w/ your API it's as if you've got these two swapped around. Hopefully, I've misinterpreted something.
Here's how to replicate my findings. As you'll see below, when I set packet_type to 1 then bit 4 will flip and when I set secondary header flag to 1 then bit 3 will flip.
#
# TEST PACKET TYPE
#

# Lets set packet_type to one, and leave everything else set to 0
>>> hdr = SpacePacketHeader(packet_type=1,apid=0,seq_count=0,data_len=0,sec_header_flag=0, seq_flags=0)

# here we see that bit 4 is set
>>> print(','.join([bin(i) for i in hdr.pack()]))
0b10000,0b0,0b0,0b0,0b0,0b0

# here is what I think it should be
0b1000,0b0,0b0,0b0,0b0,0b0

#
# TEST SECONDARY HEADER FLAG
#

# Lets set sec_header_flag to one and leave everything else set to 0
>>> hdr = SpacePacketHeader(packet_type=0,apid=0,seq_count=0,data_len=0,sec_header_flag=1, seq_flags=0)

# here we see that bit 3 is set
>>> print(','.join([bin(i) for i in hdr.pack()]))
0b1000,0b0,0b0,0b0,0b0,0b0

# here is what I think it should be
0b10000,0b0,0b0,0b0,0b0,0b0

I doubt my environment matters but to be thorough here is my complete setup on my laptop including package version, python version, and operating system information.
☕ ❯ pip3 show spacepackets
Name: spacepackets
Version: 0.22.0
Summary: Various CCSDS and ECSS packet implementations
Home-page:
Author:
Author-email: Robin Mueller<EMAIL_ADDRESS>License: Apache-2.0
Location: /home/shane/.local/lib/python3.10/site-packages
Requires: crcmod, deprecation
Required-by:

☕ ❯ python3 --version
Python 3.10.12

☕ ❯ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

The output looks correct. The primary header fields are placed contiguously, with the first 3 bits (bit 0 to 2) being the version number, then bit 3 as packet type and bit 4 as secondary header flag.
The first byte is 0b00010000 for the first example , so bit 3 is one, which is correct.

@rogueWookie Does this answer your question?


MODCLUSTER-561 Upgrade maven-war-plugin to version compatible with JDK 9

Jira
https://issues.jboss.org/browse/MODCLUSTER-561
https://issues.jboss.org/browse/MODCLUSTER-586
Now mod_cluster builds on JDK9 including the demo!

Merged 🙈

@Karm bit of a premature merge. All fixes required for support branches need to be merged before upstream can be merged. Since we need to support JDK9 for 1.3 branch, it needs to be merged first.

Opened https://github.com/modcluster/mod_cluster/pull/259 for 1.3.

Also, Jiras need to be resolved upon merge.

Ok, the mess  is cleaned up now.

@rhusar  O.K. THX.
This caught my eye though:

Since we need to support JDK9 for 1.3 branch

Hmm, do we? I was under the impression we were going to release 2.0.0.Final for

Tomcat 8.5
Wildfly 11.something

but from your comment, it seems we are stuck on 1.3.x until

Tomcat 9
Wildfly 12

Could you elaborate more? Perhaps in an article on JBoss forum?

@rhusar
Ad

All fixes required for support branches need to be merged

Fix version/s field needs updating I guess:
https://issues.jboss.org/browse/MODCLUSTER-586

Fix version/s field needs updating I guess:
https://issues.jboss.org/browse/MODCLUSTER-586

No, this was not backported as its not needed

Hmm, do we? I was under the impression we were going to release 2.0.0.Final for
I am afraid we don't have a concrete timeline yet.


[BugFix] Fix FE dead lock bug where db lock and TabletInvertedIndex lock waiting for each other

backport #30703

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:disappointed: fail : 3 / 22 (13.64%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/leader/ReportHandler.java
0
18
00.00%
[995, 997, 998, 999, 1000, 1004, 1005, 1006, 1010, 1011, 1012, 1015, 1017, 1018, 1022, 1025, 1026, 1028]

:large_blue_circle:
com/starrocks/catalog/TabletInvertedIndex.java
3
4
75.00%
[219]

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)


create error page

It should say
'“Oops! That page couldn’t be found. Would you like to check out some methods?”'
and link to the homepage.


Fixed retain all issue

This change is

https://github.com/canoo/dolphin-platform/issues/29

Coverage increased (+0.001%) to 54.32% when pulling 8e2da2a9e5eb5370e3a3d1f394e3a76e192a54e2 on ObserverableArrayListRetainAllIsNotWorking into c7313367e6b51bc8dab57f0e887096b2179405b2 on master.


DBT relationship test does not correctly support column quoting

Describe the bug
When defining a relationship test (In this case between Person and Invitation) the generated DBT test does not link the relationship back to the destination table column definition.  Hence, it does not recognise that a column in a relationship test may require quoting.
Steps To Reproduce
With a Source as follows:

The following test is generated, incorrectly leaving the quotes off the column named Id in the generated sql test.

The following error occurs:

Expected behavior
I would expect DBT to link the column with the definition and respect the quoting setting chosen.
For convenience, it may be useful to also add column quoting configuration at the model and source level.
Screenshots and log output
As above
System information
Which database are you using dbt with?

[ x] postgres
[ ] redshift
[ ] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.16.1
   latest version: 0.16.1

The operating system you're using:
Mac
The output of python --version:
Python 3.7.3
Additional context
A valid work-around  (via Drew) is to quote the Id column manually in the relationships test. You’ll need to use two sets of quotes — one to denote that the value is a string (for yaml) and the next to be passed into the SQL query.

I followed the thread to here before losing where the relationship test may be held:
https://github.com/fishtown-analytics/dbt/blob/dev/0.16.1/core/dbt/parser/schemas.py#L236-L273

Thanks for the detailed write-up @MarcelvanVliet!

I would expect DBT to link the column with the definition and respect the quoting setting chosen.
For convenience, it may be useful to also add column quoting configuration at the model and source level.

Currently, dbt supports project-level quoting configurations for relation namespaces: database, schema, and identifier. (There are specially scoped overrides for sources and seeds.)
There isn't a broad-purpose quoting configuration for columns; we tend to accomplish this in utility macros via adapter.quote, or by accessing the quoted attribute of get_columns_in_relation. We could add one; it would be a nontrivial amount of work to synchronize behavior across those macros, and quoting is always trickier than expected and especially liable to database idiosyncrasies.
We'd need to establish what exactly such a lift would get us, since (as you mention) there are workarounds available, albeit a bit funny looking.

@jtcohen6 I caught up with @MarcelvanVliet about this on Slack. I think it would be really great if we could leverage the quoting configs from these .yml files directly in the relationships test. I bet it would be a pretty big change two save exactly 4 keystrokes, but dbt should have all the info it needs to do the right thing here automatically!
So, this probably isn't something we'd hit in the immediate future, but I'd like to keep this issue open to track the change :)

Ah ok! That makes sense. I missed it in my first read-through.

I just tagged this a good first issue, as I think it'd be a fairly straightforward change. Hint: there's some prior work in #2733 that may be helpful :)

Noting that this doesn't just fail with relationships requiring quoting, but fails in general with any sources in Postgres.

@jordan8037310 Could you share the specific code snippet + error you're seeing? Not sure I follow fully

When running unique or not_null tests, the tests fail if there are column names e.g. "ipAddress".
Noting that the workaround does work, '"ipAddress"', but I think the scope of the testing for this issue should be expanded to include unique, not_null, and all of the other tests (not just relationship test as indicated in the issue title).
Error
Database Error in test source_unique_public_source_ip_whois_ipAddress (models/sources.schema.yml)
  column "ipaddress" does not exist
  LINE 10:         ipAddress
                   ^
  HINT:  Perhaps you meant to reference the column "source_ip_whois.ipAddress".

Copy of generated sql for the test:
select count(*) as validation_errors
from (

    select
        ipAddress

    from "facetlgp"."public"."source_ip_whois"
    where ipAddress is not null
    group by ipAddress
    having count(*) > 1

) validation_errors

@jordan8037310 Did you specify quote: true for ipAddress in your YAML file like:
sources:
  - name: public
    table: source_ip_whois
    columns:
      - name: ipAddress
        quote: true
        tests:
          - unique

?

@jtcohen6 - no, althought I just tested that and it works! Thanks.
Here are some things I tried. I mainly assumed that if I did applied the settings at the dbt_project.yml level it persisted down.
I tried putting it in at the dbt_project.yml for quoting with the following and it quoted everything in my project... except the sources.
quoting:
      schema: true
      identifier: true

After happening upon this thread, I saw that sources were handled differently so I tried:
# sources.schema.yml

version: 2

sources:
  - name: public
    schema: public
    loaded_at_field: '"updatedAt"'
    loader: serverless_framework
    quoting:
      schema: true
      identifier: true

To be honest I never once saw the quote parameter specified once in documentation when searching google "dbt sources quoting":

https://docs.getdbt.com/faqs/source-quotes/
https://docs.getdbt.com/reference/project-configs/quoting/
On page 1 of google this links to a 404 and should probably be redirected: https://dbt.readme.io/v0.10/docs/configuring-quoting

So perhaps this is more an issue of a hidden setting for me and documentation about quoting should be updated?

Really fair point. I guess I could've hoped that you would've magically stumbled upon https://docs.getdbt.com/reference/resource-properties/quote/.
Why do we call it quoting for database/schema/identifier names, but then quote for column names? Adding this to my list of nomenclature we might make more consistent in advance of dbt v1.0.

On page 1 of google this links to a 404 and should probably be redirected: https://dbt.readme.io/v0.10/docs/configuring-quoting

Oof, this is old.

@jtcohen6 +1 normalization of the property names would have made this easier to search and find.

There's also quote_columns, which is a seed-only config item that lives on its own level but surely belongs inside the quoting config item (or will it be quote?!) as columns 😬


Update Documentation: Add use cases for Notes

Codecov Report

Merging #268 (5185b5c) into master (4de776e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #268   +/-   ##
=========================================
  Coverage     57.69%   57.69%
  Complexity      835      835
=========================================
  Files           169      169
  Lines          3151     3151
  Branches        317      317
=========================================
  Hits           1818     1818
  Misses         1207     1207
  Partials        126      126

Continue to review full report at Codecov.

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


Get the IoU between predicted bounding boxes and GT.

What's the feature?
How can I get the IoU between the predicted bounding box and its corresponding GT when the model is inferred on the COCO minival set? Thanks!
Any other context?
No response

Try to use function: https://github.com/open-mmlab/mmdetection/blob/master/mmdet/core/evaluation/bbox_overlaps.py
Moreover, voc-type evaluation function will calculate IoUs, so you can have a look.


Quotes appearing in the GUI in french

Gitea version (or commit ref): 1.1.0

Description
Here is what I get in the GUI

There are "
Here is what there is into the translations

There is no "
There are quite a lot of places where " or ' or ` are added in the string, dunno why. Any idea?
Thks

Switching language to EN or ES: all the double quotes " disappear. So it seems to be related to the french translation

Same problem in German translation. Seems to be related to #1181

and should be fixed in #1177


Fix field data type

With Sails 10, timestamp with time zone fields are defined as datetime, not DATE.

Tests are good:
$ npm test

><EMAIL_ADDRESS>test /Users/davidcole/dev/sails-postgresql
> make test-integration

info: Testing `sails-postgresql`, a Sails/Waterline adapter.
info: Running `waterline-adapter-tests` against 4 interfaces...
info: ( semantic, queryable, migratable, associations )

debug: Latest draft of Waterline adapter interface spec:
debug: http://links.sailsjs.org/docs/plugins/adapters/interfaces

  ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
  ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․

  223 passing (3s)
  3 pending

time elapsed: 3681ms


revise visited_list_pool.h

some suggestions of revise reset function, hope it is useful.

Of course, you are right. If replace 65535 with std::numeric_limits, it should be better.In many case, USHRT_MAX = (short)-1, so your version usually is correct.  I test hnsw in MNIST dataset in my i7-6700 desktop, here are the results, HNSWBuilding index:efConstruction = 48, M = 16Build time: 1.606658stesting...ef=8, recall=0.959300, time=129.919msef=9, recall=0.960800, time=105.947msef=10, recall=0.961500, time=110.346msef=11, recall=0.961700, time=115.865msef=12, recall=0.961800, time=121.701msef=13, recall=0.963000, time=126.229msef=14, recall=0.963500, time=130.206msef=15, recall=0.963600, time=135.056msef=16, recall=0.964100, time=142.711msef=17, recall=0.964300, time=145.094msef=18, recall=0.965000, time=149.804msef=19, recall=0.964900, time=154.744msef=20, recall=0.965200, time=166.172msef=21, recall=0.965800, time=169.351msef=22, recall=0.965900, time=174.322msef=23, recall=0.966400, time=179.656msef=24, recall=0.966400, time=184.361msef=25, recall=0.966700, time=186.775msef=26, recall=0.967000, time=191.210msef=27, recall=0.967200, time=199.543msef=28, recall=0.966900, time=200.513msef=29, recall=0.967000, time=204.763msef=30, recall=0.967200, time=213.208msef=31, recall=0.967300, time=214.961msActual memory usage: 117Mb  KNN with K=39717/10000, time used:20.342s  We can find that HNSW is 12+ times faster than KNN even in a small dataset. Excellent work! And the usage of lock & mutex is impressive, simple but effective. I think this project is still in progress, for example, in addPoint function, "if the element with the same label already exists, it will be updated instead of creating a new element". like this: auto search = label_lookup_.find(label);   if (search != label_lookup_.end()) {   tableint existingInternalId = search->second;    templock_curr.unlock();    std::unique_lock std::mutex lock_el_update(link_list_update_locks_[(existingInternalId & (max_update_element_locks - 1))]);   updatePoint(data_point, existingInternalId, 1.0);   return existingInternalId;} This may not exactly what we want. May be it should like this: if (WHEN_WE_WANT && search != label_lookup_.end()) {   ...} Thank you.05.03.2021, 00:44, "Yury Malkov"<EMAIL_ADDRESS>@yurymalkov requested changes on this pull request.
Thank you! I think there might be problems if the data type is changed.
In hnswlib/visited_list_pool.h:

     }

     void reset() {

       curV++;

       if (curV == 0) {

           memset(mass, 0, sizeof(vl_type) * numelements);

       if(curV < 65535){ //avoid overflow of curV and mass (this will cause ambiguity)

I think it can go bad if vl_type changes (e.g. to a single byte, the number will be 255).
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you! Looks good to me!
Will merge it after we figure our why CI flag is not showing in github web interface.

Hi Yury,I newly put forward some requests. The follwing is the changelog. If you find some of them are useful, you can merge them anyway you like. If you think them are useless, just discard them. Thank you for your time.  changelog0316 1. add an indicator(bUpdate) at addPoint function, so it will only call updatePoint when we need.2. redefine CompareByFirst, let the smaller at the top, then we needn't use minus distance at std::priority_queue.3. revise VisitedList.4. use get_linklist_at_level to keep the code more tidy.5. add a simple example, it is tested under Linux.first, copy train-labels.idx1-ubyte, train-images.idx3-ubyte, t10k-labels.idx1-ubyte, t10k-images.idx3-ubyte to the same path of the executable file.then, run ./mnistit will look like this (we set k=1 here): efConstruction=48, M=16, vecdim=784Building index:Build time: 1.320725stesting...ef=8, recall=0.942000, time=83.650msef=9, recall=0.944700, time=89.679msef=10, recall=0.947100, time=93.547msef=11, recall=0.949000, time=116.838msef=12, recall=0.950700, time=104.603msef=13, recall=0.951600, time=111.117msef=14, recall=0.952500, time=115.467msef=15, recall=0.953300, time=120.319msef=16, recall=0.954000, time=124.361msef=17, recall=0.955600, time=148.542msef=18, recall=0.956300, time=154.498msef=19, recall=0.957100, time=138.762msef=20, recall=0.958000, time=142.354msef=21, recall=0.958500, time=150.261msef=22, recall=0.959100, time=150.379msef=23, recall=0.959900, time=154.988msef=24, recall=0.960700, time=159.845msef=25, recall=0.961100, time=177.775msef=26, recall=0.961700, time=167.215msef=27, recall=0.962100, time=171.925msef=28, recall=0.962700, time=179.467msef=29, recall=0.962800, time=179.995msef=30, recall=0.963100, time=184.014msef=31, recall=0.963800, time=188.360msActual memory usage: 115Mb I use an old desktop, if you have a new machine, it will be faster.15.03.2021, 11:20, "Yury Malkov" @.***>:
Thank you! Looks good to me!
Will merge it after we figure our why CI flag is not showing in github web interface.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Health bars

I kinda of like the retro feel of these screenshots.

This screenshot appears to be closer to the classic style for a beat-em-up.

Rough design.


Types in comprehensions

for obj in Objects:
    obj.

shows intellisense, this doesnt
[obj. for obj in Objects]

Should it be [obj. for obj in Objects]? Or you are typing nested fors?

Should it be [obj. for obj in Objects]? Or you are typing nested fors?

You are right, I corrected it

@MikhailArkhipov Do you confirm this is a bug?

Don't know yet, there are other issues in this sprint that need attention. Some time later this week I guess.

I observe basic example works. What is the Objects type?

@MikhailArkhipov
class K:
    a = 10
    b = 12
    def c(self, r):
        b = r
        return b
A = K()
AR = [A, A, A]
b = [a for a in AR]

Needs special handling since currently comprehension is not a scope and hence does not properly declare variables.


target sync committee aggregators to 16

@mcdee Did some quick math to show that the current configuration of TARGET_AGGREGATORS_PER_SYNC_SUBCOMMITTEE as 4 had an unacceptably high probability of sync committee subnets not having aggregators.
@hwwhww tossed the math and some options into this spreadsheet. Based on discussions, it looks like the choice of 16 is the right tradeoff to generally have a high chance of having at least one aggregator per slot, even on a daily basis.
Note, that 4 was naively selected to reduce chatter on yet another global channel, but assuming attestation aggregation is not already overwhelming, this increases global messages for ~6% (4 more 16 aggregator topics on top of the 64 attestation topics that also have 16 aggregator targets)

Thanks for the fix @hwwhww !

What does the restriction with (1) buy us?

What does the restriction with (1) buy us?

I was thinking that if we somehow update SYNC_COMMITTEE_SIZE or SYNC_COMMITTEE_SUBNET_COUNT  for other reasons, we would be notified to increase TARGET_AGGREGATORS_PER_SYNC_SUBCOMMITTEE if needs. However, I just tried other numbers on the spreadsheet, the TARGET_AGGREGATORS_PER_SYNC_SUBCOMMITTEE = 16 should have guaranteed a high chance of aggregator selections with different committee sizes. So, it's not "required". 😅

going to merge as is for now!
thanks


Create API for Viewing & Updating User Addresses

Notion card
https://www.notion.so/saeloun/6afc9500b2cc42af86be55f37894fb09?v=b4528f26f4424af7beaf036262796cb3&p=e312e4f0ceb849fda5f14eb05f8b2cf3
Summary
Create API for viewing & updating users' addresses. Address is a part of the Personal Details Page.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Using RSpec and Postman
Checklist:

[x] I have manually tested all workflows
[x] I have performed a self-review of my own code
[x] I have added automated tests for my code

Tested with Postman. Here are the responses for both GET and PATCH requests.

@akhilgkrishnan @harshaanNihal @keshavbiswa @gowsik-ragunath Please review this PR as soon as possible.

@mohinid Please resolve conflicts

@mohinid Please check review comments from Keshav

@keshavbiswa Hey, please review the changes. I have moved the addresses out of the team folder. Will update the other APIs as well once this is reviewed as the changes will be similar.

@keshavbiswa please check the policy file now.


Supporting consecutive STF_INST_MEM_CONTENT records

I have been hitting an issue when trying to encode memory accesses of greater than 8 bytes.
The specification says of STF_INST_MEM_CONTENT records:
For memory accesses with data size greater than 8 bytes, use multiple STF_INST_MEM_CONTENT records, where the first STF_INST_MEM_CONTENT record refers to the address specified in the STF_INST_MEM_ACCESS record, and subsequent STF_INST_MEM_CONTENT records refer to subsequent target addresses appropriately incremented to preserve continuity of data.

Trying this however, I triggered an assert in stf_lib, stf-inc/stf_inst_reader.hpp: 147
https://github.com/sparcians/stf_lib/blob/eb394e5a3fdffcf9ad4110f962f1df5134d95b1e/stf-inc/stf_inst_reader.hpp#L147
                    stf_assert(desc != IntDescriptor::STF_INST_MEM_CONTENT,
                               "Saw MemContentRecord without accompanying MemAccessRecord");

It seems like stf_lib currently only supports a single STF_INST_MEM_CONTENT record following a STF_INST_MEM_ACCESS.
stf_lib was happy if I break larger accesses into multiple smaller (64bit or less) accesses with STF_INST_MEM_ACCESS and STF_INST_MEM_CONTENT pairs, but this doesn't correctly reflect the access being performed.

Yes, this is a bug in the library. I'll start working on a fix for it.

Keeping this open until I've updated stf_tools with the latest stf_lib.

Ok, this should be fixed in the latest stf_tools master. Feel free to either reopen this issue or open one on stf_tools if you run into more problems with this.


Bump Horizon to version 2.21.0

@2opremio you have to promote package to stable. Build currently fails.


⚠ Bofrost.de has degraded performance

In 7c9ae66, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1569 ms

Resolved: Bofrost.de performance has improved in 50545d8 after 33 minutes.


Fix #265 - chmod ./app directory

Resolves #265

This PR was inadvertently deleted due to us getting rid of the old development branch (we came back to merging on good'ol master). Changing base branch to master and reopening.

@partyka1 rebase welcome, if you have the time for that :)


Add Contributing.md

We should create a Contributing.md outlining the basic steps before creating a PR. Should include all checks made by the github actions in order to avoid having to rebuild PRs multiple times.

Hey @LukasPrediger can i work on this?


Create a demo TODO APP with React / NextJS / Svelte / Vue

We built a demo repo to showcase the integration of Manifest with different frontend frameworks.
The demo is based on the popular TodoMVC website that compares the differents frameworks building the same todo app. In our use case we added a small Manifest backend with a db for persistant data:
name: My TODO App ✅
entities:
  Todo:
    seedCount: 10
    properties:
      - title
      - { name: completed, type: boolean }

We need now to create frontend examples based on the TodoMVC ones:

[ ] React
[ ] NextJS
[ ] Svelte
[ ] Vue
[ ] Other frontend ?

How to submit a demo

Clone the mnfst/frontend-examples repository
Install and checkout the angular implementation for inspiration
Go to TodoMVC Github and grab the framework that you are going to integrate
Copy it on the /examples folder and connect it to the backend
Make sure that there is an npm run dev script in the package.json
Make your PR in the  mnfst/frontend-examples mentionning this issue

Hi, I'd like to work on the React example!

I'd like to work under this issue

Hi @ChinoUkaegbu and @dawipayandas . Which frontend do you want to work with?
@brunobuddy FYI

I can work on React.

Just wondering what version of npm I should use for installing manifest. I'm getting a few errors when using Node.js v20.10.0 and I suspect it's as a result of that.

@ChinoUkaegbu can you send me a screenshot of your errors ?

@ChinoUkaegbu it is not tested on Windows, sorry.... Only Mac and Linux for now

@ChinoUkaegbu I just released a version that fixes that issue on Windows !

@LLxD yes !

Thanks! I'll continue working on the React example.

Got this error when trying to run the angular example :( Manifest installed without errors but running npm run dev is resulting in this:

Good news and bad news:
I got the manifest backend to work. Had to change the nodemonPath to end with nodemon.cmd instead of nodemon since that's the Windows specific executable for nodemon. Shown below:

I'm not sure how to modify the script to handle cross-platform compatibility? I think npx can handle that?
I'll work on the Angular error next but it still persisted

@ChinoUkaegbu sorry I did not explain to you that you had to get the latest version of the "manifest" package. I updated it on the "main" branch you can pull it and it should fix the issue

I believe I was working off the latest version. I pulled the changes before starting.

Hey @brunobuddy! Added a PR for the svelte example. Could you give it a check pls? ;)

.take

@LLxD yes I am going to have a look !

Awesome @brunobuddy! Feel free to reach me in case any questions appear ;)

Hello @brunobuddy I have implemented Vue and created a pull request, please check and let me know if any changes are required. Thank You !!!

@Ron1005 amazing, I will have a look next week !

@ChinoUkaegbu are you working on the react example ??
@brunobuddy do you mind if I work on the react example if @ChinoUkaegbu is not ??

Hi, I linked a PR for the React example but it hasn't been reviewed yet I believe

No worries

hello @ChinoUkaegbu your PR is sill in draft so I did not review it yet. If you think it's ready you can publish it !

@Ron1005 if you are up to you also can do the vanillaJS one

Oh my apologies, I marked it as a draft because I left some comments earlier but I've marked it as ready for review now!

@Ron1005 if you are up to you also can do the vanillaJS one

Sure I will give it a try

@brunobuddy I have opened another pull request to push changes for javascript-es6


Unify configs for different deployments

Description
Spring Boot has application.properties file designed to control the application without recompilation. Moreover, the values in application.properties can be overridden for different deployments without touching the filesystem/image - structurizr.editable=false for the publishing and structurizr.editable=true for editing.
structurizr.properties configuration file is excessive, and can be integrated into application.properties using the namespace structurizr.
Priority
I have no budget and there's no rush, please add this feature for free
More information
No response

The idea here is that the structurizr.properties file sits next to the workspace.dsl file, so you can have different Lite configurations for different folders/workspaces. I'm not sure I see the value in pushing that configuration to the Spring Boot configuration file.


Visit log entries are truncated that should probably be wrapped

In my relatively narrow browser window the visit log shows e.g. a last visit time of "5:15PM T.."
I was going to say there's no way to see the hidden info, but it turns out if I select and copy that truncated info, a paste will reveal the whole thing.  But this is too much work of course.  There are a few potential fixes:

wrap instead of truncate
show full entry in a tooltip or popup on hover
permit resizing of columns in the log table

(I wonder if it could be made shorter with "m minutes ago" / "d days ago")


Revert "Remove static_cast in AnimationSet data loading"

Reference: #920
This reverts commit<PHONE_NUMBER>0209d65aa5cb0c14ad2e6330e2344c.
Revert change that lead to a bug where "-1" is used as a sentinel value for frame delay and wasn't being handled correctly.

I may make more sense to use a sentinel value of 0 rather than -1 when there is no frameDelay. A frameDelay of 0 wouldn't already have a meaning.
Current definition:
const auto FRAME_PAUSE = unsigned(-1);

Existing code:
	if (!mPaused && (frame.frameDelay != FRAME_PAUSE))
	{
		while (frame.frameDelay > 0 && mTimer.accumulator() >= frame.frameDelay)
		{
			// ...

Actually, using 0 for the sentinel value might actually simplify the code.


preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated

Does this application not support using PHP 8.1? I just installed Shield and tried to use Email2Fa, and I got this error message. The description says that the error is in SYSTEMPATH\Email\Email.php at line 466.

This a screen shoot : https://im.ge/i/ufY3l6

hello @wangling97 ,
Shield also supports version PHP 8.1.
Your problem is related to not setting the values in the email configuration file.
Please set the values through file app\Config\Email.php.
<?php

namespace Config;

use CodeIgniter\Config\BaseConfig;

class Email extends BaseConfig
{

    /**
     * @var string
     */
    public $fromEmail =<EMAIL_ADDRESS>
    /**
     * @var string
     */
    public $fromName = 'your name';
}

and other cases

Can this be used with public email like gmail? and are there any special settings if using a private email server?

Can this be used with public email like gmail?

Yes, see https://github.com/codeigniter4/CodeIgniter4/issues/6217#issuecomment-1172887117

and are there any special settings if using a private email server?

Yes. see Email Preferences

I'm closing this since the originating error message wasn't even in this library. @wangling97 If you need more help please visit the CodeIgniter forums or Slack channel.

This seems to be a documentation problem.

Yes, I agree to update this item.
Additionally, I noticed that using settings to configure email does not work properly. Maybe we need to modify the email helper. In this regard, I am not sure whether it is a bug or my understanding of the settings is wrong.

I checked the code of Shield, but it seems okay because it uses settings() when sending emails.
Is it really a Shield issue?

Can you share the output of the following command (with sensitive information removed)?
php spark db:table settings

I just read the code, not actually try to save them in the database.

Well,
For example, I set the value to $SMTPUser below (app/Config/Email.php).
public $SMTPUser = 'p.parsa.dadashi...';

Everything works fine.
Now I change its value $SMTPUser below (app/Config/Email.php).
public $SMTPUser = '';

And I have the following values in the settings.
P:\Bug\4.3>php spark db:table settings

CodeIgniter v4.2.11 Command Line Tool - Server Time: 2022-12-25 09:19:43 UTC+00:00

Data of Table "settings":

+----+-------+----------+--------------------+--------+---------+--------------------+--------------------+
| id | class | key      | value              | type   | context | created_at         | updated_at         |
+----+-------+----------+--------------------+--------+---------+--------------------+--------------------+
| 1  | Email | SMTPUser | p.parsa.dadashi... | string |         | 2022-12-25 01:2... | 2022-12-25 01:2... |
+----+-------+----------+--------------------+--------+---------+--------------------+--------------------+

My guess is that it still works fine, but no email is sent.
What is in the configuration documents, the priority is as follows.
"Setting with a context > Setting without context > Config value > null"
Do I have a problem understanding the Setting ?

Do I have a problem understanding the Setting ?

No.
I think it should work.
email() function uses setting('Email.SMTPUser'):
https://github.com/codeigniter4/shield/blob/ca7335c717efcd4fadfc219cdb2c0a3bae758ae2/src/Helpers/email_helper.php#L22

I think it should work.

Oh @kenjis, I forgot to mention this. Everything works fine.
My problem was that I had customized email_helper.php.


.net CLI template

Would you be interested in maintaining a CLI template called "winservice" or something along those lines? This would probably require maintenance of a project and Nuget package, but I think it would get used a lot!
Reference: https://github.com/dotnet/templating

Same as the previous issue you opened, was busy but more than happy to do that, sounds like it can be useful to the community. In fact, I think with 100+ stars, the time has come to look into this again and add some new features. Will do the template as well

Taken care of in https://github.com/PeterKottas/DotNetCore.WindowsService/releases/tag/v1.0.20 .


Make trail icon, length and colour gradient configurable

I want to use it as a magic effect that follows my cursor, but it's too long and distracting at the moment.

@jendrummo try changing this variable https://github.com/GirkovArpa/cursor-heatmap-trail/blob/eb8968eeeb308a2fbb6442e218b4dcaec3830ef9/app/js/main.js#L17
I don't know if you could though, it seems that it packs as one executable. You can use the same code from this app with little modifications to run inside OBS Studio browser source, as a local file. I have cursor trails which use web technologies to render on transparent background. See - OBS-Studio-Cursor-skin , the web version requires Python to get mouse position from OS, there is also a shader based mouse trail which you try without installing anything assuming you are on Windows.


Get current version in markdown files

First of all, thanks a lot for this super-useful package!
I'm currently building a multi-version documentation, mostly written in Markdown using myst-parser. Everything works fine, except that I can't seem to be able to use substitutions (https://myst-parser.readthedocs.io/en/latest/syntax/optional.html#substitutions-with-jinja2) to access the current_version variable.
I've made sure that 'substitution' was in my myst_enable_extensions, and I've tried to use
{{ current_version.name }}

as well as
{{ env.config.current_version.name }}

but none of these are defined.
Is there a way to access this variable (defined in the HTML context)?
Thanks a lot!

Got the same question regarding current version in rst files.

Is this what you are looking for: https://holzhaus.github.io/sphinx-multiversion/master/context.html


when deployment hosted engine, step 3 : prepare vm failure

log  info:  fatal:[localhost]:FALED!=> msg: the  ovirt_host_facts module has been renamed to  ovirt_host_info，and the renamed one no longer returns ansible_facts
The deployment environment:  engine rpm version  :  ovirt-engine-appliance-4.3 、  OS : ovirt node 4.3.7

Hi @qsyhenu,
did you use the ovirt-4.3 branch?
https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/tree/ovirt-4.3

Closing it as there is no activity.
This role is deprecated, in case you still encounter problem deploying oVirt 4.4 please open an issue in ovirt-ansible-collection repo


Which gbm package is used?

Currently trying to package this for nixpkgs
We have rPackages.gbm which is gbm (the old version) on cran
https://cran.r-project.org/web/packages/gbm/
I'm not sure whether this is the right package
While compling I'm getting this error
/nix/store/0zcfsz4iy2p9ibm7i55xx550zkclf1f5-r-gbm-<IP_ADDRESS>/include/gbm.h:18:9: fatal error: vector: No such file or directory

which stems from the gbm.h file using c++ things when included from c.
I'm also not sure if I'm doing something wrong here

That's definitely the wrong gbm. The right one is provided by mesa.


0.7.1 release

0.7.1 release

Codecov Report

Merging #3234 (8893490) into main (3741278) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3234      +/-   ##
==========================================
- Coverage   82.35%   82.33%   -0.02%
==========================================
  Files          54       54
  Lines        6087     6087
==========================================
- Hits         5013     5012       -1
- Misses       1074     1075       +1

Files Changed
Coverage Δ

flax/version.py
100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes


Create workspace - Selected currecy does not appear selected with a green checkmark

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.73-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to Account settings > Workspaces
Click New workspace
Note that Currency field has currency selected
Click on the Currency field
Scroll down to the selected currency

Expected Result:
The selected currency will appear selected with a green checkmark
Actual Result:
The selected currecy does not appear selected with a green checkmark
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/10a71fe3-9207-4ab1-bf75-e2a1298a3f9b
View all open jobs on GitHub

coming from https://github.com/Expensify/App/pull/52164
cc. @Krishna2323

This is fixed in staging
https://github.com/user-attachments/assets/547cdc7a-3a8e-432c-abad-1d8871b88840


Rename the secret name for the credentials

This change is to keep the naming convention in sync with other providers.
ref: secretref's from https://github.com/openshift/machine-api-operator/blob/master/install/0000_30_machine-api-operator_00_credentials-request.yaml

/lgtm

/approve


FEATURE - Update slash command descriptions

Some /commands have a pretty short description, by adding some more text explaining what they do it can help people understand their meaning. This could be what parameters it takes, what the command does
Good first contribution if you haven't used GitHub before!

also could change the command names as they are inconsistent, maybe change everything to snake_case, and not snakecase?


revise changeLog for v1.2

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

/kind documentation
What this PR does / why we need it:
revise changeLog for v1.2
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/lgtm


[spdlog] Add feature for SPDLOG_USE_STD_FORMAT

Because our project makes heavy use of C++20 std::format and std::formatter, we would like to enable spdlog's option to use the  same std::format instead of  bringing fmt in as an external dependency.
Proposed solution
Add a feature for stdformat that:

Changes the configure options to:
a.  SPDLOG_FMT_EXTERNAL=OFF
b.  SPDLOG_USE_STD_FORMAT=ON
Uncomments the appropriate line in include/spdlog/tweakme.h

I'd really like to see this worked on again as the library I work on has support for vcpkg but dropping fmt as a dependency is currently impossible. The pr from LilyWangLL was closed last year for inactivity.

The pr from LilyWangLL was closed last year for inactivity.

IMO the PR couldn't continue because it implemented (and this issue requests) an anti-pattern: Choosing an alternative backend (std::format) without dropping a dependency (fmt).
Modeling alternatives in vcpkg is currently not possible except for some limited cases. What might be acceptable is modeling the choice of the fmt backend as a feature (with a proper port dependency) as long as this backend doesn't offer a different/reduced API. (Features must be additive.)
To cover pre-C++20 platforms, this would probably would need to be a default feature. Then users could opt-out of the dependency by using spdlog with "default-features": false. However, this only works if no other (used) ports apply pulls in the spdlog's default features.