TypeLoadException for Windows.Devices.Enumeration.Properties.Keys

System.TypeLoadException
HResult=0x80131522
Message=Unable to find a type named 'Windows.Devices.Enumeration.DevicePropertyStore'
Source=WinRT.Runtime
StackTrace:
at WinRT.TypeNameSupport.FindTypeByNameCore(String runtimeClassName, Type[] genericTypes) in D:\a\1\s\WinRT.Runtime\TypeNameSupport.cs:line 109
>	WinRT.Runtime.dll!WinRT.TypeNameSupport.FindTypeByNameCore(string runtimeClassName, System.Type[] genericTypes) Line 109	C#
 	WinRT.Runtime.dll!WinRT.TypeNameSupport.FindTypeByName(System.ReadOnlySpan<char> runtimeClassName) Line 48	C#
 	WinRT.Runtime.dll!WinRT.ComWrappersSupport.GetRuntimeClassForTypeCreation(WinRT.IInspectable inspectable, System.Type staticallyDeterminedType) Line 334	C#
 	WinRT.Runtime.dll!WinRT.DefaultComWrappers.CreateObject(System.IntPtr externalComObject, System.Runtime.InteropServices.CreateObjectFlags flags) Line 242	C#
 	[Native to Managed Transition]
 	System.Private.CoreLib.dll!00007ffce7ffcd7e()	Unknown
 	[Managed to Native Transition]
 	System.Private.CoreLib.dll!System.Runtime.InteropServices.ComWrappers.TryGetOrCreateObjectForComInstanceInternal(System.Runtime.CompilerServices.ObjectHandleOnStack comWrappersImpl, long wrapperId, System.IntPtr externalComObject, System.Runtime.InteropServices.CreateObjectFlags flags, System.Runtime.CompilerServices.ObjectHandleOnStack wrapper, System.Runtime.CompilerServices.ObjectHandleOnStack retValue)	Unknown
 	System.Private.CoreLib.dll!System.Runtime.InteropServices.ComWrappers.TryGetOrCreateObjectForComInstanceInternal(System.Runtime.InteropServices.ComWrappers impl, System.IntPtr externalComObject, System.Runtime.InteropServices.CreateObjectFlags flags, object wrapperMaybe, out object retValue) Line 312	C#
 	System.Private.CoreLib.dll!System.Runtime.InteropServices.ComWrappers.GetOrCreateObjectForComInstance(System.IntPtr externalComObject, System.Runtime.InteropServices.CreateObjectFlags flags) Line 231	C#
 	WinRT.Runtime.dll!WinRT.ComWrappersSupport.CreateRcwForComObject<System.Collections.Generic.IReadOnlyDictionary<string, object>>(System.IntPtr ptr) Line 66	C#
 	WinRT.Runtime.dll!WinRT.MarshalInspectable<System.Collections.Generic.IReadOnlyDictionary<string, object>>.FromAbi(System.IntPtr ptr) Line 971	C#
 	WinRT.Runtime.dll!WinRT.MarshalInterface<System.Collections.Generic.IReadOnlyDictionary<string, object>>.FromAbi(System.IntPtr ptr) Line 813	C#
 	Microsoft.Windows.SDK.NET.dll!ABI.Windows.Devices.Enumeration.IDeviceInformation.Windows.Devices.Enumeration.IDeviceInformation.Properties.get()	Unknown
 	Microsoft.Windows.SDK.NET.dll!Windows.Devices.Enumeration.DeviceInformation.Properties.get()	Unknown
 	Microsoft.Toolkit.Uwp.Connectivity.dll!Microsoft.Toolkit.Uwp.Connectivity.BluetoothLEHelper.AddDeviceToList(Windows.Devices.Enumeration.DeviceInformation deviceInfo) Line 327	C#

System.InvalidCastException: 'Invalid cast from 'WinRT.IInspectable' to 'ABI.System.Collections.Generic.IEnumerable`1[System.Collections.Generic.KeyValuePair`2[System.String,System.Object]]'.'

@azchohfi I assume the 1st stack was just a first chance exception and the 2nd was the actual failure leading to the crash?  If so, I am going to resolve this as a dupe of #535 which looks the same.

@azchohfi @ manodasanW is this issue solved for you?
I had to set env variable to compile project when referencing CsWinRt package, like this: set CsWinRTWindowsMetadata=10.0.17134.0
After doing so this still crashes for me:
Unable to find a type named 'Windows.Devices.Enumeration.DevicePropertyStore'
   at WinRT.TypeNameSupport.FindTypeByNameCore(String runtimeClassName, Type[] genericTypes)

@ShadowDancer Can you confirm whether it crashes or if it is a first chance exception that you are able to click continue on and the app continues running?

@manodasanW this works in official 1.1, probably worked in this prerelease but I have visual configured to break on exception. Sorry for bothering you.


Unlikely benchmarked?

https://github.com/seritools/q565/blob/main/q565/src/streaming_no_header.rs#L87
In computer generated images, run length encoding is not that unlikely at all, why have you added this to this opcode? I only see 0xff being unlikely since it only appears once. (Could be also ignored if input stream is cut by last byte!)
(And btw, great project, loved reading it!)

That particular very specific ordering + unlikely gave a big perf improvement on my system because it coaxed LLVM to not generate a jump table but to a regular branching check, IIRC.
But yeah, mostly premature optimization because it's fun, will probably remove it sooner rather than later x)

(And btw, great project, loved reading it!)

Thanks! Hopyefully getting around to cleaning it up a bit more, soon. ^^

When you actually tested before and after, than I take back everything, I do not mind such stuff if it is tested!

Removed unlikely for now again


[BUG] Error creating default roles and permissions

Mage version
v0.9.67
Describe the bug
After enabling user authentication in a new environment (REQUIRE_USER_AUTHENTICATION=1), I get an error when creating the default roles and permissions. I get the following error message in the log:
2024-03-21 18:04:57 HTTPServerRequest(protocol='http', host='localhost:6789', method='POST', uri='/api/seeds?api_key=ABC', version='HTTP/1.1', remote_ip='<IP_ADDRESS>')
2024-03-21 18:04:57 Traceback (most recent call last):
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/tornado/web.py", line 1786, in _execute
2024-03-21 18:04:57     result = await result
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/server/api/v1.py", line 64, in post
2024-03-21 18:04:57     return await execute_operation(self, resource)
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/views.py", line 63, in execute_operation
2024-03-21 18:04:57     raise err
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/views.py", line 56, in execute_operation
2024-03-21 18:04:57     response = await base_operation.execute()
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/operations/base.py", line 92, in execute
2024-03-21 18:04:57     result = await self.__executed_result()
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/operations/base.py", line 459, in __executed_result
2024-03-21 18:04:57     return await self.__create_or_index()
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/operations/base.py", line 511, in __create_or_index
2024-03-21 18:04:57     result = await self.__resource_class().process_create(
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/resources/BaseResource.py", line 186, in process_create
2024-03-21 18:04:57     raise err
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/resources/BaseResource.py", line 174, in process_create
2024-03-21 18:04:57     res = await res
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/api/resources/SeedResource.py", line 9, in create
2024-03-21 18:04:57     await bootstrap_permissions()
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/authentication/permissions/seed.py", line 241, in bootstrap_permissions
2024-03-21 18:04:57     action_rules_mapping[model_name] = await action_rules(policy_class)
2024-03-21 18:04:57   File "/usr/local/lib/python3.10/site-packages/mage_ai/authentication/permissions/seed.py", line 174, in action_rules
2024-03-21 18:04:57     condition = config2.get('condition')
2024-03-21 18:04:57 AttributeError: 'list' object has no attribute 'get'
To reproduce

Activate user authentication (REQUIRE_USER_AUTHENTICATION=1)
Go to project settings > roles
Click on "Create default roles and permissions"

Expected behavior
No response
Screenshots
No response
Operating system
No response
Additional context
No response

This issue should be resolved in the next version of Mage (>= 0.9.69)


No liberty file is created for ROMs

Describe the bug
Note that I'm not an expert in this, but my understanding is that we need a liberty file to do static timing analysis of a ROM when incorporating it into a larger design as a pre-hardedn macro. In particular, openlane asks for this to be added in the EXTRA_LIBS environment variable. https://github.com/The-OpenROAD-Project/OpenLane/blob/master/docs/source/reference/configuration.md#macroschip-integration
However, the current rom compiler just says "# TODO: Characterize the design":
https://github.com/VLSIDA/OpenRAM/blame/0937f86761e727ae3ba6c3e0d6df8a84a760cf8a/compiler/rom.py#L147
So this isn't actually done yet.
Has a ROM generated by OpenRAM been used in a tapeout yet? I would love to see an example if so. I am a novice at this. I was trying to make a submission for tiny tapeout 6 of a tiny ROM, but got stuck at this point because I'm not sure how to proceed without the liberty file.
Version
top of dev branch
To Reproduce
No reproducer

You are correct that this isn't done. We hand made one for our tape out:
https://github.com/VLSIDA/openram_testchip2
The file isn't that far from the SRAM one so it wasn't that difficult.


Consider using n_init option for GClust

There is a lot of variability in model fit just based on the random initialization of k-means to GMM, I think we should consider allowing the user to do some number of inits for each set of clustering parameters

I'm having this same issue on my data set e.g. the number selected by BIC is variable (5-15) across multiple runs. Unfortunately it's a private dataset so I can't put up an easy example of this.
I modified GaussianCluster to allow for n_init and this fixed the variability problem. I'm going to submit a PR with this enhancement.


Avoid cloning KafkaConnection

This is rather a cleanup. Performance wise I could not measure any significant change.

+1
You can merge it now :)

many thanks for your review.


fix: convert YAML to TOML for deprecations reasons

Please see #21, I will merge this once Alacritty releases 0.13.


Docs - Incorrect instructions in quickstarts

Referring to the documentation on quickstarts/1_client_credentials.html.
In the section titled "Authorization at the API", I read the following instructions:
"Add the following to the Configure method in Startup"
I think this is suppose to be:
"Add the following to the ConfigureServices method in Startup"
I am using ASP.NET Core 3.1.301.

Please send a PR.

merged


Discussion - should we drop nodejs-common?

After looking around the codebase, it looks like the only part of nodejs-common that's being used is the logger.  This means that we're really unnecessarily pulling in request for no good reason.  Does it make sense to abstract the logging stuff in common out to it's own smaller-purpose module?

The TraceWriter class currently inherits Service, so for right now it seems like we are locked onto using nodejs-common.

I think this has been resolved as 'not yet', so I am going to close. If there is more to discuss, please reopen.


Customize warning and error symbols

I can't find anything in the docs, but is there any way to customize the ⚠and >> symbols used for warnings and errors in the gutter?

Use "diagnostic.errorSign", "diagnostic.warningSign" in your coc-settings.json.


Feature-Request: Ability to limit FPS

Hey!
The examples update time-dependent uniforms by adding a constant value in each frame.
Since FPS are not limited, on my machine, this results in animations that are way too fast.
Additionally, this leads to the GPU running at full capacity at all times, wasting resources.
Naive solution:
const MAX_FPS: f32 = 60.0;
const INTER_FRAME_MILLIS: u64 = (1000.0 / MAX_FPS) as u64;
fn draw(gfx: &mut Graphics, state: &mut State) {
    let start = std::time::Instant::now();

    let mut renderer = gfx.create_renderer();
    // Draw something!
    gfx.render(&renderer);

    // Update some uniform
    state.angle += 0.01;

    let elapsed_millis = start.elapsed().as_millis() as u64;
    if elapsed_millis < INTER_FRAME_MILLIS {
        std::thread::sleep(std::time::Duration::from_millis(INTER_FRAME_MILLIS - elapsed_millis));
    }
}

Maybe it'd make sense for the framework to provide the time that has elapsed since starting the program.
The solution above does not cover the case where we fall below expected FPS.
Uniforms should just depend on the time since start to make them independent from FPS anyway.

Hey @reformat0r !
Sorry for the late response. The App struct contains some time information.

app.timer.delta_f32() -> f32
app.timer.delta() -> Instant
app.timer.init_time() -> Instant

You can use the delta to calculate your uniforms, or if you want, you can check the init time or the delta to avoid draw to the GPU some frames.

Nice!

Do you think the framework should provide a way for the user to set the target (max) FPS?
Should I change the examples such that they use the delta-function to compute the uniforms? Otherwise people might wonder why the examples don't exhibit consistent behavior...

I think it's a good idea to provide a way to limit the frames. Let me think about it a little because it's possible to do this with a plugin, but it will need some changes in how the app loop works probably (to be sure that the delta times are right).
Said that I think that it's also a good idea to use the delta time to set the values of the uniforms or any other value that creates animation. Just to avoid weird visual glitches if the frame is not always the same.


Please add more docsearch_config pass-through support

I currently can't see a way to customize much using this extension beyond css: I checked the docs, and checked src:
Please expose more docsearch_config  options for users to pass through at conf.py :)
For example, an option to raise the max # of results seen (seemingly hard-coded to 5 with sphinx-docsearch) - or an option to show pagination (currently it's 5 results flat) - or some kind of "show all results" link at the bottom

I look forward to seeing maxResultsPerGroup - thanks, @kai687 ! Toss me a note when it's up and I'm happy to give it a whirl.


Message about CircularJSON is shown on install

Expected behaviour
No odd messages should be shown on install.
Actual behaviour
$ npm i<EMAIL_ADDRESS>
><EMAIL_ADDRESS>postinstall D:\sandbox\random\node_modules\circular-json
> echo ''; echo "\x1B[1mCircularJSON\x1B[0m is in \x1B[4mmaintenance only\x1B[0m, \x1B[1mflatted\x1B[0m is its successor."; echo ''

''; echo "\x1B[1mCircularJSON\x1B[0m is in \x1B[4mmaintenance only\x1B[0m, \x1B[1mflatted\x1B[0m is its successor."; echo ''
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

+<EMAIL_ADDRESS>added 257 packages from 502 contributors, removed 5 packages and audited 2341 packages in 36.856s
found 0 vulnerabilities

Environment Details

Karma version (output of karma --version): 3.0.0
Relevant part of your karma.config.js file: no karma config present.

Steps to reproduce the behaviour

npm install<EMAIL_ADDRESS>
Circular JSON seems to be an indirect dependency of log4js:
$ npm list circular-json
<EMAIL_ADDRESS>C:\Users\kamik\AppData\Local\Temp\angular-cli-create-z0dWss\help-project
`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>

So contact log4js.


Error using macros needed for decl_storage within substrate node template

error[E0463]: can't find crate for `hidden_include`
  --> /Users/shawntabrizi/Desktop/substrate-node-template/runtime/src/demo.rs:40:1
   |
40 | / decl_storage! {
41 | |     trait Store for Module<T: Trait> as Demo {
42 | |         Payment get(payment): Option<T::Balance>;
43 | |         Pot get(pot): T::Balance;
44 | |     }
45 | | }
   | |_^ can't find crate

This is the original error reported in https://github.com/paritytech/substrate/pull/1637#issuecomment-461598944
When changing the support macro from support to srml_support other erros appear:
error: cannot find macro `__dispatch_impl_metadata!` in this scope
  --> /Users/shawntabrizi/Desktop/substrate-node-template/runtime/src/demo.rs:11:1
   |
11 | / decl_module! {
12 | |     pub struct Module<T: Trait> for enum Call where origin: T::Origin {
13 | |         fn play(origin) -> Result {
14 | |             let sender = ensure_signed(origin)?;
...  |
37 | |     }
38 | | }
   | |_^
   |

The first error can not be solved by us, we need to wait for rust to fix this.
This means, we can not rename crates in Cargo.toml. If you want to rename srml_support, do it in lib.rs with extern crate srml_support as support;.
For the second problem, you need to fix this to $crate::__dispatch_impl_metadata! {.

Solved with #1742


Fix linear interpolation not working with mixed (int/float) keyframes

Fixes #85858.
It is possible in the editor to create both integer and float keyframes on an animation track. With the rework of variant interpolation and blending (#84815), linear interpolation lost its ability to interpolate between such keyframes (cubic interpolation works). This PR restores a special case handling for int/float pairs similar to what was there before the rework.

Thanks!

Cherry-picked for 4.2.2.


Tomcat redeploy using OrientGraphFactory

Hello,
I'm having issues when my CI server redeploys the webapp in a Tomcat servlet container.
What I've do and tested is create a ServletContextListener which on initialization starts the persistance layer by executing the following methods:
private OrientGraphFactory graphDB;
private OrientGraphFactory oauthDB;
[....]
OGlobalConfiguration.STORAGE_KEEP_OPEN.setValue(false);
String orientdbHome = this.cfg.getEnvirontment().getOrientDBHOME();
System.setProperty("ORIENTDB_HOME", orientdbHome);
String url = this.cfg.getEnvirontment().getOrientDBDatastore();
String oauthDbURL = this.cfg.getEnvirontment().getOrientDBOAuth();
graphDB = new OrientGraphFactory("plocal:" + orientdbHome + "/databases/" + url).setupPool(1, 10);
oauthDB = new OrientGraphFactory("plocal:" + orientdbHome + "/databases/" + oauthDbURL).setupPool(1, 10);

Then, on redeploy the contextDestroyedMethod calls the persistence close function:
graphDB.close();
oauth.close();

I use the db like the following snippet. I think thats the proper way to use the graphFactory.
OrientGraph graph = graphDb.getTx();
		try {
			A3HashMap<String, Object> prop = new A3HashMap<String, Object>();
			prop.put(User.ID, u.getId());
			prop.put(User.NAME, u.getName());
			prop.put(User.EMAIL, u.getEmail());
			prop.put(User.PASSWORD, PasswordUtil.encryptPassword(password));
			prop.put(User.PROVIDER, u.getProvider().ordinal());
			prop.put(User.ENABLED, u.isEnabled());
			prop.put(User.TIMESTAMP, u.getTimestamp());
			prop.put(User.CREATION_DATE, u.getCreationDate());

			prop.cleanNullValues();

			graph.addVertex(A3DBClasses.USER, prop);
		} catch (OValidationException e) {
		} finally {
			graph.shutdown();
		}

Thanks in advance!
Gerard.
PS: This is the log from tomcat when trying to redeploy:
###################################
Destroying context
###################################

jul 22, 2014 9:02:19 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:19 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [OrientDB MemoryWatchDog] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:19 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [OrientDB WAL Flush Task (aaaida-db)] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:19 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [OrientDB WAL Flush Task (oauth-db)] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:19 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [OrientDB WAL Flush Task (aaaida-db)] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:19 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [Thread-21] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:19 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [OrientDB Write Cache Flush Task (aaaida-db)] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:20 PM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/aaaida-server]
jul 22, 2014 9:02:21 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/aaaida-server.war
Starting context
jul 22, 2014 9:02:30 PM org.apache.catalina.core.StandardContext startInternal
Grave: Error listenerStart
jul 22, 2014 9:02:30 PM org.apache.catalina.core.StandardContext startInternal
Grave: Context [/aaaida-server] startup failed due to previous errors
###################################
Destroying context
###################################

jul 22, 2014 9:02:31 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:31 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
Grave: The web application [/aaaida-server] appears to have started a thread named [OrientDB MemoryWatchDog] but has failed to stop it. This is very likely to create a memory leak.
jul 22, 2014 9:02:38 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.  Could not load java.lang.management.MemoryMXBean.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1597)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1556)
        at com.orientechnologies.orient.core.memory.OMemoryWatchDog$3.run(OMemoryWatchDog.java:163)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)

jul 22, 2014 9:02:38 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.  Could not load java.lang.management.MemoryUsage.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1597)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1556)
        at com.orientechnologies.orient.core.memory.OMemoryWatchDog$3.run(OMemoryWatchDog.java:164)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)

jul 22, 2014 9:03:16 PM org.apache.catalina.util.LifecycleBase stop
INFO: The stop() method was called on component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/aaaida-server]] after stop() had already been called. The second call will be ignored.
jul 22, 2014 9:03:17 PM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/aaaida-server]
jul 22, 2014 9:03:17 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/aaaida-server.war
Starting context
jul 22, 2014 9:03:26 PM org.apache.catalina.core.StandardContext startInternal
Grave: Error listenerStart
jul 22, 2014 9:03:26 PM org.apache.catalina.core.StandardContext startInternal
Grave: Context [/aaaida-server] startup failed due to previous errors

I'm still seeing this same issue with version 2.1.10. I'm running OrientDB embedded (plocal) in a Tomcat web app using SpringMVC.
I'm using Ivy for dependencies:
	<dependencies defaultconf="*->*,!sources,!javadoc">
		<dependency org="com.fasterxml.jackson.core" name="jackson-databind" rev="latest.release" />
		<dependency org="org.springframework" name="spring-context" rev="latest.release" />
		<dependency org="org.springframework" name="spring-webmvc" rev="latest.release" />
		<exclude org="com.ashtonit" module="odbresource" />
		<exclude org="javax.servlet" />
	</dependencies>

And https://github.com/skwidge/OdbResource/releases/tag/v2.0.1 in the apache-tomcat/lib directory.
Tomcat is version 8.0
2016-02-29 21:31:12:951 INFO  A valid shutdown command was received via the shutdown port. Stopping the Server instance. [StandardServer]
2016-02-29 21:31:12:952 INFO  Pausing ProtocolHandler ["http-nio-8080"] [Http11NioProtocol]
2016-02-29 21:31:12:955 INFO  Pausing ProtocolHandler ["ajp-nio-8009"] [AjpNioProtocol]
2016-02-29 21:31:13:006 INFO  Stopping service Catalina [StandardService]
2016-02-29 21:31:13:018 INFO  Destroying Spring FrameworkServlet 'dispatcher' [[/MyWebApp]]
2016-02-29 21:31:13:028 WARNI The web application [MyWebApp] appears to have started a thread named [OrientDB WAL Flush Task (tm)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 java.lang.Thread.run(Thread.java:745) [WebappClassLoaderBase]
2016-02-29 21:31:13:028 WARNI The web application [MyWebApp] appears to have started a thread named [OrientDB Write Cache Flush Task (tm)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 java.lang.Thread.run(Thread.java:745) [WebappClassLoaderBase]
2016-02-29 21:31:13:035 INFO  Stopping ProtocolHandler ["http-nio-8080"] [Http11NioProtocol]
2016-02-29 21:31:13:037 INFO  Stopping ProtocolHandler ["ajp-nio-8009"] [AjpNioProtocol]
2016-02-29 21:31:13:043 INFO  Destroying ProtocolHandler ["http-nio-8080"] [Http11NioProtocol]
2016-02-29 21:31:13:044 INFO  Destroying ProtocolHandler ["ajp-nio-8009"] [AjpNioProtocol]


Feature Request: Scrollable progress bar

See above: the progress bar only lets you see a small subset of the current jobs. It would be nice if I could scroll through and see them all.

Much better solution coming soon, @benjamin-manning cc: @apostolosfilippas

:)


[HUDI-1865] Make embedded time line service singleton

The filesystem view takes too much memory, make it process singleton.
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2892 (ab94864) into master (3867676) will decrease coverage by 60.39%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #2892       +/-   ##
============================================
- Coverage     69.75%   9.36%   -60.40%
+ Complexity      375      48      -327
============================================
  Files            54      54
  Lines          1997    1997
  Branches        236     236
============================================
- Hits           1393     187     -1206
- Misses          473    1797     +1324
+ Partials        131      13      -118

Flag
Coverage Δ
Complexity Δ

hudiclient
?
?

hudiutilities
9.36% <ø> (-60.40%)
48.00 <ø> (-327.00)

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

 The change is out of my range.

Close the PR because the CI always fails with jar pulling.


Make source gathering subprocesses able to give feedback

This PR introduces a way for the programs in charge of downloading or decoding data mandatory for the manifest building to be able to report the status of each download/decoding.
Originally this PR was aiming only at fixing some issues with curl, but I decided to extend it to inline and ostree since they could suffer from the same kind of issues.

This new version would need for the pr #998 to land first. I'm keeping the two commits in this one for now. This is a new "rewrite" of the solution.
In this version the important changes are:

Based on the work of the PR #998, sub-programs declare a list of SourceFetcher. Each SourceFetcher is responsible of downloading one element. The framework takes care of the execution of the downloading. Either in parallel or in sequence depending on the flavor of SourceService that is used.
Since we have a framework, I managed it will be better if signaling the error was done in it the abstraction layer. So sources.py surrounds the call on fetch() by a try block and is catching any SourceError and forwards them to the client side via the emit_signal function. This is nice because, in the actual downloading program we don't have to care about communications or signaling, we just execute the program until there's an issue, and if there is one, we raise a SourceError.
The downside of raising a SourceError, is that this type is not serializable. Raising a SourceError in a subprocess makes the python machinery crash. However, I decided to work around this issue by changing the ProcessPool to a ThreadPool. I assume it changes nothing performance wise because even though python has GIL, we are actually spawning subprocess to do the actual curling. Of course the question will need to be raised again if we actually need real python parallelization in the future.

I think also that this work paves the way for the monitoring. In the sense that, the framework could, by calling the do_fetch() method on the SourceFecthers give a monitor object as a parameter (as done for the stages or pipelines). This monitor would be able to communicate events through the emit_signal function
Also, I don't think this version prevents from keeping each individual download result even if an error occurred. And it could be easily done in the framework side.

Thanks for the review, I think I have a better proposal now.
I simplified #998 to have a solution with fetch and download methods normalized.
I use this in the fist commit on the PR, then on a follow-up commit I implement the core of your recommendations.


UI of ChatActivity

Fixes #90

redesigned the chat list and shifted the send image icon

redesigned the chat list and shifted the send image icon


Build(deps-dev): Bump @storybook/addon-actions from 6.4.21 to 6.4.22 (#3356)

Pull request opened by the merge tool on behalf of #3356

Merged in 80f43e30a53185ac43984bdb55ce20b9dce888cd


Default rest parameter names to destructuring names when of an anonymous tuple

🔍 Search Terms
default rest parameter name destructure anonymous tuple
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
Right now, when calling a function with an inline destructured rest parameter whose type is an anonymous tuple, the inferred variable names will be auto-generated like __0_0:
function withPair(...[first, second]: [number, named: string]) { }

withPair(/* __0_0: number, named: string */ 0, "");

In cases where the tuple is destructured inline, how about any constant/static destructuring names being used as a fallback for anonymous tuple elements?
I.e.:
function withPair(...[first, second]: [number, named: string]) { }

withPair(/* first: number, named: string */ 0, "");

📃 Motivating Example
The pattern of immediately destructured rest parameters of a tuple is one that sometimes gets used for better type safety on parameters than generics or overloads. One downside, though, is that developers have to either explicitly add names to the tuple type or suffer from poor auto-generated parameter hints.
A slightly more real-world example:
interface AppleInfo {
  color: "green" | "red";
}

interface BananaInfo {
  curvature: number;
}

type FruitAndInfo = ["apple", AppleInfo] | ["banana", BananaInfo];

function logFruitTuple(...[fruit, info]: FruitAndInfo) {
  switch (fruit) {
    case "apple":
      console.log(`My apple's color is ${info.color}.`);
      break;
    case "banana":
      console.log(`My banana's curvature is ${info.curvature}.`);
      break;
  }
}

logFruitTuple(/* __0_0: "apple", __0_1: AppleInfo */ "apple", { color: "red" });

With this suggested change, the parameter hints for logFruitTuple would instead be:
logFruitTuple(/* fruit: "apple", info: AppleInfo */ "apple", { color: "red" });

💻 Use Cases
This pattern of destructuring rest parameters of a tuple type allows for precise descriptions of type parameters. It can sometimes be preferable for types over:

Function overloads: which allow for descriptions of different call signatures for a function, but the function's body doesn't apply type narrowing based on them (function overloads playground)
Generic functions: which also can't always type narrow internally (generic function playground)

Thanks to @evangalen for noting this in https://twitter.com/EmilVanGalen/status/1719622053769216013!

I think I can do this, would you recommend this for a beginner @RyanCavanaugh


Fix the MIT License  content

@plushugh
In the MIT License, it says "Copyright (c) 2023 Treee Studio". Which used to be our organization

I have edited.
Plz review.

#34


Wasr-T code release

Good afternoon, could you tell, please, when you'll release code for the new Wasr-T neural net? https://arxiv.org/pdf/2203.05352.pdf

We plan to release the code for WaSR-T soon (during the summer). I will let you know once the code is available.

I'm happy to let you know, that the code for WaSR-T is now available. You can find it here: https://github.com/lojzezust/WaSR-T


Scheduled loop handler for nodes

First off, Homie is awesome! I really like how easy it is to make something without having to write boilerplate MQTT code, wifi setup, etc, etc. Thanks for the hard work!
It's a bit awkward to deal with many sensors that need to be update at different time intervals. The main Homie loop needs to keep track of elapsed time, and it just seems to go against individual handlers that settable nodes use.
I think it would be more elegant if it was possible to set individual loop handlers for nodes, with a custom interval. So basically like a scheduler, like...
temperatureNode.setLoopFunction(TempLoopHandler, 5000);
temperatureNode.advertise("degrees");

Some extra helpful functions would be a way to start/stop the schedule events and change the time interval.

👍

You can relatively easy accomplish this using the TimeAlarms.h arduino lib.
https://github.com/PaulStoffregen/TimeAlarms
I do the following
`
#include <TimeAlarms.h>
const int WEATHER_INTERVAL = 180;
void loopHandler() {
Alarm.delay(0);
}
void setup() {
....
Homie.setLoopFunction(loopHandler);
Alarm.timerRepeat(WEATHER_INTERVAL, WeatherUpdate);
}
`
With NTP it is also possible to set the time and trigger an event at a fixed time.

I've been doing this by using Timer class from Homie core. Looking at my project this really could be embedded to the loop call, because in practice all my loop functions have to perform some kind of timing control...
+1
Sent from my iPhone

On 8 Dec 2016, at 06:15, furyfire<EMAIL_ADDRESS>wrote:
You can relatively easy accomplish this using the TimeAlarms.h arduino lib.
https://github.com/PaulStoffregen/TimeAlarms
I do the following
`
#include <TimeAlarms.h>
const int WEATHER_INTERVAL = 180;
void loopHandler() {
Alarm.delay(0);
}
void setup() {
....
Homie.setLoopFunction(loopHandler);
Alarm.timerRepeat(WEATHER_INTERVAL, WeatherUpdate);
}
`
With NTP it is also possible to set the time and trigger an event at a fixed time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Definitely, good idea! This will be a post 2.0 feature, as we need to focus on stability (the dev branch seems pretty buggy right now.
Sorry for the long response time, studies are my priority!

This would be a very useful feature, so it would be really nice to have it implemented. I agree that this is too much for 2.0 and focus now should be on stabling the 2.0, so it can be officially released.
However, I don't think that 2.0 is that buggy - I think it is more that Homie is more and more known so it also attracts some novice C++ developers. Most of the bugs that make Homie seem unstable are actually caused by problems outside Homie.
The step (for the developer) from some simple playing around with an arduino to a real project with Homie and maybe some other libraries is huge.
Maybe some kind of Community Forum would be good to help Homie user and make the issue tracker focus more on real bugs again.

@euphi you're right. I just created a Gitter room, a badge on the README and a link to the room in the issue template.

👍  this would be great to have

Missed this
Since I'm going to be adding a new event bus and trimmer mechanism it would be easy to add to v2.2


misc/test_layernorm.py::test_layernorm_mix_precision mismatch

Command to run:
pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision
All the errors are float32:
=============================================================== short test summary info ===============================================================
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7800511474028167
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.696830280445704
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.9028278880387816
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.728569147644891
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.953830626775725
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.8799854050396232
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7825994085803905
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7017235847606049
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.8987713880620999
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7415875788499321
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.9044729047582791
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.8868642977685586
=============================================== 12 failed, 24 passed, 36 warnings in 264.05s (0:04:24) ================================================

This suite passes when fp32_dest_acc_en is disabled in misc/test_layernorm.py  @ncvetkovicTT could you help take a look at this?

Hey @abhullar-tt, @bbradelTT. Please take a look at ncvetkovic/14352_layernorm_fail so that we can continue the investigation. What I've done there is run only test_id=0 and in_dtype=float32 for simplicity. I have then played around with input shapes, because I suspected that either input width or height can't be larger than 4 fp32 tiles, because when we haveDstSync::SyncHalf, that's how many tiles can fit in half of the DEST.
Also, if the width is kept at 4 tiles, height can't be larger than 130 tiles, I assume this is core grid constraint because I remember seeing that number somewhere, but I am not sure.
Now there are a couple of things I don't understand here:

If I keep Wt at 2 tiles, I can do whatever I want with N, C and Ht. If I put Wt=3, then the same constraint applies as with Wt=4.
If I run all the tests for all the in_dtypes and all of the shapes that are uncommented in my branch, the last six examples fail like this (a drawback is that I don't know for which shape this was, but test passed for [1,1,32,32]):

=================================================================================================================================================================================================== short test summary info ====================================================================================================================================================================================================
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN-FLOAT32-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_RMSN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_G-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_G-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_GB-BFLOAT16-BFLOAT16-in0_L1-in0_L1]
PASSED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_GB-BFLOAT8_B-BFLOAT16-in0_L1-in0_L1]
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7051563259499515
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7510356020184914
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[LN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.8523632833423422
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7096639868818564
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_G-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7260290469183038
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[RMSN_GB-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.8573792455041984
========================================================================================================================================================================================== 6 failed, 30 passed, 36 warnings in 57.88s ==========================================================================================================================================================================================

Please notice again my comments in the test_dims array. Look closely the PCC difference as we increase the height of the block from 130 to 131 tiles and beyond - the PCC gradually decreases, meaning that the first 130x4 tiles are transferred and processed correctly, but the rest are not (they're either transferred poorly, or not processed properly by the compute kernel).
I can continue the hunt once we bring the test to the point where it fails for a single tile, just let me know.

Tried also on WH, all input shapes and test variants pass there.

Hey @bbradelTT, you can also take a look at #14594. As you can see, there the W dimension doesn't matter, or at least it is limited by L1/CB size and not DEST size.

I think the 130 was mentioned in https://github.com/tenstorrent/tt-metal/issues/14609#issuecomment-2491915367
I tried the fix in https://github.com/tenstorrent/tt-llk-bh/pull/50 as well as https://github.com/tenstorrent/tt-llk-bh/compare/main...nvelickovic/fix_pack_tilize
Neither of them made the tests pass.
The PCC is changing non deterministically, and is different for each run:
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7797403340938521
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7788630498131559
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7796628078216301
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7783906940655255

The rejected fix main factor seems to be https://github.com/tenstorrent/tt-llk-bh/commit/464f00bdf3972d09cae21393820664c8e74d22c5 made the PCC
When I had that in I got the following:
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7800424651589892

I think the 130 was mentioned in #14609 (comment) I tried the fix in tenstorrent/tt-llk-bh#50 as well as<EMAIL_ADDRESS>Neither of them made the tests pass.
The PCC is changing non deterministically, and is different for each run:
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7797403340938521
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7788630498131559
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7796628078216301
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7783906940655255

The rejected fix main factor seems to be tenstorrent/tt-llk-bh@464f00b made the PCC When I had that in I got the following:
FAILED tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision[add_LN-FLOAT32-BFLOAT16-in0_L1-in0_L1] - AssertionError: 0.7800424651589892

@bbradelTT wait an hour or so pls, I think I might have a solution for you.

Update from @ncvetkovicTT : A delay in the MATH thread by a certain known amount at a certain pinned-down location results in the weird zeroes in a [1,1,32,96] tensor disappearing.
Looks like a synchronization issue.

Looks there's a race between PACK and MATH when clearing DEST in FP32 mode. There's a missing if-statement from the very creation of the file llk_math_eltwise_binary.h when performing mul_tiles_bcast_cols. When the missing if-statement is added, the minimal test case passes. Should get results for the full test_layernorm_mix_precision soon.

@ncvetkovicTT could you please point me to code I can test out on my end?

Sure, please take a look at ncvetkovic/14352_layernorm_fail again and run pytest tests/tt_eager/python_api_testing/unit_testing/misc/test_layernorm.py::test_layernorm_mix_precision. Once you are satisfied, we can create a PR. Unfortunately, this fix doesn't resolve other layernorm/softmax issues, although for layernorm_sharded I already see a failure pattern.

@bbradelTT @nvelickovicTT @ttmtrajkovic
Putting in writing a lore of this issue. While debugging the issue we found out that there's a missing if-statement in _llk_math_eltwise_binary_ when doing element-wise multiplication with column-wise broadcast. This if-statement check wether or not DEST is being reused. If yes, DEST needs to be cleared. Because layernorm.cpp doesn't reuse DEST, this if-statement alone makes the test pass, thus fixing the issue.
Another thing noticed while debugging this issue is tha delaying of MATH thread prior to clearing the DEST also fixes the problem. That's why we have created a bug ticket #15713 trying to resolve the apparent race between PACK and MATH threads. However, this delay only made the problem invisible, and not go away. The real problem here is that ZEROACC instructions called in the mentioned execution branch were used incorrectly. On WH_B0, two ZEROACC instructions are needed to clear half of a face each, because ZEROACC cleared 8 x 16 datums (half of a face) if we use CLR_16 mode and set fp32 bit to true. On BH, however, this is not the case - CLR_16 mode will always clear 16 x 16 datums (a whole face), size of which is determined by fp32 bit of the instruction. Therefore, we need to change from clearing two halves of a face:
TT_ZEROACC(ZERO_ACC_MODE, 1/*clear fp32*/, 0, ADDR_MOD_1, ((get_dest_buffer_base() >> 4) + (dst_index << 3)) + (0 +       n*2)); // Clear lower half of faces 0 & 1
                            TT_ZEROACC(ZERO_ACC_MODE, 1/*clear fp32*/, 0, ADDR_MOD_1, ((get_dest_buffer_base() >> 4) + (dst_index << 3)) + (0 + ((n*2)+1))); // Clear upper half of faces 0 & 1

to clearing a full face in one instruction:
TT_ZEROACC(ZERO_ACC_MODE, 1/*clear fp32*/, 0, ADDR_MOD_1, ((get_dest_buffer_base() >> 5) + (dst_index << 2)) + (0 +         n));

This issue was used to confirm the behavior of the change, by removing the if-statement, therefore forcing MATH to clear DEST even if it's not reused. The test fails if two ZEROACCs are used, and passes if one correct ZEROACC is used.

PR #15754 is merged, the issue can be closed.


unexpected volume

Im a little bit puzzled, could be an error on my side, im docker newbie:
I use this docker compose configuration with Traefik 3x and Mailcow, works fine:
    certdumper:
      image: ghcr.io/kereis/traefik-certs-dumper
      command: --restart-containers ${COMPOSE_PROJECT_NAME}-postfix-mailcow-1,${COMPOSE_PROJECT_NAME}-nginx-mailcow-1,${COMPOSE_PROJECT_NAME}-dovecot-mailcow-1
      network_mode: none
      volumes:
          # Mount the volume which contains Traefik's `acme.json' file
          #   Configure the external name in the volume definition
        - acme:/traefik:ro
          # Mount mailcow's SSL folder
        - ./data/assets/ssl/:/output:rw
          # Mount docker socket to restart containers
        - /var/run/docker.sock:/var/run/docker.sock:ro
      restart: always
      environment:
          # only change this, if you're using another domain for mailcow's web frontend compared to the standard config
        - DOMAIN=${MAILCOW_HOSTNAME}

volumes:
  acme:
    external: true
    # Name of the external docker volume which contains Traefik's `acme.json' file
    name: traefik_acme

The thing which puzzles me, im always getting a unnamed volume when certdumper runs, which gets abandoned after every restart:
# docker container inspect  -f '{{ range .Mounts }}{{ .Name }}:{{ .Destination }} {{ end }}'  260f7a6a611e

:/output :/var/run/docker.sock traefik_acme:/traefik d31e21dba89964178c9fe031131c15469ccec6a3a8d25764d1ddf9ce78e01a9a:/var/lib/docker

Where is the volume linked to /var/lib/docker coming from?

Hi @tomelgato,
sorry for the late response, it got lost in notifications and I didn't really pick up the time to take a look.
The Docker image uses docker:25.0.3 as base image, which in turn automatically creates a volume via VOLUME /var/lib/docker (e. g. https://github.com/docker-library/docker/blob/master/27/dind/Dockerfile#L104). I don't know if I can do anything about that.
I hope that answer your question. :)

Why using a DinD image as a base?


quoted tags do not work

:scope main  doesn't give the same result as :scope "main"

Hi, thanks for the bugreport.
Could you give me a example org-file that produces the problem for you?
:scope is only implemented for nil, tree and files ...


Remove christmas tree image src from body in css, link it via html though

The christmas trees in the other projects directory was merging with the text, so I made a new css and removed that, not I realize that in the lyrics directory, in the songs its coming in the bottom corners but in https://mogulchristmas.kendalldoescoding.gq/lyrics there is half a christmas tree.
I need to figure out how to make a div class in index.html and in index.html for each of the song lyric directory too and link that christmas tree image to that, and nothing else, cause rn its linked to the body in css to all the pages.
@Bibhavshah, @TechStudent11 I need your help for this.
EDIT: I don't mind if main.css is in the other projects directory now but now #83 fixes the christmas tree issue.

I don't understand what you want me to do.

I don't understand what you want me to do.

@TechStudent11 In the other projects directory I added main.css because it was interfering with the text, in the lyrics directory its coming in the top corners. I only want the christmas trees in the bottom corners for the main website and not for other directories within the website.
Did you understand know?
Let me know if you got any doubts,
Kendall Does Coding

@KendallDoesCoding that seems like basic CSS.

Uh, so quick question, how and where did you add the trees?

Uh, so quick question, how and where did you add the trees?

I did it the worst way possible, and added it to the body in styles.css lol

BRO WHY

BRO WHY

I didnt know any other way lol. I mean, I did but I kinda forgot lol. That's why I asked for some help with this lol, but ik its basic

This is also causing me serious issues, because now only if the page size is 125 even in the main directory will the trees show in the bottom right & left corner. I would like if you could help me arrange it a little better lol @TechStudent11

@TechStudent11 You working on this?

@KendallDoesCoding tbh I'm not sure how I can. Wait, I just got an idea.

@KendallDoesCoding tbh I'm not sure how I can. Wait, I just got an idea.

Ok!

You creating a PR with your idea then @TechStudent11 ?

@TechStudent11 You working on this with your idea?

@TechStudent11 You working on this with your idea?

@TechStudent11 Waiting for your reply on this.

@KendallDoesCoding School in Ontario is starting so I don't really have time.

Ok!
On Wed, 5 Jan 2022 at 18:44, TechStudent10 @.***> wrote:

@KendallDoesCoding https://github.com/KendallDoesCoding School in
Ontario is starting so I don't really have time.
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/60#issuecomment-1005675087,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTNNEXV6XKDB6X7NCDLUUQ7Z3ANCNFSM5KYWGQYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@aliraza944 would like to work on this?

@aliraza944 would like to work on this?

Idk, what was your idea, can you please explain here?

What I was planning to do was to add a class to the body in the index. Then, using CSS, only apply it to the index.

You can add the CSS file for the lyrics directory. I mean when the project gets bigger it will help you organize and customize your CSS better.

You can add the CSS file for the lyrics directory. I mean when the project gets bigger it will help you organize and customize your CSS better.

True.

Since you guys are not using any JS library I'd suggest keeping the CSS short and near the folder, it is being used. Create a new CSS file for any new feature you add to the project.

Since you guys are not using any JS library I'd suggest keeping the CSS short and near the folder, it is being used. Create a new CSS file for any new feature you add to the project.

Agreed.

Yeah, good idea. I'll do this for the lyrics directory later in the day.
On Mon, 10 Jan 2022 at 22:56, Ali Raza @.***> wrote:

Since you guys are not using any JS library I'd suggest keeping the CSS
short and near the folder, it is being used. Create a new CSS file for any
new feature you add to the project.
—
Reply to this email directly, view it on GitHub
https://github.com/KendallDoesCoding/mogul-christmas/issues/60#issuecomment-1009156146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGJUTPLNRKUIL7H6ASAFZTUVMJEXANCNFSM5KYWGQYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

EDIT: I don't mind if main.css is in the other projects directory now but now #83 fixes the christmas tree issue.

I still need to delete the image src from body though, even though the issue was more or less sorted by #83 I need to just add the img src in html and format it in css, but I may need help though still.

I still need to delete the image src from body though, even though the issue was more or less sorted by #83 I need to just add the img src in html and format it in css, but I may need help though still.

@TechStudent11 I'll try to do this myself, but can you work on this?

I still need to delete the image src from body though, even though the issue was more or less sorted by #83 I need to just add the img src in html and format it in css, but I may need help though still.

@TechStudent11 I'll try to do this myself, but can you work on this?

I'm currently working on #105, sorry. I also have school, so yeah.

I still need to delete the image src from body though, even though the issue was more or less sorted by #83 I need to just add the img src in html and format it in css, but I may need help though still.

@TechStudent11 I'll try to do this myself, but can you work on this?

I'm currently working on #105, sorry. I also have school, so yeah.

No probs! I'll try doing this myself and ask you if something goes wrong.

I made this PR, mainly because the christmas trees were showing little above bottom right/left, I think this issue should be fixed though so closing this for now, Will re-open if needed in the future.


fix unaligned 64-bit atomic operation issue on arm32 device

refer to:
https://pkg.go.dev/sync/atomic#pkg-note-BUG

Thx


ci: Adding contents permission to E2E testing for release-v0.31.x

Fixes #N/A
Description

adding contents permission to E2E testing

How was this change tested?

N/A

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 84.167%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
6868

Relevant Lines:
8160

💛  - Coveralls


Make tsi handshaker result unused bytes const

Since unused bytes are owned by tsi_handshaker_result, caller is not supposed to modify it. We shall pass const unsigned ** in tsi_handshaker_result_get_unused_bytes().

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

This is a simple change. Appreciate quick review.


custom filter for selecting all rows in grid

I'm having scenario in which all the rows need to be selected if it contains a check box else the row should not be selected.Help me solve out.
Thanks in advance..

See slickgrid.net. Ask on StackOverflow. Give a more detailed question with an image if possible.

Sorry for the late reply..
Please,see the snapshot in that im not having checkbox in the row but,it is still selected.How to set filter for that.?

... follow previous advice (1 out of 3 so far) ....

Hi,
I've asked this in stackoverflow no response yet.Is it possible to get a solution.
Please find it in the link,
https://stackoverflow.com/q/51378625/9960181

Got the solution.Find it in the above link


Downloaded files are empty 0kb

Every playlist, album or song just creates an empty file, I'm on Nougat with Magisk, help!!

I've heard some report of that, can't reproduce it yet though. In v0.9.7 I'll add some checks whether the file was exported successfully, and if not, examine what is special about the environment.

Any idea of when we will have an update coming?

No, I currently have a lot of other stuff to do.. But I'll try to fit it in somewhere. May I ask what ROM you are using? And the version of Play Music? µG or regular GApps?

Galaxy s4 CrDroid rom

I have that device lying around somewhere, I'll try to reproduce this environment as close as possible. just stock opengapps? Which crdroid build?

Just changed to Resurrection Remix 7.1.2, same issue.
Hopefully you can fix it, also it depends on your model, mine is i9505 or *jfltexx"
If you have the same here's the link: https://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-resurrection-remix-v5-8-0-t3507378

That's the international version, right?

Yes it is, so I just clean same rom again and it finally worked, I think it has something to do wuth Magisk hide mode to enable safetynet, can you test that out so I won't screw my phone again? ):

I was using the app on Lineage with MagiskSU and Magisk hide successfully, so that shouldn't have been the problem. I can test it with the S4 once I get that again, my sister had it with her, and she visits tomorrow, and then I won't have time for at least a week, so you gotta wait a bit.

Absolutely, I really appreciate your work and support! Thank u so much!

no problem :) Let's just hope it keeps on working for you ^^

So I understand that this is a dead issue, but I'm on an LG G3, VS985 on LineageOS with MagiskSU and Magisk Hide.  Same exact issue.  All I had to do was flip MagiskHide to off, and for whatever reason, boom, fixed.  Still though, thank you for your work!

Does anyone still have problems with this?


Add Aktiv Grotesk support in storybook

This update adds the ability to change the Storybook default font to Aktiv Grotesk.
It currently only support 400 (regular), 500 (medium) and 700 (bold) weights because HSDS-core and HSDS-product only use those weights right now.

How
The decorator will add a classname on the body with-aktiv. The classname will update the css variable --BlueConfigGlobalFontFamily with the new font-family.
Storybook decorator
You can apply the font in two different ways:
Decorator
import withAktiv from './utils/withAktiv'

const stories = storiesOf('Text', module)
stories.addDecorator(withAktiv())

Component
import { WithAktiv } from './utils/withAktiv'

const stories = storiesOf('Text', module)
  .add('weights + hs-app font', () => (
    <WithAktiv>

        <Text weight={700}>Font weight: 700</Text>

        <Text weight={500}>Font weight: 500</Text>

        <Text weight={400}>Font weight: 400</Text>

    </WithAktiv>
  ))

Pull Request Test Coverage Report for Build 1837

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1836:
0.0%

Covered Lines:
7239

Relevant Lines:
7239

💛  - Coveralls


chore: drop deprecated 'pkg_resources' in favor of importlib

SUMMARY
The use of package pkg_resources is deprecated in favor of importlib.
This PR makes changes according to the importlib migration guide.
As this PR uses importlib.resources.files which was introduced in Python 3.9 (Superset is released with Python 3.8), I will mark this PR as draft.
Resolves https://github.com/apache/superset/issues/23899
TESTING INSTRUCTIONS
./scripts/tests/run.sh
ADDITIONAL INFORMATION

[x] Has associated issue: fixes https://github.com/apache/superset/issues/23899
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Hello @sebastianliebscher! Thank you for the contribution.
Can we also use importlib instead of import imp # pylint: disable=deprecated-module ?

the imp module is deprecated in favour of importlib and slated for removal in Python 3.12

Also use setuptools  instead of distutils and numpy.distutils module

The distutils package is deprecated and slated for removal in Python 3.12
numpy.distutils is deprecated since NumPy 1.23.0

Hi @sebastianliebscher! Do you have an account in superset slack?

@EugeneTorap it seems the link to join Supersets Slack is no longer valid, at least for me. https://github.com/apache/superset/blob/master/README.md?plain=1#LL138C32-L138C65

@sebastianliebscher Use this one - https://join.slack.com/t/apache-superset/shared_invite/zt-1mh158vmv-y67mOpmxjJyOKmJTUmYGhw

@rusackas Can we fix the invite link?

Thanks for pointing this out. It's fixed now.

@EugeneTorap This PR also drops imp in favor of importlib.

Removing distutils is in another PR: https://github.com/apache/superset/pull/24001 @EugeneTorap

I used an importlib function (.select for entrypoints) only available in Python 3.10, so this is still a draft. Maybe I figure out how to do this with Python 3.9.

Superseded by https://github.com/apache/superset/pull/24514 and https://github.com/apache/superset/pull/24578. Great work @cwegener!


Temporary fix to single facet detection

DK spotted that the processedData Dictionary was using 'undefined' the string as the key, not undefined the value.
We should probably think of a better solution than this.
We could get real life data with 'undefined' values.

@bobular this solution works for the cases I reported at Slack 👍

I didn't know you did set undefined as a key in the code smile Yes it would work as well +1

I'm surprised (and annoyed) it didn't complain and just used the string version...


Finalize the Router / Robot setup documentation

-> https://github.com/cloud-native-robotz-hackathon/hackathon-docs/tree/master/facilitator

Closed, this will be done with #23


add notebook

Codecov Report

Merging #7 (a172307) into main (bd72487) will decrease coverage by 0.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
- Coverage   92.30%   92.10%   -0.21%
==========================================
  Files           3        3
  Lines          39       38       -1
==========================================
- Hits           36       35       -1
  Misses          3        3

Impacted Files
Coverage Δ

src/pyDataverse.jl
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Fix implementation of bsearch in GitlabCI#determine_merge_request_id

This is a very simple PR, just change the == operator to >= according to ruby doc

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.
You can find it at CHANGELOG.md.

          1 Warning

:warning:
Tests were not updated

          1 Message

:book:
@dvlprliu is not a contributor yet, would you like to join the Danger org?

  Generated by :no_entry_sign: Danger

@DangerCI Of course, would love to. 😃

👍 Alright - I've sent the invite, and this looks good to me

I'm not sure this PR is the reason but Danger posts comments to the wrong Merge Request.

I'm not even sure whether it's safe to use bsearch on this array. It's definitely sorted but not by mr.sha. Am I missing something?

@nikolaykasyanov @orta I'm pretty sure that this is a reason, cause sha and base_commit are string and in ruby:
'dcb' > 'abc'
 => true
'abc' >= 'dcb'
 => false

We are not sorting array here, this block returns first merge request, which has same sha as base commit

good debugging 👍

What about replacing bsearch with stupid linear search? I can make a PR.

Seems fine to me, can't imagine it's a massive list to go through 👍

Not sure that this is necessary, cause commit sha is unique, so we can simply revert this pr

@sleekybadger I'm still confused and probably missing something. Doesn't using bsearch on an array assumes that it's sorted by the key we use in bsearch's block?

@nikolaykasyanov yeah, you're right. We can use Array.index which is leaner.
merge_request = merge_requests.auto_paginate.index do |mr|
  mr.sha == base_commit
end

merge_request.nil? ? 0 : merge_request.iid

@sleekybadger @orta thanks for discussion & making it quick!


:book: Add logo variants

Summary
We need logo variants to submit them to the CNCF. I figured it makes sense to put them in the main repository as well since the original logo is here too.
Related issue(s)
Fixes #
Release Notes

NONE

/cc @mjudeikis @sttts

/retest

Well done!
/lgtm
/approve


Tuck some fields into structs

A recent addition of a lot of rename functionality made the code a bit
unreadable.
This commit tucks all rename-related fields into a struct called
ClusterCustomizations so passing them around is more neat.
Did the same for timings related code, and put it in a module, so it's
more out of sight from the main code flow.

/test baremetalds-sno-recert-cluster-rename
/test e2e-aws-ovn-single-node-recert-serial
/test e2e-aws-ovn-single-node-recert-parallel

/cherry-pick release-4.15


GOSA29 - Re-arrange app drawer

Re-arrange in order of Home, About Us, Team, Events, Registration, Contact.

assign me

assign plz

@rithik-dev work on this bug

@rithik-dev  thank you for the contribution. You have received 5 points for the contribution. We have successfully merged your pull request.


Issue 5, a sorting error when forward and backward routes overlap, returned

Issue #5 was about a route where the forward and backward routes were going in an 8-shape, where they overlapped in the middle. This issue was solved, but it has returned.

314-353 gives a sorting error
17-19 gives a sorting and an unjust segments error

@A67-A67 thanks for reporting this problem. I will have a closer look.

Nog 2 routes met dit probleem:
01-45 in Nijmegen: https://knooppuntnet.nl/nl/route/10015252
93-95 in Zuid Limburg: https://knooppuntnet.nl/nl/route/145281

The problem has been resolved on experimental.knooppuntnet.nl (today not deployed on knooppunnet.nl yet):

314-353
17-19
01-45
93-95

Case study Issue71_OverlappingWays reproduces the problem and solution.


last clicked button is clicked again when you hit space

I accidentally started deleting instruments instead of playing the track in Live just now, after having deleted one instrument on purpose. Sointu still had keyboard focus, and I was hitting space (play), and it just deleted the first instrument, and then the second, ... took me a while to even understand what had happened.

Yeah, known issue: buttons capture focus, even though user probably doesn't want it. It's a feature of gioui buttons that atm cannot be disabled. I can roll my own button widgets but it takes a bit extra lines to implement my own widgets.
Discussed also at #151

@wayfu I made a quick fix that is now up to @vsariola to hate (because really shady, but whatchugonnedo),
so if this takes a while and you are similarly annoyed than me, you might at least test https://github.com/LeStahL/sointu/tree/fix/button-spacebar-hack
(has everything the current master has, minus the spacebar stoolification)

This one is now fully merged


Field of view coordinates and IRF axis names

The spec for field of view coordinates still needs to be written:
http://gamma-astro-data-formats.readthedocs.org/en/latest/info/coordinates.html#field-of-view
Also, I've started to write up recommended names for IRF coordinate axes:
http://gamma-astro-data-formats.readthedocs.org/en/latest/irfs/index.html#irf-axes
This info should probably be moved onto the coordinates page.
The hardest part is to describe / fix the FOV coordinates and names.
I'll make a proposal in the next few days and then we can discuss ...

Today's APOD is gamma-rays in a "relative RA/DEC" system.
http://apod.nasa.gov/apod/ap160429.html

I wonder how exactly they define it. (I didn't look, no time today.)
Made me 😄  and I thought I'd mention it here.
cc @jknodlseder @alziegler

Our proposal (from extensive discussions in HESS) for field of view coordinates would be this:

Spherical coordinates, no projection / WCS.
One version for RADEC aligned and a separate one for ALTAZ aligned.
So FOV_RADEC is just a rotated version of RADEC and FOV_ALTAZ is just a rotated version of ALTAZ
One version LON / LAT where the pointing position is on the equator and one THETA / PHI where it is at the pole.

This means there are 8 FOV coordinate columns defined:
FOV_ALTAZ_LON, FOV_ALTAZ_LAT
FOV_ALTAZ_THETA, FOV_ALTAZ_PHI

FOV_RADEC_LON, FOV_RADEC_LAT
FOV_RADEC_THETA, FOV_RADEC_PHI

We drop the current DETX, DETY because it was never well-defined / was used inconsistently in exporters and science tools. (Is this OK or do you want to do something here to avoid breakage?)
We have started to implement this in the HESS exporters and to test this with Astropy / Gammapy.
See example FITS file and script test_astrometric.py here:
https://github.com/cdeil/astrometric_checks

@jknodlseder @TarekHC and anyone else that might be interested in FOV coordinates -- thoughts?
Would it be OK if I put this into the spec for now? (Because we need something that's well-defined for HESS now and something is better than nothing) There could then still be other proposals in the coming months and extensive discussions on pros / cons of different definitions for FOV coordinates and how to serialise them for FITS events and IRFs.

Fine by me. I think it is ok if you want to add it to current specs. Other experiments are far behind regarding these issues, so if you find it optimal for HESS, then it will very likely also be optimal for IACTs/CTA.
Although just to make sure. Would dropping DETX/DETY deprecate current science tools?  Are they currently using those columns?

Would dropping DETX/DETY deprecate current science tools? Are they currently using those columns?

Yes, Gammapy and ctools use DETX / DETY at the moment for background modeling. But they are using it inconsistently, so it might be a good thing that we introduce completely new, well-defined fields.
I see two concrete options:
A. Don't have DETX / DETY in the spec. Have some short-term pain, science tools need to update.
B. Recommend that data providers fill DETX=FOV_ALTAZ_LON and DETY=FOV_ALTAZ_LAT for a while, explaining that this was the old name and some people filled them differently in the past.
I'm in favour of A, but open to do B or something else if @jknodlseder or others want.

You two are the ones that will very likely need to implement those changes... so I think it is reasonable that you two take that decision.
I would suggest B just because it would be a bit more realistic, given that they are currently in use. Although it is true that A is more formal... And would help to get rid of bad practises.

@cdeil @jknodlseder
I would like to re-initiate this discussion. The current context is that we're trying to build a background model for HESS and need to decide in which coordinates to store it. I'd like to learn what the science tools expect and see whether we can agree on a common format.
I think we have agreed that the model should be provided in a FoV coordinate system that is simply rotated with respect to some astronomical system. The two options are to align the FoV-system coordinates with the Alt/Az-system coordinates or the Ra/Dec-system coordinates.
My first question to you is: in which of these two versions do ctools and Gammapy expect the background model to be provided? The docs aren't very clear about this in both cases, my suspicion is that Gammapy expects Alt/Az-aligned coordinates and ctools Ra/Dec-aligned coordinates, but I'm not sure.
In case my suspicion is true and the tools expect the model to be provided in different formats, my second question would be whether we can agree on one of the options?
We've discussed this topic in our group here in Erlangen and feel that it would be most convenient to provide the background for each run in Ra/Dec-aligned coordinates, since the data will likely be analyzed in this system as well.
(Note that we construct the background model in an Alt/Az-aligned coordinate system in any case, since systematic effects related to the experiment will be captured best in this way. The question we need to discuss is the coordinate system in which to store the model.)
I'm looking forward to hear your thoughts about this!

In Gammapy we currently only support rotationally symmetric background, see here. We had working code that projected Alt/Az aligned background models into sky images, I'm not sure if that was in Gammapy at some point or one of the earlier HESS-internal FITS analysis repos.
My suggestion for the event lists (which is half of the discussion above) is to not store any of those coordinates, it's just a waste of space. Instead implement the FOV coordinates from the event RA/DEC. I think that's still missing in both tools, but in the spec, everything is already well-defined in a good way (e.g. FOV coords are shows as optional here). It would save 20% space for all DL3 FITS data (assuming EVENTS dominate), which something.
For the background models, it's a much more difficult decision.
https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/issues/73 contains some relevant points - non-radial symmetries in AEFF or BKG or other IRFs are pretty much the same - we don't really know much how they look like or how to handle them in a reasonably efficient way. In #73 different options are discussed, and in addition if you have axes attached to a sky frame, you could also consider just using one of the existing maps formats.

Note that we construct the background model in an Alt/Az-aligned coordinate system in any case, since systematic effects related to the experiment will be captured best in this way. The question we need to discuss is the coordinate system in which to store the model.

If you construct it in ALT/AZ, then it's also immensely helpful to have a standard format to store it in ALT/AZ in a well-defined format. We will need that in CTA anyways (cc @kosack).  Otherwise you get a mess where in H.E.S.S. you build and store and check models one way, and then in CTA they do something different and we have to adapt in HESS later. IMO we should try to avoid that and collaborate and find something good now. We can discuss this a bit tomorrow, see  Karl's presentation), and see if we can't define some formats short-term that support a few options and the most likely work that is ongoing on non-radial IRF dependencies in HESS & CTA now. Concretely for the two options discussed here that just differ by a rotation, a frame = {'radec, 'altaz'} header key would suffice to support both ways in the format, and it wouldn't be terribly hard (but yes, some work) to implement support for them in the two science tool prototypes, no?

@lmohrmann - This issue is the last substantial topic to finalise the v0.2 of the spec, that we need for the HESS release. I'd like to propose again to drop DETX and DETY from the HESS events table. IMO it's just a waste of space, and given that we don't have agreement on it's definition (we put ALTAZ aligned, ctools assumes RADEC aligned) it just creates confusion / problems. Both Gammapy and ctools work perfectly fine with EVENTS that don't have a DETX / DETY column.
@TarekHC - Please check what you fill in DETX / DETY for MAGIC and also consider removing it, or document the orientation clearly.
@mackaiver - I see that for FACT you're already not adding these two columns to your DL3 EVENTS files. Well done!
Please review the attached commit, and directly edit via a follow-up commit if something is incorrect or unclear.
For now, I just tried to clearly describe the different FOV coordinates in use, but leave the decision what to use open, stating that this will be made by CTA hopefullly soon (cc @kosack from CTA / ctapipe).
@jknodlseder - Maybe you want to comment on this one as well?

@cdeil Once we have a decision here, I can remove DETX and DETY from the event columns in the HAP exporter.

I'm OK with dropping DETX and DETY from the event column in general. Are you 100% sure it's not being used by ctools at the moment though?

They might be accessed and used when using a bkg3d model. I don't know. Can you or someone in Erlangen try? (I don't have ctools installed and don't want to spend time on it).

They might be accessed and used when using a bkg3d model. I don't know. Can you or someone in Erlangen try?

We'll have a look

Just to comment: on the Gammapy side, the plan is to only access RA / DEC / TIME and to compute FOV coordinates from that, and then to interpret background model DETX / DETY with ALTAZ alignment, i.e. how we fill it at the moment in HESS.
And then once CTA makes a decision (e.g. in 2019), change the supported format and coordinate definitions to that.

@cdeil It appears ctools does use DETX and DETY, albeit only to compute offset angles that are used to query the IRFs event-wise. Maybe someone involved in ctools development could verify this? As I said, I'd be OK with removing these columns if none of the tools uses them. I'd still vote for including both the Ra/Dec and Alt/Az aligned FOV coordinates in the HESS test release, but that's not at issue here, right?

@dtiziani confirmed that ctools runs fine without DETX / DETY present, so I'll remove it from the HESS release files EVENTS tables.
Merging this PR.


[N4S] - Add support for enforce.anyOf()

Will allow an at least one relationship between enforce assertions.
enforce(value).anyOf(enforce.longerThan(5), enforce.isEmpty())
This requires quite a big change to the way enforce currently works.

dupe


APPS-1323 Fix checking directory for s3

fix empty directory check

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

Please upload report for BASE (main@3116628). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #166   +/-   ##
=======================================
  Coverage        ?   76.60%
=======================================
  Files           ?      100
  Lines           ?     7279
  Branches        ?        0
=======================================
  Hits            ?     5576
  Misses          ?     1350
  Partials        ?      353

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


Footer positioning is fixed

What is the change?
Footer is fixed to bottom of the page
Related issue
issue: #162
How was it tested?
I checked it in my local system
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
Add a screenshot or demo video if appropriate.

Footer is positioned at bottom

Good work, do I need to add your points in some program on merging this?

@all-contributors please add @Ankita297 for code


Xcode 8 beta 6: Removed deprecated @noescapes

As of Xcode 8b6's Swift 3.0, closures are now non-escaping by default, so the @noescape keyword is no longer necessary, and deprecated (Xcode now emits on usages warning: @noescape is the default and is deprecated).  More info on this change at https://github.com/apple/swift-evolution/blob/master/proposals/0103-make-noescape-default.md and http://adcdownload.apple.com/Developer_Tools/Xcode_8_beta_6/Release_Notes_for_Xcode_8_beta_6.pdf .

Removed uses of deprecated @noescape keyword.  Double-checked to make sure there were no formerly-escaping closures that would need the new @escaping keyword.

This is cool. Thanks!


Implemented downloading by ION.

Hi,
Changed download process.
Using https://github.com/koush/ion#download-a-file-with-a-progress-bar
ION allows downloading to any folder.
Need testing.

@jonmuell Can you merge and test this pls?


Application push User filtering and sampling statistics

Is your feature request related to a problem? Please describe.
Log management statistics
Describe the solution you'd like
1 pull active user cluster
2APP terminal adds push management
3 Background automatic statistics push timeliness and arrival rate
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

already


Start container feature: Ignore CMD directives

I'm using an image that runs a script upon container start-up via a CMD directive in the Dockerfile. This script runs a web application. I recently broke the config files accidentally and the web application failed to start. The result was a container that I had to throw away. Could you imagine if it contained something that I couldn't replace? I'd be a very unhappy whale. Is there a way to get the container's OS to start and ignore the CMD scripts so I can fix the problem via exec -it bash? I searched for such a feature at the docker command-line but obviously wasn't successful.

You could docker commit the existing container as an image and start a new container from that, overriding the cmd to use from the command line (docker run -it my-committed-container bash

@dev-guy can't you just docker run --entrypoint /bin/sh yourwebappcontainer to start your image and play with it with a shell?

@thaJeztah Yes, thank you for the workaround. I hope the Docker team adds this as a real 'start' option, however. @runcom - Docker run creates a new container, right? My existing container is special (different from image) so I need to get that started.

My existing container is special (different from image) so I need to get that started.

In that case, committing is the sane way to do. I don't think re-starting an existing container with a new command is something we want (containers should be reproducible, so in general there's no need to)
I'm going to close this issue, because the question was answered, but feel free to continue the discussion.

I don't think regular humans could figure that out. Perhaps this issue will become the documentation that Docker users find when they do facepalm stuff to their start scripts.


The applications needs that the user click twice the “Social Media” icons to open/redirect to the page in apple devices.

Description:
The applications needs that the user click twice the “Social Media” icons to open/redirect to the page in apple devices.
-Env:
Crafter Hotel Blueprint
Iphone 7 IOS 10.3
Safari
Google Chrome Version 55.0.2883.79
Firefox 7.5(3349)
REPRODUCIBILITY LEVEL:
Always
STEPS:
Steps

Open the Crafter studio with the Hotel_Info site.
Go to the footer.
3.Click on the social media icons.

CURRENT RESULT:
The user needs to click twice the “Social Media” icons to open/redirect to the page in apple devices.
https://www.screencast.com/t/NFDTbudQ3K
EXPECTED RESULT:
The user should only user need to click one time the “Social Media” icons to open/redirect to the page in apple devices.

Fixed

Bug verified and closed as fixed in build a18e1b1.