Page store does not changing on history back

Describe the bug
Page store does not trigger change when navigate to hash url and use history back. In presented code fragment on each hash change needs to be 2 logs ($page object and HashChangeEvent), but sometimes logs only one record with event and store stays unchaged.
Reproduction

<svelte:window on:hashchange={console.log}/>

<button on:click={() => history.back()}>back</button>
hash

Logs
No response
System Info
System:
    OS: Linux 5.10 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    Memory: 10.99 GB / 12.44 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    npm: 8.5.4 - ~/.nvm/versions/node/v16.14.0/bin/npm
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.31
    @sveltejs/adapter-node: ^1.0.0-next.73 => 1.0.0-next.73
    @sveltejs/kit: next => 1.0.0-next.295
    svelte: ^3.46.0 => 3.46.4

Severity
serious, but I can work around it
Additional Information
No response

Confirmed. I did some console.log debugging and found something interesting. If you add another link to the page: no hash then the behavior changes quite a bit.
Scenario 1

Load page
Click on "hash" link, going to http://localhost:3000/#hash

$page store subscription fires, logging http://localhost:3000/#hash

Click on "back" button inside page, returning to http://localhost:3000/

$page store subscription does not fire

This is the same as the scenario that OP mentioned.
Scenario 2

Load page

$page store subscription fires, logging http://localhost:3000/

Click on "no hash" link (going to http://localhost:3000/ which is current URL)

$page store subscription does not fire

Click on "hash" link, going to http://localhost:3000/#hash

$page store subscription fires, logging http://localhost:3000/#hash

Click on "back" button inside page, returning to http://localhost:3000/

$page store subscription does not fire

Same behavior as scenario 1: clicking the "no hash" link while on that URL had no effect.
Scenario 3

Load page

$page store subscription fires, logging http://localhost:3000/

Click on "hash" link

$page store subscription fires, logging http://localhost:3000/#hash

Click on "no hash" link (going to http://localhost:3000/ which is NOT the current URL)

$page store subscription does not fire

Click on "back" button inside page, returning to http://localhost:3000/#hash

$page store subscription fires, logging http://localhost:3000/#hash

Click on "back" button inside page, returning to http://localhost:3000/

$page store subscription fires(!), logging http://localhost:3000/

This behavior is different from scenarios 1 and 2. By clicking on an  link that went from /#hash to /, we have changed when the bug occurs. Instead of occurring on clicking the "back" button, it occurs on clicking the "no hash" link.
So is history.back() really the cause of the issue? Or does it always fire on the next navigation after clicking a link with a hash? I'll need to do more debugging, and I'm out of time to do so today, but that's suspicious.

Possibly related https://github.com/sveltejs/kit/pull/3975#issuecomment-1043108318

I made some research and can say that your predictions are right - history.back() is not a reason of the issue.
It happens due to #3177.
The reason is the changing of field Client.current that holds current url, but #3177 preventing router navigation and Client.current leaves unchanged. When you click on the same link that before hash change this causes an issue.
history.back() history.forward() always trigger router navigation and breaks on first click on hashlink but restore after few actions (back, forward)

@Rich-Harris can you take a look?

This is somewhat related to #2673
I wanted to update the URL without fetching the page route again, as described in #2673 . As a temporary workaround, I tried changing the hash fragment instead. I ran into the same problem as described here. As mentioned above, the internal current state of the client is not updated properly. Additionally, I think the url property of stores.page would need to be updated internally.
So I think if there was a way to update the internal url of the client without triggering navigation, it can serve as a solution to both these issues.

No longer reproducible.


DBZ-363 Add support for BIGINT UNSIGNED handling for MySQL as a long

By default it BIGINT UNSIGNED will continue to be handled as a byte[]

@jpechane Any ideas why my Postgres integration tests are failing?  I barely made any changes to the Postgres code.

LGTM
@vultron81 Thanks!

@jpechane Any idea when this PR will get merged and released in 0.6.1?

@vultron81 @gunnarmorling is on JavaOne this week. We are going to decide relase date (and version) next week after his return.

Looks great, going to merge it. thanks a lot, @vultron81! Would you mind also sending a PR against the website repo for adding the new option to the list of connector properties: https://github.com/debezium/debezium.github.io/blob/develop/docs/connectors/mysql.asciidoc#connector-properties
Thanks!

Rebased, squashed everything into one commit and applied. Thanks again, @vultron81!

Done.

Ben

On Wed, Oct 18, 2017 at 2:33 AM, Gunnar Morling<EMAIL_ADDRESS>wrote:

Looks great, going to merge it. thanks a lot, @vultron81
https://github.com/vultron81! Would you mind also sending a PR against
the website repo for adding the new option to the list of connector
properties: https://github.com/debezium/debezium.github.io/blob/
develop/docs/connectors/mysql.asciidoc#connector-properties
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium/pull/294#issuecomment-337504059,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfDDFVfuicbreClS_eKXcaJ46FR9oJAks5stbf0gaJpZM4Pn2pq
.


Check if email is settled for GDPR export and delete

Updated version of this PR

Hello,
One addition to this function: it only check if email is in the guests newsletter table. For registered users no subscription is checked:
$sql = 'SELECT * FROM ' . DB_PREFIX . "emailsubscription WHERE email = '" . pSQL($customer['email']) . "'";
When a customer suscribes newsletter as a guest, the email address inserts in table "emailsubscription" but when is a registered customer this table is not used, because the info from customers table is used.
This function should use same logic as this (sorry, I'm not a developer and can't put more accurate example):
public function isNewsletterRegistered($customer_email)
{
    $sql = 'SELECT `email`
            FROM ' . _DB_PREFIX_ . 'emailsubscription
            WHERE `email` = \'' . pSQL($customer_email) . '\'
            AND id_shop = ' . $this->context->shop->id;

    if (Db::getInstance()->getRow($sql)) {
        return self::GUEST_REGISTERED;
    }

    $sql = 'SELECT `newsletter`
            FROM ' . _DB_PREFIX_ . 'customer
            WHERE `email` = \'' . pSQL($customer_email) . '\'
            AND id_shop = ' . $this->context->shop->id;

    if (!$registered = Db::getInstance()->getRow($sql)) {
        return self::GUEST_NOT_REGISTERED;
    }

    if ($registered['newsletter'] == '1') {
        return self::CUSTOMER_REGISTERED;
    }

    return self::CUSTOMER_NOT_REGISTERED;

Ping @clementdaubeuf

Hello, it seems this PR was not updated since 1 year.
I close this PR, following our review guidelines "Pull Requests may be closed after 30 days of inactivity". If however you are still interested in it, please ping us :) we can reopen.
Thank you for this contribution


GenProto: drop conditional Copyable reqs from protocol conformance descriptors

TODO:

[x] add a test

resolves rdar://124171788

@swift-ci smoke test

@swift-ci please smoke test Windows


Normalize windows paths

Pull Request Description

Fix #9619

Fix issue causing the full path to be shown on Windows.

Additional changes:

Add npm run watch:windows script to lib/client for developing on Electron.

Important Notes
Testing instructions:

Should ideally be tested on Windows. All the following should work:

Creating, opening and deleting top-level projects
Creating folders
Creating, opening and deleting nested projects
Uploading and deleting top level and nested files
Moving folders, files and projects

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

pinging @jdunkerley to verify whether this fixes the issue


129 edge detection

Initial dodal/ophyd device for pin-tip detection on I23.
Notes:

The edge detection code in edge_detect_utils.py is a refactored version of /dls_sw/prod/R<IP_ADDRESS>/support/adPython/2-1-11/adPythonApp/scripts/adPythonMxSampleDetect.py. Main changes:

Py3 compatibility
Use numpy for array operations (for efficiency)
Add unit tests
Various changes to make the API "nicer"

Using ophyd V2 as I'm using PVA to pull the array data.

Needs https://github.com/Tom-Willemsen/ophyd/tree/ntndarray to be used for initial support of NTNDArray EPICS PVA datatype, and a minor patch of timestamp -> timeStamp (the latter being the EPICS standard).
Once we've agreed this is roughly the approach we want to use I'll create the relevant PR onto ophyd.
Note that due to the absence of PVA gateways currently, if you want to test this you must do it on a beamline workstation. I've been using i02-2 as their camera is switched on.
I'm thinking of pulling out the creation of the new ophyd V2 device into a separate ticket, we need to use the DeviceCollector v2 interface but I think this is a big enough chunk of work to benefit from it's own ticket (and this should be independently reviewable).

Draft at the moment (due to necessary ophyd PR not done yet), but would appreciate any feedback on the approach so far.


Narrator blue box does not follow keyboard when tabbing through example page on Gallery Fabric

Part of the accessibility testing plan is the following step:

Narrator: Turn on Narrator (Win + Ctrl + Enter), set default verbosity levels (Settings > Accessibility > Narrator >Verbosity Level = "3 - All control details", Context level for buttons and controls = "2 - Immediate context")

Share your computer sound on the teams call (Find the presentation banner at the top of your screen & click the button that has the screen and sound icon)
Use tab and arrows to navigate through the page
Pretend you're in a coding interview - tell the reviewer what keys you're hitting as you press them
Listen to what narrator speaks
Does it make sense?
Any weirdness or differences between the visible text and text spoken?
To stop Narrator speaking, press Ctrl, to turn off narrator, press Win + Ctrl + Enter.

When enabling narrator on the example page, the blue box appears around the first component that has keyboard focus, and narrator announces information about the component. However, once the user tabs onto the next component on the page, the blue box does not follow, and Narrator stops speaking.
Example recording:
https://github.com/user-attachments/assets/caa34664-0b36-4849-9f8d-f25b40aa1354

This might be a missing event about focus changing that we're not passing to UIA. @chrisglein can you transfer this to the RNW repo?


sklearn vs xgboost inconsistency in prediction probabilities

System setup
OS: Mac OS X 10.13.6
xgboost version: 0.82
scikit-learn version: 0.20.2
numpy version: 1.16.1
Problem
When I try to train a model using some sample data I notice that while both models are able to learn the data, the xgboost model is not able to do so as confidently judging from the prediction probabilities.
Code
import xgboost as xgb
from sklearn.ensemble import GradientBoostingClassifier
import numpy as np

XGB_PARAM = {
    "learning_rate": 0.1,
    "n_estimators": 100,
    "objective": "binary:logistic",
    "verbosity": 1,
    "booster": "gbtree",
    "max_depth": 3,
    "lambda": 0,
}

features = np.load('features.npy')
labels = np.load('labels.npy')

def run_classifier(mode='xgb'):
	if mode == 'xgb':
		model = xgb.XGBClassifier(**XGB_PARAM)
	else:
		model = GradientBoostingClassifier()

	model.fit(features, labels)
	print('{} probabilities: '.format(mode), model.predict_proba(features))

run_classifier('xgb')
run_classifier('sklearn')

Results
When I run the above code I get the following result
xgb probabilities:  [[0.33988953 0.6601105 ]
 [0.80120075 0.19879927]
 [0.84622085 0.15377913]
 [0.34065586 0.65934414]
 [0.8017439  0.19825609]
 [0.8017439  0.19825609]
 [0.80120075 0.19879927]
 [0.80120075 0.19879927]
 [0.33988953 0.6601105 ]
 [0.8453405  0.15465954]
 [0.8017439  0.19825609]
 [0.34065586 0.65934414]]

sklearn probabilities:  [[4.32596905e-04 9.99567403e-01]
 [9.99783238e-01 2.16761787e-04]
 [9.99783238e-01 2.16761787e-04]
 [4.32596905e-04 9.99567403e-01]
 [9.99783238e-01 2.16761787e-04]
 [9.99783238e-01 2.16761787e-04]
 [9.99783238e-01 2.16761787e-04]
 [9.99783238e-01 2.16761787e-04]
 [4.32596905e-04 9.99567403e-01]
 [9.99783238e-01 2.16761787e-04]
 [9.99783238e-01 2.16761787e-04]
 [4.32596905e-04 9.99567403e-01]]

As can be seen above, although both models have the same class predictions the sklearn model is clearly more confident. I tried to make the xgboost params match the sklearn default params as closely as possible (and turning off the lambda regularization in xgb) and I still get this big mis match. Any help would be appreciated, thanks.

features_labels.zip
The features.npy and labels.npy files are attached in the zip file

@humzaiqbal GradientBoostingClassifier and XGBoost are different algorithms, so there is no good reason to expect them to behave identically. In particular,

Scikit-learn uses first-order gradient, whereas XGBoost uses second-order.
Scikit-learn uses Gini or Information Gain as split criteria, whereas XGBoost uses the loss reduction as split criteria.

@humzaiqbal You can see the algorithmic details of XGBoost in my master's thesis: https://drive.google.com/file/d/0B0c0MbnP6Nn-eUNRRkVOOGpkbFk/view?usp=sharing

@hcho3 @humzaiqbal Actually I ran some experiments out of curiosity.  I just generated some random normal data, when the data has only 12 rows, the difference is similar to above listed result.  But if you try to increase the number of rows to 120, the difference will become much smaller.


Not compatible with<EMAIL_ADDRESS>

Good library but it needs an update

Thank you for the kind review!
Unfortunately, I'm not maintaining this library anymore, but feel free to fork the project and make changes on your own.


Change artifact download action

Same issue as here. I accidentally copied over the faulty workflow.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 33.29%. Comparing base (37a2d92) to head (24258aa).
Report is 18 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #148      +/-   ##
==========================================
- Coverage   33.40%   33.29%   -0.11%
==========================================
  Files          68       69       +1
  Lines        3739     3835      +96
==========================================
+ Hits         1249     1277      +28
- Misses       2490     2558      +68

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


set selectTextStyle propType to Text.propTypes.style

https://github.com/peacechen/react-native-modal-selector/issues/25

Sure, Maybe this could be done under a different issue ticket tho.

If it's not too much trouble, would you mind updating all the style props with PropTypes.oneOfType ?  I won't be able to get to it right now and it'll likely fall through the cracks with my bad memory :D

I have tried to investigate prop types for arrays in style-properties, but it seems that this is somehow included in Text.propTypes.style (and other prop types for styles from RN). There is no warning in debug-mode when using arrays without explicit specifying it.
In Text from RN all properties goes trough a function which flattens any array present. So as far as I can see Text.propTypes.style accepts both objects and arrays with objects. ViewPropTypes uses the same function.
Other well maintained react-native modules seem to just use Text.propTypes.style, and not PropTypes.oneOfType to include array, e.g. react-native-elements Search inputStyle.
So I think this PR is good to go, and no further editing is necessary.

Thanks @mikaello for clarifying the style proptypes behavior.  Wasn't aware that arrays are automatically flattened first.


MIC Record

Hi, can you figure out how to record audio?
./arecord get this error

./arecord: line 1: can't create }dataq: Invalid argument
./arecord: line 1: RIFFWAVEfmt: not found

Related to the GPIO part, using strace on the various binaries does not "appear" to have any ioctl.
When I send the command BY THE ANDOIRD APP, this log appears:
p2p_tnp.c(myDoIOCtrl-5298)[16:49:10.279]:myDoIOCtrl(..): 0, IOTYPE_USER_IPCAM_AUDIOSTOP
p2p_tnp.c(myDoIOCtrl-5292)[16:49:10.768]:myDoIOCtrl(..): 0, IOTYPE_USER_IPCAM_AUDIOSTART
But no call to ioctl ...
ref:

Maybe p2p_tnp doesn't execute directly ioctl.
Probably it sends a socket command to another process.

Yes, I think that's it too


Testing Locally

In an attempt to debug a problem I'm having using Swift Klib, and upload a pull request to fix it, I'd like to test the plugin locally. Do you have a procedure to do that ?

@hartbit any time you would like to test some changes to any plugin locally, you can call
./gradlew publishToMavenLocal and then use mavenLocal() repository in your project to test your changes locally.

Closing this issue for now. Feel free to reopen if you will have any other questions.


Handle Version Negotiation packets

From Handling Version Negotiation Packets in draft-ietf-quic-transport-32:

A client that supports only this version of QUIC MUST abandon the
current connection attempt if it receives a Version Negotiation
packet, with the following two exceptions.  A client MUST discard any
Version Negotiation packet if it has received and successfully
processed any other packet, including an earlier Version Negotiation
packet.  A client MUST discard a Version Negotiation packet that
lists the QUIC version selected by the client.

Addition protection from downgrade attacks should be implemented once multiple versions are supported: https://datatracker.ietf.org/doc/html/rfc9368#name-version-downgrade-preventio


Add GitHub Enterprise Server support

Summary of the pull request
This PR contains the following changes:

Adds GitHub Enterprise Server (GHES) v3 Support (supported version determined by Octokit)

Adds LoginUI page for GHES flow to enter PAT

Refactors LoginUIController flow to be more encapsulated into Pages

Refactors CredentialVault to allow test configuration

Adds Unit Tests for DeveloperID components

Adds Functional tests for restoring and using saved credentials for repository query

Catches (and logs) a crash during Startup due to bad saved credentials

Also, enables multi-user support for widgets (requires Widget UI update in a follow-up PR)

References and relevant issues
https://github.com/microsoft/devhome/issues/825
LoginUI flow for GHES

Not uploading gif of 2nd page since it has personal info. Please try it out yourself.
Validation steps performed
Ran old and new tests, and manually ran through login flow, widget and setup flow.
PR checklist

[ ] Closes #xxx
[X ] Tests added - Currently fails due to lack of Env variables. Looking into this.
[ ] Documentation updated

Please run these these manual tests as well since developerid is being modified.

Log out of Github via settings page.
Navigate to the add repo dialog
Go to the account tab
Make sure the dialog asks you to log in, and, after logging in, the repos are shown.

For URL.

Log out of github
Navigate to the add repo dialog
Enter a private URL that you have access to.
Make sure the dialog asks you to log in, and, when logged in, the repo is added.

@bogdan-arsene

Is this PR planned to be merged anytime soon?

This feature will be part of v0.9 (likely mid-January release).


[DC-583] added suppression for cpt modifiers in procedure_source_conc…

…ept_id field

@mark-velez I have committed and pushed the updated query, when run it matches the 315 that need to be removed. Please take a look and let me know what you think. Thanks!

Closing. This was moved to another pull request #371.


First try to describe bedtools genomecov and learn CWL

This just a first step to describe bedtools genomecov [OPTIONS] -i "file" -g "genome file"

If input file in one of the bed/gff/vcf formats then prefix is -"i" if it is .bam the prefix is "-ibam"
Genome file must be in "chromName""tab""chromSize" format
For the beginning options has to be optional

I did an update bedtools-genomecov requires two params input bam file and genome file. All other params are optional. I don't know how to check type of input file (based on extension) and change prefix -i or -ibam. And force to use one of the params if the other is chosen (like --scale requires either -bg or -bga). The only default engine is JsonPointer or I can use JS?

I think I'll use this PR to setup an autotester using travis. Are these tests resource intensive?

No they are not. All of them one threaded and can be done on a laptop or VM

Hello, below is the list of GATK tools I was thinking to use for the workflow:
•	Mapping: Map with BWA for Illumina
•	Mark duplicates: Picard  MarkDuplicates
•	Indel Realignment: RealignerTargetCreator and IndelRealigner
•	Base Recalibration: BaseRecalibrator
•	Data compression with Reduce Reads: ReduceReads
•	Variant Calling: HaplotypeCaller
•	Variant recalibration: VariantRecalibrator and ApplyRecalibration
•	Variant Evaluation: VariantEval
I am assuming none of the tools are implemented using CWL as yet. What would be the best place to start? Thank you for all the help earlier,


[vcpkg docs][ES] Sync with English readme (#32698)

sync with the latest changes of the main readme file (#32698)
the changes mostly consist of removing some cmake references

I've validated the changes of this PR on ChatGPT, and they are reasonable.
Waiting for a dedicated localization person to review.


Quick question about README regarding Packagecloud::Package inititialization...

In the gem / rpm examples, an IO object is used by calling open, but the source example is just passing a string to Packagecloud::Package.new
https://github.com/computology/packagecloud-ruby#packages
Is this something that should be tweaked, or am I missing some case analysis in your implementation.
Happy to submit a PR, but wanted to make sure I am understanding things properly, cause it looks like read is called on the file object in all cases:
https://github.com/computology/packagecloud-ruby/blob/master/lib/packagecloud/client.rb#L117
Thanks for your work on packagecloud; has been really easy getting started.
Cheers!

Ah, yes this is definitely a typo in the docs, thanks for catching it!
I had planned for them to take string (the path) OR io object but never got around to it, and must have left the docs that way.
Glad you're enjoying using packagecloud!

Added a PR if my assumption is correct:
https://github.com/computology/packagecloud-ruby/pull/3

Thanks for the lightning quick reply!
Enjoy your day / weekend!


[bug] When signing messages, sometimes the website is opensea.io

Link to minimal reproducible example
preview: https://wallet-connect-demo-nine.vercel.app | github: https://github.com/liron-navon/wallet-connect-demo
Summary
I'm trying to get a user to do 2 things:

connect a wallet
sign a message

I sometimes get a title in the signing screen on metamask, stating the website "opensea.io" is requesting the signature, which is very confusing...
This signature was requested through the website wallet-connect-demo-nine.vercel.app and not opensea.io.
All the relevant code in the repo is in the file src/pages/index.tsx
devices:
This happens to me on the phone oppo find x3 lite

List of related npm package versions
"@web3modal/ethereum": "^2.6.2"
"@web3modal/react": "^2.6.2"
"viem": "^1.2.9"
"wagmi": "^1.3.7"
"ethers": "^6.6.2"

There is nothing in our codebase setting / falling back to opensea, so I'm not sure why this is happening, could be a cache bug in MetaMask or maybe dapp was setting metadata as opensea during testing?


XP Globe to show actions left.

Makes it a bit more handy when you want the client to not be that big in your screen.

Fixed in #1636


Code Pen Clone

Project title
Code Pen Clone
Project Description
It is an online editor for HTML, CSS, JS Code. https://codepenwebsiteclone.netlify.app/
It is created using React JS + Material UI.
Doc Domain

[] Solidity , Html, Css , JavaScript , Web3.js / Ether.js
[] Solidity , ReactJs /NextJs , Web3.js /Ether.js
[] Solidity , Python3 , Web3.py
[] Other , feel free to mention below

Are you contributing under any open-source program ?
I am contributing under SSOC 2.0

Great, start working on this.


Headset stuck on “the stream will begin soon”

Hi, so my quest is stuck at “the stream will begin soon”
I tried:
1.Opening 9944
2.Connecting to a faster network
3.Selecting h265 in the settings
Still stuck
Gpu: NVDIA GeForce GTX 1650
Video settings: the standard ones (except h265)
OS: Pop os (latest)

Same here.
GPU: Nvidia 2070
Standard settings
OS: Ubuntu Focal, 20.04.3
Gear: Oculus Quest 2
I haven't tried UDP yet. Not sure if it would fix it. But what I've noticed is that Steam VR detected the headset and was capturing the input from the headset. It's just there was no signal back to the Quest.

Just to add to this. This was resolved by adding the libraries as mentioned here: https://github.com/alvr-org/ALVR/issues/872#issuecomment-991292352
The problem now is that the picture is wrong and there is no sound. But at least, something is working now :)

Fixed by downloading and compiling nightly version

I'm using v17.0.0 and the issue still persists


[Proposal] Support for Multi-Values in Lookups

Motivation
The motivation is to combine two usage of two Druid features: Multi-value dimensions and Lookups. This will allow multi-value dimensions which are dynamic and have the correct value at query time, instead of data ingestion time, thus avoiding frequent and expensive data reindexing.
Note: This is considered specific use-case for now, so the proposed implementation, accordingly, tries to minimize breaking changes.
Proposed Changes
Overview
Lookups are a type of Extraction function. Extraction functions transform a string (that is, a dimension/column) into a new value. Druid query engine calls the extraction function apply() to perform the transformation on the dimension original values.
i.e.:
https://github.com/apache/incubator-druid/blob/3ae563263a23000560749071d262727d47296856/processing/src/main/java/org/apache/druid/segment/column/StringDictionaryEncodedColumn.java#L128
Each extraction functions has a DimensionSpec which defines the extraction API and its part in the query JSON.
Required changes
In the case of lookups, the transformation is a key-value lookup. So, in order to change Lookups to provide Multi-Values, and in order for queries to use these values, the following high-level changes needs to be implemented:

Changing apply() to return List<String>.
Changing the Lookups cache to store List<String> values.
Changing query engine to accept List<String> and to apply this list properly (As it does with Multi-Value Dimensions).

Principles

Minimize disruption (regressions, performance) to existing Lookups and Extraction functions codebase and users.
Don’t make breaking API changes.

Implementation
High level implementation steps:

A new LookupExtractor implementation, named MultiValueLookupExtractor is added, with the following additions:

New method: List<String> applyList(String key)
New map: Map<String, List<String>> map.

A new DimensionSpec called MultiValueLookupDinsionSpec is added. It exposes MultiValueLookupExtractor, bypassing LookupExtrationFn/ExtractionFn.
Note: I might break this into an abstract class and implementation class, which allows distinct implementations of the concept by people.

Query engine (groupBy, topN, Filters, DimensionSelector...) will be changed to call applyList() when a dimension is of MultiValueLookupDinsionSpec type.
This could be implemented in parts.

Changed Interfaces
No breaking API changes.
Adding a new DimensionSpec.
Migration / Operational impact
No migration needed.
Rejected Alternatives
Originally there was a plan to extend extraction functions along with lookups, but there were several caveats identified:

It is a much bigger change, both to extractions as well as existing lookups. It doesn’t involve just adding applyList() method but also things like storing the extractionFn in a separate field and returning it separately, and so on.
It isn’t clear if extractions will benefit for that features. It might be only relevant for lookups.
The main issue with the chosen proposal is that it create two separate code paths. In order to minimize that we could decide that if this feature tracks enough demand, we can refactor the code in the future to merge Multi-Value lookups code into the main lookups code.

Future work

This feature can be implemented gradually (across multiple prs) in the query engine code and officially released/documented when fully ready. This approach might be required, as each query-engine part needs its own deeper research.
At some point, in the chance this is becoming widely used, we can consider folding into the mainstream Lookups instead of keeping two separate code paths.

@drcrallen @b-slim I'd appreciate your perspective as you wrote lookups (or major parts of it).

I have started POC implementation to check feasibility. I'm concerned duplicating LookupDimensionSpec, as it is used by LookupModule so it probably requires to duplicate it as well.
With that, the rejected alternative might be easier.

Are there any updates on this ticket? We have a use-case that requires this functionality.

@irwvanroosmalen I welcome contributions from others. I am not actively working on implementation of this proposal.


Command sam failed with ENOENT

Hey,
When i try to deploy Start/Strop broadcasting service by using AWS CLI in windows os.
i get this Error message : "Command sam failed with ENOENT"
I already install SAM CLI version 1.29.0, AWS CLI 2.
I also execute sam --version command.

Hi，
Thanks for reporting the issue. Can you provide a more detailed log for the error?
Also, just want to double check with you, are you installing the SAM CLI on a 32-bit system or a 64-bit system? If you are on a 320-bit system, you can try to use pip install aws-sam-cli to install SAM. If you are using a 64-bit system, you can follow the instructions here.

Hi @ldai1 ,
I am using 64 bit system, i also get CLI version by execute command, this error occur while i am deploying Start/Stop broadcast service.
This error occur while execute this command : node ./deploy.js -b broadcast-lambda-cf-deploy-bucket -s broadcast-lambda-cf-stack -n broadcast-lambda -r us-east-1
i follow this step for deploying this service  : https://github.com/aws-samples/amazon-chime-live-events/tree/master/transcoding

@AnkurSavaliya Can you post the full error message? Please make sure to choose a custom stack and bucket name - do not use the stack name and bucket in the example

@AnkurSavaliya Do you still need help with this issue? Can I close it?

Closing issue due to inactivity. Please feel free to reopen the issue if you need help.


Initial port to JupyterLab 3 prebuilt extension.

This also adds a license file (BSD-3-CLAUSE), with @wolfv as the copyright owner.
Wolf, if you want to eventually transfer this to the jlab organization, I would like to iterate on this some more.

This seems to work okay in JupyterLab 3 now as a prebuilt extension:
Here we write a short extension that adds a command palette item in a text file, then loads the extension into JupyterLab:

I've commented out the widget support for now...

@wolfv - can I have write permissions on this repo? Thanks.

Hey @jasongrout yes, of course! Happy to transfer it anywhere you would like, too

hmm, somehow it seems that I can't make you admin on a personal repo?! didn't know that :)
Anyways, as I said, more than happy to transfer this repo wherever you think is best!
Really cool to see you iterating on this :)

hmm, somehow it seems that I can't make you admin on a personal repo?! didn't know that :)

I think you can make me a collaborator from https://github.com/wolfv/jupyterlab-dynext/settings/access, though.

I made you a collaborator already :)

I made you a collaborator already :)

Oh. I thought that would let me close issues, etc., but apparently not.
I'll ask during the dev meeting on Wednesday if we can transfer to the JupyterLab organization. Thanks again!


Cannot use dynamic import json file

Describe the bug
I tried to import some icons, which contain in json file, but i it give me an error when using dynamice import
Reproduction
https://stackblitz.com/edit/github-rgqsff?file=vite.config.ts
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 1.19 GB / 15.79 GB
  Binaries:
    Node: 16.4.0 - C:\Program Files\npm\node.EXE
    Yarn: 1.22.17 - C:\Program Files\npm\yarn.CMD
    npm: 7.18.1 - C:\Program Files\npm\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.39)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-react: ^1.3.0 => 1.3.2
    vite: ^2.9.7 => 2.9.8

Used Package Manager
pnpm
Logs
Unknown file extension ".json" for<EMAIL_ADDRESS>    at TypeError.get (https://github-rgqsff.w.staticblitz.com/blitz.1becece65fb9e6d89d27bbe87eedd4d64b37a3a4.js:6:292358)
    at buildErrorMessage (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:38471:29)
    at logError (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:38482:17)
    at viteErrorMiddleware (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:38499:9)
    at call (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43819:7)
    at next (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43767:5)
    at call (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43832:3)
    at next (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43767:5)
    at call (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43832:3)
    at next (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43767:5)
    at call (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43832:3)
    at next (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43767:5)
    at call (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43832:3)
    at next (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43767:5)
    at call (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43832:3)
    at next (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:43767:5)
    at viteTransformMiddleware (/home/projects/github-rgqsff/node_modules/vite/dist/node/chunks/dep-59dc6e00.js:5

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@SnowingFox I'm having the same issue, but I see that you closed this.
Did you solve it? if yes, could you please explain how :)

@SnowingFox I'm having the same issue, but I see that you closed this. Did you solve it? if yes, could you please explain how :)

Because vite config. TS is in the node environment, and node does not have the import () API, which is the browser API. If you want to dynamically import it, you can use the file to read it in.
https://github.com/unocss/unocss/tree/main/packages/preset-icons#nodejs

Eh, that part confused me as because vite is Node based so I thought the first few part of the icons documents were enough.
Thank you so much :)


Busted "busts" otherwise working Lua code

I'm having a strange issue with Busted where 5 out of 38 tests are failing for me in a suite that a) works fine for others and b) used to work for me. I'm on a new fresh machine running 2.0.0, and it's possible that I was previously using an older version and/or that others are on older versions too. I'm looking into that.
Travis has been running this suite forever and not had a problem.
I can replicate almost exactly the same code in plain Lua:
SILE = require("core/sile")

local frame = SILE.newFrame({ id = "hello", top = 20, left = 30, bottom = 200, right = 300 })
print(frame:height())

Run from the console as lua test.lua the answer I get is 180, which is correct. However trying to do the same thing with Busted gives me a different outcome:
SILE = require("core/sile")

describe("The frame factory", function()

  describe("Simple", function()
    local frame = SILE.newFrame({ id = "hello", top = 20, left = 30, bottom = 200, right = 300 })
    it("should have height", function () assert.is.equal(180, frame:height()) end)
  end)

end)

Run from the console as busted test.lua I get this:
0 successes / 1 failure / 0 errors / 0 pending : 0.090093 seconds

Failure → tests/frame_spec.lua @ 7
The frame factory Simple should have height
tests/frame_spec.lua:7: Expected objects to be equal.
Passed in:
(number) 0
Expected:
(number) 180

I can inspect the frame object and and see that is has the necessary properties and height() function. But I can also run that function outside of the it() construct and it outputs 0. Oops.
I'm stumped on what could be wrong, what might have changed, or how to debug this further.

If the code you're testing uses globals busted 2.0 may have exposed a problem in that code that busted 1 would not have. You can attempt disabling sandboxing as documented at https://olivinelabs.com/busted/#defining-tests to see if that fixes the problem, but I'd suggest fixing the code to not use globals instead just for maintainability's sake.

Thanks for the idea @DorianGray. That sounded like a promising lead because there are issues with globals in this code we're still rooting out.
Sadly this doesn't seem to be the root of the problem. I just found that our CI builds in Travis are also installing the 2.0.0 Luarock for Busted, and it is passing all tests. At the latest I expect other so be using the RC13 version and there doesn't seem to be any changes between that and the final release that would affect this.
I have tried changing up the test locally using expose() (and out of curiosity with insulate() and inspecting the output manually outside of the test framework entirely, just running it using busted ... as well), but am getting the same failures in all cases.

It must be something else about your environment specific to the tests then. If the versions of busted are the same on both systems and one passes and another fails then it's the system

As predicted by logic (@DorianGray) this was something else on my system. It took a maddening process of elimination because Lua path handling is so weird. Basically the code being tested was pre-pending package.path with local paths to test, and specific versions of some Lua Rocks were being placed locally for testing consistency. This would have worked, except in the Busted test an environment variable and convoluted code was hiding the fact that the system's default Lua path was getting prepended at the end of the process (so the system path was now listed twice, and, more relevantly, first.
An old version of one of the Lua Rocks on the system(s) in question was causing this inconsistency.


D7355-1204 error when playback

I started using the MS store version few days ago, it works flawlessly, untill it does not work from yesterday and showed me D7355.  I then installed the pack from Github and it does not work and show me D7355-1204
Any fix to make it work again?
Thanks

try update your browser
contact Netflix support

Edge is already the latest version 120.0.2210.61

I have the same issue now and I'm forced to use netflix store app.

contact the Microsoft EDGE development team. This error has nothing to do with me or Netflix. I have discussed it with Netflix.

https://github.com/lkmvip/netflix-4K-DDplus/issues/74#issue-2054633803


[#1328] Fix non-deterministic id generation

Background
https://github.com/square/sqldelight/issues/1328
We are seeing issues where sqldelight tasks break our build caching as query id generation is non-deterministic.
This can be caused by two reasons:

Gradle daemon keeps BindableQuery classloaded which means the incrementing query id is not reset between invocations
The ordering of generate*Interface task executions is non-deterministic

Change

Created QueryIdGenerator which is instantiated at the beginning of sql compilation step and additionally is scoped to a specific generate*Interface task instance
Use hash of $databaseName$counter as query identifier to ensure query identifiers for a module are consistent (solves 2)

Note this PR has some warts. @AlecStrong @JakeWharton would appreciate feedback on the approach. Ideally, we can come up with something more elegant here.
Test Plan
I ran unit tests. Some failed for me locally will verify travis CI succeeds.

Any other comments?

@AlecStrong I re-worked this a bit so we don't need to hook into SqlDelightFile which doesn't work well in practice.
Instead, I attach the database scoped queryIdGenerator to SqlDelightFileIndex. SqlDelightFile can then grab it from that class.
Let me know what you think.

much nicer, thank you. LGTM with the small nit


feat(ui): pipeline UX improvements

default fit the whole pipeline into view
drag like maps and zoom in/out using mouse wheel
[x] remember zoom preference - https://github.com/akuity/kargo/issues/2775
[x] Add screenshot/video

https://github.com/user-attachments/assets/14afcf3f-1686-4f36-bf70-1c06338a4cff

I also think the save button is overkill. I like it, but not sure if it is as useful as the reset button.
This is my personal opinion, so you don't have to do anything with that.

I think that makes sense @rpelczar, we have reset view anyways so I have removed explicit save view preference and it autosaves now. Let me know if you think otherwise @jessesuen @krancour

Btw, this breaks kargo on firefox due to https://developer.mozilla.org/en-US/docs/Web/API/Element/computedStyleMap not being supported there today

@02strich, thank you for bringing this to our attention. We've noticed this issue internally as well, and will work on a solution. Appreciate the report! 🙇


Honor new line chars. in ScoreText

It is used in Cadences identification exercise
Not possible: a CRLF starts a new paragraph.
Evaluate the real need and, if necessary, find a solution.

Closing. Time ago I used issues to track my TODO list. This is no longer the case and so I prefer to remove old issues I created.


Update kwsys

Update to newest kwsys, notably to fix bug with Apple Silicon.

@bradking @thewtex I'm confused why there should be conflicts.  Does ITK alter kwsys without going via upstream kwsys?

@seanm I think you based on a very old version of the release branch.  The conflict is with a more recent update of KWSys.

As always, git is my nemesis. :)
So I tried the following:
git checkout --track origin/release to get my own local release branch, I think.
then
git fetch upstream
git checkout release
git merge upstream/release
git push

Now it seems my fork's release is even with upstream.
Then I did:
git checkout -b update-kwsys-2021-02-10 origin/release
Modules/ThirdParty/KWSys/UpdateFromUpstream.sh

but now this fails with:
...
Resolving deltas: 100% (4770/4770), done.
++ '[' -n 2e004cc7547d3db156bed436e36bf34e6b4dd999 ']'
++ git worktree add /Users/sean/external/ITK/work/extract 2e004cc7547d3db156bed436e36bf34e6b4dd999
Preparing worktree (detached HEAD 2e004cc754)
fatal: 'add' is a missing but already registered worktree;
use '/Users/sean/external/ITK/work/extract -f' to override, or 'prune' or 'remove' to clear
+ rm -rf /Users/sean/external/ITK/work

There is a bug in the UpdateFromUpstream.sh script that breaks when running it more than once in a given work tree.  Run rm -rf .git/worktrees/extract to clean up after the first run.

I opened #2291 to update the third-party import script for that problem.

Oh!  It didn't occur to me that I'd done nothing wrong! :)
Wasn't sure how to fix this PR, so just created https://github.com/InsightSoftwareConsortium/ITK/pull/2292


vent.cfg now included in backups/restores

Codecov Report

Merging #674 into master will decrease coverage by 0.3%.
The diff coverage is 18.75%.

@@            Coverage Diff             @@
##           master     #674      +/-   ##
==========================================
- Coverage   86.05%   85.74%   -0.31%
==========================================
  Files          48       48
  Lines        3542     3557      +15
==========================================
+ Hits         3048     3050       +2
- Misses        494      507      +13

Impacted Files
Coverage Δ

vent/api/actions.py
84.04% <18.75%> (-2.38%)
:arrow_down:

tests/test_api_actions.py
99.11% <0%> (-0.89%)
:arrow_down:

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 f83a9c6...105ef7f. Read the comment docs.


Fix broken layout of kubernetes id concepts

Concept layout is broken because of missing content/id/docs/concepts/_index.md and missplaced cluster-administration directory. This PR fixes the issue.
Co-authored-by: Giri Kuncoro<EMAIL_ADDRESS>Co-authored-by: Irvi Firqotul Aini<EMAIL_ADDRESS>

Thanks for adding sitemap.md 👍 🎉 🎉   and adding index.md to concepts I'll rebase my changes for #13958 then.
/lgtm
/approve
/assign @girikuncoro

/approve


nsc-events-nextjs-1-122-add-requested-ui-features

Things of note:
[x]. Changed the name field to firstname and lastname. (Currently I have this code to communicate with the API,  the role aspect needs to be changed on the backend, as does seperating name out into firstname and lastname.
   const payload = {       name: firstName + " " + lastName,       email,       password,       role: "user",     };
[x]. Removed the Already have an account text.  (After looking at a bunch of signup pages around the internet I think we should leave this feature in as it follows common usage. But that's a decision for the product owner.)
[x]. Both passwords should be toggle-able , this is working and a prop passed to the InputFields.tsx, (note i used an online icon for this, we should discuss what to do about icons)
[x]. Added a confirm password button, also added error checking to ensure on submit both passwords are the same and >= 10 chars as it is on the backend. Also added some other basic error checking.
[x], Added null checks for the inputfields and error messages which are also passed to the InputFields, (this was written in tailwind before so I kept the tailwind code and added my own)
[x]. Added basic styling using the North Seattle style guide:
https://northseattle.edu/marketing-communications/logos-templates
(Logo was extracted from the PDF)
https://northseattle.edu/sites/default/files/inline-files/North Seattle College Branding Guidelines.pdf
[x]. connected to the backend. Currently this simply uses fetch to hit the backendAPI route with the payload above, if success it takes the token and console.logs it and saves it localstorage.
[x]. Add this to the package.json to match that of belinda's closet "dev": "next dev -p 8080",
Basic state of the page:

Error checking on null:

Showpassword toggled:

This PR closes #122

@Exochos Good job on the fields, I appreciate you adding validation to them! A problem I'm experiencing on my end, is that the image is obscuring the nav bar. This is what it looks like on my screen:


Integrate riscv-compliance

This pull request integrate riscv-compliance (riscv-arch-test) 2.0 into rv32emu-next
The Makefile target support running all test cases or a specific test case. The command line options are explained in README.md
Some tests does not pass because it still doesn't have a correct value defined yet.

Can you avoid using symbolic links in source tree? In directory build, we can create symbolic links. However, if symbol links exists outside build directory, it is a bit difficult and confusing to remove the linked entries.

Close in favor of #12


Mandatory assessment methods

Add before_summary_value question key
Required for #118392107. To add "mandatory" options to the brief view we need a way to add additional data to question summary value. So we're adding a new key to store this. Values from before_summary_value are never sent to the API, they're only used by the content loader for display in the summary tables.
Add mandatory assessment method values to brief questions
Make assessment methods quesiton optional
Since there's a mandatory value that's always added the question itself is now optional.

Let's do it :+1:


Remove hard dependency on TMPro package

Reality Collective - Reality Toolkit Pull Request
Overview
Remove hard dependency to TMPro. The assembly reference is kept in place.

Is this progressing @FejZa ?

It's on the not so distant roadmap.


Double click to enlarge the page shows an error

like title

what error does it show?

The pdf disappears when you double-click it


NFT metadata not showing up on OpenSea

Our NFTs are missing a read out of our metadata on OpenSea, not sure since when, and not sure if this is just an OpenSea indexing problem where they may only decode full metadata in testnets for some NFTs. But we had this working, only change done was the viewBox addition in #1247 which should have not affected this.

Already decoded some tokenURI directly to see if we have some syntax error or anything but couldn't find anything suspicious.
But might still be on OpenSea's side, case in point, as I wanted to screenshot the state of our current NFTs on there I got after a reload:

On etherscan appears to be fine:  https://rinkeby.etherscan.io/token/0x1a880dbd3bea1ab77c3c82a6f512ac66c36ddddc
will dig more

I triggered an update on opensea and now it looks good:
https://testnets.opensea.io/assets/0x1a880dbd3bea1ab77c3c82a6f512ac66c36ddddc/1

also, saw a bunch of other tokens published by the same address:
https://testnets.opensea.io/0x491aecc4b3d690a4d7027a385499fd04fe50b796
if you go one by one and trigger "refresh" button, opensea will queue them for update and they will be available in about one minute.

can confirm it works flawlessly with refresh

can also confirm it works with the refresh button

phew, crisis averted. So looks like OpenSea does not decode and index tokenURI by default anymore, still hoping they only do this on testnets. So for time being, we can only tell people to hit that refresh button


Some API classes are incorrectly private

A base class of a public class is implicitly public.  E.g., _HasAllowedValuesMixin shows up in the documentation but it is not clickable (here). Please check if this is more general and deal with such instances.

Sphinx does not generate docs for private members. We will have to make it public then it will be clickable.

That's what I mean. It should be public since it defines part of the interface of something else that is public. This isn't only about the Sphinx documentation.


Add an option to play the Spotted SFX for spottee, spotter, or both

Currently, the sound effect plays for tokens that get spotted. It would be fun if either a setting to play it for the spotter, or a seperate sound, could be added

Good idea, i think i will add it as a separate sound setting


Wrong width and height

I don't now if I'm doing wrong.
Here is the model settings:
image_picture_width = models.PositiveIntegerField(default=266)
image_picture_height = models.PositiveIntegerField(default=150)
image = PictureField(verbose_name = _("Category Image"), upload_to='tag_images', blank=True, width_field="image_picture_width", height_field="image_picture_height", aspect_ratios=[None, None, None, "16/9"])

In my template:
                {% picture tag.image alt="tag_image" m=2 l=2 style="max-height: 98px;object-fit: cover;" width="266" height="150" %}

I uploaded the image, but image_picture_width and image_picture_height were overridden (800px, 600px)
In Chrome inspector got this:
<picture>
  <source type="image/webp" srcset="/_pictures/tag_image/3x2/800w.WEBP 800w, /_pictures/tag_image/3x2/100w.WEBP 100w, /_pictures/tag_image/3x2/200w.WEBP 200w, /_pictures/tag_image/3x2/300w.WEBP 300w, /_pictures/tag_image/3x2/400w.WEBP 400w, /_pictures/tag_image/3x2/500w.WEBP 500w, /_pictures/tag_image/3x2/600w.WEBP 600w, /_pictures/tag_image/3x2/700w.WEBP 700w" sizes="(min-width: 0px) and (max-width: 991px) 100vw, (min-width: 992px) and (max-width: 1199px) 16vw, 200px">
  <img src="https://trivaty-dev.s3.amazonaws.com/media/tag_images/languages.jpg" alt="tag_image" style="max-height: 98px;object-fit: cover;" width="800" height="600">
</picture>

why the image width are not set correctly? how to fix that?
Thank your to clarify as no information are available in the docs.

Thank you for your reply.
I have cards with images inside. Each card is related to an object. I tried
to set a fixed width and height. I thought that setting the default values
for width_field and height_field would fix these objectives.
As  it did not work, I tried to set them in css inline. This is why I put
them as attributes in the picture filter.
Certainly, I did not understand the usage of width_field, height_field,
setting default height and width for images at the upload stage.
My aim is to get pictures with fixed width and height when they are
displayed in any browser (depending if xs, sm, m or l) as I'm using
bootstrap grid.
Hope i have clarified my current usage.
Also, I can not understand how to use this module for static images (not
depending on django model)? if you can tell me how to do this?
Many thanks for your help and how to get this work as I hope.
Sid Ahmed DINE
Directeur Général
Pinpoint Conseil
"More than knowledge, Simply a Know-How"
www.pinpoint-conseil.com
T : (+212) 5-22-21-77-83
M: (+212) 6-60-39-38-90
E: @.***
Le mer. 1 juin 2022 à 11:55, Johannes Maron @.***> a
écrit :

Hi @pinpointconseil https://github.com/pinpointconseil,
Thank you for reaching out. I believe there seems to be a bit of confusion
about how this library is supposed to work. Which tells me, I have to do a
much better job explaining it in the docs.
There are a couple of things, that strike me as odd at first glance, and
I'd really appreciate if you could give me a little more information.
Understanding your line of thought will help me improve the documentation.

Why do your width and height fields have default values? What would
you expect those default values to do?
Why do you have None defined 3 times as an aspect ratio?
You didn't specify an aspect ratio in the template, was that
intentional?
You passed an explicit width and height in the template. What were
your thoughts behind this?

Again, thanks for reaching out. Good documentation is key and with your
help I believe we can make them much better.
Best
Joe
—
Reply to this email directly, view it on GitHub
https://github.com/codingjoe/django-pictures/issues/24#issuecomment-1143449518,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALPERPKWIC6DCQBF5GDRSADVM46SRANCNFSM5XMUOG4A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @pinpointconseil,
ah, I see. So, I believe it's worth reading a bit into the fundamentals of responsive images. I believe this is a great resource:
https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images
This package is built to work with grid systems, and you don't need to define a width and height. You rather define an aspect ratio and how many columns your image is wide in your grid.
EG, you if you want a 16/6 image this is 4 colums on m and 3 on l and full width on mobile, you'd do something like:
{% picture obj.picture_field ratio="16/9" m=4 l=3 alt="picture of a dog" %}

The library will calculate the proper media queries for you and make sure that you serve the perfect sized image on any device or screen size.
This is a very different approach to how we used to handle images in the old days. There is not a single size. You need to serve the perfect resolution for 460dpi iPhones or 72dpi desktop screens.
I hope this will help you a little.
If you have any more questions, please ask. This is really helpful for me too.


Added support uint8

Thank you for the PR.
Are you aware that the package already supports uint8, aka byte, via the ByteSlice type and SearchBytes function?

Oh, sorry :) Thank you


Extract ssh/rdp/k8s info

Is your feature request related to a problem? Please describe.
To extract ssh log files from SDM, we need to use sdm-cli commands to make the conversion and output, and this is a very manual process.
Describe the solution you'd like
There's already a script to automate this in contrib logging section and it would be nice to have this script as a plugin in Log Export Container directly.

In order to enable this, you need to pass the following variable: LOG_EXPORT_CONTAINER_DECODE_CHUNK_EVENTS


KEA dhcp client hostname to syslog

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[ X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[ X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the solution you like
Would it be possible to send device hostname to syslog when device contacts server?
At the moment it only sends mac adress, example: INFO  [kea-dhcp4.dhcp4.0x33e0b3417b00] DHCP4_QUERY_LABEL received query: [hwtype=1 ma:ca:dd:re:ss:xx], cid=[ma:ca:dd:re:ss:xx], tid=0xa573c42c
Additional context
According to kea documentation this logger-name needs to be activated.
kea-dhcp4.ddns, kea-dhcp6.ddns | core | Used by the DHCP server to log messages related to Client FQDN and Hostname option processing. It also includes log messages related to the relevant DNS updates.
https://kea.readthedocs.io/en/kea-2.2.0/arm/logging.html#the-name-string-logger

@thsundel can you update the ticket with documentation links you found? It helps when someone wants to implement the feature

I'm not sure if anything needs to be activated here, according to the documentation, loggers inherit from their parent:

The loggers form a hierarchy. For each program in Kea, there is a “root” logger, named after the program (e.g. the root logger for kea-dhcp4, the DHCPv4 server, is named kea-dhcp4). All other loggers are children of this logger and are named accordingly, e.g. the allocation engine in the DHCPv4 server logs messages using a logger called kea-dhcp4.alloc-engine.

My guess would be that messages you're searching for need a higher log level, you could try to change the level for testing purposes in:
https://github.com/opnsense/core/blob/db8005b18639e7d3e6e1ea6319a80eba811f9734/src/opnsense/mvc/app/models/OPNsense/Kea/KeaDhcpv4.php#L210

Thank you for having a look at this feature request and yes I think you are correct. I had to set severity to DEBUG and debuglevel to 55 before hostname was included in the syslog message.
'severity' => 'INFO',
'debuglevel' => 55,
But that setting produces a lot of extra noise that I'm not interested in, I guess I'm out of luck then...
Thanks again for taking the time.

But if I add the following then I get the result I'm looking for, without extra noise. I guess this is not possible to get into the distro and I have to manually change whenever I update OPNsense?
                     [
                        'name' => 'kea-dhcp4.ddns',
                        'output_options' => [
                            [
                                'output' => 'syslog'
                            ]
                        ],
                        'severity' => 'DEBUG',
                        'debuglevel' => 55,
                    ]

I guess the amount of noise is staggering when changing the top level collector (kea-dhcp4) to debug/55, that would be an easy addition, micro managing the options will be quite an effort to do properly, not sure I want to spend my time on that to be honest.


removeGallery throws error: options is not defined

Relevant line: https://github.com/kairosinc/Kairos-SDK-Javascript/blob/master/kairos.js#L349

@steverucker Can you look into this?

This error is fixed.  The options argument was not being passed to the removeGallery and removeSubjectFromGallery methods.


Feature: Add always_print_primitive_fields flags into Controller and …

Add always_print_primitive_fields flags into Controller and json2pb::Pb2JsonOptions.
When serialize protobuf3 into json default fields do not dumps; this can be done by setting always_print_primitive_fields to true.

什么时候能合入版本中呀？

@jamesge 辛苦 再帮忙CR


[WIP] Setuptools packaging improvements - make each st2 component packagable and installable via package

This pull requests builds on top of of #1647 and #1668.
I spent a lot of time finishing, polishing and testing all the changes from #1668 locally. Everything worked and looked fine so I decided to merge it into master. Sadly this turned out to be a mistake - there were many, many issues with packaging and other workflows used by our CI.
After 3-4 hours of digging in and fixing issues, I still haven't managed to fix all of them so I decided to revert changes in the master and unbreak it. I believe that's better than trying to rush to whole thing. Next step will be to address all the issues and run all the packaging and related workflows on this branch and only merge it into master when everything passes.
I will work with / ask @DoriftoShoes for help with running everything on a particular branch (not sure if we are there yet, might require some changes).
The biggest offenders currently are:

[ ] Making sure we use pip >= 6.0.0 everywhere. I believe I managed to fix this by using virtualenv everywhere, but there might still be issues somewhere.
[x] Getting rid of the "recursive-include" abuse in the MANIFEST.in and replacing it with collecting all the code packages inside the setup.py files.

This branch includes the following changes and improvements:

Add new dist_utils.py module which is copied over to each component during build step and used inside setup.py instead of copy and pasting code over in setup.py.
Update all the setup.py files to include license and url attribute.
Add long_description attribute to each setup.py file. This attribute is generated by combining together README.rest and CHANGELOG.rst file.
Port README from Markdown to rst (needed because of 3).
Add new sdist Makefilet target which generates .tar.gz and wheel archive for each component.
Update setup.py files to use __version attribute from each package init.py file. For now we simply copy over init.py from st2common. This way we don't break out existing release / build workflow, but eventually we should move to per-package version.
Removed unused dependencies: flask, flask_json. This was actually done by @dennybaa, but I verified the changes and I'm pointing it out there to make it easier to track.
Sort the requirements before writing them in the requirements.txt file. This way we make sure generated requirements files are always sorted the same.

TODO:

[ ] Verify it doesn't break our current release workflows
[ ] Add end to end tests
[ ] Add new workflow steps for generating Python package distributions and publishing to to PyPi (not needed right now)

@dennybaa See the pull request description above. I had a really bad time with it.
There is a lot more of work which needs to be done making sure everything works end to end. Among other things, we need to get ride of recursive-include abuse in MANIFEST.in - using "*" means it will also try to include *.pyc and other files which are created while running setup.py dist command which will cause those commands to fail.
As noted in your other PR, we should explicitly collect Python package and module files inside setup.py and only include LICENSE, templates and files like that inside MANIFEST.in. Abusing recursive-include * is a bad idea since it results in all the files generated during dist phase also being included. You can exclude it with prune directive in MANIFEST, but that's a hack and we simply shouldn't abuse recursive-include.

I managed to get make debs and make rpms work fine locally now.
Before merging anything, I would like to run all the workflows on this branch and make sure everything works. @DoriftoShoes what's the easiest way to do this right now?

make debs and make rpms will loop through all the components and build packages for them but it will not fail if one package does not build.  This is why we have the package verification step in the build workflows.  You have to look in ~/debbuild and ~/rpmbuild on the systems where you ran make to see that all the packages got created.

@DoriftoShoes I tried building the packages locally in the VM (I installed all the dependencies) and everything worked fine.
I would like to run all the workflows which run when we merged a branch into master. I did merge branch into master yesterday after everything worked locally, but things exploded on the CI so I would like to make sure everything works before merging the branch and breaking everything (I needed to do a force revert yesterday).


fix: Updated skill manifest schema version

Description
Updated skill manifest schemas to include v2.1.
Task Item
Closes #4696
Screenshots

Coverage remained the same at 54.511% when pulling 896248106f79b2ae5df271ca9c4825aa69694942 on tdurnford:fix/manifest-schema into da63bc98db8ea8be00a96cb4c233365eae24e44d on microsoft:main.


why this method is needed?

https://github.com/shaikhAhmedRaza/hms_new/blob/d4acaea48576be18076c082236c37168db63afd9/src/app/service/client.service.ts#L158

For getting the list for the dropdown menu in add component template file


occurrences.getpoints response is limited to 10k records

I think there is a limit on the response from getpoints of 10k records.
When I use the instituteid as the getpoints query it responds with 10k records.
>> import pandas as pd
>> import pyobis
>> df_inst = pd.DataFrame(pyobis.occurrences.getpoints(instituteid='23070').execute())
>> df_inst.shape[0]
10000

However, when iterating through each dataset and use getpoints, and concatenating the responses together, I get 20,297 records.
>> combined = pd.DataFrame()
>> query = pyobis.dataset.search(instituteid='23070')
>> df = pd.DataFrame(query.execute())
>> df_meta = pd.DataFrame.from_records(df["results"])
>> for datasetid in df_meta["id"]:
...    dset = pyobis.occurrences.getpoints(datasetid=datasetid).execute()
...    df = pd.DataFrame(dset)
...    combined = pd.concat([combined, df], ignore_index=True)
>> combined.shape[0]
20297

I think this is on the API side, because https://api.obis.org/v3/occurrence/points?instituteid=23070 only returns 10k records not the expected 20,297.

Yes, I think this is on the API side because neither size nor skip parameters work at this endpoint.
One observation from your code snippet, pyobis provides a default to_pandas method to every response object across all modules to efficiently convert directly to a pandas DataFrame while also inflating the nested JSON inside some headers so that users need not take the pain. Just like this:
# construct the query
query = pyobis.dataset.search(instituteid='23070', size=100)
# execute the query, this actually helps you save your data which can be used as `query.data` anytime
query.execute()
# we get the dataframe with most nested JSON data uncoiled
df = query.to_pandas()

I think neither the API is open-source, nor the Swagger Contract is. The best case could be contacting @pieterprovoost for this.


charts: Add a values schema

It was mentioned here https://github.com/headlamp-k8s/headlamp/issues/1897 to take a look at the bitnami charts for postgresql.
The have some docs  https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml#L1635
Also they have a values.schema.json https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.schema.json
So this issue is about adding a values.schema.json JSON schema file.
https://helm.sh/docs/topics/charts/#schema-files
<EMAIL_ADDRESS>This would help people use the headlamp chart, by validating the user input.

Additionally, on artifact hub one of the quality badges is missing because it does not use a values schema.

Thank you for creating the issue. Working on this


Making some session data optional

We had the issue that the cookie produced by this project was too big for the upstream to handle (cookie size was ~ 6kb). This lead to looking into how we can reduce the amount of data stored in the cookie.
Eventually we decided to strip out the cookie entirely before passing it on upstream (not part of this pull request). Yet we already implemented a way to make some session data optional. This helps reduce overall transmission overhead. We managed to cut cookie size in half.
The option flags that need to be set for this to be activated are:
# The entire feature only works if this is set
opts.session_whitelist_vars
# Includes enc_id_token
opts.session_enc_id_token
# Includes session_refresh_token
opts.session_refresh_token

id-, and access-token cannot be omitted because they are inherently needed for the proxy to function.
New function openidc_store_session
While implementing this feature I refactored some session accesses into openidc_store_session which writes the current values into the session. The intent is to limit the access to the global state (session) to as few places in the code as possible and keeping the code legible.
This also changes the return values and fixes #69
I am open for any feedback :)

Wrt. the cookie size, see also: https://github.com/pingidentity/lua-resty-openidc/issues/33
lua-resty-session should be able to chunk up the cookie by itself since release 2.15, or you could use a server-based caching mechanism

The chunking is working. This is more about the overall cookie size

I'd rather see a single opt flag than the combination of two and thus blacklist the. E.g.
opts.session_blacklist_vars = { "enc_id_token" = true, "refresh_token" = true }

and then use:
if opts.session_blacklist_vars["enc_id_token"] then
  session.data.enc_id_token = auth_response.id_token or session.data.enc_id_token
end

etc.

superseded by #87


Error in console

I put in the mods folder the PrismPlus plugin latest version on sponge ore, and Prism-f456812-all.jar the last one, when I started the server it didn't give any problems but when it went online completely it started giving these errors, https: //pastebin.com/9uDX1sbT

This project is no longer in development but we definitely can't support PrismPlus.


TLS Code Audit link is self-referencing!

[Enter feedback here]
The line "The section Audit your code and make code changes covers auditing and updating your code." links back to this page - did you mean another page?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7341fa0a-f474-6c2d-d3c0-7e2df12fbb65
Version Independent ID: e99c489a-7518-d293-ad93-7eaca8b7191a
Content: Transport Layer Security (TLS) best practices with the .NET Framework - .NET Framework
Content Source: docs/framework/network-programming/tls.md
Product: dotnet-framework
Technology: dotnet-networking
GitHub Login: @karelz
Microsoft Alias: ncldev

That line links to a section a little further down the page. This was intentional.


Empty piecewise freezes symengine

The following code causes symengine to freeze:
import symengine

symengine.Piecewise()

In sympy this will raise an error:
TypeError: At least one (expr, cond) pair expected.

Let me know which ones you are working on (if any) and I can fix others.

We could assign ourselves to the issues we would like to work on.

I get the following error
In [1]: import symengine
   ...:
   ...: symengine.Piecewise()
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Cell In[1], line 3
      1 import symengine
----> 3 symengine.Piecewise()

File symengine_wrapper.pyx:3087, in symengine.lib.symengine_wrapper.Piecewise.__new__()

File symengine_wrapper.pyx:5298, in symengine.lib.symengine_wrapper.piecewise()

RuntimeError: piecewise undefined for this domain.

Thanks for testing. I can confirm the same error using the latest symengine.py. I was using an older version when testing this the first time.


chore(batcher): add use_kzg_da flag to propose block input

This change is

#2219  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Closing this PR, as a more end-to-end approach was taken. See #2238


Newsletters: add 297 (2024-04-10)

[ ] Lede, releases/RCs, topic entries
[ ] Bitcoin PR Review Club @stickies-v

@stickies-v here's the source to last month's review club section for reference: https://raw.githubusercontent.com/bitcoinops/bitcoinops.github.io/master/_posts/en/newsletters/2024-03-13-newsletter.md  Please don't hesitate to ask here, on IRC, or wherever if you have any questions.  Thanks for writing!  (And many thanks to @LarryRuane for his excellent work on this section every month since Aug 2022!)

I don't think I have write access here, so I've pushed a commit to add review club summary to my own repo: https://github.com/bitcoinops/bitcoinops.github.io/commit/1031b8cd7db76eb41e8948c4439a804929a7cf02
I tried to be mindful of the formatting and scripts used here but I'm not very familiar with this style so please let me know if something's off?

@stickies-v - Looks pretty good, two small things: a0 needs a close quote, and we tend to write shorter text source lines (up to around 80 columns), just because it makes the diffs easier to read if there are later edits. I didn't review for content but will try to do that in the next day or so. Thanks for taking this on!
Very minor suggestion, this might sound funny, but I've found it useful to "find on page" the question mark character when looking at the review club page (with the logs) in the browser -- the questions stand out that way and I can see if I can incorporate any of them in my writeup. (There are often questions that come up during the discussion that weren't written by the host ahead of time.)
(I had the same write access problem, but Dave fixed it.)
Another tip, in case no one mentioned it yet, don't force-push (either your initial commit or later corrections), because that could back out someone else's commit since we have multiple people pushing to the same branch. (I did that at least once!) Just do normal pushes, and Mike always squashes just before merging.

Thanks for the review, @LarryRuane and @bitschmidty . I've pushed an updated commit  8cb85fc104a9b55b46436dc58f8b7b9a186288b9 that:

fixes the missing quote issue (verified by actually building the website this time)
uses the proper linker mechanism for the BIP and bitcoin/bitcoin/pull
wraps to line length 72

Reviewed @stickies-v's section, looks great, thanks!  I made one small edit to pass our tests and one small edit to clarify a remark (since BIP62 was never activated, minimial-size pushes are only required in relay/mempool for legacy transactions, although I believe they're required for both segwit v0 and v1 at the consensus layer).
Made edits (or left a reply) for all review comments to date (thanks @LarryRuane @bitschmidty !), added lede, releases/RCs, and topic entries.  This should be ready to go, but I'll check back later to see if there are any additional reviews.
Thanks everyone!

Addressed @vostrnad additional comments (thanks!  and thanks @LarryRuane for re-reviewing!)


don't download all of the browsers

We should have a good story using playwright-core to not download any browsers on install, but get them just-in-time when the user wants to run tests in them.
This isn't trivial because it also has to work on CI, where people expect all of their dependencies to install on npm install, and then they cache their node modules folder and send it to a computer with no network access. But maybe we can make this the edge case solved via environment flags?

I'm curious what the status of this work is. The issue is closed, but when I run npm i -D @playwright/test @playwright/test-runner I still see all three browsers being downloaded.

@mxschmitt Maybe we could reopen this issue?

Ty @arjunattam!

So, is there a recommended solution from a user's perspective? The comment of @mxschmitt seems like this still needs to be implemented. Would it help to add playwright as a peer dependency? https://github.com/microsoft/playwright-test/issues/206


add main guard clause to basic multiprocessing download example

Hey not sure if this is an issue specific to my machine but when I copied the minimum batch download example in Notebook 5 for the examples I had the multiprocessing package throw errors that I needed a main guard clause. I figured I would adjust this example to be functional since folks may want to copy it directly.
This should fix this minimum working example to work with 10 processes and not throw errors due to child processes trying to restart the downloads over and over.
An alternative solution would be to just not include the processes = 10 option to avoid these errors in the example.

Never mind this was just an issue with my multiprocessing package. Tried it on a different machine and it looks great.


Update action-query.md

Docs Build status updates of commit 649f84a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

access/Concepts/Miscellaneous/action-query.md
:warning:Warning
View
Details

access/Concepts/Miscellaneous/action-query.md

Line 27, Column 3: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/answers/questions/topics/single/240765.html' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 27, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/answers/questions/topics/single/240765.html' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5f19065:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

access/Concepts/Miscellaneous/action-query.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


"nuke-colortools.toolsets.visualize.HueSweep" has a dark line in the blue channel.

In Expression10:
x>width/3&&x<width/3*2

should be
x>width/3&&x<=width/3*2
             ^

Sorry totally missed this! Thanks for the fix, I've merged it.


example/latent_sde_lorenz different from whats written in the paper?

Hi there,
first of all thank you for your work! This is great!
Disclaimer: i don't know much about SDE, but i would love to make use of neural sde, since i have some use cases that i think could work with it. But mostly i find it highly interesting! So i hope i didn't get it all wrong entirely.
I think there are quite some differences between your code example and whats decribed in your paper.
In the paper it says, that you have a 1 layer GRU to recover the dynamics and f_net and h_net both are 1 layer MLP, while f_net takes an additional context variable of size 1 .  Then, there's a decoder to map back from latent space to feature space.
So if i understand correctly, this model would work just like shown in figure 4 of your paper:
The GRU consumes a (time reversed) sequence of inputs in observation space and outputs a sequence in a 4D latent space. The final output (at t0) then is your initial condition (z0) for the sde, which is integrated through time, producing another sequence in latent space. So the dynamics would happen in latent space. Then the decocer maps back to observation space. What's a little unclear to me, is what the context would be. Just one (the last) latent variable from each of the GRU outputs?
Anyway, this describes an actual latent sde, since all the dynamics are happening in latent space.
However, in your implementation in the example, all the dynamics happen in observation space directly. f_net and h_net both map from observation space to drifts in obeservation space (well f_net again sees an additional context, which is of size 64 here). So the GRU encoder "only " provides the context, but not the initial latent state. Meaning it does not recover the dynamics, if i understood it right.
So this is not an actual "Latent SDE" model, is it?
Similar thing for the latent_sde example. The dynamics are learned in obesrvation space as well, so there is no latent space involved. One could claim that the latent space is equal to the observation space here of course. Or do i simply have the wrong idea of what "Latent SDE/ODE" actually means?
In general, i think this package could greatly benefit from a more in depth documentation in regards to training models with it and/or better explained examples. One or two examples of standart use cases in jupyter notebooks with detailed explanations could help a lot to make this more accessible to people that don't have much background in SDE (like me).

Thanks for your interest!

The GRU consumes a (time reversed) sequence of inputs in observation space and outputs a sequence in a 4D latent space.

What's a little unclear to me, is what the context would be. Just one (the last) latent variable from each of the GRU outputs?

The GRU outputs at intermediate times can also be used for practical performance benefits (e.g. check this out). The searchsorted operation here is used to find the "right" context that's produced only using future observations.

However, in your implementation in the example, all the dynamics happen in observation space directly.

I think it's fair to put it that way, and to say that points in the latent space are mapped to the observed space via an identity transform.

So this is not an actual "Latent SDE" model, is it?

I think you have a fair point. I agree that I was somewhat sloppy with the re-implementation. Essentially, the things that are simplified are 1) variational inference at time t0 (I didn't include the KL penalty, or a prior), and 2) an actual non-trivial decoder that maps points in the latent space back to the observed space.
To properly do 1), one would first select a good prior (say N(mu, sigma); mu and sigma can be optimized during training). To compute the KL penalty, one would need also the variational distribution given by the encoder (e.g. dependent on the last output of the GRU or return value of some other encoder).

In general, i think this package could greatly benefit from a more in depth documentation in regards to training models with it and/or better explained examples. One or two examples of standart use cases in jupyter notebooks with detailed explanations could help a lot to make this more accessible to people that don't have much background in SDE (like me).

Thanks for the suggestion and I totally agree! Happy to spend time in documenting the model better in the future, though quite unfortunately my schedule in the near future seems quite packed.

Thanks for answering! That cleared thing up!

What's a little unclear to me, is what the context would be. Just one (the last) latent variable from each of the GRU outputs?

The GRU outputs at intermediate times can also be used for practical performance benefits (e.g. check this out). The searchsorted operation here is used to find the "right" context that's produced only using future observations.

What i meant was: In the paper a context size of 1 is mentioned, while the latent space is 4 dimensional. I assumend context size of 1 was referring to the latent dimension, so that you took only one of the 4 latent variables of the according timestep of the GRU output sequence as the context. But it referrs to the time dimension, so all for latent variables, got it!

In general, i think this package could greatly benefit from a more in depth documentation in regards to training models with it and/or better explained examples. One or two examples of standart use cases in jupyter notebooks with detailed explanations could help a lot to make this more accessible to people that don't have much background in SDE (like me).

Thanks for the suggestion and I totally agree! Happy to spend time in documenting the model better in the future, though quite unfortunately my schedule in the near future seems quite packed.

Awesome! I am looking forward to it, whenever it may be!
Even though this is porbably not the right place, as github issues are not meant as a forum to ask for help, i'll still try sneak in a few practical questions. I would be thrilled if you could give some answers! However, if that is not appropriate, feel free to shoot me down and close.
In my potential use case, i have a bunch of timeseries data. I would like to fit one sde model to it to make predictions into the future, based on a given portion of timesteps. So it is pretty similiar to the latent_sde_lorenz example. Even more to the example of the geometric brownian motion in your paper, i think.

I am a little confused about the roles of prior h und approx posterior f in this setting. It's probably due to my lack of knowledge in the field, though i think i know what prior and posterior distributions are, but i am not entirely clear by their roles here: Is the approx. posteriors role only to condition the prior, so that we can make good predictions with it? So inferrence would always happen with the prior dirft? In the geometric brownian motion example, you make future predictions with both. But for the model setup as decribed in the last posts, that would mean that the context for the approx. posterior drift would remain static for all t>1, as the GRU didn't give outputs there, is that correct? So i guess that would deteriorate predictions the farther out in the future they are, right?

Instead of the output of one discrete path, a more relevant predicion would be the expected value and its variance at a (future) timestep. Computing those for constant drift and diffusion seems easily possible. But in case of a neual sde, do you know if it is possible to compute those directly? In the example latent_sde, i think you kind of compute them by sampling a bunch of pathes in order to show something like the pdf at each timestep (colorcoded in blue). Having an option to make sdeint compute the expectation and variance natively might be very useful actually!

Since i think this is how the adjoint backward pass is implemented anyway, having an option to integrate backward through time might be very useful too! But to implement it myself, this is a good starting point i guess? (only need to figure out why g**2 is scaled by score and how that translates to my usecase?)

What i meant was: In the paper a context size of 1 is mentioned, while the latent space is 4 dimensional. I assumend context size of 1 was referring to the latent dimension, so that you took only one of the 4 latent variables of the according timestep of the GRU output sequence as the context. But it referrs to the time dimension, so all for latent variables, got it!

The context vector is an extra piece of information that isn't really related to the latent space. It doesn't really refer to the timestamps either. On the other hand, the timestamp is used to select which context vector we should use for integrating the SDE in a specific time interval.

Even though this is porbably not the right place, as github issues are not meant as a forum to ask for help, i'll still try sneak in a few practical questions, i hope you don't mind. I would be thrilled if you could give some answers! However, if that is not appropriate, feel free to shoot me down and close.

I'm closing the issue for now after the fixes, but I'm also happy to keep chatting here if that may be helpful.

I am a little confused about the roles of prior h und approx posterior f in this setting.

I'm splitting this reply into several segments, as one giant grid of text may seem intimidating.

I am a little confused about the roles of prior h und approx posterior f in this setting.

If you're familiar with Gaussian processes, I'd say that it's reasonable to think that the prior here is analogous to the prior there when you're only fitting a single time series sequence. In fact, the OU process is a Gaussian process, and this is a special case where the two model classes somewhat coincide. Notably, things are a bit different when one is fitting multiple time series sequences and trying to do interpolation/extrapolation for each sequence individually.

But for the model setup as decribed in the last posts, that would mean that the context for the approx. posterior drift would remain static for all t>1, as the GRU didn't give outputs there, is that correct?

If the goal is extrapolation based on observations of a single time series sequence, I'd recommend using the posterior drift.

Instead of the output of one discrete path, a more relevant predicion would be the expected value and its variance at a (future) timestep. Computing those for constant drift and diffusion seems easily possible. But in case of a neual sde, do you know if it is possible to compute those directly? In the example latent_sde, i think you kind of compute them by sampling a bunch of pathes in order to show something like the pdf at each timestep (colorcoded in blue). Having an option to make sdeint compute the expectation and variance natively might be very useful actually!

I'd agree the naive method would be to estimate the statistics with samples. I'm aware of works that intend to approximately simulate SDEs by only simulating the marginal mean and covariance ODEs. I may not be up-to-date on the latest developments there, but I haven't seen a paper that convincingly demonstrated that such a method is consistently accurate and leads to models of good utility.
More generally, the problem is related to simulating the Fokker Planck, which is known to be difficult aside from special cases.

Since i think this is how the adjoint backward pass is implemented anyway, having an option to integrate backward through time might be very useful too! But to implement it myself, this is a good starting point i guess? (only need to figure out why g**2 is scaled by score and how that translates to my usecase?)

Our adjoint implementation is in this file. The core functions of interest are the reverse drift and diffusions (e.g. here and here).
What you listed in the example is something very different, and comes from another paper. I implemented it for MNIST before they released their codebase, and it was mostly for fun for myself.
Notably, the reverse SDE formulation in that paper is totally different from ours. The backward/time-reverse-SDE formulation in our paper ensures that individual sample paths can be reversed given a fixed Brownian motion sample. The time-reverse SDE in their paper only ensures that the marginal distributions can be reconstructed. Note, one could get the same marginals even with different sample paths.
For their purposes and applications, their reverse-time SDE formulation was sufficient.

Thank you for the answers! I think I'll have to read a little further into the topic and try to set up a small model for my use case when i have the time ( it's just a little side project right now, out of interest ) before asking any more questions here. Thanks for offering to keep on chatting here!


Python: Add Support for Ollama SDK Connector

Add support for Ollama using the Python Ollama SDK. This is separate from Ollama support using the OpenAI Connector.

If you redo the connectors.AI.ollama, please also think about providing some basic OpenAIPromptExecutionSettings compatibility for OllamaAIPromptExecutionSettings. Currently e.g. "temperature" with OpenAIPromptExecutionSettings becomes "options"."temperature" with OllamaPromptExecutionSettings. This is e.g. breaking the SequentialPlanning settings from python/semantic_kernel/planners/sequential_planner/Plugins/SequentialPlanning/config.json.
Yes, I know that Ollama uses "options", but I think exposing this difference to SK plugins,... is bad for the most common parameters like:

temperature, top_p, stop, seed (these just need copying to "others"....)
and also do some translation of max_tokens into num_predict, as well as frequency/presence_penalty into repeat_last_n/_penalty.


I'd like to help but don't know where

Hé potential contributor 👋,
We have tons of features we'd like to add to the site still, but we don't have neat issues for all of them.
If you don't see a neat issue you can pick up but do want to contribute, let us know here and we'll offer something 🤲, or rather, gladly accept your offer to contribute.

If you need any design support, I can help :)

@pedrocarballo definitely welcome, contact me on TG https://t.me/smilingalex

I would like to help

@Erik-McKelvey tell us a bit about your skillset (:

@alextes I have 8 months of full-time experience working with React (among some other stuff), and I've done some work with web APIs. Probably not super relevant but I have also made a Solidity smart contract project. I could help with components or API stuff.

@Erik-McKelvey completely missed your reply. Sorry Erik 🙈 . Ping me on TG if you still feel like contributing 👍 . t.me/smilingalex

Hello, would like to help. I'm a SWE generalist with a strong focus on backend. Main skillset is Scala, JS/TS and smol Rust. Happy to help any way I can.


Update kind-projector to 0.11.3

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "kind-projector" } ]

labels: library-update, semver-patch

Closing in favor of https://github.com/Banno/vault4s/pull/170