Bower+Webpack support

Please remove the ignore of src and examples from bower.json, because we need the src to pack using webpack, the dist file is already packed which is not convenient for webpack to analyze. The example is the docs which is lack now.

I can include the src folder, but if you are using webpack, you should prefer installing via npm.
Example should not be included in the package, you have to run it by cloning the repo and installing all the dependencies anyway.


Pre-Requisites not mentioned accurately

Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT

What happened:
Not able to understand the pre-requisites for Setting up OpenEBS with Kubernetes using Minikube where it has been mentioned that Machine Type - (Minimum 4 vCPUs)
What you expected to happen:
It could have been explained well
How to reproduce it (as minimally and precisely as possible):
may be in simpler terms
Anything else we need to know?:
Environment:

kubectl get nodes
kubectl get pods --all-namespaces
kubectl get services
kubectl get sc
kubectl get pv
kubectl get pvc
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

It'll be good to have a section/wiki somewhere where we enlist the processes for installing dependencies.

@NisantaSahoo  I would like to take this. Please, assign it to me.

@aj07 All yours :+1:
@aj07 Do share your thoughts on this here.

IS your cafe for hacktoberfest opened today?

@aj07 Yes, we are open from 09:30

The Docs for Minikube are now available at: https://docs.openebs.io/docs/devsolutions.html
The docs have to be updated in a way that the end user is able to understand.

The updated
prerequisites are here https://docs.openebs.io/docs/next/prerequisites.html
minikube - https://docs.openebs.io/docs/next/supportedplatforms.html#native-kubernetes-and-minikube


chore(checkboxes): add paparazzi tests

Changes description 🧑💻

Add paparazzi tests for checkboxes and fix alpha issue in disabled mode
Context 🤔

Closes #85
Checklist ✅

[x] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
[x] Check commits & PR names matches our requested structure. It must follow the https://www.conventionalcommits.org pattern.
[x] Check compose contract convention. It must follow conventions described here.
[x] Check your code additions will fail neither code linting checks.
[x] I have reviewed the submitted code.
[x] I have tested on a phone device/emulator.
[ ] I have tested on a tablet device/emulator.
[ ] I have tested on a large screen device/emulator.
[ ] If it includes design changes, please ask for a review design-system-core-team-design GitHub team.

Screenshots 📸

Other info 👋

You can download the apk here :

You can download the apk here :
sample-debug.apk :
https://app.bitrise.io/app/e9ae480151be4514/build/7bdc3709-be22-4ba1-b78d-581c31bfd8f4/artifact/b1d502a7958f8af6/p/4aabad02aea442d0a61b9a15b28a6b6d


Show duplicate token on receive list when search custom token

Describe the bug
Show duplicate token on receive list when search custom token
To reproduce the behavior
Steps:

Import any custom token successfully (Ex: 0xb161b2da48de283ec22bafbc36e5551c892629a2 - Moonbase Alpha)
After imported successfully, go to the Homepage
Click on Receive button
On the select token, input keyword = "MFG" then clear search
Repeat step 4 several times then observe the token list displayed

Actual: Show duplicate custom tokens on each search

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1515-build-1.0.8-2023-06-09T08-48-52UTC.zip
Validation passed.


chore: Rename viper to oldviper

The version of viper currently used in fabric is 5 years old. It prevents integration with any library that requires a newer version of viper.
This patch renames viper to 'oldviper' to allow for integration with libraries that use a newer version.
closes #122
Signed-off-by: Bob Stasyszyn<EMAIL_ADDRESS>

Parking this for now since there are other technical issues (WRT protos) that need to be resolved first.


Scrollbars don't reappear when fadeScrollbars=true

With fadeScrollbars enabled, the scrollbars appear only once at first load, then fade out and never appear again.

At the moment I only Override the calculations of the scrollbar sizes and leave the rest to the FrameLayout Code, but may be it is something to do with the Motion Events processing, so I will need to investigate this more.

Fixed by commit https://github.com/Zardozz/FixedHeaderTableLayout/commit/4e2cf4f6a2d0b9d4438e94358bf33f8f08461324
Will release version <IP_ADDRESS> soon with it in.


Update simple.md

Add option to pass username & password for login command.

Hi @imshashank! Thanks for noting the discrepancy between our README and the docs. :+1: I'll merge your contribution.

Hi @imshashank! Thanks for noting the discrepancy between our README and the docs. :+1: I'll merge your contribution.


[json-rpc] CORS: allowing all origins for the interface

This PR may have modified JSON-RPC server code.
Breaking changes policy:

Chaning JSON-RPC method signatures or removing/modifying fields
in the response in /V1 will not be accepted.
Adding fields is ok.
Adding a new JSON-RPC method is ok.

Please ensure you have also done the following to update the docs:

Update json-rpc/API-CHANGELOG.md.
Add/update type/method documentation under json-rpc/docs.

@xli should this be documented in the changelog?

How do we verify that this works? I just built an image from this PR and deployed to a testnet: http://rustielin.aws.hlw3truzy4ls.com/
Curl is not returning the right headers I think:
$ ▶ curl -d '{"jsonrpc": "2.0", "method": "get_account", "params": ["000000000000000000000000000000dd"]}' -H 'Content-Type: application/json' -i --verbose http://rustielin.aws.hlw3truzy4ls.com/
*   Trying 64:ff9b::2ce6:4e4e...
* TCP_NODELAY set
* Connected to rustielin.aws.hlw3truzy4ls.com (64:ff9b::2ce6:4e4e) port 80 (#0)
> POST / HTTP/1.1
> Host: rustielin.aws.hlw3truzy4ls.com
> User-Agent: curl/7.64.1
> Accept: */*
> Content-Type: application/json
> Content-Length: 91
>
* upload completely sent off: 91 out of 91 bytes
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Wed, 30 Sep 2020 20:30:57 GMT
Date: Wed, 30 Sep 2020 20:30:57 GMT
< Content-Type: application/json
Content-Type: application/json
< Content-Length: 1159
Content-Length: 1159
< Connection: keep-alive
Connection: keep-alive

<
* Connection #0 to host rustielin.aws.hlw3truzy4ls.com left intact
{"libra_chain_id":3,"libra_ledger_version":486588,"libra_ledger_timestampusec":1601497857028863,"jsonrpc":"2.0","id":null,"result":{"address":"000000000000000000000000000000dd","authentication_key":"cd907006959c0f4afb78568710e418ba3630930522a40bd3146f71de5b4f23d0","balances":[{"amount":4611686016239387903,"currency":"Coin1"},{"amount":4611686018427387903,"currency":"Coin2"},{"amount":9223371981554775807,"currency":"LBR"}],"delegated_key_rotation_capability":false,"delegated_withdrawal_capability":false,"is_frozen":false,"received_events_key":"0300000000000000000000000000000000000000000000dd","role":{"base_url":"","base_url_rotation_events_key":"0200000000000000000000000000000000000000000000dd","compliance_key":"","compliance_key_rotation_events_key":"0100000000000000000000000000000000000000000000dd","expiration_time":18446744073709551615,"human_name":"moneybags","preburn_balances":[{"amount":0,"currency":"Coin1"},{"amount":0,"currency":"Coin2"}],"received_mint_events_key":"0000000000000000000000000000000000000000000000dd","type":"designated_dealer"},"sent_events_key":"0400000000000000000000000000000000000000000000dd","sequence_number":3289}}* Closing connection 0

that would be a good way to test it! It's been years since I read anything on CORS, but IIRC you should only get it when you use some verbs like OPTION and POST?

I don't think api-changelog need to be updated.

added a test, it should work! If you're testing that from the browser, try:
var xhr = new XMLHttpRequest();
xhr.open("POST", "https://rustielin.aws.hlw3truzy4ls.com", true);
xhr.setRequestHeader('Content-Type', 'application/json');
xhr.send(JSON.stringify({
  "jsonrpc": "2.0",
  "method": "get_account",
  "params": ["000000000000000000000000000000dd"]
}));


Bring your own attribute id type

This is still effectively hardcoded to strings, but it's a first step to a more general treatment.

Now aid type is truly generic throughout the library.


Add TVos and OSX targets. Add a number of new linq extensions.

Love this extension- so much I've added targets for supporting TVos and Mac OSX. I've also added a few extensions- some set operations and a few other handy NSArray linq_ categories. See the bottom of NSArray+LinqExtensions.h.

Great job, thank you :-)
For the newly added operations can you please add unit tests and also add them to the README file? That would be really helpful!


Allow conversion from integer values to double in Firestore deserialization

Fixes #3013
Note: I'm not yet sure that we want to merge this, but I want to get it ready if we do want to merge it.

Added an extra commit for the reverse conversions, as well as handling float as well as double. PTAL - just at the last commit.


Annotate flaky tests

WHAT
Annotate flaky tests
WHY
https://github.com/google/horologist/issues/407
Checklist :clipboard:

[N/A] Add explicit visibility modifier and explicit return types for public declarations
[x] Run spotless check
[x] Run tests
[N/A] Update metalava's signature text files

Merging with red build as failed test is already annotated with FlakyTest (https://github.com/google/horologist/issues/407) and it shouldn't have ran. https://github.com/google/horologist/pull/417 should have fixed this.


Update recommendation.md

add a recommendation for tcpkeepalive option.

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


⚠ ClamAV has degraded performance

In 1b619d2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 652 ms

Resolved: ClamAV performance has improved in f6b4439.


[SvelteKit] Error: The "host" request header is not available at isSecureEnvironment - When fetching from API routes

Bug report
Describe the bug
When fetching from an API route from a client side or server side page, Supabase auth lib will throw an error:
Error: The "host" request header is not available at isSecureEnvironment
To Reproduce
Example repo to reproduce:
https://github.com/chanmathew/sk-supabase-authhelpers-host-request-header-issue

Create an API route, in the example repo, I created /routes/api/products/+server.ts
Fetch from this new API route from a page (Doesn't matter if it's client side OR server side, I've tested and issue exists for both), in the example repo I made a server side fetch from /routes/products/+page.server.ts
Load the /products page in browser and check logs in server console, you will see this error from Supabase auth helpers: Error: The "host" request header is not available at isSecureEnvironment

Expected behavior
This error should not be thrown, especially given the API route is not fetching data from Supabase and is completely unrelated.
System information

OS: macOS Ventura 13.1 (22C65)
Browser: Chrome 108.0.5359.124
Version of supabase-js: 2.2.2
Version of Node.js: 16.17.0

I'm new to coding so take it with a grain of salt. I was having the same issue, and I think it's because the fetch at /api/product/+server.ts is not receiving the host header from hooks.server.ts. I added a handleFetch function like this in my hooks.server.ts and it solved the issue for me.
`import type { HandleFetch } from '@sveltejs/kit';
export const handleFetch = (async ({ event, request, fetch }) => {
if (request.url.startsWith('https://api.my-domain.com/')) {
const host = event.request.headers.get('host')
if (host) request.headers.set('host', host);
}
return fetch(request);
}) satisfies HandleFetch;

This error should not be thrown, especially given the API route is not fetching data from Supabase and is completely unrelated.

Inside hooks.server.ts getSupabase is called which internally fetches a new session if the current one is expired.
It seems like the request does not include a host header when fetching from a +server request handler.

I'm new to coding so take it with a grain of salt. I was having the same issue, and I think it's because the fetch at /api/product/+server.ts is not receiving the host header from hooks.server.ts. I added a handleFetch function like this in my hooks.server.ts and it solved the issue for me.
import type { HandleFetch } from '@sveltejs/kit';

export const handleFetch = (async ({ event, request, fetch }) => {
  if (request.url.startsWith('https://api.my-domain.com/')) {
    const host = event.request.headers.get('host')
    if (host) request.headers.set('host', host);
  }
  return fetch(request);
}) satisfies HandleFetch;

this then blocs +layout.ts where I try to get supabase user
+layout.ts
import type { LayoutLoad } from './$types'
import { getSupabase } from '@supabase/auth-helpers-sveltekit'

export const load: LayoutLoad = async (event) => {
    const { session } = await getSupabase(event)
    console.log("LayoutLoad. User = ", session?.user.id);
    return { session }
}

+hooks.server.ts
import '$lib/supabaseClient'

import { getSupabase } from '@supabase/auth-helpers-sveltekit'
import type { Handle, HandleFetch } from '@sveltejs/kit'

export const handleFetch = (async ({event, request, fetch }) => {
    // if (request.url.startsWith('https://api.my-domain.com/')) {
    const host = event.request.headers.get('host')
    if (host) request.headers.set('host', host);
    // }
    return fetch(request);
}) satisfies HandleFetch;

export const handle = (async ({ event, resolve  }) => {
    console.log("Ran HooksServerHandle");
    const { session, supabaseClient } = await getSupabase(event)
    event.locals.supabaseServerClient = supabaseClient
    event.locals.session = session
    return resolve(event)
}) satisfies Handle;

console log  LayoutLoad. User =  undefined

@lt692 do you have a repo i can take a look at?

One thing i noticed is that you are saving the supabase client to locals.
When doing so a supabase client is created on every request, no matter if it will actually be used or not.
The getSupabase helper internally adds the client it creates to locals using a symbol as a key so it will be reused when it´s called  again for the same request.
Therefore I´d suggest calling getSupabase(event) whenever you need the supabaseClient or session.

For the moment you can also get rid of this error by manually settings the secure cookie option:
import { createClient } from "@supabase/auth-helpers-sveltekit"
import {
	PUBLIC_SUPABASE_ANON_KEY,
	PUBLIC_SUPABASE_URL,
} from "$env/static/public"

export const supabaseClient = createClient(
	PUBLIC_SUPABASE_URL,
	PUBLIC_SUPABASE_ANON_KEY,
	{},
	{
		secure: true
	}
)

One thing i noticed is that you are saving the supabase client to locals. When doing so a supabase client is created on every request, no matter if it will actually be used or not. The getSupabase helper internally adds the client it creates to locals using a symbol as a key so it will be reused when it´s called again for the same request. Therefore I´d suggest calling getSupabase(event) whenever you need the supabaseClient or session.

yeah I followed this youtuber approach of handling authentication https://www.youtube.com/watch?v=lSm0GNnh-0I&t=341s
and it comes with its cons and pros...
and for the second answer is there documentation on that "secure: true" param? Also, I don't think it will solve my problem that handleFetch is blocking the Handle function but I will try it anyway.

and for the second answer is there documentation on that "secure: true" param? Also, I don't think it will solve my problem that handleFetch is blocking the Handle function but I will try it anyway.

There isn´t currently but we are working on better docs. Manually settings the secure should indeed fix your issue. The helpers internally read the host header if secure isn´t set.

FYI, I am also facing the same issue, I does not seem to be breaking anything but is at least polluting the logs.

Also having the same issue. Scenario:

Log in: OK
Go to some page that fetches SB data under RLS using helpers: OK
Go to some page that fetches some SB data as well as from a src\routes\api\some-endpoint\+server.js API endpoint: receiving same error on the server side

For the moment you can also get rid of this error by manually settings the secure cookie option:
import { createClient } from "@supabase/auth-helpers-sveltekit"
import {
	PUBLIC_SUPABASE_ANON_KEY,
	PUBLIC_SUPABASE_URL,
} from "$env/static/public"

export const supabaseClient = createClient(
	PUBLIC_SUPABASE_URL,
	PUBLIC_SUPABASE_ANON_KEY,
	{},
	{
		secure: true
	}
)

This makes my error go away but I can't sign out from the app

Can't replicate this issue. If this is still an issue provide an reproducible example as the one provided is using outdated code.


Implement accessibility areas by distance

Hello,
will it be possible to get accessibility areas calculated by distance in the future too? One could plan trips like me for example for my kids: what children playgrounds do I reach within 5/10/15 km radius?
Best Regards,

Yes, absolutely. It´s the next thing I´ll implement.
BTW, the tool is updated in the official plugin repo, so you can download the latest version.

Thank you for considering this enhancement.

Fixed in new branch


Add doc about redis data only persistence

What this PR does / why we need it:
When changing password the redis.conf is not re-generated if persistence.enabled.

Also, can you take a look at the conflicts? It seems new changes appears in the Chart.yml

I rebased this branch on latest master and resolved conflicts

/lgtm
/ok-to-test
/approve


Unable to create an object of type 'ApplicationDbContext'

on running the command
dotnet ef migrations add "brand_extend" --project ./src/Migrators/Migrators.PostgreSQL/ --context ApplicationDbContext -o Migrations/Application
return error
Unable to create an object of type 'ApplicationDbContext'. For the different patterns supported at design time, see https://go.microsoft.com/fwlink/?linkid=851728
the command provided in documentation
dotnet ef migrations add "brand_extend" --project .././Migrators/Migrators.PostgreSQL/ --context ApplicationDbContext -o Migrations/Application
returns
No project was found in directory '.././Migrators/Migrators.PostgreSQL/'.
is that a known bug
I am trying to use this template for my MVP
Please help me if I am doing something wrong
thanks

from which directory are you running this command from?

It has to be executed from the host directory.
dotnet ef migrations add <CommitMessage> --project .././Migrators/Migrators.<Provider>/ --context ApplicationDbContext -o Migrations/Application


HPACK Dynamic Header Table not RFC Compliant

I'm looking at the function _add_to_header_table(self, header), specifically the section that's evicting entries from the end.  Unless I missed something, this is implemented incorrectly: you initially set header_table_size to 4096 which in the RFC7540 is the initial value for the setting HEADER_TABLE_SIZE. However, eviction from the table only occurs when an addition to the table would result in it's size being greater than MAXIMUM_HEADER_TABLE_SIZE or when the maximum header size is changed.  By default I believe a sender of headers expects no limit on the size unless otherwise specified by the receiver.  It looks like you're needlessly evicting entries from the table and keeping the header table size artificially at or below 4096. I'm not sure how this effects your implementation of HTTP2 in practice.

@jimcarreer Thanks for raising this issue!
I don't believe your reading of the RFC is correct. This is subtle and annoying, so bear with me while I try to explain. :smile:
The HPACK spec, RFC 7541, has the following to say in section 3.2 on this topic:

Protocols that use HPACK determine the maximum size that the encoder is permitted to use for the dynamic table.  In HTTP/2, this value is determined by the SETTINGS_HEADER_TABLE_SIZE setting.
An encoder can choose to use less capacity than this maximum size, but the chosen size MUST stay lower than or equal to the maximum set by the protocol.

In RFC 7540, the HTTP/2 spec, section 6.5.2 says (emphasis mine):

SETTINGS_HEADER_TABLE_SIZE (0x1):  Allows the sender to inform the remote endpoint of the maximum size of the header compression table used to decode header blocks, in octets.  The encoder can select any size equal to or less than this value by using signaling specific to the header compression format inside a header block (see [COMPRESSION]).  The initial value is 4,096 octets.

This leads to the following flow:

A new connection is opened. At this point I don't know what the max table size is, so I have to assume it's 4096, which is how the encoder is initialized.
We do the HTTP/2 preamble, which involves a SETTINGS frame being received from the remote size. If they want to increase the size of the header table, they should send us a value for SETTINGS_HEADER_TABLE_SIZE that says so appropriately. If they do that, we handle it in the HTTP20Connection._update_settings method.

I believe my reading of the spec is right, but I'd like to see if @tatsuhiro-t agrees with me.

Ah I see now you're correct.  I mistook some other MAXIMUM_ setting to be the MAXIMUM_HEADER size for some reason when reading RFC7540.

Easy to do, they aren't necessarily the clearest specs. ;)
Thanks for your input!

For the record, yeah, @Lukasa is correct about the spec.

Thanks @tatsuhiro-t! :cake:


fix: backup destination not found

:tada: This PR is included in version 0.9.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Page error if chart type is stacks

Hi ! I wonder why when I switch chart type to stacks, the chart does not show, the page has an error, as shown in the picture above.
The installation package is installed through npm.  version is as follows.
<EMAIL_ADDRESS>"^8.7.8",
<EMAIL_ADDRESS>"^8.7.8",
"@fluentui/react": "^8.67.2",
<EMAIL_ADDRESS>"^8.5.10",
"@msrvida/sanddance": "^3.2.1",
"@msrvida/sanddance-explorer": "^3.2.0",
"vega": "^5.22.1",
"react": "^16.12.0",

Can you provide the data sample, or other way to repro?

Can you provide the data sample, or other way to repro?

Can you provide the data sample, or other way to repro?

Can you provide the data sample, or other way to repro?

Hi, I used data from sanddance's website, downloaded from this address 'https://microsoft.github.io/SandDance/app/' .
The relevant codes are as follows.
import React, { useEffect, useState } from 'react';
import * as deck from<EMAIL_ADDRESS>import * as layers from<EMAIL_ADDRESS>import * as luma from<EMAIL_ADDRESS>import * as vega from 'vega';
import * as ReactDOM from 'react-dom';
import { Explorer, use } from '@msrvida/sanddance-explorer';
import * as fluentui from '@fluentui/react';
import './sanddance-app.css';
import './sanddance-app-site.css';
import './sanddance-explorer.css';

const Visualization = (props) => {
    let fileSrc = '/download/data?f=demo.csv';

    const [tableData, setTableData] = useState([]);

    const handleData = (dataFile) => {
        let loader = vega.loader();

        function handleRawText(text) {
            let data = vega.read(text, {
                type: dataFile.type,
                parse: 'auto'
            });
            setTableData(data);
        }
        loader.load(dataFile.dataUrl).then(handleRawText);
    }

    useEffect(() => {
        handleData({ dataUrl: fileSrc, type: 'csv' })
    }, []);

    useEffect(() => {
        if (tableData.length > 0) {
            const explorerProps = {
                logoClickUrl: 'javascript:;',
                logoClickTarget: '_self',
                mounted: explorer => {
                    explorer.load(tableData); // 这里传进去的数据格式和官网是一样的
                }
            };
            fluentui.initializeIcons();
            use(fluentui, React, ReactDOM, vega, deck, layers, luma);
            ReactDOM.render(React.createElement(Explorer, explorerProps), document.getElementById('app'));
        }
    }, [tableData])

    return (
        <>

        </>
    )
}

export default Visualization;

Can you also provide the column mappings you used? For example:

Hi, I wonder if it is related to this problem. When entering the page after initialization, the effect of chart type on the left is not selected, but the chart on the right is displayed. Do you know how to fix this problem.

Can you create a git repo so that I can install the entire project?

Can you create a git repo so that I can install the entire project?

https://github.com/Wigithub1201/sanddance-wi.git

Thanks for the repo. You are correct that some of these issues are version related. We currently refer to @fluentui/react ^7.150.0 which in turn only uses react@16.
I have noticed the bug is not with the Stacks layout, but when trying to render a 3D chart. (click the 3D cube icon in the top bar to see the error with any layout.)
When I pin the deck.gl versions to 8.3.7, it seems to work. See my fork: https://github.com/danmarshall/sanddance-wi
https://github.com/microsoft/SandDance/blob/master/packages/sanddance-explorer/README.md#installation
Sorry for the inconvenience. We will be upgrading react & fluentui in our next major version coming soon.

Thanks for the repo. You are correct that some of these issues are version related. We currently refer to @fluentui/react ^7.150.0 which in turn only uses react@16.
I have noticed the bug is not with the Stacks layout, but when trying to render a 3D chart. (click the 3D cube icon in the top bar to see the error with any layout.)
When I pin the deck.gl versions to 8.3.7, it seems to work. See my fork: https://github.com/danmarshall/sanddance-wi
https://github.com/microsoft/SandDance/blob/master/packages/sanddance-explorer/README.md#installation
Sorry for the inconvenience. We will be upgrading react & fluentui in our next major version coming soon.

ok！Thank you for your help!


some confusion

In the Blip2VicunaInstruct_MALMM class, the 235 and 237 lines of code did not calculate the image embeds in advance. Did you miss it by mistake?

Another question:I didn't understand how query memory bank is reflected in the code. I noticed that there is the apply_memory_bank function, but query_memory_bank is not defined in the code like self.visual_memory_bank. Is it possible to achieve memory bank-like results just through the attention layer?Thank you very much if you can take the time to answer my questions.

Thanks for pointing out this bug. I fixed this error and updated it in the latest commit.
For the query memory bank, you can check the detailed code here https://github.com/boheumd/MA-LMM/blob/main/lavis/models/blip2_models/blip2.py#L166


CollectionProperty validation hides the underlying property name for a task

https://github.com/gradle/gradle/blob/e998de55cd247c1dc3ce706ec7d7f551b7aad8ce/subprojects/core/src/main/java/org/gradle/api/internal/tasks/properties/bean/AbstractNestedRuntimeBeanNode.java#L163
When we try to get the value from a CollectionProperty, we perform validation, but without any context (name of the property or task).  This makes configuration to fail with a cryptic failure when a list of Strings has an Integer in it (as an example):

Caused by: java.lang.IllegalArgumentException: Cannot get the value of a property of type java.util.List with element type java.lang.String as the source value contains an element of type java.lang.Integer.

There's not an easy way to figure out which property has this problem. I think this could effect other nested properties that throw runtime exceptions when getting a property's value.  The context is available, so we should be able to add it.

@big-guy is this still an issue?

interface MyExt {
    @Input abstract ListProperty<String> getStrings()
}

abstract class MyTask extends DefaultTask {
    @Nested
    abstract MyExt getMyExt()

    @TaskAction
    void doIt() {
        System.out.println(myExt.strings)
    }
}

task myTask(type: MyTask) {
    myExt.strings.add("1")
    myExt.strings.add(1)
}

This produces a nice message now:
Execution failed for task ':myTask'.
> Failed to calculate the value of task ':myTask' property 'myExt.strings'.
   > Cannot get the value of a property of type java.util.List with element type java.lang.String as the source value contains an element of type java.lang.Integer.

@big-guy this got closed as completed without milestone so the issue is going back to our triage queue. Could you take care of finding out when it was fixed and assign a milestone?
Also the team-triage label should be removed.


[SUPPORT] Insert and Delete in a Single Operation.

Hello!
I would like to know if it is possible to perform an Insert and Delete in a single Operation.
I've noticed that is possible if im using Upsert with _hoodie_is_deleted column, but in my case, my insert operation must allow duplicateRecords.
Thank you very much!

@lucianondolenc I dont think that is possible. as if we use 'upsert' operation type, then it won't allow dups and maintain uniqueness and if we use operation type 'insert' then it won't value the '_hoodie_is_deleted' field.


Not able to apply to the group of light

I am trying to customize the group of light so that each light has the following feature. But not able to..
group.all_lights:
custom_ui_state_card: state-card-custom-ui
show_last_changed: true
state_card_mode: break-slider-toggle
stretch_slider: true
theme: happy
slider_theme:
max: 200
min: 10
off_when_min: false
pin: true
report_when_not_changed: false
group.all_devices:
show_last_changed: true
This above code is from the customize.yaml file. Am I doing something wrong?
If I do it for one entiity, it work fines

Your yaml is not formatted. Are you trying to apply CustomUI to all lights?
In that case use:
homeassistant:
  customize_glob:
    light.*:
      custom_ui_state_card: state-card-custom-ui
      ...

What you did applies the settings to the group itself.

Following is the configuration.yaml file
homeassistant:
Name of the location where Home Assistant is running
name: Home
Location required to calculate the time the sun rises and sets
Customization file
customize_glob:
".":
custom_ui_state_card: state-card-custom-ui
customize: !include customize.yaml
------------------------- Customize.yaml file:
sensor.linear_wapirz1_motion_sensor_temperature:
friendly_name: Sala Temperature
show_last_changed: true
custom_ui_state_card: state-card-custom-ui
light.cree_connected_a19_60w_equivalent_fe03e539_10:
friendly_name: Kitchen Light
light.osram_lightify_a19_rgbw_00a42028_3:
friendly_name: Sala Light
light.cree_connected_a19_60w_equivalent_fe03e82d_10:
friendly_name: Dinner Light
light.cree_connected_a19_60w_equivalent_fe03e7e9_10:
friendly_name: Passage Light
group.all_lights:
custom_ui_state_card: state-card-custom-ui
show_last_changed: true
state_card_mode: break-slider-toggle
stretch_slider: true
theme: happy
slider_theme:
max: 200
min: 10
off_when_min: false
pin: true
report_when_not_changed: false
group.all_devices:
show_last_changed: true
group.scenes: {}

group.all_lights:
  custom_ui_state_card: state-card-custom-ui
  show_last_changed: true
  state_card_mode: break-slider-toggle
  stretch_slider: true
  theme: happy
  slider_theme:
    max: 200
    min: 10
    off_when_min: false
    pin: true
    report_when_not_changed: false

Doesn't do anything useful. It applies configuration to the all_lights group, while the configuration should be applied to the lights themselves.
Either one-by-one or via customize_glob

Okay... Thank you !!


Add SetTraceLogCallback to enable users setting custom logging

This is the PR to address https://github.com/raysan5/raylib/issues/595
The number of changes needed in utils.c are quite minimum. The only tricky part is that the callback is defined as:
typedef void (*TraceLogCallback)(int msgType, const char *text, void *args);
where args is void* instead of va_list in order to avoid having to include stdargs.h since I saw that raylib.h did not previously include any other header and I figured out you wouldn't want to start including one now.
I also added an example called core_custom_logging to show users how it may be used. This is what the logger in the example looks like:
[2018-07-26 10:34:47] [INFO] : Initializing raylib 2.0
[2018-07-26 10:34:47] [INFO] : Display device initialized successfully
[2018-07-26 10:34:47] [INFO] : Display size: 1920 x 1080
[2018-07-26 10:34:47] [INFO] : Render size: 800 x 450
[2018-07-26 10:34:47] [INFO] : Screen size: 800 x 450
[2018-07-26 10:34:47] [INFO] : Viewport offsets: 0, 0
[2018-07-26 10:34:47] [INFO] : GPU: Vendor:   ATI Technologies Inc.
[2018-07-26 10:34:47] [INFO] : GPU: Renderer: AMD Radeon Pro 555 OpenGL Engine
[2018-07-26 10:34:47] [INFO] : GPU: Version:  4.1 ATI-1.68.20
[2018-07-26 10:34:47] [INFO] : GPU: GLSL:     4.10
[2018-07-26 10:34:47] [INFO] : Number of supported extensions: 46

Feel free to provide any feedback 😉

where args is void* instead of va_list in order to avoid having to include stdargs.h since I saw that raylib.h did not previously include any other header and I figured out you wouldn't want to start including one now.

I would be in favor of making it va_list * and including <stdarg.h> as it's just a standard C89 header and type safety is always good. Thoughts @raysan5?
A bit of bike shedding: SetTraceLogger has a nice ring to it.

I checked with gcc -E to how much it would increase the header and at least in macOS the overhead is minimum:
# 1 "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/9.1.0/include/stdarg.h" 1 3 4
# 30 "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/9.1.0/include/stdarg.h" 3 4
typedef __builtin_va_list va_list;
# 48 "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/9.1.0/include/stdarg.h" 3 4
typedef __builtin_va_list __gnuc_va_list;

I'd also bet on safety and add it, but since it was the first external header added I was quite reluctant to include it at first. It's up to you @raysan5

Well, as you know I'm a bit reluctant to adding headers to raylib.h... is it possible to do something like:
typedef void (*TraceLogCallback)(int msgType, const char *text, ...);

If there is no other option I can consider adding it...

I don't see any way to use typedef void (*TraceLogCallback)(int msgType, const char *text, ...); that would make it work. Once you have already created a va_list for your extra arguments, you cannot forward all of them to another function with .... You need to send the va_list. As far as I understand, that's precisely the reasoning behind having the v flavours for vprintf and the rest.
In my opinion, if we had any other header that already includes some overhead to raylib.h, I'd go with including stdargs.h for sately. But since there's none and this is anyway probably intended for users who know what they're doing, I don't thing casting an opaque argument to va_list* is such a big issue.

One could define TraceLog as a global function pointer, which is by default initialized to the normal traceStdout function, but can be overridden by the user...

Ok, let's include stdargs.h...

Merged. Thanks!


Implement Back-Ups Support

Allow for a periodic job to run which will pull the current data in all collections and save them as a specific version. This would allow us to pull previous versions of the data in the API. It would help prevent data loss.
IDEA:
Set up a quartz job to run every week.
The job will pull from all collections and put each one in its own file.
Rename the file to include the version(v1.2.1_characters_jsrf)
Create a new mongo database called "JSR-API-BACKUPS"
New collection: Event(each record represents an occurrence of a backup, contains the EventDataId)
New collection: EventData(the actual data from the backup)
When the quartz job fires off and creates the file, it creates a record in the 'Event' collection with metadata about the pull.
It also uploads the json contents of the file to the 'EventData' collection.

This is blocked until asset-service finished implementing uploading a file to drive. Will link the PR here soon.


Add support for SPF validation

just fyi: the CI appeared to get stunned by a locking issue around its default sqlite database. I switched it to postgres, which reset its contents, so the check status shown here in github will be wonky until the next push to this pr.

Rebased.


v5 deploy

#4301  👈
main

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

Join @jnsdls and the rest of your teammates on  Graphite


Feature: Add new layer - FrameBuffer

New layer: FrameBuffer
Features

The layer's expression is same as the rendering result of chosen layers.

How to use

You can get a same rendering result without merging layers.
So this may be used as mirror, shadow, glow or other usages.

I need to think a little more about the specifications


Potential use cases

A brainstorm of some potential usecases. Not totally sure whether any of these are duplicates. Where should I post these?

E-commerce (!!). People always want to know the physical size of the book/phone/watch/postcard/shoe/pen/whatever they are ordering. What better way than to just show it on the website?
Ruler webapp for smartphones. Kids would use this.
Drawing / tracing apps for the iPad or other tablets (artists need to control the pysical sizing of drawings)
Photo development apps? For instance, you could match the sizing of 4"x6" prints, or 35mm film negatives
Post-It note templates – imagine a wall of monitors with columns for Post-It notes. This could very much be a thing at companies like IBM who do "Design Thinking" corporate workshops, along with hundreds of Post-It notes.

I had the e-commerce one in that previous shorter piece :smile::

Make size matching simple. E.g. for online shopping, decide the correct size of gloves by matching the users hand on the screen directly.

also:

Give designers a correct preview impression of a website at a specific screen size. E.g. for a specific phone model.

From the  article source, but unstructured (wrong place to put anyways) and not all thought through:
    more use cases:
      - print proofing/designer preview. We can help reducing paper
        wastage!
      - Effective web proofing by correctly scaling to actual
        e.g. phone-screen sizes.
      - optical size proofing for type design
      - getting an impression what the default viewing distance is
        supposed to be on certain devices, as it is not easy to to
        do on the spot.

      - touch device UI must be touched with physical fingers,
        hence controls designed with physical sizes are best practice.

      - the web platform usage diversifies as it is becoming more ubiquitous.

      - the web platform is becoming more ubiquitous, not all use cases
        fit well into the "reference pixel" approach. Sometimes
        target screen and viewing distance could be very well known
        and hence a direct way of designing for these target could be
        desirable. In web, the flexibility of the CSS-unit approach
        requires that there's a scroll somewhere. Paged media can't
        afford this. Where a user can't scroll, e.g. a digital poster
        on a screen, that is not interactive, pages become important
        and alse that the designer can control the viewing distance
        assumptions. <!-- Clames like this need backup! it's also just
        not a good argument yet and may have false statements, definitely
        not all strong points.
        -->
      - We can control for different device sizes even when designing
        with real world units, though a support in media-queries would
        help a lot.
      - hi-res screens are so good now, we can anchor to physical units
        and won't get blurry lines.

      - what about e.g. font-sizes for legal print, are there absolute
        requirements? "legible" is one of them, but fonts becoming regularly
        smaller than e.g. 12 pt because the device defaults to 20 inches
        viewing distance instead of 28 inches may be unfortunate.


Analyzer confused by nonliterals that look like _xALPHA etc (eg _vCODE)

Nonliteral names like _vCODE may be mistaken for special variables.
They cause problems for the analyzer:
1 - if _vCODE starts a text, the text will not print out correctly.
2 - the text will be regarded as "not a string type".
3 - Even str(var) cannot force to text type.
@ddehilster

Don't know if I have the full handle on this, but nonliterals sometimes do, sometimes don't, cause a bug report in an analyzer when they are at the very beginning of a phrase.

@amnonma, I believe this goes in the VSCode-NLP repository if it is a display problem. Please move if it is.

No, this is the same as N("$text") or "$text" not printing correctly.  I
could remove it.
On Thu, Apr 27, 2023 at 12:31 PM David de Hilster @.***>
wrote:

@amnonma https://github.com/amnonma, I believe this goes in the
VSCode-NLP repository if it is a display problem. Please move if it is.
—
Reply to this email directly, view it on GitHub
https://github.com/VisualText/nlp-engine/issues/404#issuecomment-1526251850,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACFWQOIQBEMVCUETK5HMRL3XDLCPVANCNFSM6AAAAAAXKMHSCI
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Amnon Meyers
CTO
Conceptual Systems LLC (California)
web: conceptualsystems.biz
mobile:<PHONE_NUMBER>
(landline:<PHONE_NUMBER>)


How to show scale value if all legends are selected?

Hi Guys,
I am using angular chart and facing one issue. The issue is that when I select all the legend my scale values are getting hidden for . So I want to show the scale value even if all legends are selected.
For Plunker Demo : http://plnkr.co/edit/OXpRBqngdimzxDp1t7Qh?p=preview

The only way I know is to explicitly set min and max of your scale (plnkr) but you will need to precalculate those values before creating/updating your chart.

Yes that is working but in my case I don't know the max range, min will be always zero but not sure about max range.

You could use suggestedMax, which extends the max if the data are beyond the suggested value (plnkr)


[#6] Rename repo to angular2-redux-starter

Rename repo
Update readme
Update package.json

Thanks Evan.  :shipit:


edeustace.com repository is down

It looks like edeustace.com has expired. How can we depend on assets-loader for now?

Sorry - the domain lapsed - should be back up shortly.

Thanks, looking forward to it :)

Should be up now. Closing..

Now I am getting 403 Forbidden.
wget http://edeustace.com/repository/releases/com/ee/assets-loader_2.10/0.12.3/assets-loader_2.10-0.12.3.pom
--2015-01-06 09:15:18--  http://edeustace.com/repository/releases/com/ee/assets-loader_2.10/0.12.3/assets-loader_2.10-0.12.3.pom
Resolving edeustace.com (edeustace.com)... <IP_ADDRESS>
Connecting to edeustace.com (edeustace.com)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2015-01-06 09:15:18 ERROR 403: Forbidden.

Will investigate shortly..
On Tuesday, January 6, 2015, René Grüner Vangsgaard <
<EMAIL_ADDRESS>wrote:

Now I am getting 403 Forbidden.
wget http://edeustace.com/repository/releases/com/ee/assets-loader_2.10/0.12.3/assets-loader_2.10-0.12.3.pom
--2015-01-06 http://edeustace.com/repository/releases/com/ee/assets-loader_2.10/0.12.3/assets-loader_2.10-0.12.3.pom--2015-01-06 09:15:18--  http://edeustace.com/repository/releases/com/ee/assets-loader_2.10/0.12.3/assets-loader_2.10-0.12.3.pom
Resolving edeustace.com (edeustace.com)... <IP_ADDRESS>
Connecting to edeustace.com (edeustace.com)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2015-01-06 09:15:18 ERROR 403: Forbidden.
—
Reply to this email directly or view it on GitHub
https://github.com/edeustace/assets-loader/issues/40#issuecomment-68837704
.

I'm getting a 200 - can you try again?
curl -IL http://edeustace.com/repository/releases/com/ee/assets-loader_2.10/0.12.3/assets-loader_2.10-0.12.3.pom
HTTP/1.1 200 OK
Date: Tue, 06 Jan 2015 12:17:51 GMT
Server: Apache/2.2.14 (Ubuntu)
Last-Modified: Sun, 08 Jun 2014 18:55:52 GMT
ETag: "100c25-fbb-4fb57a4c5de00"
Accept-Ranges: bytes
Content-Length: 4027
Content-Type: text/plain

curl -IL http://edeustace.com/repository/releases/com/ee/assets-loader_2.10/0.12.3/assets-loader_2.10-0.12.3.pom
HTTP/1.1 403 Forbidden
Server: nginx
Date: Tue, 06 Jan 2015 13:51:09 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive

Weird - Let my try it from a few different machines see if there's a whitelist

It works for me now. Thank you.


Better extmark on the same line handling

Currently:
The virtual text is added after the image, so nvim renders the image padding first, and then the text. But we're assuming that the image should be below all of the extmarks that are on the same line. This is something that I missed in my last PR

After this PR:
Image renders with it's extmark b/c we break out of a loop when we find the images own extmark

Lol, I went to make the issue and then forgot, and then thought this was the PR


'Photo' object has no attribute 'image_path'

Traceback (most recent call last):
File "/usr/lib64/python3.4/threading.py", line 920, in _bootstrap_inner
self.run()
File "/usr/lib64/python3.4/threading.py", line 868, in run
self._target(*self._args, **self._kwargs)
File "/home/cameron/Workspace/photoshell/photoshell/views/photo_import.py", line 132, in do_import
self._window.selection
File "/home/cameron/Workspace/photoshell/photoshell/library.py", line 68, in update
image_path = current.image_path
AttributeError: 'Photo' object has no attribute 'image_path'

This happens on import sometimes. Not sure why yet.


feat(contracts): new registry (V1)

Commitment registry with external collateral
Closes #196
Closes #36
Closes #244
Closes #273
Registration procedure

Validator registers in BoltValidators. There is a registerValidatorUnsafe method that skips all verifications (BLS signature check and SSZ validator existence check). This function will be useful to test and until Pectra will be live on public testnets. We can also start testing with the precompile on Pectra EF devnets for now.
Operators register in BoltManager via registerSymbioticOperator()
Operators do all of their Symbiotic-related authorization steps on the Vaults they want to operate on
Vaults register in BoltManager via registerSymbioticVault() (currently no check on collateral asset used)

The BoltManager contract allows read access into the current stake of any operator in the network
at any given time, for any asset:
function getSymbioticOperatorStakeAt(
		address operator,   // the operator for which to get the stake
        address collateral, // the collateral asset address to query for
        uint48 timestamp    // the timestamp at which the query is made
    ) external view returns (uint256);

It also allows to query if an operator is authorized to emit commitments for a specific validator:
function isSymbioticOperatorAuthorizedForValidator(
        address operator,
        bytes32 pubkeyHash
    ) external view returns (bool);

The actual staking, unstaking, and slashing downstream logics are left to Symbiotic for now.
Diagrams

Missing & TODO

[x] should we gate the collateral assets behind a whitelist?
[x] ability to verify aggregated bls12_381 signature for batch registration
[x] ability for Validators to pause or change the currently authorized Operator

Meta

reference discussion: #95
part of #196

Summary by CodeRabbit

New Features

Introduced a Continuous Integration (CI) workflow for automated testing of smart contracts.
Added new mock contracts for testing collateralized debt positions and ERC20 tokens.
Enhanced documentation with a structured Table of Contents and detailed integration guides.

Bug Fixes

Improved error handling for non-existent operators and validators in the testing framework.

Documentation

Expanded README with comprehensive explanations of the Bolt ecosystem components and security considerations.

Tests

Implemented a robust testing suite for BoltManager and BoltValidators, validating key functionalities and interactions.

Ready for a first round of review. In scope:
Contracts:

BoltManager.sol
BoltValidators.sol
Imported libraries and interfaces

Flows:

registering as a validator (tested)
opting in via Symbiotic (tested)
reading the active stake (tested)
slashing flow (not tested)

@coderabbitai review

Let's go!! congratss


[Go SDK] Fix Off by One error splitting DataSource

Fix subtle Off By One error when splitting from a DataSource, likely caused by using an ambiguous count, rather than an index. This change renames the ambiguous variable and improves the comments around splitting to clarify that the returned split is the first element of the residual (and not the last element of the primary).
The fix is starting the bundle's index from -1 to mark a "before processing has begun", and then incrementing normally from there, so that the first one value returns 0 index.
Also resolves the follow on ambiguity of the OutputElementCount when providing bundle progress. This value is the number of "completely processed elements", which tracks the index. eg. When processing index 0 (the first element), 0 elements have been completely processed. When processing index 5, 5 elements have been completely processed, and so on.
After a bundle is complete, in both the split and unsplit cases, an additional increment occurs, making the index accurately reflect the count at the end of a bundle. In the case of splitting, the increment func is how the bundle processing exits, while for unsplit cases, it's the ordinary EOF of the data which indicates no further elements exist.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @robertwb @youngoli

Run Go Postcommit


Simplify Version command

closes #446

@itsksaurabh Thank you for the contribution!

👍

@vgarvardt Thanks for your approval. Glad to be a part of this awesome project!

+1

+1


Define mapping of AnonCreds v2 into W3C Format Verifiable Credential and Verifiable Presentation format

Define and implement the formatting of AnonCreds v2 credentials and presentation into W3C Verifiable Credentials Data Model Standard format.
In doing that, consider adding to the data model the additional fields of the VC Data Model (e.g., issuance_date) as fields included in AnonCreds.

In implementing this, consider:

automating the flattening of complex JSON (beyond the simple attribute list in AnonCreds v1) to enable support for nested JSON structures.
extending the flattening to include support for arrays in AnonCreds v2 credentials. Such support would have to include defining how to selectively disclose arrays of data, such as permitting disclosing all rows of an array, but only select items per row. The challenge in such support is how to request the data.

This part of the work gets into the always "interesting" area of canonicalization schemes. For example, should JSON-LD canonicalization be used, and if so, how?

Hi @swcurran, can I work on this issue if noone is assigned to it ? I have used this repo for some personal projects, and I would love to contribute to the issues !

Feel free to submit a pull request to the repo — contributions are welcome.  In this case, the work would be a markdown document defining the proposal.  Or perhaps just comments on this issue with the proposal.  There would not be any coding at this point.
If you do a PR, please keep in mind to sign off on all commits for DCO — DCO - Developer Certificate of Origin - https://github.com/apps/dco.


Detect malformed configuration variable keys before up/deploy

The documentation for dynamic configuration variables specifies that Configuration keys may only contain lowercase letters and underscores between letters.
Currently, if i deploy an application with a malformed configuration key (e.g. LOG_LEVEL) my application will serve 500 and my logs will contain angry shouting about what the proper format is for keys.
I think it would be ideal if we somehow validate configuration keys pre-deploy/up or ask the doctor to do it.

Yes, it looks like Spin validates the names only at run time (i.e. this happens locally not just in cloud).  I am not sure why - I think this has come up before but can't remember the outcome.  I'll take a look - thanks for flagging this!


hash_to_G2 input message size: Why bytes32?

Currently the specs mention that "message" should be bytes32:
def hash_to_G2(message: bytes32, domain: uint64) -> [uint384]:
    # Initial candidate x coordinate
    x_re = int.from_bytes(hash(message + bytes8(domain) + b'\x01'), 'big')
    x_im = int.from_bytes(hash(message + bytes8(domain) + b'\x02'), 'big')
    x_coordinate = Fq2([x_re, x_im])  # x = x_re + i * x_im

    # Test candidate y coordinates until a one is found
    while 1:
        y_coordinate_squared = x_coordinate ** 3 + Fq2([4, 4])  # The curve is y^2 = x^3 + 4(i + 1)
        y_coordinate = modular_squareroot(y_coordinate_squared)
        if y_coordinate is not None:  # Check if quadratic residue found
            return multiply_in_G2((x_coordinate, y_coordinate), G2_cofactor)
        x_coordinate += Fq2([1, 0])  # Add 1 and try again

This prevents using bigger message as input, for example the third message that was proposed for testing:
MESSAGES = [
    b'message',
    b'Bigger message',
    b'Very .............. long ............. message .... with entropy:<PHONE_NUMBER>-beacon-chain'
]

Assuming there are situations where longer messages are needed, we would need to hash once before passing to hash_to_G2. hash_to_G2 will also re-hash inside.
Only impact is type signature.

Shouldn't this parameter be treated as a message hash? Maybe rename it to message_hash for clarity?

the thing that is commonly used in that place across signature algos is some hash of the message -- i would support a renaming if it had broad support -- otherwise this is the kind of thing where if you work in the domain you know what it means from context; i agree it is not perfectly precise :)

It's also a minor win to force constant message size to reduce variability of runtime ofhash_to_G2.
+1 message_hash

Agree on message_hash. Another thing to keep in mind is that the hash that gets passed in here is sometimes a simple hash of a byte array, but it can also be an SSZ tree hash. So using message hash here is the right level of abstraction.

Fixed by https://github.com/ethereum/eth2.0-specs/commit/d3ce995cae1722a7f1c7266794767e77392db032


Add documentation for s/// operator

The =head and =item markers may need some TLC.

Note that neither the colon C<:> nor balancing delimiters such as C<{}> or C<()> can be delimiters.

Hm, well. What about this:
my $x = ‘foo’;
$x ~~ s{oo} = ‘öö’;
say $x

It's a little bit different thing but I think that it should be mentioned (instead of saying that you can't use { }.

I wasn't aware that form existed until I read the synopsis, I'll make a PR for that later.


Feature/string attribute details

Description of changes:

Adds kerning, strikethrough and underline for string attribute.
Adds text transform (uppercase, lowercase)
Add support for fixed and auto sized text fields.
Support for line height

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dbanksdesign I added a few more things. Hope it's ok to do it in the same PR.

@dbanksdesign feel free to more this guy in :-)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New features in Hybrid Topology Maker

Add a few new features for the hybrid topology maker which allows to handle more complicated cases, such as having a different substructure match between every ligand, etc.
Code also works just as before if there is a single MCS between all ligands.

Codecov Report

Merging #89 (77bed22) into main (b6d6a8a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 77bed22 differs from pull request most recent head 53ea255. Consider uploading reports for the commit 53ea255 to get more accurate results

@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   15.72%   15.72%
=======================================
  Files          51       51
  Lines        5534     5534
=======================================
  Hits          870      870
  Misses       4664     4664

Flag
Coverage Δ

unittests
15.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Updates the example using foreign field mul

This PR updates the example in pasta_fp_plonk_proof.rs that was disabled in this PR. It uses the updated functions of proof-systems for the new FFMul layout after the revised RFC
Merge after the base branch, so that more files are not added to the diff of that PR.
Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

!ci-build-me


New Button Styles

Use Google Material style buttons: http://www.google.com/design/spec/material-design/introduction.html

rectangular with sharp edges
slight shadow
Uppercase text
On hover, transition colour

Here's an example:
Styles.txt


BACKLOG-22876: Update branch name in release wf

JIRA

https://jira.jahia.org/browse/BACKLOG-22876

I'll merge the PR as the tests were passing before and the only change on this PR affects the release wf


Update README.md

Hi @fommil - Thanks for the PR!
The plugin supports being enabled on all or a subset of the projects and does not require that the root project support dockerComposeUp. For example, you can have a multi-project build.sbt file with 5 projects and you only want dockerComposeUp to be used from one of the sub-projects.
How about something like:
Enable the plugin in build.sbt on the projects (including the root project) you would like to test.

hi @kurtkopchik ... I did that initially but it didn't work, there was no dockerComposeUp command to use :-(
The problem as I see it is that Commands are project-wide whereas a Task could be scoped to a Project. So it only seems to matter to enable it on the root.
I raised #66 on this similar point, maybe you can show me there what I'm doing wrong and it's supported already?

Hi @fommil - Using the multi-project example if I comment out enablePlugins(DockerComposePlugin) from the root level project but enable it on the sub-projects only I can execute dockerComposeUp from either of the sample sub-projects but not from the root itself which is the behavior I was describing.

> projects
[info] In file:/Users/kurtkopchik/Source/sbt-docker-compose/examples/multi-project/
[info] 	 * multi-project
[info] 	   sample1
[info] 	   sample2
> project multi-project
[info] Set current project to multi-project (in build file:/Users/kurtkopchik/Source/sbt-docker-compose/examples/multi-project/)
> dockerC
{invalid input}    <--- Since the plugin is not enabled on the 'root' the commands are not available.
> project sample1
[info] Set current project to sample1 (in build file:/Users/kurtkopchik/Source/sbt-docker-compose/examples/multi-project/)
> dockerComposeUp  <-- However, the dockerComposeUp commands are available on the sub-projects that have explicitly enabled it.
Building a new Docker image.
...

Are you seeing different behavior if you try this?

interesting, I didn't know Command worked that way. It doesn't work with sample1/dockerComposeUp which is (the equivalent of) what I was trying.

dockerComposeUp is a Command and not a Task which is why I believe the syntax you used isn't quite equivalent. From the interactive shell you would have to run:
project sample1
dockerComposeUp

If you need to run it from a build system (sbt on the command line) this style of syntax will work:
sbt "project sample1" dockerComposeUp

is there any chance you could make it a Task? Commands should only be as a last resort.


MPU operations wrapped in CompletionException

Problem:
Related to https://github.com/aws/amazon-s3-encryption-client-java/issues/160 , abort MPU operation is still wrapped in a CompletionException.  Trying to abort a MPU without an invalid uploadID gives java.util.concurrent.CompletionException: software.amazon.awssdk.services.s3.model.NoSuchUploadException: The specified upload does not exist.

Addressed in https://github.com/aws/amazon-s3-encryption-client-java/pull/174
Released in https://github.com/aws/amazon-s3-encryption-client-java/releases/tag/v3.1.0


"[IO::HandlerBinaryDataArray] Unknown binary data type." when loading mzML file

I am trying to use the MSnbase R module to analyze an MRM dataset, however I obtain an error when loading the mzML file (converted with default settings from a Sciex wiff file using MSConvert).
I already opened an issue at MSnbase (https://github.com/lgatto/MSnbase/issues/517), however since the error message results from the pwiz library that MSnbase uses to load the file, I thought it's better to open an issue here.
The error I obtain is: Error in pwizModule$open(filename): [IO::HandlerBinaryDataArray] Unknown binary data type.
I attached the mzML file: DataBlank-Test_Blank.mzML.zip
What could be the cause for this error?

Replied at MSnbase repo.


set common env and reduce the kube context switch.

This PR tries to enhance the document:

set some common environment variables at the beginning of the whole guideline.
try to reduce the kube context switch, for example, clusteradm support --context flag, so we can use that to quickly refer to the expected kube context.
reduce duplicated environment variable definition, for example, MANAGED_CLUSTER_NAME can be exported after the cluster is created by the kind command and then it will be reused throughout the guideline.
fix typo.

Signed-off-by: morvencao<EMAIL_ADDRESS>

Thank you for the PR. I will need to at least run it once myself to verify the steps.

@mikeshng Another look? I rebased code changes.

@morvencao sorry for the delay. I will get to this today.

/approve
will lgtm in today if I don't hear some feedback from Dominique or Qiu Jian

I am ok with all the changes but have some concerns for the quick-start ones.
@qiujian16 @itdove could you please share your thoughts? Should we update clusteradm outputs with the --context flag before making the suggested change here?

--context could be a global flag similar as kubectl so you could have clusteradm options to know all the global flags.

/lgtm
After verifying that clusteradm join --context ${CTX_MANAGED_CLUSTER} --hub-token ... works fine.


[Feature Request] Python interface to access DESCRIBE TABLE EXTENDED output

Feature request
Overview
You can query managed Delta tables, external Delta tables, and views with DESCRIBE TABLE EXTENDED to access detailed table information.  It'd be nice if this information was easily accessible via the Python API.
Motivation
This will make it a lot easier for Python devs to query the information contained in DESCRIBE TABLE EXTENDED.  Suppose you have 10 external Delta tables and would like to iterate over the list and build another list of all the paths where they store data.  A Python interface could make this a lot easier to code.
Further details
Here's the output of DESCRIBE TABLE EXTENDED for managed Delta tables and external Delta tables.
Managed tables
columns = ["movie", "release_date"]
data = [("The Godfather", 1972), ("Detective Pikachu", 2019), ("Donny Darko", 2001)]
rdd = spark.sparkContext.parallelize(data)
df = rdd.toDF(columns)

df.write.format("delta").saveAsTable("some_managed_table")

spark.sql("DESCRIBE TABLE EXTENDED some_managed_table").show(truncate=False)

+----------------------------+---------------------------------------------------+
|col_name                    |data_type                                          |
+----------------------------+---------------------------------------------------+
|movie                       |string                                             |
|release_date                |bigint                                             |
|                            |                                                   |
|# Partitioning              |                                                   |
|Not partitioned             |                                                   |
|                            |                                                   |
|# Detailed Table Information|                                                   |
|Name                        |default.some_managed_table                         |
|Location                    |file:/Users/…/spark-warehouse/some_managed_table   |
|Provider                    |delta                                              |
|Table Properties            |[delta.minReaderVersion=1,delta.minWriterVersion=2]|
+----------------------------+---------------------------------------------------+

External tables
df.write.format("delta").option("path", "tmp/some_external_table").saveAsTable(
    "default.my_external_table"
)

spark.sql("DESCRIBE TABLE EXTENDED my_external_table").show(truncate=False)

+----------------------------+------------------------------------------------------+
|col_name                    |data_type                                             |
+----------------------------+------------------------------------------------------+
|movie                       |string                                                |
|release_date                |bigint                                                |
|                            |                                                      |
|# Partitioning              |                                                      |
|Not partitioned             |                                                      |
|                            |                                                      |
|# Detailed Table Information|                                                      |
|Name                        |default.my_external_table                             |
|Location                    |file:/Users/…/spark-warehouse/tmp/some_external_table |
|Provider                    |delta                                                 |
|External                    |true                                                  |
|Table Properties            |[delta.minReaderVersion=1,delta.minWriterVersion=2]   |
+----------------------------+------------------------------------------------------+

Possible interface
This could be a nice interface:
dt = DeltaTable.forName(spark, "my_external_table")
dt.describeTable()

That could return a dictionary like {"isExternal": True, "name": "default.my_external_table", "location": "file:/Users/…/spark-warehouse/tmp/some_external_table", ...}.
Willingness to contribute
The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

[ ] Yes. I can contribute this feature independently.
[ ] Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
[X] No. I cannot contribute this feature at this time.

Thanks, will create a Spark issue


chore(docs): add English translation to README

Add a comprehensive English translation to the README file to make the project accessible to non-Polish speakers. This update ensures that all users, regardless of their native language, can understand the project's goals, setup, and usage instructions.

@kubaszpak could you review? 🤖

@kubaszpak nie podmienilem linkow 🤦♂, tutaj fixik 😎


Update source-control.md

@nimoolen : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@sign-off

Thank you for making the update.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add GHA actions for clippy and rustfmt

Signed-off-by: Daniel Egger<EMAIL_ADDRESS>

r? @adamgreig
(rust_highfive has picked a reviewer for you, use r? to override)


Fix interface generation if @inline is present

Hello! I'm familiar with ReScript but it's my first try with OCaml. So if I did something wrong please feel free to correct me.
fix #425

Awesome! 🎉 I'll let @cristianoc comment on the OCaml itself, but the output generated by the test looks great.

I realized that my new function SourceFileExtractor.extractLine isn't needed. So I removed it.

Hello! I'm familiar with ReScript but it's my first try with OCaml. So if I did something wrong please feel free to correct me.
fix #425

That's an impressive first try!

Can you add 2 examples to the test set:
@genType
@inline
let f2 = 10

@genType @inline
let f3 = 10

see what happens

I missed that there can be more than one attribute. Fixed...I hope :)

@cristianoc One more try :)

@cristianoc Thanks a lot for your review! I fixed your comments.


dist_eval.sh is wrong. And multi GPUs evaluation is not working

In the branch:main, use multi GPUs evaluation is meet a bug.
In the dist_eval.sh , it open tools/test.py, but in this branch ,the test.py is not exist.
even i edit to evaluation.py , it not worked.

Hi @roingbu , I strongly suggenst you to try branch 1.x, you can just use dist_test.sh or slurm_test.sh for all model evaluation.

Closing due to inactivity, please reopen if there are any further problems.


[FEAT] Add Giskard ML Testing

Describe the solution you'd like
Support https://www.giskard.ai/products/ml-testing-library
Describe alternatives you've considered
Additional context

Done in #15


Unify the virtual environment recommendations

It would be good to unify the virtual environment recommendation on all of tt-flash, tt-smi and https://docs.tenstorrent.com/tenstorrent/apis-sdks-and-software/software-and-utilities
cc @adifrancescoTT

I'm confused on what the request is here.  Noting that each of the repositories' you've noted, it's README.md is targeted at developers, not end users.  There's not really a way per-se to "unify" the comments on virtual envs, as each repo is going to make a reminder note that you can use a virtual env, and have some basic instructions, but again since the docs are more targeted at developers I'm expecting they likely already have a basic idea of what a venv is, how it works, and may even have strong opinions on which flavor of venv they would prefer to use.
So I guess, is this more a developer facing bug, if so we need this duplicated into the respective repositories, as well as a clearer understanding of what's needed there.
If this is more a user facing bug, most end users should be using https://docs.tenstorrent.com/tenstorrent/add-in-boards-and-cooling-kits/grayskull-tm-e75-e150/software-setup as that's targeted at end users, not specifically developers.


Fix CLI on Windows

I think I was able to fix the CLI not working on Windows. As windows doesn't really have a defined HOME directory, chose to use APPDATA/Roaming instead (lots of apps like Heroku CLI use this), ran a few tests with a example project and was able to get it working, short video walkthrough here:
https://www.loom.com/share/4ce6188c7406406a837a7710d70284d8
Let me know if there needs to be any changes or want a longer demo.
Thanks
UPDATE: updated to use os.UserHomeDir

Tagging Issue #115
Will test and check, but can you DM me on Discord your preferred method of payment or put your crypto pubkey in the PR?

Completed. Thank you!
https://etherscan.io/tx/0x6a172cb78b81a5a0617af4b495d0926a83568ed8bb4b3a823560ae3131aec318


Implement the $split operator

I didn't see any issues mentioning support for $split, but I figured a PR is better than filing an issue.
@pcorpet - Note the potential conflict with #658 in Missing_Features.rst. I don't mind fixing this PR if it's easier to merge that one first.
Let me know if any of the .gitignore entries are a problem.
Thanks!

Side note - it was a bit strange to see all operators tested simultaneously in test__aggregate_string_operations(). Is there a reason for that, like making the tests run faster? If not, I would consider breaking those apart in a future PR.

Can you update test__mongomock also, to make sure the behavior stays the same between pymongo + MongoDb and mongomock?

Done.

Also, I believe you have no test where the split operation references a variable that does not exist:

Added. I almost committed one like that initially, but didn't see other string operations testing the same. I'm glad you pointed that out since it changed the implementation so the KeyError is caught, which in turn fixed a consistency issue I had in test__mongomock. Nice. 😃

All good! Thanks for the quick turnaround. I'm going to merge now.

Thank you! The PR process for this project was quick and easy, and kudos to you for all your efforts making it so.
I look forward to the next release. If there's a pre-release build available somewhere/somehow, I would be interested in pulling that into my workflow.


wrong display on light theme

Light theme:

Dark theme:

In the light mode, font color should be black

I think this should be reopened. For instance exporting to PDF switches the theme to light for a split second and then exports. Having to manually change the typst theme, export, change it back, should not be expected.

No correct display on PDF export should be a new issue (see also #31). I hope the THEME variable in the preamble would resolve your issue though, if not please open a new issue.

The root cause is still that this plugin does not take into consideration what theme obsidian is in and forces the user to manually override it. Changing obsidian-typst to light mode will make the PDF export right, but then i cannot read anything when i write because i write in dark mode.

It does by using the THEME variable in the preamble

You could use it like so:
#set text(if THEME == "light" {
    black
  } else {
    white
})

If this does not work as expected when exporting to PDF then please open a new issue as this is a different problem to this current issue.


JsonConvert.DeserializeObject("True") throws JsonReaderException

Tested with version 12.0.1 The following code throws:
https://deck.net/39d5bbedae2dc79bb76c03cb84d18d01
using System;
using Newtonsoft.Json;

public class Program
{
    public static void Main()
    {
        var result = JsonConvert.DeserializeObject<bool>("True");
        Console.WriteLine("Doesn't throw");
    }
}

Is this intended (and can we reconfigure the deserializer to allow this) or a bug?
And "True".ToLowerInvariant() is not an option.

Thanks for the report. Obviously, this deserialization should be working and I'm surprised we don't have a test for this scenario already. We will investigate and fix the defect.

The overall behavior is corresponding to native Json: https://dotnetfiddle.net/833PS1
The only difference to Bridge, is the exact exception it throws (Newtonsoft.Json.JsonReaderException in native vs Newtonsoft.Json.JsonException in Bridge.

Oh sorry, I just published the issue to the wrong project. I wanted to push that issue out to Newtonsoft, not to deck.net.

If you create the issue in the official newtonsoft repo, please link it here, in case it gets implemented in newtonsoft, we should follow. But I believe having it case-insensitive is achieved with serialization settings, or using custom serializers.


If order of Qs (bullets in docs) is changed or altered sync is messed up

hello again!
i just noticed this quite recent bug.
if i have lets say 8 Qs in bullet form in the google docs, that means i have 8 Anki flashcards. If i alter the order, for example before the 7th bullet i add another NEW Qs then when i sync it says i have 9 new cards, then after a while i hit sync again and now it says i have less new cards.
I think this bug happens when the order is altered, first time it happens. before i used to alter the order, copy paste here and there and everything would be normal, when syncing total cards would stay the same.
now it seems it Adds the cards normally, but if i then hit sync again it removes some of the new cards. Its a loop.
any idea? if u need me to record a video showing this please let me know, its a really annoying bug.
the big issue is that if i add a tag to a new card from a recent sync, if i hit sync again(due to me altering the order) it will be removed then re-added but without the tag.

Hum.
That does sound confusing. I will try and test it later and see if I can reproduce.
If you could make a video it would be really helpful!

I have been having a look at it but was not able to replicate it from the description anyway.
The way it is currently setup anyway i think if you add a tag if would not update the card with a new tag. Are you adding the tag inline or on the line below?

Could not replicate so will close for the time being


docs: add return types to arrow functions

and fix a minor code style

thanks @carusogabriel
I'm merging this, since the failure in the CI is not related


English translation

The amazeui is beautiful!
I want to start using it but I don't speak Chinese.
Do you think eventually there will be a translation?

+1 it is a waste

start studying

Amaze UI docs English translation is online now: http://amazeui.github.io/docs/en/
Big thanks to @hongdp.

:+1:


Is there anyway to reconstruct 3d face from multiple face image(left side face, right side face and front face) by 3DDFA_V2

Is there anyway to reconstruct 3d face from multiple face image(left side face, right side face and front face) by 3DDFA_V2. reconstruct from front face is good, but I want more better, so if I can provide left side face and right side face image, how can I get a more better result. Very thanks.

your idea is multi camera image rebuild 3d face?

@shushanxingzhe @JH95-ai Did you figure out a solution? Thanks


A11y_SQL Azure Data Studio_New Terminal_Keyboard:Tab key or shift+tab does not move to link "https://aka.ms/pscore6" is n

“Check out Accessibility Insights! – Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags: #A11yMAS;#A11yTCS;#A11ySev1;#BM_SQLAzureDataStudio_Oct2020;#SQL Azure Data Studio;#Win10;#FTP;#DesktopApp;#WCAG2.1.1;#Benchmark;#Keyboard;#AINotInScope;#AILimited;
Environment Details:
Application Name: SQL Azure Data Studio
Version 1.22.1 User Setup
Windows Version: Windows10
Repro Steps:

Launch Azure Data Studio Insiders application.
Tab to server drop down and tab again to button new connection press enter key and add the server details.
Tab to view menu item in the menu bar and use down key arrow to select item "terminal"
Use shift+tab to navigate to  https://aka.ms/pscore6

Actual:
On navigating using shift+tab or tab to link https://aka.ms/pscore6 keyboard key tab cannot access it.
Expected:
Tab and shift+tab from the first line of command should move to link https://aka.ms/pscore6
User Impact:
Keyboard users will not be able to access the link.
Attachment:
#12984_A11y_SQL Azure Data Studio_New Terminal_Keyboard.zip

first of all, the feature mentioned in the issue is a command line interface, I don't think command line interface works like a normal UI based application, so closing as by design.

@alanrenmsft  the command line as well need to be accessible the link in it cant be accessed so keyboard users will not be able to click on it and use it
please reopen this issue
#Regressed:02-20-23;

@fsteffi as per our discussion, these are really old bugs, please reopen so that we can reset the SLA status.

logged new bug https://github.com/microsoft/azuredatastudio/issues/22333.
** GitHub Tags**: #closed;


[web] flaky tests on inactive tabs: css transitions, requestAnimationFrame

A few lib/html and co19 tests are testing CSS transitions, and these tests currently timeout or flake on Chrome.
See for example lib/html/transition_event_test: https://dart-current-results.web.app/#/filter=lib/html/transition_event_test
This test passes consistently in FF and Safari, but flakes on dart2js-linux-chrome nearly 90% of the time.
It appears that, like setTimeout, Chrome ignores CSS transitions on background tabs. As a simple repro, you can create a small JS program that:

creates an element with a css transition (like the one in transition_event_test)
uses setTimeout to start the transition after a delay, this gives you time to switch tabs and put it in the background before triggering the CSS transition
use a few additional setTimeout to log JS activity every few seconds.
add a listener for transitionrun, transitionstart, and transitionend events to log when they occur

What I observe is that all the JS timers complete and log data on the console, but the transition events do not trigger until after I reopen the tab and bring it in the foreground.
This leads me to believe we can't run these tests unless:

there a flag similar to what was recently discovered for timers that we can apply here to allow CSS transitions in background tabs
we make sure tabs are always active instead (e.g. open multiple windows, instead of opening multiple tabs?)

@whesse - are any of these possible?
@srujzs - should we just delete these tests?

I'm also seeing a similar behavior with requestAnimationFrame API calls

lib/html/transition_event_test mostly just uses native APIs and the conversion to a Stream. The latter conversion is tested in other places, so I think there isn't much value to testing the APIs that are within that test.
lib/html/request_animation_frame_test is a bit weird. There's one call to _ensureRequestAnimationFrame which does vendor-specific implementation checking, and then replaces requestAnimationFrame with a callback wrapped in a timeout?

lib/html/transition_event_test mostly just uses native APIs and the conversion to a Stream. The latter conversion is tested in other places, so I think there isn't much value to testing the APIs that are within that test.

agree

lib/html/request_animation_frame_test is a bit weird. There's one call to _ensureRequestAnimationFrame which does vendor-specific implementation checking, and then replaces requestAnimationFrame with a callback wrapped in a timeout?

Technically it is checking for whether it is implemented, and if not, it adds a polyfill for this feature. I believe we never hit the case of the polyfill.
Most of the test is doing 1 or 2 calls to requestAnimationFrame and testing whether the callback is called as expected or whether cancelling the request works as expected. All of this is native behavior, and nothing specific about Dart IMO.
FWIW - I just sent out https://dart-review.googlesource.com/c/sdk/+/335030 to start skipping these tests in Chrome for now.


Unable to upgrade/downgrade subscription on android using in_app_purchase

Is there an existing issue for this?

[X] I have searched the existing package issues
[X] I have read the guide to filing a bug

What package does this bug report belong to?
in_app_purchase
What target platforms are you seeing this bug on?
Android
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
in_app_purchase: ^3.1.1
in_app_purchase_android: ^0.3.0+13

Steps to reproduce
I am fetching past purchase details and as mentioned in the documentation I am providing the fetched details to ChangeSubscriptionParam to PurchaseParam with required ProationMode.
Expected results
The subscription should downgrade and upgrade accordingly.
Actual results
The error in console says : Activity finished with resultCode 0 and billing's responseCode: 5.
The playstore sheet shows error : Something went wrong on our end. Please try again
Code sample
Code sample
final platform = iapConnection
            .getPlatformAddition<InAppPurchaseAndroidPlatformAddition>();
        final pastPurchases = await platform.queryPastPurchases();

        GooglePlayPurchaseDetails? oldPurchaseDetails;

        // Assumes 1 or none active purchase.
        for (var purchase in pastPurchases.pastPurchases) {
          oldPurchaseDetails = purchase;
        }

        final purchaseParam = GooglePlayPurchaseParam(
            productDetails: event.productDetails,
            changeSubscriptionParam: oldPurchaseDetails != null
                ? ChangeSubscriptionParam(
                    oldPurchaseDetails: oldPurchaseDetails,
                    prorationMode: ProrationMode.deferred)
                : null);

        await iapConnection.buyNonConsumable(purchaseParam: purchaseParam);

Screenshots or Videos

Screenshots / Video demonstration

[Upload media here]

Logs
Logs
Activity finished with resultCode 0 and billing's responseCode: 5

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.13.5, on macOS 13.2.1 22D68 darwin-arm64, locale en-IN)
    • Flutter version 3.13.5 on channel stable at /Users/samikshagarg/Developer/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 12fccda598 (5 days ago), 2023-09-19 13:56:11 -0700
    • Engine revision bd986c5ed2
    • Dart version 3.1.2
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/samikshagarg/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.82.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.72.0

[✓] Connected device (3 available)
    • sdk gphone arm64 (mobile) • emulator-5554 • android-arm64  • Android 11 (API 30)
      (emulator)
    • macOS (desktop)           • macos         • darwin-arm64   • macOS 13.2.1 22D68
      darwin-arm64
    • Chrome (web)              • chrome        • web-javascript • Google Chrome
      116.0.5845.187

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Hi @Samiksha-Garg. Thanks for filing this. From the logs, the error message seems to be with  Invalid arguments being provided to the API, you might want to read up more on this here to see if it helps.

Hey @dam-ease, Purchasing a new subscription seems to work fine if I just don't try to upgrade/downgrade any existing subscriptions i.e
final purchaseParam = GooglePlayPurchaseParam(
            productDetails: event.productDetails);

        await iapConnection.buyNonConsumable(purchaseParam: purchaseParam);

seems to work fine. Providing ChangeSubscriptionParam makes all the difference. I don't know what I am doing wrong and what different change I need to do for this.

Hi @Samiksha-Garg. Thanks for your response.

Providing ChangeSubscriptionParam makes all the difference

Can you provide more information on this, please?

I just mean that the error comes up when I provide ChangeSubcriptionParam to the GooglePurchaseParam, without providing it the purchase of subscription takes place successfully. But I want to upgrade/downgrade any existing subscription. @dam-ease

Hey, I figured out the reason for my error. So I was trying subscription model in India and has 3 subscription model set up however 2 of them were priced above 5000 because of which they were being treated as prepaid plan (India's Subscription Rules). And according to documentation When upgrading, downgrading to a prepaid plan from auto-renewing plan, the only allowed proration mode is IMMEDIATE_AND_CHARGE_FULL_PRICE and I was aiming for DEFERED proration mode, hence the error.


How to replicate paper results?

Attempting to retrain the model with MR=0.0 results to significantly lower performance (F1 .55, compared to .85 in the paper).
Moreover, even loading the pretrained model with MR=0.0 yields about ~5 points lower F1, and similarly, as MR increases the performance gap between reported scores and replicated scores increases up to 20 points in F1 for MR=.7.
Could you please provide some guidance on what could be the issue?
Thank you!

Attempting to retrain the model with MR=0.0 results to significantly lower performance (F1 .55, compared to .85 in the paper).
Moreover, even loading the pretrained model with MR=0.0 yields about ~5 points lower F1, and similarly, as MR increases the performance gap between reported scores and replicated scores increases up to 20 points in F1 for MR=.7.
Could you please provide some guidance on what could be the issue?
Thank you!

May I ask if you've solved it?

Hi! If you want to obtain a pretrained model, i.e., MR=0.0, you need to remove all codes that are used for missing modality recovery, turn on the gradient of BERT, and set the learning rate to 0.0001. For the F1 .55, I don't know what's going on. It's weird.

Hi! If you want to obtain a pretrained model, i.e., MR=0.0, you need to remove all codes that are used for missing modality recovery, turn on the gradient of BERT, and set the learning rate to 0.0001. For the F1 .55, I don't know what's going on. It's weird.

Yes, I trained the model according to the instructions in the README, and set MR = 0.5. However, the accuracy is much lower than that in the article. May I ask if there is something wrong with my operations?

Hi! If you want to obtain a pretrained model, i.e., MR=0.0, you need to remove all codes that are used for missing modality recovery, turn on the gradient of BERT, and set the learning rate to 0.0001. For the F1 .55, I don't know what's going on. It's weird.

Yes, I trained the model according to the instructions in the README, and set MR = 0.5. However, the accuracy is much lower than that in the paper. May I ask if there is something wrong with my operations?

Here are some suggestions and tricks. You can increase the learning rate when the MR increases (0.001 or 0.002). You can also select the best results by early-stop. Grid-search has also been suggested to improve performance.


fix: check credential expiration timestamp when generating tokens

What this PR does / why we need it:
There are two expirations which must be considered when using a signed EKS token:

15 minutes after the point in time when the AWS STS request has been signed
The underlying AWS credentials can expire at which point the token won't be accepted

The second case is particularly common when making frequent requests while using AssumeRole or AssumeRoleWithWebRequest as mentioned in #590 as the default session timeout is 1 hour.
This PR adds an additional check fetching the AWS credential expiration and using that as the returned expiration if it is before the 15 minute token expiration.
Which issue(s) this PR fixes
Fixes #590

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Replaces https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/724
/assign @micahhausler

I'll check on this, but I think this PR is unnecessary. Most AWS temporary creds' advertised expiration is well before (as much as 50% of the cred lifetime) the actual credential is invalid. This is meant to increase the stability of an application in the event that the credential distribution method is ever impaired. Ex: If you have a 6 hour cred, but the advertised expiration is after 4 hours and normal issuance of new creds is every 4 hours, you can ride out a new credential distribution disruption for up to 2 hours.

I'll check on this, but I think this PR is unnecessary. Most AWS temporary creds' advertised expiration is well before (as much as 50% of the cred lifetime) the actual credential is invalid. This is meant to increase the stability of an application in the event that the credential distribution method is ever impaired. Ex: If you have a 6 hour cred, but the advertised expiration is after 4 hours and normal issuance of new creds is every 4 hours, you can ride out a new credential distribution disruption for up to 2 hours.

This change is definitely necessary, we made this after we saw frequent auth failures which this fixes, which is why we are currently using a fork with this change. You might be right that this is less of a problem with longer-lived creds, but we for example have a max session validity of 1h for compliance reason. Without this change, it happens regularly that the creds used to sign this request expire and the returned token stops working.

I'm ok adding this behavior with a flag (default off) because of the above situation where a cred might be reported as expired, but is still valid, we wouldn't want to create tokens with a reported expiration in the past.
I'll get #741 merged first which includes a test you should be able to extend for the new behavior

Ok, I've merged #741, that test should be extensible for this change, with the addition of a flag

@micahhausler thanks for that, I've updated the PR, please have another look

@micahhausler any chance you could have a look?


AutoSaveStateMiddleware not documented

On this page, SetAsync and SaveAsync are discussed. However it turns out that there is also middleware that can do this: AutoSaveStateMiddleware.
It is explained in https://github.com/Microsoft/AI/issues/1168 but not documented on this documentation page.
It would improve this page if you would explain the pros/cons/how to use it etc of the different approaches.

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

ID: 2c94a4c9-e988-3b42-a7db-3634d15e9c47
Version Independent ID: 68765289-1d77-6e4a-c6fb-1abbc067fcbd
Content: Save user and conversation data - Bot Service
Content Source: articles/v4sdk/bot-builder-howto-v4-state.md
Service: bot-service
Sub-service: sdk
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

At the bottom of the article, in Additional resources, we say that, "you should get, set, and save state as close together in your bot as possible." Saving state in middleware is an option, but not recommended at this point.
There are other potential issues with saving state in middleware, and the dev team currently recommends against using this, even if the folks maintaining the enterprise template like it.
I realize this is not ideal, but until the middleware and state features are more mature, we've decided not to document the auto-save state middleware.

Got confirmation from the dev team, "We do not recommend using it, as it makes behavior under error conditions unpredictable." I think the enterprise templates will be migrating away from this middleware after the 4.4 release of the SDK.

Thank you for the clarification


Define Interfaces

Abstract
Define and implement different interfaces to enable data exchange/communication between different components/parts of the application.
Steps

[x] data exchange format for calender entries
[ ] class to pass a list of calender entries around

[ ] add calender entries one by one
[ ] add calender entries in bulk
[ ] ensure uniqueness of calender entries

[ ] provide an API for holiday providers

[ ] a holiday provider provides a list of calender entries that describe holidays
[ ] possibly these providers should be organized by country / region / ..., but of course they will work with any set of datetime objects

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.5%) to 86.628%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

calingen/interfaces/data_exchange.py
0
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-1.5%

Covered Lines:
145

Relevant Lines:
166

💛  - Coveralls