Add derive macro for Collection

Collection currently has a lot of boilerplate code that could be reduced or eliminated by a derive macro. We should consider adding macros to help implement collections:

Collection Authority and Name can be set as parameters on the struct
DefaultSerialization can be auto-derived, or overridden with a parameter.
Views can be specified as a list of type names (e.g. [ByName, ...]).
We should consider #69 and determine if there is any way to support deriving Collection while still offering the lifecycle event implementations easily.

Originally posted by @ModProg in https://github.com/khonsulabs/bonsaidb/issues/106#issuecomment-1017519606
Maybe other things could also be derived like DefaultSerialization.
Maybe also Collection, but that would only be sensible for once without views etc. but at least for my use that would be really comftable :D.
#[derive(Collection)]
#[collection_name = ["hoppi", "notification_subscription"]]
// or
#[collection_name = "hoppi.notification_subscription"]

If you want I would look into implementing the macro.
I have this a lot:
impl Collection for SubscriptionInfoTable {
    fn collection_name() -> Result<CollectionName, InvalidNameError> {
        CollectionName::new("hoppi", "notification_subscription")
    }

    fn define_views(_schema: &mut Schematic) -> Result<(), bonsaidb::core::Error> {
        Ok(())
    }
}
impl DefaultSerialization for SubscriptionInfoTable {}

I could look into this as I said, but while I do know derive Macros, I have not a lot of experience with bonsaidb :)

I would love for you to try your hand at it if you're feeling motivated. My pre-coffee brain didn't see the offer for help.
I think I might prefer this syntax, but play around with some variations and see what you think feels most natural:
#[derive(Collection)]
#[collection(name = "Name", authority = "Authority", views = [a,b,c])]
struct MyCollection {...}

There's a crate bonsaidb-macros for these proc-macros to live within already. It could probably use some cleanup, as I believe it was my first set of proc macros ever.
If that syntax for views breaks rust-analyzer or you have a different idea on how to tackle that, feel free to suggest alternate ideas!

As per Discord

if you don't specify serialiation, implement DefaultSerialization
If serialization is None, do not implement any serialization trait
If you specify a typename, use the typename to implement this:

#[derive(Collection)]
#[collection(serialization = transmog_bincode::Bincode)]
struct Foo {}

impl SerializedCollection for Foo {
    type Contents = Foo;
    type Format = $arg;

    fn format() -> Self::Format {
        $arg::default()
    }
}

Appart from the better syn support when using strict Meta attributes, this is rustfmt works better as well.
In my test it formatted the code using serialization(...) but not serialization = ....

[ ] We should consider Add Collection Lifecycles #69 and determine if there is any way to support deriving Collection while still offering the lifecycle event implementations easily.

This seams more like a future problem? If there is anything that can be done now for the macro let me know.

There should probably be an example in the Collection docs right?

This seams more like a future problem? If there is anything that can be done now for the macro let me know.

It is no longer relevant. Spent some time thinking about it and this will end up being like View -- a Collection and CollectionSchema trait eventually.


Create SECURITY.md

This very basic structure of security vulnerability reporting, shows the base on what a file of such should look like. This may be changed at any time, if so desired by the owner!

Thanks for your contribution!
I'm not quite sure what this guide is used for. Could you explain a bit more?

Thanks for your contribution!
I'm not quite sure what this guide is used for. Could you explain a bit more?

Dear @pd4d10,
This is used for a basic structure of a security vulnerability reporting file. This will be what pops up when users select the report a vulnerability in the issues creation section.
Best Wishes,
Lukas Batema

Dear @pd4d10,
This is used for a basic structure of a security vulnerability reporting file. This will be what pops up when users select the report a vulnerability in the issues creation section.
Best Wishes,
Lukas Batema

Thanks for your contribution!
I'm not quite sure what this guide is used for. Could you explain a bit more?

Dear @pd4d10,
Do you need me to change anything, or is this gonna be closed without merge? Thank you!
Best Wishes,
Lukas Batema

Thanks for your contribution!
I'm not quite sure what this guide is used for. Could you explain a bit more?

Dear @pd4d10,
Do you need me to change anything, or is this gonna be closed without merge? Thank you!
Best Wishes,
Lukas Batema

Oh, I didn't use this before. Is there any documentation of how it works?

Oh, I didn't use this before. Is there any documentation of how it works?

Oh, I didn't use this before. Is there any documentation of how it works?

Dear @pd4d10,
Here is the documentation.

Best Wishes,
Lukas Batema

@Lukas-Batema, @PedestriaMC-Network

(Grade 10, JavaScript and Java Programmer, and Front End Web Designer)

Pedestriapedia Official
BatemaDevelopment
My Portfolio

Oh, I didn't use this before. Is there any documentation of how it works?

Dear @pd4d10,
Here is the documentation.

Best Wishes,
Lukas Batema

@Lukas-Batema, @PedestriaMC-Network

(Grade 10, JavaScript and Java Programmer, and Front End Web Designer)

Pedestriapedia Official
BatemaDevelopment
My Portfolio


python3Packages.owslib: 0.28.1 -> 0.29.2

disable new test failing due to missing network access
set Geospatial team as maintainer

Description of changes
Update package to the latest version.
List of changes:

https://github.com/geopython/OWSLib/releases/tag/0.29.0
https://github.com/geopython/OWSLib/releases/tag/0.29.1
https://github.com/geopython/OWSLib/releases/tag/0.29.2

Maintain package under Geospatial team.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Thanks @mweinelt for review and merge.


Get pedersen + transcripts fully working, with tests

This will give you a good look into the transcripts, fiat-shamir, and pedersen commitments. I don't think it'll be too hard, most of this except the pedersen is done.

Implement all the todos in the pedersen commitments module: commit_native_with_multiple_indices, commit_native, compress_native_array, compress_native_buffer_to_field, compress_native, compress_native_with_multiple_indices, compress_native_index, merkle_damgard_tree_compress, merkle_damgard_compress_with_multiple_ivs, merkle_damgard_compress
Implement all the tests: zero_one, endomorphism_test, hash_single, hash_pair, merkle_damgard_compress, merkle_damgard_compress_multiple_iv, merkle_damgard_tree_compress. Get them passing.
Make sure all three hasher types are good to go and fully implemented, producing sane output vs original bberg (is the way the hash functions are being split sane, in your opinion? feel free to workshop it... I think it's okay but not fantastic...)
get the univariate_serialization and validate_transcript tests written and passing

After this, the batch_commit test from the commitments bounty should be tackle-about.

relevant files src/transcript.rs and src/crypto/pedersen/mod.rs and src/crypto/pedersen/lookup.rs

don't bother with lookups yet for anything- just get the rest working.

will be awarded to @PatStiles upon closing #89
cc @brunny-eth

Hey, I recently implemented a barretenberg-compatible version of pedersen commitments/hashing in https://github.com/noir-lang/noir/pull/4871 working off of the existing implementation in barustenberg as a base. I had to make the hash_to_curve function specific to grumpkin to get the choice of y to match up however (this is probably the limitations mentioned in https://github.com/laudiacay/barustenberg/issues/89).
Thought I'd mention this here in case there's interest in pushing some of these changes back into barustenberg.


Revisit binning range when value lies exactly on range stop

We may need to ensure that bins include an additional step when maximal values exactly match the high-end of the binning range.

Fixed and released.


KQueueEventLoop won't unregister active channels reusing a file descriptor

Motivation:
The current KQueueEventLoop implementation does not process concurrent domain socket channel registration/unregistration in the order they actual
happen since unregistration are delated by an event loop task scheduling. When a domain socket is closed, it's file descriptor might be reused
quickly and therefore trigger a new channel registration using the same descriptor.
Consequently the KQueueEventLoop#add(AbstractKQueueChannel) method will overwrite the current inactive channels having the same descriptor
and the delayed KQueueEventLoop#remove(AbstractKQueueChannel) will remove the active channel that replaced the inactive one.
As active channels are registered, events for this file descriptor won't be processed anymore and the channels will never be closed.
Modifications:

Change the logic of KQueueEventLoop#remove(AbstractKQueueChannel) channels so it will check channels equality prior removal.

Result:
KQueueEventLoop won't remove anymore active channels reusing a file descriptor.

@vietj PTAL... This contains your change + some small adjustments to also fix the case when we update the filters for the wrong Fd.

If this looks ok to you @vietj I will just squash both commits and give you the attribution :)

Proper fix for https://github.com/netty/netty/pull/9114 and https://github.com/netty/netty/issues/9113

@netty-bot test this please

it looks good to me @normanmaurer

@vietj PTAL again as I adjusted it even more :)

LGTM @normanmaurer good job!

Alright let me merge this one...

Cherry-picked as https://github.com/netty/netty/commit/e348bd9217eb626aa20dfd15d7c8c860e1fd7596

This was quite interesting, as this appears to also fix a related TCP issue I had in my project (which I worked around by deferring to a future iteration of the event loop). I suspected it was a Netty bug but wasn't entirely sure. I tested my project with 4.1.37.Final and removed my workaround, and this worked.


Always map keys to the same language

If you would always map keys to the same language it would remove the extra step of looking down on the options and you could focus on the code.
Great game btw :)

This could increase difficulty in guessing the code as there would be much more option, so this could be a higher difficulty, or the 4 options could remain while just showing the different keys they are assigned to

That's exactly what I thought when playing the game and I've been meaning to look into it and give it a go but haven't found the time to implement it yet unfortunately.

Thanks for opening an issue and showing interest in the game :3 ❤
This has been suggested by a few other people, but I still don't think I quite understand it. If the languages are always mapped to the same keys, wouldn't there only ever be 4 possible options? (A big downgrade from there currently being 24 languages that you could possibly be quizzed on)

This could increase difficulty in guessing the code as there would be much more option

Again, wouldn't there be much less options?

the 4 options could remain while just showing the different keys they are assigned to

Also don't think I quite understand this.
This might be because I just woke up haha and my minds still trying to get back in action, sorry :) could you try to explain in more detail?

Wouldn't that require the user memorizing every single key? At that point, wouldn't it be easier to just provide a one-line text box where the user can type in either the language name or extension?

Yep the player would have to memorise every key assignment, but most people already have a muscle memory of where each key is

I don't think that would be very beginner friendly

You could add it as an option

I still don't fully understand how it would work. What do you suggest all the keys to be?

q - go
w - kotlin
e - javascript
r - typescript
t - rust
.
.
.

@MaximilianGaedig
I've imagined it more like

g = go
c = c
p(y) = python
j = java
js = javascript

So that when you see the code snippet and are sure it's c, you wouldn't have to look down into the list to see where c is, but only press the key 'c'. I think the idea with an arbitrary key assignment down the first row on the keyboard wouldn't make the experience better at all.

I thought of using the first letter of the language aswell but did not know what to do with conflicts, this is a good idea, typing out the language until there are no other options, also removes the problem of different keyboard layouts

First-letter-collisions would be fairly easy to handle I think as the program would only have to wait ever so shortly after the letter for a second letter to be pressed immediately afterwards. Alternatively, the program could wait for  to avoid frustration for when you lost bc you didn't hit the second key fast enough.

Maybe just confirming shorter shortcuts with an enter key press

On 16. Aug 2022, at 21:34, Malte Dostal @.***> wrote:
First-letter-collisions would be fairly easy to handle I think as the program would only have to wait ever so shortly after the letter for a second letter to be pressed immediately afterwards. Alternatively, the program could wait for to avoid frustration for when you lost bc you didn't hit the second key fast enough.
—
Reply to this email directly, view it on GitHub https://github.com/Lioness100/guess-that-lang/issues/13#issuecomment-1217078258, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJHYWVIKFKLJXVUW6PSFVDTVZPUMZANCNFSM56VEMNGA.
You are receiving this because you were mentioned.

I can't really think of a way to implement either of these cleanly. At the very least we'd have to have a key to press to confirm you finished typing your answer, but to have good UX we'd also have to:

Register all standard text editor keypresses (backspace, arrow keys, delete, etc) which may be more trouble than it's worth
Provide a good UI in the form a text box so people can see what they're typing

Both of these could be solved using an external crates, but external crates will almost always depend on the cursor being in a predictable position, and under these circumstances, it won't be. We'd have to completely overhaul the terminal integration.
Given the above, I don't think this is a feature I'm going to pursue personally. However, please feel free to submit a PR, I'd love to see what you come up with :)

Specifically, migrating to tui might make this easier, as well as any other additions like this in the future.

After thinking about it a bit more, I think using tui and pursuing this feature is a good idea. Is anybody currently working on this?

This would also fix resizing issues and allow the language options to be displayed on the side or top


Websocket connection failures

I get various connection failures when browsing the OSE web console. I have no issues on the command line console. Shutting down the other masters 02 and 03 solves the problem, but I assume it should work in HA as well.
Maybe the asynchronous loading fails when the request is loadbalanced to a different master than the one the first page was served with. This is after accepting permanently all certificates. I am running Firefox 49.0.2 and I have seen this issue before. I noticed a mention in an internal doc about configuring reverse proxy, maybe there is some additional AWS config I must do manually that I may have missed?

I believe we had resolved this in the past with the Cross-Zone Load Balancing: Enabled setting on the load balancers. Spinning up a cluster now

@jbrannst so this is issue seems to only happen with firefox and an untrusted cert. I tested on my local machine with firefox and ran into a similar issue. I imported the ca.crt in firefox and the error goes away.  I'm wondering if this error relates back to a previous firefox bug where firefox would ask you to accept the certificate over and over without ever accepting the certificate.
This does not seem to happen with chrome

@cooktheryan ok cool yes manually exporting and then importing the ca cert works! And Chrome does not have the issue.


Enabling useBus breaks my app

Package version
1.0.0-4
Describe the bug
As soon as I turn on useBus my app no longer loads:
.useBus(
drivers.redisBus({
connectionName: 'main',
})
),
Then npm run dev gives:
Error: Error: Connection is closed.
Despite using and referencing the redis in L2 cache which works fine. So redis is definitely working.
Reproduction repo
No response

Hey @craigharman! 👋🏻
Thanks for raising this issue! 🙏
Just a heads-up: this package isn't ready for production yet. Currently, Bentocache depends on an outdated version of the Bus package, which is likely causing the issue you’re experiencing. Updating it should help resolve the problem.
Would you mind opening a PR to update this dependency? Here’s the link: package.json#L75
cc @Julien-R44

Done, thanks @RomainLanz  https://github.com/Julien-R44/bentocache/pull/41


Use runpy.py and future.py from StdLib

Equivalent of https://github.com/IronLanguages/ironpython3/pull/328


Info: Add alignment v2

Description
Same PR as before but fixed merge conflicts with the new info() and prin() functions.
Examples:
# LEFT

user@hostname
-------------
OS            : Arch Linux
Kernel        : Linux 4.9-ARCH
Uptime        : 1 hour, 41 minutes

# RIGHT

user@hostname
-------------
           OS : Arch Linux
       Kernel : Linux 4.9-ARCH
       Uptime : 1 hour, 41 minutes

Features

Align the info output into columns.

Issues

[x] $align_amount must be hardcoded since we don't know the max subtitle width.
[x] --disable doesn't update max subtitle length.

Testing
neofetch --align_info left
neofetch --align_info right

Old PR: https://github.com/dylanaraps/neofetch/issues/524

Unless we fix the bug mentioned in the comments of the previous PR, this won't be merged. I have ideas on how to fix it and I'll implement those in this PR.


Update node and neo4j versions in ci

coverage: 97.701%. remained the same
when pulling 48eeca8c5f8136f45ceb6d9a2fb4b9561684231e on update-node-neo4j-test-versions
into 0e43fb421d7bf4fe49ca9fba49b36dfd74652853 on master.


Update DefaultNoBound derive macro

Updates the DefaultNoBound derive macro.

Fixes a bug when deriving for enums with no generics

This may seem like an odd use case, but I hit this when deriving DefaultNoBound in generated code

Changes the behaviour on enums for selecting the default variant from silently choosing the first variant to requiring a #[default] attribute. This aligns with std: https://github.com/rust-lang/rust/issues/87517
Small improvements to diagnostics:

Fixed erroneous mention of CloneNoBound when attempting to derive on a union (and add UI test)
Added UI tests for the new #[default] attribute
Added compile pass tests for deriving DefaultNoBound on a struct and enum with no generics

Cleaned up the code a bit, importing items instead of using fully qualified paths and renaming single letter variables

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2056575

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2056577

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2056582

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2056576

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2058182

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2058189

/tip small

/tip small

bot rebase

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2083120


How can I pass particular row prop to sub component

Hello,
How to pass single row data as props to subcomponent?
when I am accessing props it is passing all rows data to the child. I need only parent row data in the subcomponent
Thanks,
Dinesh

Got it row.original have the list of parent row params

If you have questions about support or implementation, please use the React Table Spectrum Community


Add propEq and propPathEq to predicates

These are a pair of handy predicates that should be included in the library.
They should have the following signatures:

propEq :: String -> a -> Object -> Boolean
propPathEq :: [ String ] -> a -> Object -> Boolean

Both should return false if the key does not exist. and should throw in the case of String (or [ String ]) or Object not being the proper types. Under the hood src/core/equals.js should be used for equality by value.
The following needs to be accomplished:

Add code, each function in its own file.

[ ] src/predicates/propEq.js
[ ] src/predicates/propPathEq.js

One spec file per function (src/predicates)

[ ] src/predicates/propEq.spec.js
[ ] src/predicates/propPathEq.spec.js

Documentation (/src/pages/docs/functions/predicate-functions.md)

[ ] Entry for propEq
[ ] Entry for propPathEq

Expose new functions to public API (src/index.js, in predicates section)

[ ] Entry for propEq
[ ] Entry for propPathEq

Add specs for new public functions (src/index.spec.js)

[ ] Entry for propEq
[ ] Entry for propPathEq

For reasons of consistency, should it be propEq :: (String | Number) -> a -> Object -> Boolean, similar to hasProp

Yeppers!! You got it!

A few quick questions about propPathEq

I'm planning to use the already implemented propPath for this one, but it's not a part of src/core. Thoughts?
Since propPath returns a Maybe, should we also do an unboxed equality check? In other words, should propPathEq(["some", "key"], 5, { some: { key: 5 } }) be true?

This has been merged.
Closing!!


Extend CLI with --spaces flag option configurable

Is your feature request related to a problem? Please describe.
We do keep Field-types in Organisation level (https://app.storyblok.com/#/me/org/fields), which is accessible ONLY for users having Admin level.
Multiple developers can contribute to plugin monorepo, and they should be able to push new plugins in automated way via CLI only with no need to go to Admin panel to configure them, hence they must be able to have plugin assigned to some certain spaces via CLI.
Describe the solution you'd like
Extend CLI with --spaces flag option to instantly assign plugin to certain spaces, f.e
--spaces 0123456

or multiple:
--spaces 0123456,0123457,0123458

Additional context
Severity: high.

Hi @edvinasjurele This is a good idea. I assume you mean --spaces flag to deploy command, right?

Hi @eunjae-lee, yes! Sorry, was not specific enough. Will update description accordingly.

Hi @eunjae-lee, yes! Sorry, was not specific enough. Will update description accordingly.

No worries! I just wanted to make sure :D

IMHO there should be an option for interactive question of the deploy command.
This is useful to automate the deplyoment.
In our case we need an option to set a value for the question Where to deploy the plugin?.


Using SMA not shrinking files when downgrading mp4's to SD

Hi,
I've been using SMA for years as a post download script with NZBGet.  Now I'm wanting to make all my TV shows SD (480p) to save on drive space, so I'm now using SMA using a docker container based on sonarr-sma.  Most shows download at the desired quality, but some shows are only released at higher qualities.
I have a separate autoProcess.ini for Sonarr & Radarr...

link to my docker compose
link to my autoProcess.ini for Sonarr

When trying to convert down to 480p with SMA, I'm finding that the file size (eg 1080p file that is about 800MB) stays about the same size, but when I convert the same file with Handbreak to 480p, it is down to 168.5MB.
I'm trying to work out where I'm going wrong, but having trouble.  Could someone please have a look at my config files and give any pointers?  Thanks in advance for any assistance given!

I would try using the video-crf option to help lower the bitrate. A 1080p file at 800MB is already very heavily compressed so FFMPEG is just preserving the bitrate because at 480p that bitrate is still acceptable


Version gate changes from 11706

Breakage is from https://github.com/riptano/cassandra-dtest/pull/1281/files
Fixes https://issues.apache.org/jira/browse/CASSANDRA-12579
@knifewine to review, please

+1 if the tests run without problems


A little bit more details?

Would be fantastic if you let us know a little more details, I meant what do u mean with "mad libs" ? :D  Some links :D

I am deliberately vague so that the learner has to google.
Seeking for resources is one of the most important skills in programming.


Error with add document to custom field

Hi, before Error will display, i'll create Special Field (for example License), in Special Field in Type i choose "Object", "Object Type - Document Storage> Device Document", Model(s) (DCIM>Device).

Then i'll going on another Device, and when i Add/Edit Device to add some file to my License field i see error.

Thanks for reporting.
I just published version 0.4.6 that should fix this for you. Please run pip install netbox-documents --upgrade to pull the updated release.


State no longer has a context

I am getting the following error in my ListView containing the images.

How to reproduce this issue @anmol-me ?

This might help.
"newsItem" is the model class and its property imageUrl contains the URL string obtained through the web.
            newsItem.imageUrl.isNotEmpty
                    ? FastCachedImage(
                        url: newsItem.imageUrl,
                        height: 90,
                        width: 120,
                        fit: BoxFit.cover,
                        errorBuilder: (context, _, s) => Image.asset(
                             'assets/images/notfound.png',
                            height: 90,
                            width: 120,
                            fit: BoxFit.cover,
                          ),
                        loadingBuilder: (context, _) => const Center(
                          child: CircularProgressIndicator(
                            color: Colors.red,
                            strokeWidth: 1,
                          ),
                        ),
                      )
                    : Image.asset(
                        'assets/images/notfound.png',
                        height: 90,
                        width: 120,
                        fit: BoxFit.cover,
                      ),

Fixed


benches: fix resource download and extract.

@BusyJay @AndreMouche , PTAL.

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

@BusyJay , PTAL, thanks.

/run-all-tests

/run-all-tests

/rebuild

Let's add a #[ignore] to the test cases for now. We generally only want to bench it rather than test it.

Now we can use cargo bench --features "default" -- --nocapture --ignored to run those benches.

/run-all-tests

LGTM

/run-all-test


Add a CrystalMetadata enum

For beamlines with a monochromator  that use a Si or Ge crystal.
at first implemented in the PR
https://github.com/DiamondLightSource/dodal/pull/722

merged in
https://github.com/DiamondLightSource/dodal/pull/843


MAX_WAV_VALUE

excuse me，What is the role of  MAX_WAV_VALUE ？

It's the audio's bit depth and it is used to scale the audio to [-1, 1]


Toggle line numbers

Ctrl+R for ruler
Example addition to settings.json to boot without ruler
{
    "colorscheme": "solarized",
    "tabsize": 4,
    "autoindent": true,
    "syntax": true,
    "tabsToSpaces": false,
    "ruler": false
}

Is there a command in micro available? Something like set ruler off?

Ok saw it in the code, should work, sorry :)

set ruler off and ctrl+r should toggle numbers


Add official website in TSV export

The feature
In the export that can be downloaded for every country, it would be great if the official website could be present as a new row 😊.
Why?
I haven't found any other way to extract it from Govdirectory (but maybe I've missed something) and extracting from Wikidata is cumbersome.
The direct need is a website doing automatic analysis of government websites (from an accessibility, privacy and performance perspective) that would like to use Govdirectory as a source for its list of websites to crawl.
Examples and inspiration
No response

I'm posting this here after discussing it with @Ainali. Also interested is @marcusosterberg.

So what the download feature currently does is that it takes the content of the table and provides that as a download. So the easiest solution would be to add the homepage to the table, which I think makes sense too. @Ainali thought or ideas about how it could look?

I like the idea!
It could just be the quite well-used 🌐 icon in the Platforms column that links to the website.

This is also completed. #341

All the other icons for social media links got a colored background and white front, what background color could we use for a plain website?

Fixed by #389


Update Governance.rst

Change LGE representative.

Approved by review and the TSC. I am going to merge this.


Correct Vietnam country code

For this issue https://github.com/casdoor/casdoor/issues/1722

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

@saosangmo backend i18n file missed:

@saosangmo also fix CI:


Fix unstable qunit tests

1)test/client/fixtures/sandbox/event/focus-blur-change-test.js
Test: body.innerHTML in iframe
2)test/client/fixtures/sandbox/code-instrumentation/setters-test.js
Test: focus after calling setSelectionRange()

@miherlosev  Please, refer the discussion and add more info to the title and description. Hint: we should fix it using "quarantine" mechanism in quint-harness

@inikulin @AlexanderMoskovkin
Guys, I propose to make a simple decision and cease to suffer with the unstable tests.
 window.wait = function (condition) {
        return new Promise(function (resolve) {
            var timeoutId = window.setTimeout(function () {
                window.clearInterval(intervalId);
                window.clearTimeout(timeoutId);
                ok(false, 'Timeout error');
            }, 1000);

            var intervalId = window.setInterval(function () {
                if (condition) {
                    window.clearInterval(intervalId);
                    window.clearTimeout(timeoutId);
                    resolve();
                }
            }, 50);
        });
    };

It should solve all the problems with the hammerhead tests. I suggest not to run the tests several times. If the virtual machine slows down, all 10 times the tests will not pass. If the test works through time, it is a bad test and we have to rewrite it.

@churkin I like it, but I think we should increase general timeout to 3 seconds. @AlexanderMoskovkin We should implement it in harness I guess

agree. Maybe we should and the second optional agrument ms ? We will able to cover the scenarios when we should wait more long time

@AlexanderMoskovkin Do we have them? I suppose what test which waits more than 3 seconds is a bad test

I hope no, we have not ))

The wait feature is availabe in the qunit-harness v.0.2.0. Here is an example how to use it:
asyncTest('test with wait', function () {
    var resolved = false;

    window.setTimeout(function () {
        resolved = true;
    }, 50);

    window.QUnitGlobals.wait(function () {
        return resolved;
    }).then(function () {
        ok(true);
        start();
    });
});

The test will fail with the timeout error if condition returns 'false' within 3000 ms.
I suppose you can try to fix unstable tests.
I think you need not the Add the attempts parameter to tests feature yet and I can close it? /cc @miherlosev @churkin

We decide don't make "quarantine" mechanism.
We have a separate issue #280 to stabilize tests


GPTs to add

Better GPT Builder: https://chat.openai.com/g/g-w8wjRexpv-better-gpt-builder
ResourceFinder GPT: https://chat.openai.com/g/g-8aHtP3r6X-resourcefinder-gpt
Thank you for adding my GPTs!

Added


Date of last available data should be included

Completed with https://github.com/ivelasq/covid-edu-risk/commit/e45efb7bea8f0f51d83a80c5c6edeb4ce2cfdefd.


Remove umount command from remote client.

Since there is no mount command in remote, it does not make sense to have umount.
Signed-off-by: Ashley Cui<EMAIL_ADDRESS>

Tests aren't hip  :^(

LGTM

/lgtm

/approve


CompiledBindingExtension vs AvaloniaRider plugin

Describe the bug
After compile binding is enabled,  markup is parsed as CompiledBindingExtension, where RelativeResource is not available.
But it still compiles and runs as expected. So what should we do? change Binding to ReflectionBinding, or it is a bug from plugin?
To Reproduce
Add x:CompileBindings="True" in FluentTheme scrollviewer theme page.
Expected behavior
None
Screenshots

Desktop (please complete the following information):

OS: [e.g. Windows, Mac, Linux (State distribution)]
Version: Avalonia: latest nightly. Plugin: <IP_ADDRESS>

Additional context
Add any other context about the problem here.

Please report Rider bugs to the Rider youtrack.
This one specifically was already reported and I added it to the list in this issue https://github.com/AvaloniaUI/Avalonia/issues/10356 just to keep it in one place.

Specifically this https://youtrack.jetbrains.com/issue/RSRP-491613/Avalonia-not-all-bindings-properties-are-properly-supported-by-XAML-editor
Seems like it was fixed in the latest builds, not sure if public or eap.

@maxkatz6 thanks


Update consul.go

Add type “int64” to func CheckKeyValuePairs in /support/consul-client/consul.go for ConfigurationStruct::CleanupDefaultAge in /support/notifications/const.go

Closing due to inactivity. Reopen if needed.


Few performance optimizations

I am looking at implementing O'Sullivan in a Spotlight Resource Indexer and noticed that parsing any sizable manifest (e.g. http://iiif.bodleian.ox.ac.uk/iiif/manifest/eeb272cc-bb48-44b0-9ee3-2cee0338a691.json w/ 1087 canvases) was particularly slow.
I decided to do a quick profile on IIIF::Service.parse to see what was going on.  The classes being iterated over the (uncached) ObjectSpace#each_object is particularly expensive.  This PR both caches the results of the IIIF::Service descendants as well as uses ActiveSupport's subclasses core extension.
Before this PR a call to IIIF::Service.parse on the contents of http://iiif.bodleian.ox.ac.uk/iiif/manifest/eeb272cc-bb48-44b0-9ee3-2cee0338a691.json averaged around 26 seconds on my laptop.  After this change the time to parse this manifest is down to a more manageable 5 seconds.

@jkeck that's great! This is some of the first Ruby code I ever wrote, and I'm sure it's full of possible optimizations and general ungliness. Thanks!

There were a few other tweaks sitting around on the development branch, so:  https://rubygems.org/gems/iiif-presentation/versions/0.0.5

:+1: thanks @jpstroop!

:+1:


feat: Add setAppID

Adding wrapper for setAppID to RN library

Oh, I didn't see any change to the README that would help people discover this feature? A README sentence somewhere in the initialization section would help I think? https://github.com/thebergamo/react-native-fbsdk-next/blob/master/README.md#sdk-initialization

Oh, I didn't see any change to the README that would help people discover this feature? A README sentence somewhere in the initialization section would help I think? https://github.com/thebergamo/react-native-fbsdk-next/blob/master/README.md#sdk-initialization

Have added section on setAppID to the readme. If there is anything else that need changed or added just let me know.

I'd like to make sure @thebergamo doesn't see anything I'm missing but I tagged it as pending merge because in the absence of any other feedback in a couple days, I'll merge. That leads me to say using patch-package between now and a merge+release should be safe, I'm certain this exact code or perhaps some tiny modification will make it to release so if you do a local patch it'll converge shortly
:trophy:

It seems solid for me :)
Yeah, that's a very nice thing to have as sometimes some of us could get a bit confused with this native part.
It seems good to me to be merged.
Great work and thanks @torbenkikkert o/

Thanks for the good feedback and help getting this little feature in.


Update hard requirements of ipycytoscape to soft ones and add pip ins…

…tall .[docs] as method to install doc dependencies

looks good!
I just updated the path to conf.py to reflect the docs setup on this project

Do the readthedocs builds only trigger when there is a change to the docs directory? It doesn't look as though merging this caused a build to happen


Refactor/document normalize-filename so it can be used as a library

http://qr.ae/RgnqI7

I'm not really interested in doing this any more.


Analyzer highlights wrong span for "must be initialized"

The field String message, I think should be highlighted, not the constructor.

We actually put a fair bit of thought into this, so I'll start by describing some of those thoughts.
One principle we considered is that diagnostics should be reported as close to the point at which the corrective change should be applied as possible. In this case, there are two places where a change could be applied--at the declaration of the field and in the constructor--and both are equally likely given what the analyzer knows about your intent (which is virtually nothing). So, that didn't really help us make a choice between the two locations.
Another principle is that diagnostics should be reported consistently. In this context that means that the same problem shouldn't be highlighted in different locations under different conditions unless there is a really compelling reason to do so. Users use the context of the message as much as (maybe more than) the actual wording of the message when understanding what the problem is and how to fix it. Consistency helps users learn responses to diagnostics making them more productive. When we considered the fact that sometimes there are multiple constructors and only one of them is missing the initialization of a field, we concluded that consistently highlighting the constructor(s) when there are constructors, and highlighting the field when there are no constructors, was a good tradeoff.
It's definitely a tradeoff, though. It's possible that we should always highlight the field unless there is at least one constructor that initializes the field. It would be interesting to measure some production code to see how common it is for a field to have an initializer versus how common it is for the constructors to initialize the field. I don't think we had a large enough body of code at the time this decision was first made, but we probably do now.

Closing this as per Brian's comment. If someone has more thoughts, feel free to comment, re-open, or open anew.


Feature request: Lambda Layer support for new regions eu-central-2 & eu-south-2

Use case
Over the past days AWS has launched two new regions: eu-central-2 (link) and eu-south-2 (link).
Both regions are opt-in but they both launched with AWS Lambda support, which means Layers should be available.
Solution/User Experience
Over the next releases we should make an effort to publish Powertools Layers in those new regions similar to what we do currently in all other commercial ones.
Before start working on this, we should agree on the version strategy. For example, Powertools for Python keeps versions aligned also on newer regions, they have developed a script that does that automatically and that we could leverage.
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Lambda Powertools Tenets
[X] Should this be considered in other Lambda Powertools languages? i.e. Python, Java

Hi @dreamorosi, how do you generate the layers listed in https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/docs/index.md ?
I see they are all pointed to arn:aws:lambda::094274105915:layer:AWSLambdaPowertoolsTypeScript:6, so I am interested in knowing how the version (last token) is published, if it's possible to extract for example from github actions.
Thanks!

Hi @caioquirino the layers are published with this workflows, which uses a CDK app to do the job.
However at the moment the we manually update the version number in the docs after each release. We have an open issue to automate this (#1124) but we haven't gotten around implementing it yet.
From your question I'm assuming you'd like to get the latest version available in a programmatic way, is that the case? I would love to hear more about your use case/need and see if there's something that we can do to help you onboard the layers.

@am29d offered to tackle this one.
As part of this item we should include also:

any other region that was launched since the issue creation (i.e. ap-southeast-4)
making sure the the layer version in the new regions is aligned with the existing ones


Merge prTesting_201910101308 branch to master branch

Docs Build status updates of commit f326efc:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit f326efc:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestCon.md
:warning:Warning

Details

split/updateTestCon.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 1: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Rainow monke doesnt work

I've downloaded and redownloaded the mod multiple times enabled and disabled and restarted gorilla tag many times but no matter what i do the mod doesnt work please can you help me?

Currently the mod is outdated with the current version of Gorilla Tag so its broken temporarily, but i'll try fix it soon

When will it be fixed? And also will it delete my hats?

I have a working one
....

I have a working one
....

;)


Casing converter inferring incorrect underscore position

Describe the issue
IncludeAPIs is being generated as include_ap_is. I've tried putting in both API and APIs (i've also tried all lowercase) into the list of overrides but it still generates it as include_ap_is
** REQUIRED **
ModelerFour version: 4.12.301
AutoRest-core version: 3.0.6282
CommandLine : autorest ../azure-rest-api-specs/specification/cosmos-db/data-plane/readme.md --python --use=. --tag=package-2019-02 --python-sdks-folder=../azure-sdk-for-python/sdk
OpenAPI/Swagger file: this file from this pr

Closing since the readme override looks only at full words, so I've added IncludeAPIs to the override list https://github.com/Azure/autorest.python/pull/603


always be killed when build TensorRT engine

I try to run llama-7b with TensorRT-LLM, when build TensorRT engine as follows:
python3 build.py --model_dir /opt/llms/llama-7b
--dtype float16
--remove_input_padding
--use_gpt_attention_plugin float16
--enable_context_fmha
--use_gemm_plugin float16
--use_inflight_batching
--output_dir /opt/trtModel/llama/1-gpu
but the program always be killed, I am confused。

@Burning-XX  I think this error is caused by insufficient CPU memory size.

@Burning-XX I think this error is caused by insufficient CPU memory size.

you mean GPU memory or CPU memory?

@Burning-XX I think this error is caused by insufficient CPU memory size.

you mean GPU memory or CPU memory?

what param could I change to make it success, if I do not have enough memory

@Burning-XX I don't know which branch you are using, I solved this problem according to https://github.com/NVIDIA/TensorRT-LLM/issues/102#issuecomment-1780231895 under version 0.5.0.

How much CPU memory do you have in your system?

Hello, I am seeing this and have this for nvidia-smi:
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.104.12             Driver Version: 535.104.12   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA A100 80GB PCIe          On  | 00000000:05:00.0 Off |                  Off |
| N/A   42C    P0              46W / 300W |      4MiB / 81920MiB |      0%      Default |
|                                         |                      |             Disabled |
+-----------------------------------------+----------------------+----------------------+
|   1  NVIDIA A100 80GB PCIe          On  | 00000000:06:00.0 Off |                  Off |
| N/A   38C    P0              44W / 300W |      4MiB / 81920MiB |      0%      Default |
|                                         |                      |             Disabled |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|  No running processes found                                                           |
+---------------------------------------------------------------------------------------+
and have for top:
top - 14:43:49 up 17:19,  0 users,  load average: 0.00, 0.00, 0.02
Tasks:   2 total,   1 running,   1 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.3 us,  0.2 sy,  0.0 ni, 99.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  32089.1 total,  30334.8 free,   1381.9 used,    372.4 buff/cache
MiB Swap:      0.0 total,      0.0 free,      0.0 used.  30280.9 avail Mem
PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  1 root      20   0    9136   6272   1792 S   0.0   0.0   0:00.15 bash
462 root      20   0    7800   3584   2944 R   0.0   0.0   0:00.01 top

I don't think memory is my issue and building the engine is always killed:
python ../llama/build.py --model_dir ./Mixtral-8x7B-v0.1
--use_inflight_batching
--enable_context_fmha
--use_gemm_plugin
--world_size 2
--pp_size 2
--output_dir ./trt_engines/mixtral/PP
[12/27/2023-14:45:54] [TRT-LLM] [I] Using GPT attention plugin for inflight batching mode. Setting to default 'float16'
[12/27/2023-14:45:54] [TRT-LLM] [I] Using remove input padding for inflight batching mode.
[12/27/2023-14:45:54] [TRT-LLM] [I] Using paged KV cache for inflight batching mode.
You are using a model of type mixtral to instantiate a model of type llama. This is not supported for all configurations of models and can yield errors.
[12/27/2023-14:45:54] [TRT-LLM] [I] Serially build TensorRT engines.
[12/27/2023-14:45:55] [TRT] [I] [MemUsageChange] Init CUDA: CPU +14, GPU +0, now: CPU 129, GPU 427 (MiB)
[12/27/2023-14:45:58] [TRT] [I] [MemUsageChange] Init builder kernel library: CPU +1973, GPU +350, now: CPU 2238, GPU 777 (MiB)
[12/27/2023-14:45:58] [TRT-LLM] [W] Invalid timing cache, using freshly created one
[12/27/2023-14:45:58] [TRT-LLM] [I] [MemUsage] Rank 0 Engine build starts - Allocated Memory: Host 2.5429 (GiB) Device 0.7592 (GiB)
Killed
Can you help me understand why? Am I doing something wrong? I am running in the docker and it built fine.

I was doing this with mixtral, but tried with qwen and I am seeing the same issue:
python build.py --hf_model_dir ./tmp/Qwen/7B/                 --dtype float16                 --remove_input_padding                 --use_gpt_attention_plugin float16                 --enable_context_fmha                 --use_gemm_plugin float16                 --output_dir ./tmp/Qwen/7B/trt_engines/fp16/1-gpu/
[12/27/2023-15:13:09] [TRT-LLM] [I] Serially build TensorRT engines.
[12/27/2023-15:13:09] [TRT] [I] [MemUsageChange] Init CUDA: CPU +14, GPU +0, now: CPU 116, GPU 427 (MiB)
[12/27/2023-15:13:12] [TRT] [I] [MemUsageChange] Init builder kernel library: CPU +1973, GPU +350, now: CPU 2225, GPU 777 (MiB)
[12/27/2023-15:13:12] [TRT-LLM] [W] Invalid timing cache, using freshly created one
[12/27/2023-15:13:22] [TRT-LLM] [I] Loading HF QWen ... from ./tmp/Qwen/7B/
/root/.cache/huggingface/modules/transformers_modules/modeling_qwen.py:943: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
logger.warn(
[12/27/2023-15:13:29] The model is automatically converting to bf16 for faster inference. If you want to disable the automatic precision, please manually add bf16/fp16/fp32=True to "AutoModelForCausalLM.from_pretrained".
[12/27/2023-15:13:29] Try importing flash-attention for faster inference...
[12/27/2023-15:13:29] Warning: import flash_attn rotary fail, please install FlashAttention rotary to get higher efficiency https://github.com/Dao-AILab/flash-attention/tree/main/csrc/rotary
[12/27/2023-15:13:29] Warning: import flash_attn rms_norm fail, please install FlashAttention layer_norm to get higher efficiency https://github.com/Dao-AILab/flash-attention/tree/main/csrc/layer_norm
Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 8/8 [00:01<00:00,  7.42it/s]
[12/27/2023-15:13:31] [TRT-LLM] [I] HF QWen loaded. Total time: 00:00:08
[12/27/2023-15:13:31] [TRT-LLM] [I] Loading weights from HF QWen...
Converting...:  92%|███████████████████████▉  | 239/259 [00:26<00:01, 10.65it/s]Killed

How much CPU memory do you have in your system?

32G

0.5.0

also release 0.5.0

Could you try on machine with larger RAM? Also, we suggest trying latest main branch or release branch.

It would be good to get requirements of hardware per model. Errors are unclear and shooting with different parameters hoping for lower memory consumption is not clear.

@Burning-XX Do you still have the problem? If not, we will close it soon.

Same issue when creating checkpoint for mistral
python3 ${CONVERT_CHKPT_SCRIPT} --model_dir ${LLAMA_MODEL} --output_dir ${UNIFIED_CKPT_PATH} --dtype float16

[TensorRT-LLM] TensorRT-LLM version: 0.12.0.dev2024080600
0.12.0.dev2024080600
286it [00:50,  5.63it/s]
Total time of reading and converting 52.12702465057373 s
Killed


Question: Leia official integration ?

Hi, first of all thank you very much for the excellent work you're doing here !
I was wondering if you are in contact with the Kodi team for an official integration into Kodi 18.
If so, can you please point me (us) to the reference place where the discussion is happening ?
I'd love to follow the progress and eventually try this addon myself !
Thanks again !

@mcallegari
Hi,
first of all, I´m not sure what you mean with "official integration"?!
If you ask if that plugin will be tightly integrated into Kodi itself, then I can point you to this issue: https://github.com/FernetMenta/kodi-agile/issues/172 - Short version: Not going to happen for good reasons.
Your question could also be understood in a way, that you don't need Kodi Agile, that the plugin does run on the official Kodi 18 builds. If that´s your question, then I can say that work in that direction is ongoing & for sure (I´d say in a couple of weeks) this should be the case. Having it work with mainline Kodi is the primary goal.
If you´re asking if the plugin will end up in the Kodi.tv repo. I´m fairly certain, that this won't happen. First of all, you need the widevine library, which you need to somehow integrate into your Kodi installation (which is tricky in terms of licensing), as only official distributors are allowed to ship with their software (the License actually goes that far to say, that even only the use of it must be blessed by Google). Second, that plugin has no blessing from Netflix itself, so putting that into the main Kodi repo might get the Kodi team in to another companies crosshair & we all know that they´ve got all hands full with fighting illegal content. So, it´s nit wise to open up another front.
I hope I could answer your question here, whatever its main intention was.

Hi, thanks for your answer.
Yes, by "official integration" I meant "will run on official Kodi builds".
You need to excuse my ignorance, but it's not clear to me what "Kodi agile" builds are ? Aren't they nightly builds or do they come from a "unofficial" fork of the main repo ?
Where the addon is stored is another story, but reading your answer made me think of libmad.
MP3 licensing is tricky as well, and it would taint the GPL license, but the trick over the years has been (AFAIK):

the library is available in the Ubuntu repos. Basically someone just built an open source project, packaged it and published it online
the user is the one who decides if he wants to taint his installation with a software not complying with the base license

So in other words. Ubuntu cannot send it to you. You have to download it and take the responsibility for it.  :)
Maybe the same paradigm can be used for the widevine library ?

P.S. When you're done with the rework you're doing, I am very willing to provide an italian translation !

@mcallegari Unfortunately it´s a bit more complicated with the widevine library (As if your example wouldn't be complicated enough itself...)
Google strictly says, even the use of it (without their blessing) is a violation of their EULA. We´ve been thinking of many ways how we could download the browser for the OS & extracting that lib or point Inputstream into the right directory, so that we don't violate the EULA by extracting files etc.
But in the end, my contact at google said that this would all be pointless.
It seems that the only way to have it waterproof, is to sign papers with google (which individuals can't, only organisations or companies can do so). We´re investigating what can be done there, and hope to find a clean solution with a fine user experience in the end. Fingers crossed.
P.s.: Thanks for the translation offer, I´ll ping you once I´m done (might be another week or two, as I´m iterating over the complete code base, to make it compliant with python styleguides etc.)
P.p.s.: I hope you don't mind if I close this one, as there is no action that can be taken from our side now.
P.p.p.s.: Nice avatar :D

P.s.: Thanks for the translation offer, I´ll ping you once I´m done (might be another week or two, as I´m iterating over the complete code base, to make it compliant with python styleguides etc.)

P.p.s.: I hope you don't mind if I close this one, as there is no action that can be taken from our side now.

No problem at all

P.p.p.s.: Nice avatar :D

Get ready fot the 10th ! The doctor returns :)


Too frequently delta log scans.

We observed delta logs are scanned many times during the running of a SQL, which submits too many small queries to spark. The main query was even been blocked by waiting for the scheduler being ready. We'd better make the metadata processing (or get current snapshot) more efficient.

How many executor slots does your cluster have?  The snapshot should be cached after the first read, so I would expect most of these log queries to be very fast (for real tables often faster than listing the files in the table). If you have a small cluster / table you might consider decreasing the number of snapshot partitions using the config spark.databricks.delta.snapshotPartitions.

Thanks, @marmbrus , very valuable comments. Indeed, the scheduler blocking was on local mode which make the situation worse. However, on my 18 nodes cluster, I found about 70% queries were such log queries, all of them were very fast, but the amount is huge. I guess this would also bring pressure on the scheduler.
And as my investigation, the log scans originate from, 1, when the relation was resolved, where the DeltaLog is instanced, and 2, the TahoeLogFileIndex#listFiles was called. The second part would save time compared to listFiles from HDFS, but the first part would make the plan analyzation time long?
Pls correct me if I'm wrong.

I would expect 1 log query for every real query. Scanning / filtering the log is done each time the table is read. In our internal benchmark (TPC-DS and others) this cost is comparable to the work required to list files or contact the metastore (including any extra scheduler work).
The first one you see when the relation is resolved is likely the most expensive one.  This query is caching a snapshot of the table for all future queries. This will only happen when the table changes, so generally does not affect the time required for analysis.

Close it temporarily.  Will investigate it more and reopen if necessary.


Turn Palo Alto on for production

This PR flips the switch to enable the Palo Alto in production. (A retry from https://github.com/CDCgov/prime-reportstream/pull/2828)
Deployment Checklist

[ ] Ensure changes to CDC DNS are applied (Richard Teasley should notify us)
[ ] Notify senders of downtime - Anshul
[ ] Disable the release GitHub Action - Chris
[ ] Merge this PR - Chris
[ ] Deploy Terraform to production - Chris

[ ] Deploy tf-01-network to production
[ ] Deploy tf-02-config to production
[ ] Deploy tf-03-persistent to production
[ ] Deploy tf-04-app to production

[ ] Verify we have App Insights logs - Jim
[ ] Verify we have no blocked SFTP connection to senders - Jim
[ ] Inspect Palo Alto logs to see if any unexpected traffic is blocked - Timothy
[ ] Perform post-deployment validations - Jim
[ ] Enable the release GitHub Action - Chris
[ ] Notify receivers they can remove our old IP address from their firewall - Ming/Adrian

@cwinters-usds Thanks for updating the checklist! These steps are no longer needed:

[ ] Update the dnsmasq mapping file for production IP addresses - Chris

[ ] Submit a PR with the changes
[ ] Apply tf-01-network to force the dnsmasq server to update

@ronaldheft-usds thanks much for the pointer, fixed

@ronaldheft-usds good point -- I forgot to add that after bringing it up in our standup!
Is there any reason not to make this change in the terraform here? It'd get applied in the 'Deploy Terraform to Production' step and the function app would be restarted as a result.

@ronaldheft-usds good point -- I forgot to add that after bringing it up in our standup!
Is there any reason not to make this change in the terraform here? It'd get applied in the 'Deploy Terraform to Production' step and the function app would be restarted as a result.

Nope! That's the perfect spot! I would add it to this PR, so when we merge, that change will be included.

@ronaldheft-usds added that config item, also a short doc about DNS -- hopefully it makes sense.


Regression in 1.8.0: Line with formatting immediately following line with HTML doesn't render

Hi,
One of our Kirby customers reported a bug in Parsedown 1.8.0-beta7 (see https://github.com/getkirby/kirby/issues/1943):
Markdown input:

Simple HTML

# Test

Output from Parsedown 1.7.3:

Simple HTML

Test

Output from Parsedown 1.8.0-beta7:

Simple HTML

# Test

Code example:
$markdownWithHtml = <<<MARKDOWN

Simple HTML

# Test
MARKDOWN;

$parsedown = new Parsedown();
echo $parsedown->text($markdownWithHtml);

Hi there, this is intended behaviour and replicated in the reference parser.
Reasoning for this is that the line
Simple HTML
 starts a HTML block (of type 6 in this case), which requires a blank line to end it per the CommonMark spec. This seems a bit weird at first, but (AFAIK) this is because CommonMark tries to avoid having to parse potentially more complicated HTML in a correct way—instead it roughly says that if something looks like it starts a block of HTML then treat it like HTML until the next line break (there are a few special cases where this differs, but this is the gist). This generally works well, but can sometimes be surprising (as you point out here).

Basically, the way around this treatment of HTML blocks (and generally with CommonMark things) is to separate separate things by blank lines where possible, i.e. write:

Simple HTML

# Test

Looking at the referenced issue though, this is a bug when the HTML block of concern is script, pre, or style however. This is fixed in the 2.0.x branch but not yet in 1.8.x-beta

Thanks for the quick reply! Is there any timeframe for a release of the 2.0.x branch? Or if not, would you recommend using the current state of the 2.0.x branch over 1.8.0-beta7 in production?

This is a problem even if the post-HTML text is separated by a blank line. For example, pasting the following after the demo text leaves the "Regards" part unparsed. Both  and  are block-level elements and there's a blank line between the  and the "Regards".
Overall score: How do you score this paper?weak accept (3)
Regards,
The Conference Chairs & TPC

@schulzrinne this issue was focussed on 1.8-beta (the demo page still uses 1.7 afaik) does this happen in the latest release of the beta branch?

Yes, 1.8.0-beta-7 appears to fix this issue. Thanks for the quick follow up.
On Sun, Aug 4, 2019 at 3:56 PM Aidan Woods<EMAIL_ADDRESS>wrote:

@schulzrinne https://github.com/schulzrinne this issue was focussed on
1.8-beta (the demo page still uses 1.7 afaik) does this happen in the
latest release of the beta branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/erusev/parsedown/issues/721?email_source=notifications&email_token=AANHS5CAQPQPIGEZCFM3KULQC4X7RA5CNFSM4IGSWO52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3QIQ5Q#issuecomment-518031478,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANHS5CZ53RLOGRXDJXG25TQC4X7RANCNFSM4IGSWO5Q
.

@aidantwoods The original issue I've reported is not resolved (I tested that with 1.8.0-beta7 as I wrote in the original post). Could you please reopen the issue?


Fix missing dash on readme and rename start to starter

What was changed
This PR adds a missing dash on the Async Activity Completion README file.
It also fixes the README on the Custom Search Attributes sample that referred to a start folder, which does not exist, and should be starter instead.
In the same vein, it renames the start folder and references to it on the Sending Signals External exercise to match the rest of the files.
Why?
I had some time to kill after completing the course, and rather than opening an issue to point things out I fixed them myself.
Checklist

Any docs updates needed?
No.

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


Process exited with code<PHONE_NUMBER>

Issue Type: Bug
This occurs on my Node.js project as backend API. I've observed the pattern as:

whenever it's run as "Disable all breakpoints" or no breakpoints at all.
then "Disable all breakpoints", "Enable all breakpoints" will run ok.

This is related to this "Unbound breakpoints":
https://stackoverflow.com/questions/64589447/unbound-breakpoint-vs-code-chrome-angular/68323650#68323650
On a side note for this SO issue, I'm also running Angular v11 UI project. The way I discovered this not-hitting-breakpoint issue is most of work is on UI, and sometimes the debug execution not hitting any breakpoint at all, yet no errors printed on console, nor terminal, but execution at browser was not going anywhere, like died in the middle without any error. Meanwhile, all standalone browsers Chrome and Edge are running fine meaning they reach the expected result, not kind of execution seems lost (not hanging). After applying all fixes mentioned in this SO except "devtoolModuleFilenameTemplate: '[absolute-resource-path]'", UI project hits breakpoint always! Did I have this issue before? My memory is not before mid-June.
Because my API project is much smaller, so sometimes I simply disabled breakpoints, then this "Process exited with code<PHONE_NUMBER>" came up.
I tried to do "code --crash-reporter-directory " following https://github.com/microsoft/vscode/wiki/Native-Crash-Issues. New dump folder contains only metadata and settings.dat, "reports" folder is empty so no dump file is available for report.
Thank you!
VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:13:12.822Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
23.89GB (14.85GB free)

Process Argv
--crash-reporter-directory C:\Users\me\Documents\CanDel\VSCDump

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

openssl-configuration-file
gee
0.0.1

vscode-pull-request-github
Git
0.29.0

regionfolder
map
1.0.15

python
ms-
2021.3.680753044

vscode-pylance
ms-
2021.8.0

jupyter
ms-
2021.3.684299474

cpptools
ms-
1.5.1

debugger-for-chrome
msj
4.12.12

debugger-for-edge
msj
1.0.15

sonarlint-vscode
Son
2.0.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt700cf:30270857
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805:30301674
pythonvspyt200:30340761
vscextlangct:30333562
binariesv615:30325510
vsccppwt:30329788
pythonvssor306:30344512
bridge0708:30335490
vstre464cf:30346473

/jsDebugLogs

Thank you for the debugged log. The log you posted looks like the program exited normally, and we reported the code that it exited with. At the time it exited, breakpoints weren't touched. You're also debugging a Node.js program, I'm not sure what you're referring when you talk about browser issues. If those are separate problems, please open a separate issue.

Connor,
Forget about the browser issue, it's a totally diff one.
The exit is on a Node.js program running as backend API:
My machine is always power off at the end of the day.
First start in the morning, if F5 starts this API without any breakpoint enabled, as soon as a request comes in will cause "Process exited with code<PHONE_NUMBER>"
But if F5 with one breakpoint enabled anywhere in the execution path for a request, this breakpoint will always be hit, no more exit.
Further more, I can disable/remove any breakpoint from now on, even restarting VSC and F5, no problem.
In other words, with a breakpoint does matter for Node.js debugging. I can set up a demo over MS TEAM if needed. Let me know.
Appreciate it.
On August 17, 2021 at 10:24 AM, Connor Peet @.***> wrote:
Thank you for the debugged log. The log you posted looks like the program exited normally, and we reported the code that it exited with. At the time it exited, breakpoints weren't touched. You're also debugging a Node.js program, I'm not sure what you're referring when you talk about browser issues. If those are separate problems, please open a separate issue.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

This seems like a bug in Node.js where something is crashing. I suggest seeing if it repro's in the latest 16.x version and, if so, open an issue on them.

If it is helpful to anyone, I had the same exact problem. To solve it I recreated a new debug configuration via the menu and checked the difference with my launch.json file that I was carrying over since a few years. I then did two things, I suspect the second one was the one that actually made a difference:

Make sure the debugger type is pwa-node. Mine was still node.
Make sure skipFiles only contains the one default value.

"configurations": [
  {
    "name": "Launch Program",
    "program": "${workspaceFolder}/app.js",
    "request": "launch",
    "skipFiles": [
      "<node_internals>/**"
    ],
    "type": "pwa-node"
  }
}

I'm not sure how, probably because of the old debugger, my skipFiles settings had other values:
"skipFiles": [
    "<node_internals>/**/*.js",
    "/usr/local/lib/node_modules/**/*.js",
    "${workspaceFolder}/node_modules/**/*.js"
]

My suspicion  is that these other values create some infinite loop or memory leak somewhere in the new debugger.

I have exactly only one skipFiles
 "skipFiles": [
                "<node_internals>/**"

FYI, also have this outside of configurations, hope it's not the culprit.
"resolveSourceMapLocations": [
        "${workspaceFolder}/**",
        "!**/node_modules/**"
    ]

@TLKG With VS Code 1.60 node is just an alias for pwa-node. The underlying VS Code debugger extension (js-debug) is the same.
skipFiles is just a property that tells js-debug to ignore certain files when stepping through the code or hitting exceptions. Whether skipFiles has one or more glob patterns shouldn't matter. More patterns are just adding more files to the set of ignored files.
Having debugger extension specific properties like resolveSourceMapLocations outside of configurations doesn't make sense (and should be flagged as an error if the launch.json is opened in an editor).
These properties are defined per type (e.g. pwa-node) and they must occur in the configuration structure inside the configurtaions array.
Please use Intellisense in the launch.json editor to find the possible properties and values.
Any errors ("squigglies") in the launch.json are asking for trouble.

@weinand Thanks for the detailed instruction.

resolveSourceMapLocations outside of configurations doesn't have red squigglies, used intellisense adding into configuration.
remove the one outside.

Same outcome.


Cleanup

Remove double underscores from tests name
Remove South compatibility codes
Fix documentation problems in usage.rst

@hramezani mind if I push a couple commits on top of this branch?


React native support

It would be great to make this work on react-native too.

Would also really like to see this!
I have noticed that after my app has been running for a bit, tab switching becomes very laggy on my Android device. Swiping up and down within each tabs remains smooth. And swiping back and forth while keeping my finger on the screen seems to work okay after a few seconds.
But when I swipe between tabs it gets choppy sometimes. Reinstalling the app fixes the issue for a bit.

I have noticed that after my app has been running for a bit, tab switching becomes very laggy

Do you think we have some memory or node leak?


Bump mongodb and bson version

Bumps up mongodb and bson version to latest. Observed some performance improvements on lower end machine, but need to do more tests to get actual results on improvement.

Noticed that this will run fine when updated on a node, but spits out the following error when attempting to sync from 0:
Initializing light node - this may take a while..
2022-11-06 01:31:53 error: [Blockchain] /root/hivesmartcontracts/libs/Block.js:157
    for (let i = 0; i < contractsConfig.contractTicks.length; i += 1) {
                                        ^

TypeError: Cannot read properties of null (reading 'contractTicks')
    at Block.produceBlock (/root/hivesmartcontracts/libs/Block.js:157:41)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async createGenesisBlock (/root/hivesmartcontracts/plugins/Blockchain.js:32:5)
    at async init (/root/hivesmartcontracts/plugins/Blockchain.js:179:3)

Node.js v18.12.0

Mongodb's gone up even higher, will try again soon.


Badges misaligned inside a table row

When inside a table row the badge lacks proper vertical alignment thus being positioned slightly under the table row text.
Tested under linux Chrome 64 and Firefox 56.
Example: https://codepen.io/anon/pen/ZrQgPg
Something like
tr .badge {
  vertical-align: text-bottom;
}

would solve the problem but I think this should be a default...

This isn't something we'll universally add to Bootstrap—it all depends on how you structure your HTML. We'll pass, thanks though.


#79 TWS timeout

Codecov Report

Merging #82 (860f19a) into master (aff88d5) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #82      +/-   ##
============================================
+ Coverage     96.90%   96.92%   +0.02%
  Complexity      166      166
============================================
  Files            45       45
  Lines           355      358       +3
  Branches          8        8
============================================
+ Hits            344      347       +3
  Misses           10       10
  Partials          1        1

Impacted Files
Coverage Δ

...a/sk/ivankohut/quantifa/FmpMarketPriceOfStock.java
100.00% <ø> (ø)

.../java/sk/ivankohut/quantifa/MarketDataHandler.java
100.00% <100.00%> (ø)

...ain/java/sk/ivankohut/quantifa/TwsFundamental.java
100.00% <100.00%> (ø)

...hut/quantifa/utils/UncheckedCompletableFuture.java
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add tags to metrics

@yiminc all comments addressed. let me know if you have more concerns thanks.

Coverage decreased (-0.03%) to 65.164% when pulling bd0e70d31adfc4127b6bd040e7178811ba405f5a on metric into 8e121e2d2a6fae71c403d5070139c2881a83aad4 on master.


http:Client GET request doesn't work on 2201.2.1, but works on 2201.1.1

Description:
The following service and its resource function works fine on 2201.1.1. But on 2201.2.1 it gives error: Connection between client and remote host is closed with no other information.
import ballerina/http;

public type Country record {
    string name;
};

service / on new http:Listener(8080) {

    resource function get country/[int callingCode]() returns string|error {
        http:Client restCountriesEp = check new ("https://restcountries.com");
        Country[] countries = check restCountriesEp->get("/v2/callingcode/" + callingCode.toString());
        if countries.length() == 0 {
            return "Invalid Calling Code";
        }

        return countries[0].name;
    }
}

Steps to reproduce:
See description
Affected Versions:
2201.2.1
2201.2.2

With the update 2 we have changed HTTP2 as the default transport for http module.
This is the trace log obtained for this sample :
[2022-10-14 12:23:38,771] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb] REGISTERED
[2022-10-14 12:23:38,795] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] ACTIVE
[2022-10-14 12:23:38,814] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] INBOUND: DefaultFullHttpRequest(decodeResult: failure(java.lang.IllegalArgumentException: invalid version format: LOCALHOSTŸ), version: HTTP/1.0, content: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 0, cap: 0))
GET /bad-request HTTP/1.0, 0B
[2022-10-14 12:23:38,849] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] READ COMPLETE
[2022-10-14 12:23:38,905] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] OUTBOUND: DefaultFullHttpResponse(decodeResult: success, version: HTTP/1.0, content: CompositeByteBuf(ridx: 0, widx: 65, cap: 65, components=1))
HTTP/1.0 404 Not Found
content-type: text/plain
content-length: 65
server: ballerina
date: Fri, 14 Oct 2022 12:23:38 +0530, 65B
no matching resource found for path : /bad-request , method : GET
[2022-10-14 12:23:38,908] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] FLUSH
[2022-10-14 12:23:38,910] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] CLOSE
[2022-10-14 12:23:38,912] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] INACTIVE
[2022-10-14 12:23:38,914] TRACE {http.tracelog.downstream} - [id: 0xaaf5f4fb, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51281] UNREGISTERED
[2022-10-14 12:24:19,351] TRACE {http.tracelog.downstream} - [id: 0x3263493b] REGISTERED
[2022-10-14 12:24:19,352] TRACE {http.tracelog.downstream} - [id: 0x3263493b, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51288] ACTIVE
[2022-10-14 12:24:19,379] TRACE {http.tracelog.downstream} - [id: 0x3263493b, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51288] INBOUND: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
GET /country/1 HTTP/1.1
host: localhost:8080
user-agent: ballerina
connection: keep-alive
upgrade: h2c
HTTP2-Settings: AAEAABAAAAIAAAABAAN_____AAQAAP__AAUAAEAAAAYAACAA
connection: HTTP2-Settings,upgrade
[2022-10-14 12:24:19,380] TRACE {http.tracelog.downstream} - [id: 0x3263493b, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51288] INBOUND: EmptyLastHttpContent, 0B
[2022-10-14 12:24:19,422] TRACE {http.tracelog.downstream} - [id: 0x3263493b, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51288] OUTBOUND: DefaultFullHttpResponse(decodeResult: success, version: HTTP/1.1, content: EmptyByteBufBE)
HTTP/1.1 101 Switching Protocols
connection: upgrade
upgrade: h2c, 0B
[2022-10-14 12:24:19,423] TRACE {http.tracelog.downstream} - [id: 0x3263493b, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51288] FLUSH
[2022-10-14 12:24:19,425] TRACE {http.tracelog.downstream} - [id: 0x3263493b, L:/<IP_ADDRESS>:8080 - R:/<IP_ADDRESS>:51288] OUTBOUND SETTINGS: ack=false settings={MAX_HEADER_LIST_SIZE=8192}
[2022-10-14 12:24:19,426] TRACE {http.tracelog.downstream} - [id: 0x3263493b, correlatedSource: n/a, host:/<IP_ADDRESS>:8080 - remote:/<IP_ADDRESS>:51288] OUTBOUND: 15B

[2022-10-14 12:24:19,439] TRACE {http.tracelog.downstream} - [id: 0x3263493b, L:/<IP_ADDRESS>:8080 - R:/<IP_ADDRESS>:51288] INBOUND SETTINGS: ack=false settings={MAX_HEADER_LIST_SIZE=8192}
[2022-10-14 12:24:19,440] TRACE {http.tracelog.downstream} - [id: 0x3263493b, L:/<IP_ADDRESS>:8080 - R:/<IP_ADDRESS>:51288] OUTBOUND SETTINGS: ack=true
[2022-10-14 12:24:19,441] TRACE {http.tracelog.downstream} - [id: 0x3263493b, L:/<IP_ADDRESS>:8080 - R:/<IP_ADDRESS>:51288] INBOUND SETTINGS: ack=true
[2022-10-14 12:24:20,442] TRACE {http.tracelog.upstream} - [id: 0x3739cf2f, correlatedSource: n/a, host:/<IP_ADDRESS>:51289 - remote:restcountries.com/<IP_ADDRESS>:443] DEREGISTER
[2022-10-14 12:24:20,444] TRACE {http.tracelog.upstream} - [id: 0x3739cf2f, correlatedSource: n/a, host:/<IP_ADDRESS>:51289 - remote:restcountries.com/<IP_ADDRESS>:443] USER_EVENT: SslHandshakeCompletionEvent(SUCCESS)
[2022-10-14 12:24:20,445] TRACE {http.tracelog.upstream} - [id: 0x3739cf2f, correlatedSource: n/a, host:/<IP_ADDRESS>:51289 - remote:restcountries.com/<IP_ADDRESS>:443] CLOSE
[2022-10-14 12:24:20,449] TRACE {http.tracelog.upstream} - [id: 0x3739cf2f, correlatedSource: n/a, host:/<IP_ADDRESS>:51289 - remote:restcountries.com/<IP_ADDRESS>:443] USER_EVENT: SslCloseCompletionEvent(SUCCESS)
[2022-10-14 12:24:20,449] TRACE {http.tracelog.upstream} - [id: 0x3739cf2f, correlatedSource: n/a, host:/<IP_ADDRESS>:51289 - remote:restcountries.com/<IP_ADDRESS>:443] READ COMPLETE
[2022-10-14 12:24:20,449] TRACE {http.tracelog.upstream} - [id: 0x3739cf2f, correlatedSource: n/a, host:/<IP_ADDRESS>:51289 - remote:restcountries.com/<IP_ADDRESS>:443] UNREGISTERED
error: Connection between client and remote host is closed
[2022-10-14 12:24:20,462] TRACE {http.tracelog.downstream} - [id: 0x3263493b, L:/<IP_ADDRESS>:8080 - R:/<IP_ADDRESS>:51288] OUTBOUND HEADERS: streamId=1 headers=DefaultHttp2Headers[:status: 500, content-type: text/plain, server: ballerina, date: Fri, 14 Oct 2022 12:24:20 +0530] padding=0 endStream=false
[2022-10-14 12:24:20,467] TRACE {http.tracelog.downstream} - [id: 0x3263493b, L:/<IP_ADDRESS>:8080 - R:/<IP_ADDRESS>:51288] OUTBOUND DATA: streamId=1 padding=0 endStream=true length=51 data=51B

Changing the client version to HTTP 1.1 is working properly :
http:Client restCountriesEp = check new ("https://restcountries.com", httpVersion = http:HTTP_1_1);

Seems there is an issue when we have kind of a passthrough scenario(when we have the client calling the backend inside the service). When I added the same code sample in the main function it works without any issues.
import ballerina/io;
import ballerina/http;

public type Country record {
    string name;
};

public function main() returns error? {
    http:Client restCountriesEp = check new ("https://restcountries.com");
    Country[] countries = check restCountriesEp->get("/v2/callingcode/45");
    if countries.length() == 0 {
        io:println("Invalid Calling Code");
    } else {
        io:println(countries);
    }
}

Also when I debugged the code in the first scenario, it falls back to the HTTP1.1. And it goes through the HTTP1.1 pipeline.  After that somehow the connection gets closed.

When the client resides inside a main function, the source handler is null but inside a passthrough service, source handler is not null. The execution flow differentiate based on it. We can check based on that fact first.

There is an io.netty.channel.StacklessClosedChannelException happens when writing header to the channel between client and remote host by the client.

This flow is working fine for HTTP1.1 which was the default HTTP client version in 2201.1.1
From 2201.2.0 onwards the default version changes to HTTP2. This issue has been there for HTTP2 for long. I checked with 2201.1.2, the following error is observed
error: The secureSocket configuration should be provided to establish an HTTPS connection
        at ballerina.http.2:createSimpleHttpClient(http_client.bal:170)
           ballerina.http.2.HttpClient:init(http_client.bal:31)

Once secure socket configs added to the client config, following is observed
error: SSL connection failed:javax.net.ssl.SSLHandshakeException: General OpenSslEngine problem restcountries.com/<IP_ADDRESS>:443

When investigating further, It was found that SSL engine application protocol is chosen and HTTP1.1. When H2 channel goes through the H1 flow, before executing the request, the channel is registered to the respective Source handler after registering from the initial eventloop which bounded during the channel creating. During the deregistration channel move to connected state to closed state resulting io.netty.channel.StacklessClosedChannelException.
Hence as the solution, this deregistration is avoided for h2 channels

Related to https://github.com/ballerina-platform/ballerina-standard-library/issues/3440

Trying this scenario on 2201.2.3, but I'm still getting the same issue. Here's what I tried:
import ballerina/http;

final http:Client backendEP = check new ("https://petstore3.swagger.io/api/v3",
            config = {secureSocket: {enable: false}});

service on new http:Listener(9090) {
    resource function get store/[int id] () returns http:Response|error {
        return backendEP->get(string `/pet/${id}`);
    }
}

And as suggested above, explicitly making the client work with HTTP 1.1 works.

Trying this scenario on 2201.2.3, but I'm still getting the same issue. Here's what I tried:
import ballerina/http;

final http:Client backendEP = check new ("https://petstore3.swagger.io/api/v3",
            config = {secureSocket: {enable: false}});

service on new http:Listener(9090) {
    resource function get store/[int id] () returns http:Response|error {
        return backendEP->get(string `/pet/${id}`);
    }
}

And as suggested above, explicitly making the client work with HTTP 1.1 works.

Tried using same ballerina version and got the following response
$ curl localhost:9090/store/1 -v
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 9090 (#0)
> GET /store/1 HTTP/1.1
> Host: localhost:9090
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 200 OK
< date: Wed, 09 Nov 2022 18:38:34 GMT
< content-type: application/json
< access-control-allow-origin: *
< access-control-allow-methods: GET, POST, DELETE, PUT
< access-control-allow-headers: Content-Type, api_key, Authorization
< access-control-expose-headers: Content-Disposition
< x-http2-stream-id: 7
< server: Jetty(9.4.9.v20180320)
< transfer-encoding: chunked
<
* Connection #0 to host localhost left intact
{"id":1,"name":"Dogs","photoUrls":["adipisicing laboris"],"tags":[{"id":-24265804,"name":"ex incididunt"}],"status":"available"}* Closing connection 0


Latest code-gen changes

Description of changes:
Latest code-gen changes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


Is this project still alive?

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

This project was a scam and died in oblivion without being born.


Resolve conflicts and add new staff registration fields to ERPSAAS

Overview
This pull request resolves merge conflicts in the 3.x branch and adds enhancements to the staff registration system.
Changes Made

Resolved merge conflicts in staff_controller.php and routes/web.php.
Updated the StaffRegistrationController to handle new fields.
Modified the staff.blade.php view to add input fields for department and position.

Related Issues
Resolves #68 regarding staff registration enhancements.
Testing

Local testing on the registration form for new fields.
To-do: Test on production for existing data compatibility.

Notes for Reviewers
Please review the changes in staff_controller.php as conflicts were resolved manually.

@farhadrahmanii I will say the same thing I said on your last Pull Request.
Thank you for your time and interest in contributing. I'm sorry but what you want to merge is not something currently planned for this app. Please make a discussion post next time and we can discuss if your idea is suitable for future releases of this app.


 : Hệ thống hoàn chỉnh

Link  release :
https://github.com/HCMUS-OSSD/T2_3H2D/releases/tag/v3
Link wiki :
https://github.com/HCMUS-OSSD/T2_3H2D/wiki
https://github.com/HCMUS-OSSD/T2_3H2D/wiki/Module-đăng-tin-khuyến-mãi
https://github.com/HCMUS-OSSD/T2_3H2D/wiki/Triển-khai-Hệ-thống
@ndhuyfit

Thanks em,
Thầy đã nhận được source và thông tin của nhóm em.
Thân
On Thu, Jul 6, 2017 at 9:03 PM, Nguyen Ngoc Hau<EMAIL_ADDRESS>wrote:

Link release :
https://github.com/HCMUS-OSSD/T2_3H2D/releases/tag/v3
Link wiki :
https://github.com/HCMUS-OSSD/T2_3H2D/wiki
https://github.com/HCMUS-OSSD/T2_3H2D/wiki/Module-đ�%
83ng-tin-khuy%E1%BA%BFn-m%C3%A3i
https://github.com/HCMUS-OSSD/T2_3H2D/wiki/Triển-
khai-H%E1%BB%87-th%E1%BB%91ng
@ndhuyfit https://github.com/ndhuyfit
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HCMUS-OSSD/HuongdanThuchanh/issues/81, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIuy5k2xoNJWt5KpmAWItTn-HIjvhM7Hks5sLOlGgaJpZM4OPrmN
.

--
Nguyen Duc Huy
Department of Software Engineering
Faculty of Information Technology
University of Science, VNU (HCMC)
227 Nguyen Van Cu St., Dist. 5. HCMC, Vietnam
<EMAIL_ADDRESS>- www.fit.hcmus.edu.vn/~ndhuy


Document how to get 0.3 behaviour

I've just taken a stab at migrating from 0.3 to 2.0, and the experience has not been very smooth; to reproduce the old swagger-ui behaviour required a bunch of step-debugging through the new CoreAPI code to determine what was going on.
Worth adding some disclaimers to the migration docs?

CoreAPI doesn't provide response schemas, which django-rest-swagger 0.3 did. This makes the generated docs less useful. (https://github.com/marcgibbons/django-rest-swagger/issues/583)
CoreAPI by default doesn't render endpoints which the logged in user doesn't have permissions for. To override this and get the original 0.3 behaviour of displaying all endpoints, you need to subclass the SchemaGenerator thusly:

from rest_framework.schemas import SchemaGenerator

class PublicSchemaGenerator(SchemaGenerator):
    def has_view_permissions(self, path, method, view):
        """
        Return `True` if the incoming request has the correct view permissions.
        """
        return True

@paultiplady Thanks for the message. This project is no longer responsible for schema generation; this is now done by Django REST Framework.
Re: your two points.

CoreAPI doesn't provide response schemas.
This is true at the moment, and discussion is taking place here: https://github.com/tomchristie/django-rest-framework/issues/4502

CoreAPI by default doesn't render endpoints which the logged in user doesn't have permissions

This is true of the get_swagger_view shortcut as the request context is provided to the schema generator. To change this behaviour, write your own schema view and do not pass in the request.
See: http://www.django-rest-framework.org/api-guide/schemas/#using-an-explicit-schema-view

Hi @marcgibbons , thanks for the response. I'm aware of these points, as I spent a few hours digging into why this stuff wasn't working the same as in 0.3. I already commented on the issue that you linked; seems like it would be a good time for you to raise this library's requirements with Tom if you haven't elsewhere.
My suggestion was to document the differences so that users making the switch from 0.3 have a smoother migration path, and if they require response schemas, know that they are currently unsupported on the new version. Unfortunately I don't think that linking to the CoreAPI docs is sufficient; they are still a work in progress, and don't clearly describe how to get the 0.3 behaviour. Just saying "write your own schema" isn't very user-friendly when there are no examples of the sort of schema that we need in the CoreAPI docs; a simple example like the one I posted would have saved me a good chunk of time, and I would imagine that it would help others too.

@paultiplady As described in the docs, 2.0 breaks from 0.3 versions, so there is no upgrade guide, so to speak. The schema generation and introspection is now performed by Django REST Framework and encoded into CoreAPI documents; so duplicating documentation from these projects doesn't really make sense. Likewise, feature requests and issues related to schema generation should be raised on those channels as these features could potentially benefit other documentation formats such as blueprint.
With that said, help is appreciated to improve documentation,  perhaps an FAQ and expand on the example app.


Solves ValueError (using same graph)

Solves: ValueError problem because of not saving the graph just after loading the pre-trained weights of ResNet50.
Error:
(at execution of model.predict(image))
ValueError: Tensor Tensor("fc1000/Softmax:0", shape=(?, 1000), dtype=float32) is not an element of this graph.
System details:
Ubuntu 18.04
Keras Version: 2.1.6
Tensorflow Version: 1.8.0
Python Version: Python 3.6.5
Reference: https://github.com/tensorflow/tensorflow/issues/14356#issuecomment-385962623

Your PR will fail if the user is using a non-TF backend (such as Theano, CNTK, mxnet, etc.). If you're making TF specific checks you'll want to check and see if the user is actually using TF.


Youtube Clone (Front-End)

Issue Type:

[x] Feature Request

Describe the bug
I have a project Youtube-Clone made by HTML, CSS & Vanilla JS
Possible solution
I have made the project for the same
Screenshots

Kindly Assign me this issue!
Thanks

Issues for new projects will be assigned next week. This week we are only focussing on improving the existing ones. You can raise this issue / reopen it next week.


Update toggldesktop to 7.4.47

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Thank you for the contribution. It was merged directly as 0ed94cd445d0ade65581acc2bc4c4d3fe050b85f. Your contribution is still credited to you.


fix: enable escapeCodeTagInterpolation, fix #1540

I am not sure why it was disabled before. But I think it would make sense to have it as the better default.

Oh I see, it was for Twoslash - I will find another solution


Improved Redis config

Me again. Here is an improved Redis config, which you most want to try with m7a.large or m7a.xlarge (or higher AWS instances). Increase io-threads when needed.
I'm actually using Valkey myself, but since it's a fork of Redis. This configuration should just work fine!
I'm curious if it makes the difference!
Brief explanation:

tcp-keepalive: Try to increase the keepalive ensures idle TCP connections remain active. Most likely will not make a huge difference in your test, but on production use case it might.
allkeys-lru: Redis evicts the least recently used keys, regardless of their type or expiration status. This maximizes memory efficiency by keeping frequently accessed data in memory. There are other options as well.  On a Symfony setup I use volatile-ttl for example.
lazyfree-lazy-eviction yes: Instead of synchronously freeing memory during eviction (which could cause latency spikes), it offloads memory cleanup to a background thread.
lazyfree-lazy-expire yes: With this setting, expired keys are lazily deleted in the background. This reduces blocking operations, especially for large keys.
lazyfree-lazy-server-del yes: When commands like FLUSHALL or FLUSHDB are issued, Redis typically deletes all keys synchronously, which can be resource-intensive.
replica-lazy-flush yes: When enabled, the flush operation is performed lazily in the background, reducing latency during replication processes.
lazyfree-lazy-user-del yes: for deleting keys, Redis will delete those keys asynchronously using lazy freeing.
lazyfree-lazy-user-flush yes: If custom commands trigger a flush operation (e.g., to clear a database), those flushes are handled in the background using lazy freeing.
io-threads 2: With multi-threading enabled, Redis can process certain network I/O tasks.. Valkey give better performance here. But you can play around and increase if needed if you have more vCPUs.
io-threads-do-reads yes: Redis can use I/O threads to read requests from clients in parallel, improving performance under high network load.

Last but not least, I also try to use unixsocket to reduce the network overhead, but that depends on the stack.

You're welcome. I wanted to add that if you are testing KeyDB as well, then the IO threads option is called differently under KeyDB. When using KeyDB, use: server-threads 2
(or again, since any other higher number of threads depending on your AWS instance).

@melroy89 just tested on a single CPU (m7a.medium). It makes performance much worse (10% of using default settings). It might make sense on larger instances with 2 or more CPUs, but then you can scale it horizontally, so it's not clear if it's beneficial after all. I'll test a 3-node Redis cluster as  well and publish the results.

@melroy89 just tested on a single CPU (m7a.medium). It makes performance much worse (10% of using default settings). It might make sense on larger instances with 2 or more CPUs, but then you can scale it horizontally, so it's not clear if it's beneficial after all. I'll test a 3-node Redis cluster as well and publish the results.

That is very interesting!! I wouldn't expect it to make the performance worse!
This information is also worth sharing btw.

Ps. Could you also compare redis, Valkey, keydb and dragonfly together?

@melroy89 just tested on a single CPU (m7a.medium). It makes performance much worse (10% of using default settings).

I also said this in my original message.. This is kinda obvious right?

which you most want to try with m7a.large or m7a.xlarge (or higher AWS instances).

yes will do them later in a week or two