why i can't play 4k in edge

why i can't play 4k in edge

https://help.netflix.com/zh-tw/node/13444

hihaozhe  were you able to play 4k in new edge at least a week ago ?
For me it was working fine until about october 29 when suddenly video quality became 1080p  at max (no hevc,  prk,  hdr  in video codec only avc/avchigh)   Netflix  win 10 app works ok and i cant watch 4k + hdr using it.
There is even a thread in reddit about it
https://www.reddit.com/r/MicrosoftEdge/comments/jkh7y6/netflix_4k_is_not_working_on_new_edge_but_it/
So its a common problem i guess.   The best way to watch 4k on pc right now  (and hdr if you have capable monitor)  is to use Netflix app

hihaozhe  were you able to play 4k in new edge at least a week ago ?
For me it was working fine until about october 29 when suddenly video quality became 1080p  at max (no hevc,  prk,  hdr  in video codec only avc/avchigh)   Netflix  win 10 app works fine and i can watch 4k + hdr using it.
There is even a thread in reddit about it
https://www.reddit.com/r/MicrosoftEdge/comments/jkh7y6/netflix_4k_is_not_working_on_new_edge_but_it/
So its a common problem i guess.   The best way to watch 4k on pc right now  (and hdr if you have capable monitor)  is to use Netflix app

now i fixed this problem
https://github.com/lkmvip/netflix-4K-DDplus/commit/7c3ec792f9b15bebccff570c0efd5dda0bf9fa97

lkmvip,   Thanks.  4K + HDR works  now in Microsoft Edge  after i edit cadmium-playercore-6.0026.529.031.js  file like in your post .

Forgive my ignorance, where do I do this?

5J2J ,  you can simply drop this edited file https://www.mediafire.com/file/l2l1k3cpxdvzh3y/cadmium-playercore-6.0026.371.031.js/file   in  your netflix-4K-DDplus extension root folder rewriting your cadmium-playercore-6.0026.529.031.js file

after install Microsoft Store link，i can play videos ，but I still can't play 4K

after install Microsoft Store link，i can play videos ，but I still can't play 4K

Recommended software:
1,Win10.Ver.2004

Forgive my ignorance, where do I do this?

https://github.com/lkmvip/netflix-4K-DDplus/archive/master.zip

Edge

Netlfix Windows

Windows versión:

you edge version?

you edge version?

Now, the store version of the extension does not support streaming 4K. This is actually caused by Microsoft or Netflix. You can use this https://github.com/lkmvip/netflix-4K-DDplus/issues/11#issuecomment-722080911, If you must use the store version, you may need to wait a long time, maybe 10 days, 20 days, because Microsoft review is very slow

Do I have to activate any of these options?

no

used the https://github.com/lkmvip/netflix-4K-DDplus/archive/master.zip
version, still no 4k only 1920x1080p

It doesn't work for me in 4k either.

It seems that 4K is fixed as it works without  checking disguised as edge  option  but HDR is broken.  Worked fine just a few days ago in EDGE but now  works only in UWP .
I wonder  are the any way to fix  by edit cadmium playercore settings  or just wait till  it will be eventually fixed....

used the https://github.com/lkmvip/netflix-4K-DDplus/archive/master.zip
version, still no 4k only 1920x1080p
clicked on all 6 options should I not use one or more?

@spreadpositivity3, you need to enable "Use hardware acceleration when available" for your browser (Microsoft Edge). I had the same issue, but it was fixed after I enabled it.

used the https://github.com/lkmvip/netflix-4K-DDplus/archive/master.zip
version, still no 4k only 1920x1080p
clicked on all 6 options should I not use one or more?

@spreadpositivity3, you need to enable "Use hardware acceleration when available" for your browser (Microsoft Edge). I had the same issue, but it was fixed after I enabled it.

5J2J , you can simply drop this edited file https://www.mediafire.com/file/l2l1k3cpxdvzh3y/cadmium-playercore-6.0026.371.031.js/file in your netflix-4K-DDplus extension root folder rewriting your cadmium-playercore-6.0026.529.031.js file

Nope, Edge detects that something changed, disables the extension and offers to "repair it" which effectively means it will be uninstalled.

Forgive my ignorance, where do I do this?

https://github.com/lkmvip/netflix-4K-DDplus/archive/master.zip

How to manually install the extension?

5J2J , you can simply drop this edited file https://www.mediafire.com/file/l2l1k3cpxdvzh3y/cadmium-playercore-6.0026.371.031.js/file in your netflix-4K-DDplus extension root folder rewriting your cadmium-playercore-6.0026.529.031.js file

Nope, Edge detects that something changed, disables the extension and offers to "repair it" which effectively means it will be uninstalled.

Forgive my ignorance, where do I do this?

https://github.com/lkmvip/netflix-4K-DDplus/archive/master.zip

How to manually install the extension?

Nevermind, in new Edge versions there is "Developer mode" switch in left-bottom part of edge://extensions/
Still, I haven't got all this to work.

Nevermind, in new Edge versions there is "Developer mode" switch in left-bottom part of edge://extensions/
Still, I haven't got all this to work.


basic/digest auth per frontend..is that possible?

What version of Traefik are you using (traefik version)?
2a61c9049f119b6e57c7d086f2c07f2086d7b2c1 / cheddar
What is your environment & configuration (arguments, toml...)?
What did you do?
I am using Traefik with docker labels to setup dynamic paths ala:
-l traefik.frontend.rule="PathPrefixStrip: /test"
I have http redirecting to https and basic auth setup for the https entry point.
It is working well.
What did you expect to see?
I would like to setup basic/digest auth on a per frontend basis.
so
https://server/path1 uses  htpasswd1
https://server/path2 doesnt use any authentication
https://server/path3 uses htpasswd3
If it can be defined per frontend then I would have full control.
Thank you!
I love Traefik..I am finding more uses for it every day.
What did you see instead?

This looks very similar to #751. Could you please explain what the difference is supposed to be?

I did not see that issue. I will close this one. I see there is a pull request to resolve this. Hopefully it will allow   htpasswd use.
Thanks!


Is there an implementation for retrieving media and attachments count in channels/supergroups?

I couldn't find any documentation for retrieving the count or number of media files and attachments in a channel.
There is member_count for getSupergroup, but there exists no member for media count, links count, or files count.
However, previewing a channel on https://t.me/s/channel, the site seems to able to display the above missing counts:

Perhaps this is unspecced?

You need to use the method getChatMessageCount for this.

that was it - thank you very much!
example usage for getting links count:
{
    "@type": "getChatMessageCount",
    chat_id: -1001123464890,
    filter: {
        "@type": "searchMessagesFilterUrl"
    }
}


feat: add query parser to treesitter config

Based on the nvim-treesitter README.md which states query as one of the five parsers that should always be installed.

I think it means that nvim treesitter will always keep parsers from that list installed. I have opened a discussion in nvim-treesitter repo for someone to clarify the meaning.

I just added the ones from nvim-treesitter, thanks for the PR though, would not have noticed otherwise


Preparing for release to new HOST

I'm not sure when the right time for this to release is @Blackbaud-TerryHelems and @Blackbaud-JonathanBell.

Codecov Report

Merging #73 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #73   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          23     23
  Lines         505    505
  Branches       56     56
=====================================
  Hits          505    505

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 8833678...150904a. Read the comment docs.

When we make this switch, we need to update the URL in the description for the url property that we just added to https://github.com/blackbaud/skyux-cli/blob/master/README.md and that I have queued up for the Learn docs.

Are all builds currently building to that URL @Blackbaud-TerryHelems?  Good point @blackbaud-johnly.


FLUME-2799 Kafka Source - Add message offset to headers

It seems we solving https://issues.apache.org/jira/browse/FLUME-2799 , an oversight resulted in the message offset not being added to the header. This change corrects this.

Thanks for the contribution @jbruggem

thanks for the reply szaboferee. I'm not sure what to do though, because the warnings you reference hereabove is due to the use of a fully qualified name for a constant, which is done throughout the file and in particular in the lines just preceding mine.
What should I do ? Change just my lines and break style with the rest of the file ? Just change the lines around it ? The whole file ?

Done !

great ! Do I still have something to do here or will this run its course naturally and by merged ?


FIX: Set DOTNET_ROOT with str and not Path

As pointed out in https://github.com/ansys/pyedb/pull/924/files#r1870405256, the value that we are passing to os.environ is a Path instance while it should be str. This solves this issue.
@isaacwaldron I'll check that this works correctly when I get back from my trip and make a new release.

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

Project coverage is 82.66%. Comparing base (59d21f1) to head (6b792b1).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #933   +/-   ##
=======================================
  Coverage   82.66%   82.66%
=======================================
  Files         160      160
  Lines       21037    21037
=======================================
  Hits        17390    17390
  Misses       3647     3647

@SMoraisAnsys looks good to me.  Interesting that line 86 is covered, since you haven't modified any test to do this I'm surprised this could have been passing earlier as apparently there is a workflow that activates this code path.

@SMoraisAnsys looks good to me. Interesting that line 86 is covered, since you haven't modified any test to do this I'm surprised this could have been passing earlier as apparently there is a workflow that activates this code path.

It isn't covered by testing. I'll extend this PR with some tests on clr_module

Thanks for the review @isaacwaldron let me know if something else is not correct

@SMoraisAnsys I had started a test run using a dependency to the initial commit (which has the actual change I need) on my downstream project that was failing.  So far so good... will come back and finally approve when that passes.


Click interaction animation

Description of the new feature / enhancement
In the options on mouse highlighter, I'd like to use custom animation on left click or right click. Nowadays, it is only possible to change color in click interactions.
Scenario when this would be used?
When in presentation, the possibility to show the click interactions, it would be interesting.
Supporting information
No response

Can you be more specific what you mean by "custom animation" /needinfo

I would like to suggest a feature for the mouse that creates an animation at the moment of clicking. It would be great if this feature could differentiate between right and left clicks, with each click animation being distinguishable either by different colors or by distinct animations. This would not only make the user experience more interactive but also visually appealing.
To make it easier I show you below a gif with interaction on the click. I'd be interesting animation and color choice as option.
Both are without transparency and no coloring options:
[Click] Left click, but still without transparency (example)
[Right arrow] Right click, but still without transparency (example)
I hope to be able to contribute to the PowerToys tool and I would like to know if I was able to be clear in my explanations.
Thank you.

De: Joseph Finney @.>
Enviado: quarta-feira, 4 de outubro de 2023 11:37
Para: microsoft/PowerToys @.>
Cc: Vitor de Melo Gonçalves @.>; Author @.>
Assunto: Re: [microsoft/PowerToys] Click interaction animation (Issue #29011)
Can you be more specific what you mean by "custom animation" /needinfo
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/29011#issuecomment-1747118464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABTIY5XH4IYFCORVLFAYTG3X5V7CZAVCNFSM6AAAAAA5SX3SHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBXGEYTQNBWGQ.
You are receiving this because you authored the thread.Message ID: @.***>

@vitormagyver The GIFs do not come through when replying via email. I am interested to see your concepts, please attach to a comment on GitHub.

Oh, sorry, now I can show here.

available link: https://cdn-icons-gif.flaticon.com/6416/6416353.gif
this could be use for left-click

available link: https://cdn-icons-gif.flaticon.com/7740/7740503.gif
And this could be use for right-click
I believe, compatible  webm, gif, png files to custom option on the mouse highlighter in powertoys and change the form square instead circle too.
It can be something simple:
mouse click example: https://gifs.eco.br/wp-content/uploads/2022/08/gifs-de-click-2.gif
In this the click show red color spread
It's possible a water spread effect on click. it would be very nice.

I think it would be great feature, fully customisable mouse clicks, maybe supporting both custom gif/apng and custom animation controls. Some default animations could also be preloaded with powertoys.


Additional permission issues

Chris reported that he hit another "permission denied" error when trying to view APrime output.

This is still not working in my test this week with processflow-1.0.0-rc5. Trying to view aprime web pages returns a '403 Forbidden' error.


Modify rna-seq pipeline to zip together a sample's results to output_dir or S3_bucket

[ ] Zip output from every terminal step and add to fileStore
[ ] Add final job that pulls output zips from FileStore and writes new zip.
[ ] Test on sample


Hashify

Hashify operation is used to calculate hashes from top-level keys in JSON:
{
  "a": 1,
  "b": {"z":[1,2,3]}}
}

=>

[
  <hash1>,
  <hash2>
]

Codecov Report

Merging #3 into master will decrease coverage by 6.72%.
The diff coverage is 59.25%.

@@             Coverage Diff              @@
##             master       #3      +/-   ##
============================================
- Coverage     68.08%   61.36%   -6.73%
+ Complexity       27       18       -9
============================================
  Files             4        4
  Lines            94       88       -6
  Branches         16       11       -5
============================================
- Hits             64       54      -10
- Misses           18       24       +6
+ Partials         12       10       -2

Impacted Files
Coverage Δ
Complexity Δ

...co/soramitsu/sora/json/NotJsonObjectException.java
0% <0%> (ø)
0 <0> (?)

...main/java/jp/co/soramitsu/sora/json/Hashifier.java
64% <64%> (ø)
3 <3> (?)

...jp/co/soramitsu/sora/crypto/MerkleTreeFactory.java

...n/java/jp/co/soramitsu/sora/crypto/MerkleTree.java

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 13c85c3...4322951. Read the comment docs.


Ignore the specific NAN encoded by f32/f64::NAN

Closes #16
cc @joseluis. The problem here was that Rust's f32::NAN and f64::NAN don't guarantee any particular payload. It's not necessarily all zeroes. If we don't fit that payload in our decimal number then instead of truncating it we return None.
This fixes that up by ignoring the specific bitpattern that f32::NAN and f64::NAN happen to be using. Alternatively we could always ignore payloads from f32 or f64. I'd be open to either approach.

I'm actually thinking now that maybe just ignoring all NAN payloads when converting from f32 and f64 is the least surprising way to go here. We'll still accept them from strings and encode them if they're set though. What do you think?

I'm actually thinking now that maybe just ignoring all NAN payloads when converting from f32 and f64 is the least surprising way to go here. We'll still accept them from strings and encode them if they're set though. What do you think?

I like this approach the most.

I found some inconsistencies in signaling too for binary floating points, so I think I'll also remove any attempt to retain the signaling bit when converting between f32/f64 and decimals. At least for decimals signaling has a well defined encoding.


plot.spatial_pcolormesh_plot should be able to handle a CubeList

I'm not sure this makes sense for a spatial map, so closing.


Spark: Fix glue symlinks formatting bug

Use the correct spark and hadoop configuration params for populating symlinks when using Glue catalog in EMR Spark or Athena Spark jobs. This fixes the symlinks with correct Glue ARNs for namespace and name formats.
Fixes: #2766
Fixes: #2765
Problem
When using AWS Glue catalogId in the spark configuration - EMR and Athena, it is not picked up and the symlinks point to hive urls instead of glue ARNs.
Solution
Use the correct spark and hadoop configuration params for populating symlinks when using Glue catalog in EMR Spark or Athena Spark jobs. This fixes the symlinks with correct Glue ARNs for namespace and name formats.
Code changes:

Reorder the Symlink fetching order to start from glueArn instead of hive metastore URI since hive metastore URIs are present for glue catalog configurations as well.
Read params for glue catalog id specified in various formats - EMR spark, Athena spark, etc and use them for glue ARNs

Before:
     ....
        "symlinks": {
          "_producer": "https://github.com/OpenLineage/OpenLineage/tree/...integration/spark",
          "_schemaURL": "https://openlineage.io/spec/facets/1-0-1/SymlinksDatasetFacet.json#/$defs/SymlinksDatasetFacet",
          "identifiers": [
            {
              "namespace": "hive://ip-10-1-114-149.ec2.internal:9083",
              "name": "datalake_akash.products",
              "type": "TABLE"
            }
          ]
        }
    ....

After:
     ....
        "symlinks": {
          "_producer": "https://github.com/OpenLineage/OpenLineage/tree/.../integration/spark",
          "_schemaURL": "https://openlineage.io/spec/facets/1-0-1/SymlinksDatasetFacet.json#/$defs/SymlinksDatasetFacet",
          "identifiers": [
            {
              "namespace": "arn:aws:glue:us-east-1:123456789012",
              "name": "datalake_akash.products",
              "type": "TABLE"
            }
          ]
        }
    ....

Tested with actual EMR spark jobs with Glue catalog
One-line summary:
Bug fix: Fixes glue symlinks with config parsing for glue catalog Id
Checklist

[x] You've signed-off your work
[x] Your pull request title follows our guidelines
[x] Your changes are accompanied by tests (if relevant)
[x] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[x] Your comment includes a one-liner for the changelog about the specific purpose of the change (not required for changes to tests, docs, or CI config)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2024 contributors to the OpenLineage project

I'm not a repo maintained, I cannot merge this PR

@pawel-big-lebowski @mobuchowski Can you please review this PR?


[88] Merge Sorted Array

Codecov Report

Merging #42 (92cfeff) into master (eaa7379) will increase coverage by 0.6%.
The diff coverage is 100.0%.

Impacted Files
Coverage Δ

src/problem/p0088_merge_sorted_array.rs
100.0% <100.0%> (ø)


there is no /config.yaml in /config!

there is no /config.yaml in /config!

config.yaml was intended as a generic placeholder for any config file. I clarified this in the README.

maybe an example？you know it's hard for beginers. thx


Error: No module factory available for dependency type: Dependency

I have created a small sandbox here that shows the error with minimal code
https://github.com/scottburch/rewire-error
To reproduce:
npm install
webpack
I have found that webpack 1.12.2 works, 1.12.3 does not.

@jhnns This require a change to rewire-webpack. A Dependency must correctly have a constructor property on it's prototype. The Class property is not needed anymore.

Thanks.  Maybe this change should have been a minor version bump rather than a revision bump.

yeah, maybe, but now it's too late... ;)

@sokra I just read that you wrote most of the code for webpack-rewire.  Thank you.

Has been fixed with rewire-webpack 1.0.1


Drmm_tks

Is it possible to provide further details on DRMM_TKS (I mean, paper).

Right now, it is our idea to expand DRMM on short text pairs. So, you can refer the paper DRMM to understand the code. It's not much hard.

It is based on DRMM, by replacing the matching histogram by top-k strongest signals for short texts.

@faneshion @JiafengGuo Thanks!


Managed Debugging Assistant 'PInvokeStackImbalance'

Trying to run this sample:
using System;
using OpenRealSense;
using System.IO;

class Program
{
    static void Main(string[] args)
    {
        var context = Context.Create(11100);
        var device = context.GetDevice(0);

        device.EnableStream(StreamType.Depth, 640, 480, FormatType.Z16, 30);
        device.Start();

        while (true)
        {
            device.WaitForFrames();
            var frameInBytes = device.GetFrameData(StreamType.Depth).Bytes;
            using (var stream = new MemoryStream(frameInBytes))
            {
                using (var reader = new BinaryReader(stream))
                {
                    //do something with the frame :)
                }
            }
        }
    }
}

I get an exception on Context.create(11100):

Managed Debugging Assistant 'PInvokeStackImbalance' : 'A call to PInvoke function 'OpenRealSense!OpenRealSense.NativeMethods.Context::rs_create_context' has unbalanced the stack. This is likely because the managed PInvoke signature does not match the unmanaged target signature. Check that the calling convention and parameters of the PInvoke signature match the target unmanaged signature.'

Using version 1.12.0 from NuGet and .NET 4.6.2 console app.
Any idea what's going on and how to fix it?
Thanks!

I seem to have fixed it by changing all the DLL imports from:
[DllImport(DllSource.Path)]

to:
[DllImport(DllSource.Path, CallingConvention = CallingConvention.Cdecl)]

I'll confirm that this is indeed fixes everything then I'll make a pull request!

Hi @FuzzyWuzzie , Thanks a lot. Let me know if you need any help :)

Tks, @FuzzyWuzzie , the nuget package with your changes are already online :)
https://www.nuget.org/packages/OpenRealSense/

Awesome, thanks!


Add work_type validator

Ensure they are members of a set:
Data
Image
Multimedia
Other
Software or Code
Sound
Text
Video

Duplicate of #167


Set fee recipient as global env

Set fee recipient as global env

Depends on https://github.com/dappnode/DNP_DAPPMANAGER/pull/1404


Crash reporting

For my own app I was thinking to integrate the new firebase crash reporting tool:
https://firebase.google.com/docs/crash/
It looks very promising, in the past at my old company we used Fabric.io.


SUCCESS & a question ref. possible 4rth Test Scenario

I am beyond thrilled to report success with using live Galileo data (via locally connected USB dongle) as the source for evaluation by your app running on the local PC!

... and that prompted me to wonder if a 4rth testing scenario was possible.   Your documentation and very welcome help on other ISSUES posted here allowed me to finally get the longan-nano to properly process INAV and OSNMA data via the serial port client.
I wondered if it might be possible to utilize live data from the USB device in place of the web stream to feed the longan-nano data.
I believe that I might have been successful (see images below) but I do not fully understand the result.   In the second image below, the output deviates and I'm not sure if that is just a line-wrap error or if an OSNMA authentication has been achieved.  Naturally the full PC app is more verbose.   Would you be kind enough when time permits to explain in just a bit more detail what the longan-nano is telling us as it receives the live data stream?   Many thanks in advance!

It's working.
The output you've marked in red means that it's managed to authenticate the ephemeris data for E08 and E13 at that point. Interestingly, it hasn't managed to authenticate the constellation timing parameters yet (that's what ADKD=4 stands for). Perhaps it will manage later on (you would see AUTH ADKD=4 TOW xxxx).
The reason why the AUTH ADKD=0 E08 TOW 7860 E13 TOW 7860 line disappears quickly, returning to AUTH ADKD=0 NONE is because the SRAM of the Longan nano is not particularly large, so it has barely enough storage space to process the authentication data. Once the next subframe starts (at TOW 7951), the old navigation data (which just has been authenticated) needs to be discarded to make room for the data in the new subframe.
That's why the authenticated data disappears so quickly. What the output is doing is, at each moment, printing what is the latest authenticated data it has (or NONE if there is NONE). Since the authenticated data is so short lived, we see NONE most of the time. It might be possible to play with the definition of the storage size to try to make the authenticated data live longer, but one needs to be careful, because if the program runs out of SRAM, it crashes.
If everything is going well, if you search through the output you would see successful authentication for ADKD=4 as well as for other satellites besides E08 and E13.

After upgrading to commit 599804e, I rebuilt all the applications including the firmware for the Longan-nano.
Using 'live' GNSS data via the serial client, I allowed the collection to run for a while.  Unlike my initial report which only contained a single authenticated ephemeris data packet, you can see below that I happened to catch a string of multiple packets that were authenticated - both ephemeris data AND constellation timing parameters.  So, I was very pleased with that result and wanted to share it for reference on this thread.

Nice! Now I see a bug that I've introduced in that commit. The AUTH ADKD=0 line says EE15 rather than E15. I will fix this.

I'm trying to clean up the issues by closing what is already solved and moving to a discussion what has background information that could be interesting to others. I think this is best transferred to a discussion, since it has some information about how to read the output from osnma-longan-nano that others may find useful.


Increase scrollbar height for horizontal scroll of grid query results

Issue Type: Feature Request
The horizontal scrollbar is very thin on the grid query results, making it difficult to scroll without accidentally selecting a cell. The vertical scrollbar has a wide scroll thumb and is easy to select via the mouse.
Azure Data Studio version: azuredatastudio 1.39.1 (7553f799e175f471b7590302dd65c997b838b29b, 2022-08-30T01:11:13.047Z)
OS version: Windows_NT x64 10.0.22621
Restricted Mode: No

@Zeddox just to confirm you are talking about the bottom h-scroll bar in the image below, right?

@alanrenmsft Yep that is the one I'm referring to


Multiple observations for HMM

Imagine that I have observed several different length sequences from a HMM.
At the moment I'm doing the below, which seems quite somewhat annoying in the case in which thousands of sequences are observed. Am I missing something?
Z = CategoricalMarkovChain(a0, A, states=N)
Y = Mixture(Z, Gaussian, mu_est, Lambda_est)
Y.observe(y)

Z1 = CategoricalMarkovChain(a0, A, states=N1)
Y1 = Mixture(Z1, Gaussian, mu_est, Lambda_est)
Y1.observe(y1)

Q = VB(Y, Y1, Z, Z1, mu_est, Lambda_est, A, a0)

Yep, if they had the same length, then you could use plates. But as they have different lengths, you need to have a node for each sequence. You can of course use for loops or list comprehensions to generate a bunch of nodes.
Z = []
Y = []
for i in range(sequences):
    Z.append(CategoricalMarkovChain(a0, A, states=N[i]))
    Y.append(Mixture(Z[i], Gaussian, mu_est, Lambda_est))
    Y[i].observe(y[i])

nodes = Y + Z + [mu_est, Lambda_est, A, a0]
Q = VB(*nodes)

Something like that. Just wrote it quickly without trying, so there can be some errors. Anyway, I hope you get the idea. Is this what you were looking for?

Got it. Yep. Thanks!


build: get rid of recompilation bigger part of project after cmake run

Purpose
After minor changes in cmake files bigger part of the project was rebuild without a need in that. So many time was wasting on that rebuilds.
For reviewers
Because removed variables was needed only it Test part of Network I just removed it. But it could be also added to needed target with target_compile_definitions if it is needed

prnet cleaned-up successfully


Fop and h20 benchmarks fail mysteriously

Hi,
I'm trying the 309e1fa evaluation snapshot and have noticed that the fop benchmark exits 255 (i.e. failure), but without any further details.
$ ./graalvm-ce-java11-19.3.2/bin/java -jar dacapo-evaluation-git+309e1fa-java8.jar  -n 5 fop
--------------------------------------------------------------------------------
IMPORTANT NOTICE:  This is NOT a release build of the DaCapo suite.
Since it is not an official release of the DaCapo suite, care must be taken when
using the suite, and any use of the build must be sure to note that it is not an
offical release, and should note the relevant git hash.

Feedback is greatly appreciated.   The preferred mode of feedback is via github.
Please use our github page to create an issue or a pull request.
    https://github.com/dacapobench/dacapobench.
--------------------------------------------------------------------------------

===== DaCapo evaluation-git+309e1fa fop starting warmup 1 =====
$ echo $?
255

I've managed to reproduce this on both GraalCE and OpenJ9 on Debian 10.

I also tried this with OpenJDK14 and got the same outcome.

Thank you Edd.
I am looking into this and a number of other issues right now.

Seems like it's the same for h2o.

I have not been able to reproduce on 309e1fa.
/usr/lib/jvm/java-11-openjdk-amd64/bin/java -jar dacapo-evaluation-git+309e1faf.jar -n 5 fop
--------------------------------------------------------------------------------
IMPORTANT NOTICE:  This is NOT a release build of the DaCapo suite.
Since it is not an official release of the DaCapo suite, care must be taken when
using the suite, and any use of the build must be sure to note that it is not an
offical release, and should note the relevant git hash.

Feedback is greatly appreciated.   The preferred mode of feedback is via github.
Please use our github page to create an issue or a pull request.
    https://github.com/dacapobench/dacapobench.
--------------------------------------------------------------------------------

===== DaCapo evaluation-git+309e1faf fop starting warmup 1 =====
===== DaCapo evaluation-git+309e1faf fop completed warmup 1 in 4928 msec =====
===== DaCapo evaluation-git+309e1faf fop starting warmup 2 =====
===== DaCapo evaluation-git+309e1faf fop completed warmup 2 in 1314 msec =====
===== DaCapo evaluation-git+309e1faf fop starting warmup 3 =====
===== DaCapo evaluation-git+309e1faf fop completed warmup 3 in 1100 msec =====
===== DaCapo evaluation-git+309e1faf fop starting warmup 4 =====
===== DaCapo evaluation-git+309e1faf fop completed warmup 4 in 1011 msec =====
===== DaCapo evaluation-git+309e1faf fop starting =====
===== DaCapo evaluation-git+309e1faf fop PASSED in 899 msec =====

Closing.  Will reopen if you're able to reproduce with RC3 or more recent.


Fix batchnorm precision

https://github.com/ROCmSoftwarePlatform/MIOpen/blob/46fbbbf33f96953e98e50d43407dbe29b35de0df/src/ocl/batchnormocl.cpp#L958-L985
In above part，if in_cstride <= 512 && in_cstride >256 && n < 64, batchnorm will use variant = 0 and xlocalsize = 256. The corresponding code is as follows:
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/46fbbbf33f96953e98e50d43407dbe29b35de0df/src/kernels/MIOpenBatchNormBwdSpatial.cl#L90
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/46fbbbf33f96953e98e50d43407dbe29b35de0df/src/kernels/MIOpenBatchNormBwdSpatial.cl#L117
The max lid is 255, and the memory of x_in[256] to x_in[in_cstride] will nerver be accessed.

@zpwenjh We appreciate your efforts but it looks like you do not have enough time to work on this PR.
@ce1adon @muralinr Can we take all good changes from this PR are create a new one, removing the unwanted changes and fixing the root cause of the issue there?
/cc @junliume

@zpwenjh We appreciate your efforts but it looks like you do not have enough time to work on this PR.
@ce1adon @muralinr Can we take all good changes from this PR are create a new one, removing the unwanted changes and fixing the root cause of the issue there?
/cc @junliume

yes Artem. That would be my plan.

@atamazov I'm investigating this PR as well as issue #915 , and also the comment left by @zpwenjh in https://github.com/zpwenjh/MIOpen/pull/14#discussion_r629792216 . I have concern if these three things have connections or they are actually three different issues. I have made some commits to solve the fp16 issues reported in issue #915 . I observe successful verification in 80x80 and 160x160 cases while 20x20 cases only failed in dscale checking. I doubt the cause is datatype max limits. Still investigating on this one.

@zpwenjh
Is the purpose of this PR to fix test cases in issue #915 ? Or you are trying to fix other config failures?

@zpwenjh
Is the purpose of this PR to fix test cases in issue #915 ? Or you are trying to fix other config failures?

@ce1adon The following configs are also verification failed, and this PR fixed them all.
./MIOpenDriver bnormfp16 -n 16 -c 1280 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 1280 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40  -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -P 0 -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1 -P 0 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 320 -W 320 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 320 -W 320 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 1280 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 1280 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 320 -W 320 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 320 -W 320 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 1280 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1

@zpwenjh
Is the purpose of this PR to fix test cases in issue #915 ? Or you are trying to fix other config failures?

@ce1adon The following configs are also verification failed, and this PR fixed them all.
./MIOpenDriver bnormfp16 -n 16 -c 1280 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 1280 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40  -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -P 0 -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -F 4 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1 -P 0 -F 2 -t 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 320 -W 320 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 80 -H 320 -W 320 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 1280 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 1280 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 160 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 320 -H 80 -W 80 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 640 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 320 -W 320 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 4 -c 80 -H 320 -W 320 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 1280 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 20 -W 20 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 640 -H 40 -W 40 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 320 -H 40 -W 40 -m 1 --forw 1 -b 0 -s 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 160 -W 160 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1
./MIOpenDriver bnormfp16 -n 16 -c 160 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1

@zpwenjh
Is the purpose of this PR to fix test cases in issue #915 ? Or you are trying to fix other config failures?

@ce1adon The following configs are also verification failed, and this PR fixed them all.

Thank you for the feedback! Notice that all these configures are fp16. In my investigation, I notice that the fp32 types are running OK.
Meanwhile I notice the output and bias are correct while the failure occurs in scale.
Will keep updating in this PR.

@ce1adon Not all FP32 is ok，I only used FP16 for testing my program. There is a FP32 config that failed to verify too.
MIOpenDriver bnorm -n 38 -c 128 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1 -V 1

@ce1adon Not all FP32 is ok，I only used FP16 for testing my program. There is a FP32 config that failed to verify too.
MIOpenDriver bnorm -n 38 -c 128 -H 80 -W 80 -m 1 --forw 0 -b 1 -r 1 -V 1

This one should be fixed by PR https://github.com/zpwenjh/MIOpen/pull/14

@ce1adon The following configs are also verification failed, and this PR fixed them all.
The "-F 4" flag in your cmd should be removed when testing.

In above part，if in_cstride <= 512 && in_cstride >256 && n < 64, batchnorm will use variant = 0 and xlocalsize = 256.

@zpwenjh I evaluated your comments. This is true for non-fp32 cases, while fp32 cases will not be affected since the rule to set group size for fp32 and non-fp32 are different.
@atamazov  @muralinr  We need a solution involving either group size or layout change, which will affect performance anyway. Please keep us updated about the performance test.

In above part，if in_cstride <= 512 && in_cstride >256 && n < 64, batchnorm will use variant = 0 and xlocalsize = 256.

@zpwenjh I evaluated your comments. This is true for non-fp32 cases through variant 0 path, while fp32 cases and other non-fp32 paths will not be affected since the rule to set group size for them are different. However, the cases of fp16 through variant 0 do fail due to current layout rules. Thanks for catching it!
The problem of fp32 and the other non-fp32 path is due to fail to accumulate float4 residual data properly. A fix is done in zpwenjh#14 . Please check.
@atamazov @muralinr We need a solution involving either group size or layout change, which will affect performance anyway. Please keep us updated about the performance test.

Do we have final code ready for both PRs to evaluate performance?

@ce1don In other words, please update @muralinr with repository name, branch name and git hash that you would like to test BN performance of.
@muralinr AFAICS the current baseline for performance testing of this PR is develop 46fbbbf33 (see https://github.com/zpwenjh/MIOpen/commits/fix_batchnorm_precision)

@ce1don In other words, please update @muralinr with repository name, branch name and git hash that you would like to test BN performance of.
@muralinr AFAICS the current baseline for performance testing of this PR is develop 46fbbbf (see https://github.com/zpwenjh/MIOpen/commits/fix_batchnorm_precision)

@ce1don Can you please let me know once PR is ready for performance testing..

@ce1don In other words, please update @muralinr with repository name, branch name and git hash that you would like to test BN performance of.
@muralinr AFAICS the current baseline for performance testing of this PR is develop 46fbbbf (see https://github.com/zpwenjh/MIOpen/commits/fix_batchnorm_precision)

@ce1don Can you please let me know once PR is ready for performance testing..

Sure. Will let you know @muralinr

@atamazov @muralinr @zpwenjh   After re-examining the non-fp32 variant 0 path, I believe @zpwenjh 's proposal of enlarge the group size for non-fp32 case will have the minimum impact on performance. I reverted this change in https://github.com/zpwenjh/MIOpen/pull/14. Now https://github.com/zpwenjh/MIOpen/pull/14 should have everything fix reported issues in both #916 and #915 . @zpwenjh Thank you for your contribution in this topic!
@muralinr Please go ahead to pull changes in https://github.com/zpwenjh/MIOpen/pull/14 for a performance test. Thank you!

@zpwenjh Yes, thanks again for your contribution! Could you please merge the recent develop to zpwenjh:fix_batchnorm_precision? I do not have access.
Then we'll compare performance of this PR with develop, make sure the PR pass CI, and finally, merge this to develop. Thanks!
/cc @muralinr

@zpwenjh Yes, thanks again for your contribution! Could you please merge the recent develop to zpwenjh:fix_batchnorm_precision? I do not have access.
Then we'll compare performance of this PR with develop, make sure the PR pass CI, and finally, merge this to develop. Thanks!
/cc @muralinr

@atamazov This develop branch is now merged to this PR.

@zpwenjh Yes, thanks again for your contribution! Could you please merge the recent develop to zpwenjh:fix_batchnorm_precision? I do not have access.
Then we'll compare performance of this PR with develop, make sure the PR pass CI, and finally, merge this to develop. Thanks!
/cc @muralinr

@atamazov This develop branch is now merged to this PR.

I started running verification and performance tests.  I will update results this week.

@zpwenjh Yes, thanks again for your contribution! Could you please merge the recent develop to zpwenjh:fix_batchnorm_precision? I do not have access.
Then we'll compare performance of this PR with develop, make sure the PR pass CI, and finally, merge this to develop. Thanks!
/cc @muralinr

@atamazov This develop branch is now merged to this PR.

I started running verification and performance tests. I will update results this week.

Both BN forward and backward verification and performance tests are fine.  We can go ahead with this PR.

@ce1adon Do you approve?

@zpwenjh @ce1adon @muralinr
:tada:


otk.target aren't recognized if defined inside otk.include

a.yaml:
otk.version: '1'

otk.include.b: "b.yaml"

b.yaml:
otk.target.foo.bar:
  yolo: true

python3 -m otk validate ../a.yaml
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/obudai/work/otk/src/otk/__main__.py", line 3, in <module>
    root()
  File "/home/obudai/work/otk/src/otk/command.py", line 45, in root
    return validate(arguments)
           ^^^^^^^^^^^^^^^^^^^
  File "/home/obudai/work/otk/src/otk/command.py", line 118, in validate
    return _process(arguments, dry_run=True)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/obudai/work/otk/src/otk/command.py", line 60, in _process
    doc = Omnifest.from_yaml_file(src)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/obudai/work/otk/src/otk/document.py", line 33, in from_yaml_file
    return cls.from_yaml_bytes(file.read())
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/obudai/work/otk/src/otk/document.py", line 25, in from_yaml_bytes
    cls.ensure(deserialized_data)
  File "/home/obudai/work/otk/src/otk/document.py", line 64, in ensure
    raise ParseTargetError("omnifest must contain at least one key by the name of `%s.*`" % (PREFIX_TARGET,))
otk.error.ParseTargetError: omnifest must contain at least one key by the name of `otk.target..*`

Yea, we should fix this. We should probably also change the entrypoint documentation to allow otk.target via includes.


Add Spacebars support.

It would be great if your code formatter supported Spacebars.
https://atom.io/packages/language-spacebars
This is part of the templating language for meteor.js

Duplicate of #217.
Is it not working for you? Could you run the Atom Beautify's command Help Debug Editor


Use constant for non state changing functions

Instead of
function get() returns(uint r) { return info; }

do
function get() constant returns(uint r) { return info; }

This way, the function does not incur transaction gas when called via RPC (or use internal keyword if intended to be used only internally).
http://solidity.readthedocs.io/en/latest/contracts.html?highlight=constant#constants

Oh this is interesting. So that's how it knows it's not modifying state?

https://github.com/makoto/blockparty/pull/37


training losses become 0 after doing test among epochs

I did a little change in LaneDetTrainer and base.py, I comment the fast_evaluate code('Only segmentation based methods can be fast evaluated!') and use the LaneDetTester test_one_set function like below. Trying to add val part among epochs.
if self._cfg['validation']:
#
# fast_evaluate code
#
if i == len(self.dataloader) - 1 and epoch > 0 and epoch%self._cfg['val_num_steps'] == 0:
print('start validation on epoch: ', epoch)
LaneDetTester.test_one_set(self.model, self.device, self.validation_loader, self._cfg['mixed_precision'],
[self._cfg['input_size'], self._cfg['original_size']],
10, 42, None,
'tusimple', False, 6, self._cfg['exp_name'], val_json_gt)
self.model.train()
save_checkpoint(net=self.model.module if self._cfg['distributed'] else self.model,
optimizer=None,
lr_scheduler=None,
filename=os.path.join(self.cfg['exp_dir'], 'model' + str(epoch) + '.pt'))
as you can see, I add self.model.train() like  the fast_evaluate code.
However, the loss became 0 after test part like below:
[2, 980] training loss: 29.0062
[2, 980] loss label: 0.6740
[2, 980] loss curve: 2.1232
[2, 980] loss upper: 0.4012
[2, 980] loss lower: 0.6994
[2, 980] training loss aux0: 14.1670
[2, 980] loss label aux0: 0.7017
[2, 980] loss curve aux0: 2.0173
[2, 980] loss upper aux0: 0.2924
[2, 980] loss lower aux0: 0.6955
start validation on epoch:  1
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████| 227/227 [00:02<00:00, 96.23it/s]
[{"name":"Accuracy","value":0.016865079365079364,"order":"desc"},{"name":"FP","value":0.019089574155653453,"order":"asc"},{"name":"FN","value":0.993208516886931,"order":"asc"}]
Epoch time: 38.95s
[3, 80] training loss: 17.1586
[3, 80] loss label: 0.6709
[3, 80] loss curve: 2.0960
[3, 80] loss upper: 0.4002
[3, 80] loss lower: 0.7055
[3, 80] training loss aux0: 2.4547
[3, 80] loss label aux0: 0.1318
[3, 80] loss curve aux0: 0.3381
[3, 80] loss upper aux0: 0.0546
[3, 80] loss lower aux0: 0.1298
[3, 179] training loss: 13.8403
[3, 179] loss label: 0.6764
[3, 179] loss curve: 1.9323
[3, 179] loss upper: 0.3870
[3, 179] loss lower: 0.6878
[3, 179] training loss aux0: 0.0000
[3, 179] loss label aux0: 0.0000
[3, 179] loss curve aux0: 0.0000
[3, 179] loss upper aux0: 0.0000
[3, 179] loss lower aux0: 0.0000
[3, 278] training loss: 14.7566
[3, 278] loss label: 0.6881
[3, 278] loss curve: 2.1140
[3, 278] loss upper: 0.3753
[3, 278] loss lower: 0.6859
[3, 278] training loss aux0: 0.0000
[3, 278] loss label aux0: 0.0000
[3, 278] loss curve aux0: 0.0000
[3, 278] loss upper aux0: 0.0000
[3, 278] loss lower aux0: 0.0000
If I use LaneDetTester after the whole training it works fine. need some advices~

Yes. But after the first validation, The aux0 loss will always be 0

Yes. But after the first validation, The aux0 loss will always be 0

that is interesting, could you see similar behavior for other algorithms(other than lstr)?

@mengxia1994 I think this could be a bug.  Because I rewirte eval() in line 109 of lstr code.  I don't have my laptop, could you try add a corresponding train() method that sets everything to True?

Yes. But after the first validation, The aux0 loss will always be 0

that is interesting, could you see similar behavior for other algorithms(other than lstr)?

Not yet. After a simple trial on all algorithms, I chose lstr to do some more digging and finetune. I tried to add the code above because there is an overfitting and i'm not used or convenient to use tensorboard. Are you suggesting that your first reaction is that it may because of lstr other than some torch settings?

@mengxia1994 I think this could be a bug. Because I rewirte eval() in line 109 of lstr code. I don't have my laptop, could you try add a corresponding train() method that sets everything to True?

In which file?

find it, I will have a try.

@mengxia1994 I have verified this bug, it affects LSTR, BézierLaneNet & RepVGG, and this should fix it. Thanks a lot for pointing this out!

rewrite train
def train(self, mode=True):
    super().train(mode)
    self.aux_loss = True
    self.transformer.decoder.return_intermediate = True

Yes, this mod should bring the same correct behavior for LSTR.

This issue seems to be addressed. I'll close it for now. Feel free to continue commenting for reopen/open a new one.


Support update in the Terraform bridge

The Terraform bridge prototype does not yet support Update, only Create/Read/Delete.
We need to check out what the options are there and preferably implement support in the bridge.

Closed by #159


Looks like the app doesn't know how to handle numbers starting with 0

From times to times, I stumble across some unsolvable numbers. The last example was 0395, but the app only will identify the last 3 digits. You can test the issue by typing 0 to 9, sequentially and isolated. (type 0, enter, type 1, enter, and so on, so you can test all the 10 numbers)

I just got another example:

Well, actually, the zero is not the problem, but the app is generating repeated numbers:

Oh, something is broken. Thanks!
Also there must be a validation: "Your number" must have 4 digits. I can't believe it's not already implemented. :))
Please feel free to contribute (fork + pull request).

@andremarcondesteixeira Solved. :)


Add seabed mask

TODO, after Wu Jung Lee's comments to our PR:

[ ] move the methods to echopype/mask/seabed.py, rename with _
[ ] move get_seabed_mask to echopype/mask/api.py
[ ] test setup part should now use pytest fixtures and be in tests/clean/conftest.py and requested by the test modules

Closing since no longer part of our workflow


uninitialized variable in pio.c

Not to be nit-picking  https://github.com/raspberrypi/pico-sdk/blob/2e6142b15b8a75c1227dd3edbe839193b2bf9041/src/rp2_common/hardware_pio/pio.c line 21. I know this will end up in .bss and get zeroed out but I recommend explicitly initializing it to 0.

Nevermind.


Convert without loss of quality

When converting my sample obj it had ~11k positions in the resulting mesh whereas the original had ~ 45k positions, resulting in edges instead of the round shapes as the original. Can this be prevented or is this indeed an issue?

It's possible it's a bug. Are you able to share the obj?

Unfortunately not the object itself. Can I get you something else to help on it. Would also be available to show you via zoom if you want.

You can also email it to me at<EMAIL_ADDRESS>if you can't share it publicly here.

done. You should have in your inbox

@tomfree I imported the model into Blender and it has around the same number of faces as the gltf from obj2gltf. The glTF also looks the same as in Blender, with hard edges in some places.
Are you sure the obj you used is the higher detail version?


message_view_header: add tooltip over stream name.

Added tooltip to the stream name in the top bar. This tooltip displays stream name and subscriber count as shown in the attached screenshot.
Changes made:

~Grouped stream name and sub count~
As a pr is made to remove sub count, I removed the grouping and made both sections separate again.
Created file message_view_header_tooltip.hbs
Added tippy(tooltip) in message_view_header.js

Fixes: #27360

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Thanks! Please see here for guidelines on how to format your commit message.

@sayamsamal could you please do a first-round review on this PR? I haven't tested.
Dropping the separate tooltip on the subscriber count sounds great to me.

@retsambew What's the answer to this part?

Is it easy to use stream privacy icons here? If not, we can use a #. (See https://github.com/zulip/zulip/issues/25257)

You will also need to re-add and fill out the self-review checklist for this PR to be ready for review. Thanks!

@retsambew What's the answer to this part?

Is it easy to use stream privacy icons here? If not, we can use a #. (See #25257)

Although it's possible to use privacy icons here, I'm not sure if it would look that good in tooltip. Also, it has negligible functionality as the privacy icon of stream is visible right above the tooltip. What's your opinion on this?

Also, I found some issues with your commit message, so please go through the guidelines as mentioned by @alya.

Thank you @sayamsamal for that in-depth review, I understood the points and tried to solve this problem in the simplest way I could. Can you review the newer version of code please?

I have left you some feedback through my review. But to summarise we don't need event handlers to trigger tippyjs tooltips, that part is already handled by the tippyjs library and can be customized using the trigger property.
Also, as I mentioned in https://github.com/zulip/zulip/pull/27466#discussion_r1379338226, another alternative approach is to append a tooltip template message_view_header.hbs and then just reference the template using the data-tooltip-template-id attribute. I don't know which of these two methods is more accurate, but the latter does feel simpler.

Also, please shift the Fixes ... line to the end of your commit message. Following the practices over at https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html will make the work of the reviewers much easier and thus increase the chances of a faster review.

Thank you for the work @retsambew. Due to time constraints, I have opened #27666 to accelerate the integration. Please feel free to pick another issue.

Sorry for the inconvenience @sayamsamal and thank you for all the guidance. I'll try to do better in the next one.

Closing in favor of https://github.com/zulip/zulip/pull/27666 for this issue.


Small fixes

Fixes

Benchmark Python test failure
https://github.com/neondatabase/neon/actions/runs/2977846982
https://neon-github-public-dev.s3.amazonaws.com/reports/main/release/2977846982/index.html#suites/792a596a01c566b9215997335bf18812/8185c7bf6360013c/

AttributeError: 'ZTenantId' object has no attribute 'hex'
test_runner/performance/test_bulk_insert.py:27: in test_bulk_insert
    env.flush()
test_runner/fixtures/compare_fixtures.py:115: in flush
    self.pscur.execute(f"do_gc {self.env.initial_tenant.hex} {self.timeline} 0")
E   AttributeError: 'ZTenantId' object has no attribute 'hex'

Takes https://github.com/neondatabase/neon/pull/2368/files#r959375753 and again embeds it into another PR 🙂

I've added run-benchmarks label, but workflow was already marked as skipped, worth running it to check that it helped. Maybe it will work with a retry (cannot check yet, because workflow is still running)

I've tried rerunning it a few times, but looks like benchmarks won't start for such jobs:

but looks like benchmarks won't start for such jobs:

Eh, it means it evaluates skips once per push, so may be we should check for benchmark label on label creation event, if thats even possible


No Support for stage regions like South Central US Stage in Azure.Core.AzureLocation enum

Please add support for stage regions like South Central US Stage in Azure.Core.AzureLocation enum. As different teams are onboarding to stage regions for internal testing, this is a requirement now.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.22268374,Storage:0.0589747,Search:0.035927936'

Since there's been no follow-up for discussion of scenarios where the recommended approach does not work, I'm going to mark this as addressed.   Please feel free to unresolve if you'd like to continue the discussion.


PT FX inspect tensor

Type of Change
Support "inspect tensor" feature for FX model
No API changed
Expected Behavior & Potential Risk
Inspect tensor value correctly

Need to update ut test.


Packaging/publication/naming (what to include in main stylesheet)

I like that we've broken out userscript styling and user overrides into separate files so the main stylesheet can be versioned independently (and will hopefully remain fairly stable).
We should start thinking about how to package and publish the separate stylesheets, though.
Just some rough ideas to kick off discussion:

Publish WKElementaryDark.css as its own separately maintained and versioned stylesheet.

Fold WKED-wkof-menus.css into the main stylesheet rather than as a separate file.
Rationale: the Wanikani Open Framework is used by almost every user script in active use. Probably worth folding this into the main script (along with anything else this prevalent).

Keep WKED-self-study.css, WKED-stroke-order.css, and WKED-ultimate-timeline.css as separate stylesheets versioned and published independently. Users will need to pick and choose which of these (if any) that they want to install separately.

Publish at least one non-default color scheme as an example for how to do your own theming. Propose we rename the "color-spins" folder "user-themes" and use a .css extension.

We should probably start including the @-moz-document rules in the source files (both for the main stylesheet as well as userscript overrides and user-themes). I've just been manually adding "URLs in domain: wanikani.com" in the stylus editor, but we should probably an explicit @-moz-document domain("wanikani.com") { ... } (or whatever) around all the rules in revision control.

Fold WKED-wkof-menus.css into the main stylesheet rather than as a separate file.

I was thinking of doing exactly this, it felt weird having to load 2 additional styles for a single script. I will add it as an issue.

Publish at least one non-default color scheme as an example for how to do your own theming. Propose we rename the "color-spins" folder "user-themes" and use a .css extension.

I agree with introducing some alternative color schemes, even a blank template might prove useful. But changing the folder name to "user-themes" seems a bit ambiguous. Theme, at least in my mind, evokes an image of an independently working stylesheet. Something like "user-palettes" might be more appropriate in our case.

We should probably start including the @-moz-document rules in the source files

It used to be a part of the file in the past. But it messed with indents on my side, so I decided to drop it.
It's not a direct solution, but I would prefer to leave the developer version as is and introduced a parallel file, which would reflect the state of the latest public release, including the @-moz-document wrapper and the ==UserStyle== metadata.

We should also alter the userscripts to take their colors directly from the new palette files instead of the main theme file. It could be changed to take the colors in addition, rather than instead of, but working with var(--USER, var(--ED, *color*)) could get messy really quickly.

Something like "user-palettes" might be more appropriate in our case.

I'll name it "user-overrides" just in case we introduce any props for non-color things (spacing, etc.).

It used to be a part of the file in the past. But it messed with indents on my side, so I decided to drop it.

Heh. I thought I accidentally deleted it while cutting-and-pasting between my editor and stylus. I need to see if I can figure out a more elegant solution than cut-n-paste.
Regardless, it's a minor nit.
No work is the best work: I agree, let's just leave the dev versions without the ==UserStyle== headers or @moz-document directives. I'll let you add those when publishing.

We should also alter the userscripts to take their colors directly from the new palette files instead of the main theme file.

I'm not sure I follow, but I think we're both thinking the same thing: We're effectively publishing an API.
We need to have the freedom to change internal variables (e.g. palette colors) at will going forward. As long as we keep things internally consistent, those changes won't break anything in userscript (or user override) stylesheets.
But we are "publishing" an external interface with the "semantic" variables. We should be much more reticent to change, add to, or delete from those (even spelling or other naming changes). Changes to those props are effectively an API version change that will have ripple effects.
As long as userscript stylesheets only reference "semantic" props and don't access palette colors directly, I think maintenance is easy. On rare occasions, a userscript stylesheet may need to define its own colors for something we don't have a semantic variable for, but I think it's okay to leave that ad hoc.
I do, however, still think it's worthwhile to only have users override with --USER-* variables (not touching the --ED-* props). Having supported many things over the years, I like the bullet-proofing: I can pretty much guarantee that we'll field support requests from people not loading things in the correct order, or accidentally changing something they shouldn't have if we don't do this.

It could be changed to take the colors in addition, rather than instead of, but working with var(--USER-*, var(--ED-*, color)) could get messy really quickly.

True. I'm playing with it now, though, and the pain is pretty localized and only done once.
I'm starting to think this external/semantic vs. internal/don't-touch/"static" distinction is important. I'm beginning to think that we probably shouldn't use the same --ED-* naming convention for both, since the API is only the former.

I'm not sure I follow, but I think we're both thinking the same thing

I do, however, still think it's worthwhile to only have users override with --USER-* variables

That's what I have been getting at. My intention was to remove the --ED-* overrides from all the userscript styles and replace them with --USER-* ones. The fallback colors should match the default theme, so there shouldn't be any reason to have the script inherit the same colors again. If there is an --USER-* variable, that is overriding some of the default --ED-* values, we can use it directly instead of going through the --ED-*.
Additionally, if someone were to load only a user color palette and a script, everything should still work.

It could be changed to take the colors in addition, rather than instead of, but working with var(--USER-*, var(--ED-*, color)) could get messy really quickly.

True. I'm playing with it now, though, and the pain is pretty localized and only done once.

That might be true, but I don't see the benefit of still including the --ED-* inheritance. I would like to discourage the users from altering the main theme file, as their changes might get reverted with future updates that stylus automatically manages.

I'm starting to think this external/semantic vs. internal/don't-touch/"static" distinction is important. I'm beginning to think that we probably shouldn't use the same --ED-* naming convention for both, since the API is only the former.

I wouldn't be opposed to changing the static prefix to something like --Default , --Static, --Internal or even something less telling but shorter like --S

We should also introduce some sort of variable that would work with extra-study img filters. Possibly even WK logo and other images. As things stand, the extra study img is an eyesore, when trying to move to different surface colors.

Ah!
I think we're accomplishing the same objective two different ways. Both of us want users (and userscript stylesheet writers) to leave these files alone and only create their own.
I was thinking WKElementaryDark.css itself as well as any userscript stylesheets should use any --ED-* props in their rules that they want. Those become the API.
We define those props at the top of the WKElementaryDark.css file like:
:root {
  --ED-surface-1: var(--USER-surface-1, var(--EDI-gray-1));
  ...
}

Then users can override any of these as they wish in their own simple css files:
:root {
  --ED-surface-1: #222222;
  ...
}

I've actually done all the work for this in the README branch already.

We should also introduce some sort of variable that would work with extra-study img filters. Possibly even WK logo and other images. As things stand, the extra study img is an eyesore, when trying to move to different surface colors.

Agree. Take a look at how open-props does things. Please open an issue to track separately.

Also gonna nuke --ED-brand-alt. It was only used for "new" badges on the levels page, I think, and was just a slightly darker version of the brand color. I think just using the brand color suffices.

I will take a look at all the changes tomorrow as Im short on time today. But it looks promising

All of this is included in Pull Request #65. Closing this issue so we can track it there.


Add Budget accounting

Description
Adds the budget accountant that manages the privacy budget.
Affected Dependencies
None.
How has this been tested?
The budget_accounting_test.py file contains some simple additional tests.
Checklist

[x] I have followed the Contribution Guidelines and Code of Conduct
[x] I have commented my code following the OpenMined Styleguide
[x] I have labeled this PR with the relevant Type labels
[x] My changes are covered by tests

Thank you very much for the feedback!


Fix bytes type error on httpcient set_proxy

In python3.4 occured bytes type error when connect by setting proxy.
sample
>>> blob_service = BlobService(account_name=storage_account_name, account_key=storage_account_key)
>>> blob_servie.set_proxy('192.168.xx.x', 8080)
>>> [b.name for b in blob_service.list_blobs(storage_container_name)]

stacktrace
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/vagrant/venv/work340/lib/python3.4/site-packages/azure/storage/blobservice.py", line 606, in list_blobs
    response = self._perform_request(request)
  File "/home/vagrant/venv/work340/lib/python3.4/site-packages/azure/storage/storageclient.py", line 167, in _perform_request
    resp = self._filter(request)
  File "/home/vagrant/venv/work340/lib/python3.4/site-packages/azure/storage/storageclient.py", line 156, in _perform_request_worker
    return self._httpclient.perform_request(request)
  File "/home/vagrant/venv/work340/lib/python3.4/site-packages/azure/http/httpclient.py", line 216, in perform_request
    self.send_request_headers(connection, request.headers)
  File "/home/vagrant/venv/work340/lib/python3.4/site-packages/azure/http/httpclient.py", line 184, in send_request_headers
    if i.startswith("Host: "):
TypeError: startswith first arg must be bytes or a tuple of bytes, not str

Thank you!


Custom Policy

TL;DR
modify the repository.rego file, commenting or removing some line to disable some rule.
Error at run time

Expected behavior
see if we can deactivate some rules according to team policies
Observed behavior
No response
Version
0.2.7
On which operating system are you using legitify?
Linux
Relevant log output
Error: compiler: 11 errors occurred:
../gitlab/repository.rego:11: rego_type_error: multiple default rules data.repository.project_not_maintained found
../gitlab/repository.rego:150: rego_type_error: multiple default rules data.repository.no_conversation_resolution found
../gitlab/repository.rego:180: rego_type_error: multiple default rules data.repository.code_review_not_required found
../gitlab/repository.rego:102: rego_type_error: multiple default rules data.repository.repository_require_code_owner_reviews_policy found
../gitlab/repository.rego:195: rego_type_error: multiple default rules data.repository.code_review_by_two_members_not_required found
../gitlab/repository.rego:240: rego_type_error: multiple default rules data.repository.repository_allows_committer_approvals_policy found
../gitlab/repository.rego:254: rego_type_error: multiple default rules data.repository.repository_dismiss_stale_reviews found
../gitlab/repository.rego:50: rego_type_error: multiple default rules data.repository.forking_allowed_for_repository found
../gitlab/repository.rego:121: rego_type_error: multiple default rules data.repository.project_webhook_doesnt_require_ssl found
../gitlab/repository.rego:210: rego_type_error: multiple default rules data.repository.repository_allows_review_requester_to_approve_their_own_request found
rego_compile_error: error limit reached

Additional information
No response

Hi @ctit-cl,
Custom policies are only for adding new policies and not for removing existing ones.
I've created this feature request to support it.
Meanwhile, If you're willing to compile legitify from source I could guide you how to deactivate the unwanted policies

@ctit-cl  I've just added support for specifying policies to ignore - https://github.com/Legit-Labs/legitify/pull/218
If you run from the main branch you can use the --ignore-policies-path PATH option to do that.
The ignore file needs to contain each policy name in a new line, e.g.
no_conversation_resolution
requires_status_checks

Let me know how it works for you 😄


Support Neo4j GraphChainQA and Vector Store

Mainly adding this here as a placeholder, for myself and anyone else who is interested to track. I may be able to find time to work on this but I'm waiting to see how this PR progresses first (https://github.com/langchain-ai/langchainjs/pull/2514), then I'll replicate a similar approach to whatever the accepted approach is.

Yes will sort that soon! Apologies for the delay.

As far as I'm aware this has been implemented now. I'll go ahead an close this.


Updated Migration Table content for JDK 11 and above

Update Migration guide: OpenJDK 11 and above #1912

Greetings of the day, Hope you are doing well @smlambert
please review this PR, and let me know if any changes are required.
Thanks and Regards


Pass writeable down to addMarkers

Should resolve #721
@chriswhong Lemme know what you think here; it feels dangerous to set a parameter to a default like this, but I couldn't find another way to do it.

We were calling addMarkers() without passing in writable


Log details of jobs in Provider image

Predecessor: https://github.com/prosopo/captcha/issues/45
For any provider jobs that run (batch commit, calculate solutions, database maintenance), the status and outputs of these jobs must be stored somewhere.

child of #339

Needs refinement:

What specific jobs
When to store
-Where to store


chore: align more hotcases

Summary
Resolves hotCases:

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

!eco-ci


Update UniFi to 7.3.83

snappyjava not install to openjdk11 requerid in UniFi 7.3.83
How to fix?

Fix install openjdk8.


test(plugin-wdm): prove we do not get an ios url when refreshing an expired device

merged via a rebase; closing manually


Expanding incorrect section on click

Upon clicking on a heading in the quiet outline, the heading above is expanded, rather than the one clicked.
https://github.com/guopenghui/obsidian-quiet-outline/assets/85257386/771f791a-d5ec-40c3-977c-362871c66dd2

Ok, I have kind of fixed this. (waiting 200ms -> 500ms)
There are two different events controling heighlighing and expanding——cusor position change and scroll. But when you click a heading, both event occurs. So sometimes calculating to different position results. Current strategy is, when clicking a heading, scroll event will be blocked for 500ms, so only cursor position change takes effect. But 500ms may not be a perfect choice, clicking too fast can make it lose effectiveness.

Thank you. Works well enough.


New Domain

Domain is used to steal facebook accounts

I need to know how to create a pishing site links

This domain seems to be defunct, however it was used for a german facebook scam.

Why in suspicious domains? It was used in a German Facebook scam. I can add even more link. They try to scam you like 100 times a day. My chat box is full of that spam.

Please provide evidence for the scam you have witnessed.
If you do so, feel free to re open the PR :)

Here is the evidence, however the domain seems to be defunct.

Here is the evidence, however the domain seems to be defunct.

tyvm, didn't found the url in my history anymore.


Add 3D viewer for Alphafold-predicted protein structures

Description
This PR adds a viewer of 3D protein structures predicted by the AlphaFold AI to Ensembl pages. The first organism that we are testing this on is wheat (Arabidopsis thaliana).
The proposed widget incorporates the pdbe-molstar plugin and wraps it into a custom web component using the Lit library for convenience. The code is written in modern javascript (supported by ~95% of web browsers) and saved into /widgets/htdocs/alphafold, outside of the components folder which would be processed by our regular build scripts.
Note that because this code exists outside of our usual build pipeline, the files will not be concatenated, minified and stamped with a hash in a usual way. To avoid caching issues, this PR disables caching of the static files in the alphafold folder. Since they are tiny, this should not result in significant performance issues.
Sandbox
http://ves-hx2-75.ebi.ac.uk:8450/Arabidopsis_thaliana/Transcript/AFDB?db=core;g=AT3G52430;r=3:19431095-19434450;t=AT3G52430.1
The pull request is submitted against the master branch.
See also
Related PR in ensembl-webcode: https://github.com/Ensembl/ensembl-webcode/pull/856

Geneview pages need fixing on this sandbox though before I can approve

I believe they are fixed now, @ens-st3

From code review meeting also to do:

handle rest call failure (Show error message)
Get rid of extra component (Component/AFDB.pm)

handle rest call failure (Show error message)
Get rid of extra component (Component/AFDB.pm)

Done for both.


About my last filter

Hello, about my last contribution please note that now Steam:true is not supported anymore because I  think is duplicated with steam:installed, but If you don't think that way I can add it too.

This should be discussed in the pull request itself and not as an issue.


chore: fix post_update hook

See zulip discussion at

https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/Disable.20lake.20post-hook.20when.20importing.20mathlib.3F/near/401811422
https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/lake.20update.3A.20invalid.20toolchain.20name/near/401860157

bors merge
Thanks!


Scala 3: * is replaced by _ when together with given

When importing package.{given, *}, the * is replaced by _, leading to compilation errors. E.g.
-import foo.domain.{ given, * }
+import foo.domain.{_, given}

This happens using the latest snapshot: 0.5.0+42-7e4a4f8a-SNAPSHOT.

In particular this leads to compilation error if the compiler flag -source:future is set. In any case, one would expect organize-imports to rewrite _ by * since the former is deprecated.

Scalafix 0.11.0 is out with OrganizeImports built-in, and does contain the fix.

(assuming this is a duplicate of https://github.com/liancheng/scalafix-organize-imports/issues/279, but it does look like it)


Add shape and dtype of leaked tracer to UnexpectedTracerError.

Adding some extra info which helped me track down a leaked tracer. Looks like:
...
The tracer that caused this error was created on line (...)
The tracer has shape (4, 3) and dtype int32.
...

Looks like flake8 is unhappy: you may need to quote some characters in your regex or use a raw string.


IBSng accounting

IBSng II Lan Accounting
IBSng Lan Accounting is a system for policymaking, management, monitoring, and control of network resource consumption (Internet and local and enterprise servers) in organizations, offices, and companies. This system helps the managers of the communication and information technology department of the organization to optimize the use of network resources in addition to monitoring the network users. The use of Lan Accounting system helps to increase the efficiency of the people in the organization, and by controlling the accesses, it also increases the security of the system, which will lead to a reduction in costs by optimizing the network.
IBSNG is a powerful system that, relying on 20 years of presence in more than 3000 networks across the country in different dimensions and different needs, can provide all your needs to control and maintain the maximum quality of the network.

IBSng II Lan Accounting
IBSng Lan Accounting is a system for policymaking, management, monitoring, and control of network resource consumption (Internet and local and enterprise servers) in organizations, offices, and companies. This system helps the managers of the communication and information technology department of the organization to optimize the use of network resources in addition to monitoring the network users. The use of Lan Accounting system helps to increase the efficiency of the people in the organization, and by controlling the accesses, it also increases the security of the system, which will lead to a reduction in costs by optimizing the network.
IBSNG is a powerful system that, relying on 20 years of presence in more than 3000 networks across the country in different dimensions and different needs, can provide all your needs to control and maintain the maximum quality of the network.


Add Google Colab Demo

The demo on HG Spaces is amazing! I used it for a few photos and really like it.
Unfortunately it seems it's getting quite crowded and takes over 20min to process due to the queue. Also it runs on a CPU.
I added a colab notebook that lets you upload a photo and run the model. It works on both CPU and GPUs. You can see what it looks like here: https://colab.research.google.com/github/xhlulu/animegan2-pytorch/blob/main/colab_demo.ipynb

cool, also the demo on HF is using gpu now, try it out :)

Thanks! Actually there is a colab demo in readme so I updated it with the hub model.

@bryandlee the notebook is different. it is specifically a interact jupyter app that lets you upload your file, select the file type and run the model without having to run any code cell.

I see! That gives better accessibility


Unresolved references to methods

I have a problem in buildtime with generated code, it seems to be using different naming of method names on a Grpc service than there actually is. I have a proto file like
service BookService {
    // Book detail
    rpc getBook (GetBookRequest) returns (Book) {}
}

and the generated BookServiceGrpc contains method
 public void getBook(com.book.BookOuterClass.GetBookRequest request,
        io.grpc.stub.StreamObserver<com.book.BookOuterClass.Book> responseObserver) {
    ...
}

but generated file from kroto have this method
suspend fun BookServiceStub.getBook(request: BookOuterClass.GetBookRequest =
        BookOuterClass.GetBookRequest.getDefaultInstance()): BookOuterClass.Book =
        clientCallUnary(request, BookServiceGrpc.getGetBookMethod())

and the problem is in getGetBookMethod. There is no such method and it fails with Unresolved reference: getGetBookMethod
i cant find anything about it in config. Am I doing something wrong? I've tried also another library for kotlin + coroutines (https://github.com/rouzwawi/grpc-kotlin) and the build problem was the same
Note - I am using this in Android project with protobuf-lite, here is my config:
    implementation ("javax.annotation:javax.annotation-api:1.2")
    implementation("com.google.protobuf:protobuf-lite:3.0.1")

    implementation("io.grpc:grpc-core:1.16.1")
    implementation ("io.grpc:grpc-protobuf-lite:1.16.1")
    implementation ("io.grpc:grpc-okhttp:1.16.1")
    implementation ("io.grpc:grpc-stub:1.16.1")

    implementation ("com.github.marcoferrer.krotoplus:kroto-plus-coroutines:0.3.0")
    implementation ("com.github.marcoferrer.krotoplus:kroto-plus-test:0.3.0")
    implementation ("com.github.marcoferrer.krotoplus:kroto-plus-message:0.3.0")

protobuf {
    protoc {
        artifact = 'com.google.protobuf:protoc:3.6.1'
    }
    plugins {
        grpc {
            artifact = 'io.grpc:protoc-gen-grpc-java:1.0.0-pre2'
        }
        javalite {
            artifact = 'com.google.protobuf:protoc-gen-javalite:3.0.0'
        }
        kroto {
            artifact = "com.github.marcoferrer.krotoplus:protoc-gen-kroto-plus:0.3.0:jvm8@jar"
        }
    }
    generateProtoTasks {
        def krotoConfig = file("krotoconfig.asciipb") // Or .json
        all()*.plugins {
            javalite {}
        }
        ofNonTest()*.plugins {
            grpc {
                // Options added to --grpc_out
                option 'lite'
            }
            kroto {
                outputSubDir = "java"
                option "ConfigPath=$krotoConfig"
            }
        }
    }
}

I've figured it out, I had some old dependency versions

On a separate note, you might want to remove the default java configuration if using java lite. The Gradle protobuf plugin adds it implicitly. It’s mentioned in more detail here. https://github.com/google/protobuf-gradle-plugin/blob/master/README.md#default-outputs
Also if you are using the kroto dslmarker option you’ll want to make sure you set your kroto out to javalite not java
        all()*.builtins(){
            remove java
        }
        ofNonTest()*.plugins {
            grpc {
                // Options added to --grpc_out
                option 'lite'
            }
            kroto {
                outputSubDir = "javalite"
                option "ConfigPath=$krotoConfig"
            }
        }


Support IPv6

The ExternalDNS integration currently always creates DNSEndpoints with A records, even if the target IP is an IPv6 address. Instead either A or AAAA records should be created, depending on the target address family.

Hey @DerEnderKeks! I've never used IPv6 with Kubernetes ... can you give me an example of how the service's .status field looks like? Are IPv6 addresses simply appended to .status.loadBalancer.ingress[]?

Yup, just like with IPv4:
status:
  loadBalancer:
    ingress:
      - ip: 2001:db8::1

Thanks a lot! Could you please release a new image version?

Done!


Support select measurement transformation

This adds simple support for LLVM select instruction measurement use transformation. LLVM inlining can at times take a branch instruction and turn it into a select instruction, which means it would no longer match the branch rule and end up leaving behind calls to __quantum__rt__result_equal. This treats select like branch such that select on result value One will be turned into an appropriate use of __quantum__rt__read_result.

I'm done with the review round.

Thanks @kuzminrobin! I'll work through the feedback later; for now I'm just trying to make sure the new unit test actually passes...

Finally got the passes CI working, but the component governance check is still failing. I think the merge from main in #1181 should resolve that.


Intl.js: refactor fallback logic to be more general to any platform implementation behavior

See: https://github.com/Microsoft/ChakraCore/pull/3769#discussion_r140082740

We should't have any fallback logic anymore as of #4390


Linking HELICS 3.X with Matlab

Hello,
Earlier, my attempts to integrate Matlab with HELICS 2.8 ended in a fiasco, so, with suggestion from the developers, I decided to move up to HELICS 3.
As, I execute the installation instructions given on: [https://github.com/GMLC-TDC/matHELICS]
I get the following error: (for clarity, I am sharing the exact screenshot)
(Pardon if I did something wrong, I am relatively new to linux)

Looking forward to your support in this regard.

What operating system is this on?

What operating system is this on?

It is a Ubuntu 21.10

If possible, uploading a copy of helicsMex.mexa64 might help with figuring out what is going on/replicating the issue.

@nightlark
Appears that the mexa64 is not one of the supported types here, so I can email that alternatively.

@phlptp
Here is what happens with using mex -setup C++

I am not sure if I am putting the strings line in correct syntax:

You will have to do that second one on the bash command line,  not in matlab it is is linux command line,  not even sure it works there or if you need to install something to use strings.

strings is often installed on Linux systems, if it isn't I think the package it comes from is binutils.
The << and >> are being used to show that the text inside is a description of what the argument that replaces those <<>> and everything inside them would be (as in those carrots and all the text inside them will be gone). All that is saying is to run strings on the libstdc++ file given in the error message.
For uploading the mex file, you can probably trick GitHub by making a copy with a supported extension like .png, .zip or similar to upload.

@phlptp
Sorry I missed that it had to be executed on a Command Line.
So here is how I was able to do it:

I get the same result as above, after I execute the buildHelicsInterface(), clearly I am not able to get the syntax correct.
@nightlark
Here is the Zip file of mexa64.
helicsMex.zip

You left the << and >> characters in the string instead of replacing them -- in the example command given, those are being used to mean replace the descriptive string including those characters with a file; unfortunately << and >> are both valid syntax for bash (redirection operators). A maybe clearer way of putting it is: strings path/that/points/to/libstdc++.so.6 | grep GLIBCXX.
Or run the strings command on the libstdc++.so.6 file, and pipe the output | to the grep command to look for lines starting with GLIBCXX

Here's a screen recording of running the command.

@nightlark
Thanks for the succinct explanation, My output is exactly the same as yours:

Hello Philip and Ryan,
Any leads up till now?

Hello,
Checking back to see if their are any leads on it?

Sorry, I don't have any updates on this.
I think Philip was going to see if the bug occurs on one of the HPC systems here that already has Matlab installed -- I'm not sure if that has been tried yet.

As best as we can tell the Matlab interface is behaving normally on Linux now as of the 3.3.0 release.  We are going to tag a 3.3.1 release soon to match with the latest HELICS release.

Hi Philip,
Downloaded the newest version from the repo, extracted it and ran buildhelicsinterface() from inside Matlab, got the same error.