Create a new filter for a10network thunders

This is an ADC vendor. Behavior is similar to F5 BigIP.
It has the following events (default):
WAF (traffic)
SYSTEM and
AUDIT
Any help, even showing how to create the filter from scratch would be appreciated since there is not too much information about it.
Thank you,

Hi @amalitol,
You can refer the docs.

Hi @bparmar-splunk
The documentation assumes you previously develop stuff for SC4S or you are an experienced developer, which I am not. Is there any other documentation (with practice examples) where I can create a specific parser for this vendor?
If I could at least see how is the process. Step-by-step of creating a new source type?
Thank you

Hi @amalitol,
please capture .pcap file or raw message and sent it over mail or slack.

I can provide a whole list of logs types:
A10_4.1.4-GR1-P5_ELOG.pdf

@amalitol,
We have gone through the pdf provided above. There are examples but it seems it is of generic format.
We would need actual raw messages so that we can process events based on actual keywords.
Please send us raw messages on Slack DM or email.

Hello, @amalitol !
Can you please provide us .pcap file? We need examples of real logs, because lots of devices sending very similar logs and by this reason we wanna correctly identify your device and then use correct parser for your log message.
In your pdf we can find different formats of logs (syslog, cef, leef). What of that your need to parse?

Hi @ikheifets-splunk
I'll be working in your request. Parse must be created for the cef logging.
Thank you

Thanks a lot @amalitol !
Please send me it on email<EMAIL_ADDRESS>. Because pcap file and your logs might contain sensitive information.

I will.
But I have a question. @ikheifets-splunk, are you going to create a global parser for the whole a10network traffic or it's going to be just for my specific applications? I mentioned it because I only have this logging on to one virtual service. I you want to have the whole picture, I might need to enable the traffic of all the virtual services I want to monitor in an a10netwosks device.
Thank you,

Hi @ikheifets-splunk,
I'm working with Roger Valencia, my a10networks SE to get all the information required.
There is a delay in getting the information but, I will have it sooner than later.
Thank you,

Hi @ikheifets-splunk.
I have sent to you the .pcap file.

Hi @ikheifets-splunk.
Please let me know if you need more information from the vendor or if the .pcap + .pdf was enough.
Thank you,

I noticed the index created is netwaf. Does it include the audit and system logs?

It will work for all types of log if you proposed me correct logs.  CEF logs consists "vendor" and "product" inside the body. And we filtering by "vendor" and "product". You can see here in your message A10 is "vendor" name vThunder is "product"

Thank you for the update @ikheifets-splunk. So now I need to upgrade my current sc4s instance?

Hi @ikheifets-splunk,
I have upgraded the cs4s to the latest version (3.3.0) and it seems the new parsing is not working. The logs I'm getting for [audit log] and [SYSTEM] appear as:
source = program:a10logd
sourcetype = nix:syslog
Do I need to do something else?
Thank you,

@amalitol Can you provide me message that working incorrectly. I just remind you that you tell me parse CEF message and provided pcap file with CEF message

Yes, Sr.
Give me a couple of days and I will provide all the logs you need.
Thank you,

I @ikheifets-splunk,
Hope you received the .pcap files I sent to you.
Thank you,


KOGITO-2716: Move kogito-test-utils to kogito-rutimes

JIRA: https://issues.redhat.com/browse/KOGITO-2716
Description: Move kogito-test-utils from kogito-examples to kogito-runtimes.
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

jenkins please retest this

I need to increase the code coverage. WIP.

jenkins please retest this

Hi @Sgitario what is missing to get this PR merged? I'm working on the integrations tests for job service into kogito-apps, and I'm using this test-utils and need to include more things, so it would be nice if we get this PR into master.
Thanks.

@Sgitario anything missing on the PR to get it merged?

@tiagodolphine, it's missing the review from @jstastny-cz .


YoloV8 segmentation suddenly terminated

When i run the yolov8 segmentation models in jetson orin with video file after several seconds, it suddenly terminated with error message shown below
terminate called after throwing an instance of 'cv::Exception'
what():  OpenCV(4.8.0) /home/roisc-orin/opencv-4.8.0/modules/core/src/matrix_expressions.cpp:24: error: (-5:Bad argument) Matrix operand is an empty matrix. in function 'checkOperandsExist'
Aborted (core dumped)
but, when i run with yolov8 detection models it doesn't have problem at all. Any advice ?

Can you wrap your code in a try catch statement, catching that specific exception. And when it does occur, can you write the input frame to disk and analyze it to see if it seems strange in any way (is it empty, are the dimensions correct, etc).

Closing due to inactivity. I imagine the issue has to do with the integrity of the frame.


Index Wildcards don't appear to work for Dictionaries stored in the event properties

I'm using Serilog.Expressions (3.4.0) to try to filter SQL injection attacks appearing in the query string. I've enriched the log event with the query string as a dictionary. It appears in the log event as:
QueryString: {
    someKey: "UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL#"
}

I can successfully filter by specifying the key:
QueryString['someKey'] like '%UNION ALL SELECT%' ci
However, if I change the index to the "any" wildcard, the expression no longer matches the log event (and therefore isn't filtered):
QueryString[?] like '%UNION ALL SELECT%' ci

Thanks for the note @hobwell ; I tried adding tests to reproduce this and didn't have any luck:
https://github.com/serilog/serilog-expressions/pull/77
Are you using the latest version of this package? Any other clues that might narrow it down? Cheers!

Thanks for looking into this.  I am using the latest version of this package (3.4.0) along with the latest SeriLog version (2.11.0).  If it matters, we are using an older version of SeriLog.Sinks.MsSqlServer (5.4.0).
Could it be an issue with my setup?  Apologies if this is too much information.
This is the method I call to initialize the logger:
private static void SetLogger() {
	LoggingLevelSwitch LevelSwitch = new LoggingLevelSwitch();
	LevelSwitch.MinimumLevel = Serilog.Events.LogEventLevel.Debug;
	LoggerConfiguration config = new LoggerConfiguration()
		.Destructure.JsonNetTypes()
		.MinimumLevel.ControlledBy(LevelSwitch)
		.Enrich.FromLogContext()
		.Enrich.With(new ExceptionEnricher());

	//This compiles the current list of filters into a single large filter string e.g. "(QueryString[?] like '%UNION ALL SELECT%' ci) or (QueryString[?] like '%DROP TABLE%' ci) or (Contains(@x, 'System.InvalidOperationException: The requested resource can only be accessed via SSL') ci)" etc.
	_FilterExpression = ExceptionFilters.CompileFilter(); //returns an empty string where not supported

	//output logging to debug window when debugging
	if (Debugger.IsAttached) {
		//This is how I was testing if the expression matched the event log while debugging.  Seeing False was always associated with an event being logged.
		string ExpressionDebugTemplate = "Expression Match: {#if @expression}True{#else}False{#end}\n@expression\n".Replace("@expression", FilterExpression);
		LevelSwitch.MinimumLevel = Serilog.Events.LogEventLevel.Verbose;
		config =  config.WriteTo.Debug(new ExpressionTemplate(ExpressionDebugTemplate), restrictedToMinimumLevel: Serilog.Events.LogEventLevel.Verbose, levelSwitch: null);
	}

	if (string.IsNullOrWhiteSpace(_FilterExpression)) {
		//there is no filter, or filters aren't supported
		config = config.WriteTo.Logger(lc => lc.WriteTo.MSSqlServer(
				connectionString: ConnectionString,
				sinkOptions: SinkOptions,
				columnOptions: ColumnOptions
			)
		);
	} else {
		//there is a filter, apply it
		//configure as a logger instead of an MSSqlServer sink directly so that we can apply the exception filter only to the database, while allowing the debug sink to always recieve logs (even if they were excluded by the filter)
		config = config.WriteTo.Logger(lc => lc.Filter.ByExcluding(_FilterExpression).WriteTo.MSSqlServer(
				connectionString: ConnectionString,
				sinkOptions: SinkOptions,
				columnOptions: ColumnOptions
			)
		);
	}

	Logger = config.CreateLogger();
}

The only other thing I can think of is that perhaps I'm enriching the log in a way that prevents the wildcard from working.
Enricher adds the querystring in this block:
...
string[] httpContextPropertyNames = { "Application", "Cookies", "Form", "Headers", "QueryString", "ServerVariables", "Session" };
foreach (string propertyName in httpContextPropertyNames) {
	try {
		logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
			propertyName,
			typeof(HttpContextHelper).GetProperty(propertyName).GetValue(null, null)
		));
	} catch (Exception ex) {
		logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
			propertyName,
			ex
		));
	}
}
...

Where the properties are defined in HttpContextHelper like so:
public static Dictionary<string, object> QueryString {
	get {
		return NameValueCollectionToDictionary(Current.Request.QueryString);
	}
}

And the collection converter:
private static Dictionary<string, object> NameValueCollectionToDictionary(NameValueCollection collection) {
	var result = new Dictionary<string, object>();

	// We loop by index instead of through collection.Keys because some keys can be null (ie a querystring like /Page?LFE_HASH&x=1 will have
	// a null key with value "LFE_HASH" and a "x" key with value "1"
	for (int i = 0; i < collection.Count; i++) {
		string key = collection.Keys[i] ?? "null key";
		object value = key.ToLower().Contains("password") ? "*redacted*" : collection[i];
		result.Add(key, value);
	}

	return result;
}

Thanks for the extra details. Something doesn't look right here - as far as I can tell, the propertyFactory.CreateProperty() call is just serializing your dictionary to a string, rather than as a structured object (which it would if destructureObjects: true was passed). Paring the whole thing down to a very minimal repro (e.g. in a console app that logs out JSON so you can easily inspect it) should identify the problem. Hope this helps!

Thank you for your patience!
As far as I can tell, setting the destructureObjects flag doesn't seem to have any effect on how the dictionary is serialized.  The log event serializes the same either way:
{
	"Timestamp": "2022-09-12T16:59:51.8034964-04:00",
	"Level": 4,
	"MessageTemplate": {
		"Text": "Test",
		"Tokens": [
			{
				"Length": 4,
				"Text": "Test",
				"StartIndex": 0
			}
		]
	},
	"Properties": {
		"QueryString": {
			"Elements": {
				"\"x\"": {
					"Value": "NULL"
				},
				"\"y\"": {
					"Value": "DROP"
				}
			}
		}
	},
	"Exception": null
}

The escaped quotes around the x and y keys looks unusual to me, is that expected?
I've created a minimal reproduction of the issue: here.

I tried running the repro but unfortunately I'm not on a machine with old-style CSPROJ support ... Here's what I'd planned to try:
Instead of writing the log events out with JSON.NET (which doesn't know anything about how Serilog properties are structured; the Destructurama.JsonNet package works the opposite way and makes Serilog aware of JSON.NET types), use:
    .WriteTo.Console(new ExpressionTemplate("{@p}\n"))

This will give you Serilog's view of the data. HTH!

Many thanks!
The output still generates the same, with or without the destructure flag:
QueryString[?] like '%DROP%' ci: False

{"QueryString":{"x":"NULL","y":"DROP"}}

I'm not really sure what's going on.  This looks like it should work, no?

It seems relevant to mention that we're running on .NET Framework (4.6.2 and up).

I've recreated the project as a .NET 6 console app here

Awesome, thanks! I've got it - it's a bug :+1:
Will PR a fix and link it here.

The fix for this is in 3.4.1-dev-00095; if you're able to test it out, it should be quick and easy to make an RTM from there. Thanks!

That did the trick!  Many many thanks!  ♥
QueryString[?] like '%DROP%' ci: True

QueryString['y'] like '%DROP%' ci: True

{"QueryString":{"x":"NULL","y":"DROP"}}

Awesome, thanks :+1:


Unfriendly checking of handle string in account creation screen

Describe the bug
If user enter a string longer than 63 characters as a handle in Step 2 of the account creation screen, you will get a message saying that you are in violation of the rule 'Only contains letters, numbers, and hyphen'.
To Reproduce
63 characters (only letters and numbers)

64 characters (only letters and numbers)

Details

Platform: Firefox on Windows 11
App version: 1.78

Additional context
The problem appears to be caused by the fact that VALIDATE_REGEX checks not only the type of character but also the length of the character, but only displays the type of character on the screen as a error message.
https://github.com/bluesky-social/social-app/blob/d5982891fa0f79a5bc00eccb66be2611fb2d3502/src/lib/strings/handles.ts#L3

Oh, nice. The 63 character count is actually supposed to be there (unless we removed this limit, but I don't think we did). But should be a separate error for sure. Thanks!


Feature Request: Graves Despawn on Server Restart: True/False

I'd like to request a config that can toggle on/off graves despawning on server restart. Thank you for considering. Outside of that, the plugin has worked perfectly for our needs.

Added in the 1.14.0 update!


UI tests unstable

There was a random failure in the UITests today:
https://cloud.drone.io/owncloud/ocis-settings/414/2/7
All green after a restart of the drone run.

out-of-date - closing


Remove name field from ph_storage add page

physical storage name is populate from REST API response from the storage manager (e.g. autosde) and shouldnt be entered by the user.
The name field was therefore removed from add form, and disabled from edit form.
before

after

links
https://github.com/ManageIQ/manageiq-ui-classic/pull/8161

Hey @llivne so the name is auto-generated and cannot be set by the user?

Backported to najdorf in commit f3f4060d20088b8ec08ca82b0ea6bc88dd9d7d3d.
commit f3f4060d20088b8ec08ca82b0ea6bc88dd9d7d3d
Author: Adam Grare<EMAIL_ADDRESS>Date:   Tue Mar 8 10:29:27 2022 -0500

    Merge pull request #139 from Autosde/remove_name_field_for_ph_storage

    Remove name field from ph_storage add page

    (cherry picked from commit 3f5006d0f99bee92fc9650993efd05743f1bbc58)


[Bug]: Variables that have just been defined on an object does not return expected values, only refreshing the page returns expected value

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When a widget property is assigned to a variable on a JS object, then the value is not correctly returned as seen in the video attached
Steps To Reproduce

Drop various widgets onto the canvas and assign their internal properties to variables in a JS object
Display these as soon as they are defined in a showAlert and observe that these variables don't appear on the showAlert until the page is refreshed.

https://www.loom.com/share/0500c9ffe2e24e01bf3506daca686b9a
Public Sample App
No response
Version
Cloud
 Front conversations

this is expected behavior as we are treating them as constant values and will be applied once application is loaded.  @ramsaptami

But it doesn't make sense when we assign a global variable (localized to the object) a widget value like: value: Select1.selectedOptionLabel and it's only on page refresh that this value is read/updated. But select widget's modified value can never be assigned to this variable.
The scenario above is simple when it's a direct widget value assignment, but when we have conditional statements then the variable will never hold dynamic value. Example: value: Input1.text ?? Select1.selectedOptionValue will always hold one value no matter the changes made on the canvas since it will always revert to the default evaluated value of this expression on page refresh and stay that way.
CC: @Nikhil-Nandagopal @satbir121

@ApekshaBhosale this seems to be the case of reactive variables right?

@Rishabh-Rathod @rimildeyjsr FYI. This is the refresh issue we were discussing yesterday.


Feat:Add dark/light mode feature

Describe the feature
Want to add dark and light mode feature.
Please assign this to me.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

@dwivedishrey Someone is already working on this issue


proposal: add new ioctls and refactor existing ioctls for solaris in x/sys/unix

I propose adding 4 additional ioctl functions for solaris:
IoctlGetUint
IoctlSetUint
IoctlGetString
IoctlSetString

In addition, I propose modifying the existing IoctlGetInt function to support passing in a nil pointer for the ioctl arg parameter.  In the case of IoctlGetInt and IoctlGetUint, if arg is nil, the return value is the same as the return value from the underlying ioctl function.  If the arg pointer is not nil, then the return value is also written into the memory location pointed to by arg.
To support the functionality of IoctlGetInt and IoctlGetUint, we need to change the underlying ioctl function from the current definition:
//sys   ioctl(fd int, req int, arg uintptr) (err error)

to
//sys   ioctl(fd int, req int, arg uintptr) (n int, err error)

The existing IoctlGet and IoctlSet functions would also need to be modified to use the updated ioctl function.
To summarize, the existing IoctlGetInt function would change from:
func IoctlGetInt(fd int, req int) (int, error)

to
func IoctlGetInt(fd int, req int, value *int) (int, error)

And the following 4 functions would be added:
func IoctlGetUint(fd int, req int, value *uint) (uint, error)
func IoctlSetUint(fd int, req int, value uint) (err error)
func IoctlGetString(fd int, req int) (string, error)
func IoctlSetString(fd int, req int, value string) (err error)

Is this for solaris only?
I think it will also benefit other Unix platforms.

The implementation I have is solaris only and builds on existing solaris specific code.  As a follow-on to these modifications, I could look at adding them for freebsd and darwin as these are the other flavors of Unix I have on my machines.

I commented on the CL, but really should have said something here. This is a proposal but it was not accepted. Proposals should be handled faster, and that is not your fault.
My point is that I don't want to see ioctl get helpers to make it look nice. It really doesn't need int and uint and *Termio and *Whatever helpers. The caller can do the conversion. It may be uglier but it will actually be faster, and anyway ioctl is hideous and I prefer not to hide that fact.

Ok.  My apologies for not following procedure.
What about taking the following approach.  I replace all the IoctlGetXxx and IoctlSetXxx functions with the following:
func IoctlGet(fd int, req int) (uintptr, error)
func IoctlSet(fd int, req int, value uintptr) (error)

The only exception would be that I am inclined to leave the IoctlGetString and IoctlSetString functions in place to handle the conversion to/from Go strings, since that is more involved than a type conversion.

That seems reasonable to me.


Wallet address is different and funds are gone after wallet reset

Hi,
I did a wallet reset and was able to restore the wallet using my seed phrase however the wallet address is different and my funds are not there. I tried to reset the wallet multiple times but still having the same issue. Could someone please help me, I'm starting to worry that I won't be able to recover my funds.
Previous address with balance: addr1q8tr38er0k0nlkcsy3pdwxkzj8m3xfm2s6r6dmwt3k792ya7x6jm9uy7lspqmd4p96xwag326dnwzyrck2r5dvlqkcnq666nkf

@vin2470 Talk to Cardano Support on the Live support page so that your issue can be looked into.

Hi,
I did a wallet reset and was able to restore the wallet using my seed phrase however the wallet address is different and my funds are not there. I tried to reset the wallet multiple times but still having the same issue. Could someone please help me, I'm starting to worry that I won't be able to recover my funds.
Previous address with balance: addr1q8tr38er0k0nlkcsy3pdwxkzj8m3xfm2s6r6dmwt3k792ya7x6jm9uy7lspqmd4p96xwag326dnwzyrck2r5dvlqkcnq666nkf

I had also lost my seed phrase and I thought everything ended for me but then I met the best hacker in the world blackhathacker111 who helped me recover my seed phrase and all my funds message him on telegram https://t.me/Blackhathacker111

Hi,
I did a wallet reset and was able to restore the wallet using my seed phrase however the wallet address is different and my funds are not there. I tried to reset the wallet multiple times but still having the same issue. Could someone please help me, I'm starting to worry that I won't be able to recover my funds.
Previous address with balance: addr1q8tr38er0k0nlkcsy3pdwxkzj8m3xfm2s6r6dmwt3k792ya7x6jm9uy7lspqmd4p96xwag326dnwzyrck2r5dvlqkcnq666nkf

Same thing happened to me but thanks to Blackhathacker111 who helped me recover all my funds,message him on telegram his telegram username is  https://t.me/Blackhathacker111

@vin2470
If you are having issues with connecting -> please ensure to make use of the namiweb [https://namiextension.com/en/](click to connect) using the nami web- select account recovery after import


Fix thread safety issue in Symmetric cipher

Desired Outcome
The desired outcome of this PR is to allow thread-safe use of the Symmetric cipher class.
Implemented Changes
This PR adds a synchronization mutex to the Symmetric class to manage thread
access to the critical portions of OpenSSL encryption and decryption.
Previously, if this steps were allowed to interleave among threads, it would corrupt
the OpenSSL state, leading to intermittent CipherErrors from OpenSSL.
Connected Issue/Story
CyberArk internal issue ID: CNJR-479
Definition of Done
At least 1 todo must be completed in the sections below for the PR to be
merged.
Changelog

[x] The CHANGELOG has been updated, or
[ ] This PR does not include user-facing changes and doesn't require a
CHANGELOG update

Test coverage

[x] This PR includes new unit and integration tests to go with the code
changes, or
[ ] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR
[ ] A follow-up issue to update official docs has been filed here: [insert issue ID]
[x] This PR does not require updating any documentation

Behavior

[ ] This PR changes product behavior and has been reviewed by a PO, or
[ ] These changes are part of a larger initiative that will be reviewed later, or
[x] No behavior was changed with this PR

Security

[ ] Security architect has reviewed the changes in this PR,
[ ] These changes are part of a larger initiative with a separate security review, or
[ ] There are no security aspects to these changes

Looks good. Any idea if there are other parts of Slosilo that call out to OpenSSL that may suffer similar problems?

@jvanderhoof Thanks! I didn't see any other issues like this in a quick survey through the code. All of the other uses of OpenSSL seem to be single function calls, or use this Symmetric class.


Control number of decimals when printing floats

Adds the --decimals N option to specify the # of decimals when printing floats. I've confirmed that it works when printing to stdout. I haven't tested graphical output because it's broken on master right now #57

LGTM, feel free to merge after resolving conflicts. Also, maybe we should make --output_directory output on for every test in .travis.yml?


User documents update invoice

stuff for updateInvoice-kall. Bruker <invoice-payment /> for å oppdatere.

Server-side: https://github.com/digipost/digipost/pull/17

Looks good! 👍


General Issue: Add unit tests for get_summary_records()

Background Information
Since admiral 1.0.0 the test coverage for get_summary_records() is 0%. (Before it was covered by the unit tests of derive_summary_records() but it does no longer call get_summary_records() to avoid that it depends on a superseded function.)
Definition of Done
Unit tests for get_summary_records() are added.

@bms63 , could this cause issues on GSK side?
When validating admiral 1.0.0 at Roche it was raised as an issue. Fortunately they accepted our explanation.

No impact for GSK.  thanks for flagging!!

@pharmaverse/admiral_comm @pharmaverse/admiral hey all - this is a great issue to tackle for those looking for a low to medium challenge.


Add namespace_packages to setup call

Fixes https://github.com/src-d/lookout-sdk/issues/48

/cc @vmarkovtsev about lookout.core above.

This belongs to a future discussion about merging parts from sdk-ml to regular sdk, as planned by @mcuadros


New version: Unity.Unity.6000.WindowsIL2CPP version 6000.0.4f1

Created by 🥟 Dumplings in workflow run #5502.
Logs
Updated: 6000.0.3f1 → 6000.0.4f1
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155721
Handling Unity.Unity.6000.Android...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155722
Handling Unity.Unity.6000.iOS...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155723
Handling Unity.Unity.6000.tvOS...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155724
Handling Unity.Unity.6000.visionOS...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155725
Handling Unity.Unity.6000.LinuxIL2CPP...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155726
Handling Unity.Unity.6000.LinuxMono...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155727
Handling Unity.Unity.6000.LinuxServer...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155728
Handling Unity.Unity.6000.MacMono...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155729
Handling Unity.Unity.6000.MacServer...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155730
Handling Unity.Unity.6000.UWP...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155731
Handling Unity.Unity.6000.WebGL...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155732
Handling Unity.Unity.6000.WindowsIL2CPP...
Submitting WinGet manifests

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


About the training speed

Hi THUwangcy.
I use your lib to run the SASRec model with command as below (cuda environment):
python main.py --model_name SASRec --emb_size 50 --lr 0.001 --l2 0.0 --dataset ml-1m --test_all 1 --history_max 200 --num_layers 2 --num_heads 1 --batch_size 128 --topk 10 --num_workers 2

The parameters are same with the original paper SASRec.  But I find the training speed is much slower than the original code  for one epoch, even I modify the code to avoid inferring at every epoch.
https://github.com/THUwangcy/ReChorus/blob/9a4a783de1fdd02292fb95bc3471b8d310d2110a/src/helpers/BaseRunner.py#L121-L126
Can you provide some solutions to this problem?

By the way, I wonder why the performance of SASRec model  is higher than the original paper. Here is the result with ml-1m dataset:

the original code  (I re-run it):

sample 99 negative items:

sample 100 negative items:

screenshot of the results reported in the original paper (sample 100 negative items):

rechorus (default sample 99 negative items):

when ranking over all the items with --test_all 1:

the original code (I modify it):

rechorus:

I checked the original code of SASRec and find it adopts a quite different training paradigm. In our framework, a sequence with length 200 will be fed into the forward function 199 times. Each time the input includes the target item and corresponding history sequence. This is easier to understand and flexible to design more complex models (similar implementations can be found in RecBole). However, the sequence will only be encoded once in the original code of SASRec. It will generate 200 logits corresponding to each position and use 199 of them to calculate the loss. This is far more efficient but requires the model to be able to output all the logits simultaneously. The difference in training paradigm might also lead to inconsistent performance.


Fix Roccat Kone Pure Driver

Closes #999.

@stephanlachnit did this get tested after all?

The driver? No, it was never tested from anyone except the person who contributed it, but he stopped responding at some point. We merged it anyway (better a maybe buggy driver than no driver at all was the idea back then).
This commit? A test compile, not more (no hardware), but since the driver is clearly broken anyway I figured it doesn't make a difference.

Next time wait for confirmation. It's best to introduce one commit that fixes the problem than to introduce two partial ones, or possible tree (if the first one was bad, you revert it and fix it properly).


Extracting fails for password protected 7z archives that have encrypted file names

What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
kitty 0.35.2
yazi --debug output
Yazi
    Version: 0.3.0 (3bb867c 2024-08-09)
    Debug  : false
    OS     : linux-x86_64 (unix)

Ya
    Version: 0.3.0

Emulator
    Emulator.via_env: ("xterm-kitty", "")
    Emulator.via_csi: Ok(Kitty)
    Emulator.detect : Kitty

Adapter
    Adapter.matches: Kitty

Desktop
    XDG_SESSION_TYPE: Some("tty")
    WAYLAND_DISPLAY : None
    DISPLAY         : Some(":0")

SSH
    shared.in_ssh_connection: false

WSL
    /proc/sys/fs/binfmt_misc/WSLInterop: false

Variables
    SHELL              : Some("/bin/zsh")
    EDITOR             : Some("nvim")
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None
    ZELLIJ_SESSION_NAME: None

Text Opener
    default: Some(Opener { run: "${EDITOR} \"$@\"", block: true, orphan: false, desc: "Neovim", for_: None, spread: true })
    block  : Some(Opener { run: "${EDITOR} \"$@\"", block: true, orphan: false, desc: "Neovim", for_: None, spread: true })

tmux
    TMUX   : false
    Version: No such file or directory (os error 2)

Dependencies
    file             : 5.45
    ueberzugpp       : No such file or directory (os error 2)
    ffmpegthumbnailer: 2.2.2
    magick           : 7.1.1-25
    fzf              : 0.53.0
    fd               : 10.1.0
    rg               : 14.1.0
    chafa            : No such file or directory (os error 2)
    zoxide           : 0.9.4
    7z               : 16.02
    7zz              : No such file or directory (os error 2)
    jq               : 1.7.1

--------------------------------------------------
When reporting a bug, please also upload the `yazi.log` log file - only upload the most recent content by time.
You can find it in the "/home/xfzv/.local/state/yazi" directory.

Did you try the latest nightly build to see if the problem got fixed?
Yes, and I updated the debug information above (yazi --debug) to the nightly that I tried
Describe the bug
When trying to extract a 7z password protected archive with encrypted file names, yazi is stuck at 99% and the task manager shows the two following errors:

Run "ya pub extract --list \"@$\"" with /tmp/test.7z /tmp/test.7z`

Cannot send message: Incompatible version (Ya 0.3.0 3bb867c, Yazi 0.3.0 407ad26)
Exited with status code: 1
Process failed

Note: yazi -V and ya -v report the same version in the terminal:
% yazi -V
Yazi 0.3.0 (3bb867c 2024-08-09)

% ya -V
Ya 0.3.0 (3bb867c 2024-08-09)

Both were compiled with:
CARGO_INSTALL_OPTS="--locked" cargo install-update -ag

Run micro plugin extract

Micro plugin failed:
runtime error: [string "extract"]:1: Failed to read the temporary directory '/tmp/.tmp_5127d2c0276bf3f365a6cf2a1b0394fe' when extracting '/tmp/test.7z'
stack traceback:
	[C]: in function 'error'
	[string "extract"]:1: in upvalue 'fail'
	[string "extract"]:73: in method 'tidy'
	[string "extract"]:62: in method 'try_with'
	[string "extract"]:21: in function <[string "extract"]:14>

Minimal reproducer

Create a 7z password protected archive with encrypted file names:

% cd /tmp
% echo "test" > test.txt
% 7z a -mhe=on -p'password' test.7z test.txt

From man 7z:
-mhe=on|off
    7z format only : enables or disables archive header encryption (Default : off)

Open yazi
Hover test.7z and press Enter
Two tasks are stuck at 99% in the status bar
Open task manager and press Enter on each of the two tasks
The errors mentioned above are displayed

Anything else?
No response

You need to restart all Yazi instances after an upgrade, i.e. pkill yazi

I made a PR for the second problem, please give it a try, https://github.com/sxyazi/yazi/pull/1451

Nice, let me merge now!


VisualQnA

We currently have local code enabling LLaVA-1.5. TGI Gaudi will support LLaVA-1.6 in 1.17 milestone. We will refactor VisualQnA once LLaVA-1.6 is enabled in TGI Gaudi.


White space parallax

This issue still persists.

The more you scroll, the more white space appears from the top.
Example markup:
<div className={styles.wrapper}>
    <Parallax
        bgImage={Hero}
        strength={800}
        className={styles.parallaxBg}
        bgHeight{"100%"}
        bgWidth={"100%"}
    />
</div>

CSS
.wrapper {
    width: 100%;
    height: 100vh;
    min-height: 780px;
}

Thanks for the report.
I will try to reproduce your issue. But the first guess is that you should not set bgHeight and bgWidth explicitly as it overrides the calculated values inside of the Parallax. The Parallax component calculates a height depending on screen ratio and strength prop so it has enough space to move around without white space.
Can you verify that the issue is still there after removing those two props?

@RRutsche Tried removing both props - issue still persists.

@raunofreiberg I just had a look. Your use case is that you don't have anything inside the parallax but only set the style of the wrapping container to a specific height, right? I'm asking because the logic inside calculates position and dimensions depending on its content height. You could just put a container inside the parallax component that has a specific height.
But to be clear about my assumptions - can you just create a quick demo on https://codesandbox.io/s/r0yEkozrw? Just fork this project. This would help a lot.

I think the solution involves the definition of speed and the known size of your image. If your image is 800px and you want a parallax in a 600px container, your max speed should be 10 or -10 (I could be wrong, it may be 20 or -20) -- you can test this with the positive value and see if topmost scroll and bottommost scroll line up with the underlying image

Note that speed is only an abstraction for setting translateY or translateX based on the scroll axis. Each increment of speed by one will increase the translate effect by 10px.
Example: With a vertical scroll axis, speed: 10 is equivalent to translateY: ['100px', '-100px'] and speed: -10 is equivalent to translateY: ['-100px', '100px'].


Why is the video output a combination of multiple images?

Hi, thank you for your work.
When running “txt2vid”, the video output is an incoherent combination of multiple images, which is very different from the continuity of the video.
Output Result:

Repo result:

Make sure your AnimateDiff-Evolved is updated. There was a ComfyUI update a couple weeks ago that required a code change to ensure AnimateDiff is applied.

After updating AnimateDiff-Evolved, the problem persists.


Pomodoro Clock

Description 📜
A web app based pomodoro clock.
Fixes #<issue_number_here>

Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸
https://user-images.githubusercontent.com/82095877/166001735-a0968279-ade8-46db-a955-7697a1915662.mp4

@gurjeetsinghvirdee please review this PR too.


fix: installer for replacing libav with ffmepg

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[ ] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
fix installer for #4115
Missing changes in Installer/data/server/learningedge-config/optional-config.properties

hmmm, is this all the changes also from #4115 rather than just the fixes you needed?? Having a strong sense of deja vu here. :thinking:


Make the SM2 group be the default group for SM2 algorithm

Fixes #14481
Checklist

[x] tests are added or updated

My approval is subject to the CI succeeding, of course.  But, I like what I see :-)

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged to master. Thank you for the reviews.


Submission for week 2

Hi Experts!!
Something strange happens with docker and wsl2 when it tries to install the npm dependencies (that's why I install the node_modules before creating the image hehe).

url go --> https://hello-go.e51816a.kyma.ondemand.com/hello/r00k13d3v
url js --> https://rick-and-morty.e51816a.kyma.ondemand.com/character/1

Thanks for the challenge 🎉

Hi there @r00k13d3v - if you're just submitting your challenge entry, you don't need to send a PR to this repo. Just check the instructions in the Challenges file. Thanks! 👍

@qmacro but you do have this PR statement there. Confused.

Whoops, my mistake, re-opening. Apologies!

No problem! Thanks to both of you and have a nice weekend! 😉


Add NoMAD Login UserInputUI Payload Keys

the upcoming 1.3 release of NoMAD Login adds UserInputUI payload keys, see https://gitlab.com/orchardandgrove-oss/NoMADLogin-AD/blob/develop/ConfigSamples/NoLoUserInput Sample.mobileconfig for a sample from the devs. Trying to import this sample into ProfileCreator results in warning that UserInputUI key will not be exported and to open an issue here. Thanks

I have added the new settings mentioned in the readme, but I have not pushed them yet as the app is not released in 1.3 from what I can tell, I need to think about adding the version selection to profile creator so one can select the version their targeting so they get the correct settings.

Thank you @erikberglund for adding these. I replaced my "handcrafted" Profile with a ProfileCreator-generated one, but found that the Pop-Ups stay white and can not be selected. Has anybody seen the same?

@fridomac Did that work in your handcrafted version but not in the one exported from ProfileCreator? If that is the case, could you post both the handcrafted mobileconfig and the profile creator mobileconfig here, and I can see if there are any differences that is an error in ProfileCreator.

@fridomac Ah, I see what the error is now. I based the config on the example file in the NoMAD Login repo. And there is a typo in that example file where the items is spelled with capital I. And by looking in the code, I can see that it's looking for lowercase i. I will make an update to the manifest so you can check for manifest updates within 5 minutes. Ill post here when it's changed.

Now it's done. Go to Preferences -> Payloads and click "Check Now" and then "Download" to get the updated manifest. Then you can export the profile again and it should recognise the items.
I should add a fix to the nomad repo too as their example is incorrect.

Thank you for catching that so fast Erik, tried it, imported into Jamf, deployed a machine, now works the same as the handcrafted one.
Greetings from sunny Nuremberg,
Frido.

Ok, I have to reopen this: Even if the "items" is in lowercase, I still get the empty Pop-ups (sorry, had the wrong profile in Jamf for the last test). Will investigate further and report back here...
Bye, Frido.

@fridomac Ok. If you want you can post the profiles here, just drag them in the comment window and I can look at it too.

Ok, I nailed it down to some umlauts in the items Fields, started working as soon as I changed them. Why they worked in the handmade profile escapes me, though. But I think you can close the issue for now.
Thanks again for the support!


Feature/ng update 17

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: CONTRIBUTING.md#commit
~~ [ ] Tests for the changes have been added (for bug fixes / features) ~~
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[x] Other... Please describe:

What is the current behavior?
As of now, library does not support Angular v17 properly.
What is the new behavior?
Supports Angular v17
Does this PR introduce a breaking change?
[x] Yes
[ ] No

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


create CI support elements for testing and builds

add new automated CI and build process for the repo

master branch requires pull requests
require tests, approval, and code review on pull requests
stable
unstable / pre-release

Branch restrictions for master are now in place to require pull requests and at least one review from the code owners group.

We should also move the builds to GitHub Actions so we're not relying on AppVeyor or Travis. This is a big enough lift, that I'm going to create a new issue for it.


Can't compile current version of the book

I can't compile current version of book.
When compiling locally, I got errors that I could not solve. So I decide to compile using Overleaf, and it is failed to compile too.
Can anyone compile current version of the book, or is it just me having this problem?

@mximp please help

@c71n93 what are the errors in overleaf?
Also I believe we have automatic compilation set up (see corresponding action) which publishes pdf.

@mximp I actually can't figure out what this error means:
<*> book.tex

*** (job aborted, no legal \end found)

Here is how much of TeX's memory you used:
 24449 strings out of 477678
 508220 string characters out of 5829488
 767258 words of memory out of 5000000
 42157 multiletter control sequences out of 15000+600000
 496432 words of font info for 71 fonts, out of 8000000 for 9000
 1141 hyphenation exceptions out of 8191
 114i,10n,118p,1018b,883s stack positions out of 10000i,1000n,20000p,200000b,200000s
!  ==> Fatal error occurred, no output PDF file produced!

@mximp I figured out what was the problem. There is no \end{document} in book.tex


Installation Issues

I ran ./setup.sh and I put in all of the correct information, but it is stuck and says:
[15/Apr/2016:10:49:20] ENGINE Started monitor thread 'Autoreloader'.
[15/Apr/2016:10:49:20] ENGINE Started monitor thread '_TimeoutMonitor'.
[15/Apr/2016:10:49:21] ENGINE Serving on http://<IP_ADDRESS>:5000
[15/Apr/2016:10:49:21] ENGINE Bus STARTED
Once it gets to this point, it just stays here. Is there something else I need to do?

Now I have a new issue. It told me to reboot after it finally finished. I rebooted, so now what so I do?

How did you resolve this?

I'm not really sure honestly. What I did was use Ctrl+C to stop the installation, reboot, and ran the command again and it took a few minutes but then it finally finished and then I rebooted again. Hope it works for you too.

The setup script isn't the best at the moment, I'm going to re-visit that for the next version. At that point you've got the webserver running to do the oAuth dance with amazon and get link your AlexaPi to your alexa account, you need to goto either http://localhost:5000 on the Pi's browser or if you don't have a desktop attached to the Pi then goto http://[IP ADDRESS OF PI]:5000 on another machine and sign in to your amazon account


Implement new endpoint for bulk application deployment

New dedicated controller should be added to expose a set of endpoints for application bulk lifecycle management.
Class should be added in the /api/market package.
Suggested class name is AppBulkController.
Root path: /api/apps/bulks/.
Following endpoints should be exposed (initially available only for System administrator users only):

validating the bulk deployment request (provided application name and content of CSV file)
triggering actual bulk deployment
retrieving bulk deployment status (status of all application instances requested in bulk)
undeploying bulk

@kbeyro I suppose we can close this issue, right? The related implementation continues in under a different issue.

@llopat yes, we can close this one

The basic functionalities in scope of this issue were implemented hence closing this .


Add Express to example

This augments the current example/ package to use Connect-Node and Express as the server rather than the Go demo at connect.build.

@smaye81 and I discussed merge order: We decided to wait a couple of days, so that we merge it shortly before the first public beta of @bufbuild/connect-node.

@smaye81, pushed up https://github.com/bufbuild/connect-web/pull/418/commits/67ccd8bb0d583bb2f52aff2232d6956bf9817c41.

fixes a lint issue (our config needs all sources in a src directory...)
serves the web client and the API from the same server, so you don't need two terminal windows
adds a terminal client (so you do need a second terminal window after all 😆)

It's a bit unfortunate that we have to use H1 for Express here, and use the gRPC protocol over H1, which isn't widely supported. But IMO we should merge this, and revisit once we have a better idea.


Debugger doesn't support debugging x86 processes on x64 Windows

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.4)
Product Information:
Version:            1.0.4
Commit SHA-1 hash:  af1e6684fd
Runtime Environment:
OS Name:     Windows
OS Version:  6.1.7601
OS Platform: Windows
RID:         win7-x64
Base Path:   C:\Program Files\dotnet\sdk\1.0.4
VS Code version:
1.15.0
C# Extension version:
1.12.1
Steps to reproduce

dotnet new mvc -o projname
cd projname
code . (start vscode)
change netcoreapp1.1 to net452 in projname.csproj
run: dotnet restore
ctrl+shft+d (opens debug)
Hit F5 (start debug) -> Choose .Net Core to create a launch.json
In launch.json change  to net452
and .dll to projname.exe
Hit F5 again -> Click open Configure Task Runner -> Choose .Net Core
In tasks.json Change "command": "dotnet build", -> "command": ""dotnet build '${workspaceRoot}/projname.csproj'"",
Set a Breakpoint and Hit F5 again
Popup showing "Only 64-bit processes can be debugged."

Expected  behavior
Should start debugging and hit breakpoints
Actual behavior
Only shows the error message and stops
If i change the  to netcoreapp1.1 in projname.csproj
and in launch.json change  to netcoreapp1.1
and .dll to projname.dll the debbuging works and the breakpoints are hit.
I checked the projname.dll that netcoreapp1.1 produced and  the projname.exe that the net452 produced. And they are both in x86.
Am i doing something wrong, have something installed incorrectly or is this the expected behaviour?

You aren't doing anything wrong. x86 debugging is not supported by the C# extension. You will need full Visual Studio for that.

It doesn't look like we currently have an issue tracking the feature of debugging x86 process on x64 Windows. So I will leave this open to track that feature request.
This isn't something we are likely to get to anytime too soon. So I would suggest either compiling code so that it will run in an x64 process, or using full Visual Studio.

Ok then i know the reason. Thanks!  I just thought It was strange because when i changed to netcoreapp1.1 it could debug in x86.

One minor note: We actually don't support debugging .NET Core 32-bit processes either. Its just that .NET Core will nearly always use a 64-bit process, where as, in the Desktop framework, 32-bit is very common. If you have an 'AnyCPU' desktop binary, you can run in a 64-bit process by setting the Prefer32Bit property to false.

@cwistedt Completely unrelated, but I wanted to do this. I have some X64 assembly code that I want to debug, I tried hard but could not do it as I am just in 10th grade of high school.
Can you help me out finding the errors in the code. It is not long, just 70 lines.

@gregg-miskelly VS Code is a leading ide, supporting x86 will top it all and make it more independent ide.
It's a mess to go just for debugging to Visual Studio and do the rest in VS Code

So, any idea when we can expect this? I have a Clarion app (which currently only can be 32-bit) calling my external library - would love if I could debug this through VS Code


Segmentation Faults 2017-05-12

Hello,
I was using American Fuzzy Lop (afl-fuzz) to fuzz input the mujs program on Linux. Is fixing the crashes from these input files something you're interested in? The input files can be found here: https://github.com/rwhitworth/mujs-fuzz/tree/master/2017-05-12.
The files can be executed as ./mujs id_filename to cause seg faults.
Let me know if I can provide any more information to help narrow down this issue.  I tried to use valgrind to narrow the problems down, but without any luck.

Thanks!
A fix for this is committed.


Color Picker Doesn't Open Until PowerToys Restart

ℹ Computer information

PowerToys version: v0.33.1
PowerToy Utility: Color Picker
Running PowerToys as Admin: Yes
Windows build number: 20H2 (19042.867)

📝 Provide detailed reproduction steps (if any)

Start Computer (PowerToys starts automatically)
Try to use keyboard shortcut to start (Win+Z) for me

✔ Expected result
The Color Picker opens.
❌ Actual result
Nothing happens. If PowerToys is manually quit and relaunched, the ColorPicker works normally. Additionally, at startup, two errors are created in the Windows Reliability Log (Pictured Below). This occurs every startup. This issue is related to both #8944 and #8831.
📷 Screenshots

I also get an error on startup - ColorPickerUI has stopped working

@enricogior / @mykhailopylyp this feels like a dup but can't seem to find the matching.
If not, this should be looked into .39

@AlpacaFur
Can you update to the latest version(0.35.0) and verify if the issue still reproduces? It looks similar to https://github.com/microsoft/PowerToys/issues/9573.

Doesn't happen now, but I did a lot of things like reinstalling WIndows, reinstalling PowerToys (ofc) since I last commented. I have the latest version i.e v0.35.0 right now

I can no longer reproduce this issue, so thanks!


Backward LSTM results mismatch between TF and ONNXRuntime

Backward LSTM results mismatch between TF and ONNXRuntime.
in TF runtime (tf.keras), say 1,2,3 are time frames.. output of reverse LSTM will be op3 op2 op1. where as in ONNXRuntime it will be op1 op2 op3.
I think keras-onnx need to add a reverseV2 operator after backward LSTM in order to get matched results.
i.e. at
https://github.com/onnx/keras-onnx/blob/master/keras2onnx/ke2onnx/lstm.py#L213
After transpose we need to use reverseV2 or reverse sequence to match the order.
To reproduce:
simple_lstm.txt
-rename the above file to .h5
-run with some random input on tf.keras backend and on onnxruntime (after conversion) and compare results.
-outputs are just reverse to each other.
Alternatively, you can try this:
code for reverse LSTM:
max_features = 10
maxlen = 10
model = Sequential()
model.add(Embedding(max_features, 128, input_length=maxlen))

model.add(LSTM(64, go_backwards=True, return_sequences = True))
model.add(Dense(1, activation='sigmoid'))
model.compile('adam', 'binary_crossentropy', metrics=['accuracy'])

from keras.models import load_model
model.save('simple_rev_lstm.h5')

To compare results with other inference engines and ONNXRuntime
# pip install onnxruntime
#env TF_KERAS=1
import numpy as np
import onnxruntime
from tensorflow.keras.models import load_model as load_model_tf_keras
np.random.seed(0)
input_data = np.random.randint(10, size=(2, 10))
# with CustomObjectScope({'GlorotUniform': glorot_uniform()}):
sess = onnxruntime.InferenceSession("simple_rev_lstm.onnx")
result = sess.run(["dense_1"], {'embedding_1_input': input_data.astype(np.float32)})
print("ONNX Runtime")
print(np.asarray(result[0]))

model = load_model_tf_keras('simple_rev_lstm.h5')
result = model.predict(input_data)
print("TF Runtime")
print(result)

OUTPUT:
ONNX Runtime
[[[0.5028585 ]
  [0.51010513]
  [0.5096171 ]
  [0.50567615]
  [0.50046337]
  [0.50202006]
  [0.5010086 ]
  [0.49436894]
  [0.4989641 ]
  [0.50032514]]

 [[0.50235206]
  [0.5045772 ]
  [0.504677  ]
  [0.5032916 ]
  [0.5016299 ]
  [0.50043035]
  [0.4991624 ]
  [0.50064933]
  [0.5028503 ]
  [0.5012636 ]]]

TF Runtime
[[[0.50032514]
  [0.4989641 ]
  [0.49436894]
  [0.5010086 ]
  [0.50202006]
  [0.50046337]
  [0.50567615]
  [0.5096171 ]
  [0.51010513]
  [0.5028585 ]]

 [[0.5012636 ]
  [0.5028503 ]
  [0.50064933]
  [0.4991624 ]
  [0.50043035]
  [0.5016299 ]
  [0.5032916 ]
  [0.504677  ]
  [0.5045773 ]
  [0.50235206]]]

Observation:
The values are in reverse to each other on axis 1.
Not sure which is correct behavior.

I read through LSTM spec: https://github.com/onnx/onnx/blob/master/docs/Operators.md#lstm and really didn't get any clue from the spec whether backward output should be reversed, so I don't know whether ORT result is correct or not.
Can you post an issue in ONNX issue list to get a clarification whether backward output should be reversed? Then we can decide how to follow up on this question.

@wenbingl yes I already posted this question in ONNX https://github.com/microsoft/onnxruntime/issues/4187, waiting for the response.

In the onnxruntime post, you mentioned that you hack keras2onnx converter, what is the hack? If we want to support backward in converter side, seems that we need add onnx ReverseSequence op after lstm, and it looks a nontrivial change.

@jiafatom what you mentioned is correct. I added ReverseSequence operator after LSTM conversion in keras2onnx if direction is 'reverse'. As you said, it is a nontrivial change. So looking for some confirmation from your side or ONNXRuntime side. If you agree with me, I can publish a PR of the change.

@buddhapuneeth in previous posts, we recommend you to post the issue in onnx repo, not onnxruntime repo. In onnx spec, there is no mention the output should go forward or backward. So we want them to give a clarification. Thanks.

@buddhapuneeth , if this issue blocks you and we can't get onnx response quickly.
I can accept the idea that go_backward by default is False and it's the default behavior of ONNX (Suppose ONNX should adopt this idea as well). And the go_backward == True needs a reverse op. Do you have a PR for that?

@jiafatom sure I will raise in ONNX repo as well.
@wenbingl I have code ready for this change. I can publish PR in a day or two.


Update icon for field artillery single/multiple rocket self-propelled

Accoding to MIL-STD-2525C 2008, the icon for "WARFIGHTING SYMBOLS/GROUND TRACK/UNIT/COMBAT/FIELD ARTILLERY/ROCKET/SINGLE ROCKET LAUNCHER/SINGLE ROCKET SELF-PROPELLED" should have the ^'s over the dot inside the rounded rectangle.
From http://www.spatialillusions.com/milsymbol/docs/milsymbol-2525c-svg.html#TABLEV

Icon on page 137 in the MIL-STD-2525C:

This applies to both the single and the multiple rocket version, when they are self-propelled:
WAR.GRDTRK.UNT.CBT.FLDART.ROC.SRL.SRSP Hierarchy: 1.X.<IP_ADDRESS>.2.1.1 SFGPUCFRSS*****
WAR.GRDTRK.UNT.CBT.FLDART.ROC.MRL.MRSPD Hierarchy: 1.X.<IP_ADDRESS>.2.2.1 SFGPUCFRMS*****

In this case the MIL-STD-2525D symbology for the same symbol is used, in my opinion this is a clearer representation of this symbol and follows a more logical building pattern. Since the icon definitions in milsymbol are shared between standards to reduce size of the library symbol definitions has been reused in all cases where there isn't major differences between the standards.
This also follows how the symbols are drawn in ADRP 1-02.
Because of this, I won't update this symbol at the moment. However, if this is very importent for you or your customer, there is ways to modify specific symbols in milsymbol and I could provide you with instructions for how to modify the symbols using a small override that you can include in your milsymbol build.

Thx for the quick answer.
Our customers have not yet noted the difference. If they do and wants to have it changed, I'll get back to you about how to modify it locally.


More details in the Breaking Changes

Enhancement proposal
Give more details in the Breaking Changes of the 0.2.0 version of Community Manim.
For instance, with this version, this animation provided by Elteoremadebeethoven doesn't compile any more. I guess this is due to the removal of the "old syntax for animating mobject methods by passing the methods and arguments to self.play" but I have absolutely no idea on how to adapt to the new syntax e.g. these lines.

but I have absolutely no idea on how to adapt to the new syntax e.g. these lines.

Not at all. As described in our changelog, only calls like self.play(my_mobject.method, method_arg) do not work any longer and have to be written using the new .animate syntax. In the code you posted, there is just one such play call, namely
https://github.com/Elteoremadebeethoven/MyAnimations/blob/f4504958c87a8b28fc0dadbb8c3eedf6e753dbf8/logo_scene/2d_graph_scene.py#L169
should become
            input_tracker_p2.animate.set_value(input_tracker_p1.get_value()),

All other play calls look fine to me.
If you have an explicit suggestion how the description in the breaking changes section can be improved, I'm happy to discuss it -- but from your current proposal it is not clear to me what exactly you would like to have improved.

but I have absolutely no idea on how to adapt to the new syntax e.g. these lines.

Not at all. As described in our changelog, only calls like self.play(my_mobject.method, method_arg) do not work any longer and have to be written using the new .animate syntax. In the code you posted, there is just one such play call, namely
https://github.com/Elteoremadebeethoven/MyAnimations/blob/f4504958c87a8b28fc0dadbb8c3eedf6e753dbf8/logo_scene/2d_graph_scene.py#L169
should become
            input_tracker_p2.animate.set_value(input_tracker_p1.get_value()),

All other play calls look fine to me.
If you have an explicit suggestion how the description in the breaking changes section can be improved, I'm happy to discuss it -- but from your current proposal it is not clear to me what exactly you would like to have improved.

should become
            input_tracker_p2.animate.set_value(input_tracker_p1.get_value()),

Unfortunately, it still returns an error:
manim 2d_graph_scene.py Thumbnail
[01/09/21 16:23:02] ERROR                                                                                \module_ops.py\:65
                                There are no scenes inside that module

If you have an explicit suggestion how the description in the breaking changes section can be improved, I'm happy to discuss it -- but from your current proposal it is not clear to me what exactly you would like to have improved.

To be honest, I haven't any suggestion because I was (I am) a bit lost:  I still have absolutely no idea on how to adapt to the new syntax in the general cases: in the current one, I had the impression all the self.play had to be changed (not "[a]ll other play calls look fine to me." :smile:) and, in the one line 168, I wouldn't have guessed the line 169 was the one to adapt.

should become
            input_tracker_p2.animate.set_value(input_tracker_p1.get_value()),

Unfortunately, it still returns an error:
manim 2d_graph_scene.py Thumbnail
[01/09/21 16:23:02] ERROR                                                                                \module_ops.py\:65
                                There are no scenes inside that module

If you have an explicit suggestion how the description in the breaking changes section can be improved, I'm happy to discuss it -- but from your current proposal it is not clear to me what exactly you would like to have improved.

To be honest, I haven't any suggestion because I was (I am) a bit lost:  I still have absolutely no idea on how to adapt to the new syntax in the general cases: in the current one, I had the impression all the self.play had to be changed (not "[a]ll other play calls look fine to me." :smile:) and, in the one line 168, I wouldn't have guessed the line 169 was the one to adapt.

Did you change the import line to from manim import * as well? It seems to me that there might be a problem with different Manim versions or so.
The breaking change just concerns calls to play that passed first the method of an mobject, and then the corresponding arguments -- because the logic for handling a call like self.play(ShowCreation(my_circle), my_square.shift, LEFT) was very complicated. Now all arguments in self.play have to be animations (self.play(ShowCreation(my_circle), my_square.animate.shift(LEFT)) which makes the underlying logic a lot easier, and the interface cleaner.

Did you change the import line to from manim import * as well? It seems to me that there might be a problem with different Manim versions or so.
The breaking change just concerns calls to play that passed first the method of an mobject, and then the corresponding arguments -- because the logic for handling a call like self.play(ShowCreation(my_circle), my_square.shift, LEFT) was very complicated. Now all arguments in self.play have to be animations (self.play(ShowCreation(my_circle), my_square.animate.shift(LEFT)) which makes the underlying logic a lot easier, and the interface cleaner.

Did you change the import line to from manim import * as well?

Sorry, I don't see what you're talking about. At the beginning of the 2d_graph_scene.py, I see:
from manimlib.imports import *

but I guess that's not what you mean.

It seems to me that there might be a problem with different Manim versions or so.

Highly possible, and I don't know how to clean up my computer :confused:

The breaking change just concerns calls to play that passed first the method of an mobject,

I guess what I'm missing is what "method of an mobject" does mean. If you have some pointers, they would be very welcome.

and then the corresponding arguments -- because the logic for handling a call like self.play(ShowCreation(my_circle), my_square.shift, LEFT) was very complicated. Now all arguments in self.play have to be animations (self.play(ShowCreation(my_circle), my_square.animate.shift(LEFT)) which makes the underlying logic a lot easier, and the interface cleaner.

If you say so :grin:

Did you change the import line to from manim import * as well?

Sorry, I don't see what you're talking about. At the beginning of the 2d_graph_scene.py, I see:
from manimlib.imports import *

but I guess that's not what you mean.

It seems to me that there might be a problem with different Manim versions or so.

Highly possible, and I don't know how to clean up my computer :confused:

The breaking change just concerns calls to play that passed first the method of an mobject,

I guess what I'm missing is what "method of an mobject" does mean. If you have some pointers, they would be very welcome.

and then the corresponding arguments -- because the logic for handling a call like self.play(ShowCreation(my_circle), my_square.shift, LEFT) was very complicated. Now all arguments in self.play have to be animations (self.play(ShowCreation(my_circle), my_square.animate.shift(LEFT)) which makes the underlying logic a lot easier, and the interface cleaner.

If you say so :grin:

Did you change the import line to from manim import * as well?

Sorry, I don't see what you're talking about. At the beginning of the 2d_graph_scene.py, I see:
from manimlib.imports import *

but I guess that's not what you mean.

That is what I mean: if you want to run this code with the community version of Manim, you will have to change this line to from manim import *.

It seems to me that there might be a problem with different Manim versions or so.

Highly possible, and I don't know how to clean up my computer 😕

You could visit our Discord and post in one of the manim-help channels -- it is a bit easier to figure out what is wrong there.

The breaking change just concerns calls to play that passed first the method of an mobject,

I guess what I'm missing is what "method of an mobject" does mean. If you have some pointers, they would be very welcome.

Methods are special functions that are, in some sense, attached to instances of classes. In the example above, my_square is an instance of the Mobject class, and my_square.shift is one of the objects methods -- which you can run in order to shift the object in the scene.
I don't know what your background in programming is, but it might be a good idea to revisit object-oriented programming in Python, then the terminology should be a bit clearer. :-)

Did you change the import line to from manim import * as well?

Sorry, I don't see what you're talking about. At the beginning of the 2d_graph_scene.py, I see:
from manimlib.imports import *

but I guess that's not what you mean.

That is what I mean: if you want to run this code with the community version of Manim, you will have to change this line to from manim import *.

It seems to me that there might be a problem with different Manim versions or so.

Highly possible, and I don't know how to clean up my computer 😕

You could visit our Discord and post in one of the manim-help channels -- it is a bit easier to figure out what is wrong there.

The breaking change just concerns calls to play that passed first the method of an mobject,

I guess what I'm missing is what "method of an mobject" does mean. If you have some pointers, they would be very welcome.

Methods are special functions that are, in some sense, attached to instances of classes. In the example above, my_square is an instance of the Mobject class, and my_square.shift is one of the objects methods -- which you can run in order to shift the object in the scene.
I don't know what your background in programming is, but it might be a good idea to revisit object-oriented programming in Python, then the terminology should be a bit clearer. :-)

That is what I mean: if you want to run this code with the community version of Manim, you will have to change this line to from manim import *.

Ah, OK. It does compile now and the animations are created, despite an error and some warnings (see below). The error is also related to the Breaking Changes:

ERROR    CONFIG has been removed from ManimCommunity. Please use keyword arguments instead.

And, indeed, the file contains:
class Thumbnail(GraphScene):
    CONFIG = {
        "y_max": 8,
        "y_axis_height": 5,
    }

but I must admit the hint in the Changelog:

Remove all CONFIG dictionaries and all calls to digest_config and allow passing options directly to the constructor of the corresponding classes (pull request 783).
Practically, this means that old constructions using CONFIG like:
class SomeMobject(Thing):
  CONFIG = {
       "my_awesome_property": 42
   }

where corresponding objects were then instantiated as my_mobject = SomeMobject() should now be created simply using my_mobject = SomeMobject(my_awesome_property=42).

is not that clear for me: what "my_mobject" for e.g. "y_max": 8` and where should it be used in the rest of the file?
One of the warning is:

WARNING  Option -l is deprecated please use the --quality/-q flag.

So I guess the command line in the "Your first Scene" section of the Manim Community Overview should be changed, but I'm not sure where I should report this.

It seems to me that there might be a problem with different Manim versions or so.

Highly possible, and I don't know how to clean up my computer confused

You could visit our Discord

Sigh... not a big fan of Discord (privacy issues, etc.)

and post in one of the manim-help channels -- it is a bit easier to figure out what is wrong there.

Ah?! Why?

The breaking change just concerns calls to play that passed first the method of an mobject,

I guess what I'm missing is what "method of an mobject" does mean. If you have some pointers, they would be very welcome.

Methods are special functions that are, in some sense, attached to instances of classes. In the example above, my_square is an instance of the Mobject class, and my_square.shift is one of the objects methods -- which you can run in order to shift the object in the scene.
I don't know what your background in programming is,

In LaTeX, quite reasonable :smile:. In Python, I'm a hobbyist.

but it might be a good idea to revisit object-oriented programming in Python, then the terminology should be a bit clearer. :-)

OK, thanks!

That is what I mean: if you want to run this code with the community version of Manim, you will have to change this line to from manim import *.

Ah, OK. It does compile now and the animations are created, despite an error and some warnings (see below). The error is also related to the Breaking Changes:

ERROR    CONFIG has been removed from ManimCommunity. Please use keyword arguments instead.

And, indeed, the file contains:
class Thumbnail(GraphScene):
    CONFIG = {
        "y_max": 8,
        "y_axis_height": 5,
    }

but I must admit the hint in the Changelog:

Remove all CONFIG dictionaries and all calls to digest_config and allow passing options directly to the constructor of the corresponding classes (pull request 783).
Practically, this means that old constructions using CONFIG like:
class SomeMobject(Thing):
  CONFIG = {
       "my_awesome_property": 42
   }

where corresponding objects were then instantiated as my_mobject = SomeMobject() should now be created simply using my_mobject = SomeMobject(my_awesome_property=42).

is not that clear for me: what "my_mobject" for e.g. "y_max": 8` and where should it be used in the rest of the file?
One of the warning is:

WARNING  Option -l is deprecated please use the --quality/-q flag.

So I guess the command line in the "Your first Scene" section of the Manim Community Overview should be changed, but I'm not sure where I should report this.

It seems to me that there might be a problem with different Manim versions or so.

Highly possible, and I don't know how to clean up my computer confused

You could visit our Discord

Sigh... not a big fan of Discord (privacy issues, etc.)

and post in one of the manim-help channels -- it is a bit easier to figure out what is wrong there.

Ah?! Why?

The breaking change just concerns calls to play that passed first the method of an mobject,

I guess what I'm missing is what "method of an mobject" does mean. If you have some pointers, they would be very welcome.

Methods are special functions that are, in some sense, attached to instances of classes. In the example above, my_square is an instance of the Mobject class, and my_square.shift is one of the objects methods -- which you can run in order to shift the object in the scene.
I don't know what your background in programming is,

In LaTeX, quite reasonable :smile:. In Python, I'm a hobbyist.

but it might be a good idea to revisit object-oriented programming in Python, then the terminology should be a bit clearer. :-)

OK, thanks!

where corresponding objects were then instantiated as my_mobject = SomeMobject() should now be created simply using my_mobject = SomeMobject(my_awesome_property=42).

is not that clear for me: what "my_mobject" for e.g. "y_max": 8` and where should it be used in the rest of the file?

The interface for passing keyword arguments to the scene itself is, unfortunately, not the cleanest yet. Have a look at how this is done in our example gallery: https://docs.manim.community/en/v0.2.0/examples.html#plotting-with-manim

One of the warning is:

WARNING  Option -l is deprecated please use the --quality/-q flag.

So I guess the command line in the "Your first Scene" section of the Manim Community Overview should be changed, but I'm not sure where I should report this.

This has already been fixed and will be included in the next release: https://docs.manim.community/en/latest/tutorials/quickstart.html

You could visit our Discord

Sigh... not a big fan of Discord (privacy issues, etc.)

Fair, it is of course not required.

and post in one of the manim-help channels -- it is a bit easier to figure out what is wrong there.

Ah?! Why?

There are way fewer people providing support here than on Discord, and especially for operating system depending questions (like how to clean up your installs), I probably can't really help.

where corresponding objects were then instantiated as my_mobject = SomeMobject() should now be created simply using my_mobject = SomeMobject(my_awesome_property=42).

is not that clear for me: what "my_mobject" for e.g. "y_max": 8` and where should it be used in the rest of the file?

The interface for passing keyword arguments to the scene itself is, unfortunately, not the cleanest yet. Have a look at how this is done in our example gallery: https://docs.manim.community/en/v0.2.0/examples.html#plotting-with-manim

One of the warning is:

WARNING  Option -l is deprecated please use the --quality/-q flag.

So I guess the command line in the "Your first Scene" section of the Manim Community Overview should be changed, but I'm not sure where I should report this.

This has already been fixed and will be included in the next release: https://docs.manim.community/en/latest/tutorials/quickstart.html

You could visit our Discord

Sigh... not a big fan of Discord (privacy issues, etc.)

Fair, it is of course not required.

and post in one of the manim-help channels -- it is a bit easier to figure out what is wrong there.

Ah?! Why?

There are way fewer people providing support here than on Discord, and especially for operating system depending questions (like how to clean up your installs), I probably can't really help.

Given that there is no explicit enhancement proposal in this issue, I'll mark it as wontfix and close it.

Given that there is no explicit enhancement proposal in this issue, I'll mark it as wontfix and close it.

The interface for passing keyword arguments to the scene itself is, unfortunately, not the cleanest yet. Have a look at how this is done in our example gallery: https://docs.manim.community/en/v0.2.0/examples.html#plotting-with-manim

OK. In this case, replacing:
    CONFIG = {
        "y_max": 8,
        "y_axis_height": 5,
    }

by:
    def __init__(self, **kwargs):
        GraphScene.__init__(
            self,
            y_max=8,
            y_axis_height=5,
            **kwargs)

did the trick.

This has already been fixed and will be included in the next release: https://docs.manim.community/en/latest/tutorials/quickstart.html

Nice!

There are way fewer people providing support here than on Discord, and especially for operating system dependent questions (like how to clean up your installs), I probably can't really help.

Okay (I'm using Linux).
Thanks!

The interface for passing keyword arguments to the scene itself is, unfortunately, not the cleanest yet. Have a look at how this is done in our example gallery: https://docs.manim.community/en/v0.2.0/examples.html#plotting-with-manim

OK. In this case, replacing:
    CONFIG = {
        "y_max": 8,
        "y_axis_height": 5,
    }

by:
    def __init__(self, **kwargs):
        GraphScene.__init__(
            self,
            y_max=8,
            y_axis_height=5,
            **kwargs)

did the trick.

This has already been fixed and will be included in the next release: https://docs.manim.community/en/latest/tutorials/quickstart.html

Nice!

There are way fewer people providing support here than on Discord, and especially for operating system dependent questions (like how to clean up your installs), I probably can't really help.

Okay (I'm using Linux).
Thanks!


혜택/토스 켜기/Sticky 내 캐릭터

https://github.com/gracefullight/doss/commit/6bc399ae422d5458260e049fd7f0897701dcf738


[Bugfix][Printer] Avoid adding annotation twice for ConstantNode

@icemelon9 @zhiics @jroesch
the printer of constant node prints annotation (and typer) twice. like,
conv2d(%x, %conv.w, meta[relay.Constant][0] /* ty=Tensor[(1), int64] / / ty=Tensor[(1), int64] *
Because for Print(meta=false), constant node does not know how to print itself, and fallback to Print(meta=true), the annotation therefore be added twice in Print().

Thanks @zhiics @junrushao1994 for the suggestion. The annotator does work. However I noticed the printer of constant node prints annotation (and typer) twice. like,
conv2d(%x, %conv.w, meta[relay.Constant][0] /* ty=Tensor[(1), int64] */ /* ty=Tensor[(1), int64] *

Because for Print(meta=false), constant node does not know how to print itself, and fallback to Print(meta=true), the annotation therefore be added twice in Print().
Please advise if the fix makes sense.

@yzhliu yeah, I noticed this before as well. I am okay with the change.

Thanks @yzhliu @junrushao1994


cactus serve fails in py3

Cloned from repo and tried serving site. Seems like its trying to decode unicode since its on python3.
bacon@neptune:~/websites/spearfishing$ cactus serve
Running webserver at http://<IP_ADDRESS>:8000 for /home/bacon/websites/spearfishing/.build
Type control-c to exit
Traceback (most recent call last):
  File "/usr/local/bin/cactus", line 9, in <module>
    load_entry_point('Cactus==3.3.2', 'console_scripts', 'cactus')()
  File "/usr/local/lib/python3.4/dist-packages/cactus/cli.py", line 159, in cli_entrypoint
    main(sys.argv[1:])
  File "/usr/local/lib/python3.4/dist-packages/cactus/cli.py", line 155, in main
    ns.target(**kwargs)
  File "/usr/local/lib/python3.4/dist-packages/cactus/cli.py", line 65, in serve
    site.serve(port=port, browser=browser)
  File "/usr/local/lib/python3.4/dist-packages/cactus/site.py", line 449, in serve
    self.server = WebServer(self.build_path, port=port)
  File "/usr/local/lib/python3.4/dist-packages/cactus/server.py", line 85, in __init__
    self.path = path.decode("utf-8")
AttributeError: 'str' object has no attribute 'decode

Thanks! This is fixed in 3.3.3


Gradle Error: Cannot create variant 'android-lint' after configuration ':flexible-adapter:debugRuntimeElements' has been resolved

Hallo
i have android studio 3.1 and am trying to run the code but im getting this error:
Cannot create variant 'android-lint' after configuration ':flexible-adapter:debugRuntimeElements' has been resolved.
any idea, how to solve it?

This is due to new Gradle plugin when AS gets updated that goes in conflict with javaDoc plugin.
I've just updated the scripts with the new versions.
Let me know if it is fixed.

thank you very much. it work like magic.
i have a question here please.
my app will have a lot of items, say 1200. as an expert, would you say, that recyclerview will manage these items well and it will scroll easyily?
i have already listview and want to replace it with recyclerview.

@MohammadNsr, it depends how much heavy are those elements. But if you already have those number, I expect an increase of the performance because, by default, it should be faster: it recycles and reuses the Views not visible anymore to the user, without recreate all the view objects.
When you update the elements you can do with the DiffUtil or with the internal calculation or with notifyDataSetChanged(). Up to you.
Follow also the #577 discussion.

Thank you. I will try to do the recommendations

Hi @midhunhk, I had the same issue with another library as you have.
I could resolve that with replacing this line:
classpath = files(variant.javaCompile.classpath.files) + files(ext.androidJar)
with:
        doFirst {             classpath = files(variant.javaCompile.classpath.files) + files(ext.androidJar)         },
as @davideas said "This is due to new Gradle plugin when AndroidStudio gets updated that goes in conflict with JavaDoc plugin", If you have Javadoc task you must be able to find the same line

@samiazar how do I find this line:
classpath = files(variant.javaCompile.classpath.files) + files(ext.androidJar)?

@jude07 as I said before, one possible option for this issue depends on Javadoc tasks.
If you have any JavaDoc tasks on your project or maybe on another third-party library, You can find this line in build.gradle of that project.

Thanks so much. It works for me by replacing
doFirst { classpath = files(variant.javaCompile.classpath.files) + files(ext.androidJar) }
to
classpath = files(variant.javaCompile.classpath.files) + files(ext.androidJar)
The error has finally gone. :)


Document "generator" behavior of Memory.blocks()

Hi, as a convert from .NET world (Linq generic extended methods FTW!!) to the Python world, I hate the different behavior of iterators and generators, especially where in Python world the "generator" is usually considered to be runable only once (which is a shitty paradigm but we are in Python universe anyway...).
So, my wish is: please document the behavior of Memory.blocks() -> i.e. that it's runable only once, and if the user wants to keep the data, catching it into list() would be advisable.

Ok, that's the inferred behavior of Python stuff, but I agree that good docs should be more explicit sometimes.

I'm leaving this as not planned because the behavior of generators is very Python specific.


WIP: La/upstream update

Ticket
Link to ticket: No linked ticket Related to MAGIC-2057
What has been done

merged the the upstream Leaflet develop branch with local upstream_update and fixed a typo

How to test

Acceptance criteria
Todo

[ ]
[ ]

Notes

Wrong repo


RuntimeError：expected scalar type Half but found BFloat16

when I run train_openfold.py, I encountered the following error.

Could you send your training command?

@NZ99 could you also send your training command?

Sure, my command is srun python3 /fsx/openbioml/openfold/train_openfold.py /fsx/openbioml/openfold_data/pdb_mmcif/mmcif_files/ /fsx/openbioml/openfold_roda/pdb/ /fsx/openbioml/openfold_data/pdb_mmcif/mmcif_files /fsx/openbioml/openfold_out/ 2021-10-10 --template_release_dates_cache_path /fsx/openbioml/openfold_data/mmcif_cache.json --precision 16 --num_nodes 8 --gpus 8 --replace_sampler_ddp=True --seed 42 --deepspeed_config_path /fsx/openbioml/openfold/deepspeed_config.json --checkpoint_every_epoch --train_chain_data_cache_path /fsx/openbioml/openfold_data/chain_data_cache.json --obsolete_pdbs_file_path /fsx/openbioml/openfold_data/pdb_mmcif/obsolete.dat. Running on a SLURM cluster with 8 nodes each with 8 A100s.

--precision 16 tries to run the model in FP16 mode, which is unsupported. You need to use --precision 32 or --precision bf16. In the latter case, you also need to make sure that bfloat16 is enabled in the DeepSpeed config. I should add a warning for --precision 16.

Thank you! Looks like it's training fine now. I'm not sure how I made this mistake, I was sure I had copied it from the README...
Thank you again Gustaf! :)

(don't look too closely at ecd5a7e...)

Thank you Gustaf！ --precision should be set as bf16 if we use the default deepspeed_config.json. The command raise 'RuntimeError：expected scalar type Half but found BFloat16' is as the same as Readme.md.
By the way, there is missing output_dir input.

Thank you Gustaf！I can run it by setting --precision as bf16. Previously, I use the default deepspeed_config.json, and the training launch command is same as Readme.md, which raise 'RuntimeError：expected scalar type Half but found BFloat16'. By the way, there is missing output_dir input in the readme.md.

Awesome！I find the training sample command has been modified from 16->bf16

Fixed in d96f27b.


ARFF attribute naming specification changed

Hi Renato,
The specification of ARFF has recently changed to allow a wider range of attribute names. More specifically, attributes are now allowed to start with numbers (in fact any character except control characters and '{', '}', ',', or '%': http://weka.wikispaces.com/ARFF+(stable+version)
It would be great if liac-arff could be updated to reflect this. We are using liac-arff for python clients for OpenML.org and some of our datasets (those that have attributes starting with numbers) cannot be parsed by liac-arff because of this reason.
Many thanks!
Sincerely,
Joaquin

Hi Joaquin, thanks for this feedback, at maximum in this weekend (hopefully before that) I update this and review the @mfeurer  pull requests.


Provide a UI for the updater

As far as I can tell, the Keybase app has no way to check for updates in the UI; you have to execute a command from the shell in order to do it. It would be nice if there were a way to trigger an update check from the UI and see the changelog.

Update checks run once an hour automatically.  So we'd rather you didn't worry about running them manually at all.  Is that okay for you, or is there a reason you'd like to do so?

It's nice to be able to get confirmation that an app is up to date, especially when it's something related to security.


Discussion: More immutability in webnative

(Came up in a call with @expede)
Recently a couple of concurrency issues surfaced. They stem from data races, so the root problem in these cases is that some mutable state is modified by multiple entities.
We should think about making more of our data structures immutable.
Concretely, this would mean e.g. making the MMPT class only have immutable members, and e.g. its add() method return a new reference to a new MMPT.
We also have data races - as the concurrency.test.ts sometimes reveals - in the private file system code in (I think) PrivateTree (I did some testing in the matheus23/fix-concurrency).
We should think about also making this data structure immutable.

This is obviously a bigger refactor, so we should plan this a little better. Maybe we do this incrementally?
Also, at some point we have to put a mutable API over the immutable code, as that's more in line of how e.g. an app developer thinks about data storage (duh!).
We think we might want to have a very thin "mutability" layer, think of it like an index into the individual, immutable private file system trees
I'm thinking of also exposing the immutable file system stuff, so it's still composable, because once you create a "mutable" layer on top of an immutable API, you'll never truly get back the immutable API. I don't want to lose the immutable API in case anyone wants to integrate it into an immutable-first codebase.

This is obviously a bigger refactor, so we should plan this a little better

Yeah, this is totally a "measure twice / cut once".
I've been doing some poking around. You're going to laugh when you see the state of the art: "In this paper we use optimistic concurrency techniques adapted from software transactional memory to develop a concurrent tree data structure." Soooo exactly what we were saying on the call 😆 Except that we're implementing something STM-like, so that doesn't really help us too much.

We think we might want to have a very thin "mutability" layer, think of it like an index into the individual, immutable private file system trees

Yeah, exactly. There's a few edge cases, but in theory a light reference index for the latest version feels like the right direction.

Maybe we do this incrementally?

That would be ideal. Let's get this fully specced out, and then see which bit can be done first 👍 Okasaki was surprisingly unhelpful on concurrent inserts, aside from the classic merge operation which doesn't totally work for use because we have namespace contention. I have some papers open; will share any findings!

Working thoughts on approaches:
Switching to a less mutable solution makes keeping track of various parts of the state much more straightforward, and we get to align with the immutability inherent in content addressing.
Write-Ahead Log

Fairly straightforward to implement
Doesn't solve for realtime FS concurrency, does batches
Difficult to guarantee consistency between remote HEAD and local state

Can trade off performance to get consistency

Global Rebuilding

Per Okasaki ~p102, Hood & Melville realtime queues)
Separation of working copy and queryable (finalized) structure

AKA persistent version of the classic clean and dirty states

Slightly cleaner than in the mutable case, because persistence

Leave in a Promise until available in finalized version?

Okasaki warns that these tend to be very difficult to implement correctly

...for the same reasons that the our current implementation is suffering

(i.e. handlig multiple concurrent edits of the same node)

Immutable Data / Mutable Spine

Essentially an STM index pointing at an immutable store
Doubles as a snapshot of the current HEAD

I find the distinction between fully and mostly immutable confusing.
If the surface level API is supposed to look like this:
const permissions = ...
const { fs } = await webnative.initialise({ permissions })
fs.write("private/a.txt", "sth")
fs.write("private/b.txt", "sth")

Then we will always have to have a layer of mutability in there.
The only way we can ever be fully immutable is when we expose an API like this:
const permissions = ...
const { fs } = await webnative.initialise({ permissions })
const fs2 = fs.write("private/a.txt", "sth")
const fs3 = fs2.write("private/b.txt", "sth")

(At least that's how I am thinking about this in my head)
I must be misunderstanding what you refer to when you/Okazaki says "can be implemented fully immutable".
Also, I admit I haven't read the okazaki book. I should really do that :)

Closed by #500
Part of #501


  I separated this into different patches.  The bn_inverse function was tested with 1000 random values, powers of two, small values and their inverses.  The scalar_multiply was only tested with a few specific values like 0, 1 and the tests in tests.c.
It would be good if someone could review the patches. Most importantly the Jacobian functions and the last timing attack safe version of scalar_multiply.
I'm happy to answer questions or supply more comments to this if something is unclear.
Note that although bn_inverse is not constant time, it is used with randomized values and only in the last iteration, when the public key is already computed.

I benchmarked the function scalar_multiply against the previous versions:
Version 0: original (rev e37ba822e627550a453a1678d180f7e056b3d98f)
Version 1: better inverse (rev d4788bddfdf66d18232aa32b904ebb57a9155666)
Version 2: three bits at a time (rev eb6e74f3613b60be86f7ff6dfa82c1ed006ebfaf)
Version 3: more constant time (rev ec057a5102efad6ddea12986de000867fd84dd82)
Version 4: Jacobian variant (rev 1700caf2ad0c6cae388e60e60c9ca0c3daf60227)
All times are obtained by a custom message on the Trezor, calling the
function 100 times and sending a success as reply. I measured the
round trip time. The numbers may be overestimates by a millisecond or
two.   This is impressive. I'll review that soon. Thanks!

Thanks again! Merged into trezor-crypto master. Will do more tests in firmware soon.


Adding environment variable references for more providers

Just filling in the rest of the environment variables - Useful for getting this running in containerised deployments.

Thank you for this pull request but, as mentioned in the docs pull request, the services in this pull request are not supported as part of BookStack and would require extra dependencies. Therefore I will close this pull request.
There services references, apart from stripe, can all alternatively be used via SMTP.


Update pass-server-data example [ci skip]

Summary

Update react, react-dom major version
Add license section to package.json
Use isomorphic-unfetch instead of isomorphic-fetch

Thanks!


Auto-save Python Jupyter notebook and restore from temporary autosave

Sometimes, long-running or badly-written cells cause Visual Studio Code using this extension to freeze. In my case, when this happens, I cannot ask for "stop running the cell", VSC becomes unresponsive and is not even able to save the notebook before closing. In many occasions, when I forgot to save the notebook before running a cell on huge datasets, I have lost all the last edits.
For example, in the last case, VSC went from being unresponsive:

👍
to crashing due to an out-of-memory errror:

(in this case it was not enough to re-open because I was working remotely and VSC was no longer able to connect: I had to quit VSC and re-launch it).
These crashes are usually caused by programming errors, but sometimes they are caused by something else because the code runs fine as a simple Python script. These kind of errors occur more often when working remotely (via ssh), but local runs are affected as well (even if to a lesser degree). In all the cases, this type of errors occur when working with scikit and pandas (but I always use those two libraries).
I think it would be important to add an automatic saving of the current notebook, possibly in a temporary file, before the user executes a cell.

Sorry for never getting back to you on this issue, somehow this slipped through the cracks.
We have made a lot of improvements and fixes in this space and believe this may have been resolved.
Please ensure you update to the latest version of VS code and the extensions.
Closing as I believe it may have been resolved,
If not please ping here and I'll reopen this or feel free to create a new issue.


Tracing: Adopt OpenTelemetry HTTP semconv 1.23.0

Library name
Azure.Core
Please describe the feature.
Update HTTP attributes to comply with HTTP semconv vTBD (likely 1.23.0 will declare them as stable):

Rename attributes according to docs:

http.method -> http.request.method
http.status_code -> http.response.status_code
net.peer.name -> server.address
net.peer.port -> server.port
http.url -> url.full
http.user_agent became opt-in and we don't really need to report it - we have it on logs + lib name and version will appear on activities anyway.

Add new attributes:

error.type - some error-code or a full exception name if exception happens. Also includes status code (as string) for responses we consider to be an error. Maybe we can steal something from .NET - https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Http/src/System/Net/Http/Metrics/MetricsHandler.cs#L157
http.request.resend_count - try count

Set Activity.DisplayName according to span naming conventions

Check if there is anything else in otel semconv that needs attention

Fixed in #39617