Export inrangecount from NearestNeighbors.jl

Export inrangecount from NearestNeighbors.jl, as discussed in https://github.com/JuliaDynamics/Entropies.jl/pull/71#discussion_r1002435920 and in #16.
Is this approach ok? I'm not sure whether to export inrangecount directly, or override it with its own docstring here.

i's okay but also bump patch version!

Hm, actually it isn't. This should be defined in the API file with a "search strcture" terminology. Then, the file that extends the API based on NearestNeighbors.jl should provide the concrete implementation.

Codecov Report
Base: 86.82% // Head: 86.66% // Decreases project coverage by -0.15% :warning:

Coverage data is based on head (55636ea) compared to base (fa1ed57).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   86.82%   86.66%   -0.16%
==========================================
  Files           6        6
  Lines         167      180      +13
==========================================
+ Hits          145      156      +11
- Misses         22       24       +2

Impacted Files
Coverage Δ

src/api.jl
78.37% <0.00%> (-1.04%)
:arrow_down:

src/kdtree.jl
84.61% <0.00%> (-0.39%)
:arrow_down:

src/bruteforce.jl
100.00% <0.00%> (ø)

src/Testing.jl
93.33% <0.00%> (+0.65%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Hm, actually it isn't. This should be defined in the API file with a "search strcture" terminology

Defining e.g. struct WithinRangeCount; r; end in api.jl, you mean? And then in kdtree.jl define the following?
function Neighborhood.inrangecount(tree::KDTree, querypt, t::WithinRangeCount)
    ....
end

@Datseris Ok, I think I got what you meant, and updated the PR accordingly. Changes:

In api.jl: Added the WithinRangeCount search type, the inrangecount function.
In kdtree.jl: Dispatch on inrangecount(::KDTree, query, ::WithinRangeCount).
Added some tests.

That's pretty much what I've meant. However I removed the type because, by the definition of its name, inrangecount always uses the WithinRange type of search, so an additional struct is not necessary.

Nice! I'll update the open PRs in Entropies.jl to use the new version of Neighborhood.jl (I assume this is merged and tagged within not-too-long).


Add some RAKwireless WisBlock based devices

@brocaar
I added some basic RAKwireless devices. Please check if we are doing it right.
About the "profiles", these devices are using LoRaMAC stack V1.0.2. I chose a naming that allows to define more profiles for LoRaMAC stack V1.0.3 and V1.0.4 that we will add later.

@brocaar
Changed the file names and removed the ^

@beegee-tokyo the test is failing:

Sensor type error!: 66

Could you please check (make sure that the input bytes are integers, not hex).

@brocaar
Can you try again

The codec tests is passing now, but it is failing on AS923_1 because in the validation I only added AS923-1, which is the official common-name, but ChirpStack itself expects AS923_1 (I think that was because of Go / Rust const to string mapping). I will update the validation to for now accept both values and then update ChirpStack to use the official naming.

(I deleted my prev. comment).
Could you update the common-names to match the Regional Parameters values? Sorry I have missed this in my review:

@brocaar
Done.

Thanks @beegee-tokyo for adding the first real device :-) All tests are passing and I have merged your PR.

🥳


demonstration: Sdk46 ibc4 nft

Description
As noted by @dreamerzq, it doesn't make a ton of sense to upgrade an sdk 45 version of ibc-go to support NFTs since NFTs are added to the cosmos sdk in v46.  This is a branch for their review, combining their work on NFTs and Notional's work on sdk 46.
In total, this changes the source of the storekey type definition, and is otherwise entirely #1413 plus #1444
assists with: #1444

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #1484 (6eea0c0) into main (2566569) will decrease coverage by 0.98%.
The diff coverage is 45.13%.

@@            Coverage Diff             @@
##             main    #1484      +/-   ##
==========================================
- Coverage   80.36%   79.38%   -0.99%
==========================================
  Files         166      172       +6
  Lines       12105    12275     +170
==========================================
+ Hits         9728     9744      +16
- Misses       1920     2067     +147
- Partials      457      464       +7

Impacted Files
Coverage Δ

...27-interchain-accounts/controller/keeper/keeper.go
94.73% <ø> (ø)

.../apps/27-interchain-accounts/host/keeper/keeper.go
83.33% <ø> (ø)

modules/apps/27-interchain-accounts/module.go
58.44% <ø> (+0.74%)
:arrow_up:

modules/apps/29-fee/keeper/keeper.go
92.39% <ø> (ø)

modules/apps/29-fee/module.go
56.60% <ø> (+1.04%)
:arrow_up:

modules/apps/nft-transfer/types/ack.go
0.00% <0.00%> (ø)

modules/apps/nft-transfer/types/keys.go
0.00% <0.00%> (ø)

modules/apps/transfer/keeper/keeper.go
94.11% <ø> (ø)

modules/apps/transfer/module.go
59.64% <ø> (+1.02%)
:arrow_up:

modules/core/02-client/proposal_handler.go
77.77% <ø> (ø)

... and 21 more


Could you provide a consistent way to calculate BLEU?

It takes several steps to calculate BLEU. And it is not absolutely clear how BLEU should be calculated with the decoded text.
I would be nice to have a eval function just calculate the BLEU in the standard and correct way against given target.

Just depending how you tokenize your text could lead to different value.
Google for "mt eval nist" or "multibleu" and you will find what you're looking for.

Our BLEU functions are correct, use the utils/get...bleu.sh script for results comparable with publications.

I think no one uses the get_ende_bleu.sh script because two lines are hard-wrapped, so it cannot be executed as is: https://github.com/tensorflow/tensor2tensor/blob/097ea5f90c53c6ca5e5356f3295f1fc3093d7afb/tensor2tensor/utils/get_ende_bleu.sh#L15-L18
It would be nice to have a way how to compute the official BLEU (both case sensitive and insensitive) for a beam-searched translation (of a possibly avg_checkpointed model) and see this curve in TensorBoard. Now, when beam-search decoding is fast (4 minutes for 3000 sentences) it seems doable (I use --save_checkpoints_secs=3600 that is one checkpoint&evaluation per hour).
It's on my todo list (together with character-based metrics, e.g. chrF3 or characTER), but unfortunately at the bottom of the list, which is rather a wish list:-).

I plan to make a PR with a script as described in my previous post.
So far I have a Python-only (no Perl) function which computes BLEU (including tokenization):
https://github.com/martinpopel/tensor2tensor/tree/bleu

Would be great to have as a metric! We're also thinking about reporting all future results (on test) with https://github.com/mjpost/sacreBLEU -- what do you think guys?

I will send a PR soon (just tidying and testing).
Thanks for pointing to sacreBLEU - the idea of autodownloading test sets and reproducible BLEU is great. There is even a PR with chrF3.
I am just missing international tokenization there (without this the correlation of BLEU with humans is much lower for languages with non-ascii characters, which includes also English with “typographic” quotes), but I can discuss this with @mjpost at sacreBLEU's github.

reporting all future results (on test) with https://github.com/mjpost/sacreBLEU

Yes. Even if sacreBLEU is integrated into T2T, I will still need most of my new code, which evaluates all checkpoints in a directory and stores the curve in TensorBoard events file (--schedule=continuous_eval evaluates just the last checkpoint and then waits for new ones, also it cannot use beam search, model averaging and I guess it would be difficult to make it use proper BLEU de/tokenization).

I did the PR: #436


Headers that is checked in middleware

I have a middleware that checks for token.
The Authorization header is Required.
but the needed header does not show up in documentation.
maybe add extra documentation support for middleware?

same as https://github.com/rakutentech/laravel-request-docs/issues/321
To both @trongio  san and @dade1987
Currently the frontend doesn't communicate with user specific config on Laravel config/request-docs.php
In order to implement this, I'd need to update the frontend, so it can obtain desired information from user as pre-loaded.
Sorry, I haven't had time to implement due to busy with many other projects and life.
I'd be open to pull reqs or please wait til I get some time off hands and push these features.

Fixed in v2.31


[RIP-11]MQTT:completing  pub and sub logic of qos=0 messages(single node only )

What is the purpose of the change
finish single-node version of publish and subscribe logic of qos=0 messages
Brief changelog

completing logic  of publishing and subscribing, unsubscribing
polish the logic of encode/decode between MqttMessage and RemotingCommand
add some NPE inSnodeController.java

Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[√] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[√] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[√] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[√] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[√] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Please rebase and resolve the conflict codes in the Conflicting file list.


Expose Data Models For Public use

Summary of Changes
Makes some properties and functions public

@pharms-eth Sorry for the long delay.
Could you please describe your intentions that led to these changes? Just curious. I do not see any particular issues with adding that to the release but wondering what were you trying to achieve.

@pharms-eth Sorry for the long delay. Could you please describe your intentions that led to these changes? Just curious. I do not see any particular issues with adding that to the release but wondering what were you trying to achieve.

storing the values using my own algorithms


Add ChipCarousel component

There are valid use cases for a ChipCarousel component that exist in the platform today (notably, on edX.org):

There is a mock Chip carousel component shown on the documentation website to demonstrate that OverflowScroll (and useOverflowScroll) may be used to create UI component-agnostic carousel-like behaviors.
This issue intends to create a true ChipCarousel component that mimics the behavior shown on the above edX.org example.
Depends on https://github.com/openedx/paragon/issues/1950

https://github.com/openedx/paragon/pull/2378


ARTEMIS-4078 Fix divert configuration reloading

Reloading has been fixed for divert:

filter
address
exclusive

Source address and exclusivity changes require divert redeployment.
Please review.

@jsmucr, nice work. Thanks for the PR!


problems with variations stock above 0

Can you reproduce this issue on default Wordpress theme (eg Storefront)?
yes
Can you reproduce this issue when all other plugins are disabled except WooCommerce, Polylang and Hyyan WooCommerce Polylang Integration?
yes
What product versions and settings are you using when this issue occurs?

PHP: 7,0,33
WordPress: 4,9
WooCommerce: 3,5,7
Polylang: [state if using Polylang PRO]
Hyyan WooCommerce Polylang Integration: 1,3,0
Browser: chrome

Steps to Reproduce

change stock in spanish product at 0,
save
changes are not updated in english product

What I Expected
expected that stock change with the updated of product
What Happened Instead
stock in variations remain the same if I set stock to 0, stock in english is not updating and remains with the last number (above 0) it has before.
If I set stock at 1... or any number above 0 it updates, the problem is only when I set stock to 0.
WordPress Environment

Name: Storefront Child 02
Version: <IP_ADDRESS>1174042
Author URL: https://woocommerce.com/
Child Theme: ✔
Parent Theme Name: Storefront
Parent Theme Version: 2.4.2 – 2.5.0 está disponible
Parent Theme Author URL: https://woocommerce.com/
WooCommerce Support: ✔
Templates
Overrides: –
`

@elliemg  I couldn't reproduce this and I tried setting stock both to 0 and blank:

is Spanish the master language?
are all the stock options enabled under Settings, WooPoly, Metas ?
are you seeing the number not updating in the front end or the admin?

Hi, answering your questions:

yes, Spanish is the master language
all the stock options are enabled
I see number not updating in front and backend

thanks for your attention

Stock synchronisation on save of product has always worked and I can't reproduce it on either this plugin 1.3 or the checked in version.
What does not work well in this plugin 1.3 is changes of stock when purchased - a complete fix for this will be released in version 1.4 in about 10 days time.
more questions:

this is when you save the product, yes?
are you setting the stock on the individual variation or at the product level?
the stock options are definitely enabled under both Settings, WooPoly, Features and Metas List?
Is this a standard Variable product or are you using another product type supplied by a plugin?
Are you able to see if the stock on the variation is updated in the database?
What other plugins are enabled?  just to reconfirm you get this with all other plugins disabled? (apart from polylang and woocommerce)

UPDATE: with the new file stock is working fine, but the price of the product does not update on the english version of the website, which gets the data from the spanish version of the website. If we change to the previous file price update right, so is this file the one messing with it now.

this is when you save the product, yes?
Yes..

are you setting the stock on the individual variation or at the product level?
I am setting the stock on the individual variation located on the product level, like this:

the stock options are definitely enabled under both Settings, WooPoly, Features and Metas List?
Yes, checkbox are selected.

Is this a standard Variable product or are you using another product type supplied by a plugin?
It is a variable product.

Are you able to see if the stock on the variation is updated in the database?
Yes.

What other plugins are enabled? just to reconfirm you get this with all other plugins disabled? (apart from polylang and woocommerce)
Other enabled plugins are: a3 Lazy Load, Admin Menu Editor Pro, Advanced Custom Fields, All-in-One WP Migration, Booster Plus for WooCommerce, Custom Product Tabs para WooCommerce, Elementor, Elementor Pro, Facebook for WooCommerce, Hyyan WooCommerce Polylang Integration, Loco Translate, Machete, MailChimp for WordPress, Menu Icons, optimizador.io, Polylang, Post Duplicator, Really Simple SSL, Redsys WooCommerce, tipsacarrier, WooCommerce, WooCommerce added to cart popup (Ajax), WooCommerce Live Checkout Field Capture, WooCommerce Product Feed, WooCommerce QR Codes, WooCommerce Variation Swatches.

Thanks for your help.

We've just sent you an invitation to see our project on GitHub

Hi,

about Settings, WooPoly, Metas, your screenshot shows the Features page, the pricing and stock meta needs to be turned on, on the other tab.
please test with those other plugins turned off - this is one of the questions at the beginning of the ticket.

Some of those plugins definitely have the potential to interfere with the product saving process, such as:
Advanced Custom Fields
WooCommerce Variation Swatches
Booster Plus for WooCommerce
Custom Product Tabs para WooCommerce
Elementor
WooCommerce Variation Swatches
[as far as I know some of those plugins do also have the potential to break each other as well so this looks like quite a challenging installation]
Thanks for the invitation, but I am just helping out debugging this plugin in my free time, and I don't have enough free time to do detailed debugging of other people's projects.
Anyhow, most likely another plugin is hooking the saving process and disturbing the normal sequence of events.  It would be good to know which one.
In the meantime I'll add some defensive code to stock.php for this tomorrow.

hi Jon,
thank you very much for taking your time in answering :)
I understand what you mean with plugins but we deactivate every plugins leaving just woocommerce, Polylang and Hyyan actived, and it doesn't update price either... so maybe we can dismiss the compatibility with other plugins?
We really appreciate your help as we are looking at the code and don't really get how it works... :-/

Ok, I have verified that save on the product screen for Variable product is triggering the stock synchronisation.  This is not causing a problem in my setup but is not necessary and could potentially be causing conflict with other plugins hooking into the product save process.
I am testing some defensive code to eliminate the possibility, and will check it in within 24 hours.


FetchStreamState returns null

When there is no stream for a given streamId or streamKey the FetchStreamState returns null. Could you please change the signatures of the methods to reflect that they return nullable StreamState? instead of StreamState?
Thanks,
Denys

Fixed in a branch.


[AutoPR iothub/resource-manager] typo: iothub/resource-manager/Microsoft.Devices/iothub.json

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4512

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/547


[Backend] Forget&Reset Password Functionality for Brand and Influencers

Description

[ ] Create an API in backend which will help the influencer/brand to reset their password.
[ ] Make sure to have the authorization check so that the brand/influencer can only reset their own password, maybe otp on email can help to achieve the same.(I am all ears to hear about better method)

[ ] Create one more API in backend which will help the influencer/brand to update their password.
[ ] Verify their token and the body of reset will be currentPassword, newPassword, so make sure you match the currentPassword value existing in the db before updating it.

Hey @Kajol-Kumari  @RohitGupta1237
I'm interested to work on the issue.

@BHS-Harish hey any doubt with the task?

@BHS-Harish hey any doubt with the task?

Now not @RohitGupta1237
I'm currently working on another issue and once i completed that, i will work on this issue.

Hello Sir,
My name is Shivam Kanchole, and I am a fourth-year student at IIT Roorkee. I find this issue both interesting and challenging. Additionally, I have worked on similar projects in the past. Could you please assign this issue to me?
Thank you.
Best regards,
Shivam Kanchole

@Shivam2534  hey assigned you this ..u can work on this ...happy learning

@Shivam2534 hey can u work on this issue first as #11 issue is completed already

@BHS-Harish can u please confirm if u are working on this issue?

Hello @Kajol-Kumari  I'm not started..
If @Shivam2534 Interested on the issue, kindly assign him.

@Shivam2534 hey any doubts with issue ?

Not yet
On Mon, 17 Jun, 2024, 8:57 pm RohitGupta1237, @.***>
wrote:

@Shivam2534 https://github.com/Shivam2534 hey any doubts with issue ?
—
Reply to this email directly, view it on GitHub
https://github.com/Kajol-Kumari/InfluMart/issues/37#issuecomment-2173712001,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHVOBI3CFAV6SNI35REXDFDZH354LAVCNFSM6AAAAABJIJUBWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZTG4YTEMBQGE
.

@RohitGupta1237 Assign it to me my exams are over so i will resolve it ASAP.

@UtkarshBirla28 can you take this issue ASAP?

@Kajol-Kumari Yah sure

@UtkarshBirla28 hey any updates ? any doubts

@RohitGupta1237 i will start from today

@UtkarshBirla28  hey try to wrap this today only we r short of time pls

@RohitGupta1237 sure

@RohitGupta1237 i have a question
i have setuped everything backend , frontend, DB but ur login and signup pages r not working at all
so i have made some mistakes or these pages r not working ??

Ig i have to use postman for authentications

@UtkarshBirla28  login page username not email to login

Can we connect on meet for 5 mins u will get idea how it’s working

seee

 seee

request is not going

@UtkarshBirla28

its working here

@RohitGupta1237 ha on netlify it is working but on my local it's not

backend is also connected

and DB is also running

seee

@RohitGupta1237 I am sorry but assign it to someone else .

@RohitGupta1237  can you please assign this to me.


Unclear Error Message - High Performance Banks

When using e.g. Y5 or W5 (bank 3 / 4 / 5) on the Lattice Crosslink-NX Eval Board, LVCMOS33 doesn't work (not supported). And in my case I was trying to use I2C (BIDIR_LVCMOS33). The error message (below) is helpful in that it lists all available standards, but I think it could benefit from a quick explanation detailing that pins in banks 3, 4 and 5 require the 'H' appended to the standard (AFAIK). Something like "Btw, this bank needs H appended (and only goes up to 1.8v)".
In my (newb) case, I spent 1/2 a day thinking these pins didn't have bidir IO primitives (as even the lattice radiant tool will error for the i2c design I was using) (of course, radiant error messages are completely useless). Only figured it out when I changed the pins from inout to out in the generated litex verilog (I was planning to use open drain instead of bidir IO) and that didn't fix the design.
Could even go so far as to automatically switch to '*H' standards in the tool (not sure if there are other gotchas here though).
Info: Program finished normally.
thread 'main' panicked at 'No option named BIDIR_LVCMOS33 for enum PIOA.SEIO18.BASE_TYPE in tile CIB_R56C12:SYSIO_B5_0.
Valid options are: BIDIR_HSTL15_I, BIDIR_HSUL12, BIDIR_LVCMOS10H, BIDIR_LVCMOS12H, BIDIR_LVCMOS15H, BIDIR_LVCMOS18H, BIDIR_SSTL135_I, BIDIR_SSTL135_II, BIDIR_SSTL15_I, BIDIR_SSTL15_II, INPUT_HSTL15_I, INPUT_HSUL12, INPUT_LVCMOS10H, INPUT_LVCMOS10R, INPUT_LVCMOS12H, INPUT_LVCMOS15H, INPUT_LVCMOS18H, INPUT_SSTL135_I, INPUT_SSTL135_II, INPUT_SSTL15_I, INPUT_SSTL15_II, NONE, OUTPUT_HSTL15_I, OUTPUT_HSUL12, OUTPUT_LVCMOS10H, OUTPUT_LVCMOS12H, OUTPUT_LVCMOS15H, OUTPUT_LVCMOS18H, OUTPUT_SSTL135_I, OUTPUT_SSTL135_II, OUTPUT_SSTL15_I, OUTPUT_SSTL15_II
Please make sure Oxide and nextpnr are up to date and input source code is meaningful. If they are, consider reporting this as an issue.', prjoxide/src/chip.rs:415:75

Also, it seems prjoxide won't tell you which pins are causing the issue. E.g. I have a pdc like:
ldc_set_location -site {P1} [get_ports clk]
ldc_set_port -iobuf {IO_TYPE=LVCMOS18H} [get_ports clk]

but there's no mention of any signals (e.g. clk) in the output:
Info: Program finished normally.
prjoxide pack ppm_uart_bridge.fasm ppm_uart_bridge.bit
thread 'main' panicked at 'No option named INPUT_LVCMOS18 for enum PIOA.SEIO18.BASE_TYPE in tile CIB_R56C12:SYSIO_B5_0.
Valid options are: BIDIR_HSTL15_I, BIDIR_HSUL12, BIDIR_LVCMOS10H, BIDIR_LVCMOS12H, BIDIR_LVCMOS15H, BIDIR_LVCMOS18H, BIDIR_SSTL135_I, BIDIR_SSTL135_II, BIDIR_SSTL15_I, BIDIR_SSTL15_II, INPUT_HSTL15_
I, INPUT_HSUL12, INPUT_LVCMOS10H, INPUT_LVCMOS10R, INPUT_LVCMOS12H, INPUT_LVCMOS15H, INPUT_LVCMOS18H, INPUT_SSTL135_I, INPUT_SSTL135_II, INPUT_SSTL15_I, INPUT_SSTL15_II, NONE, OUTPUT_HSTL15_I, OUTPU
T_HSUL12, OUTPUT_LVCMOS10H, OUTPUT_LVCMOS12H, OUTPUT_LVCMOS15H, OUTPUT_LVCMOS18H, OUTPUT_SSTL135_I, OUTPUT_SSTL135_II, OUTPUT_SSTL15_I, OUTPUT_SSTL15_II
Please make sure Oxide and nextpnr are up to date and input source code is meaningful. If they are, consider reporting this as an issue.', prjoxide/src/chip.rs:415:75
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [Makefile:34: ppm_uart_bridge.bit] Error 101

of course, I can get around this by looking this up in the datasheet / playing around with Radiant / just guessing LVCMOS18 or LVCMOS18H for each signal til I get it right, but clearer error messages would be most ideal :)

Agreed, I will assign this to myself to fix in the nextpnr IO handling code.

https://github.com/YosysHQ/nextpnr/pull/1105


Map logos section and colour revision

Following suggestions from UX team about issues with the current colour contrast, the following updates are required:

[ ] orange colour for the whole site (including logos and title top section) to be changed to

design of top section to be changed to this:

More information here: https://drive.google.com/drive/folders/1sr0939J5ZV27FuA-AMdVy5J0VAJ8FmDn
including the white Austrade logo


Is it possible to change the radio system?

Was wondering if it would be possible to change the radio station tuner as in the UK we dont have SXS, its Tune in. Happy to try and do the work.
Just need to know where to start and if its even possible.
If anyone can help Thanks.
PS Awesome work done on this Thanks for all the time and effort,!

node-sonos-http-api has an issue open to add tune-in
https://github.com/jishi/node-sonos-http-api/issues/366

I have partially  worked around this by adding the radio stations I normally listen too as favorites and  then "Ask Sonos to play the favourite FAVOURITE_NAME in ROOM"  works.


Takes minutes to compile

Using latest stable build <IP_ADDRESS>:
Every reload of the webpage uses an enormous amount of time on the .scss files. A 300 line file takes 3-10 second (varies videly), and bootstrap takes several minutes.
Bootstrap uses around 1.1 minute, (comparably, it takes around 1.5 seconds with LESS and dotless)

Use the Alpha & beta versions. the "Stable" versions are unstable.
https://www.nuget.org/packages/libsassnet.Web/2.3.0-alpha-1
and
https://www.nuget.org/packages/libsassnet/3.3.7-alpha-2

Thank you! That worked. Now it's actually 10 times faster than our LESS compilator. Any idea when this is out of alpha?
Maybe you should mention this in the README.md? https://github.com/darrenkopp/libsass-net

@darrenkopp do you have time to push those as proper versions?

the latest version is in stable channel on nuget now.


Change workflow to use a reusable workflow for building the Go release

Changes introduced with this PR
Modify the build to use the arcaflow-reusable-workflows/go_release.yaml reusable workflow.

By contributing to this repository, I agree to the contribution guidelines.

@jaredoconnell, the build appears to have run fine, but GH is still looking for a job from the old build (which isn't going to run, let alone report status), so, once this is approved, you'll need to use the Admin override to merge it.

This PR is now back in draft awaiting https://github.com/arcalot/arcaflow-reusable-workflows/pull/17.

This appears to have been merged, but not closed due to a Github glitch.


Enhancement: Enable yoda_style fixer and enforce non-yoda-style comparisons

This PR

[x] explicitly requires friendsofphp/php-cs-fixer:^2.7.1 (already locked to, but composer.json doesn't reflect it)
[x] enables the yoda_style fixer and enforces non-yoda-style comparisons
[x] runs make cs

Follows https://github.com/opencfp/opencfp/pull/500#pullrequestreview-67378081.
💁♂ For reference, see https://github.com/FriendsOfPHP/PHP-CS-Fixer#usage:

yoda_style [@Symfony]
Write conditions in Yoda style (true), non-Yoda style (false) or ignore those conditions (null) based on configuration.
Configuration options:

equal (bool, null): style for equal (==, !=) statements; defaults to true
identical (bool, null): style for identical (===, !==) statements; defaults to true
less_and_greater (bool, null): style for less and greater than (<, <=, >, >=) statements; defaults to null

Perfection! Thanks @localheinz. Looks good to me.

Thank you, @mdwheele!


Swipe back navigation

Hey again.
UIKIt navigation with compose is too laggy now so i just added iOS-like compose swipe back navigation.

Thanks for the PR!
Do you run the ./gradlew spotlessApply to apply the code style?

Done. May be it will also be good to have an ability to set swipe properteis for each route separatly like nav transition?

@Tlaster, I guess PR is ready for review

How can I use the new features?


fix: compression status for cephblockpool

Signed-off-by: Rishabh Bhandari<EMAIL_ADDRESS>

/cherry-pick release-4.11-compatibility


Add condition config for use with lazy

Discussed in https://github.com/willothy/flatten.nvim/discussions/27

Originally posted by herrvonvoid March 25, 2023
...  this way of setting the plugin up with lazy.nvim is not very convenient because then flatten.nvim appears as plugin to clean in the lazy ui and has to be reinstalled every time I clean some other plugins. How about putting the check in lazy.nvim's global condition (defaults.cond) instead?  ...

Checking if the instance is host or guest is not possible until after the plugin has loaded due to the wezterm/kitty logic, so I don't think I'm going to implement this. Loading flatten.nvim first should be fine, that's what I have always done.


Update example pub key log in machine account creation documentation

Description
The encoding used by the tool changed since this example was created. This ensures the example has the same length as those generated by operators following this doc, to prevent confusion.

⚠ Push and update hashes for boot-tools after https://github.com/onflow/flow-go/pull/1226 ⚠


(PUP-5502) Improve error messages for faulty hiera.yaml

Errors originating from syntax errors in the hiera.yaml were nested
and the error messages were repeated, resulting in a long blob of
unhelpful text where the original stack trace was lost.

Merged. Should have gone to stable though. Not sure if this cherry picks over...


⚠ Bofrost.lu has degraded performance

In 8d93640, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2769 ms

Resolved: Bofrost.lu performance has improved in eed6a82 after 6 minutes.


This plugin is incompatible with asdf-java

Currently this plugin is not really usable alongside asdf-java, since both want to install shims for java, javac etc. Edit: To be precise, when I have both a jdk (through the java plugin) and graalvm 19.0.0 installed, java etc. still point to the versions from the jdk while graalvm-specific binaries like gu point to graalvm. And I don't really know how I would solve this.
I couldn't find any general asdf "policy" for different plugins that use the same binary names, don't know if this ever came up?
One idea for compatibility might be to e.g. deprecate this plugin and add support for graalvm-x.y.z "versions" to the java plugin instead?

Ok, maybe I was a bit too fast there: I now found this closed issue and this PR. I experimented a bit more, and it seems to work as long as I don't have a global version of Java set in my ~/.tool-versions. As long as my individual project folders then have either a java or a graalvm version set in their .tool-versions, java etc. will point to the right version. As soon as I have a global default java version, that always seems to override the tools from graalvm, even if I am in a folder that just has graalvm in the .tool-versions.

Ok probably a bug in asdf itself. We could write a test reproducing your directory layout and .tool-versions placement and asdf whould fail for it.


[AutoPR keyvault/resource-manager] Keyvault preview

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2798

(message created by the CI based on PR content)


TypeError: rasterize_gaussians(): incompatible function arguments. The following argument types are supported:

Is there anybody sattle this bug? In other 3dgs project, i never meet this bug, only in [GPS-Gaussian]. how can i solve it?
TypeError: rasterize_gaussians(): incompatible function arguments. The following argument types are supported:
1. (arg0: torch.Tensor, arg1: torch.Tensor, arg2: torch.Tensor, arg3: torch.Tensor, arg4: torch.Tensor, arg5: torch.Tensor, arg6: torch.Tensor, arg7: torch.Tensor, arg8: float, arg9: torch.Tensor, arg10: torch.Tensor, arg11: torch.Tensor, arg12: float, arg13: float, arg14: int, arg15: int, arg16: torch.Tensor, arg17: int, arg18: torch.Tensor, arg19: bool, arg20: bool) -> Tuple[int, torch.Tensor, torch.Tensor, torch.Tensor, torch.Tensor, torch.Tensor]

Hi, have you solve this problem? I meet the same problem.

s

So am I

Hi, have you solve this problem? I meet the same problem.

So am I

is the problem solved? what is the soln ?

Apparently, This is a problem that comes when there is a mismatch with diff-gaussian-rasterization submodule. one solution is discard the entire environment you might have created, clone the git again, create a new conda environment & start all over.

have you solve this problem?

Yeah. I got this error when i was executing one of the already existing implementations of another paper. After i reinstalled the conda environment, the error was gone

Yeah. I got this error when i was executing one of the already existing implementations of another paper. After i reinstalled the conda environment, the error was gone. For your case you may try reinstalling just the submodule part.

Thank you for your reply.That is work!


[Feature Request] Add cuDNN-accelerated LSTM and GRU to PyTorch

Hi,
are there any plans to add cuDNN-accelerated versions of LSTM and GRU to the PyTorch backend? Without cuDNN acceleration, the LSTM and GRU are considerably (several times) slower, even when running on GPU; however, we still use RNNs heavily (for example, adding them after Transformer encoder still helps in some cases).
The torch.nn.LSTM/torch.nn.GRU offer cuDNN acceleration, and wrapping them to a keras.layers.Layer works, but the resulting model is not backend-agnostic (so the resulting model cannot be used cross-frameworks).
Thanks for consideration :pray:  and cheers!
PS: Relatedly, torch.nn.LSTM/GRU offers bidirectional computation by a single call (by passing bidirectional=True) -- I am not sure how much faster it is compared to two asynchronous unidirectional computations, but if it is faster, keras.layers.Bidirectional would probably have to be updated to handle keras.layers.LSTM and keras.layers.GRU specifically to support it.

@foxik Thanks for the issue!
Would you like to contribute this by modifying the following file?
https://github.com/keras-team/keras/blob/master/keras/backend/torch/rnn.py#L377C1-L382C30

@haifeng-jin I am not sure I can do it correctly. I assume that

The cudnn_ok will probably need to consider also the current device (whether it is cuda or not) [in addition to verifying that the arguments are supported by CuDNN implementation)

that may require changes in the code, because cudnn_ok is currently being called only for tensorflow backend; on the other hand, it is used only to set supports_jit to False, which is probably not needed for PyTorch, because the sources indicate that TorchScript can compile torch.nn.LSTM/GRU.

the torch.nn.LSTM/GRU is a whole layer including parameters, but we need to use the given parameters. Therefore, we should probably call torch._VF.lstm/gru, but I am not sure whether that would be considered OK
nontrivial care must be taken to assure the results of CuDNN branch are the same as the usual branch
the go_backwards has no direct analogue in Torch API, so some manual reversing will be needed
on the other hand, bidirectional run is supported by Torch API, so

similarly to backend.lstm/gru, backend.lstm/gru_bidirectional should be introduced
Bidirectional wrapper should try calling this lstm/gpu_bidirectional to use CuDNN-accelerated bidirectional call (only PyTorch would implement this method)
With this support in place, the go_backwards would not be used in PyTorch for most usages, so it would not matter its implementation would not be great

In any case, for the time being I unfortunately do not have time to work on this.

This feature would be great indeed. Hopefully someone high capable will attend to this sometime soon.


Deprecation error on jasmine 4.0

ERROR: 'DEPRECATION: The matcher factory for "toBeObservable" accepts custom equality testers, but this parameter will no longer be passed in a future release. See <https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0#matchers-cet> for details.
Error:
    at <Jasmine>
    at addMatchers (http://localhost:9876/_karma_webpack_/webpack:/node_modules/jasmine-marbles/es6/index.js:92:1)
    at UserContext.<anonymous> (http://localhost:9876/_karma_webpack_/webpack:/node_modules/jasmine-marbles/es6/index.js:130:1)
    at ZoneDelegate.invoke (http://localhost:9876/_karma_webpack_/webpack:/node_modules/zone.js/fesm2015/zone.js:372:1)

Yep, seeing this too. Thank you for raising it.

Would someone like to put in a PR for this?

If I understand correctly, all that needs to be changed is to remove _equalityTester from this line
https://github.com/CodeSequence/jasmine-marbles/blob/master/index.ts#L71

Yes, that looks correct on the change. For the release, it would be under the 0.9.x release so you can just target the master branch for the PR.


Conan package

It would be nice to have a conan package available for this project. I've created a conan2 recipe, let me know if you would like to review it.

It would be nice to have a conan package available for this project. I've created a conan2 recipe, let me know if you would like to review it.

Admittedly, I haven't used Conan up to now. However, it is certainly a good idea to support package management systems to make the component available for more users/developers.
So, yes, I'd like to review your Conan recipe.

I will create a PR for Issue#109 regarding cmake install first. If the build system handles the copy of the files (headers, lib etc..), the conan recipe will be shorter and cleaner.
I have one question to this topic. This is the list of headers which are added to the cmake target:
src/cipher_common.h
src/cipher_config.h
src/fastpbkdf2.h
src/mystdint.h
src/rijndael.h
src/sha1.h
src/sha2.h
src/sqlite3.h
src/sqlite3ext.h
src/sqlite3mc.h
src/sqlite3mc_vfs.h
src/sqlite3userauth.h
src/test_windirent.h
Which ones shouldn't be used by users? I would only move the public ones to the include folder.

I will create a PR for Issue#109 regarding cmake install first.

Great. TIA.

If the build system handles the copy of the files (headers, lib etc..), the conan recipe will be shorter and cleaner.

The "problem" with SQLite is that there are so many configuration options.

I have one question to this topic. This is the list of headers which are added to the cmake target:

[ ] src/cipher_common.h
[ ] src/cipher_config.h
[ ] src/fastpbkdf2.h
[ ] src/mystdint.h
[ ] src/rijndael.h
[ ] src/sha1.h
[ ] src/sha2.h
[x] src/sqlite3.h - the include file of the original SQLite library
[x] src/sqlite3ext.h - optional, required only when creating own SQLite extensions
[x] src/sqlite3mc.h - main include file (includes all necessary header files)
[x] src/sqlite3mc_vfs.h - public API of the encryption VFS
[x] src/sqlite3userauth.h - optional, only used if user authentication extension is enabled
[ ] src/test_windirent.h

Which ones shouldn't be used by users? I would only move the public ones to the include folder.

Only the flagged header files should be made public, all not flagged header files are used internally only.

I will add to the recipe that zlib and icu are conditionally required, based on the compiler flags. But I haven’t found information about the minimum required versions. Do you have a suggestion?

I will add to the recipe that zlib and icu are conditionally required, based on the compiler flags. But I haven’t found information about the minimum required versions. Do you have a suggestion?

Well, actually the SQLite extensions should work with any prior version. Actually, I haven't tested whether there are prior versions of zlib and icu, which would not work. We can set the following minimum version numbers for now, although it is very likely that prior versions could be used as well.

ICU: The first version used together with SQLite3 Multiple Ciphers was version 67.1.
zlib: let's use version 1.2.9 as the minimum version. That version was released in 2017.

Regarding zlib the user can choose to use the included miniz implementation avoiding the external dependency.

Thank you for the information.
I have added the conan recipe in the PR. I wrote (the non-existing) version 1.7.5, since that will be the first version that contains the latest cmake changes required by this recipe. The SHA hash of the new package file will be needed in the conandata.yml.
I think you should be the one to upload the package to conan center as the project owner. You can find the guideline for the process here:
https://docs.conan.io/en/1.17/uploading_packages/bintray/conan_center_guide.html
But based on the guideline, a test_package is necessary. I'll have to add one to my recipe. I'll update my PR with it in a few days.
I believe the conan folder won't be necessary in the repo once the package is uploaded to the conan center.

I have added the conan recipe in the PR. I wrote (the non-existing) version 1.7.5, since that will be the first version that contains the latest cmake changes required by this recipe. The SHA hash of the new package file will be needed in the conandata.yml.

Thanks. We will see what the version number of the next release will be. Maybe 1.7.5, maybe 1.8.0 - depends on how my own activities will proceed.

I think you should be the one to upload the package to conan center as the project owner. You can find the guideline for the process here: https://docs.conan.io/2/tutorial/conan_repositories/conan_center.html

I will try to study the guidelines within the next days.

But based on the guideline, a test_package is necessary. I'll have to add one to my recipe.

What sort of test package? For example, my GitHub workflow executes some SQL scripts testing to access encrypted database files.

I'll update my PR with it in a few days.

Ok, I'll wait with merging, until I get the green light from you.

I believe the conan folder won't be necessary in the repo once the package is uploaded to the conan center.

Meaning what? IMHO it's not a bad idea to keep these files in a separate directory in the repo.

What sort of test package? For example, my GitHub workflow executes some SQL scripts testing to access encrypted database files.

It's for testing the package itself rather than the underlying source code. It ensures that consumers can link to the package and use it.

Ok, I'll wait with merging, until I get the green light from you.

I have added a new commit, I think it's okay now. The remaining necessary modifications are to update the version numbers once the 1.7.5/1.8.0 is released, and to add the SHA to the conanfile.yml. Then the process of adding the package to the conan center can be started. When you check out the repo mentioned in the guide, there will be the recipes folder. There you can create the folder for the project, and everything from this repo's conan folder can go there.

Meaning what? IMHO it's not a bad idea to keep these files in a separate directory in the repo.

As far as I remember, projects usually don't contain the conan recipe in their repo, only on the conan center. But if you want to have it here as well, that's fine by me.

I have found an issue during testing when I include sqlite3mc.h instead of sqlite3.h:
sqlite3mc.h(16,10): error C1083: Cannot open include file: 'sqlite3mc_version.h': No such file or directory
I'll have to check that.
A question: I have seen in many conan recipes, that they define the option fPIC true by default, and remove the option if the os is Windows. Do you think I should add this option to the recipe?

I have found an issue during testing when I include sqlite3mc.h instead of sqlite3.h: sqlite3mc.h(16,10): error C1083: Cannot open include file: 'sqlite3mc_version.h': No such file or directory I'll have to check that.

In the conan recipe no header files are mentioned. Maybe the header file sqlite3mc_version.h was not copied to wherever the header files are expected to be?

A question: I have seen in many conan recipes, that they define the option fPIC true by default, and remove the option if the os is Windows. Do you think I should add this option to the recipe?

Good question. AFAIK the autoconf/automake build files coming with sqlite3mc handle that automatically under the hood. But in CMake it may be necessary to specify the option explicitly.

What sort of test package? For example, my GitHub workflow executes some SQL scripts testing to access encrypted database files.

It's for testing the package itself rather than the underlying source code. It ensures that consumers can link to the package and use it.

Ok.

I have added a new commit, I think it's okay now. The remaining necessary modifications are to update the version numbers once the 1.7.5/1.8.0 is released, and to add the SHA to the conanfile.yml.

Ok.

Then the process of adding the package to the conan center can be started. When you check out the repo mentioned in the guide, there will be the recipes folder. There you can create the folder for the project, and everything from this repo's conan folder can go there.

I will check with the conan docs.

Meaning what? IMHO it's not a bad idea to keep these files in a separate directory in the repo.

As far as I remember, projects usually don't contain the conan recipe in their repo, only on the conan center. But if you want to have it here as well, that's fine by me.

On the one hand, it's logical to not have the recipe in the repo. At least not the final version due to the sha256 checksum.
On the other hand, it does no harm to have the recipe template in the repo. For now, I guess I will keep it in the repo.

In the conan recipe no header files are mentioned. Maybe the header file sqlite3mc_version.h was not copied to wherever the header files are expected to be?

Yeah that was the issue. In this case, I have to modify the CMakeLists.txt to copy every header files during install.

Good question. AFAIK the autoconf/automake build files coming with sqlite3mc handle that automatically under the hood. But in CMake it may be necessary to specify the option explicitly.

I will add it to the recipe.

In the conan recipe no header files are mentioned. Maybe the header file sqlite3mc_version.h was not copied to wherever the header files are expected to be?

Yeah that was the issue. In this case, I have to modify the CMakeLists.txt to copy every header file during install.

Really EVERY header file? It would be good if that could be restricted to the header files required by applications using sqlite3mc.

You're right, I have checked and sqlite3mc_version.h is the only additional header that's needed, so I only add that to the list when installing.

Good question. AFAIK the autoconf/automake build files coming with sqlite3mc handle that automatically under the hood. But in CMake it may be necessary to specify the option explicitly.

I will add it to the recipe.

To the CMake recipe I guess.
I will still wait a bit before merging your PR.
Yes, I will update my PR this evening.

@Myroendan: I created a PR in the Conan repository. Unfortunately, at least 2 checks failed.
Could you please take a look: https://github.com/conan-io/conan-center-index/pull/21354? TIA.

In the meantime I applied a few minor adjustments (i.e. removing C++ compiler settings, because the library is a C library). Nevertheless, some build check steps still fail. The reason seems to be, that in the Conan check environment only an old CMake version 3.15.7 is available while sqlite3mc's CMake file asks for version 3.24.0 or higher.

I see the yaml linter threw an error for the "---" beginning. I included that in the first place due to their guidelines: the yaml linter warned me locally that it was missing, well nevermind. I see you removed it from the conandata.yml, the config.yml also has it.
conan v1 pipeline: the recipe is not conan1 compatible. I don't know if its a requirement for a new recipe, but it would be weird, since they're trying to push everyone towards conan2.

The reason seems to be, that in the Conan check environment only an old CMake version 3.15.7 is available while sqlite3mc's CMake file asks for version 3.24.0 or higher

Yeah, this is also interesting. I think we could downgrade our CMake requirement to 3.15.7, I don't think we use features that require a higher version (I'll have to check it). But does this mean conan is not supporting projects using CMake with a version higher than 3.15.7? That's a 4 years old version.

Could you please clarify point 2 and 3 with them?

I see the yaml linter threw an error for the "---" beginning. I included that in the first place due to their guidelines: the yaml linter warned me locally that it was missing, well nevermind. I see you removed it from the conandata.yml, the config.yml also has it.

Yes, I saw that, after the checks failed again. I'll remove the line from that file, too, once I get information about the other issue.

conan v1 pipeline: the recipe is not conan1 compatible. I don't know if its a requirement for a new recipe, but it would be weird, since they're trying to push everyone towards conan2.

Personally, I don't see that failure as a real error, because all recipes should be using version 2. Interestingly, less than 20 recipes ofover 1600 recipes refer to version 2 at all in their required_conan_version, and if they do it is a combination like required_conan_version = ">=1.56.0 <2 || >=2.0.6".

Yeah, this is also interesting. I think we could downgrade our CMake requirement to 3.15.7, I don't think we use features that require a higher version (I'll have to check it). But does this mean conan is not supporting projects using CMake with a version higher than 3.15.7? That's a 4 years old version.

In the Conan documentation I see nowhere mentioned that CMake support is restricted to version below 3.15.7.

Could you please clarify point 2 and 3 with them?

I opened issue https://github.com/conan-io/conan-center-index/issues/21358. We will see what answer we get.

Personally, I don't see that failure as a real error, because all recipes should be using version 2. Interestingly, less than 20 recipes ofover 1600 recipes refer to version 2 at all in their required_conan_version, and if they do it is a combination like required_conan_version = ">=1.56.0 <2 || >=2.0.6".

I think it's because conan2 was released this February, and most of these projects were available since conan1. The recipes were adjusted to support conan2 as well, but they didn't want to break the already existing conan1 support.

Coming from https://github.com/conan-io/conan-center-index/issues/21358
conancenter recipes adjust required_conan_version depending on features they rely on. It turns out that 95% of conancenter recipes use "conan v2" features implemented in conan<=1.53.0, and therefore there is absolutely no reason to ask for a more recent conan version to users (except when you don't like them).
This required_conan_version = ">=1.56.0 <2 || >=2.0.6" (which should be required_conan_version = ">=1.60.0 <2 || >=2.0.5" actually) you can see in few recipes comes from usage of a feature (foo/<host_version> in build requirements when foo is also in requirements) implemented in conan 2.0.5 and backported to conan v1.

conancenter recipes adjust required_conan_version depending on features they rely on. It turns out that 95% of conancenter recipes use "conan v2" features implemented in conan<=1.53.0, and therefore there is absolutely no reason to ask for a more recent conan version to users

Well, all over the Conan place one reads about the transition to version 2, and that recipes have to be compatible with version 2. Staying compatible with version 1 means that no "version 2 only" feature can be used.

(except when you don't like them).

Sorry, this remark was unnecessary and inadequate.

This required_conan_version = ">=1.56.0 <2 || >=2.0.6" (which should be required_conan_version = ">=1.60.0 <2 || >=2.0.5" actually) you can see in few recipes comes from usage of a feature (foo/<host_version> in build requirements when foo is also in requirements) implemented in conan 2.0.5 and backported to conan v1.

I changed the version requirement, but the Conan v1 Pipeline check still fails. However, the Conan v2 Pipeline check finally completed successfully a few minutes ago.

Finally, both Conan Pipelines succeeded. Now, we have to wait for the required 2 approving reviews.

Finally, both Conan Pipelines succeeded. Now, we have to wait for the required 2 approving reviews.

Great! Thank you.

HI,
did you receive any news from conan team since?

did you receive any news from conan team since?

No. The Conan pipelines all show green, but the PR is still waiting for a second review. On this page you can find a section "Time Spent in Review". The average is well above 30 days at the moment, with many entries way over 60 days. So, just keep your patience. I will close this issue, once the recipe will have been accepted.

Week after week is passing by ... nothing happens ... no comments to my/our remarks ... no new review ...
I have to admit that I'm gradually loosing interest in supporting a Conan recipe for my component.

Yeah, I didn't expect it would take this much time. I also wonder what's the process of adding new versions, once you have an existing conan package. Hopefully you don't have to wait months for each release.

Finally, the Conan package is available: sqlite3mc/1.8.0.

I also wonder what's the process of adding new versions, once you have an existing conan package.

Me too. I guess a PR has to be done to update the Conan recipe for each new version.

Hopefully you don't have to wait months for each release.

I really hope that adding new versions will be a smoother process.


chore(main): release 0.0.17

:robot: I have created a release beep boop
0.0.17 (2024-08-16)
Features

add support for connecting to Azure Government and Azure in China (#245) (965bbac)

Dependency Updates

deps: update golang docker tag to v1.23 (#241) (f9eb93c)
deps: update module github.com/validator-labs/validator to v0.1.5 (#238) (617869d)
deps: update module sigs.k8s.io/controller-runtime to v0.19.0 (#244) (cb04981)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.0.17
:sunflower:


indexer: remove unnecessary column index

kept checkpoint timestamp, b/c it is used in the network stats.


fix uuid high-risk vulnerability

Good job! @fengshunli Can you please reopen against dev?

https://github.com/armosec/kubescape/pull/407/ @dwertent completed

Merged #407 . Thank you :)


Add a delegate to support resources without a trailing slash

In https://github.com/Azure/azure-sdk-for-net/blob/psSdkJson6/src/SdkCommon/ClientRuntime.Azure.Authentication/ApplicationTokenProvider.cs, there are a few places we are calling settings.TokenAudience.ToString().
In case of Key Vault, the resource must be "https://vault.azure.net" without a trailing slash. This doesn't work with Key Vault since .ToString() always adds a trailing slash.

Hello, my apologies for this taking so long.  Is this still an issue?


ipred.rs: Replace C types with Rust equivalents

Closes #815

Why should we stick to C types in FFI? I think it'd be better to use the concrete Rust types rather than c_int and friends.

Why should we stick to C types in FFI? I think it'd be better to use the concrete Rust types rather than c_int and friends.

Because it's extern "C".  I think c_int is always i32, but others like c_long can be different, and I think it's better to be consistent with making the integer types in extern "C" fns use C types.

Because it's extern "C". I think c_int is always i32, but others like c_long can be different, and I think it's better to be consistent with making the integer types in extern "C" fns use C types.

I agree. A key reason why 32-bit builds were broken after transpiling for a 64-bit host was that c_ulong is
pub type c_ulong = u64;

for x86_64-unknown-linux-gnu but
pub type c_ulong = u32;

for i686-unknown-linux-gnu. I spent a lot of time getting that unbungled.

Ah okay noted. I'll close this for now then, I threw this together quickly because it was easy, going through and cleaning up C types within functions probably isn't worth the time right now.


Revise metrics definition

Revise metrics definition and added link to improving your model.
Fixes #11514
Internal Review URL

Thanks, @luisquintanilla!


Upgrade to Bootstrap 4 (from Bootstrap 3)

Performed a brief test of Portal CMS using Bootstrap 4, some work will be needed to upgrade components that are no longer supported or changed. Such as Tabs.


Create a generic deployment_platform param [WIP]

Generic platform parameter to override when using vagrant so we can track onprem and vagrant clusters deployed in our metrics.

CC @karlkfi

Replaced by https://github.com/dcos/dcos/pull/645


[typescript] Fix withStyles edge cases, require TS 2.8

Fixes #11109.
Fixes #11191.
This employs conditional types to define an Overwrite type operator which resolves the edge cases around withStyles, without destroying the integrity of props that are specified as a union. This means requiring a minimum TypeScript version of 2.8.

I took it around the block with all of my own code.  All looks good!
You might want to document Overwrite a bit; it takes some staring at it and examples to understand.  Something like:

Overwrite takes a type T and a "mixin" type U, removes any properties from T that would conflict with properties in U, and returns the combined type T&U.  When T extends U already, it just returns T.

It seems like the stakeholders from the issues that this resolves are all in favor of it, so I'll merge. We'll want to mention in the release notes that TypeScript 2.8 is required now.

@pelotom Oops, just after the release train 🚂.

@oliviertassinari 😩

The next one will be this weekend :)

@pelotom will this fix all the compile errors introduced around withStyle after beta.43? My code had a comfortable life before 43 :)

@semiadam with any luck 🙂

@semiadam you can import the following fix instead of material-ui/styles to get around the compile errors:
import withStylesOld from 'material-ui/styles/withStyles';

export * from 'material-ui/styles';

import { WithStyles, StyleRules, StyleRulesCallback, StyledComponentProps } from 'material-ui/styles';
import { WithStylesOptions } from 'material-ui/styles/withStyles';

type ConsistentWith<O> = Partial<O> & Record<string, any>;
declare function WithStylesFixed<ClassKey extends string>(
    style: StyleRules<ClassKey> | StyleRulesCallback<ClassKey>,
    options?: WithStylesOptions,
): {
    <P extends ConsistentWith<StyledComponentProps<ClassKey>>>
    (component: React.ComponentType<P & WithStyles<ClassKey>>): React.ComponentType<P & StyledComponentProps<ClassKey>>;
    (component: React.ComponentType<WithStyles<ClassKey>>): React.ComponentType<StyledComponentProps<ClassKey>>;
};

export const withStyles =  withStylesOld as typeof WithStylesFixed;

@olee Do you know of some problem with @pelotom's fix for this?  IIt might be more productive if folks tried that.  Flipping the overloads just causes problems in other cases.  If you want to see, try patching a copy of material-ui with your declaration, npm run typescript, and see what breaks.

@pelotom In your copious spare time, you might want to consider adding test cases for the issues that were posted due to my PR, either in this PR or another.

I did, in this PR... were there others that I missed?

@pelotom Sorry, no need for more AFAIK.  I looked for them in the diffs, don't understand how I missed them!


Turn off Data Dashboard in production [with update to latest DCA]

our update to https://github.com/Sage-Bionetworks/data_curator/releases/tag/v22.11.3 turns on the data dashboard.
I imagine this will result in quite a few questions from centers about data completeness. I have some already.
I would like to explore the possibility of hiding the data daashboard in production until there is appropriate documentation for centers and we can properly launch the feature at a steering committee.
I would like to remove ASAP and then target adding back in during the 23/01 sprint.

Dashboard causing a disconnect in #48

Confirming that we are going to revert per the PR above

[ ] Merged
[ ] Kicks off action that deploys this to staging
[ ] Action successful
[ ] Check that staging has removed the dashboard and seems to be functioning
[ ] Make a draft release tagged v22.11.2. Note that this reverts us to DCA v22.11.2
[ ] Wait for action to complete
[ ] Confirm production looks OK
[ ] PR to re-update to DCA v22.11.3
[ ] Merge
[ ] Confirm that this deploys in staging.

@adamjtaylor I can confirm that reverting to codebase in the main branch of the DCA upstream (i.e. v22.11.2) would get the bug fixes noted in v22.11.3; you'd only be missing the dashboard features and suppression of warning messages in the log. The steps above are good to go!

@milen-sage we just completed the actions above. I can confirm that production looks ok again.

@adamjtaylor and @elv-sb could you start gh issues for the bugs/features you'd like to see with the dashboard (aside from docs - we are planning on that work)? Thanks!

@milen-sage we can add those during our next sprint. Thank you!

Thanks @elv-sb! Meanwhile feel free to explore more of the dashboard in the testing HTAN instance. Once we finish the docs on how schema validation rules are reflected in the dashboard and how the dashboard results can be interpreted we can have a dashboard exploration/play meeting. But certainly agreed with you and @adamjtaylor that we don't want to scare centers, if they see a bunch of their metadata, clinical and biospecimen data are marked as invalid out of the blue.

Bring to next data with FAIR on 12/12

What is the plan at the end of this sprint?
Leave at DCA 22.11.2
Able to turn off data dashboard and use >=22.11.3
Manually merge in bug fixes from 22.11.2 but not take the DCA commit

Per discussion with Milen on 1/19 HTAN/FAIR stakeholder call:
Adam: Ability to toggle dashboard - is this being considered?
Milen: Approach will be to remove by default and make optional; only enable for projects that have gone through process of ramping up users/rolling this out - this will then be turned on. Next DCA release is expected to have this removed (targeted for 1/11; v23.1.1), so we can pull in latest release with other fixes

@adamjtaylor the dashboard has been disabled by default in the main branch of DCA and release v23.1.1.
One note: you'll need to incorporate the changes in shinyapps_deploy.yml . The step Save service account credentials for Schematic will properly convert the schematic service account credentials stored as a github secret to a json file. Moving forward, schematic will authenticate the google API using the service account credentials instead of the token.pickle file.

I'd like to be able to update our DCA to v23.1.1, but when I try and open a PR for this it won't allow me
https://github.com/ncihtan/HTAN-data-curator/compare/update-dca...Sage-Bionetworks:data_curator:v23.1.1

Following @milen-sage's comment in FAIR Data sprint review we should actually update to v23.1.2 (ie level with the head repo main branch) as the Google auth changes are included in the newest version.

Moving to ready for review as the DCA is off. Suggest we have a new issue for the cleanup and actually getting to the latest DCA version.

@adamjtaylor why is the DCA off? Based on discussion  with @afwillia and the jira issue, I had assumed the DCA was running w/ updated schematic code (v23.1.1) and DCA v22.11.x, which would have switched to updated Google auth mechanism, even if not using the latest DCA version. I was assuming @afwillia was syncing up with @adamjtaylor to update the DCA to v23.1.3 to move on to the latest version but that was not a blocker for DCA running, based on conversation with @afwillia.
Was my understanding incorrect?

@milen-sage Typo on my behalf. Data dashboard is currently off - not the DCA. Have updated comment.
Otherwise your understanding correct and we will need to sync up with @afwillia to get us fully up to v23.1.x
Sorry for the confusion!


Save evaluation output in correct location

The refactor in a0c60f1 introduced some errors that prevented post fitting evaluation from running properly.
This fixes those by:

Saving evaluation output in the correction location
Writing evaluation output separately from comet logging
Properly passing the comet logger to the evaluation code
Some other minor cleanup

Fixes #32
Fixes #33

LGTM


DbContextEntityTypesProvider isn't always exhaustive enough

It's fine for database-first contexts, where all the DbSet properties are auto-generated on the context. However in a lot of code-first contexts there may not be a property for each table.
The DbContextEntityTypesProvider should use the same mechanism as Entity Framework to decide which types it should treat as entities.

The Entity Framework mechanism is not currently exposed; it will be in v7 so this can be addressed then.


How to install Python Community Edition plugin into sandbox

Given
intellij {
    version "IC-2018.2"
    plugins = ["PythonCore:2<IP_ADDRESS>84.101"]
}

https://plugins.jetbrains.com/plugin/7322-python-community-edition/update/48089
will add python plugin to the classpath, but it is never in the sandbox.
When manually installing the Python CE plugin, it will add "python-ce" into the <sandbox>/config/plugins
How can I get it into the sandbox automatically? Edit: This is for 0.3.10

Nvm, my build system is approaching insanity :-/, works fine


Fix IIR filter breaking when NaN on edges of signal

issue #14

Hello @srcole, Thank you for submitting the Pull Request !

In the file neurodsp/filt.py, following are the PEP8 issues :

Line 114:31: E226 missing whitespace around arithmetic operator
Line 219:57: E226 missing whitespace around arithmetic operator
Line 219:89: E226 missing whitespace around arithmetic operator
Line 219:153: E226 missing whitespace around arithmetic operator
Line 219:179: E226 missing whitespace around arithmetic operator
Line 220:9: E722 do not use bare except'

Do see the Hitchhiker's guide to code style


Huggingface Transformers model compatibility?

Is there any way to directly load the ESM models with the HF Transformers (or similarly compatible) libraries? e.g. with AutoModelForTokenClassification?
Thanks!
(I want to do finetuning, and to use additional libraries that support the HF models' format).

Very happy to share that - thanks to the amazing work of @Rocketknight1 and team - this is now possible:

Classification tasks with proteins, just like BERT: https://colab.research.google.com/github/huggingface/notebooks/blob/main/examples/protein_language_modeling.ipynb
Fold proteins in Colab or your local GPU and export PDB files: https://colab.research.google.com/github/huggingface/notebooks/blob/main/examples/protein_folding.ipynb

Is that work? I found that it's difficult to load ESM1b_650M with half precision in a RTX3090


Update release-v1.0 to main

Update release-v1.0 with changes to main since v1.0.0-rc.2

Codecov Report

Merging #4417 (4fc92b1) into release-v1.0 (153e680) will increase coverage by 0.08%.
The diff coverage is 72.02%.

:exclamation: Current head 4fc92b1 differs from pull request most recent head 9316b33. Consider uploading reports for the commit 9316b33 to get more accurate results

@@               Coverage Diff                @@
##           release-v1.0    #4417      +/-   ##
================================================
+ Coverage         69.12%   69.21%   +0.08%
================================================
  Files               212      212
  Lines             14458    14580     +122
================================================
+ Hits               9994    10091      +97
- Misses             4412     4437      +25
  Partials             52       52

Flag
Coverage Δ

unittests
69.21% <72.02%> (+0.08%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apis/config/v1alpha1/zz_generated.deepcopy.go
0.00% <ø> (ø)

pkg/catalog/fake.go
33.33% <ø> (+0.18%)
:arrow_up:

pkg/k8s/mock_controller_generated.go
0.00% <ø> (ø)

pkg/k8s/types.go
100.00% <ø> (ø)

cmd/cli/support_bugreport.go
22.72% <12.50%> (-1.03%)
:arrow_down:

cmd/cli/version.go
44.57% <40.25%> (-13.76%)
:arrow_down:

pkg/providers/kube/client.go
72.22% <50.00%> (ø)

cmd/cli/namespace_add.go
83.63% <100.00%> (-0.53%)
:arrow_down:

cmd/cli/util.go
68.75% <100.00%> (+1.29%)
:arrow_up:

pkg/configurator/methods.go
73.38% <100.00%> (+2.85%)
:arrow_up:

... and 13 more

Continue to review full report at Codecov.

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


Debugger timed out issue while debugging Aurora

What are you experiencing an issue with?

[ ] Aurora
[ ] Aurora supported game, (Fill in the game)
[ ] Aurora Wrapper
[ ] Aurora Profile
[ ] Aurora supported device, (Fill in problematic devices)
[ ] Aurora Scripts
[ ] Aurora Updater
[ ] Aurora Lighting issue
[x] Other, (Debugging Aurora)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[ ] Visual bug
[ ] Localization issue
[ ] Enhancement suggestion
[ ] Device issue
[x] Other, (Debugger bug)

Have you experienced "debugger timed out" on starting Aurora from studio? It hangs immediately after start, then message with "debugging operation taking longer that it should" appears and finally error dialog "Evaluating the function timed out and needed to be aborted in an unsafe way.".
I've recently began to experience this issue. Firstly it was happening sometimes and now, after reboot and some windows updates, it reached 100% chance of happening so I was unable to continue debug something and begin to search for an origin of cause.
The problem is a bit complex and caused by that Main method of aurora calls to System.Diagnostics.Debug (in Logger) in parallel thread while initializing the app by var WinApp = new System.Windows.Application(); in main thread.
Is more like the problem of VS debugger than Aurora's architecture, so I've reported it to Microsoft. But nevertheless to continue working I had to resolve it. So If you are also experiencing it or will start experiencing it you will already know by what it caused.
Here is example of clear new project that causes this issue to appear.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace DebuggerTimeoutBugTest
{
	class Program
	{
		static Task Task = Task.Run(() =>
		{
			System.Diagnostics.Debug.WriteLine("");
		});

		static void Main(string[] args)
		{
			new System.Windows.Application();
		}
	}
}

The issue only appeared after I added the Mutex.WaitOne check to the Main method and when I'm debugging I just comment that out because if it is active I get the issue the entire time.

I believe the problem is not in mutex. Or maybe mutex also causes it, or just making it worse.
In dev branch I am using now, I can't see any mutex and the problem still exists. The sample project also has no kind of mutex and still causes problem.
Maybe it's just bad idea to do some initialization before/simultaneously with initializing main application.
Why not init everything in main form on load event for example?
I've solved the problem by commenting System.Diagnostics.Debug.WriteLine in logger for myself. But it took me a nice some hours while I've found the origin and what is going on.

In my testing, it hasn't even reached the point where it is creating a new instance of the Application by the time the debugger dies. I think the example you've got is another example of the issue and that Mutex could be in the same position as the Application in our case.

Having moved the instance creation for the Logger class to a method that is called straight after the call of Mutex.WaitOne I've yet to have the issue show again after starting the debugger multiple times. Anytime I got the issue before it always showed a thread at the Debug.WriteLine and the primary at the start of the Program.Main method. I'm pretty confident that our situation is caused by the Mutex but can also be caused by Application.


update github.com/ncw/swift package in vendor to avoid potential memo…

This PR is try to solve this issue. The purpose is to void potential memory leaks caused by the github.com/ncw/swift package.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "swift_vendor" git@github.com:mlmhl/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


chore: merge main into release

this also succeeds, so this morning's inability to make a PR with exactly the same title must have been transient.


Joeychrys/issue7

There are a few things that need to be added like Navbar Links and a Navbar Item but this can maybe act as a starting point.

I made this a draft so you guys can review everything first. Let me know if you need anything.

Hello @joeychrys,
Thanks for your contributions, the first thing I want to ask you is if you can remove this commit
from your branch because that looks to be coming from the work in progress branch of the Tabs components.

Hello @joeychrys,
Thanks for your contributions, the first thing I want to ask you is if you can remove this commit from your branch because that looks to be coming from the work in progress branch of the Tabs components.

Okay I reverted with git revert --strategy resolve 559b7e9. If I need to remove it with a different process, let me know.

Hello @joeychrys,
Thanks for your contributions, the first thing I want to ask you is if you can remove this commit from your branch because that looks to be coming from the work in progress branch of the Tabs components.

Okay I reverted with git revert --strategy resolve 559b7e9. If I need to remove it with a different process, let me know.

No that's will do it, thanks.

Just read through the reviews and I'll start working on them asap. P.S I think we're in different timezones so my responses might be delayed. (It's 4am here lol)

Just read through the reviews and I'll start working on them asap. P.S I think we're in different timezones so my responses might be delayed. (It's 4am here lol)

Great thanks. That's quite early haha take your time no worries 😀


Unselected objects get exported

Hi!
I am encountering a model exporting issue.
Describe the bug
I have a scene with one tree model and one animated horse model. I want to export only the tree model, so I select it only and upon export, I enable the "Selected Objects" option but it also exports an empty node for each bone of the horse.
To Reproduce
Steps to reproduce the behavior:

Open the attached file with blender 2.91.0
Select tree model and export it to gltf (with "glTF Separate" format and "Selected Objects" enabled)
Open the exported gltf file and you will notice it contains extra nodes with the name "Bone0XX" which belong to the horse rig.

Expected behavior
It should only export the selected tree model.
.blend file/ .gltf
model.zip
Version

OS: linux mint
Blender Version 2.91.0

Anyone can confirm this, please?

Anyone can confirm this, please?

This is #1298.

This is #1298.

Ok, thanks. For now, going to put them in separate blend files, until this bug is fixed.

Ok, thanks. For now, going to put them in separate blend files, until this bug is fixed.

Merged


bump version of conbench CLI

This PR bumps the version of the conbench CLI to account for small bugfixes including https://github.com/conbench/conbench/pull/1048.

I wonder if we need the version pin at all, honestly

We recently added a pin in https://github.com/voltrondata-labs/arrow-benchmarks-ci/pull/96, because we accidentally broke the CLI in conbench/conbench with 3.9-style type hints. IMO that was mainly because we don't test against old versions of python (see https://github.com/conbench/conbench/issues/618) and pinning was a quick way to stop that kind of thing from happening again.


The game board should display the current data structure in the center, so that I can see a visual representation of what I need to accomplish.

The main element of the gameboard is the data structure that the user is playing with. It will be prominently displayed in the center of the screen, and users will see how various actions affect the state of the data structure.

Moving this back to backlog since @ryancb4 is doing different developer stories now; therefore, no current developer stories reference this user story.


Issue with k8s.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
pods/storage/pv-pod.yaml has an extra indent under ports for containerport.
Proposed Solution:
i think - containerPort: 80 should start just below ports.
Page to Update:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/

I think indentation is correct here.
I check this on yaml checker as well and it is correct.
Have you faced any issue while creating pods using this yaml file?

I think u can close this.
Thanks,
Roy
On Thu, Feb 14, 2019, 3:17 AM Neha Yadav<EMAIL_ADDRESS>wrote:

I think indentation is correct here.
I check this on yaml checker as well and it is correct.
Have you faced any issue while creating pods using this yaml file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/12556#issuecomment-463534106,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUQ4Celu6sAcgK1woeIuh5NNSOL1X_9gks5vNRt7gaJpZM4ax0gr
.

/close

@Rajakavitha1 can you please close this issue

Thanks for your update @imaneha
/close

/close


ValueError: not enough values to unpack reported when running MNIST example

Describe the bug
Hi,
I encountered a ValueError: not enough values to unpack when running the provided examples as instruction told, error details shown as following:
stack trace:
Traceback (most recent call last):
  File "Add/add.py", line 4, in <module>
    from deepproblog.engines import ExactEngine
  File "/Users/mac/Documents/Academic/projects/dissertation/deepproblog/src/deepproblog/engines/__init__.py", line 1, in <module>
    from deepproblog.engines.approximate_engine import ApproximateEngine
  File "/Users/mac/Documents/Academic/projects/dissertation/deepproblog/src/deepproblog/engines/approximate_engine.py", line 2, in <module>
    from deepproblog.engines.prolog_engine import (
  File "/Users/mac/Documents/Academic/projects/dissertation/deepproblog/src/deepproblog/engines/prolog_engine/__init__.py", line 1, in <module>
    from .engine import PrologEngine
  File "/Users/mac/Documents/Academic/projects/dissertation/deepproblog/src/deepproblog/engines/prolog_engine/engine.py", line 4, in <module>
    from pyswip import Prolog
  File "/usr/local/anaconda3/lib/python3.8/site-packages/pyswip/__init__.py", line 29, in <module>
    from pyswip.prolog import Prolog
  File "/usr/local/anaconda3/lib/python3.8/site-packages/pyswip/prolog.py", line 28, in <module>
    from pyswip.core import *
  File "/usr/local/anaconda3/lib/python3.8/site-packages/pyswip/core.py", line 567, in <module>
    (_path, SWI_HOME_DIR) = _findSwipl()
  File "/usr/local/anaconda3/lib/python3.8/site-packages/pyswip/core.py", line 416, in _findSwipl
    (path, swiHome) = _findSwiplDar()
  File "/usr/local/anaconda3/lib/python3.8/site-packages/pyswip/core.py", line 370, in _findSwiplDar
    (path, swiHome) = _findSwiplFromExec()
  File "/usr/local/anaconda3/lib/python3.8/site-packages/pyswip/core.py", line 93, in _findSwiplFromExec
    rtvars = dict((name, value[1:-1]) for name, value in ret) # [1:-1] gets
  File "/usr/local/anaconda3/lib/python3.8/site-packages/pyswip/core.py", line 93, in <genexpr>
    rtvars = dict((name, value[1:-1]) for name, value in ret) # [1:-1] gets
ValueError: not enough values to unpack (expected 2, got 1)

To Reproduce
Steps to reproduce the behavior:

cd ~/deepproblog/src/
export PYTHONPATH=`pwd`
python3 deepproblog/examples/MNIST/addition.py

Desktop (please complete the following information):

OS: macOS 11.4
Python Version: 3.8
problog                            <IP_ADDRESS>
PySDD                              0.2.10
pyswip                             0.2.10
torch                              1.8.0
torchvision                        0.9.0

Please help, thank you !

Hi mexicer. From your stack trace, this seems like a bug in pyswip instead. It seems to me like the same issue as this one: https://github.com/yuce/pyswip/issues/76
Good luck.

Hi mexicer. From your stack trace, this seems like a bug in pyswip instead. It seems to me like the same issue as this one: yuce/pyswip#76
Good luck.

I guess this could be a problem of OS, I'll try to run it on Linux, thanks !


[Feature Request] Make translators "inline" property configurable

Right now, inline anchors/links are placed on a new line.
HTML:

Markdown:

What I am requesting is to add the ability to make anchors remain inline, as putting them on new line can make the final markdown unnecessarily messy and bulky, especially when the inputted HTML is only a few words/one sentence.

Fixed - please upgrade to V1.1.2


specify serve.config.js file location

Operating System:
Node Version:
NPM Version:
webpack Version:
webpack-serve Version: 1.0.4

This issue is for a:

[ ] bug
[x] feature request
[ ] modification request

New Feature Use Case

  $ webpack-serve --serve-config .tool/serve.config.js

I want to put "serve.config.js" in the "tool" directory

Sad panda 🐼 😢  You removed portions of the issue template, so we have to close your issue as invalid. Please don't ignore Issue or Pull Request template sections. They're in the template because they're useful to the maintainers of this project.


Reranking

Need to implement a general approach to reranking. This is one of the main limitations in the current typechecker.

The new typechecker does not have this problem.


Update broken links affected by branch renaming

What issue does this PR address?
Update broken links in docs, quickstarts, readme and other files affected by renaming 'master' branch to 'main'.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[ ] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

 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.:x: btshft sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

wow. thanks a lot. I totally didn't see that coming ;)


Duplicate description on customization

the description for customizing self-hosted runners was listed twice

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@zmoazeni

#278
Duplicate of #

@AdamTheCreator
Thanks so much for opening a PR! I'll get this triaged for review :zap:

👋 @AdamTheCreator, thanks for this PR. There are actually two different paragraphs there, and one should show when Mac tab is selected at the top of the page, and the other should show when Linux is selected.
It looks like there might be a bug where the OS tab not selected when loading the page. I'm going to close this issue and open an internal one for our engineering team to fix.


Method BaseComparer/AddComparerOverride does not not override

Because the internal method ComparerOverridesCollection/AddCompare throws an exception
        public void AddComparer(MemberInfo memberInfo, IValueComparer valueComparer
        {
            if (memberInfo == null)
            {
                throw new ArgumentNullException(nameof(memberInfo));
            }

            //if (_overridesByMember.ContainsKey(memberInfo))
            //{
            //    throw new ValueComparerExistsException(memberInfo);
            //}

            _overridesByMember[memberInfo] = valueComparer ?? throw new ArgumentNullException(nameof(valueComparer));
        }

@Upper-Link, can you please provide your code?
It throws exception if member has already been overwritten.


Fix build failure for clang

This fixes a build failure with clang.
[ 78%] Building CXX object CMakeFiles/vcpkg-test.dir/src/vcpkg-test/mockcmakevarsprovider.cpp.o
In file included from /home/pi/repos/vcpkg-tool/src/vcpkg-test/mockcmakevarsprovider.cpp:1:
In file included from /home/pi/repos/vcpkg-tool/include/vcpkg-test/mockcmakevarprovider.h:3:
In file included from /home/pi/repos/vcpkg-tool/include/vcpkg/cmakevars.h:10:
In file included from /home/pi/repos/vcpkg-tool/include/vcpkg/packagespec.h:3:
/home/pi/repos/vcpkg-tool/include/vcpkg/base/expected.h:208:29: error: no member named 'invoke' in namespace 'std'; did you mean '__invoke'?
                return std::invoke(f, *m_t.get(), static_cast<Args&&>(args)...);
                       ~~~~~^~~~~~
                            __invoke
/usr/bin/../lib/gcc/arm-linux-gnueabihf/8/../../../../include/c++/8/bits/invoke.h:89:5: note: '__invoke' declared here
    __invoke(_Callable&& __fn, _Args&&... __args)
    ^
In file included from /home/pi/repos/vcpkg-tool/src/vcpkg-test/mockcmakevarsprovider.cpp:1:
In file included from /home/pi/repos/vcpkg-tool/include/vcpkg-test/mockcmakevarprovider.h:3:
In file included from /home/pi/repos/vcpkg-tool/include/vcpkg/cmakevars.h:10:
In file included from /home/pi/repos/vcpkg-tool/include/vcpkg/packagespec.h:3:
/home/pi/repos/vcpkg-tool/include/vcpkg/base/expected.h:221:29: error: no member named 'invoke' in namespace 'std'; did you mean '__invoke'?
                return std::invoke(f, std::move(*m_t.get()), static_cast<Args&&>(args)...);
                       ~~~~~^~~~~~
                            __invoke
/usr/bin/../lib/gcc/arm-linux-gnueabihf/8/../../../../include/c++/8/bits/invoke.h:89:5: note: '__invoke' declared here
    __invoke(_Callable&& __fn, _Args&&... __args)
    ^

std::invoke needs header <functional> to be included.

Thanks for the fix!


opening a new window with the calculator in it

Make a new menu entry in the gradido wallet - opening a new Window with the calculator in it
calculator: https://github.com/gradido/DankBar-converter

https://gradido.net/de/gradido-zu-dankbar-umrechner/


Improve coverage

Especially on https://github.com/numberly/flask-graphite/commit/dd1683409c8143aa81dbf087c6e7eef3514136be :100:

:chicken:


change getOneFulfilledExpectationWithIgnoredParameters to right name

change getOneFulfilledExpectationWithIgnoredParameters to right name which compliant with it's behavior

@basvodde what's your opinion? This name even perplex me when I read those code parts, because it do not describe correctly what it does.

OK maybe I do not describe clearly.
the detail is, there is a discrepancy between this function MockExpectedCallsList::getOneFulfilledExpectationWithIgnoredParameters's behavior and it's name.
MockCheckedExpectedCall* MockExpectedCallsList::getOneFulfilledExpectationWithIgnoredParameters()
{
    for (MockExpectedCallsListNode* p = head_; p; p = p->next_) {
        if (p->expectedCall_->isFulfilledWithoutIgnoredParameters()) {
            return p->expectedCall_;
        }
    }
    return NULL;
}

this function should own it's fit name. @basvodde do you think it should be fixed or just omitted?

Personally, I think it should be changed. I hate stuff with names that suggest it does something else than what it actually does. Same is misleading comments ;-)

so?

I'll check it later, I didn't check it in detail yet, sorry!

@basvodde did you get time to check this PR? :)

Hey, can you open it again? Why close it?


Is the doc site ready to be published?

Aside from a logo, the two major milestones (a persistent header, #6, and searching, #2) have been implemented into the site.
Is there anything else that needs to be added before this can be published?
Docs: http://hargasinski.github.io/async/docs.html
/cc @megawac @aearly

Make a pull request :) (please exclude the docs/ folder)
On Tue, Jun 28, 2016 at 3:21 AM, Hubert Argasinski<EMAIL_ADDRESS>
wrote:

Aside from a logo, the two major milestones (a persistent header, #6
https://github.com/hargasinski/async/issues/6, and searching, #2
https://github.com/hargasinski/async/issues/2) have been implemented
into the site.
Is there anything else that needs to be added before this can be published?
Docs: http://hargasinski.github.io/async/docs.html
/cc @megawac https://github.com/megawac @aearly
https://github.com/aearly
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hargasinski/async/issues/10, or mute the thread
https://github.com/notifications/unsubscribe/ADUIEBmrfj85gFLhmAKGYzpAdNhuCRVyks5qQMuEgaJpZM4I_z-x
.

Also search isn't working on the site as it links to the wrong page (it loses track of route).

Good thing you noticed that, I tested it locally, so that wasn't a problem. I'll fix that and open the pull request tonight.

Sounds good, mind also squashing both of our commits into relevant parts before submitting the PR. Just remove the tweak commits and the ones for rebuilding docs. I'd say 10-20 commits is reasonable for this

Thanks for all your hard work @hargasinski .  Anything else you'd like to finish before the final PR?  After the PR, any other tweaks you want to make will have to go through PRs to the upstream project.

I'm glad to help out. I use async a lot, so I'm glad to finally have a docs site for it. I think everything's good for the PR now, I'll just need to fix the issue @megawac pointed out. Idk if I'll be able to address your comments in #4 without delaying this significantly. Adding the minami theme to the repo will be easy, but it might be difficult to do everything the jsdoc-fix-html.js script is doing without spending a lot of time modifying the theme. I could slowly work on that in the next couple weeks.

I have a feeling jsdoc-fix-html.js will stick around for the things we can't accomplish through the template or plugins, totally fine.

There might be small things that are pointed out when the site goes live, but it should't anything too major. It should be easy to apply those fixes through a PR.

Oh okay, so yeah, I'll just apply the fix tonight, squash the commits so that they are more relevant, and open the PR.

Yeah, it's 95% of the way there, it's all small tweaks from here on out. :smile: :100:

@hargasinski I think I fixed that issue earlier (didn't test much though as I was busy with other things) if you get a second can you confirm that https://github.com/hargasinski/async/commit/becd6835b5378d62b3fee896648b9a8f10f8ec64 fixes it

@megawac sorry, I didn't realize you fixed it. I can't test it now, but from the looks of it, it should work. I'll quickly test it again tonight before squashing the commits. Thanks for that!

Yeah I forgot to ping this issue when fixing it, my b
On Jun 28, 2016 5:28 PM, "Hubert Argasinski"<EMAIL_ADDRESS>wrote:

@megawac https://github.com/megawac sorry, I didn't realize you fixed
it. I can't test it now, but from the looks of it, it should work. I'll
quickly test it again tonight before squashing the commits. Thanks for that!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hargasinski/async/issues/10#issuecomment-229189629,
or mute the thread
https://github.com/notifications/unsubscribe/ADUIEMRD4SwmKzt5qUR5pwRZzaIVbpeRks5qQZIYgaJpZM4I_z-x
.

I just opened the pull request :smile:. @megawac I branched off of docs-jsdocs to docs-pr for the PR, just in case I messed something up while squashing the commits. It ended up being 18 after everything. I had to just fix one line (66a6b67), but besides that your fix worked perfectly. Thank you!


Solution Dev - Mapping

Mapping has been completed.  Of course, they may be some changes during testing.  The link to the mapping file is https://docs.google.com/spreadsheets/d/1SzB8MxeVOYDjBECfHR82525KD40pIPjh/edit#gid=951091919


Update paella-core

Updates paella-core to 1.49.4 to fix floating/scrolling pop-up menus.

There is still something very wrong: when scrolling down before opening the menu, it appears too high. I would suspect that this needs to be fixed in Paella. So unless that's fixed, I don't think merging this is really worth it? (As an aside: the Paella changelog does not includes these latest releases, so I have little idea what else changed...)

Given that we are waiting for https://github.com/polimediaupv/paella-core/issues/368 and #1223 updated it to the latest version without the new bug, I think this PR can be closed for now.


No up-to-date versions on registry.connect.redhat.com?

The latest tag showing at the Redhat registry is 2.4.0.  The search results show last update as 7 days ago - I wonder if tagging is broken?

There is a fix PR in #499

Hi @sfhardman,
Thanks for bringing this to our attention. We will investigate and report back soon.
Cheers!

Any update on this please? The latest release available on RH containers is 2.5.1

Hi @sfhardman we will look into this. Thanks for reporting!

https://catalog.redhat.com/software/containers/5bd44e6269aea375267725e2?architecture=amd64&tag=2.8.1


cleanSchemaMap contained incorrect logic

cleanSchemaMap contained incorrect logic, which caused some wierd issues when using dependencies inside arrays (and possibly deeper nested structures)

Thanks @madsmtm!


Can the "TypeConverter" support data of type "Future"?

Like this：
import 'dart:typed_data';
import 'dart:ui' as ui;
import 'package:floor/floor.dart';

class ImageTypeConverter extends TypeConverter<ui.Image?, Uint8List?> {
  // Return a 'Future'
  @override
  Future<ui.Image?> decode(Uint8List? databaseValue) async {
    if (databaseValue == null) return null;

    final codec = await ui.instantiateImageCodec(databaseValue);
    final image = (await codec.getNextFrame()).image;

    codec.dispose();

    return image;
  }

  // Return a 'Future'
  @override
  Future<Uint8List?> encode(ui.Image? value) async {
    if (value == null) return null;

    final data = await value.toByteData();

    return data?.buffer.asUint8List();
  }
}

I really need this feature.

I encountered with this issue too 😔

This feature request is also in line with support for generic type converters. I created one as below but it failed to match any of the data.
Generic Type Converter
If this feature can be provided it would be a great help

I think allowing Futures to be used could potentially allow people to use long running operations, which IMO does not belong in a type converter.
Just my thought.


The readme mentions "Go 1.11+" for Go version.

The readme mentions "Go 1.11+" for Go version.
Which version of Go is the minimum version?
Which version of Go is the maximum version?
To avoid another issue in this single repo for a simple, short question.
Which version of make is the minimum version?
Which version of make is the maximum version?

Reference
1 https://github.com/github/hub/issues/2616
2 Too much spam about create a new issue in some repos on Github. Maybe even in https://github.com/github. Please fix. 🙏
thanks ret394

And thanks for not being careless enough to disable blank, no template issues. Appreciate the huge favour.
Another issue to fix if it's in https://github.com/github. I mean the repos as in repositories.
This comment is verbose due to Github's extremely competent support staff.
hiding as it's simpler to read. Just click show.

Which version of Go is the minimum version?

It's Go 1.11+, like our documentation mentions.

Which version of Go is the maximum version?

There is no maximum Go version. Until today, there was a bug that prevents compiling with Go 1.15, but that was accidental and it's fixed now in the main branch.

Which version of make is the minimum version?
Which version of make is the maximum version?

I don't know which versions of make are compatible, but in my experience, any GNU make will do.
Closing since I hope your questions have been answered! 🙇

If response is too bad, stop

mislav's site

Follow my hot takes and pretty pictures

hot takes? bruh! you jus parrot stuff and try to fit in. To avoid being hunted by your peers. Don't you?
I used to be scared to death too. But, like, being scared is overrated.