Browser Droping down on all devices when I uploading file(video) ~100mb and more

Browser Droping down on all devices when I uploading file(video) ~100mb and more
maybe somebody can help

@alexander-v-ysbm I'm sorry but it's not clear to me what problem you're experiencing, please try to clarify. Additional information like error messages, code samples, browser names and versions are very helpful. The more effort you put in describing the issue the more willing people are to help you out.

@alexander-v-ysbm If this is about uploads of big files failing you could try this => https://github.com/pqina/filepond/issues/48

@rikschennink Hi, sorry for long reply, for some reason when my users load files more that ±100mb browser freezing down(I have use it for upload videos on server) iPhone(safari) MacBook, Ubuntu(firefox),
I have already resolve this problem using another uploader with chunk upload process, I saw that your uploader will be use it chunk upload at future 👍 . It will be interesting to use it in another project.
Thx for your work!

@alexander-v-ysbm Thanks for the update! Glad to hear you've found a working solution. :-)
Hope to be able to add chunk uploading soon.


Problem with sanitize an array of objects

Hi!
I'm trying to sanitize an array of objects with a custom function using exec, but when I run the sanitization, nothing happens. If I use the same function but outside the array of objects, it works perfectly.
This is my schema:

var schema = {
	type: 'object',
	properties: {
		firstName: {
			type: 'string',
			rules: ['trim', 'title']
		},
		lastName: {
			type: 'string',
			rules: ['trim', 'title']
		},
		emails: {
			type: 'array',
			items: {
				address: {
					type: 'string',
					rules: ['trim', 'lower']
				}
			}
		},
		phones: {
			type: 'array',
			items: {
				number: {
					type: 'string',
					exec: function(schema, post) {
						return '+54' + post;
					}
				},
				type: {
					type: 'string'
				}
			}
		}
	}
};

Any ideas of what can be wrong?
Thanks!
Luciano

Hi @LucianoGanga
Your schema only sanitize the object properties it cannot work because you have to encapsulate it inside the array type:
var schema = {
    type: 'array',
    items: {
        type: 'object',
        properties: {
            firstName: {
                type: 'string',
                rules: ['trim', 'title']
            },
            lastName: {
                type: 'string',
                rules: ['trim', 'title']
            },
            emails: {
                type: 'array',
                items: {
                    address: {
                        type: 'string',
                        rules: ['trim', 'lower']
                    }
                }
            },
            phones: {
                type: 'array',
                items: {
                    number: {
                        type: 'string',
                        exec: function(schema, post) {
                            return '+54' + post;
                        }
                    },
                    type: {
                        type: 'string'
                    }
                }
            }
        }
    }
};

Thank you for using schema-inspector :)

Hello @Atinux !
Thanks for your answer! :D
The problem is that the array of objects that I was saying is not the full schema, it's only the "phones" property in the big object. Anyway, I tried your solution and it didn't work :(
Thanks anyway!
I'm probably missing something here.
Cheers,
Luciano

I read again my original post and I notice that I wasn't so clear, sorry for the confusion!

No problem @LucianoGanga
Can you give me an example of your original data and what you expect in return?
This way I can help you to fix your sanitization schema :)

Sure!
This is what I have:

{
	firstName: 'Alejandro',
	lastName: 'García',
	phones: [

		{
			number: '823155231918'
		}

	],
	emails: [

		{
			address<EMAIL_ADDRESS>		}

	]
}

And this is what I expect:

{
	firstName: 'Alejandro',
	lastName: 'García',
	phones: [

		{
			number: '+54<PHONE_NUMBER>18'
		}

	],
	emails: [

		{
			address<EMAIL_ADDRESS>		}

	]
}

Hi, this is what I would do to sanitize your object:
var schema = {
    type: 'object',
    properties: {
        firstName: {
            type: 'string',
            rules: ['trim', 'title']
        },
        lastName: {
            type: 'string',
            rules: ['trim', 'title']
        },
        emails: {
            type: 'array',
            items: {
                type: 'object',
                properties: {
                    address: {
                        type: 'string',
                        rules: ['trim', 'lower']
                    }
                }
            }
        },
        phones: {
            type: 'array',
            items: {
                type: 'object',
                properties: {
                    number: {
                        type: 'string',
                        exec: function(schema, post) {
                            return '+54' + post;
                        }
                    },
                    type: {
                        type: 'string'
                    }
                }
            }
        }
    }
};

As you can see, I added the type: 'object' inside your items for phones and emails.

Excellent!! It works perfectly now. I didn't know that I had to add the type explicitly there.
Thanks @Atinux !!
And have a nice day :)
Luciano

One more question. If I run a validation instead of a sanitization... Do I have to declare explicitly the type of the content of the array? I mean, for the same schema.
Thanks!
Luciano

I'm not sure to understand, you're afraid that the validation will fail if you don't give an object in the phones property?

No no, I just meant that if I have to use the same schema structure that you told me when I write the schema for the validation, no for sanitization.
What I had before was this:
{
...
phones: {
	type: 'array',
	items: {
		type: {
			type: 'string'
		},
		number: {
			type: 'string'
		},
		primary: {
			type: 'boolean'
		},
		mobile: {
			type: 'boolean'
		},
		enabled: {
			type: 'boolean'
		}
	},
...
}

Should I replace it with this?
{
...
 phones: {
	type: 'array',
	items: {
		type: 'object',
		properties: {
			type: {
				type: 'string'
			},
			number: {
				type: 'string'
			},
			primary: {
				type: 'boolean'
			},
			mobile: {
				type: 'boolean'
			},
			enabled: {
				type: 'boolean'
			}
		}
	},
...
}

Yes you have to use the second version, the sanitization and the validation have the same logic about the items property.

Perfect! Cheers @Atinux!
And sorry for all the questions!
From:  Sébastien Chopin
Reply-To:  Atinux/schema-inspector
Date:  Tuesday, February 16, 2016 at 5:17 PM
To:  Atinux/schema-inspector
Cc:  Luciano Ganga
Subject:  Re: [schema-inspector] Problem with sanitize an array of objects (#36)
Yes you have to use the second version, the sanitization and the validation have the same logic about the items property.
—
Reply to this email directly or view it on GitHub.

Don't be sorry! I like to see that people find the scheme inspector useful :)
Thanks to you!


Fix parser to parse flag with .(dot).

Each source of SRC_URI can have a name. And the checksum is expressed as:
SRC_URI = "http://example.com/foo.tar.bz2;name=foo
http://example.com/bar.tar.bz2;name=bar"
SRC_URI[foo.md5sum] = "5c274e52576976bd70565cd72505db41" SRC_URI[bar.md5sum] = "9e822cc27b4a419529572b422c9c3970"
But current parser cannot parse flag with .(dot).

Thx - very well spotted - thanks for your contribution

Thanks for reviewing!


Make WinUI App Window Same Size as UWP App

Currently, UWP app and WinUI Desktop app has Different Initial App Window Size, It would be great if we have same size as UWP app for WinUI 3 Desktop App. Current WinUI 3 Desktop App Window is Wider but when it comes to UWP it's taller and gives more space for contents than WinUI 3 App Window in My Opinion
Proposal: [Make WinUI App Window Same Size as UWP App]

Summary

App Window Size Consistency
Rationale

This would make Apps Consistent regardless of App Model

Scope

Capability
Priority

This proposal will allow developers to accomplish Consistency regardless of App Model
Must

This proposal will allow end users to have consistent experience across the apps
Must

Screenshots

This can be easily done with WinUIEx (see https://github.com/dotMorten/WinUIEx/). It can not only set the initial window's size and location, but also remember it for next time.
*I use it to fix this WinUI 3 problems in my .NET MAUI and WinUI 3 projects
// In App.xaml.cs
var manager = WinUIEx.WindowManager.Get(window);
manager.PersistenceId = "MainWindowPersistanceId"; // this remembers the last position and size

// set minimums
manager.MinWidth = 640;
manager.MinHeight = 480;

// or just Center the window at every launch
// manager.CenterOnScreen(1024,768);

WinUIEx is a great library, however such simple features should be present out of the box for WASDK.

Yep, make sure your voice is head here (they don't follow other repos) https://portal.productboard.com/winappsdk/1-windows-app-sdk/tabs/2-planned

I don't think the team uses Product Board anymore. @BenJKuhn can you confirm/deny? Or maybe @dotmorten can share his experience with PB here?

@riverar According to the product board, "Windowing APIs" have already been released 🤦♂

Any update on this?

@teohumeau Just use Morten's helper and avoid the headache altogether.
using WinUIEx;

// To set an explicit size on launch
const int width = 1920;
const int height = 1080;
const int x = 3440 / 2 - width / 2;
const int y = 1440 / 2 - height / 2;
window.MoveAndResize(x, y, width, height);

The better option is to remember the user's window size and position, the next time the app launches it will put the app window where it was the last time it was closed.
var manager = WindowManager.Get(window);
manager.PersistenceId = "MainWindowPersistanceId";
manager.MinWidth = 640;
manager.MinHeight = 480;

I prefer the 2nd option, and I even use it in my .NET MAUI projects (see this example).


[Documentation] Write documentation for adding another language with i18n to the docs

How do doc folders work? I saw that there is a folder called da , can I create it the same way?

Yes, you can :)

I don't understand this issue, could you help with a little context?

@TheInvincibleRalph We should have a page in the docs where it explains how to add different locales to the docs e.g. add a spanish translation to the 'how to host it for free' document


Fixed Incorrect locale returned when using different domains

[…differentDomains: true and locale.domain is set with a protocol header.

🔗 Linked issue
https://volta.net/nuxt-modules/i18n/issues/2374
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Fixed Incorrect locale returned when using different domains

When using different domains, setting the domain to http://zh.nuxt-app.localhost or https://en.nuxt-app.localhost does not correctly retrieve the locale.code. I fixed this bug.

Resolves #2374
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.
](https://volta.net/nuxt-modules/i18n/issues/2374)

@risingsun529
Hi!
Thank you for your contribution!
Your PR is great job!
We are always adding the issue case as a fixture and add the test here to prevent regression recurrence.
https://github.com/nuxt-modules/i18n/tree/next/specs/issues
Could you please add them as minimal ?

@kazupon ok,I can.

@kazupon I added the issue case as a fixture and add the test.

Hi!
`[intlify] the message that is resolve with key 'xxxx' is not supported for jit compilation`

There is a waning message as shown above.
You can resolve it with syncing latest commit.

Hi @kazupon, I'm facing the same issue: [intlify] the message that is resolve with key 'xxxx' is not supported for jit compilation
How can I solve the latest commit?
I'm using NPM and updated to ´8.0.0-rc.4` but the error still persists

That issue was fixed.
If you want to fix just now, You can install edge channel version.


Install windup addon.

The operator needs to install the windup addon.  This includes:
The windup CR in the tackle namespace.
---
kind: Addon
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
  name: windup
spec:
  image: quay.io/konveyor/tackle2-addon-windup.
  mounts:
  - claim: m2
    name: m2

The claim is RWX and can follow the same pattern as buckets.  The same initial size is fine for now.  We can properly adjust the default before GA.
Related to: https://github.com/konveyor/tackle2-operator/issues/13

Closed , resolved via #15


Build fails on FreeBSD-12.0 ghc-8.6.3

This PR fixes a fatal build issue. To reproduce:
cabal new-build results with the following:
Resolving dependencies...
Build profile: -w ghc-8.6.3 -O1
In order, the following will be built (use -v for more details):

vector-th-unbox-<IP_ADDRESS> (lib) (first run)
Configuring library for vector-th-unbox-<IP_ADDRESS>..
Preprocessing library for vector-th-unbox-<IP_ADDRESS>..
Building library for vector-th-unbox-<IP_ADDRESS>..
ghc: fd:16: hGetContents: invalid argument (invalid byte sequence)

Data/Vector/Unboxed/Deriving.hs:18:21: error:
warning: treating Unicode character <U+2212> as identifier character rather than as '-' symbol [-Wunicode-homoglyph]
|
18 | Copyright:   ? 2012?2015 Liyang HU
|                     ^
cc' failed in phase C pre-processor'. (Exit code: -13)

Newer cabal-install reads .cabal files as binary. I don't think this issue is reproducible with cabal-install-<IP_ADDRESS> or <IP_ADDRESS>

Newer cabal-install reads .cabal files as binary. I don't think this issue is reproducible with cabal-install-<IP_ADDRESS> or <IP_ADDRESS>

Right in those circumstances, it compiles. However, some systems still use cabal-install-2.4.0.x and newer cabal isn't accessible from package repositories.
Would updating the version of the cabal file cause the compilation to fail gracefully? :)

@phadej , Have you maybe received the email by any chance that I have addressed to @liyang ?

@mmzx

in #23 i also made .cabal file ASCII,  so it would fix the issue when merged
No I haven't received any mails, I actually sent an email myself to Liyang partly as a Hackage Trustee to follow the NMU policy. I hope Liyang would reply some of us, so trustees don't need to step in.

Coincident, I had emailed him on the day of your update in this conversation; thinking that @phadej may actually be a Hackage Trustee member. Great! :)


Feat/esplora sync

Esplora instead of Electrs
Note that I had to (temporarily) remove a panic -
A note on testing this with our currently flaky tests:
When running all test I run into problems where sometimes a test fails and sometimes one or multiple tests may hang indefinitely. This is also happening when I run multiple on main - so I am not sure if these changes have made things worse or have introduced new / different problems.
When I run each of the (failing) tests individually the test passed - so overall all tests passed 😬

bors r-

Note: I removed the tailing slash from the esplora URL.
After that fix, then testing against a mainnet environment we still see errors sporadically, but I don't think they are a problem.
Example:
2023-05-04 17:30:12  INFO lightning_transaction_sync::esplora: Starting transaction sync.
2023-05-04 17:30:17 ERROR ln_dlc_node::ldk_node_wallet: Sync failed due to HTTP connection error, retrying: Esplora client error: Reqwest(reqwest::Error { kind: Status(502), url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("blockstream.info")), port: None, path: "/api/scripthash/b04aea33a71f5bc57b0f84fa3dc345fe4ccdb2acafeb9eda85b7d67447b89707/txs", query: None, fragment: None } })
2023-05-04 17:30:17 DEBUG reqwest::connect: starting new connection: https://blockstream.info/
2023-05-04 17:30:17 DEBUG reqwest::connect: starting new connection: https://blockstream.info/
2023-05-04 17:30:24  INFO lightning_transaction_sync::esplora: Finished transaction sync.

This error happened once in a period of ~10 minutes and it seems we just lost connection because otherwise two new connections were established.
My understanding is that this is not critical.

bors r+

I run the tests locally and some of them failed with
thread 'tests::just_in_time_channel::offline_receiver::offline_receiver' panicked at 'called `Result::unwrap()` on an `Err` value: Failed to build oracle client due to Failed to build oracle client: IO error: builder error: Too many open files (os error 24): Too many open files (os error 24), retry limit 10 reached', crates/ln-dlc-node/src/tests/just_in_time_channel/offline_receiver.rs:16:53
FAILED
test tests::multi_hop_payment::multi_hop_payment ... thread 'tests::multi_hop_payment::multi_hop_payment' panicked at 'Failed building the Runtime: Os { code: 24, kind: Uncategorized, message: "Too many open files" }', crates/ln-dlc-node/src/tests/multi_hop_payment.rs:84:6
FAILED
test tests::onboard_from_lnd::onboard_from_lnd ... thread 'tests::onboard_from_lnd::onboard_from_lnd' panicked at 'Failed building the Runtime: Os { code: 24, kind: Uncategorized, message: "Too many open files" }', crates/ln-dlc-node/src/tests/onboard_from_lnd.rs:67:56
FAILED
test tests::single_hop_payment::single_hop_payment ... thread 'tests::single_hop_payment::single_hop_payment' panicked at 'Failed building the Runtime: Os { code: 24, kind: Uncategorized, message: "Too many open files" }', crates/ln-dlc-node/src/tests/single_hop_payment.rs:58:6
FAILED

failures:

failures:
    tests::just_in_time_channel::channel_close::collab_close
    tests::just_in_time_channel::channel_close::force_close
    tests::just_in_time_channel::offline_receiver::offline_receiver
    tests::multi_hop_payment::multi_hop_payment
    tests::onboard_from_lnd::onboard_from_lnd
    tests::single_hop_payment::single_hop_payment

test result: FAILED. 7 passed; 6 failed; 0 ignored; 0 measured; 3 filtered out; finished in 135.27s

I'm rebasing on latest main and invstigating

I run the tests locally and some of them failed with
thread 'tests::just_in_time_channel::offline_receiver::offline_receiver' panicked at 'called `Result::unwrap()` on an `Err` value: Failed to build oracle client due to Failed to build oracle client: IO error: builder error: Too many open files (os error 24): Too many open files (os error 24), retry limit 10 reached', crates/ln-dlc-node/src/tests/just_in_time_channel/offline_receiver.rs:16:53
FAILED
test tests::multi_hop_payment::multi_hop_payment ... thread 'tests::multi_hop_payment::multi_hop_payment' panicked at 'Failed building the Runtime: Os { code: 24, kind: Uncategorized, message: "Too many open files" }', crates/ln-dlc-node/src/tests/multi_hop_payment.rs:84:6
FAILED
test tests::onboard_from_lnd::onboard_from_lnd ... thread 'tests::onboard_from_lnd::onboard_from_lnd' panicked at 'Failed building the Runtime: Os { code: 24, kind: Uncategorized, message: "Too many open files" }', crates/ln-dlc-node/src/tests/onboard_from_lnd.rs:67:56
FAILED
test tests::single_hop_payment::single_hop_payment ... thread 'tests::single_hop_payment::single_hop_payment' panicked at 'Failed building the Runtime: Os { code: 24, kind: Uncategorized, message: "Too many open files" }', crates/ln-dlc-node/src/tests/single_hop_payment.rs:58:6
FAILED

failures:

failures:
    tests::just_in_time_channel::channel_close::collab_close
    tests::just_in_time_channel::channel_close::force_close
    tests::just_in_time_channel::offline_receiver::offline_receiver
    tests::multi_hop_payment::multi_hop_payment
    tests::onboard_from_lnd::onboard_from_lnd
    tests::single_hop_payment::single_hop_payment

test result: FAILED. 7 passed; 6 failed; 0 ignored; 0 measured; 3 filtered out; finished in 135.27s

running the single test tests::just_in_time_channel::channel_close::collab_close manually failed with the same reason as in the pipeline.
thread 'tests::just_in_time_channel::channel_close::collab_close' panicked at 'can call blocking only when running on the multi-threaded runtime', crates/ln-dlc-node/src/ldk_node_wallet.rs:295:26

"too many open files" means that you were not able to open a new file descriptor, because your OS has ran out of them. macOS has a fairly conservative limit, I would suggest restarting the computer and trying again (or increasing the file descriptor limit).

I'm rebasing on latest main and invstigating

I've rebased on main too, and reproduced it. If you don't mind @da-kami I'll take it over as this is blocking fixing production issues.

@holzeis I have managed to work around 'too many open files', I have pushed a fix to adjust the amount of available file descriptors (it's fairly conservative on macOS by default).
I also monitored the amount of open file descriptors, and there was no major increase. as far as I'm concerned, we can merge it.

bors r+


pip3 install -r requirements.txt  error with gmp.h

I'm trying to configure and run the server but I get this error: src/curve.h:4:10: fatal error: 'gmp.h' file not found
I'm using Python 3.9.6 installed via Brew.
Any suggestion?
 skadnetwork-server % pip3 install -r requirements.txt
Collecting fastecdsa==2.1.2 (from -r requirements.txt (line 1))
  Using cached fastecdsa-2.1.2.tar.gz (45 kB)
  Preparing metadata (setup.py) ... done
Collecting Flask==1.1.2 (from -r requirements.txt (line 2))
  Using cached Flask-1.1.2-py2.py3-none-any.whl (94 kB)
Collecting Werkzeug>=0.15 (from Flask==1.1.2->-r requirements.txt (line 2))
  Using cached werkzeug-3.0.1-py3-none-any.whl.metadata (4.1 kB)
Collecting Jinja2>=2.10.1 (from Flask==1.1.2->-r requirements.txt (line 2))
  Using cached Jinja2-3.1.2-py3-none-any.whl (133 kB)
Collecting itsdangerous>=0.24 (from Flask==1.1.2->-r requirements.txt (line 2))
  Using cached itsdangerous-2.1.2-py3-none-any.whl (15 kB)
Collecting click>=5.1 (from Flask==1.1.2->-r requirements.txt (line 2))
  Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB)
Collecting MarkupSafe>=2.0 (from Jinja2>=2.10.1->Flask==1.1.2->-r requirements.txt (line 2))
  Using cached MarkupSafe-2.1.3-cp311-cp311-macosx_10_9_universal2.whl.metadata (3.0 kB)
Using cached click-8.1.7-py3-none-any.whl (97 kB)
Using cached werkzeug-3.0.1-py3-none-any.whl (226 kB)
Using cached MarkupSafe-2.1.3-cp311-cp311-macosx_10_9_universal2.whl (17 kB)
Building wheels for collected packages: fastecdsa
  Building wheel for fastecdsa (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [48 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.macosx-14-arm64-cpython-311
      creating build/lib.macosx-14-arm64-cpython-311/fastecdsa
      copying fastecdsa/benchmark.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa
      copying fastecdsa/util.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa
      copying fastecdsa/__init__.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa
      copying fastecdsa/keys.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa
      copying fastecdsa/curve.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa
      copying fastecdsa/point.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa
      copying fastecdsa/ecdsa.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa
      creating build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_point.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_keygen.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_nonce_generation.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_key_recovery.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_whycheproof_vectors.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/__init__.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_brainpool_ecdh.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_rfc6979_ecdsa.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_whitespace_parsing.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_prime_field_curve_math.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      copying fastecdsa/tests/test_p256_ecdsa.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests
      creating build/lib.macosx-14-arm64-cpython-311/fastecdsa/encoding
      copying fastecdsa/encoding/pem.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/encoding
      copying fastecdsa/encoding/util.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/encoding
      copying fastecdsa/encoding/__init__.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/encoding
      copying fastecdsa/encoding/sec1.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/encoding
      copying fastecdsa/encoding/der.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/encoding
      copying fastecdsa/encoding/asn1.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/encoding
      creating build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests/encoding
      copying fastecdsa/tests/encoding/test_sec1.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests/encoding
      copying fastecdsa/tests/encoding/__init__.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests/encoding
      copying fastecdsa/tests/encoding/test_der.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests/encoding
      copying fastecdsa/tests/encoding/test_asn1.py -> build/lib.macosx-14-arm64-cpython-311/fastecdsa/tests/encoding
      running build_ext
      building 'fastecdsa.curvemath' extension
      creating build/temp.macosx-14-arm64-cpython-311
      creating build/temp.macosx-14-arm64-cpython-311/src
      clang -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk -Isrc/<EMAIL_ADDRESS>-c src/curve.c -o build/temp.macosx-14-arm64-cpython-311/src/curve.o -O2
      In file included from src/curve.c:1:
      src/curve.h:4:10: fatal error: 'gmp.h' file not found
      #include "gmp.h"
               ^~~~~~~
      1 error generated.
      error: command '/usr/bin/clang' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for fastecdsa
  Running setup.py clean for fastecdsa
Failed to build fastecdsa
ERROR: Could not build wheels for fastecdsa, which is required to install pyproject.toml-based projects

Update:
With CFLAGS=-Ibrew --prefix gmp/include LDFLAGS=-Lbrew --prefix gmp/lib pip3 install -r requirements.txt I managed to install the requirements but then with python skadnetwork_server.py I get:
skadnetwork-server % python3 skadnetwork_server.py
Traceback (most recent call last):
  File "/Users/kappe/Developer/Singular-SKAdNetwork-App/skadnetwork-server/skadnetwork_server.py", line 5, in <module>
    from flask import Flask, request, jsonify
  File "/opt/homebrew/lib/python3.11/site-packages/flask/__init__.py", line 14, in <module>
    from jinja2 import escape
ImportError: cannot import name 'escape' from 'jinja2' (/opt/homebrew/lib/python3.11/site-packages/jinja2/__init__.py)

FYI: I solved configuring a Python3 virtual environment and changing the server dependencies to:
fastecdsa==2.1.2
flask==3.0.0
jinja2==3.1.2


Issue while showing NN to relationship as tag

Hi,
i am looking for the exact requirement, followed your code and tried in our Dev. But its not working. id attribute and name attribute are always null. Also i have a question. could you please let me know when can i see the code which is related to existing relations?
Thanks
Ram

Also could you please let me know how to use Plugins which are part of this solution.

Hello @ram-sannidi,
This sounds like a configuration issue with the field. Can you please ensure that the parameters (Related Entity, Relationship Name and Relationship Entity) are properly configured?
It should look something like this:

The code that handles existing relations can be found here:

TagPickerComponent
TagPickerGridComponent

Finally, as for the plugin, it should automatically be registered when importing the managed / un-managed solution. The plugin registers a step on Post create of any entity. It scans the fields looking for a given prefix (TAGDATA) which indicates whether the plugin needs to create links to other entities. This allows us to link to existing entities when working with a new (versus existing) entity.
Here's what the plugin step should look like:

Hope this answers your questions.
Thanks,
Joshua Campbell

Thanks a lot for speed response.
I am unable to download the managed solution. Could you please help me where can I get it?
Also could you please tell how the plugin worked with PCF component and what should I mention in related entity and relationship entity? I mean if A has N:N relationship with B what should I mention in related entity ?
Regards
Ram
Thanks
Ram

From: Joshua Campbell<EMAIL_ADDRESS>Sent: Thursday, August 27, 2020 3:22:01 PM
To: opc-cpvp/OPC.PowerApps.PCFControls<EMAIL_ADDRESS>Cc: Ram Sannidi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [opc-cpvp/OPC.PowerApps.PCFControls] Issue while showing NN to relationship as tag (#18)
Hello @ram-sannidihttps://github.com/ram-sannidi,
This sounds like a configuration issue with the field. Can you please ensure that the parameters (Related Entity, Relationship Name and Relationship Entity) are properly configured?
It should look something like this:
[Capture]https://user-images.githubusercontent.com/1784236/91445725-7a918a00-e844-11ea-9a8b-88e1946c72f5.PNG
The code that handles existing relations can be found here:

TagPickerComponenthttps://github.com/opc-cpvp/OPC.PowerApps.PCFControls/blob/master/src/Components/TagPickerComponent/TagPickerComponent/TagPickerBaseComponent.ts#L139
TagPickerGridComponenthttps://github.com/opc-cpvp/OPC.PowerApps.PCFControls/blob/master/src/Components/TagPickerGridComponent/TagPickerGridComponent/TagPickerBaseComponent.ts#L178

Finally, as for the plugin, it should automatically be registered when importing the managed / un-managed solution. The plugin registers a step on Post create of any entity. It scans the fields looking for a given prefix (TAGDATA) which indicates whether the plugin needs to create links to other entities. This allows us to link to existing entities when working with a new (versus existing) entity.
Here's what the plugin step should look like:
[Capture2]https://user-images.githubusercontent.com/1784236/91446823-efb18f00-e845-11ea-8a33-55c706784a49.PNG
Hope this answers your questions.
Thanks,
Joshua Campbell
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/opc-cpvp/OPC.PowerApps.PCFControls/issues/18#issuecomment-681945380, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK6O7A3VWHATUM6VMWSZBMTSCZMXTANCNFSM4QMXL4CA.

I am unable to download the managed solution. Could you please help me where can I get it?

You can download the latest managed solution from the following URL: https://github.com/opc-cpvp/OPC.PowerApps.PCFControls/releases/latest

Also could you please tell how the plugin worked with PCF component

The plugin only gets triggered after an entity is created. It then scans each of the fields of the entity for the prefix and converts the data into relationships on the field.

what should I mention in related entity and relationship entity? I mean if A has N:N relationship with B what should I mention in related entity

You should be using the "Relationship name" of the relationship between your two entities.

Regards,
Joshua Campbell

Hi Joshua,
My apologies for spamming your mailbox.
I doubt that below code wont work for N:N relationships:
<EMAIL_ADDRESS>I added relationshipName instead of relationship entity. It was throwing error when I am using relationshipEntity.
Also there is some issue with EntityMetadata it seems. I was going through Primary Attributes and could not find the attributes which were mentioned in the solution.
PrimaryNameAttribute is
<EMAIL_ADDRESS>Primary Id Attribute is
<EMAIL_ADDRESS>Also one question for which I am waiting for response. Sorry for not putting the things clearly. Thing is that
Assume I have two entities A and B and N:N relationship exists between them. Relation ship name should go in “Relation Name” property but
Related Entity -> A
RelationshipEntity -> B. Does this order really matters?
Thanks
Ramakrishna Sannidi
From: Joshua Campbell<EMAIL_ADDRESS>Sent: Thursday, 27 August 2020 15:50
To: opc-cpvp/OPC.PowerApps.PCFControls<EMAIL_ADDRESS>Cc: Ram Sannidi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [opc-cpvp/OPC.PowerApps.PCFControls] Issue while showing NN to relationship as tag (#18)
I am unable to download the managed solution. Could you please help me where can I get it?
You can download the latest managed solution from the following URL: https://github.com/opc-cpvp/OPC.PowerApps.PCFControls/releases/latest
Also could you please tell how the plugin worked with PCF component
The plugin only gets triggered after an entity is created. It then scans each of the fields of the entity for the prefix and converts the data into relationships on the field.
what should I mention in related entity and relationship entity? I mean if A has N:N relationship with B what should I mention in related entity
You should be using the "Relationship name" of the relationship between your two entities.
[Image removed by sender. Relationship name]https://user-images.githubusercontent.com/1784236/91450467-5638ac00-e84a-11ea-9c5a-846bc76c0677.png
Regards,
Joshua Campbell
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/opc-cpvp/OPC.PowerApps.PCFControls/issues/18#issuecomment-681960929, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK6O7A22GRYHZ7AWKEVMSMLSCZQAPANCNFSM4QMXL4CA.

Sorry, the image I previously uploaded contained the wrong information. Please ensure that you're using the "Relationship entity name" of your N-N relationship when providing the "Relationship Entity" parameter as per the following screenshot:

Also one question for which I am waiting for response. Sorry for not putting the things clearly. Thing is that Assume I have two entities A and B and N:N relationship exists between them. Relation ship name should go in “Relation Name” property but Related Entity -> A RelationshipEntity -> B. Does this order really matters?

If you're editing the form for entity A to include a tag picker component for entity B, then the "Related Entity" should be the logical name of entity B and the "Relationship Entity" should be the logical name of the relationship entity of the N-to-N relationship between entity A and entity B (see previous screenshot).
Joshua Campbell

@ram-sannidi I will be marking this issue as closed. If you feel like your question was unanswered, please re-open the issue. Thanks!

Hi Josh,
I'm facing same issue
configuration is correct as mentioned but value is removed once page is refreshed Please help on this.

Hello @girishbellani14,
It doesn't sound like your relationship is saving.
Can you please share your configuration with me?
Thanks,
Joshua Campbell

Hi @joshcampbell191 ,
This is configuration
Thanks for quick reply.

It appears that the "Relationship Entity" property is incorrect.
Can you please share the properties of the m365_Tag relationship? @girishbellani14

It is same as relationship entity name , i manually added that
and one thing i'm facing issue as 19th
Sorry for bit mess @joshcampbell191

@girishbellani14  Can you please share the relationship properties so I can get a better understanding of how your environment is configured?

@joshcampbell191

Can you please ensure that you're using a N-to-N type relationship between your entities?

Yes it's n-n @joshcampbell191

Unfortunately, I can no longer see the configuration you used for the control. Can you please share it again?

Is it possible to connect through teams/skype?
Configuration is as per documentation only
@joshcampbell191

Sorry for the delay @girishbellani14. I can make myself available next Wednesday if that works for you.

I can help Girish on Monday.
@Girish let me know your free time. I will try to help you.
Thanks
Ram
Thanks
Ram

From: Joshua Campbell<EMAIL_ADDRESS>Sent: Saturday, September 19, 2020 12:11:13 AM
To: opc-cpvp/OPC.PowerApps.PCFControls<EMAIL_ADDRESS>Cc: Ram Sannidi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [opc-cpvp/OPC.PowerApps.PCFControls] Issue while showing NN to relationship as tag (#18)
Sorry for the delay @girishbellani14https://github.com/girishbellani14. I can make myself available next Wednesday if that works for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/opc-cpvp/OPC.PowerApps.PCFControls/issues/18#issuecomment-695108725, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK6O7A55ABEXQCZEZPCDIKDSGPLIDANCNFSM4QMXL4CA.

@ram-sannidi @girishbellani14 were you guys able to connect and resolve the issue?

Hi,
No. I have not received any response from Girish.
Thanks
Ram

From: Joshua Campbell<EMAIL_ADDRESS>Sent: Wednesday, September 23, 2020 7:10:35 PM
To: opc-cpvp/OPC.PowerApps.PCFControls<EMAIL_ADDRESS>Cc: Ram Sannidi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [opc-cpvp/OPC.PowerApps.PCFControls] Issue while showing NN to relationship as tag (#18)
@ram-sannidihttps://github.com/ram-sannidi @girishbellani14https://github.com/girishbellani14 were you guys able to connect and resolve the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/opc-cpvp/OPC.PowerApps.PCFControls/issues/18#issuecomment-697716389, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK6O7AYERFXDFFNOZW7DIPDSHITYXANCNFSM4QMXL4CA.


Update library with Croatia's move to the Euro

Thank you so much for this self-updating library. As you may know, Croatia moved to the Euro on January 1st. This has been reflected already in the source XML files but this library hasn't been updated yet.
As far as I understand, the library is updated every Friday so by then this should be fixed. Right?
This can be quite a long tome for such data to be outdated. Do you think it would make sense to update the GitHub workflow to run every day?

Thanks for using the package!

As far as I understand, the library is updated every Friday so by then this should be fixed. Right?

Yes, it is pretty well automated, the data should get updated automatically this Friday. But I've [manually spun the update for you just now, check it out][(https://github.com/parzh/iso4217/actions/runs/3831911530).

Do you think it would make sense to update the GitHub workflow to run every day?

Not sure every day would be the best option. Perhaps, it would make sense to additionally update the data at the 1st day of every month? This can be done.

Seems to have been successfully published, I'm closing the issue.

Thank you for the quick update.
About when to run the update workflow, I'm not sure either. On the first day of the month specifically makes sense to me. But I'm worried about timezone differences of a) the country that changes the currency, b) the time at which the ISO standard is updated and c) the time at which this workflow runs. If the workflow runs before a) or b), it won't pick up the updated currency. That's why I think running this once a day should be frequent enough to pick up changes but also not too frequent to be be abusive towards the source file server. But I don't have strong opinions about this :).

Well indeed, if it ain’t broke then don’t fix it, right? After all, I’m not a maintainer of GitHub or ISO API, request rate limiting is not my concern. Once a day it is.


Version-sync should be a build dependency

That dependency is only used in unit tests. Having it as a dependency slows library users build time by compiling unused code.

You are right, looks like typo!


Crash when starting without an auth handler

I am running registry:2 (docker image ddfb3bf27ae2) behind an authorizing proxy. Most of my configuration:
version: 0.1
log:
  level: warn
  formatter: text
  fields:
    service: registry
    environment: garden
  hooks:
    - type: mail
      levels:
      - panic
      options:
         smtp:
          addr: something
          username: foo
          password: bar
        from<EMAIL_ADDRESS>    to:
      -<EMAIL_ADDRESS>storage:
   s3:
http:
  addr: :5000

This results in a whine about realm not being set for htpasswd auth.  The same configuration worked last week.

@ferrix What error message are you getting which specific configuration?
 Is there something you're trying to test?

For the first incarnation of the config.yml:
panic: unable to configure authorization (htpasswd): "realm" must be set for htpasswd access controller

This is for the second incarnation:
panic: unable to configure authorization (silly): "path" must be set for htpasswd access controller

That is a bit funny since silly does not require "path" at all. The third one I don't have but practically "service" must be set for silly access controller.
The originating line was: https://github.com/docker/distribution/blob/master/registry/handlers/app.go#L236
So my theory is that nothing or something equal auth.htpasswd for some reason and those errors need to be handled some way.
 The bottom line is that it does not hurt much either unless there is some specific insecurity about it that is not documented. I do have the authenticating proxy anyway. Without it, registry crashes and I am getting nothing. So it is just a really silly workaround.

@ferrix What is the output of docker run -it registry:2 --version?
I just tried the following configuration, with and without the auth section, and it worked fine:
version: 0.1
log:
  level: debug
  fields:
    service: registry
    environment: development
storage:
  filesystem:
    rootdirectory: /usr/local/var/lib/registry
http:
  addr: :5000
  debug:
      addr: localhost:5001
  headers:
      X-Content-Type-Options: [nosniff]
auth:
  silly:
    realm: silly-realm
    service: silly-service

My guess would be that there is a spacing issue or the complete configuration is incorrect in some way.
I'd recommend starting with a completely fresh configuration and turn off all environment variables. From there, work through one of the getting started handbooks.

Here's the version:
/bin/registry github.com/docker/distribution v2.2.0

All of this started happening when the image got upgraded. Initially, I did not have the auth section in my configuration at all but suddenly that resulted in a crash. Also, I am validating my YAML, so spacing issues are simply not there.

@ferrix Could you provide the whole configuration in a gist along with the unmodified log? I simple wasn't able to reproduce this with 2.2.
Here is the configuration I use for development:
version: 0.1
log:
  level: debug
  fields:
    service: registry
    environment: development
storage:
  filesystem:
    rootdirectory: /usr/local/var/lib/registry
http:
  addr: :5000
  debug:
      addr: localhost:5001
  headers:
      X-Content-Type-Options: [nosniff]

ping @ferrix has this been resolved for you? If not, could you provide the information that @stevvooe requested?

I've also run into this issue and I think I have a reproduce case with the config @stevvooe provides.
I got the same error after upgrading to v2.2.1 from v2.1.1, and tracked it down to an errant environment variable. I'd previously played with having auth done at the registry itself before putting nginx in front of it. However, I inadvertently left REGISTRY_AUTH_HTPASSWD_PATH set in the environment variables file for the registry.
It looks like if that environment variable is set without any auth section in the registry config it will cause the panic. Perhaps it circumvents some sanity checks by being an environment variable and causes the panic instead of simply a misconfiguration error (since realm is required in the htpasswd section of auth).

@dsanders11 Interesting. Thank you for the investigation.
Generally, we treat misconfigurations as panics, since they may result in unintended, insecure deployments. While in this case it was confusing, the registry took the right action by not proceeding with serving a registry that may have required authentication.
I've reproduced this behavior with the following incantation:
REGISTRY_AUTH_HTPASSWD_PATH=foo ./bin/registry ./cmd/registry/config-dev-osx.yml

We'll look into a possible bugfix for the error message, but this is still from a bad configuration.

In case it helps
I did have this error message, which turned out to be a typo in the arguments:
docker run [...] -e "REGISTRY_AUTH=htpasswd" -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" [...]
I had some typos in the environment variable names...

I also experienced this. It turned out that I forgot to define the REGISTRY_AUTH_HTPASSWD_PATH variable as described in https://docs.docker.com/registry/deploying/ .
I initially thought that only the highlighted red lines need to be added and thus overlooked REGISTRY_AUTH_HTPASSWD_PATH. Perhaps you could highlight it as well.

I also experienced this. It turned out that I forgot to define the REGISTRY_AUTH_HTPASSWD_PATH variable as described in https://docs.docker.com/registry/deploying/ .
I initially thought that only the highlighted red lines need to be added and thus overlooked REGISTRY_AUTH_HTPASSWD_PATH. Perhaps you could highlight it as well.

@3Nigma The highlighting is just for string syntax in the shell command.
I am not really seeing much of an issue. In all cases, it is preventing incorrect configuration from going live. This is working as intended and the error message is reporting something actionable.
Unless anyone wants to step up and submit a PR, we should probably close this.

Closing as wildly outdated. Besides, things work as expected.


Tag auto rename issue?

Each time I use <prefix> , to rename my working tag, it will be automatically renamed back whenever I do something in this tag, which is annoying since I am using a remote server that has a very nonsense hostname like  root@iZ2zej8qby6d0rbmoxcdw5Z:~
I am wondering in which way could I turn this feature off.

It fixed! Thanks!
I have tried to set automatic-rename to off but not useful at all. allow-rename option helps.

Cool.
Are we good then?


[Guidance] Power Platform Landing Zones for brownfield

Provide prescriptive guidance for:

Customers with existing Power Platform footprint, and how to transition into Power Platform Landing Zones architecture, and align with the principles and recommendations
2 or 3 scenarios that are most common, and use as starting point

@krnese @daltondhcp thank you for the update, as this item has the backlog label, could you please assign a team member? Thank you

Yes @aydinderya - we're working to figure out who to assign this effort the coming days.


web server

When I submit tasks using RNA-MSM web server, the following issue always appear.

When I submit tasks using RNA-MSM web server, the following issue always appear.

Hello, I just checked our website and submitted a simple test task. The website works normally without the state of 414. Could you try to submit it again?

Okay, the problem has been resolved. Thank you.


Mark the documentation consolidation in the Roadmap as done.

Signed-off-by: Chris Lalancette<EMAIL_ADDRESS>

I'm going to go ahead and merge this one without review.


chore(deps): update common-dev-assets digest to 16e53c8

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
64fc718 -> 16e53c8

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This issue has been resolved in version 3.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add XGBoost based models

Need to evaluate models of the type :
Transformed_Signal = Trend + Periodic + XGBoostRegressor(target = PeriodicResidue, input = PeriodicResidue_Lags)
Of course, this is done inside the competition (all possible combinations of transformations, trends and periodics are tested).

Easy to implement,. A generic scikit-learn model can already be used (SVR models are alreay OK).
A new package dependency
pip install xgboost

create anew branch pyaf_xgboost

Time series models based on XGBoost regressors has been added. They are not activated by default.
Need to activate these using something like :
lEngine.mOptions.set_active_autoregressions(['AR', 'XGB']);

Fixed.
Some tests here :
https://github.com/antoinecarme/pyaf/tree/master/tests/xgb
Closing.


Error when compiling quantized LSTM with vai_c_xir

I am attempting to compile a quantized LSTM model for the ZCU102, and am getting a fatal error.

`(vitis-ai-pytorch) Vitis-AI /workspace/tools/RNN/rnn_compiler > vai_c_xir -x quantize_result/xmodel/Lstm_StandardLstmCell_layer_0_forward_int.xmodel -a /opt/vitis_ai/compiler/arch/DPUCZDX8G/ZCU102/arch.json -n LSTM
**************************************************
* VITIS_AI Compilation - Xilinx Inc.
**************************************************
[UNILOG][INFO] Target architecture: DPUCZDX8G_ISA0_B4096_MAX_BG2
[UNILOG][INFO] Compile mode: dpu
[UNILOG][INFO] Debug mode: function
[UNILOG][INFO] Target architecture: DPUCZDX8G_ISA0_B4096_MAX_BG2
[UNILOG][INFO] Graph name: Lstm_StandardLstmCell_layer_0_forward, with
op num: 80[UNILOG][INFO] Begin to compile...
[UNILOG][WARNING] xir::Op{name = Lstm_StandardLstmCell_layer_0_forward__ft_input_2_new, type = depthwise-fix} has been assigned to CPU: [DPUCZDX8G_ISA0_B4096_MAX_BG2 does not have alu-engine].
[UNILOG][WARNING] xir::Op{name = Lstm_StandardLstmCell_layer_0_forward__it_cct_new, type = depthwise-fix} has been assigned to CPU: [DPUCZDX8G_ISA0_B4096_MAX_BG2 does not have alu-engine].
[UNILOG][WARNING] xir::Op{name = Lstm_StandardLstmCell_layer_0_forward__h_next_new, type = depthwise-fix} has been assigned to CPU: [DPUCZDX8G_ISA0_B4096_MAX_BG2 does not have alu-engine].
[UNILOG][FATAL][XCOM_ITEM_UNDEFINED][The requested item is not finded or defined!]
*** Check failure stack trace: ***
Aborted`

I cannot figure out how to check further details about the error to figure out exactly what is going wrong.
Thank you

Are the layers supported by Xilinx as a default? If not I would work my way back from a reference LSTM example.

Looks like you're using the CNN compiler, if you want to compile  LSTM model, The RNN compiler is needed.

Hi @chtapodi ,
The RNN workflows are at https://github.com/Xilinx/Vitis-AI/tree/v2.0/demo/DPU-for-RNN . For RNN workflows, you will need to build the RNN docker https://github.com/Xilinx/Vitis-AI/tree/v2.0/demo/DPU-for-RNN

Hi @chtapodi ,
Has the problem been resolved? Do you have any other questions? If there are no more issues, we will close this issue. There is a problem later, please reopen the issue. Thank you.

[AMD Official Use Only - General]
HI. You can close it. Thank you.
From: zhenzhen-AMD-Xilinx @.>
Reply-To: Xilinx/Vitis-AI @.>
Date: Friday, July 22, 2022 at 10:38
To: Xilinx/Vitis-AI @.>
Cc: dzhy Xilinx @.>, Comment @.>
Subject: Re: [Xilinx/Vitis-AI] Error when compiling quantized LSTM with vai_c_xir (#507)
Resent-From: dzhy Xilinx @.>
CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
Hi @chtapodihttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fchtapodi&data=05|01|dong.han%40amd.com|c97699856457481f960908da6b8b3f9c|3dd8961fe4884e608e11a82d994e183d|0|0|637940543060359062|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0w7dij1Vm7wVjqVWmlKGU4NPCh1ecMvNwpC63id302Y%3D&reserved=0 ,
Has the problem been resolved? Do you have any other questions? If there are no more issues, we will close this issue. There is a problem later, please reopen the issue. Thank you.
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FXilinx%2FVitis-AI%2Fissues%2F507%23issuecomment-1192119503&data=05|01|dong.han%40amd.com|c97699856457481f960908da6b8b3f9c|3dd8961fe4884e608e11a82d994e183d|0|0|637940543060359062|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=UejBF%2F5IsAeEHPjedttfDLHLs3iWm6QSH%2BaQypzx7EU%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAVJ7DCZOUDY72IO226557R3VVICRXANCNFSM5B7SJ4AA&data=05|01|dong.han%40amd.com|c97699856457481f960908da6b8b3f9c|3dd8961fe4884e608e11a82d994e183d|0|0|637940543060359062|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=A2bYYEBhMlAmtM4VGXxTwRobjg6WvlKOZ%2B9wCus3a8c%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>


new package: lzip 1.21

Description of package
Checklist

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

done


bits and bobs to make the pipeline run

mma_areas needs to be created by webserver
mma_area_hits needs to be created on the filter node
removed very annoying WARNING message from ingest

Please don't disable the annoying warning message in ingest. There is a proper fix in another branch (refactor/system-tests). If you can't wait then please copy the fix from there.


Remove iterable pseudotype

This isn't a real interface. Because of this stub PhpStorm currently doesn't complain about such code:

But PHP ends with fatal error: https://3v4l.org/UYkWD
The RFC https://wiki.php.net/rfc/iterable states:

This RFC proposes a new iterable pseudo-type. This type is analogous to callable, accepting multiple types instead of one single type.

jetbrains/phpstorm-stubs do not contain "interface callable" either...

@ondrejmirtes Unfortunately, PR can't be merged right away because a lot of functionality (such as type inference, completion, inspections) depends on this type declaration in stubs. The type was added in scope of WI-32378. I've filled WI-71397 to fix the problem with not highlighted implements iterable (possible in scope of the fix declaration will be removed, but can't say for sure at the moment)


Docs + GE integration

@shemogumbe , can you please describe this feature, so that others are also able to help / propose a possible PR?
Please, let's make this repo inclusive, so that the open-source community can help us too.

This work is done.
During the building of SDKs, after generating snippets, we intended to have the snippets added to graph explorer and the docs as


release one tispark jar instead of two

What problem does this PR solve?
currently we must release two jars, one for spark-2.3 another for spark-2.4
What is changed and how it works?
release only one jar, both work for spark-2.3 and spark-2.4
Related changes

Need to update the tidb-ansible repository (jar name may change)

close https://github.com/pingcap/tispark/issues/932

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.4

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.4

/run-all-tests profile=spark-2.4

/run-all-tests profile=spark-2.4

/run-all-tests profile=spark-2.3

/run-all-tests profile=spark-2.4

/run-all-tests profile=spark-2.4

/run-all-tests profile=spark-2.4

/run-all-tests profile=spark-2.4

How large is the jar size now?

How large is the jar size now?

28M

/run-all-tests profile=spark-2.3

/run-all-tests

/cc @birdstorm PTAL

/run-all-tests

/run-all-tests


Feature Request: Ability to export as image

Thanks for making this; It is awesome, but I think we can make it even further; I think it is nice to have the "Export as image" ability for general use cases, thanks.

@erbanku Hi, I don't think the library should have an image export function, its purpose is to render animation.
I am currently working on an example export-as-image :eyes:

export-as-image merged


error count does not match the number of errors outputted

Environment information
CLI:
  Version:                      1.6.0
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.19.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.14.3"

Biome Configuration:
  Status:                       unset

Workspace:
  Open Documents:               0

Rule name
useImportType
Playground link
N/A
Expected result
The number of errors found in the output of both the check and lint commands should match the number of errors that were printed.
Let's create a file named a.ts with the following content:
import React from "react";
const a: React.ReactNode = null;

When executing the biome lint a.ts command, the output is:
a.ts:1:1 lint/style/useImportType  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ All these imports are only used as types.

  > 1 │ import React from "react";
      │ ^^^^^^^^^^^^^^^^^^^^^^^^^^
    2 │ const a: React.ReactNode = null;
    3 │

  ℹ Importing the types with import type ensures that they are removed by the transpilers and avoids loading unnecessary modules.

  ℹ Safe fix: Use import type.

    1 │ import·type·React·from·"react";
      │        +++++

Checked 1 file in 15ms. No fixes needed.
Found 2 errors.
lint ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Some errors were emitted while running checks.

It says Found 2 errors, but only one error is present.

When executing the biome check a.ts command, the output is:
a.ts:1:1 lint/style/useImportType  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ All these imports are only used as types.

  > 1 │ import React from "react";
      │ ^^^^^^^^^^^^^^^^^^^^^^^^^^
    2 │ const a: React.ReactNode = null;
    3 │

  ℹ Importing the types with import type ensures that they are removed by the transpilers and avoids loading unnecessary modules.

  ℹ Safe fix: Use import type.

    1 │ import·type·React·from·"react";
      │        +++++

Checked 1 file in 10ms. No fixes needed.
Found 3 errors.
check ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Some errors were emitted while running checks.

The printed errors are the same as in the lint case, but the error count is 3 for some reason now.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Hello @chansuke, I did some debug for this issue just out of curiosity and for getting familiar with the codebase. The extra count of the error seems from this piece:
https://github.com/biomejs/biome/blob/984626de115e4b8f64dec97d3f66ba353ebf1b65/crates/biome_cli/src/execute/traverse.rs#L418-L420
The way I debugged it is printing a message before each line of self.errors.fetch_add and ran the lint and check commands respectively. Here are the results.

cargo run --bin biome lint ./a.ts --verbose --diagnostic-level=info
It says it found 2 errors, 1 of them is from the Message::Failure branch.

cargo run --bin biome check ./a.ts --verbose --diagnostic-level=info
It says it found 3 errors, 2 of them are from the Message::Failure branch.

I think the reason is that the error count will be correctly increased in other dedicated branches, so the one in branch Message::Failure seems redundant. I not sure though if we should remove this branch. But by searching Message::Failure in the whole codebase, it seems that this message will only be sent from the lint and check processes.
I hope my findings can provide some help :)

@Sec-ant Hi!Thank you so much for the information!I was busy last week but start working on this issue tomorrow.

Hi @chansuke, I'm gonna take over this issue to ship a fix before v1.6.4 is released.

@Sec-ant
NP. Thank you for your great work!!!


Update dependencies in Godep for #275

As part of #284 , in #275 , we adds in new dependencies on gopsutil and OpenCensus.
This PR updates Godep so that NPD can build correctly.
I separated these code out from #275 , so that #275  can focus on real code changes, rather than dependency management.

/assign @wangzhen127

/ok-to-test

/lgtm
/approve
@xueweiz You need to force push in #275.


Rename to kubeip

Looks like travis did not like the repo renaming:
$ git clone --depth=50 https://github.com/doitintl/kubeIP.git doitintl/kubeIP
Cloning into 'doitintl/kubeIP'...
$ cd doitintl/kubeIP
$ git fetch origin +refs/pull/30/merge:
fatal: Couldn't find remote ref refs/pull/30/merge

https://travis-ci.org/doitintl/kubeIP/builds/433925378

Builds are just fine.
I merged before and deleted the branch during the build
https://travis-ci.org/doitintl/kubeIP/builds/433925564
On Thu, Sep 27, 2018 at 9:13 AM Patrick Decat<EMAIL_ADDRESS>wrote:

Looks like travis did not like the repo renaming:
$ git clone --depth=50 https://github.com/doitintl/kubeIP.git doitintl/kubeIP
Cloning into 'doitintl/kubeIP'...
$ cd doitintl/kubeIP
$ git fetch origin +refs/pull/30/merge:
fatal: Couldn't find remote ref refs/pull/30/merge
https://travis-ci.org/doitintl/kubeIP/builds/433925378
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/doitintl/kubeip/pull/30#issuecomment-424970985, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADHSJfsBBxt7doh0r0ntGNnF8Bfebg9fks5ufGyXgaJpZM4W79q7
.

--
Aviv Laufer
| DoiT International
| phone: +972-54-5365536
| email<EMAIL_ADDRESS>Follow me: [image: linkedin] https://www.linkedin.com/in/avivl/[image:
twitter] https://twitter.com/avivl[image: medium]
https://medium.com/@avivl[image: github] https://github.com/avivl


Merge bitcoin#13152: Add getnodeaddresses RPC command

bitcoin#13152

That's not the only place were we use non-default ports really. I'm just going to merge it as is, feel free to submit a PR that changes all the 8333 ports to 9999 ones :)


Invalid JavaScript for arrow functions with comments

I've been converting a lot of ES6 JavaScript into TypeScript, and noticed a lot of places got broken where there is a comment between an arrow function opening and implementation.
The code below is supposed to be convertible from ES6 to TypeScript as 1-to-1, without any changes needed:
function test(){
    return ()=>
    // some comments here;
    123;
}

Calling such a function within ES6 returns the expected ()=>123.
When compiling such TypeScript into ES5 JavaScript we are expecting something like this:
function test(){
    return function () {
        // some comments here;
        return 123;
    };
}
// returns: ()=>123

But instead, we are getting this:
function test() {
    return function () {
        // some comments here;
        return
        // some comments here;
        123;
    };
}
// returns: ()=>undefined

Which produces a different output result: ()=>undefined.

Hi @vitaly-t I'm not sure where you're getting that emit from. Here is exactly what I'm getting in the TypeScript Playground which runs TypeScript 1.8.
function test() {
    return function () {
        // some comments here;
        return 123;
    };
}

What version of TypeScript are you running? You can run tsc --version to find out.

@DanielRosenwasser
D:\NodeJS\tests\ts>tsc --version
Version 1.8.10

Now running tsc test, using input:
function test(){
    return ()=>
        // some comments here;
        123;
}

getting output:
function test() {
    return function () {
        // some comments here;
        return
        // some comments here;
        123;
    };
}

So I don't know what's the difference from your setup...

@DanielRosenwasser looks like one shouldn't rely on that Playground for this test. If you run it locally yourself, you will get the same result as me.

Mybe, This is effected by target option. When I compile tsfile with tsc test.ts
output:
function test() {
    return function () {
        // some comments here;
        return
        // some comments here;
        123;
    };
}

But, with tsc test.ts --target "es5"
function test() {
    return function () {
        // some comments here;
        return 123;
    };
}

@YuichiNukiyama I can confirm that is indeed the case.

@vitaly-t  default target vaule is es3. see Compiler Options wiki.
@DanielRosenwasser
This must be bug. I found suspicious code in Emmiter.ts L7882(compilerOptions.target is worng. This variable should be languageVersion). If you also think so, I run tests and send PR.

The target is ES3 by default. Thank you for finding this, and @YuichiNukiyama, thank you for investigating! We'd definitely appreciate a PR!

A simple test case to add would be
tests/cases/compiler/singleLineCommentInConciseArrowFunctionES3.ts
function test(){
    return ()=>
    // some comments here;
    123;
}

thanks @YuichiNukiyama !


Parameters on the command line are (silently) ignored after Sumatra upgrade

This is a bug report on behalf of another user who experienced the following issue:
After upgrading Sumatra to version 0.6.0 any parameters supplied on the command line would be ignored. There was no error message, but Sumatra would just silently use the values in the default.param file.
After some debugging the reason seems to be that the option allow_command_line_parameters in the file .smt/project was set to null. Instead, it should have been set to true because the project was never configured with the --plain option. I presume that this happened during the upgrade because the option was only introduced recently?
I'm currently travelling so can't reproduce this on my own or look into it for another week, but I wanted to report it because it seems like a dangerous and annoying issue (dangerous because a user might not notice it for a long while because there is no error message and annoying because it's not clear how to change it from a user's point of view). I also thought that there is probably a quick fix, but otherwise I'm happy to dig into it once I'm back.
Imported from Bitbucket issue 207,  created by cilix on 05-02-2014 at 12:06, last modified: 05-05-2014 at 20:21

This was fixed in commit 46d05a388eb81614.


Chunk Animator Not Animating with Shaders

Notice
If you are opening an issue for any other reason than to report a bug or request a new feature, you should probably be using the Discussions tab.
Describe the bug
Chunk Animator does not animate when any shader besides OptiFine Internal is enabled.
To Reproduce
Steps to reproduce the behavior:

Have OptiFine installed.
Load any shader besides Internal in OptiFine.
Chunks no longer animate.

Expected Behavior
Chunks animate while shader is loaded in OptiFine.
Versions:

Minecraft Version: 1.18.2
Forge Version: 40.1.74
Chunk Animator Version: 1.3.4
OptiFine Version: 1.18.2 HD U H9 Pre1

Additional context
#26

Animations remain broken when loading any shader pack. I used Sildur's Shader Version 1.41 since it was updated.

Fixed in 1.3.7. Make sure render regions is off as it is still incompatible with this option.


test_user_prayer_status_change_answer.py:103: Добавить кейсы

The puzzle 1214-90d051e0 from #1214 has to be resolved:
https://github.com/blablatdinov/tg-quranbot/blob/c4bb29248e98ce20f9d5cce1601c21f59015e16d/src/tests/it/handlers/test_user_prayer_status_change_answer.py#L103-L103
The puzzle was created by Almaz Ilaletdinov on 02-Sep-24.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1214-90d051e0 has disappeared from the source code, that's why I closed this issue.


Add Environment.Delete

Add a method to delete value from environment by key.
The new method should have documentation comment with code example and be covered by test.

Hi @gavv, can I work on this?

Sure, thanks!


Add legislator misconduct data?

At GovTrack we're creating a database of legislator misconduct --- anything investigated by Congress's ethics offices or by law enforcement:
https://www.govtrack.us/misconduct
Is there interest in storing that data here? I expect to create a YAML file with records for each investigation and fields holding links to relevant documents and a 'text' key holding a Markdown description of the investigation.

I love legislator misconduct! But to be precise, it appears you're talking about only misconduct that has been the subject of official cognizance or action. That's arguably a small subset of the misconduct legislators do. Be sure to describe it accurately as that limited set of misconduct data.
There is a lot of play in the joints about what is misconduct and what is treated as misconduct. There are false accusations and sometimes false findings and excessive punishments. So the subject matter is a little inconsistent with the bulk of the data here, which is neutral, objective, and not subject to serious debate about the fairness of it, the accuracy with which it depicts events, and so on.
So count this is the mildest of nay votes -- from a  big fan of misconduct!

"Big fan of misconduct!" -- Jim Harper
I think it would be useful, as long as it's got some sort of metadata touching on the outcome of investigations, beyond just the full-text description of how the investigation turned out. I think that would speak to Jim's concerns, and make it easier for consumers to filter on the gravity of misconduct or create displays that factor this information in.

I think it would be great transparency so long as it is presented as objective and fact-checked.

I like it. I agree with the others in the thread. As long as its official misconduct, that has legal investigation, and a node for outcome, it would be great data to have.

Thanks for the feedback all. We're incubating the info at https://github.com/govtrack/misconduct.

This is great data and seems to be maintained.  Should this issue be closed at this stage?


Lower App Engine deployment costs

Have been observing costs that exceed the free tier on a relatively consistent basis that I would like to reduce more consistently. The following screenshot captures an example of what that looks like over the last month.
Worth noting that the flatline at "1" for the recent gew days does correspond with the most recent deployment of the site, so some of this could just be related to instances spun up for use in different version deployments and we can wait a bit to see if that trend continues.

In that image, the pink line represents "idle" instances, which seems unnecessary.
Configuration changes
App Engine automatic scaling
App Engine is configured by a set of configuration options in the app.yaml file documented here: https://cloud.google.com/appengine/docs/standard/go/config/appref#automatic_scaling
The options I have configured today are: https://github.com/kujenga/website/blob/dc352ff98ea603ccbe74a0bf85a05570c6f6c93b/app/app.yaml#L6-L17
Ideas:

tweak down the max_idle_instances value to probably just 1.
turn up the max_concurrent_requests that defaults to 10, probably all the way to 80 is reasonable, but should be validated.
Increase min_pending_latency to a non-zero value (it defaults to 0 for paid apps) and see if setting max_pending_latency explicitly makes a difference.

Load testing
Since the above changes affect scaling properties of the site, would be good to know about
Keeping with the Go theme, some tools that can be used for load testing the site:

https://github.com/tsenart/vegeta has a basic CLI interface that should be capable of what is needed
https://github.com/grafana/k6 is a neat tool I had not seen before which can do scripting more thoroughly

docs: https://k6.io/docs/getting-started/running-k6/

For more realistic testing, perhaps something with puppeteer? From here: https://stackoverflow.com/a/57607950

https://github.com/svenkatreddy/puppeteer-loadtest
https://github.com/thomasdondorf/puppeteer-cluster described in https://stackoverflow.com/a/52233124

Seeing basically flat counts a this point. Seems the extras may have been due to App Engine version configurations rather than something specific to the individual app versions.
Closing this out. Last 6 weeks of instance counts:


fix typo on plans.mdx

I am submitting this small MR to fix a typo I found while reading the docs. Thanks!

Thanks @msholty-fd! I've cherry-picked your change over here:

https://github.com/liveblocks/liveblocks/pull/1433


Unable to load module

With three in the latest version (0.142.0) if I try to use @react-three/postprocessing I get an error:
 Error: Cannot find module '/xxx/node_modules/three/examples/jsm/capabilities/WebGL'
Which I could track back to this package, it seems that your require statement isn't valid anymore.
Is there a way to fix this?
thanks

Yeah this effect needs that "WebGL.js" module from three.js' demo folder to check if WebGL2 is available. I just inlined that function now and removed the import of the "WebGL.js".
Could you test if the issue is resolved in the newest version (2.0.3)?


Merge Ryan's Cleanup and Tom's maas 2.0 changes

Shouldn't these changes be added to master so master actually supports the new version of maas?

Not sure what's going on here. version 2.0.0 is on rubygems: https://rubygems.org/gems/knife-maas. I'll close this for now, you can reopen it with none of the merge conflicts if you want.


Provide an Insert Snippet command ID

Could you please provide a command ID for the Insert Snippet command please so we can trigger it via a keybind?

Do you want to insert a snippet with keybinding https://code.visualstudio.com/docs/editor/userdefinedsnippets#_assign-keybindings-to-snippets or to open a dialog?

I want to open the quick pick triggered by the Insert Snippet command palette command:

You can do that without specifying an argument:
{
	"key": "ctrl+shift+9",
	"command": "editor.action.insertSnippet"
}

Awesome thank you, I didn't find this command anywhere.


Bug: SELECTION_CHANGE_COMMAND is not triggered when [cmd+a -> delete/backspace]

Lexical version: latest (12.0)
Steps To Reproduce

Open lexical and type some text, have debug mode to display all commands
Press cmd+a (ctrl+a), then delete/backspace
No SELECTION_CHANGE_COMMAND is triggered

Link to code example:
https://codesandbox.io/s/lexical-rich-text-example-5tncvy
The current behavior
When removing character by character or selecting a bulk with mouse and then removing, SELECTION_CHANGE_COMMAND triggers, however, when selecting text with cmd/ctrl+a and then removing  SELECTION_CHANGE_COMMAND does not trigger.
The expected behavior
SELECTION_CHANGE_COMMAND should trigger when [cmd+a -> delete/backspace]
https://github.com/facebook/lexical/assets/43103024/7534e56a-c0a4-4ee1-832e-13411ffc1904

Is there a workaround for this?


'<' operator is reserved for future use

The instructions indicate that to "Change the default Linux distribution installed
By default, the installed Linux distribution will be Ubuntu. This can be changed using the -d flag.
To change the distribution installed, enter: wsl --install -d .
BUT
At line:1 char:18

wsl --install -d
The '<' operator is reserved for future use.

CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
FullyQualifiedErrorId : RedirectionNotSupported

No issue template.


improve documentation to prevent build failures (google analytics)

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I am mindful of the project scope

Proposal
At the hugo blox documentation on Analytics there are snippets of code that help us to get quickly going on activating e.g. google analytics.
However activating this without further ado, breaks hugo builds of the site:
error calling partial: "C:\Users\ferna\AppData\Local\hugo_cache\modules\filecache\modules\pkg\mod\github.com\!hugo!blox\hugo-blox-builder\modules\blox-analytics@v0.1.0\layouts\partials\blox-analytics\services\google_analytics.html:5:24": execute of template failed: template: partials/blox-analytics/services/google_analytics.html:5:24: executing "partials/blox-analytics/services/google_analytics.html" at <site>: invalid value; expected bool

As mentioned by @gcushen in the discord channel, adding this snippet of code fixes the issue.
features:
  privacy_pack:
    enable: false

It would be nice if the documentation is improved, at least a brief mention with a link to the Privacy section of the documentation would suffice.
e.g. something along the lines of:
Please notice that the analytics functionality interacts with other site params, such as those documented under Privacy. In some cases enabling analytics without disabling the privacy_pack feature may result in build failures.
Moreover, perhaps Privacy should have a section on its own (e.g. a link under Reference on the left navbar). As it is currently hidden under Customization.
Motivation and context
It would improve the documentation, and would help users avoid build failures or quickly find solutions.

However activating this without further ado, breaks hugo builds of the site:

This was already fixed after the issue was first reported. The privacy_pack configuration is no longer explicitly required in order to use Google Analytics.

Moreover, perhaps Privacy should have a section on its own (e.g. a link under Reference on the left navbar). As it is currently hidden under Customization.

Thanks for the suggestion, we've moved the Priacy docs to its own page and clarified the current privacy features: https://docs.hugoblox.com/reference/privacy/


Complete example of install-server goal

I'm struggling with install-server goal.
I have created a pom.xml with a serverHome of a empty directory:
c:/dev/wlp-2<IP_ADDRESS>-x
If I read the docs a mvn liberty:install-server command should install a liberty from repository, but I get this error message.
[ERROR] Failed to execute goal net.wasdev.wlp.maven.plugins:liberty-maven-plugin:1.2-SNAPSHOT:install-server (default-cl
i) on project kundeside-server: CWWKM2100E: When serverHome attribute is set, it must point to a directory that contains
lib/ws-launch.jar. -> [Help 1]
Probably I don't understand how to do this, so I request a better config with a working example.
I thougth the serverHome was neccesary to tell the plugin where to install the server binaries ? And the same setting is to tell other goals where the server is located ?

If you are installing Liberty using the repository option, you can configure where it gets installed using the assemblyInstallDirectory parameter. The installDirectory parameter is used if you just want to point to an existing Liberty installation. There are a few different ways the plugin can be configured with Liberty profile. We tried to describe these options in the Liberty installation configuration section. If there is something missing or unclear there please let us know and we can try to address it.

Currently I am using the jar to install my liberty. I might have miss understood the install guide but how would I got about install with the liberty-plugin using the wlp jar ?

Hi @mcmorab has updated the documentation for the install-server goal, this contains more examples about the usage. Take a look to the install-server documentation.


Android registration "android. int. ACTION-DECODE-DATA" triggers soft keyboard

Is your feature request related to a problem? Please describe.

I registered an infrared scanning event，Simultaneously triggering the soft keyboard while obtaining the encoding。
Describe the solution you'd like
How can I obtain encoding without triggering the soft keyboard？
I hope that when the interface only has buttons and labels, the soft keyboard will not pop up
Describe alternatives you've considered
No response
Additional context
No response

Uploading d0581f87f354bc985bc419c84d98f3db.mp4…

[
https://github.com/AvaloniaUI/Avalonia/assets/141573398/13ce531c-2d67-422f-b21e-cbb5db50213d
](url)

UI

I hope that when the interface only has buttons and labels, the soft keyboard will not pop up。

It seems even worse now,The command of the button is constantly triggered。Triggered by infrared scanning。

Hello, does this issue still occur? If it does, could you provide a minimal reproduction.


[Question] Should support to compare different generic type variables?

To reproduce
Code snippet to reproduce

//# publish
module 0x42.EQ{
    public test_eq<F, S>(f: &F, s: &S): bool {
    label b0:
        return move(f) == move(s);
    }
}

//# publish
module 0x42.M {
    struct T has drop { f: u64 }
    struct U has drop { f: u64 }

    public new_t(a: u64): Self.T {
    label b0:
        return T { f: move(a) };
    }

    public new_u(a: u64): Self.U {
    label b0:
        return U { f: move(a) };
    }
}

//# run
import 0x42.M;
import 0x42.EQ;

main() {
    let t: M.T;
    let t2: M.T;
    let u: M.U;
label b0:
    t = M.new_t(1);
    t2 = M.new_t(1);
    u = M.new_u(1);

    assert(EQ.test_eq<M.T,M.T>(&t, &t2), 42);
    assert(!EQ.test_eq<M.T,M.U>(&t, &u), 43);
    return;
}

Stack trace/error message
task 0 'publish'. lines 1-7:
Error: Unable to publish module '00000000000000000000000000000042::EQ'. Got VMError: {
    major_status: EQUALITY_OP_TYPE_MISMATCH_ERROR,
    sub_status: None,
    location: 0x42::EQ,
    indices: [(FunctionDefinition, 0)],
    offsets: [(FunctionDefinitionIndex(0), 2)],
}

Expected Behavior
The F and S may be the same, so f == s is possible.
Additional context
The bytecode verifier requires the two operands of Eq and Neq must been same.
https://github.com/move-language/move/blob/0fe2e6ce5af811d68b8a995b7da3f4c4ecc485fa/language/move-bytecode-verifier/src/type_safety.rs#L646-L654
if we release the operands type check in the type_safety, and we need to check the container type in the VM runtime, otherwise the last assert will abort.

As discussed, this is intended behavior and not a bug.
Although sometimes we need to compare different generic types of variables, this is difficult to implement. if we implement such a method in Rust, need to write code like the following:
fn test_eq<F: Debug + std::cmp::PartialEq<S>, S: Debug + std::cmp::PartialEq<F>>(f: &F, s: &S) {
    if f == s {
        println!("{:?} == {:?}", f, s);
    } else {
        println!("{:?} != {:?}", f, s);
    }
}

#[test]
fn test() {
    let f = 1;
    let s = 2;
    test_eq(&f, &s);
}

Closing since this is not a bug. Feel free to open a separate issue for comparing values of different types if there is a compelling motivation for this!

To reproduce
Code snippet to reproduce
//# publish
module 0x42.EQ{
    public test_eq<F, S>(f: &F, s: &S): bool {
    label b0:
        return move(f) == move(s);
    }
}

//# publish
module 0x42.M {
    struct T has drop { f: u64 }
    struct U has drop { f: u64 }

    public new_t(a: u64): Self.T {
    label b0:
        return T { f: move(a) };
    }

    public new_u(a: u64): Self.U {
    label b0:
        return U { f: move(a) };
    }
}

//# run
import 0x42.M;
import 0x42.EQ;

main() {
    let t: M.T;
    let t2: M.T;
    let u: M.U;
label b0:
    t = M.new_t(1);
    t2 = M.new_t(1);
    u = M.new_u(1);

    assert(EQ.test_eq<M.T,M.T>(&t, &t2), 42);
    assert(!EQ.test_eq<M.T,M.U>(&t, &u), 43);
    return;
}

Stack trace/error message
task 0 'publish'. lines 1-7:
Error: Unable to publish module '00000000000000000000000000000042::EQ'. Got VMError: {
    major_status: EQUALITY_OP_TYPE_MISMATCH_ERROR,
    sub_status: None,
    location: 0x42::EQ,
    indices: [(FunctionDefinition, 0)],
    offsets: [(FunctionDefinitionIndex(0), 2)],
}

Expected Behavior
The F and S may be the same, so f == s is possible.
Additional context
The bytecode verifier requires the two operands of Eq and Neq must been same.
https://github.com/move-language/move/blob/0fe2e6ce5af811d68b8a995b7da3f4c4ecc485fa/language/move-bytecode-verifier/src/type_safety.rs#L646-L654
if we release the operands type check in the type_safety, and we need to check the container type in the VM runtime, otherwise the last assert will abort.


Implement edit button on home page Wish Wednesday

There's an edit button on the figma, and I'm not 100% sure what it's use case is. Currently it's commented out but we should implement before final deploy

Likely won't need this. Can be edited through manage page.


Access to passcode via curl when using SAML idp (siteminder)

What version of UAA are you running?
74.x
How are you deploying the UAA?

as part of a commercial Cloud Foundry distribution (Tqnzu Qpplicqtion Services)

What did you do?
curl siteminderserver/basic to get de SMSESSION
curl uaaserver/passcode with the SMSESSION
What did you expect to see? What goal are you trying to achieve with the UAA?
Get the passcode in the response
What did you see instead?
302 redirect to uaaserver/login
Please include UAA logs if available.
No log actually

@defus, what is the exact version (including minor and patch version) of the UAA 74? Also, it appears that you use siteminder as the external SAML IDP for UAA. In that case, it is likely that uaa passcode endpoint behavior depends on siteminder and the problem resides in siteminder side.

Closing due to no activity


Specific accuracy of llama models

Hello, I saw a graph showing the results of llama2 models (foundation model and chat model) in the paper.
Could you tell me the specific accuracy of them?

Here's a JSON object with the results of the LLaMA-2 models. keys are model names, value is a list of tuples where each tuple is (gold position, accuracy):
{
    "Llama-2-7b-chat-hf": [
        [
            0,
            0.428842504743833
        ],
        [
            4,
            0.41783681214421253
        ],
        [
            9,
            0.4459203036053131
        ],
        [
            14,
            0.45692599620493357
        ],
        [
            19,
            0.5540796963946869
        ]
    ],
    "Llama-2-13b-chat-hf": [
        [
            0,
            0.5149905123339659
        ],
        [
            4,
            0.4774193548387097
        ],
        [
            9,
            0.47666034155597725
        ],
        [
            14,
            0.5244781783681215
        ],
        [
            19,
            0.5882352941176471
        ]
    ],
    "Llama-2-70b-chat-hf": [
        [
            0,
            0.573055028462998
        ],
        [
            4,
            0.538899430740038
        ],
        [
            9,
            0.5472485768500949
        ],
        [
            14,
            0.6003795066413662
        ],
        [
            19,
            0.6998102466793169
        ]
    ],
    "Llama-2-7b-hf": [
        [
            0,
            0.23440453686200377
        ],
        [
            4,
            0.23100189035916824
        ],
        [
            9,
            0.23553875236294897
        ],
        [
            14,
            0.24914933837429112
        ],
        [
            19,
            0.410586011342155
        ]
    ],
    "Llama-2-13b-hf": [
        [
            0,
            0.43629489603024574
        ],
        [
            4,
            0.2166351606805293
        ],
        [
            9,
            0.21323251417769376
        ],
        [
            14,
            0.23251417769376181
        ],
        [
            19,
            0.40869565217391307
        ]
    ],
    "Llama-2-70b-hf": [
        [
            0,
            0.499054820415879
        ],
        [
            4,
            0.4170132325141777
        ],
        [
            9,
            0.41776937618147447
        ],
        [
            14,
            0.4487712665406427
        ],
        [
            19,
            0.5705103969754254
        ]
    ]
}

Hi, amazing work @nelson-liu as always!
A noob question: I was just wondering about the postprocessing of the generated answer. If I understand your code correctly, you basically took the raw output directly. I tried generating answers for NQ open using LLaMA2 7b chat model and it tends to be a bit verbose in its generation, starting the answer with a sentence like "Based on the provided search results, the ...". What strategy did you use to mitigate this?

Hi @aryopg , thanks for the kind words! Yes, we took the LLaMA-2 chat model outputs directly. The chat models are indeed quite verbose---this ends up making EM / F1 a meaningless metric, but there's still some signal in best substring EM (i.e., do any of the gold answer strings show up in the generation), especially if the goal is to compare performance of changing the answer-bearing paragraph (this paper is somewhat relevant in this regard https://arxiv.org/abs/2305.06984 ), since the filler / boilerplate text generated by the chat model basically never contains the answer. I think the relative comparisons between settings is very trustworthy, but it's quite possible that the absolute performance %s differ from human eval by a few percentage points (but this paper is mostly concerned with relative comparisons anyway, i.e., start vs. middle vs. end).
This issue above is primarily why we used best substring EM as our metric of choice. In a perfect world, I would have liked to do some sort of model-based eval vs. just relying on string overlap, but from manually looking at the results I didn't see many where it would have made a huge difference.
I think this becomes a little more of a problem when you have models that are very verbose in ways that aren't just boilerplate (e.g., consider a model that repeats the input text before answering---copying the input to the output would result in perfect best substring EM). We didn't observe this in any of the models that we tested, but it's possible that future models might require something a bit more sophisticated than best substring EM. Picking the right metric for the job can ultimately depend on looking at model behavior.
Anyway, I realize this is a little bit of a brain-dump---let me know if this answered your question / if you have any follow-up questions.

Hi @nelson-liu , thank you very much for the answer! It makes total sense, and we're also planning to use best substring EM as that would be the fairest metric in this case.  I can indeed see a very verbose model, particularly if you prompt it to do exactly that (e.g. CoT and all that jazz). Probably we should use/introduce metrics that are independent of this. Wonder if something like BERTScore (with some tweaks) would help here.
Keep the brain-dump coming tho! In the constraint of my question, you've sufficiently answered it! We can move the discussion to emails instead :)

I can indeed see a very verbose model, particularly if you prompt it to do exactly that (e.g. CoT and all that jazz). Probably we should use/introduce metrics that are independent of this. Wonder if something like BERTScore (with some tweaks) would help here.

Yeah, I can see something like that working reasonably, but there are still cases where you need to actually understand the model response. In some sense, evaluating the responses is just another QA task, one where best subspan em seems to correlate quite well on (at least for some models).
Part of me feels like the most robust solution would probably be just eval with a LM (e.g., gpt-4-turbo or some fine-tuned open model). you'd just give it:

the question
the gold answer
the model response

and ask it to assess whether the model response accurately conveys the gold answer. we tried this for a bit with gpt-4 and it worked quite well,l but i ended up not doing it for the paper results because it was unnecessary cost and I didn't think was really telling us anything that best subspan EM wouldn't. If i were redoing this project today and had a model that was more verbose (e.g., claude 2.1 seems to really enjoy rephrasing its input text, maybe because it's trained with some sort of context distillation), I think the LM eval is the first thing I'd try.


Incorrect data dimensions lead to somewhat misleading error message

While updating some code from 2.3.0 to 2.7.0 I noticed I was apparently incorrectly passing vertex data to Mesh's vertex.position: the dimensions set on the data array included the vector dimension itself, e.g. for 5 vertices I would pass {5, 3, 1}. This leads to the error (ospray::Mesh must have 'vertex.position' array with element type vec3f), even though the correct element type was set. So it took me some time to figure out what the actual issue was as the error reported isn't accurate (and the dimensions don't seem to be checked in this particular case).
Here's an example:
#include <ospray/ospray_cpp.h>

static void
error_func(void* /*userdata*/, OSPError error, const char *details)
{
    printf("OSPRAY ERROR: %d (%s)\n", error, details);
}

static void
status_func(void* /*userdata*/, const char *message)
{
    printf("OSPRAY STATUS: %s\n", message);
}

struct vec3ul {
    uint64_t x, y, z;

    vec3ul(): x(0), y(0), z(0) {}
    vec3ul(uint64_t xx, uint64_t yy, uint64_t zz): x(xx), y(yy), z(zz) {}
};

namespace ospray {
OSPTYPEFOR_SPECIALIZATION(vec3ul, OSP_VEC3UL);
}

ospray::cpp::CopiedData
dup(ospray::cpp::CopiedData& d)
{
    return d;
}

int main(int argc, const char **argv)
{
    ospInit(&argc, argv);

    ospray::cpp::Device device(ospGetCurrentDevice());
    ospDeviceSetErrorCallback(device.handle(), error_func, nullptr);
    ospDeviceSetStatusCallback(device.handle(), status_func, nullptr);

    vec3ul num_vertices { 4, 3, 1 };
    vec3ul byte_stride { 0, 0, 0 };

    float vertex[] = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 };

    ospray::cpp::CopiedData v(vertex, OSP_VEC3F, num_vertices, byte_stride);

    ospray::cpp::Geometry mesh("mesh");
    mesh.setParam("vertex.position", v);
    mesh.commit();
}

melis@juggle 21:38:~/concepts/ospray-python$ g++ -I ~/software/ospray-2.7.0.x86_64.linux/include/ t_data.cpp  -L ~/software/ospray-2.7.0.x86_64.linux/lib/ -lospray -ot_data
melis@juggle 21:41:~/concepts/ospray-python$ ./t_data
OSPRAY ERROR: 1 (ospray::Mesh must have 'vertex.position' array with element type vec3f)

If I change num_vertices to be {4, 1, 1} the error goes away.

Thanks for improving OSPRay's warning messages, loosely related to #396. Actually the dimensions are checked, leading to the error message: A one-dimensional array for  vertex.position is expected, whereas you passed a 2D array of size 4×3 of type vec3f (note the element type is the vector, not float). However, this is not clear from the message. How about
ospray::Mesh must have 'vertex.position' 1D array with element type vec3f

Yes, that would be an improvement. What would be even better in cases where a check on data type/size has failed is to also (if that's feasible) report what was erroneously passed, to provide even more information. E.g. ospray::Mesh must have 'vertex.position' 1D array with element type vec3f, got 2D array of vec3f instead.