Confusion between layers.Activation('softmax'...) and activations.softmax(...)

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows7
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version (use command below): 2.0.0
Python version: 3.7.5
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 10.0.1
GPU model and memory: QuadroK620M

I am building a custom model, and trying to use mixed precision. Please take a look at the following two custom models
from __future__ import absolute_import, division, print_function, unicode_literals
import functools

import numpy as np
import tensorflow as tf
from tensorflow.keras import layers, activations

class SFM1(tf.keras.Model):
    def __init__(self):
        super(SFM1, self).__init__()
        self.output_layer = layers.Activation('softmax', dtype='float32')

    def call(self, inputs):
        return self.output_layer(inputs)

class SFM2(tf.keras.Model):
    def __init__(self):
        super(SFM2, self).__init__()

    def call(self, inputs):
        return activations.softmax(inputs, axis=1)

x = tf.random.uniform((2, 4, 64, 64, 64), dtype=tf.float32)
sfm1 = SFM1()
y1 = sfm1(x)

sfm2 = SFM2()
y2= sfm2(x)

tf.math.equal(y1, y2)

y1 and y2 differ, because layers.Activation(...) assumes axis=-1 by default.
The issue is, that in mixed presion doc here
The dtype of the output layer shall be specified as tf.float32, but activations.softmax(...) cannot do it. If I use layers.Activation(...), the axis cannot be specified as 1 ( I am using channel_first data, and I am afraid that cannot change source data). So what can I do?
Shall I have to work around by
 tf.dtypes.cast(activations.softmax(inputs, axis=1), dtype=tf.float32)

@yourtheron  You can refer to the following question which should be able to answer your question.
Also please post questions like these on stackoverflow as this question is not related to bug/performance, build/install, feature request or docs related issue. Thanks!

@gowthamkpr . Thanks for the notice. And I will do so in future. But unfortunately, that post on Stackoverflow cannot answer my question. Softmax layer cannot specify precision, which means that if I use mixed precision and a Softmax layer as the output layer, I cannot convert float16 back into float32. Any work-around? I have asked the same thing in the post on Statckoverflow.


[B03656] Changes to support automated deployment

Coverage decreased (-0.5%) to 23.896% when pulling 2768f6aa6c10dc4fe1404a65f293b1175e4ff706 on aug-dame-sprint-b03656-deploy into<PHONE_NUMBER>41e8d63598211e7961a6adf47578a6 on master.


Cannot set different color in specific Tex forms.

Let's say I have:
        p_calc = TexMobject("p","=",r"\frac{n}{q}")
        p_calc.set_color_by_tex_to_color_map({
            "n": RED,
            "p": BLUE,
            "q": GREEN
        })

which p_calc  is p=n/q.
I want p to be blue colored,n red colored and q green colored.
I have tried different methods,even \frac{{\color{Red} a}}{b} but still it changes all n/q to color green or is not acceptable.

frac has two arguments, you can't color it with Manim unfortunately (I too complain about that don't worry).
An alternative is to use \over :
x = TexMobject("a", "+", "{2", r"\over", "3}")

Thank you!
So if anyone has a similar problem,just do this:
x = TexMobject("a", "+", "{n", "\\over", "q}")
x.set_color_by_tex("n", YELLOW).set_color_by_tex("q", RED)

or this:
x = TexMobject("a", "+", "{q", "\\over", "n}")
x.set_color_by_tex_to_color_map({
     "n": YELLOW,
     "q": RED
})

t2c = {"n": YELLOW, "q": RED}
text = TexMobject("a+{n \\over q}", tex_to_color_map=t2c)

@JimChr-R4GN4R This is also feasible.
This is because when initializing TexMobject, the incoming tex_to_color_map will automatically split the incoming string according to the keys in the t2c dictionary. However, the string cannot be automatically split when using the set_color_by_tex_to_color_map method after initialization.


[Feature] Add Angular 7 support

I'm submitting a

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Enhancement
[x] Feature request
[ ] Documentation issue or request

Description
We should add Angular 7 support, since it have very small breaking changes, probably just swapping dependencies will do the job.
Version Information
ngx-editor: 4.1.0
angular: 7.0.0

@waynethompson @amiram
Please check my fork of this package, updated to be compatible up to angular 9, and not depending on bootstrap or fontawesome, just angular/material.
https://www.npmjs.com/package/@iget/editor


[UPDATE] - Header nav should be dropdown

@fvntr to add more submenu items please updated the config.toml file

@fvcproductions will do the updates.
Yes, you will need to add the submenu items in the config file.

@fvntr config.toml just needs to have all the children links defined unless a function is used in the HTML.
@cclaro Sounds good - thank you again - they are minor and mostly related to design and mobile-responsiveness.

Closing in favor of #228 - thanks for your contributions @cclaro 😊

Welcome @fvntr, sorry not getting back to you for the last updates, let me know if you still need some help on this.


Breaks tests

OS/Platform
My actual OS is not present in the bug report template.
Installed
OS/Platform's package manager
Version
122.0.6261.128
Have you tested that this is not an upstream issue or an issue with your configuration?

[X] I have tried reproducing this issue in Chrome and it could not be reproduced there
[X] I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
[ ] I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description
When applying ungoogled-chromium's patchset to a chromium source, it breaks tests
How to Reproduce?

Fetch Chromium and relevant ungoogled patchset for versions 122.0.6261.128
Run <ninja_out>/bld/base_unittests --test-launcher-bot-mode

Actual behaviour
Tests fail.

Relevant log output
[6895/6895] All/StatisticsRecorderStarvationTest.StatisticsRecorderNoStarvation/5 (5435 ms)
Retrying 5 tests (retry #0)
[0319/190338.859744:INFO:test_launcher.cc(1192)] Starting [FileUtilTest.PreReadFile_Executable]
[0319/190338.882295:INFO:test_launcher.cc(1192)] Starting [ReadOnlyFileUtilTest.ContentsEqual]
[ RUN      ] FileUtilTest.PreReadFile_Executable
../../base/files/file_util_unittest.cc:4558: Failure
Value of: PreReadFile(test_exe, true)
  Actual: false
Expected: true
[  FAILED  ] FileUtilTest.PreReadFile_Executable (0 ms)
[6896/6900] FileUtilTest.PreReadFile_Executable (0 ms)
[0319/190338.904986:INFO:test_launcher.cc(1192)] Starting [StringUtilTest.MatchPatternTest]
[ RUN      ] ReadOnlyFileUtilTest.ContentsEqual
../../base/files/file_util_unittest.cc:2746: Failure
Value of: ContentsEqual(binary_file, binary_file_same)
  Actual: false
Expected: true
[  FAILED  ] ReadOnlyFileUtilTest.ContentsEqual (0 ms)
[6897/6900] ReadOnlyFileUtilTest.ContentsEqual (0 ms)
[0319/190338.927542:INFO:test_launcher.cc(1192)] Starting [AlternateBucketDistribution/PartitionAllocThreadCacheTest.Bookkeeping/0]
[ RUN      ] StringUtilTest.MatchPatternTest
../../base/strings/pattern_unittest.cc:12: Failure
Value of: MatchPattern("www.9oo91e.qjz9zk", "*.com")
  Actual: false
Expected: true
../../base/strings/pattern_unittest.cc:40: Failure
Value of: MatchPattern(u"www.9oo91e.qjz9zk", u"*.com")
  Actual: false
Expected: true
[  FAILED  ] StringUtilTest.MatchPatternTest (0 ms)
[6898/6900] StringUtilTest.MatchPatternTest (0 ms)
[0319/190338.950140:INFO:test_launcher.cc(1192)] Starting [AlternateBucketDistribution/PartitionAllocThreadCacheTest.Bookkeeping/1]
[6899/6900] AlternateBucketDistribution/PartitionAllocThreadCacheTest.Bookkeeping/0 (0 ms)
[6900/6900] AlternateBucketDistribution/PartitionAllocThreadCacheTest.Bookkeeping/1 (0 ms)
3 tests failed:
    FileUtilTest.PreReadFile_Executable (../../base/files/file_util_unittest.cc:4548)
    ReadOnlyFileUtilTest.ContentsEqual (../../base/files/file_util_unittest.cc:2704)
    StringUtilTest.MatchPatternTest (../../base/strings/pattern_unittest.cc:11)
Tests took 36 seconds.
>>> ERROR: ungoogled-chromium: check failed
>>> ungoogled-chromium: Uninstalling dependencies...

Additional context
I am using Alpine, and building from source.

Whats your goal with this? Do you want to see if ungoogled still passes all tests to catch us introducing bugs?
I guess we can adjust domain substitution to ignore tests

to not require the need for ignoring tests that ungoogled-chromium breaks, making it easier for people to build ungoogled-chromium (i waited foo hours just to see it fail due to tests) using their package managers

Those two goals are mutually exclusive. As per building instructions for ungoogled-chromium one isn't supposed to run tests. If you're using ungoogled-chromium patches within your other workflow, you're expected to adapt it, say exclude tests for example.
Not breaking tests is admittedly a noble goal. It might however have impact on maintainability of ungoogled-chromium.

I hope your question(-s) has(-ve) been answered, otherwise please let us know.
Closing this issue for now.

I'm not sure it was answered. Tests help gurantee the behavior of Chromium, and the ungoogled-chromium patchset introducing unexpected behavior is unwanted.
Unless there is a specific reason for the behavior to change (such as documentation on why it changed), this shouldn't be closed, as it is a bug, not a question.

this shouldn't be closed, as it is a bug

We try to keep those bugs open, upon which we can act somehow. I doubt this one being a priority at this time unfortunately.

I doubt this one being a priority at this time unfortunately.

Doesn't this imply maybe one day it can be looked into?

We try to keep those bugs open

If this bug is unsolvable, or out of scope, then i will agree in that it should be closed.

@apprehensions I admit testing is important and I'm not implying it being out of scope, it is that no one looked into it yet. Also it might be a non-trivial undertaking considering the amount of changes ungoogled-chromium brings into the code.


permit2_sign not work on bsc

permit_data, signable_message = codec.create_permit2_signable_message(
        approve_token,
        allowance_amount,
        codec.get_default_expiration(365*24*3600),  # 30 days
        p2_nonce,
        UR_ADDRESS,
        codec.get_default_deadline(),  # 180 seconds
        56,
    )

signed_message = client.w3.eth.account.sign_message(signable_message,  private_key=wallet_key)
    encoded_input = (
            codec
            .encode
            .chain()
            .permit2_permit(permit_data, signed_message)
            .v2_swap_exact_in(FunctionRecipient.SENDER, amount_in, min_amount_out, path, payer_is_sender=True)
            .build(codec.get_default_deadline())
    )

i used the code to generate permit_data and signed_message, then add permit2_permit(permit_data, signed_message) to the call chain, the transaction fails. but if i signed in the pancake and swap once, then remove the permit2_permit from the sign, the code works like a charm.

failed transcation (with permit2_perimit) decoded data:

(<Function execute(bytes,bytes[],uint256)>, {'commands': b'\n\x08', 'inputs': [(<Function PERMIT2_PERMIT(((address,uint160,uint48,uint48),address,uint256),bytes)>, {'struct': {'details': {'token': '0x55d398326f99059fF775485246999027B3197955', 'amount':<PHONE_NUMBER>330902918203684832716283019655932542975, 'expiration':<PHONE_NUMBER>, 'nonce': 0}, 'spender': '0x1A0A18AC4BECDDbd6389559687d1A73d8927E416', 'sigDeadline':<PHONE_NUMBER>}, 'data': b'>\xb4\x145\xc4t[]zS\xad\xc7\x9e\x926\x9c\xafR-.O\x1cM\x85;\xd6W\x8fy\xdaOluc\xac\xbc\xeb\x01\xfbO|\xd2\r|\xc7\x00\xd6S%s1\x8c\x8a \xcd\x9c\x1f#\x1c\xe8|`\xa5\xc1\x1c'}, {'revert_on_fail': True}), (<Function V2_SWAP_EXACT_IN(address,uint256,uint256,address[],bool)>, {'recipient': '0x0000000000000000000000000000000000000001', 'amountIn':<PHONE_NUMBER>000000000, 'amountOutMin':<PHONE_NUMBER>00000000000, 'path': ['0x55d398326f99059fF775485246999027B3197955', '0xe9e7CEA3DedcA5984780Bafc599bD69ADd087D56', '0xF700D4c708C2be1463E355F337603183D20E0808'], 'payerIsSender': True}, {'revert_on_fail': True})], 'deadline':<PHONE_NUMBER>})

success transaction without permit2_permit decode data:

(<Function execute(bytes,bytes[],uint256)>, {'commands': b'\x08', 'inputs': [(<Function V2_SWAP_EXACT_IN(address,uint256,uint256,address[],bool)>, {'recipient': '0x0000000000000000000000000000000000000001', 'amountIn':<PHONE_NUMBER>0000000000, 'amountOutMin':<PHONE_NUMBER>00000000000, 'path': ['0x55d398326f99059fF775485246999027B3197955', '0xe9e7CEA3DedcA5984780Bafc599bD69ADd087D56', '0xF700D4c708C2be1463E355F337603183D20E0808'], 'payerIsSender': True}, {'revert_on_fail': True})], 'deadline':<PHONE_NUMBER>})

Hello @freereaper !
Are you sure:

you use the right permit2 nonce?
you have approved the permit2 contract to the token contract?

If yes, can you please share the link to the failing transaction? (one you did not "override" with one from pancake)

Thanks for  your help
Yes, approve the permit2 contract to token contrace is done in the first step:
       contract_function = approve_token_ca.functions.approve(
                permit2_address,
                permit2_allowance
        )

Transaction:
https://bscscan.com/tx/0x186e377e13ff5245c3e4ca5aa66c6558f0313713932f49924b132aca18117677
And this is the one from pancake, sign and swap
https://bscscan.com/tx/0xfa95224b52a245dbe2f4d5414d301f588d43fe7d85b12cb8c3f733608806d66a
I get the permit2 nonce from the below code and use it in the  codec.create_permit2_signable_message.
:
    p2_amount, p2_expiration, p2_nonce = permit2Contract.functions.allowance(
        wallet,
        approve_token,
        UR_ADDRESS
    ).call()

This is the fail one with sign and swap:
https://bscscan.com/tx/0x6ba61492ec778ea39861ebc1dc3a5d75caab8643a4b3013a609c56a810a1d72d

Ok, thanks! I'm a bit busy at the moment, but I'll try to look into it over the week-end.

Thanks , wait for the solution.

Hello, have solved the issue, pancake use different permit2 address.
https://github.com/Elnaril/uniswap-universal-router-decoder/pull/48

Great! Thanks for the PR. Will review it asap.


As a project manager, I need to complete and finalize all user stories, so that the development team has a clear understanding of the project's requirements and tasks.

As a [role]
I need [function]
So that[benefit]
Details and Assumptions
* [document what you know]

Acceptance Criteria
    gherkin
    Given  [some context]
    When  [certain action is taken]
    Then   [the outcome of action is observed]

User Story
As a project manager,
I want to complete and finalize all user stories,
so that the development team has a clear understanding of the project's requirements and tasks.
Acceptance Criteria

[ ] All required user stories are documented
[ ] User stories are clear and detailed
[ ] User stories are reviewed and approved by the team


x/tools: build failing on windows-amd64-longtest

The windows-amd64-longtest builder is failing in numerous ways on x/tools.
Looks like some of the same out-of-memory issues as in #33951, but there may be other failures too.
https://build.golang.org/log/591874cbe6ad7d7b59ad1f9ef2b3d34e81af20a4
CC @ianthehat @matloob @stamblerre

I believe this is a release-blocker via #11811.

I've spun up a bunch of VMs/laptops with Windows 7/10 (WindowsBuild was very helpful), some with 8 GB RAM and one with 16 GB.
8 GB
On 8 GB configurations, I could not get go test -race golang.org/x/tools/... to pass even once, despite multiple attempts and test caching helping out:

All 7-8~ GB RAM were used up during a large portion of the time.
16 GB
With 16 GB, go test -race golang.org/x/tools/... passed on first try.

RAM usage still reached nearly all 15~16 GB RAM used up some of the time.

I've sent CL 213557 which bumps the RAM from 7.2 to 14.4 on windows-amd64-{longtest,race} builders. I think it's a reasonable next step to try, since some other builders already get 16 GB.

The aforementioned change has had an effect. Both windows-amd64-longtest and -race have been passing on x/tools since the builder change was deployed this morning. I'll keep watching a bit more, and then close this issue if the pattern continues.
There have been instances where x/tools has passed on all builders with tip and on release-branch.go1.13:

The freebsd-amd64-race builder still fails due to low memory occasionally, but that's outside of scope of this issue. I'll use issue #34621 to track increasing its memory to match Linux and Windows if needed.

This issue is resolved now, based on the current state of the windows-amd64-longtest column on https://build.golang.org/?repo=golang.org%2Fx%2Ftools:


how configure console routes?

I got this simple module https://github.com/mirkhamidov/yii2-console-dbextend
That module just for console
Adding to console config like
'modules' => [
        'dbex' => 'mirkhamidov\dbex\Module',
    ],

and it appears in console
- dbex/dbex
    dbex/dbex/drop-all-tables  Drop all tables in existing DB

this dbex/dbex confusing me, but it works fine
But how to make it not repeated dbex twice?
for example
- dbex
    dbex/drop-all-tables  Drop all tables in existing DB

@mirkhamidov I guess that's question mainly to developer of https://github.com/mirkhamidov/yii2-console-dbextend

@andrewnester thanks, im developer is myself ;)
Thats why, I cand understand how console routes works.

GitHub is for bug reports. We are happy to help you on support forum or in gitter room https://gitter.im/yiisoft/yii2. It's always better to text there, unless you are sure it is a Yii2 core problem.
However, here are solutions for you:
Option 1
Cheat. Register single controller instead of module:
//    'modules' => [
//        'dbex' => 'mirkhamidov\dbex\Module',
//    ],
    'controllerMap' => [
        'ab' => 'mirkhamidov\dbex\console\controllers\DbexController'
    ],

Option 2
Use bootstrap properly. Your module bootstrapping function will be never called, because you didn't define it nor in the app config, neither in composer.json.
Simplify your bootstrap function:
    public function bootstrap($app)
    {
        if ($app instanceof \yii\console\Application) {
            $app->controllerMap[$this->id] = 'mirkhamidov\dbex\console\controllers\DbexController';
        }
    }

    'bootstrap' => ['log', 'dbex'],
    'modules' => [
        'dbex' => 'mirkhamidov\dbex\Module',
    ],

or
composer.json
    "extra": {
        "bootstrap": "mirkhamidov\\dbex\\Module"
    }


Fix load metadata for docker.synapse.org/syn22277123/physical-address-annotator-example:1.1.2

$ docker compose up
[+] Building 11.0s (21/21) FINISHED
 => [contact-annotator internal] load build definition from Dockerfile                                                             0.0s
 => => transferring dockerfile: 104B                                                                                0.0s
 => [id-annotator internal] load build definition from Dockerfile                                                                  0.0s
 => => transferring dockerfile: 99B                                                                                0.0s
 => [physical-address-annotator internal] load build definition from Dockerfile                                                    0.0s
 => => transferring dockerfile: 113B                                                                                0.0s
 => [phi-deidentifier internal] load build definition from Dockerfile                                                              0.0s
 => => transferring dockerfile: 102B                                                                                0.0s
 => [date-annotator internal] load build definition from Dockerfile                                                                0.0s
 => => transferring dockerfile: 101B                                                                                0.0s
 => [nginx internal] load build definition from Dockerfile                                                                         0.1s
 => => transferring dockerfile: 61B                                                                                0.0s
 => [person-name-annotator internal] load build definition from Dockerfile                                                         0.1s
 => => transferring dockerfile: 108B                                                                                0.0s
 => [contact-annotator internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [id-annotator internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [physical-address-annotator internal] load .dockerignore                                                                       0.0s
 => => transferring context: 2B                                                                                0.0s
 => [phi-deidentifier internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [date-annotator internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [nginx internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [person-name-annotator internal] load .dockerignore                                                                            0.0s
 => => transferring context: 2B                                                                                0.0s
 => CANCELED [contact-annotator internal] load metadata for docker.synapse.org/syn22277123/contact-annotator-example:1.1.2        10.4s
 => CANCELED [id-annotator internal] load metadata for docker.synapse.org/syn22277123/id-annotator-example:1.1.2                  10.4s
 => ERROR [physical-address-annotator internal] load metadata for docker.synapse.org/syn22277123/physical-address-annotator-exam  10.4s
 => CANCELED [phi-deidentifier internal] load metadata for docker.synapse.org/syn22277123/phi-deidentifier-example:edge           10.3s
 => CANCELED [date-annotator internal] load metadata for docker.synapse.org/syn22277123/date-annotator-example:1.1.2              10.3s
 => CANCELED [nginx internal] load metadata for docker.io/library/nginx:1.19.6-alpine                                             10.3s
 => CANCELED [person-name-annotator internal] load metadata for docker.synapse.org/syn22277123/person-name-annotator-example:1.1  10.3s
------
 > [physical-address-annotator internal] load metadata for docker.synapse.org/syn22277123/physical-address-annotator-example:1.1.2:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

Solved after cleaning up containers / images / networks


Updated Readme added Badges

please add hacktoberfest acceptedd tag, help me making it count.

Thank you for your contribution.
Happy HacktoberFest!


Consider switching from lxml's clean_html for enhanced security (and possibly performance)

I'd like to bring to your attention that we are discussing the possibility of removing lxml's clean_html functionality from lxml library. Over the past years, there have been several concerning security vulnerabilities discovered within the lxml library's clean_html functionality – CVE-2021-43818, CVE-2021-28957, CVE-2020-27783, CVE-2018-19787 and CVE-2014-3146.
The main problem is in the design. Because the lxml's clean_html functionality is based on a blocklist, it's hard to keep it up to date with all new possibilities in HTML and JS.
Two viable alternatives worth considering are bleach and nh3. Here's why:
bleach:

Bleach is a widely adopted Python library specifically designed for sanitizing and cleaning HTML input.
It has a strong track record in terms of security – it's allowed-list-based.
It was deprecated in January but it will still receive security updates, support for new Pythons and bugfixes, see upstream issue.

nh3:

nh3 is Python binding for the ammonia library. Ammonia is written in Rust and it's also allowed-list-based.
Thanks to the Rust backend, nh3 is also significantly faster than bleach.
Rust backend is nothing to be afraid of. nh3 uses the latest PyO3 compatible with Python 3.12 and provides wheels built on top of compatible ABI for different architectures and platforms.

We'll probably move the cleaning part of the lxml to a distinct project first so it will still be possible to use it but better is to find a suitable alternative sooner rather than later.
Let me know if we can help you with this transition anyhow and have a nice day.

Just an update on this. The latest version of lxml (5.2.0) no longer contains the HTML cleaner. Its code is now available as a dedicated project on GitHub and PyPI.
If you want to continue using it, you can either depend on lxml[html_clean] or on lxml_html_clean directly. lxml contains backward-compatible import so there is nothing else you need to change than the dependency.

The UX for this project is currently broken due to dependency on legacy lxml.
Doing this on a Mac makes it work seamlessly:

brew install libxml2
brew install libxslt

But your production environment is probably not Mac, which means there's some annoying Linux ops work in your future.
Last commit to main branch was 4 years ago, so I imagine people have moved on to a different library?


Dev

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 50.96%. Comparing base (a2727c6) to head (4cc8849).
Report is 6 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   50.96%   50.96%
=======================================
  Files          17       17
  Lines         259      259
  Branches       56       56
=======================================
  Hits          132      132
  Misses        127      127

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


Undefined 'url' when trying to play blocked video

Error occurs when trying to play a video that is blocked in my country
Example used: https://www.youtube.com/watch?v=0WV-MV18JCU
I believe it should have properly thrown an error saying the video is blocked instead of hanging
Tested on Node.js v12.16.1 with master branch
(node:12376) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'url' of undefined
    at /Users/eritislami/evobot/node_modules/ytdl-core-discord/index.js:40:41
    at /Users/eritislami/evobot/node_modules/ytdl-core-discord/node_modules/ytdl-core/lib/info.js:288:23
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:12376) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:12376) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

In the same environment & test<EMAIL_ADDRESS>properly rejects with 'Video unavailable'
Error: input stream: Video unavailable
    at Object.exports.playError (/Users/eritislami/evobot/node_modules/ytdl-core/lib/util.js:441:12)
    at downloadFromInfoCallback (/Users/eritislami/evobot/node_modules/ytdl-core/lib/index.js:57:18)
    at /Users/eritislami/evobot/node_modules/ytdl-core/lib/index.js:18:5
    at processTicksAndRejections (internal/process/task_queues.js:97:5)


implement mulx based tests as mentioned in ietf spec appx A

This one should be closed by now i think

i meant that we could try implementing polyval in terms of the mul-x and reverse bytes, which is not yet implemented, sorry for not being clearer. See appx a; this is at best supplementary testing and low priority.

name: implement ghash using mul-x and byte reversal
about: implement alternative version of ghash using mul-x and byte reversal as described in appendix A of the IETF AES-GCM implementation
title: implement ghash using mul-x and byte reversal
labels: Bounty 💰
assignees:

Bounty description
Implement an alternative version of GHASH using the mul-x operation and byte reversal as described in Appendix A of the IETF AES-GCM spec. This implementation will be used for supplementary testing to validate the existing GHASH implementation in the AES-proof repo.
Implementation requirements

[ ] Implement ByteReverse function
[ ] Implement mulX_GHASH function
[ ] Implement mulX_POLYVAL function
[ ] Implement GHASH in terms of POLYVAL using spec
[ ] Create unit tests to verify correctness of the implementation, using test vectors from IETF spec
[ ] Document implementation

Bonus features

[ ] Implement performance benchmarks to compare existing implementation with this one

Resources
AES-GCM-SIV IETF Draft (Appendix A)
NIST SP 800-38D (GCM)
Criteria
Bounties will be rewarded based on the following criteria:

Correctness and security: A thorough review of the implementation should convince our team that they are correct and secure, with all requirements met.
Code clarity and quality: Succinct, easy-to-follow code with appropriate naming conventions. Utilize Rust’s type system for flexibility and security (e.g., compile-time checks where possible), and avoid external crates. Optimizations should be a lower priority than clarity, but can be included behind a feature flag as a bonus.
Documentation quality: Provide comprehensive README’s, Cargo docs, and inline comments where code itself is not self-explanatory. Prioritize clarity and readability.

@thor314  this is my attempt at turning this into a proper bounty, please provide feedback or update the issue with this if appropriate!
cc: @Autoparallel + @0xJepsen

@brunny-eth this one thor and i are working on so i am not sure it's well suited for a bounty mainly because we have already invested a good amount of time into it ourselves

ok cool, no problem at all. can you call out 1-3 others in this repo that might make sense to have as issues for contributors instead?


allow configure timezone in dashboards

Currently timezone selector is hardcoded to utc. Please consider adding a parameter to be able to select different timezone or browser. Local customization gets overridden by puppet

I am experiencing the same issue.


fix: "dependency_version_2": true

Description
Explicitly setting "dependency_version_2": true so the UI renders dependencies better in the tile
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

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

GitHub release
v1.24.2

Your semantic-release bot :package::rocket:


Ensure that the language used in this repo is consistent with final NeuroBench paper

Ensure that the language used in this repo is consistent with final NeuroBench paper, once it has been published

Also to add the fixed-timeout benchmark specification into the QUBO document

Remove the validation set from ASC task, it is a subset of the test set.

#12


Redesigning About us page

Redesigning About us page

we'll redesign this page later on...if you want to work on this issue then discuss in meeting then start working on it

Share the current changes in discord when you mak

sure


Doc: Provide example of building image

I'm trying to build and I'm not getting reproducible images. This is the buildx command I'm using:
docker buildx build -o type=oci,dest=image.img,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 .

Could there be an example buildx invocation in the README to help someone use this strategy?

I'm not getting reproducible images

What's non-reproducible?

Here is my console output:
➜  repro-sources-list.sh git:(master) ✗ docker buildx build -o type=oci,dest=image.img,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 .

[+] Building 97.3s (8/8) FINISHED                                             docker-container:multiarch2
 => [internal] load build definition from Dockerfile.debian-12                                       0.0s
 => => transferring dockerfile: 416B                                                                 0.0s
 => [internal] load metadata for docker.io/library/debian:bookworm-20230904-slim                     1.3s
 => [auth] library/debian:pull token for registry-1.docker.io                                        0.0s
 => [internal] load .dockerignore                                                                    0.0s
 => => transferring context: 2B                                                                      0.0s
 => [internal] load build context                                                                    0.0s
 => => transferring context: 43B                                                                     0.0s
 => CACHED [stage-0 1/2] FROM docker.io/library/debian:bookworm-20230904-slim@sha256:050f00e86cc4d9  0.0s
 => => resolve docker.io/library/debian:bookworm-20230904-slim@sha256:050f00e86cc4d928b21de66096126  0.0s
 => [stage-0 2/2] RUN   --mount=type=cache,target=/var/cache/apt,sharing=locked   --mount=type=cac  81.8s
 => exporting to oci image format                                                                   14.1s
 => => exporting layers                                                                              6.5s
 => => rewriting layers with source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC)            6.9s
 => => exporting manifest sha256:d6997b9712dcae63aa13aba30a08fab9a18d7a65981d921fcb91c296eec8359e    0.0s
 => => exporting config sha256:3fae53ed7a611e1ad0f533e234cc89a7238276f8bc766bac496111a1d65da272      0.0s
 => => sending tarball                                                                               0.8s
➜  repro-sources-list.sh git:(master) ✗ docker buildx build -o type=oci,dest=image2.img,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 .

[+] Building 89.6s (7/7) FINISHED                                             docker-container:multiarch2
 => [internal] load build definition from Dockerfile.debian-12                                       0.0s
 => => transferring dockerfile: 416B                                                                 0.0s
 => [internal] load metadata for docker.io/library/debian:bookworm-20230904-slim                     0.5s
 => [internal] load .dockerignore                                                                    0.0s
 => => transferring context: 2B                                                                      0.0s
 => [internal] load build context                                                                    0.0s
 => => transferring context: 43B                                                                     0.0s
 => CACHED [stage-0 1/2] FROM docker.io/library/debian:bookworm-20230904-slim@sha256:050f00e86cc4d9  0.0s
 => => resolve docker.io/library/debian:bookworm-20230904-slim@sha256:050f00e86cc4d928b21de66096126  0.0s
 => [stage-0 2/2] RUN   --mount=type=cache,target=/var/cache/apt,sharing=locked   --mount=type=cac  74.9s
 => exporting to oci image format                                                                   14.2s
 => => exporting layers                                                                              6.5s
 => => rewriting layers with source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC)            6.8s
 => => exporting manifest sha256:f3f7ebaa5cd2498431d4c1cc275e3ecc7490a0f77743e7b02d7bf787d45faf6c    0.0s
 => => exporting config sha256:2b0a504fbecbdce0009173ef63d3db74df58800aaab8aaf44c3fd50608c0b2f1      0.0s
 => => sending tarball                                                                               0.8s
➜  repro-sources-list.sh git:(master) ✗ sha256sum image.img
2001dd290e510347e01bc04a03e2b73b842cda6256418fb44fc802284a562843  image.img
➜  repro-sources-list.sh git:(master) ✗ sha256sum image2.img
\2fa5d75d6665dad76924ca277ccf3543be5c94f071e12cc78e9ecdc27f7f1316  image2.img

Manfest, config and actual image files have different hashes with two back to back runs on the same machine.
Do you have an example buildx command where they come out the same?

The differences are caused by:

var/cache/ldconfig/aux-cache
var/log/alternatives.log
var/log/apt/history.log
var/log/apt/term.log

You may just remove them with RUN rm -f.
Full example:

https://github.com/docker-library/httpd/pull/248

See also

https://github.com/docker-library/official-images/issues/16044

@AkihiroSuda I'm not sure if this is the place to talk about this but you seem like the most knowledgeable person on this process.
With the changes made in #16 I now have a reproducible build for linux/amd64 and the same dockerfile for linux/arm64 but when I tell buildx to make both into a multi-arch image for some reason the output is different even though the two separate arches are reproducible when built alone. Where is the right place to raise this?
This was my command:
docker buildx build -o type=oci,dest=image.img,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64,linux/arm64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 .

Interestingly, I'm building on two different machines and comparing the output. One is an amd64, and one is arm64. They both produce the same output (when producing a single arch image) even though obviously each time for one of them it's a non-native build.

You may use https://github.com/reproducible-containers/diffoci to check the diff.
It should be noted that the scope of repro build is limited to manifests, not indexes, as an index may contain references to SPDX provenances, etc.

Thanks for the tool @AkihiroSuda!
Output of diffoci:
DebainBuild ➜  repro-sources-list.sh git:(master) ✗ ./diffoci-v0.1.4.linux-amd64 diff docker://maxedw/image1 docker://maxedw/image2
INFO[0000] Target platforms: [linux/amd64]
INFO[0000] Loading image "docker.io/maxedw/image1:latest" from "docker"
docker.io/maxedw/image1:latest          	saved
Importing	elapsed: 0.8 s	total:   0.0 B	(0.0 B/s)
INFO[0001] Loading image "docker.io/maxedw/image2:latest" from "docker"
docker.io/maxedw/image2:latest          	saved
Importing	elapsed: 0.8 s	total:   0.0 B	(0.0 B/s)
TYPE     NAME                                                                             INPUT-0                                                                                INPUT-1
Desc     application/vnd.oci.image.manifest.v1+json                                       fd5379d8878302e938698586db3869b25bbb0bca1030eb48835bd84a47187b6d                                                1ea38231b7eea6d91ac8bd96602b30aafd6e6c88f25b5e514f420be676a421d0
Desc     application/vnd.oci.image.manifest.v1+json                                       fd5379d8878302e938698586db3869b25bbb0bca1030eb48835bd84a47187b6d                                                1ea38231b7eea6d91ac8bd96602b30aafd6e6c88f25b5e514f420be676a421d0
Mani     ctx:/manifest                                                                    ?                                                                                ?
Desc     application/vnd.oci.image.config.v1+json                                         0611c3c137f98c0f4990d26f57a8edaa156fc4be613cfd34811356dee03c3dfe                                                1ba11898aa9b6d3e579bb6a5b51c82b1e2dade40fc1c834164a4ae09fda879ef
Cfg      ctx:/config/config                                                               ?                                                                                ?
Desc     application/vnd.oci.image.layer.v1.tar                                           cf3420c34116c7777c0660d1e99d477bb48d347fa660da216867ccbdee7fd02c                                                f02cc727caf22e74251fcdec0164e1e6b78e87b2edbedccac4b2ca975a73af65
File     blobs/sha256/155eab17d86c47443adc8cebe7fc62c847c03db8cfb1ca53aa6276564fff23ef    Index 3                                                                                Index 4
File     blobs/sha256/d2c7ba5b367ab427569aa8e0f6551a224ee6b1b31cc585b3625fb676355666af    Index 13                                                                                Index 12
File     blobs/sha256/d5a1697de149c4584e824aed15ffe82412466e700f7a1c15451b255cd8a79511    Index 14                                                                                Index 13
File     blobs/sha256/ee6efcfa9510fa714668f0a2f00b256cfcaa3538c1108a42e36e32ea6faf12ec    Index 15                                                                                Index 14
File     blobs/sha256/1f2a5c5f21abf788427963c515a0b60359ebc0b594789f425428a6b8cf97eda9    Index 4                                                                                Index 5
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/2ee6937ec697a293be718f27df65fc665d355f2edede02fa0a071b43f8089302" only appears in input 0
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/47f94f0e4dda0e127756f9aa48541b15e140b923ceddcc9c8e2597e40779fd80" only appears in input 0
File     blobs/sha256/0b9622d7cd405af087a352f882207fa2e54e85988bb395956840c3a13afcf21d    Index 2                                                                                Index 3
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/a44de156a7f46cac4ae15feb3e8e2d3127b9b6349761089b2f0f9bcf43e62bd5" only appears in input 0
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/8abb5ebae0c47c283756a9de0ca2b2287a7563e935b2162a57ea7c6651107774" only appears in input 0
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/94f26548633ca6e1b1af4486913c750c5628c79179b2a3cc67443a9bef6b625b" only appears in input 0
File     index.json                                                                       c9549cee48733bf4aa5ad635a19113f925a3b0508061af409adf017ac50d387c                                                d3b66896f36f0645af0086ac1beeab1a648b3c79e823e7eeaafb607c5d4aa537
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/33bf26bf869c7497c4ffdde1842fc76d1fc8db78cc2103395d37d59c85c61392" only appears in input 0
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/5abc1189feeab99aad971fdae2a199a70e559b440a119ba3b9a928e7db746b55" only appears in input 0
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/ae656186cf62c3ffff1f3ffaff1e569e92c8f79302e333fa9a4ff14e6570fd43" only appears in input 1
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/d22f304ed9b9719867ebdab1f6a4fce6a8b4d14e66a241dff3a1d4b4e7d297fe" only appears in input 1
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/0b8418c757238f8c0bebdf63724fa00c36d3ecb1b7eb866780364a56f982f7de" only appears in input 1
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/27153e7f7ca35cfe83c9e6ed9b12b32dbcac84c613776d3ea34ef9d4fcc0ef86" only appears in input 1
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/c3eebf09ec733b8f01c4d3db506b42fd66331fe157335faa34a94e3c95c436ee" only appears in input 1
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/acf1548d261354d48be809a35ae2e8730a178866adbdf0b32d98d7010e3148b0" only appears in input 1
Layer    ctx:/layers-0/layer                                                              name "blobs/sha256/ee87862996bc639ac76fd54dfd0778c97a44bbd2efb2184a1c3957bf198bc6be" only appears in input 1

Don't fully follow what the doffoci is telling me here but shall I just assume that it's currently not possible to make reproducible multi-arch images?

Don't fully follow what the doffoci is telling me here but shall I just assume that it's currently not possible to make reproducible multi-arch images?

Possible, but you may have to specify registry reference stringss rather than docker:// strings.

This is the result I got (repro-sources-list.sh v0.1.3, buildx v0.14.0, BuildKit v0.13.1):
$ docker buildx build -o type=image,name=docker.io/akihirosuda/tmp20240424:0,push=true,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64,linux/arm64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 .
[...]
 => exporting to image                                                                                61.9s
 => => exporting layers                                                                                12.9s
 => => rewriting layers with source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC)                                                                                10.8s
 => => exporting manifest sha256:efbda9bc79ec583cd48edd015ace1f05a5807e27477f868add652e6d64dc6f20                                                                                0.0s
 => => exporting config sha256:d5a1697de149c4584e824aed15ffe82412466e700f7a1c15451b255cd8a79511                                                                                0.0s
 => => exporting attestation manifest sha256:4e97c4b92482f5798563eb0294eddbd3d991573726261e4dfc3230c21db58fee                                                                                0.0s
 => => exporting manifest sha256:1f2a5c5f21abf788427963c515a0b60359ebc0b594789f425428a6b8cf97eda9                                                                                0.0s
 => => exporting config sha256:ee6efcfa9510fa714668f0a2f00b256cfcaa3538c1108a42e36e32ea6faf12ec                                                                                0.0s
 => => exporting attestation manifest sha256:c94dde3b8ce891dfca5ad673b253d04ebe48cc9246e3415e9a89d45fd3cfb267                                                                                0.0s
 => => exporting manifest list sha256:787688757b1caad6539976fd5a64dc50416b24505d40f01e6d034b70341f4d98                                                                                0.0s
 => => pushing layers                                                                                19.9s
 => => pushing manifest for docker.io/akihirosuda/tmp20240424:0@sha256:787688757b1caad6539976fd5a64dc50416b24505d40f01e6d034b70341f4d98                                                             4.5s
 => [auth] akihirosuda/tmp20240424:pull,push token for registry-1.docker.io                                                                                0.0s

$ docker buildx build -o type=image,name=docker.io/akihirosuda/tmp20240424:1,push=true,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64,linux/arm64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 .
[...]
 => exporting to image                                                                                51.4s
 => => exporting layers                                                                                12.7s
 => => rewriting layers with source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC)                                                                                13.7s
 => => exporting manifest sha256:efbda9bc79ec583cd48edd015ace1f05a5807e27477f868add652e6d64dc6f20                                                                                0.0s
 => => exporting config sha256:d5a1697de149c4584e824aed15ffe82412466e700f7a1c15451b255cd8a79511                                                                                0.0s
 => => exporting attestation manifest sha256:64aa10db60f094ade29be8c949c83e012a35f140e7f8da6ea9f3beef869e73d6                                                                                0.0s
 => => exporting manifest sha256:1f2a5c5f21abf788427963c515a0b60359ebc0b594789f425428a6b8cf97eda9                                                                                0.0s
 => => exporting config sha256:ee6efcfa9510fa714668f0a2f00b256cfcaa3538c1108a42e36e32ea6faf12ec                                                                                0.0s
 => => exporting attestation manifest sha256:6c0dc5e87e4e5a0434c000d524d6f06b7ad3d5e5ae4196a99574beea6da34731                                                                                0.0s
 => => exporting manifest list sha256:71b28118565e07eece365aabaa6b40d3acdc2eb210c57c22a62addc9c4586189                                                                                0.0s
 => => pushing layers                                                                                5.3s
 => => pushing manifest for docker.io/akihirosuda/tmp20240424:1@sha256:71b28118565e07eece365aabaa6b40d3acdc2eb210c57c22a62addc9c4586189                                                             4.9s
 => [auth] akihirosuda/tmp20240424:pull,push token for registry-1.docker.io

While the digest of the manifest list (aka OCI index) is not reproducible as it contains the attestation manifest (SLSA provenance), the image manifests themselves are 100% reproducible:

manifest sha256:efbda9bc79ec583cd48edd015ace1f05a5807e27477f868add652e6d64dc6f2 (amd64)
manifest sha256:1f2a5c5f21abf788427963c515a0b60359ebc0b594789f425428a6b8cf97eda9 (arm64)

See https://explore.ggcr.dev/?image=docker.io%2Fakihirosuda%2Ftmp20240424%3A0 and https://explore.ggcr.dev/?image=docker.io%2Fakihirosuda%2Ftmp20240424%3A1

@AkihiroSuda I truly appreciate you taking the time to run those examples for me!

The manifest list (index) can be made reproducible too by specifying --provenance=false
$ docker buildx build -o type=image,name=docker.io/akihirosuda/tmp20240424:no-provenance-0,push=true,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64,linux/arm64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 --provenance=false .
[...]
 => exporting to image                                                                                46.8s
 => => exporting layers                                                                                14.1s
 => => rewriting layers with source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC)                                                                                11.7s
 => => exporting manifest sha256:9959b500c85383c0c534d67d4411b98e4031db54d629f28cfef0a945d7dfdd09                                                                                0.0s
 => => exporting config sha256:d5a1697de149c4584e824aed15ffe82412466e700f7a1c15451b255cd8a79511                                                                                0.0s
 => => exporting manifest sha256:c463b35ef852663064a67fe055b59df86991403275de7da113f4eaa5cdc50e26                                                                                0.0s
 => => exporting config sha256:ee6efcfa9510fa714668f0a2f00b256cfcaa3538c1108a42e36e32ea6faf12ec                                                                                0.0s
 => => exporting manifest list sha256:13954d9f9d01070d648d2e00b15d152fcb58ecf4a93fac1cde89672c61fb0e7e                                                                                0.0s
 => => pushing layers                                                                                2.4s
 => => pushing manifest for docker.io/akihirosuda/tmp20240424:no-provenance-0@sha256:13954d9f9d01070d648d2e00b15d152fcb58ecf4a93fac1cde89672c61fb0e7e                                               3.9s
 => [auth] akihirosuda/tmp20240424:pull,push token for registry-1.docker.io                                                                                0.0s

$ docker buildx build -o type=image,name=docker.io/akihirosuda/tmp20240424:no-provenance-1,push=true,rewrite-timestamp=true -f Dockerfile.debian-12 --platform linux/amd64,linux/arm64 --no-cache --build-arg SOURCE_DATE_EPOCH=1675298208 --provenance=false .
[...]
 => exporting to image                                                                                45.0s
 => => exporting layers                                                                                13.5s
 => => rewriting layers with source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC)                                                                                11.2s
 => => exporting manifest sha256:9959b500c85383c0c534d67d4411b98e4031db54d629f28cfef0a945d7dfdd09                                                                                0.0s
 => => exporting config sha256:d5a1697de149c4584e824aed15ffe82412466e700f7a1c15451b255cd8a79511                                                                                0.0s
 => => exporting manifest sha256:c463b35ef852663064a67fe055b59df86991403275de7da113f4eaa5cdc50e26                                                                                0.0s
 => => exporting config sha256:ee6efcfa9510fa714668f0a2f00b256cfcaa3538c1108a42e36e32ea6faf12ec                                                                                0.0s
 => => exporting manifest list sha256:13954d9f9d01070d648d2e00b15d152fcb58ecf4a93fac1cde89672c61fb0e7e                                                                                0.0s
 => => pushing layers                                                                                2.5s
 => => pushing manifest for docker.io/akihirosuda/tmp20240424:no-provenance-1@sha256:13954d9f9d01070d648d2e00b15d152fcb58ecf4a93fac1cde89672c61fb0e7e                                               1.6s
 => [auth] akihirosuda/tmp20240424:pull,push token for registry-1.docker.io

BTW source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC) isn't legit for a Dockerfile with FROM debian:bookworm-20230904-slim, and the value was not consumed due to lack of ARG SOURCE_DATE_EPOCH in the Dockerfile

The manifest list (index) can be made reproducible too by specifying --provenance=false

Amazing!

BTW source-date-epoch<PHONE_NUMBER> (2023-02-02 00:36:48 +0000 UTC) isn't legit for a Dockerfile with FROM debian:bookworm-20230904-slim, and the value was not consumed due to lack of ARG SOURCE_DATE_EPOCH in the Dockerfile

Great catch


[Bug] FlinkTrackController's trackIds, canceling, endpoints, jobStatuses uniformly use appId as Key

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
FlinkTrackController's trackIds, canceling, endpoints, jobStatuses uniformly use appId as Key.
FlinkTrackController

trackIds,canceling use appId as key

endpoints,jobStatuses use TrackId as key

StreamPark Version
1.2.4-SNAPSHOT
Java Version
No response
Flink Version
1.14.5
Scala Version of Flink
2.12
Error Exception
Only one job is run, and the size of the jobStatuses cache is 2

To explain its impact, `FlinkJobStatusWatcher.touchApplicationJob()`  When jobDetails.isEmpty || jobDetails.get.jobs.isEmpty condition is true, inferApplicationFlinkJobStateFromK8sEvent() will change from
`val latest: JobStatusCV = trackController.jobStatuses.get(trackId)`
...

Screenshots

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Thanks for your feedback, really a bug. welcome to fix it.


Range slider control

This request covers the addition of a range slider control. As an example of a use for this is when creating a video trimming application.

Added as part of commit 6da975a.
Can be used for a variety of applications. Currently used in a media editing application I've written.
Will be made publicly available in next NuGet release.


flocker-deploy and "ERROR: Wrong number of arguments"

I'm following the tutorial and when attempting to run flocker-deploy, I get the error above (ERROR: Wrong number of arguments).  I'm running inside vagrant on OSX.
# flocker-deploy --version
0.4.0-1609-ge38e701

# flocker-deploy deployment-node1.yml fig.yml
Usage: flocker-deploy [OPTIONS] <control-host> <deployment.yml-path> <application.yml-path>

If you have any issues or feedback, you can talk to us:         https://docs.clusterhq.com/en/latest/gettinginvolved/contributing.html#talk-to-us
Options:
  -p, --port=    The REST API port on the server. [default: 4523]
      --version  Print the program's version and exit.
  -v, --verbose  Turn on verbose logging.
      --help     Display this help and exit.

flocker-deploy allows you to configure existing nodes.
ERROR: Wrong number of arguments.`

Any ideas?
Thanks.

Hi,
It looks like you're using an unreleased version of Flocker - did you intend to do that?  For such versions, the docs on the website won't necessarily be correct.  If you're really interested in the latest bleeding edge version of Flocker, you can try looking at https://doc-dev.clusterhq.com/ instead.  Those instructions are more likely to be correct for the version of Flocker you have (but they still may not quite match up).
If you're just trying out Flocker, I recommend sticking to the latest release - 0.4.0 - things should go more smoothly.
The particular issue you've run in to is that we've introduced a new required argument to flocker-deploy - the address of a control service which coordinates activity on a Flocker cluster.  If you want to continue using the version of Flocker you have, you'll also have to set up a control service and then supply its attribute to flocker-deploy.
If you didn't intentionally install an unreleased version of Flocker, I wonder if you could describe how you went about installing Flocker so we can figure out why you didn't end up with a released version instead.
Thanks for your interest!  Looking forward to hearing more details about your experience.

Thanks - I copied and pasted the brew install instructions from the tutorial.  From my history:
brew update &&  brew tap clusterhq/flocker &&  brew install flocker-0.4.0
Thanks - Matt

Thanks Matt,
Unfortunately I caused this issue earlier today and we have just fixed it. Thank you very much for making us aware, it should be fixed now. You will have to uninstall the testing version of Flocker which you installed first and update. I think that this will be:
brew uninstall flocker-0.4.0
brew update
brew install flocker-0.4.0

Adam

Just to follow up from Adam and say thanks very much for pointing out this error, @msbritt :) It should be fixed now, and it would be great if you could try again as per Adam's instructions.
If this works for you, let us know and we'll close the issue.
Have fun with Flocker! I'm curious: what are you thinking about using it for?
Cheers,
Luke

Fantastic - thank you Adam.  That problem is solved and I was able to run
the demo.  fwiw, to whoever wrote the tutorial, it was really well done,
both in creating a problem which depicts what Flocker can solve (no easy
feat) as well as being well written and easy to follow.
Luke - I have two projects.  One is our production ELK, Redis, and Graphite
deployments.    The other is a proof-of-concept to deploy example HPC
environments to assist in debugging resource management and scheduling
issues.  We not infrequently come across issues which are difficult to
explain, but w/ Dockerized environment (made much easier via Flocker), we
can build and script a scenario and (hopefully) easily show behaviors and
then send that environment to the developer so they can view and more
easily find the cause.
Thanks again for all of your help!

Matthew Britt
Advanced Research Computing - Technology Services
<EMAIL_ADDRESS>On Thu, May 7, 2015 at 6:32 PM, lukemarsden<EMAIL_ADDRESS>wrote:

Just to follow up from Adam and say thanks very much for pointing out this
error, @msbritt https://github.com/msbritt :) It should be fixed now,
and it would be great if you could try again as per Adam's instructions.
If this works for you, let us know and we'll close the issue.
Have fun with Flocker! I'm curious: what are you thinking about using it
for?
Cheers,
Luke
—
Reply to this email directly or view it on GitHub
https://github.com/ClusterHQ/flocker/issues/1384#issuecomment-100038633.

No problem at all. I'm closing this now but feel free to re-open it or create new ones if you get stuck or want any feature requests.
If you would like more in depth examples of the kinds of problems Flocker can solve and what it can do, you might want to take a look at our in depth tutorial and examples at https://docs.clusterhq.com/en/0.4.0/indepth/index.html. This goes further than the quick tutorial you followed.
In particular we have an example about linking containers with Flocker and this describes a simple setup of ELK where the the logging data can be moved across nodes - https://docs.clusterhq.com/en/0.4.0/indepth/examples/linking.html.
Adam


header can't really hidden in version 0.2.8

when i use v0.2.8 and when i scrolling the recyclerview, the header of  which item will attach the top is showing,  the word(A,B,C,D...) will changing still.
but when i change to v0.2.6, this problem disappeared。

I don't quite understand the issue you're describing. Can you provide a screenshot and/or some sample code to help debug the problem?


TypeError: cluster.queue is not a function

I am trying to define a function in a cluster queue method following the NPM example but no matter what I do I get the titled type error. Here is an example of what I am trying to do:
(async () => {
  const cluster = Cluster.launch({
    concurrency: Cluster.CONCURRENCY_BROWSER,
    maxConcurrency: 3,
  });

  cluster.queue(async ({ page }) => {
    let i = 0;
    for (i = 0; i < 5; i++) {
      await page.goto('https://google.com/');
      await page.waitFor(500);
      await page.screenshot();
      await page.waitFor(500);
      console.log(`Finished ${i} runs of task.`);
    }
  });

I forgot the await keyword before Cluster.launch. Closing now


remove unused variables

Codecov Report

Merging #544 into master will not change coverage.
The diff coverage is 90.9%.

@@          Coverage Diff           @@
##           master    #544   +/-   ##
======================================
  Coverage    92.8%   92.8%
======================================
  Files          36      36
  Lines        2876    2876
======================================
  Hits         2669    2669
  Misses        207     207

Impacted Files
Coverage Δ

vent/menus/main.py
76.36% <ø> (ø)
:arrow_up:

vent/api/actions.py
93.99% <100%> (ø)
:arrow_up:

vent/helpers/meta.py
89.1% <100%> (ø)
:arrow_up:

vent/core/file-drop/file_drop.py
100% <100%> (ø)
:arrow_up:

vent/core/rmq-es-connector/rmq_es_connector.py
100% <100%> (ø)
:arrow_up:

vent/core/rq-worker/file_watch.py
88.09% <100%> (ø)
:arrow_up:

vent/api/plugins.py
92.08% <80%> (ø)
:arrow_up:

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 385ac67...24ee0d9. Read the comment docs.


Troubleshooting tips for slow Brooklyn

Very useful and extensive.

Thanks - I've incorporated those comments; merging now.


Connect to AWS RDS with aws-sdk client

I see that the migration requires a PostgreSQL client to handle the database calls. Would it be possible to extend the library to use the aws ask client to connect to an Aurora Serverless V1 database? This would make configuring a VPC, or opening the database up to the public obsolete and greatly reduce complexity in using node-pg-migrate to manage migrations on Aurora Serverless clusters on AWS.

I think you are describing a very specific use-case.
You need to use AWS CDK to manage infrastructure and deploy AWS RDS Aurora instance with CDK.
Then you can add to CDK outputs the newly deployed RDS URL and port. Or you can find them in AWS console.
Use these to set DATABASE_URL env variable as in this package readme.

I got it working with node-pg-migrate. Just would want to be able to do it without having to use a VPC ;)

@sthuber90 you can use https://github.com/marcgreenstock/data-api-suite
It has a pretty good migration tool.


Error with conda.py

Hi! First of all, thanks for this great job.
 The problem is that sometimes object becomes a dict object. In thos case I solved the problem with this
if isinstance(other, dict):
    pname = other.get('name', '')
    pversion = other.get('version', '')
else:
    pname, pversion, pdist = other.rsplit('-', 2)

I have seen this error but found it to be transient (??!) and not often repeatable.

This error was no transient to me, It have been appearing many times while I was testing this package.

the error repeats here as well.
NB: when I was installing deploy.xml on Ubuntu 14 all passed smoothly, but for Ubuntu 16.04.2 the error showed up (default python 3.5.2)
The fix by @zodiacfireworks has sovled the issue, thanks!


EC:1.14.12 is being used as an xref in multiple enzyme activities

These appear to be coming in via UM-BBD_reactionIDs.
The term EC:1.14.12 appears to be a very generic term, much like a EC:1.14.12.-
There are around 30 terms with EC:1.14.12 as an xref.
There are EC:<IP_ADDRESS>, EC:<IP_ADDRESS>; these are unique. No problem.
Concern: aren't xrefs suppose to be unique?

I'll check these to see if EC2GO maps these to multiple terms

So looking at the ec2go file; as expected, this is mapping to all children of EC:1.14.12
So these are just like if we did EC:1.14.12.- as an xref
EC:1.14.12 > GO:oxidoreductase activity, acting on paired donors, with incorporation or reduction of molecular oxygen, NAD(P)H as one donor, and incorporation of two atoms of oxygen into one donor ; GO:0016708
EC:1.14.12 > GO:nitrobenzene 1,2-dioxygenase activity ; GO:0018603
EC:1.14.12 > GO:4-aminobenzoate 3,4-dioxygenase (deaminating) activity ; GO:0018604
EC:1.14.12 > GO:benzenesulfonate dioxygenase activity ; GO:0018606
EC:1.14.12 > GO:1-indanone monooxygenase activity ; GO:0018607
EC:1.14.12 > GO:1-indanone dioxygenase activity ; GO:0018608
EC:1.14.12 > GO:chlorobenzene dioxygenase activity ; GO:0018609
EC:1.14.12 > GO:dibenzofuran 4,4a-dioxygenase activity ; GO:0018610
EC:1.14.12 > GO:toluate dioxygenase activity ; GO:0018611
EC:1.14.12 > GO:dibenzothiophene dioxygenase activity ; GO:0018612
EC:1.14.12 > GO:9-fluorenone dioxygenase activity ; GO:0018613
EC:1.14.12 > GO:ethylbenzene dioxygenase activity ; GO:0018614
EC:1.14.12 > GO:2-indanone monooxygenase activity ; GO:0018615
EC:1.14.12 > GO:trihydroxytoluene dioxygenase activity ; GO:0018616
EC:1.14.12 > GO:4-aminobenzenesulfonate 3,4-dioxygenase (deaminating) activity ; GO:0018617
EC:1.14.12 > GO:1-naphthoic acid dioxygenase activity ; GO:0034521
EC:1.14.12 > GO:tetralin ring-hydroxylating dioxygenase activity ; GO:0034825
EC:1.14.12 > GO:N-isopropylaniline 1,2-dixoxygenase activity ; GO:0034906
EC:1.14.12 > GO:acetanilide 1,2-dioxygenase activity ; GO:0034907
EC:1.14.12 > GO:2-chloro-N-isopropylacetanilide 1,2-dioxygenase activity ; GO:0034908
EC:1.14.12 > GO:phthalate 3,4-dioxygenase activity ; GO:0034911
EC:1.14.12 > GO:diphenyl ether 2,3-dioxygenase activity ; GO:0034954

We might need a rule that EC number used for xrefs MUST have 4 numbers, not three. Otherwise,  the mapping to a GO term is NOT unique

see EC:6.5.1 (DNA and RNA ligase)
<IP_ADDRESS> DNA ligase (ATP)
<IP_ADDRESS> DNA ligase (NAD(+))
<IP_ADDRESS> RNA ligase (ATP)
<IP_ADDRESS> RNA 3'-terminal-phosphate cyclase (ATP)
<IP_ADDRESS> RNA 3'-terminal-phosphate cyclase (GTP)
<IP_ADDRESS> DNA ligase (ATP or NAD(+))
<IP_ADDRESS> DNA ligase (ATP, ADP or GTP)

Also, demonstrating what Chris mentioned, we have two GO terms that have Xrefs to EC:6.5.1, with a parent term that has an even more general Xref to EC, but we don't have a GO term that could uniquely map to EC:6.5.1
GO:0016886 - ligase activity, forming phosphoric ester bonds; Xref = EC:6.5

is_a GO:0008452 - RNA ligase activity; Xref = EC:6.5.1
is_a GO:0003909 - DNA ligase activity; Xref = EC:6.5.1

This is ongoingly being fixed as many came in from plant enzyme project. Thought I got them all but some still pop up now and then and are usually covered by their individual tickets.

These are still being looked at from long list to remove 3 digit EC from leaf terms.   Focusing on these two for this ticket.
EC:1.14.12.-
EC:6.5.1.-

pinging @hdrabkin

As of today, I don't see any terms with a EC:6.5.1.- xref, so that seems fixed.
But there are still 19 terms with inappropriate EC:1.14.12.- xref:
id: GO:0018603
name: nitrobenzene 1,2-dioxygenase activity
id: GO:0018604
name: 4-aminobenzoate 3,4-dioxygenase (deaminating) activity
id: GO:0018606
name: benzenesulfonate dioxygenase activity
id: GO:0018607
name: 1-indanone monooxygenase activity
id: GO:0018608
name: 1-indanone dioxygenase activity
id: GO:0018609
name: chlorobenzene dioxygenase activity
id: GO:0018611
name: toluate dioxygenase activity
id: GO:0018612
name: dibenzothiophene dioxygenase activity
id: GO:0018613
name: 9-fluorenone dioxygenase activity
id: GO:0018614
name: ethylbenzene dioxygenase activity
id: GO:0018615
name: 2-indanone monooxygenase activity
id: GO:0018617
name: 4-aminobenzenesulfonate 3,4-dioxygenase (deaminating) activity
id: GO:0034521
name: 1-naphthoic acid dioxygenase activity
id: GO:0034825
name: tetralin ring-hydroxylating dioxygenase activity
id: GO:0034906
name: N-isopropylaniline 1,2-dixoxygenase activity
id: GO:0034907
name: acetanilide 1,2-dioxygenase activity
id: GO:0034908
name: 2-chloro-N-isopropylacetanilide 1,2-dioxygenase activity
id: GO:0034911
name: phthalate 3,4-dioxygenase activity
id: GO:0034954
name: diphenyl ether 2,3-dioxygenase activity

The remaining issues on this ticket were fixed as part of the recent enzyme review.
This is now the only (and correct) EC:1.14.12.- mapping:
id: GO:0016708
name: oxidoreductase activity, acting on paired donors, with incorporation or reduction of molecular oxygen, NAD(P)H as one donor, and incorporation of two atoms of oxygen into one donor
def: "Catalysis of an oxidation-reduction (redox) reaction in which hydrogen or electrons are transferred from NADH or NADPH and one other donor, and two atoms of oxygen are incorporated into one donor." [EC:1.14.12.-]
xref: EC:1.14.12.-
Closing.


[DO NOT MERGE] Upstream test PR

Changes w.r.t. habana_main:

Reverted https://github.com/HabanaAI/vllm-fork/pull/250 - may be merged later on, not required for basic HPU functionality
Reverted https://github.com/HabanaAI/vllm-fork/pull/195 - may be merged later on, not required for basic HPU functionality
Reverted https://github.com/HabanaAI/vllm-fork/pull/191/ - links were referring to local repo, not the upstream
Reverted https://github.com/HabanaAI/vllm-fork/pull/236/ - breaks GPU UTs with numerical accuracy, beats me ¯\(ツ)/¯
Reverted https://github.com/HabanaAI/vllm-fork/pull/286/ - we were asked to exclude quantization changes
Removed INC quantization backend & weights_load_device parameter - we were asked to do so
Removed mark_step() injections from models - we were asked to do so
Removed changes to common LoRA code
Removed finish_measurements from LLMEngine and LLM.py
Removed custom unit tests & any changes to unit tests
Removed README_GAUDI.md
Removed changes in README.md

Upstream finished, closing.

@kzawora-intel Regd #286 (Autofp8) support. Is this feature dropped all together or will it come back in future upstream ?


add deprecated notice

closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/5239
@yogkumgit

Docs Build status updates of commit ebeb9e1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Complete-CsCceApplianceUnregistration.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 662316f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Complete-CsCceApplianceUnregistration.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a79d356:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Complete-CsCceApplianceUnregistration.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Revert changes of 776d7a52

This change is

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

Comparison is base (31f0400) 70.80% compared to head (e279b5a) 70.80%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1352      +/-   ##
==========================================
- Coverage   70.80%   70.80%   -0.01%
==========================================
  Files          59       59
  Lines        7540     7538       -2
  Branches     7540     7538       -2
==========================================
- Hits         5339     5337       -2
  Misses       1779     1779
  Partials      422      422

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


Update react 0.14.0 rc1

I'm wondering. Why did you change onTouchTap for onClick?

As far as i understand, React 0.14.0 now handles tap events correctly using the onClick so there is no need for a separate tap-event plugin.
I did the same as what was done here : https://github.com/juhaelee/material-ui-io

So I don't understand why https://github.com/zilverline/react-tap-event-plugin add a react v0.14 support instead of making it deprecated.

@s0meone any clue on this?

yes i am unsure now how it should be :)
After reading the list of breaking changes
it looks like the Touch events are now included with the react lib at react/lib/TapEventPlugin.js
You don't need to include them anymore from a separate plugin.
and you don't need to initialize them manually.
But i guess you still need to use the onTouchTap instead of onClick ...
A bit further down on that page in the Notable bug fixes section it sais :
Click events are handled by React DOM more reliably in mobile browsers, particularly in Mobile Safari.
So i'm not sure at this point.
If anybody could shed some light on this it would be great.
Let me know if i need to revert back to onTouchTap ;)

Touch events are enabled by default now, which means touchstart, touchend, touchmove, touchcancel events are now handled by React's event system.
React 0.14 rc1 doesn't include the TapEventPlugin. React's repository does include my fix however (although not credited or documented). And onClicks are still 300ms behind.
So if you want to use onTouchTap, you'll need react-tap-event-plugin. Nothing has changed really :)

thx for clearing that up.
switched back to using onTouchTap and react-tap-event-plugin ;)

closing this as the only change remaining is this one :
Change to ReactDOM.findDOMNode() and use separated react addon libs
and this PR is not up to date with the 0.12.0 release.


pysqlite3-binary

I'm getting below error when when trying to install
pip install pysqlite3-binary
ERROR: Could not find a version that satisfies the requirement pysqlite3-binary (from versions: none)
ERROR: No matching distribution found for pysqlite3-binary
how can i fix this..

I'm getting below error when when trying to install
pip install pysqlite3-binary
ERROR: Could not find a version that satisfies the requirement pysqlite3-binary (from versions: none)
ERROR: No matching distribution found for pysqlite3-binary
how can i fix this..

Did you create a seperate new environment with python > 3.9 and < 3.12? Then installed using requirements.txt?

yes I have environment variable ...I'm using Python 3.12.4.....

yes I have environment variable ...I'm using Python 3.12.4.....

Okay maybe downgrade it a little bit. Also pysqlite3-binary is used for psycopg2 but i guess you already have sqlite binaries if you are windows user. Try to install other dependencies. And inside Home.py comment out the import of pysqlite3.

import('pysqlite3')
import sys
sys.modules['sqlite3']=sys.modules.pop('pysqlite3')
Only comment these three lines. And see if it works by uploading a dataset. If you don't have api key it will throw error. Make sure you have it.

Let me know if you face any issues after running it. https://eda-gpt-24.streamlit.app/EDA_GPT I deployed it on streamlit but it's not a powerful server so it might lag. If you have a powerful cpu then it'll work better locally.

I have done that already ...but when i run the streamlit ...when i can click the EDA GPT page ...page upload doesn't complete...

Did it show the home page?

yes ..it is ...

Show me the logs in the terminal.

It's not showing any log ...

Did you reload the page? While it's running?

yes ..I did but still showing the same thing ...

This should be logged on initial oage reload. It will download some nltk packages.

Try to change the page to home then settings and so on. And then come back to EDA page.

Still facing the same issue ...

Still facing the same issue ...

I think it must be some system issue. Since home page is working but for some reason EDA page is not working. Did you try a different browser?

yes ..I have tried ...but didn't work ...

yes ..I have tried ...but didn't work ...

If you want me to make a package which supports structured data analysis i can do that. Or maybe since there are dependency issues i can dockerize it and make a web app for that like Julius ai. The problem is i am not getting time these days. If anyone wants to work on this with me I'll explain the project.


Visible neighbors option does not work with refresh graph button

When trying to set the cob option "Visible Neighbors (For Custom)" to 0, the network still displays neighbors if the "refresh graph" button is used. If I use the "build graph" button on the network tab, then it works.

Sounds like a event bug or is that the expected behavior? @monprin?

Was a logic bug, fixed in next version.


std.process should use lightweight forks where available

rsw0x (@rsw0x) reported this on 2015-07-04T03:21:56Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=14770
CC List

dsp (@dsp)
kubo39
post (@kyllingstad)
schveiguy (@schveiguy)

Description
fork(even with CoW pages) can be extremely slow with modern memory usages due to the antiquated default page size of OSes because it requires copying the page table.

For example, a program using 400MiB of memory with 4KiB pages requires copying 102,400 page structs. On Linux, a page struct in the kernel is at least 72 bytes so this requires a copy of 7.2MiB.

This scales linearly with heap size, after some personal testing on Linux I found forking with almost nothing allocated to take ~60 microseconds, 100 MiB ~3 milliseconds, and 1GiB to take 30-45 milliseconds. vfork took a constant 20 microseconds no matter the heap size.

Solution: where available, use posix_spawn, vfork, etc. These do not require copying page tables. std.process does not require the page tables since it immediately replaces itself with another process.

I marked this all OSes, but really it's all POSIX OSes I guess.

kubo39 commented on 2018-07-30T15:01:33Z
tl;dr: I think spawnProcess uses vfork internally iff Linux available.

* We must care about the process privilege, since if the parent process or child process can change effective UID/GID, different privileged processes shares memory.
* We must use _exit(2), same as before.
* signal handlers may rewrite global variables, so set SIG_DFL before vfork.
* Solaris has bug.
* Other platform planed(e.g, NetBSD has nice posix_spawn systemcall), but not implement now.

Okay, I try to do this.

## References.

* posix_spawn(3) requires glibc 2.24+.
* posix_spawn(IEEE Std 1003.1-2008) cannot specifies working directory(chdir).
* http://www.tedunangst.com/flak/post/OpenBSD-and-vfork OpenBSD's vfork doesn't share memory.
* https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9ff72da471a509a8c19791efe469f47fa6977410 glibc's posix_spawn uses clone(2) instead of vfork(2).
* https://bugs.ruby-lang.org/issues/11265#note-8 In Solaris, vfork causes dynamic linker problem.
* https://github.com/golang/go/commit/9e6b79a5dfb2f6fe4301ced956419a0da83bd025 Go uses clone(CLONE_VFORK | CLONE_VM,..) Linux only.
* https://github.com/rust-lang/rust/pull/48624 Rust uses posix_spawn(3) on FreeBSD/macOS/Linux.

schveiguy (@schveiguy) commented on 2015-07-06T12:46:36Z
CC'ing Lars, this is a good idea.

post (@kyllingstad) commented on 2015-07-31T07:21:56Z
I think the "correct" thing to do here (on Linux, at least) is to use the clone() function, as described in this article:

    http://blog.famzah.net/2009/11/20/a-much-faster-popen-and-system-implementation-for-linux/

NOTE: If anyone wants to take a stab at implementing this for Phobos, don't look at the actual source code for the "popen-noshell" library, as it is LGPL-licensed.

Both clone() and vfork() are GNU library wrappers around Linux' clone system call, but clone() allows a much finer control over which data gets copied into the new process. Unlike vfork(), however, clone() is not a drop-in replacement for fork(). It takes a function to execute and a stack space in which to execute it, as opposed to continuing execution from the same point in the child process. In other words, there's a bit more work needed to incorporate it in spawnProcess().

Note that vfork() seems to be generally frowned upon; see for example the NOTES section of the man page:

    http://man7.org/linux/man-pages/man2/vfork.2.html#NOTES

dsp (@dsp) commented on 2015-07-07T05:52:14Z
https://github.com/D-Programming-Language/phobos/pull/3476

I opted for using vfork. It seems we are in all cases doing the right thing, not tempering with the process space and correctly calling execv* or _exit.

It seems that the "correct" method would be using posix_spawn, however we need support for this in druntime, so at the moment, I think going with vfork is less invasive while providing the proposed enhancements.

schveiguy (@schveiguy) commented on 2018-07-30T15:50:42Z
FYI, new PR by Hiroki Nada: https://github.com/dlang/phobos/pull/6644

kubo39 commented on 2018-08-02T15:54:49Z
(In reply to anonymous4 from comment #6)
> Maybe have a branch for linux and call clone there, call posix_spawn or fork
> for other systems. vfork looks scary and posix deprecated it.

If we use clone(2), the stack of the child process is newly allocated and the stack of the parent process is not shared. It's preferred.

Maybe I should add clone(2) to druntime before...

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9ff72da471a509a8c19791efe469f47fa6977410

dfj1esp02 commented on 2018-08-01T13:50:03Z
Maybe have a branch for linux and call clone there, call posix_spawn or fork for other systems. vfork looks scary and posix deprecated it.


Fix bug with multi-select field

I tried to use the multi-select field, but I came across a problem that only the last selected parameter remains

Hi @okopny,
you are right about the bug, gut your patch seems to brake the form validation in a way that I didn't understand yet.

Hi @oberix,
Hmmm, can you show me in which way the form validation is broken? I've tested the form validation and everything work well.

Hi @okopny,
sorry I had a bug in my testing project. Your patch is working correctly, merged. Also I removed the attribute self.params which is useless at this point.
Could you double test please, if it's working good for you too I'll make a new tag.
Thanks

I created a simple report for testing
from django import forms
from admin_reports import Report, register

class TestReportForm(forms.Form):
    action_from = forms.DateField()
    action_to = forms.DateField()
    aggregated_by = forms.ChoiceField(choices=[[None, 'None'], ['daily', 'Day'], ['monthly', 'Month']])
    country = forms.MultipleChoiceField(choices=[['us', 'US'], ['au', 'AU'], ['gb', 'GB']])

@register()
class TestReport(Report):
    form_class = TestReportForm

    def aggregate(self, **kwargs):
        return []

Requests:

/

/?action_from=2020-20-20&action_to=aaaa&aggregated_by=value&country=fr

/?action_from=2017-10-03&action_to=2017-10-04&aggregated_by=daily&country=us&country=au

Cool! I've tested code on my own project and everything work perfectly. I think you can add new tag. Thanks a lot!

new tag v0.10.8 ready


Uncaught TypeError: Cannot read property 'getBoundingClientRect' of null

[Enter steps to reproduce below:]

Open a file
Resize the Go-Debug panel
Uncaught TypeError pops up

Atom Version: 1.7.2
System: Mac OS X 10.11.4
Thrown From: go-debug package, v0.1.11
Stack Trace
Uncaught TypeError: Cannot read property 'getBoundingClientRect' of null
At /Users/Neil/.atom/packages/go-debug/lib/panel.jsx:261

TypeError: Cannot read property 'getBoundingClientRect' of null
    at Panel.onResize (/Users/Neil/.atom/packages/go-debug/lib/panel.jsx:261:33)

Commands
     -0:03.2.0 minimap:toggle (atom-text-editor.editor.vim-mode.normal-mode.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "markdown-preview",
      "travis-ci-status"
    ],
    "packagesWithKeymapsDisabled": [
      "markdown-preview"
    ],
    "themes": [
      "one-dark-ui",
      "monokai-seti"
    ]
  },
  "go-debug": {
    "delvePath": "/usr/local/go/bin/dlv",
    "limitCommandsToGo": true
  }
}

Installed Packages
# User
autocomplete-go, v1.0.6
builder-go, v1.0.0
change-case, v0.6.0
color-picker, v2.1.1
compare-files, v0.6.2
emmet, v2.4.3
environment, v1.2.0
file-icons, v1.7.7
fonts, v1.2.0
go-config, v1.1.4
go-debug, v0.1.11
go-get, v1.0.3
go-plus, v4.1.0
gofmt, v1.1.6
gometalinter-linter, v1.1.0
gorename, v1.0.2
highlight-line, v0.11.1
javascript-snippets, v1.2.1
last-cursor-position, v0.9.0
linter, v1.11.4
linter-jsonlint, v1.2.5
markdown-preview-plus, v2.4.0
merge-conflicts, v1.4.2
minimap, v4.22.1
monokai-seti, v0.7.0
navigator-godef, v1.0.3
pigments, v0.26.0
tester-go, v1.0.4
vim-mode, v0.65.0
vim-surround, v0.8.1

# Dev
No dev packages

Any more details? Works for me for atom 1.7.2 and atom beta 1.8...

I can reproduce it, by doing the following:

Restarted Atom
Opened a Perl project (a nice feature would be for Go-Debug to hide/disable the panel on non-Go source files
Attempted to resize the Go-Debug panel's width to a smaller size
The panic is triggered

You've done a great job with this addition to Atom's Golang support, thanks so much for all of your hard work!

You actually can hide the panel --> see https://github.com/lloiser/go-debug#key-bindings

cmd-k cmd-g (mac) / ctrl-k ctrl-g (others) toggles the main panel

I will try to reproduce it with a perl project then although I suspect it to be a problem.
Maybe some of your other packages affects it, I will check that too...

I found the keybindings didn't work as described, I had to use (Mac) cmd-k-g to toggle on and off.

Additional, I found that after the panel resize panic in a Perl project, toggling the Go-Debug panel on again and then resizing had no further errors.

Ok, so after a panel toggle it works. Strange... Does it still work after a restart and atom close/open?
Tbh: I can't imagine how this could have helped... :confused:

Yes, after toggling the panel on/off/on, cmd-q and restarting Atom, it works fine.


regions plugin: adjustable zIndex

Hey, thank you for contributing to wavesurfer.js!
To review/merge open PRs it is very helpful to know as much as possible about the changes which are being introduced. Reviewing PRs is very time consuming, please be patient, it can take some time to do properly.
Title: Please make sure the name of your PR is as descriptive as possible (Describe the feature that is introduced or the bug that is being fixed).
Please make sure you provide the information below:
Short description of changes:
Breaking in the external API:
Breaking changes in the internal API:
Todos/Notes:
Related Issues and other PRs:

thanks @HuangZhongtao2020. can you make a parameter for this instead and add some documentation?

ping @HuangZhongtao2020

No response, closing. Please re-open after making requested changes.

If anyone needs this, you can write CSS to set the z-index of the region element, using a selector like:

wave > region {
    z-index: 123;
}


Build on windows failure

Title: build failure on windows
Description:
I've followed the procedure as per https://github.com/envoyproxy/envoy/tree/main/bazel under windows section. Once the build was done and bazel test failed. Later on after cleanup (bazel clean --expunge) and I'm getting following error:
C:\Users\user_xx\envoy>bazel build //source/exe:envoy-static
Starting local Bazel server and connecting to it...
... still trying to connect to local Bazel server after 10 seconds ...
INFO: SHA256 (https://golang.org/dl/?mode=json&include=all) = 4bb9f5f7d71d826c10b10c65bcaf53847a038f646101c25de10e52d8ffae7a7e
INFO: Analyzed target //source/exe:envoy-static (763 packages loaded, 24096 targets configured).
INFO: Found 1 target...
ERROR: <builtin>: Failed to determine workspace status: Process exited with status 127
/bin/bash: bazel\get_workspace_status: No such file or directory
Target //source/exe:envoy-static failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 644.487s, Critical Path: 16.93s
INFO: 181 processes: 178 internal, 3 local.
FAILED: Build did NOT complete successfully

Other details:
Executing this in windows cmd prompt , had tried git bash but on build error there as well realized that 'link' should refer to MS - VS-Code 'link' and not from gnu.

Hey, thanks for the issue

Once the build was done and bazel test failed

How did the test fail?

Executing this in windows cmd prompt , had tried git bash but on build error there as well realized that 'link' should refer to MS - VS-Code 'link' and not from gnu.

Yeah your observation is correct. You might want to ensure that the link.exe that resolves on your PATH is from VC++ Build Tools and not /usr/bin/link.exe from MSYS2, which is determined by their relative ordering in your PATH. A dirtier hacky way is to rename gnu link.exe to link_.exe.

Executing this in windows cmd prompt

I know that some people have successfully built the project from cmd but for the time being we only recommend and test that all bazel commands should be executed from MSYS2. Is this an inconvenience for you?

Hey, thanks for the issue

Once the build was done and bazel test failed

How did the test fail?

It was the same error of 'Failed to determine workspace status'

Executing this in windows cmd prompt , had tried git bash but on build error there as well realized that 'link' should refer to MS - VS-Code 'link' and not from gnu.

Yeah your observation is correct. You might want to ensure that the link.exe that resolves on your PATH is from VC++ Build Tools and not /usr/bin/link.exe from MSYS2, which is determined by their relative ordering in your PATH. A dirtier hacky way is to rename gnu link.exe to link_.exe.

Executing this in windows cmd prompt

I know that some people have successfully built the project from cmd but for the time being we only recommend and test that all bazel commands should be executed from MSYS2. Is this an inconvenience for you?

Executing from MSYS2 also gave error:
C:\Windows\Temp\tmp.ZbY9g03Z4B\com_github_luajit_luajit\src>cl /nologo /c /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_STDIO_INLINE=__declspec(dllexport)__inline /DLUAJIT_ENABLE_LUA52COMPAT /O2 host\minilua.c
minilua.c

C:\Windows\Temp\tmp.ZbY9g03Z4B\com_github_luajit_luajit\src>link /nologo /out:minilua.exe minilua.obj
link: extra operand 'minilua.obj'
Try 'link --help' for more information.

*******************************************************
*** Build FAILED -- Please check the error messages ***
*******************************************************
Traceback (most recent call last):
  File "C:\_eb\execroot\envoy\external\com_github_luajit_luajit\build.py", line 53, in <module>
    win_main()
  File "C:\_eb\execroot\envoy\external\com_github_luajit_luajit\build.py", line 45, in win_main
    shutil.copy("lua51.lib", dst_dir + "/lib")
  File "C:\Users\user_xx\Python38\lib\shutil.py", line 418, in copy
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "C:\Users\user_xx\Python38\lib\shutil.py", line 264, in copyfile
    with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 'lua51.lib'

Not sure if this is also due to 'link'
$ link --help
Usage: link FILE1 FILE2
  or:  link OPTION
Call the link function to create a link named FILE2 to an existing FILE1.

      --help     display this help and exit
      --version  output version information and exit

GNU coreutils online help: <https://www.gnu.org/software/coreutils/>
Report any translation bugs to <https://translationproject.org/team/>
Full documentation <https://www.gnu.org/software/coreutils/link>
or available locally via: info '(coreutils) link invocation'

The issue that you are seeing is because link.exe resolves to link.exe from gnu and not from MSVC.
You might want to ensure that the link.exe that resolves on your PATH is from VC++ Build Tools and not /usr/bin/link.exe from MSYS2, which is determined by their relative ordering in your PATH. A dirtier hacky way is to rename gnu link.exe to link_.exe.

Thanks @davinci26 , I shall try with this change.


The pid_m calculation in matrix-multiplication tutorial

The code at line 216 defines pid_m as follows:
pid_m = first_pid_m + (pid % group_size_m)
This line seems to be incorrect? Why we do not need an additional modulo operation as follows:
pid_m = first_pid_m + (pid % num_pid_in_group) % group_size_m

num_pid_in_group = GROUP_SIZE_M * num_pid_n
Because num_pid_in_group is a multiple of GROUP_SIZE_M`, we don't need to do the mod twice?

Yes, but the group_size_m is not always equal to GROUP_SIZE_M in the last group?

Hm, you do have a good point...
I'm not 100% sure how this is supposed to work.  Does the code do the wrong thing when we hit that branch?

num_pid_in_group >= group_size_m

Maybe you are confused about pid_m's order in the last group? IIUC, it doesn't matter as long as they are unique

Hi @Pairshoe , From code readability side, it should be  (pid % **num_pid_in_group**) % group_size_m. From computation side, it doesn't matter. Here's a possible explanation (correct if there's something wrong).
Considering A = first_pid_m * num_pid_n, B is a variable within the range of [0,  (num_pid_m - first_pid_m) * num_pid_n], while we can see A as constant for the last group, then for the last group,
pid % group_size_m is equal to (A + B) % (num_pid_m - first_pid_m)  , and it must be in the range of [0, (num_pid_m - first_pid_m) ], just not the right order.


chore: limit global variable current.Configuration usage

/test limit=local

#5134 is an addition to this PR that removes nearly all the usages, but it is complex to review and probably not worth the inconvenience.