Results from SRI KG not in answer

Possibly a repeat of #165
Query:
{
    "message": {
        "query_graph": {
            "nodes": {
                "n0": {
                    "id": "NCBIGene:1017",
                    "category": "biolink:Gene"
                },
                "n1": {
                    "category": "biolink:Pathway"
                }
            },
            "edges": {
                "e01": {
                    "subject": "n0",
                    "object": "n1"
                }
            }
        }
    }
}

Returns no results from strider.   But in the logs in the response we see:
{'message': 'Received response from KP', 'url': 'https://trapi.monarchinitiative.org/query', 'request': {'message': {'query_graph': {'nodes': {'n0': {'category': 'biolink:Gene', 'is_set': False, 'id': 'NCBIGene:1017'}, 'n1': {'category': 'biolink:Pathway', 'is_set': False}}, 'edges': {'e01': {'subject': 'n0', 'object': 'n1', 'predicate': 'biolink:actively_involved_in'}}}}}, 'response': {'message': {'query_graph': {'nodes': {'n0': {'id': 'NCBIGene:1017', 'category': 'biolink:Gene', 'is_set': False}, 'n1': {'id': None, 'category': 'biolink:Pathway', 'is_set': False}}, 'edges': {'e01': {'subject': 'n0', 'object': 'n1', 'predicate': 'biolink:actively_involved_in', 'relation': None}}}, 'knowledge_graph': {'nodes': {'GO:0006977': {'category': ['biolink:NamedThing', 'biolink:BiologicalProcess', 'biolink:Occurrent', 'biolink:Pathway'], 'name': 'DNA damage response, signal transduction by p53 class mediator resulting in cell cycle arrest',

i.e. the KP is returning some results and GO terms mapped to the pathway.

After talking to @patrickkwang I don't think that this observation is related, but I'll mention that the things being returned bound to n1 are GO terms that we don't usually consider Pathways (i.e. the node normalizer will not call them pathways)

May be fixed by #166. Please confirm.

We're now getting results from REF KG for this query.


Provide version package variable

Hi there! Almost all Python libraries I know have a package variable __version__ that provides the current version as a string. This is nice if you want check in an interactive session with what version you are dealing and in general for debugging purposes. I know that another great Blue Yonder package called PyScaffold provides this out of the box ;-)

I heard that PyScaffold also introduces unwanted dependencies ;-). Valid point about the __version__ variable, though.

That really is a misconception, only during development, not when you ship your package.


kubectl describe storageclass<storage class name> is incorrect

kubectl describe storageclass<storage class name> uses the wrong 'slash'
kubectl describe storageclass/ works.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3135f590-c419-e321-83f6-79145c5701e5
Version Independent ID: 9c191ee0-f065-c003-04a3-bacc68987579
Content: Storage configuration - Azure Arc
Content Source: articles/azure-arc/data/storage-configuration.md
Service: azure-arc
Sub-service: azure-arc-data
GitHub Login: @uc-msft
Microsoft Alias: umajay

@dmc-tech Thanks for your comment! We will review and provide an update as appropriate.

@dmc-tech Thank you for catching that. This has bee fixed internally and should be updated on the public-facing documentation site soon.

#please-close


I can't open the project

This is the error that pops out:
ERROR  workspace configuration error: package.json: no workspaces found. Turborepo requires npm workspaces to be defined in the root package.json

Help me!

This is the error that pops out: ERROR workspace configuration error: package.json: no workspaces found. Turborepo requires npm workspaces to be defined in the root package.json

from what I can tell you are running npm run dev or whatever. Glowsquid uses the pnpm package manager, so install it via the instructions at https://pnpm.io/installation .


Report system test stats to data dog with job name.

Summary:
This enables us to run system tests on branches without polluting the
data dog dashboard for the master branch.

P.S. did you know you can parametrize DD dashboards which should be handy when comparing master with other branches.

Sweet!


rename probability functions

Summary:
Rename probability functions to match the language definitions.
Description:

[ ] _log to  _lpdf or _lpmf
[ ] _log_cdf to _lcdf
[ ] _log_ccdf to _lccdf

This will hugely simplify the code generation component of Stan.
To Do

[ ] Rename functions

[ ] Update function name
[ ] Update documentation
[ ] Update file name
[ ] Update tests

[ ] Figure out how to test distributions (might not need to change the generated code)
[ ] Update makefile appropriately

Current Version:
v2.10.0

Do we need to worry about backwards compatibility here?

normal_log() should be renamed to normal_lpdf()
Do we need to keep a normal_log() function that's deprecated that calls normal_lpdf(); if so, how do we deal with deprecation?

We need to maintain backward compatibility until Stan 3.0.
At that point, I can do the do-si-do in stan-dev/stan to get
rid of the _log suffixes in the math lib and the language.
For now, we should add a doxygen command for each of the _log
forms:
@deprecated ---how to replace it---
along with the @param etc.  See:
https://www.stack.nl/~dimitri/doxygen/manual/commands.html#cmddeprecated

Thanks. That makes sense.
On Fri, Oct 14, 2016 at 11:25 AM, Bob Carpenter<EMAIL_ADDRESS>wrote:

We need to maintain backward compatibility until Stan 3.0.
At that point, I can do the do-si-do in stan-dev/stan to get
rid of the _log suffixes in the math lib and the language.
For now, we should add a doxygen command for each of the _log
forms:
@deprecated ---how to replace it---
along with the @param etc. See:
https://www.stack.nl/~dimitri/doxygen/manual/commands.html#cmddeprecated
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/issues/320#issuecomment-253833775, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZ_FyrPinL2zcxv5eAFTCfSbrSugIudks5qz58HgaJpZM4JTuYn
.


Allow setting of grid col number

What is the context of this PR?
Allow setting of grid col number in the pageConfig. This change was due to it needing to be able to be overwritten for the census website
How to review
Check pageColNumber can be set and it defaults to 8 if not set

 Add ability to set col widths in page template

I don't think this should be set at this level, as in defined in pageConfig. This would mean every template that extends this would have it set.
I think we need to create a variable and set it in the page_template and then this can be overriden within templates that extend it. This would need to be tested as there may be an inheritance issue at the point the value gets set.


Build error when updating from 2.16.6 to 2.16.7

Hey @dankinsoid , thanks for providing this nice library to generate the OpenAPI specs!
Not sure if you're aware but we've just run into a compile error when updating from 2.16.6 to 2.16.7:
https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/actions/runs/5220111100/jobs/9422776122?pr=2421
❌ /__w/SwiftPackageIndex-Server/SwiftPackageIndex-Server/.build/checkouts/VaporToOpenAPI/Sources/VaporToOpenAPI/AnyValue++.swift:37:3: switch must be exhaustive
                switch self {
                ^

I'll try and figure out what the fix might be once I've got a moment but I wanted to let you know right away in case it's an easy fix for you.

Hello, @finestructure, you are welcome
I'm sure i'v fixed it in VaporToOpenAPI 4.3.6, which version of VaporToOpenAPI do you use?

@finestructure If you use VaporToOpenAPI 3.x, I fixed it at 3.15.2

Ah cheers. I'd run a package update just before but it stayed at "3.15.1", weird.
Let me actually try and move forward to 4.x, I hadn't realised I'm a full major version behind!

Ok, bumping it to 4.x.x fixes it, thanks for your help!


vmlinux.h question

In the vmlinux.h on line 950 appears:
struct hlist_node pid_links[4];
shouldn't it be
struct pid_link pid_links[4];
instead?

https://elixir.bootlin.com/linux/v5.8.18/source/include/linux/sched.h#L842

Thanks @chenhengqi  that was really helpful
Does it mean that libbpf doesn't support kernels < 5.8.18 or this is a generic representation for all the bpf supported kernels?

Libbpf supports any kernel version. vmlinux.h doesn't have to match exact kernel version as long as all the types and their fields are what you expect. If there was some change in most recent kernel that you need (like hlist_node to pid_link change), then you'll need to re-generate vmlinux.h, or you can just define your own definition of a data structure you'd like to read with BPF CO-RE. vmlinux.h is just a convenient way to have most of kernel types defined for you, so  that you don't have to re-define them manually.


make gitlab scripts reusable - 2nd try

I closed the #44 by accident, instead of trying to figure out how to restore that, here's a new one ;)
This adds the possibility to add easier gitlab ci integration into our projects. It abstracts some of the stuff everyone needs and is then easily added to every project without having to reinvent the wheel all the time or have the same scripts in every project.
See https://github.com/chregu/rawbot-virtualization/blob/gitlabci_scripts/ci/README.md for the instructions, how to use it (noone is forced to use it, but it will make our life at the Migros project much easier, where we have the many small projects)

I merge this and will see if it needs some tuning when it will be adopted by more projects :)


some qa items for marketing modal

Some tweaks to accomplish the three responsive styles outlined in https://cloud.githubusercontent.com/assets/1022172/22787136/42f6904c-eea9-11e6-8482-406488163e9b.jpg

I don't think the failing spec was related to this work so I hit rebuild.

@craigspaeth reassigning to you because christina is ooo, but you guys are both welcome to chime in

when force is loaded on mobile (no change, but to confirm it still works):

👍  code looks good. Weird failure—I kicked it again. Maybe make sure to pull the latest upstream code in case it's from someone else's old PR.


Latest sha256 for git-annex appears to be out of date

I see the following when trying to update git-annex today:
Vulcan ~/Products $ nix build --option build-use-substitutes false darwin.pkgs.gitAndTools.git-annex
hash mismatch in fixed-output derivation '/nix/store/r71i5anr7k7514rq0rzx8bjdybjfj5sa-git-annex-7.20190219-src':
  wanted: sha256:1v2v6cwy957y5rgclb66ia7bl5j5mx291s3lh2swa39q3420m6v0
  got:    sha256:00k31p06pmzsd1gm3yw6b6sj06q9cj9cccxhqjqpzgyf1y5mjv2a
cannot build derivation '/nix/store/6c3mcr2sznbpdjb59a72vni5q3k3lmnx-git-annex-7.20190219.drv': 1 dependencies couldn't be built

@peti Is it safe to just update, or is this possibly a Darwin-related thing?

If this problem still exists in recent versions of the master branch, then it's appropriate to update the sha265 value in the configuration-common.nix. this phenomenon has nothing to do with gammon. It's a consequence of the fact, that we cannot use the source tarball for git-annex from Hackage, so we cannot auto detect the appropriate hash value easily when an update comes out.

I ran into the problem on the unstable channel.

The SHA mismatch does not exist in master-


malwarebytescloud: Bugfix - Hotfix Version 2.0.0

…lwarebytes telemetry code
Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

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

[x] Testing of all the changes has been performed (for bug fixes / features)
[x] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[x] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[x] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[x] Verify all checks are passing.
[x] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[x] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

Version 1.2.1 - Released February 8, 2022

Fixed APi requests bugs
Added Telemetry code
Added Python3 support

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

@cpangam Is it possible to review this PR?

@szarembo-mwb | @rskumar-mwb,
We have one query regarding copyright year, generally, for SOAR apps we are following these standards for re-releasing app Copyright (c) Malwarebytes, <initial release year>-<current_year>. As you updated the copyrights with the only 2022 just want to make sure that it is intensely changed or can we update with our standard practice Copyright (c) Malwarebytes,2019-2022?
Also, we have made a few changes in other files as per our standard practices, please have a look into that. Let us know in case of any query or if it looks correct?

@vhirapara-crest you can update with your standard practice Copyright (c) Malwarebytes,2019-2022. Thanks.

@vhirapara-crest Does this version of our app get released immediately or is there a release cycle on your guy's end? Just curious.

@vhirapara-crest Does this version of our app get released immediately or is there a release cycle on your end? Just curious.

Hi @rskumar-mwb, For this PR we will release the app. But in the very near future, the automation job will introduce which will release the app on Splunk base once PR is merged.


Typing_Speed_Test_Game

Hello, I am Shreyash and wanted to add a project under GSSOC23 and Level3. This is a typing speed calculation and analysis tool.
Tech Stack - Html, CSS, JS
Expected behavior
Words per minute , accuracy and Time left is displayed and we can take test again by clicking on Try Again. it will prompt new paragraph.
Screenshots (optional)

@TusharKesarwani @pranjay-poddar


Recreating in Swift

I am recreating this in Swift for MacOS, and have some questions.

Do you need the headers? Or are they only needed for getting the questions because I tried making some requests without headers and was able to retrieve basic scheduling info and prizes.
When making a request, are the questions located under: https://api-quiz.hype.space/shows/now?type=hq&userId=xxxxx? Using Insomnia and making a request with all the right headers and I only get basic info, is there a separate host to use for getting questions? If you could give me the URL directly to the questions/answers I would appreciate it.

I didn't understand:
# Remove control characters in the WebSocket message
message = re.sub(r"[\x00-\x1f\x7f-\x9f]", "", message)
message_data = json.loads(message)
logging.info(str(message_data))
in your Python version, so if you could clear that up for me (how to get questions/answer) I would appreciate it!
PS: I have noticed that you can still watch the game without being signed into an account so I don't think you would need authentication to do so (and user ID)...

I'm not sure if you need the headers or not. I put them in so HQ would be less likely to be able to differentiate between the program making the connection and an actual phone.
The questions are not located there. When the game is live, a socketUrl appears in the JSON and you connect to that with a WebSocket client. The server sends messages with chat messages, viewer counts, and questions/question summaries.

The replacement of control characters is needed for the JSON to be properly read. The message from the WebSocket connection is then transformed into a dictionary with json.loads, and the message data is logged to a file.
Hope this answered your questions. Good luck!

Ok, so I gotta find the socket url once it appears and then read from that? Then just open up the websocket? Is there only one set of questions/answers in there at a time? I haven't ever used a websocket before. How do I get it to automatically get the socket url? Does it have a constant name or something?

Yes, you read the socket URL once it appears and open a connection. The websocket server then sends a stream of messages containing JSON messages. When the show is live the socket URL appears under the "socketURL" key in the "broadcast" key of the JSON.

So I can just deserialize the json and open a websocket with whatever is in "jsonURL"? It would be broadcast (shown in my screenshot), and then socketURL, then that URL should be opened in a websocket?

Also, do you have any recordings (if that is even possible) so I don't have to wait until the game tomorrow at 3? Like recordings of the traffic, etc.

Yes, that's it. A partial log file of tonight's game is here: https://pastebin.com/5fbk4vd7. The first line is the response from https://api-quiz.hype.space/shows/now?type=hq&userId=xxxxx, and the rest is from the websocket connection.

Alright thanks, do you know any Swift? Was wondering if you know how I could sort of convert your Python code into Swift.

I don't know any Swift, sorry.

Alright, know any way I could give this Python script a GUI? Maybe display results a little better because sometimes its hard to tell with the console, and there are often multiple possible answers with similar scores.

Agreed. Some human decision-making is still needed if the exact answer is not found in the search results to decide if the word matches are significant enough to make it the right answer, and it might not find any possible answers if the question is worded weirdly. A GUI can be made with something like tkinter or PyQT. Feel free to fork and submit a pull request if you end up making one.

Alright, I'm gonna go to sleep, but I'll let you know what I do. I'm new to this whole GitHub thing, still figuring out how everything works.


Unsupported calling convention on i686-pc-windows-msvc

I was investigating how easy it would be to create bindings for Windows 32-bit with different calling conventions and so I ran the example in the ./bindgen-integration directory.
System
> rustup show
Default host: x86_64-pc-windows-msvc

installed toolchains
--------------------

stable-i686-pc-windows-msvc
stable-x86_64-pc-windows-msvc (default)
nightly-i686-pc-windows-msvc
nightly-x86_64-pc-windows-msvc

active toolchain
----------------

stable-i686-pc-windows-msvc (directory override for 'C:\Repos\rust-bindgen\bindgen-integration')
rustc 1.15.1 (021bd294c 2017-02-08)

> clang -v
clang version 3.9.1 (branches/release_39)
Target: i686-pc-windows-msvc

Input C/C++ Header
#pragma once

class Test {
  int m_int;
  double m_double;
public:
  static const char* name();
  Test(int foo);
  Test(double foo);

  static const int COUNTDOWN[];
  static const int* COUNTDOWN_PTR;
  static const int* countdown();
};

namespace testing {

typedef Test TypeAlias;

} // namespace testing

typedef testing::TypeAlias TypeAlias;

Bindgen Invokation
let bindings = Builder::default()
        .no_unstable_rust()
        .enable_cxx_namespaces()
        .raw_line("pub use self::root::*;")
        .header("cpp/Test.h")
        .clang_arg("-x")
        .clang_arg("c++")
        .clang_arg("-std=c++11")
        .generate()
        .expect("Unable to generate bindings");

Actual Results
error: failed to run custom build command for `bindgen-integration v0.1.0 (file:///C:/Repos/rust-bindgen/bindgen-integration)`
process didn't exit successfully: `C:\Repos\rust-bindgen\bindgen-integration\target\debug\build\bindgen-integration-a1a8c12a2facefae\build-script-build` (exit code: 101)
--- stdout
TARGET = Some("i686-pc-windows-msvc")
OPT_LEVEL = Some("0")
TARGET = Some("i686-pc-windows-msvc")
HOST = Some("i686-pc-windows-msvc")
TARGET = Some("i686-pc-windows-msvc")
TARGET = Some("i686-pc-windows-msvc")
HOST = Some("i686-pc-windows-msvc")
CXX_i686-pc-windows-msvc = None
CXX_i686_pc_windows_msvc = None
HOST_CXX = None
CXX = None
TARGET = Some("i686-pc-windows-msvc")
HOST = Some("i686-pc-windows-msvc")
CXXFLAGS_i686-pc-windows-msvc = None
CXXFLAGS_i686_pc_windows_msvc = None
HOST_CXXFLAGS = None
CXXFLAGS = None
PROFILE = Some("debug")
running: "C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\bin\\amd64_x86\\cl.exe" "/nologo" "/MD" "/Z7" "/FoC:\\Repos\\rust-bindgen\\bindgen-integration\\target\\debug\\build\
\bindgen-integration-89b7af89d851f38d\\out\\cpp\\Test.o" "/c" "cpp/Test.cc"
ExitStatus(ExitStatus(0))
TARGET = Some("i686-pc-windows-msvc")
running: "C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\bin\\amd64_x86\\lib.exe" "/OUT:C:\\Repos\\rust-bindgen\\bindgen-integration\\target\\debug\\build\\bindgen-integratio
n-89b7af89d851f38d\\out\\libtest.a" "/nologo" "C:\\Repos\\rust-bindgen\\bindgen-integration\\target\\debug\\build\\bindgen-integration-89b7af89d851f38d\\out\\cpp\\Test.o"
ExitStatus(ExitStatus(0))
TARGET = Some("i686-pc-windows-msvc")
HOST = Some("i686-pc-windows-msvc")
TARGET = Some("i686-pc-windows-msvc")
TARGET = Some("i686-pc-windows-msvc")
HOST = Some("i686-pc-windows-msvc")
CXX_i686-pc-windows-msvc = None
CXX_i686_pc_windows_msvc = None
HOST_CXX = None
CXX = None
cargo:rustc-link-search=native=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\lib\
cargo:rustc-link-lib=static=test
cargo:rustc-link-search=native=C:\Repos\rust-bindgen\bindgen-integration\target\debug\build\bindgen-integration-89b7af89d851f38d\out
TARGET = Some("i686-pc-windows-msvc")
cpp/Test.h:1:9: warning: #pragma once in main file [-Wpragma-once-outside-header], err: false

--- stderr
thread 'main' panicked at 'unsupported calling convention: 4', C:\Repos\rust-bindgen\src\ir\function.rs:103
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Steps to reproduce

Install clang 3.9.1 for Windows 32-bit
> git clone https://github.com/servo/rust-bindgen.git
> cd rust-bindgen\bindgen-integration
> rustup override set stable-i686-pc-windows-msvc
> cargo build

OK I wanted to isolate the problem so I could try with stdcall and cdecl so I removed nearly everything from the header:
#pragma once

class Test {
  int m_int;
  double m_double;
public:
  static const char* name();
};

And it compiles with this. But as soon as you try to use cargo test you get
  = note: bindgen_integration-2ef5a86ee87393d3.0.o : error LNK2019: unresolved external symbol _?name@Test@@SAPBDXZ referenced in function __ZN19bindgen_integration8bindings4root4Test4name17h1c2ec80b5b5613d1E
C:\Repos\rust-bindgen\bindgen-integration\target\debug\deps\bindgen_integration-2ef5a86ee87393d3.exe : fatal error LNK1120: 1 unresolved externals

Which just looks like a mangling problem.

I don't have a windows machine to test on, could you inspect the generated library to see which mangled names are being generated?

The original issue here is that calling convention 4 is __thiscall, which is the default ABI for methods in MSVC.  However, the packages bindgen is using (syntex_syntax) don't define anything for __thiscall.
@emilio is it feasible to just modify syntex_syntax here to define __thiscall, and then do the appropriate adjustments to bindgen?

@froydnj yeah, also, note that syntex_syntax is pretty much a clone of libsyntax in the rust compiler, so this should probably be upstreamed.
Is this blocking you in any meaningful way? If there's any workaround we can do in bindgen, happy to help. Perhaps making it a soft error may help for now.

Is this blocking you in any meaningful way? If there's any workaround we can do in bindgen, happy to help. Perhaps making it a soft error may help for now.

Throwing a soft error here is hard, because we have to pass in /something/ for the calling convention.  I guess we already have special cases for Obj-C method declarations, we could fake things up for C++ method declarations, and then cross fingers that nobody is actually bindgen'ing calls to C++ methods?
We can work around this in Stylo by simply not building Stylo for win32 for the time being.

All that is required to repro is this:
// bindgen-flags: -- --target=i686-pc-windows-msvc

class Foo {
  public:
    void test();
};

or with --target=i686-pc-win32 as well.


webpack @easy-webpack/config-uglify broken the template html structure

I'm submitting a bug report

Aurelia Skeleton Version

skeleton-esnext-webpack

Framework Version:
1.0.0

Please tell us about your environment:

Operating System:
Windows [7|10]

Node Version:
4.4.2

NPM Version:
3.10.3

JSPM OR Webpack AND Version
webpack 2.1.0-beta.17

Browser:
all

Language:
ESNext

Current behavior:
when config Code-Splitting: Chunks / Async Bundles and webpack's output.publicPath  for cdn, i get error.  but, only config Code-Splitting: Chunks / Async Bundles work fine.
webpack.config.js
} else if (ENV === 'production') {
    // http://webpack.github.io/docs/configuration.html#output-publicpath
    config.output.publicPath = '//cdn.newtouch.com/resources/'
}

package.json
  "aurelia": {
    "build": {
      "resources": [
        "aurelia-i18n/t",
        "aurelia-i18n/nf",
        "aurelia-i18n/df",
        "aurelia-i18n/rt",
        {
          "bundle": "network",
          "path": [
            "network/network",
            "network/network-firewall",
            "network/network-private",
            "network/network-router",
            "network/network-router"
          ],
          "lazy": true
        }
      ]
    }
  },

Expected/desired behavior:
i can use async loading of splitting chunks, when serve my static resources on cdn.

What is the expected behavior?

What is the motivation / use case for changing the behavior?

i have found it  because of: it seems to destroy the HTML template structure.
            require('@easy-webpack/config-uglify')
            ({ debug: false })

change webpack config like this will work fine, but i still do not know why?

            require('@easy-webpack/config-uglify')
            ({ debug: false, mangle: false })

Got the reason

Solution

Ah, fantastic. Thanks @xiwc !

your are welcome!


[LiveComponent] Bug with ChoiceType in Form

Hi,
I am currently trying out Symfony Forms and Live components to reduce the need for Javascript. The first try outs went quite well and I would love to use this in the future!
But I have found a bug which seemed random at first (my form is a little bit more complicated using the choices type to add additional fields to the form), but I can now reproduce it in a simple form:
Requirements:
I have a form with a choice type and 3 choices, and an additional text field with a NotBlank validation.
Steps to reproduce:

Select choices zero and one
Submit the form, which will trigger the validation error of the text field
Deselect choice zero
Select choice zero again ==> Triggers error "The selected choice is invalid.". Also from now on the checkbox group seems to be broken

Everything works fine, before the submit is done.
What I have found in the Chrome inspector is:
After the first step the data-live-data-value attribute looks like this:
{"test":{"choices":["zero","one"],"name":""},"isValidated":false,"validatedFields":["test.choices"]}
==> The choices field is an array, as expected
After step 3 it looks like this:
"{"test":{"choices":{"1":"one"},"name":""},"isValidated":true,"validatedFields":[]}
==> The choices field now is a json value
And finally after step 4 it looks like this:
{"test":{"choices":"zero","name":""},"isValidated":true,"validatedFields":[]}
==> The choices field now has a string value
And this string value seems to be submitted to the form which triggers the invalid value error.
I have created a reproducer with this simple form here if needed: https://github.com/nklth/live-component-form-choices

Bump

Hi i found a workaround: use the PostMount and unset the initialFormData: The prefilled form works fine:
`    #[PostMount]
public function postMount(): void
{
$this->initialFormData = [];
}
protected function instantiateForm(): FormInterface
{
    return $this->createForm(YourFormType::class, $this->initialFormData);
}`


yurt-cntroller-manager's log show an error: error retrieving resource lock kube-system/yurt-controller-manager

I follow the GitHub Manually Setup doc, but I find a error in yurt-controller-manager:

error retrieving resource lock kube-system/yurt-controller-manager: leases.coordination.k8s.io "yurt-controller-manager" is forbidden: User "system:serviceaccount:kube-system:default" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system"

and I think the yurt-controller-manager is not working, because when I disconnect the yurthub on edgenode, the edgenode's status is still ready.

@xmwilldo maybe rbac setting step is missed in manually setup doc, you can exec the following command to add permission for yurt-controller-manager.
kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default


HBASE-24615 MutableRangeHistogram#updateSnapshotRangeMetrics doesn't calculate the distribution for last bucket.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m  8s
Docker failed to build yetus/hbase:7cf97016b9.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/2070

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2070/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


IIIF Browser component

See also:

#5
https://github.com/digirati-co-uk/iiif-canvas-panel/issues/90
https://github.com/digirati-co-uk/iiif-manifest-editor/wiki/IIIF-Browser

(TBC)

Prototype is at https://tomcrane.github.io/scratch/contentstate/cs.html

This would be really nice to have in v 1.0 but needs some UX assistance.

v1.0 MVP  - same as current new canvas, but accepts a Manifest, then shows a thumbnail strip.
1.x is more like https://preview.uxpin.com/cabb8dec496a444a18e1ed442230485a02c17484#/pages/148163673/simulate/sitemap?mode=i
Allows folder/file like navigation until you are in a Manifest
Allows content state selection
Is standalone component for use elsewhere.

Updated https://tomcrane.github.io/scratch/contentstate/cs.html to include "media" as a mode.
When call-to-action is media, pick media by returning list from canvas
Need to solve where this appears… is it an additional panel? A new window? A modal dialogue? You might want to keep it open to make several selections from the same or nearby sources when building a manifest. If can be launched from many places.

For Canadiana, demonstrate and review the current status of this component.
It's possible we might work more on it to allow it to be used as a "source pane" as mentioned in #133

Need to check that we cover the scenarios in https://github.com/digirati-co-uk/iiif-manifest-editor/issues/20

Additions:
New output types

Canvas list (Canvases)
Manifest list (Manifests only)
Collection item list (Collections + Manifests)

Interaction additions

Supporting multi-select using various interactions

modifier keys + click (select another, select range)
Drag box
Checkbox "mode" for selection

Possible concept of a "tray" when doing multi-select
Support for dragging items out of the explorer (uses same mechanism as copy/paste)


Avoid warnings when proper scope not included

If the scopes does not include "user-read-email", the "email" field will be empty in response and will cause an a notice "Notice: Undefined index: email in src/Oauth2/Client/Provider/Spotify.php on line 59".

@imaimai86 thanks for this contribution, and for #1 too!


Is there any way to "lock" the PDF ID value?

Question
I've an icon build system that, among various things, generates a set of PDF files. One for each icon.
It seems that at some point in the past (maybe #1110) the ID parameter was introduced.
If I update PDFkit to 0.11.0, being ID time of creation based, it means that now every time the PDF is generated, the ID changes, and our build system has all the PDFs with changes now. This isn't ideal.
Is there any way to either specify a specific timestamp (it doesn't seem to pick up doc.info.CreationDate) or not add the ID at all?
See here for more details:
https://github.com/Automattic/gridicons/pull/310
Your environment

pdfkit version: 0.11.0
Node version: 15.0.1 (but not relevant)
Operating System: macOS 10.15.7 (19H2)

The id is dependent on all info fields: see https://github.com/foliojs/pdfkit/blob/326350b7f958ed24730ce809b98dc803d3e14562/lib/security.js
See how info is build here: https://github.com/foliojs/pdfkit/blob/326350b7f958ed24730ce809b98dc803d3e14562/lib/document.js#L88-L102
Try to lock the passed info. It should get the same id

That's what's odd: I'm not changing Producer and Creator, and fixing CreationDate. Yet, it changes every rebuild.
I tried to set them all, but still nothing:
        pdf.info.Producer = "Test";
        pdf.info.Creator = "Test";
        pdf.info.CreationDate = "";

You must pass CreationDate as constructor param:
var date = new Date(0,0,0)
var pdf = new PDFDocument( { size: [ 24, 24 ], info: {CreationDate: date} } );

Thank you! That worked.
Now we are having another problem where the ID changes even if I fix the date... on a colleague laptop, but I'm not sure what it is yet.
In terms of this issue, I think it can be closed.
Thanks again. :)


Convert Azure hosting startup and integration projects to use ProjectRef

Implements #4246 for a subset of projects in src/AzureIntegration.
There is still code left in src/AzureIntegration. It's unclear if this code needs to be kept. I've started email to figure out if it's okay to delete the left over code in src/AzureIntegration which was used for these projects:

Microsoft.Extensions.ApplicationModelDetection (a package that never shipped)
Runtime SiteExtension - never shipped after 2.1.0 and 2.2.0 RTM. May not be needed in servicing
The SDK site extension which includes the SDK - never shipped after 2.1.0 and 2.2.0 RTM, and will not ship in 3.0.

Updated to remove Microsoft.Extensions.ApplicationModelDetection


Add documentation for using package sources

Some users are not familiar with NuGet package sources, so we should add some documentation to the README for this.

The following text was added to the readme in PR #151
The Latest Builds
Where to get the Nuget package
The NuGet package for Open XML SDK is currently available as a custom feed on MyGet. You can trust this package source, since the custom feed is locked and only this project feeds into the source.
How to install the Nuget package
The package you want to install is DocumentFormat.OpenXml. See https://dotnet.myget.org/gallery/open-xml-sdk
The package feed or the package source is specified by the feed URL. Depending on your version of Visual Studio, choose the appropriate feed URL from the table below.
Table 1: The latest builds are available via a MyGet feed
Client                                                            Feed URL
NuGet V3 (Visual Studio 2015+)                  https://dotnet.myget.org/F/open-xml-sdk/api/v3/index.json
NuGet V2 (Visual Studio 2012+)                  https://dotnet.myget.org/F/open-xml-sdk/api/v2
Specify the package source via a configuration option. For more info, see https://docs.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior. Note that usually a NuGet.config file is placed in the directory and the configuration options are added there to ensure the sources are persisted in the version control.
Install the package. The Install-Package command considers the package source either via configuration or argument. (If you have trouble installing the package, try restarting Visual Studio. Package sources could be cached and changes you've made to any NuGet.config files may not be detected.)
PM> Install-Package DocumentFormat.OpenXml
PM> Install-Package DocumentFormat.OpenXml -Source https://dotnet.myget.org/F/open-xml-sdk/api/v3/index.json
Note: This example is for Visual Studio 2015 and later.

This is great.
Install-Package DocumentFormat.OpenXml -Source https://dotnet.myget.org/F/open-xml-sdk/api/v3/index.json
This doesn't work though. Is there a delay here? Just want to confirm whether the documentation is correct or whether it's just a matter of time before it's resolved.

I added the version. (see below) It seems to work for me. Can you confirm if it works for you? If it does, then I'll update the README instruction.
PM> Install-Package DocumentFormat.OpenXml -Version 2.7.0-vnext0061 -Source https://dotnet.myget.org/F/open-xml-sdk/api/v3/index.json

Hello, Could someone explain, why do you use MyGet instead of Nuget? Do you plan to push 2.7.* builds to https://www.nuget.org/packages/OpenXMLSDK-MOT/ ? When?

Hi @Ivan-Grishkov . This is common practice for CI builds. MyGet is a way of hosting a private feed so you have complete control over it. NuGet is a public feed that anyone and everyone can push to. For instance, that package you link to is not an official package and not put up or supported by the Office team (AFAIK). We are definitely looking into pushing a package to NuGet, but for now, adding this package source will get you unblocked. Please be aware that when a package is listed on NuGet.org, it is the Owner field that shows you you really owns it, not the Authors - ie, the Authors field is just a field that anything can be put into.

@tomjebo I've reached out to the listed owner of that package so we can figure out where it's coming from.

"Moss and Lichens" provides the NuGet packages for OpenXMLSDK-MOT on demand. I long back used Open XML and I liked it and started providing the packages on NuGet.


Updated config validator violation to include violation message properly.

Resolves #2735

Will this cause any upgrade or release issue? (LGTM)

This will not cause any upgrade issue as the column has already been created in the violations table.


Forked JVM process for surefire has no heap space limit configured

Currently, we only set MAVEN_OPTS which is not enough.

For reference, in the existing repositories, I did not roll out this fix, because it would be necessary to apply it to all branches in all group repositories. Instead I've opted to use the JAVA_TOOL_OPTIONS environment variable. All runners have this variable set to -Xmx1G.


moved local.conf and bblayers.conf out of the meta-sol repo into the …

…manifest repo. Also removed tegra-sfm to allow for building

@alexhholmes I removed the sfm stuff for right now to allow us to build cleanly. Otherwise I just moved the bblayers.conf and local.conf to the other repo.

@Atomicchipmonk What is the reason for moving the configuration files to a different repo?

Mainly because they felt weird being global configuration files in a meta package. I dont think I am hard set on them being in either place, the conf folder just felt a little polluted (both meta-sol stuff and global stuff).
You also talk about how to make those files in the README which i think is useful and the general way yocto is advertised. The repo-manifest repo basically has our entire global environment in it, so i thought the global conf files should live there too.

Alternatively, would you be okay with me just making changes to the local.conf.template. It would have only layer specific configs that can be overwritten by an appended config that JHU can have in the manifest repo with. i.e. In local.conf.template in meta-sol MACHINE ?= rather than 'MACHINE ='.
This way we have a common layer specific template and both JHU and UGA can have our own CI repos that append changes to the common config file.

Sure! Yeah if you want to keep them in there, that works for me. I think this is a case where having it in two places doesn't hurt. Feel free to put them back in.


Custom Value Generator Which is trying to acces DI Service failed

Hi,
I am trying to implement a Custom Value generator. Whchi is getting number from other DB.
My code is as follows.
public class MyValueGenerator: ValueGenerator<int>
    {
        private ISeqDefinitionRepository _repository;

        public MyValueGenerator(ISeqDefinitionRepository repository)
        {
            _repository = repository;
        }

        public override bool GeneratesTemporaryValues => false;

        public override int Next(EntityEntry entry)
        {
            if (entry == null)
            {
                throw new ArgumentNullException(nameof(entry));
            }

            int res = _repository.NextValue(1);
            return res;
        }
    }

On Model Creating

 private void ConfigureMfr(EntityTypeBuilder<Mfr> builder)
        {
            builder.Property(b => b.MfrId).HasValueGenerator<MyValueGenerator>();
        }

I am getting following Error
Cannot create instance of value generator type 'MyValueGenerator'. Ensure that the type is instantiable and has a parameterless constructor, or use the overload of HasValueGenerator that accepts a delegate.
No parameterless constructor defined for this object.
Requesting to guide met to  get the instance of the service in custom ValueGenerator Class.
Further technical details
EF Core version: 2.0
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system:  Visual Studio 2017
Thanks & Regards,
Easwar

It would be nice to see that feature in the EF Core. I got some problem with persisting dates based on the user timezone which is a scoped service.

FYI, I've been able to access a service registered for scope using
var userProvider = entry.Context.GetService<ITeamTunerUserProvider>();

It worked for me the same way @taconaut  was proposing. You can't include the repository in the constructor of your custom value generator since the injectable type is not listed in the registered services for the service provider.
Below are the classes I used to make it work.
UserGenerator.txt
IUserProvider.txt
TestDbContext.txt
Program.txt

My code
services.TryAddSingleton<IMyLongIDGenerator, MyLongIDGenerator>();

public class MylongValueGenerator : ValueGenerator<long>
{
     //......
    public override long Next([NotNull] EntityEntry entry)
    {
        if (entry == null)
        {
            throw new ArgumentNullException(nameof(entry));
        }
        var gen = entry.Context.GetService<IMyLongIDGenerator>();
        return gen.NextValue();
    }
}

// for some single DbContext ID generator
services.AddDbContext<DBContext>(options =>{
                options.ReplaceService<IValueGeneratorSelector, MyValueGeneratorSelector>();
            };
//Or for global
//services.TryAddSingleton<IValueGeneratorSelector, MyValueGeneratorSelector>();

public class MyValueGeneratorSelector : ValueGeneratorSelector
{
    //......
    public override ValueGenerator Create(IProperty property, IEntityType entityType)
    {
        //......
        if (property.ValueGenerated != ValueGenerated.Never)
        {
            if (propertyType == typeof(long))
            {
                return new MylongValueGenerator(false);
            }
            //......
        }
    }
}

it work for EF Core version: 3.0/3.0.1


Could not find a version that satisfies the requirement ipython==6.1.0 (from -r requirements.txt (line 6))

pip install -r requirements.txt
Collecting bleach==2.0.0 (from -r requirements.txt (line 1))
Downloading bleach-2.0.0-py2.py3-none-any.whl
Collecting decorator==4.1.1 (from -r requirements.txt (line 2))
Using cached decorator-4.1.1-py2.py3-none-any.whl
Collecting entrypoints==0.2.3 (from -r requirements.txt (line 3))
Using cached entrypoints-0.2.3-py2.py3-none-any.whl
Collecting html5lib==0.999999999 (from -r requirements.txt (line 4))
Using cached html5lib-0.999999999-py2.py3-none-any.whl
Collecting ipykernel==4.6.1 (from -r requirements.txt (line 5))
Using cached ipykernel-4.6.1-py2-none-any.whl
Collecting ipython==6.1.0 (from -r requirements.txt (line 6))
Could not find a version that satisfies the requirement ipython==6.1.0 (from -r requirements.txt (line 6)) (from versions: 0.10, 0.10.1, 0.10.2, 0.11, 0.12, 0.12.1, 0.13, 0.13.1, 0.13.2, 1.0.0, 1.1.0, 1.2.0, 1.2.1, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 3.0.0, 3.1.0, 3.2.0, 3.2.1, 3.2.2, 3.2.3, 4.0.0b1, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.1.0rc1, 4.1.0rc2, 4.1.0, 4.1.1, 4.1.2, 4.2.0, 4.2.1, 5.0.0b1, 5.0.0b2, 5.0.0b3, 5.0.0b4, 5.0.0rc1, 5.0.0, 5.1.0, 5.2.0, 5.2.1, 5.2.2, 5.3.0, 5.4.0, 5.4.1, 5.5.0)
No matching distribution found for ipython==6.1.0 (from -r requirements.txt (line 6))

It looks like your pip isn't upgraded.

I get the same also after updating pip with
sudo -H pip2 install --upgrade pip
also in Mac OS sierra

This requires python3.6 (so you'll have to use pip3.6).  Also , there's no cuda support for Mac , so you'll have to make changes to the code (remove all .cuda()) calls


Build(deps-dev): Bump @types/react-dom from 17.0.12 to 17.0.13 (#3004)

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

Processing this pull request

An unexpected error occurred while processing this pull request. The request might have been partially processed. Caused by: GitHub API query failed: got errors in response: [{'type': 'UNPROCESSABLE', 'path': ['createPullRequest'], 'locations': [{'line': 2, 'column': 9}], 'message': 'A pull request already exists for inmanta:dependabot/npm_and_yarn/types/react-dom-17.0.13.'}]


Enhances readablity of arrowhead code

@theundeadmonk, nice job. Want to take a look at the comments? Should be easy changes ;-)


Codechef May Lunchtime 2021 Division 3 : Birthday Gifts (Problem Code: TWINGFT)

A question in which, basically two persons take K turns alternately to choose gifts. In a turn, a person may choose one gift. The only exception is the last turn, in which whoever moves second, he gets to choose two gifts instead of one.  We need to find the maximum total cost of the gifts that a person can keep.
For more info, here is the link to the question: https://www.codechef.com/LTIME96C/problems/TWINGFT
Can you please assign me this task, as it is a good level problem from the perspective of a newbie to CP, and will help him/her to approach to this type of questions. Please assign me this under LGMSOC'21. I would like to share my C++ code.
THANK YOU

Already we have


I24 ssx: have a clean abort process

Find a graceful way to stop a collection and exit the while loop if something goes wrong - and get the abort button to work.
At the moment, when using Ctrl+C nothing seems to happen while the abort button should not be used.
(Note: Subprocess opens up the edm screens, might need some tweaking.)

Closing as not relevant anymore


Creating KC IP Pool Page

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @Whatthefoxsays,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


RHEL-07-010492 referencing explicit EFI path

Describe the Issue
The updated RHEL-07-010492 block in fix-cat2.yml in v1.3.1 explicitly references /boot/efi/EFI/redhat/grub.cfg, which will fail on CentOS systems.
Expected Behavior
Task should succeed on CentOS.
Actual Behavior
Task fails on CentOS due to nonexistent path/file.
Control(s) Affected
RHEL-07-010492
Environment (please complete the following information):

Ansible Version: 2.9.25
Host Python Version: Python 3.6.8
Ansible Server Python Version: same
Host OS: CentOS 7.9 in UEFI mode

Possible Solution
Replace:
https://github.com/ansible-lockdown/RHEL7-STIG/blob/2b4a30c637ec4c80890e4b98984cfdf9ba7bac48/tasks/fix-cat2.yml#L893
With:
path: "{{ rhel7stig_bootloader_path }}/grub.cfg"

Hi Dan
As always thank you for highlighting this issue and supplying a resolution. I have raised a new PR for this today and hope to get this pushed through asap.
many thanks again
uk-bolly

Hi @danbarr
I just noticed i closed this in error a little early before the PR was approved. The fix is now in dev and will be rolled in main hopefully later today.
Please feel free to reopen if i have missed anything.
Many thanks
uk-bolly


Init docker registry service and package

Motivation for this change
Re-adding the docker registry service with their new software.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Fixes https://github.com/NixOS/nixpkgs/issues/14129

Ha, awesome, @globin !
I happen to have "Setup up Docker registry" on my ToDos for this month :D

This makes more sense if there are multiple versions available, to be able to choose, I don't think this necessary here.


Refactoring of KubeVirt image cloning

What this PR does / why we need it:
We need to simplify a logic of image cloning and remove KKP concepts like standard or custom images, MC should be free of this.
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?
/kind feature

Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

Enable KubeVirt image cloning over KUBEVIRT_ALLOW_PVC_CLONE and KUBEVIRT_PVC_CLONE_NAMESPACES env vars

Documentation:

NONE

/hold
didn't test yet, however @hdurand0710 it's good for a review

/retest

/approve
I like it, I let you test, but looks good!

/retest

/test pull-machine-controller-e2e-kubevirt

/test pull-machine-controller-e2e-kubevirt

/hold cancel

/retest

/lgtm
/approve


Can't Add Character

Any name I enter results in a error "configuration with that name already exists" in the new GUI

This should be fixed now

That worked, thanks.


Webpack should handle loading worker instead of setting workerSrc

When following the Webpack example and importing pdfjs-dist with import * as pdfjsLib from 'pdfjs-dist'; Webpack will create a pdfjsWorker.js and also automatically load it in the browser. The file may be named differently(hashed names, prefixes, etc.)
Still pdf.js requires to set a absolute path: pdfjsLib.GlobalWorkerOptions.workerSrc = 'pdfjsWorker.js';
This will let Webpack load the worker, and then pdf.js will also load the worker itself. Why is that the case? Instead we could just create a Worker and let Webpack do the loading?
Also i am having heavy trouble setting the workerSrc: The filename might be pdfjsWorker.js in development, but in production it has hashes and differential loading prefixes. I could use an external worker.js but then the worker(1.5mb) will be loaded twice and should not be included in Webpack bundling.

@MickL I'm facing the same. Did you find any workarounds?

No I didnt find any. I used a second, precompiled, pdfjsWorker. So as far as I see the 1.5 MB worker gets loaded twice (bundled and loaded with webpack and loaded by pdf.js again but from different source).

FWIW you can try importing import pdfjsLib from 'pdfjs-dist/webpack'; which handles the url assignment automatically. It does seem to come with a caveat though, if you're using (a newer version of) create-react-app the hot module replacement doesn't seem to be compatible right now. There is an example project I've found today: https://github.com/yurydelendik/pdfjs-react

Fantastic, thank you. You found the same resource I had been reading in my searches.
I still have to figure out what's not working but you helped me ruling out quite a few bits.
Kindest regards,
Giampaolo

Hey Giampaolo,
I'm also running into the same issue. I haven't been able to completely resolve the issue, but I was able to see that the worker-loader is trying to require the FetchCompileWasmPlugin here:
https://github.com/webpack-contrib/worker-loader/blob/master/src/index.js#L26
Seems like there may be some inconsistencies between Webpack 4 and 5?

Hey Giampaolo,
I'm also running into the same issue. I haven't been able to completely resolve the issue, but I was able to see that the worker-loader is trying to require the FetchCompileWasmPlugin here:
https://github.com/webpack-contrib/worker-loader/blob/master/src/index.js#L26
Seems like there may be some inconsistencies between Webpack 4 and 5?

Oh great pick @edcheung1 . Do you think we should raise the issue with the Webpack team and maybe open an issue?
Looking at their website I understood to ask on SO first, which I did without feedback so far, so it might be a good idea.

I'm running into the same problem here. admittedly this is a super old project with a lot of out-of-date dependencies so maybe I'm missing something, but I can't get a newer version of pdfjs-dist to work where previously I had it working by importing 'pdfjs-dist/webpack'. now after updating pdfjs-dist, worker-loader and webpack, I am getting the following output:
WARNING in ./node_modules/worker-loader/dist/index.js
Module not found: Error: Can't resolve 'webpack/lib/web/FetchCompileAsyncWasmPlugin' in '/home/rett/projects/LSCPortalFE/node_modules/worker-loader/dist'
 @ ./node_modules/worker-loader/dist/index.js
 @ ./node_modules/worker-loader/dist/cjs.js
 @ ./node_modules/pdfjs-dist/webpack.js
 @ ./app/scripts/modules/PDFJSTools.ts
 @ ./app/scripts/UploadModalCtrl.ts
 @ ./app/scripts/angular-scripts.js
 @ multi (webpack)-dev-server/client?http://localhost:9000 @babel/polyfill ./app/scripts/deps.js ./app/scripts/angular-scripts.js ./app/scripts/stylesheet-bundle.js

WARNING in ./node_modules/worker-loader/dist/index.js
Module not found: Error: Can't resolve 'webpack/lib/web/FetchCompileWasmPlugin' in '/home/rett/projects/LSCPortalFE/node_modules/worker-loader/dist'
 @ ./node_modules/worker-loader/dist/index.js
 @ ./node_modules/worker-loader/dist/cjs.js
 @ ./node_modules/pdfjs-dist/webpack.js
 @ ./app/scripts/modules/PDFJSTools.ts
 @ ./app/scripts/UploadModalCtrl.ts
 @ ./app/scripts/angular-scripts.js
 @ multi (webpack)-dev-server/client?http://localhost:9000 @babel/polyfill ./app/scripts/deps.js ./app/scripts/angular-scripts.js ./app/scripts/stylesheet-bundle.js

ERROR in (webpack)/lib/node/NodeTargetPlugin.js
Module not found: Error: Can't resolve 'module' in '/home/rett/projects/LSCPortalFE/node_modules/webpack/lib/node'
 @ (webpack)/lib/node/NodeTargetPlugin.js 11:1-18
 @ ./node_modules/worker-loader/dist/index.js
 @ ./node_modules/worker-loader/dist/cjs.js
 @ ./node_modules/pdfjs-dist/webpack.js
 @ ./app/scripts/modules/PDFJSTools.ts
 @ ./app/scripts/UploadModalCtrl.ts
 @ ./app/scripts/angular-scripts.js
 @ multi (webpack)-dev-server/client?http://localhost:9000 @babel/polyfill ./app/scripts/deps.js ./app/scripts/angular-scripts.js ./app/scripts/stylesheet-bundle.js

+1 FWIW facing the exact same error msgs mentioned above with a clean setup of create-react-app and using the App component from https://github.com/yurydelendik/pdfjs-react.

We are also facing the exact same issue after upgrading the pdfjs library,
@timvandermeij can the issue be re-opened?

vue-cli4，same error

I was able to solve the problem with the responses on
https://stackoverflow.com/questions/63553008/looking-for-help-to-make-npm-pdfjs-dist-work-with-webpack-and-django
Nevertheless, as i was still facing other issues using pdfjs with vue 3... To make it work i ended up using version 2.0.943 of the pdfjs-dist package. Not the best solution, but the only way i found to make it work after a week of trial and error...

+1 FWIW facing the exact same error msgs mentioned above with a clean setup of create-react-app and using the App component from https://github.com/yurydelendik/pdfjs-react.

Currently facing the exact same issue. Did you find a fix?

Same issue here, I followed all steps described in the sparse docs/examples and countless online blog post for old version and still no clear way to integrate pdfjs to a project.
This post shows all the hoops one went through to make it work: https://stackoverflow.com/questions/63553008/looking-for-help-to-make-npm-pdfjs-dist-work-with-webpack-and-django
Would really be nice if the dev experience was nicer, in the mean time will try to downgrade to  2.0.943 as the post above suggests ...

Here's the fix copied from SO, posted by Siddhesh on 20th October:

This issue seems to arise due to esModule option introduced in<EMAIL_ADDRESS>The fix for this was merged in (pre-release<EMAIL_ADDRESS>You can fix this by either upgrading pdfjs-dist to v2.6.347 OR downgrading worker-loader to v2.0.0

It's easiest to downgrade worker-loader, as the pdfjs-dist containing the fix has not yet been released to npm.
You can then import pdfjs-dist with:
let pdfjs = require("pdfjs-dist/webpack");
let loadingTask = pdfjs.getDocument(url);

This works for me within a Vue.js component, in a project created by vue-cli. I'm using pdfjs-dist 2.5.207 and worker-loader 2.0.0.

Here is how I imported everything pdfjs and pdfjsworker
import * as pdfjsLib from 'pdfjs-dist';
import { pdfjsWorker } from 'pdfjs-dist/webpack'

thanks @morgan4080 the solution works pretty well
below is for someone who is looking for dynamic import
import type PDFJS from 'pdfjs-dist';

let loader: Promise<typeof PDFJS>;

export default async function pdfjs() {
  if (!loader) {
    loader = new Promise((resolve, reject) => {
      import('pdfjs-dist/webpack')
        .then(() => import('pdfjs-dist/build/pdf').then(resolve))
        .catch(reject);
    });
  }

  return loader;
}

Just leave the final solution here.
import * as pdfjsLib from 'pdfjs-dist/webpack';

export const pdfView = () => {
  const loadingTask = pdfjsLib.getDocument(pdfData.myPdfDoc)

  pdfData.myPdf = loadingTask.promise.then(pdf => {
    pdfData.pdfTotalPageN = pdf.numPages;
    return pdf;
  })
}


all: Go 1.16.10 release status

Issue tracking the go1.16.10 release by releasebot.

Log
2021/11/04 08:58:58 starting
2021/11/04 08:58:58 working in /usr/local/google/home/thanm/go-releasebot-work/go1.16.10
2021/11/04 08:58:58 $ git fetch origin master
2021/11/04 08:58:59 $ git fetch origin release-branch.go1.16
2021/11/04 08:59:00 $ git clone --reference /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gitmirror -b release-branch.go1.16 https://go.googlesource.com/go /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gitwork
2021/11/04 08:59:01 $ git codereview change relwork
2021/11/04 08:59:02 $ git config gc.auto 0
2021/11/04 08:59:02 an associated security release branch "release-branch.go1.16-security" does not exist; assuming it has been merged and deleted, so proceeding as usual
2021/11/04 08:59:02 $ git rev-parse go1.16.10
2021/11/04 08:59:02 Release status issue title: "all: Go 1.16.10 release status"
2021/11/04 08:59:03 Release status issue: https://golang.org/issue/49344
2021/11/04 08:59:03 $ git add VERSION
2021/11/04 08:59:03 $ git commit -m go1.16.10

Change-Id: I872971806a723e6add42bb78f91a8ef8586f3d58
 VERSION
2021/11/04 08:59:04 $ git codereview mail -trybot -trust
2021/11/04 08:59:08 $ go clean -modcache
2021/11/04 08:59:08 $ go install golang.org/x/build/cmd/release@latest
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target windows-amd64-longtest -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-386 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-arm64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-armv6l -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target darwin-arm64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-s390x -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-386-longtest -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-ppc64le -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target windows-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target darwin-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target freebsd-386 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target windows-386 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-amd64-longtest -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target freebsd-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 08:59:31 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target src -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 09:00:21 release -target="src": build succeeded (after 0 retries)
2021/11/04 09:02:59 release -target="linux-ppc64le": build succeeded (after 0 retries)
2021/11/04 09:03:39 release -target="linux-s390x": build succeeded (after 0 retries)
2021/11/04 09:10:01 release -target="linux-arm64": build succeeded (after 0 retries)
2021/11/04 09:10:37 release -target="darwin-arm64": build succeeded (after 0 retries)
2021/11/04 09:10:45 release -target="darwin-amd64": build succeeded (after 0 retries)
2021/11/04 09:11:45 release -target="linux-armv6l": build succeeded (after 0 retries)
2021/11/04 09:13:16 release -target="windows-amd64-longtest" did not produce expected output files [go1.16.10.windows-amd64-longtest.test-only]:
error from cmd/release binary = <nil>
output from cmd/release binary:
2021/11/04 08:59:31 windows-amd64-longtest: Start.
2021/11/04 08:59:31 windows-amd64-longtest: Creating buildlet.
2021/11/04 09:00:05 windows-amd64-longtest: Pushing source to buildlet.
2021/11/04 09:00:10 windows-amd64-longtest: Installing go1.4.
2021/11/04 09:00:13 windows-amd64-longtest: Writing VERSION file.
2021/11/04 09:00:13 windows-amd64-longtest: Cleaning goroot (pre-build).
2021/11/04 09:00:13 windows-amd64-longtest: Building (make.bash only).
2021/11/04 09:01:54 windows-amd64-longtest: Cleaning goroot (post-build).
2021/11/04 09:01:54 windows-amd64-longtest: Pushing and running releaselet.
2021/11/04 09:05:51 windows-amd64-longtest: Cleaning workdir.
2021/11/04 09:05:52 windows-amd64-longtest: Installing go1.4 (second time, for all.bash).
2021/11/04 09:05:54 windows-amd64-longtest: Building (all.bash to ensure tests pass).
2021/11/04 09:13:16 windows-amd64-longtest: Error: Build failed: exit status 1
Output:
Building Go cmd/dist using C:\workdir\go1.4
Building Go toolchain1 using C:\workdir\go1.4.

Building Go toolchain2 using go_bootstrap and Go toolchain1.
Building Go toolchain3 using go_bootstrap and Go toolchain2.
Building packages and commands for windows/amd64.

##### Testing packages.
ok  	archive/tar	0.057s
ok  	archive/zip	58.480s
ok  	bufio	0.134s
ok  	bytes	2.759s
ok  	compress/bzip2	0.126s
ok  	compress/flate	13.676s
ok  	compress/gzip	0.188s
ok  	compress/lzw	0.108s
ok  	compress/zlib	1.513s
ok  	container/heap	0.048s
ok  	container/list	0.043s
ok  	container/ring	0.045s
ok  	context	0.248s
ok  	crypto	0.030s
ok  	crypto/aes	0.050s
ok  	crypto/cipher	0.249s
ok  	crypto/des	0.044s
ok  	crypto/dsa	10.604s
ok  	crypto/ecdsa	6.285s
ok  	crypto/ed25519	0.102s
ok  	crypto/elliptic	2.786s
ok  	crypto/hmac	0.032s
ok  	crypto/internal/subtle	0.026s
ok  	crypto/md5	0.025s
ok  	crypto/rand	0.252s
ok  	crypto/rc4	0.062s
ok  	crypto/rsa	1.016s
ok  	crypto/sha1	0.029s
ok  	crypto/sha256	0.026s
ok  	crypto/sha512	0.033s
ok  	crypto/subtle	0.026s
ok  	crypto/tls	5.819s
ok  	crypto/x509	2.945s
ok  	database/sql	1.579s
ok  	database/sql/driver	0.042s
ok  	debug/dwarf	0.046s
ok  	debug/elf	0.061s
ok  	debug/gosym	3.672s
ok  	debug/macho	0.032s
ok  	debug/pe	7.997s
ok  	debug/plan9obj	0.037s
ok  	embed/internal/embedtest	0.052s
ok  	encoding/ascii85	0.041s
ok  	encoding/asn1	0.032s
ok  	encoding/base32	0.055s
ok  	encoding/base64	0.030s
ok  	encoding/binary	0.055s
ok  	encoding/csv	0.030s
ok  	encoding/gob	0.048s
ok  	encoding/hex	0.054s
ok  	encoding/json	2.001s
ok  	encoding/pem	0.067s
ok  	encoding/xml	0.051s
ok  	errors	0.051s
ok  	expvar	0.061s
ok  	flag	0.209s
ok  	fmt	0.154s
ok  	go/ast	0.039s
ok  	go/build	1.690s
ok  	go/build/constraint	0.035s
ok  	go/constant	0.027s
ok  	go/doc	0.152s
ok  	go/format	0.038s
ok  	go/importer	0.301s
ok  	go/internal/gccgoimporter	0.057s
ok  	go/internal/gcimporter	5.855s
ok  	go/internal/srcimporter	7.547s
ok  	go/parser	0.087s
ok  	go/printer	0.586s
ok  	go/scanner	0.032s
ok  	go/token	0.077s
ok  	go/types	23.890s
ok  	hash	0.052s
ok  	hash/adler32	0.048s
ok  	hash/crc32	0.035s
ok  	hash/crc64	0.054s
ok  	hash/fnv	0.053s
ok  	hash/maphash	201.534s
ok  	html	0.036s
ok  	html/template	0.616s
ok  	image	0.304s
ok  	image/color	0.068s
ok  	image/draw	0.100s
ok  	image/gif	0.824s
ok  	image/jpeg	0.307s
ok  	image/png	0.803s
ok  	index/suffixarray	95.972s
ok  	internal/cpu	0.034s
ok  	internal/execabs	0.061s
ok  	internal/fmtsort	0.039s
ok  	internal/poll	1.003s
ok  	internal/profile	0.032s
ok  	internal/reflectlite	0.105s
ok  	internal/singleflight	0.056s
ok  	internal/syscall/windows	0.079s
ok  	internal/syscall/windows/registry	0.034s
ok  	internal/trace	2.308s
ok  	internal/unsafeheader	0.029s
ok  	internal/xcoff	0.056s
ok  	io	0.148s
ok  	io/fs	0.032s
ok  	io/ioutil	0.039s
ok  	log	0.032s
ok  	math	0.041s
ok  	math/big	5.128s
ok  	math/bits	0.041s
ok  	math/cmplx	0.057s
ok  	math/rand	7.698s
ok  	mime	0.074s
ok  	mime/multipart	0.968s
ok  	mime/quotedprintable	0.876s
--- FAIL: TestDialerFallbackDelay (0.67s)
    dial_test.go:433: #2: got 460.9422ms; want <= 395ms
FAIL
FAIL	net	67.363s
ok  	net/http	97.513s
ok  	net/http/cgi	0.358s
ok  	net/http/cookiejar	0.043s
ok  	net/http/fcgi	0.037s
ok  	net/http/httptest	2.303s
ok  	net/http/httptrace	0.026s
ok  	net/http/httputil	1.020s
ok  	net/http/internal	0.038s
ok  	net/http/pprof	5.296s
ok  	net/internal/socktest	0.024s
ok  	net/mail	0.027s
ok  	net/rpc	0.067s
ok  	net/rpc/jsonrpc	0.055s
ok  	net/smtp	0.046s
ok  	net/textproto	0.026s
ok  	net/url	0.031s
ok  	os	128.193s
ok  	os/exec	6.573s
ok  	os/signal	1.722s
ok  	os/user	0.036s
ok  	path	0.030s
ok  	path/filepath	0.600s
ok  	plugin	0.026s
ok  	reflect	3.728s
ok  	regexp	29.742s
ok  	regexp/syntax	0.482s
ok  	runtime	295.414s
ok  	runtime/debug	0.143s
ok  	runtime/internal/atomic	2.845s
ok  	runtime/internal/math	0.051s
ok  	runtime/internal/sys	0.028s
ok  	runtime/metrics	0.032s
ok  	runtime/pprof	74.229s
ok  	runtime/race	0.109s
ok  	runtime/trace	22.332s
ok  	sort	0.923s
ok  	strconv	2.049s
ok  	strings	1.693s
ok  	sync	6.008s
ok  	sync/atomic	4.157s
ok  	syscall	0.022s
ok  	testing	3.024s
ok  	testing/fstest	0.034s
ok  	testing/iotest	0.027s
ok  	testing/quick	0.072s
ok  	text/scanner	0.025s
ok  	text/tabwriter	0.042s
ok  	text/template	1.412s
ok  	text/template/parse	0.032s
ok  	time	9.388s
ok  	unicode	0.028s
ok  	unicode/utf16	0.031s
ok  	unicode/utf8	0.036s
ok  	cmd/addr2line	6.159s
ok  	cmd/api	18.580s
ok  	cmd/asm/internal/asm	1.425s
ok  	cmd/asm/internal/lex	0.128s
ok  	cmd/compile	9.235s
ok  	cmd/compile/internal/gc	37.703s
ok  	cmd/compile/internal/logopt	0.959s
ok  	cmd/compile/internal/ssa	202.682s
ok  	cmd/compile/internal/syntax	7.926s
ok  	cmd/compile/internal/test	0.111s
ok  	cmd/compile/internal/types	0.027s
ok  	cmd/cover	6.717s
ok  	cmd/doc	0.387s
ok  	cmd/fix	5.764s
ok  	cmd/go	162.997s
ok  	cmd/go/internal/auth	0.035s
ok  	cmd/go/internal/cache	97.032s
ok  	cmd/go/internal/fsys	0.308s
ok  	cmd/go/internal/generate	0.055s
ok  	cmd/go/internal/get	0.060s
ok  	cmd/go/internal/imports	0.028s
ok  	cmd/go/internal/load	0.049s
ok  	cmd/go/internal/lockedfile	2.505s
ok  	cmd/go/internal/lockedfile/internal/filelock	0.089s
ok  	cmd/go/internal/modconv	0.042s
ok  	cmd/go/internal/modfetch	0.694s
ok  	cmd/go/internal/modfetch/codehost	0.032s
ok  	cmd/go/internal/modfetch/zip_sum_test	0.037s
ok  	cmd/go/internal/modload	0.257s
ok  	cmd/go/internal/mvs	0.052s
ok  	cmd/go/internal/par	0.052s
ok  	cmd/go/internal/renameio	87.641s
ok  	cmd/go/internal/search	0.056s
ok  	cmd/go/internal/str	0.039s
ok  	cmd/go/internal/test	0.057s
ok  	cmd/go/internal/txtar	0.027s
ok  	cmd/go/internal/vcs	0.556s
ok  	cmd/go/internal/web	0.120s
ok  	cmd/go/internal/work	0.460s
ok  	cmd/gofmt	12.583s
ok  	cmd/internal/archive	2.417s
ok  	cmd/internal/buildid	0.525s
ok  	cmd/internal/dwarf	0.040s
ok  	cmd/internal/edit	0.048s
ok  	cmd/internal/goobj	0.034s
ok  	cmd/internal/moddeps	5.721s
ok  	cmd/internal/obj	0.245s
ok  	cmd/internal/obj/ppc64	0.485s
ok  	cmd/internal/obj/riscv	4.091s
ok  	cmd/internal/obj/s390x	0.093s
ok  	cmd/internal/obj/x86	18.548s
ok  	cmd/internal/objabi	0.050s
ok  	cmd/internal/pkgpath	0.587s
ok  	cmd/internal/src	0.037s
ok  	cmd/internal/sys	0.082s
ok  	cmd/internal/test2json	0.313s
ok  	cmd/link	50.706s
ok  	cmd/link/internal/benchmark	0.218s
ok  	cmd/link/internal/ld	51.656s
ok  	cmd/link/internal/loader	0.336s
ok  	cmd/nm	17.620s
ok  	cmd/objdump	17.011s
ok  	cmd/pack	15.166s
ok  	cmd/trace	0.708s
ok  	cmd/vet	19.501s
FAIL
go tool dist: Failed: exit status 1
2021/11/04 09:13:16 release -target="windows-amd64-longtest": waiting a bit and trying again
2021/11/04 09:14:16 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target windows-amd64-longtest -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/18f2e612835b5b71f80e94c6128c8f32dc8de24f_2691857511 -rev 18f2e612835b5b71f80e94c6128c8f32dc8de24f
2021/11/04 09:15:11 release -target="freebsd-386": build succeeded (after 0 retries)
2021/11/04 09:15:30 release -target="freebsd-amd64": build succeeded (after 0 retries)
2021/11/04 09:16:26 release -target="linux-386": build succeeded (after 0 retries)
2021/11/04 09:20:13 release -target="linux-amd64": build succeeded (after 0 retries)
2021/11/04 09:20:16 release -target="linux-amd64-longtest": build succeeded (after 0 retries)
2021/11/04 09:23:51 release -target="windows-386": build succeeded (after 0 retries)
2021/11/04 09:24:55 release -target="windows-amd64": build succeeded (after 0 retries)
2021/11/04 09:25:47 release -target="linux-386-longtest": build succeeded (after 0 retries)
2021/11/04 09:44:57 release -target="windows-amd64-longtest": build succeeded (after 1 retries)
2021/11/04 09:44:57

The prepare stage has completed.

Please review and submit https://go-review.googlesource.com/q/I872971806a723e6add42bb78f91a8ef8586f3d58
and then run the release stage.

Latest build: go1.16.10

src (tar.gz)
linux-386 (tar.gz)
linux-armv6l (tar.gz)
linux-amd64 (tar.gz)
linux-arm64 (tar.gz)
freebsd-386 (tar.gz)
freebsd-amd64 (tar.gz)
windows-386 (zip) (msi)
windows-amd64 (zip) (msi)
darwin-amd64 (tar.gz)
darwin-arm64 (tar.gz)
linux-s390x (tar.gz)
linux-ppc64le (tar.gz)
linux-386-longtest (test only) - ok
linux-amd64-longtest (test only) - ok
windows-amd64-longtest (test only) - ok

Log
2021/11/04 09:58:41 starting
2021/11/04 09:58:41 working in /usr/local/google/home/thanm/go-releasebot-work/go1.16.10
2021/11/04 09:58:41 $ git fetch origin master
2021/11/04 09:58:41 $ git fetch origin release-branch.go1.16
2021/11/04 09:58:42 $ git clone --reference /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gitmirror -b release-branch.go1.16 https://go.googlesource.com/go /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gitwork
2021/11/04 09:58:44 $ git codereview change relwork
2021/11/04 09:58:45 $ git config gc.auto 0
2021/11/04 09:58:46 an associated security release branch "release-branch.go1.16-security" does not exist; assuming it has been merged and deleted, so proceeding as usual
2021/11/04 09:58:46 Release status issue title: "all: Go 1.16.10 release status"
2021/11/04 09:58:46 Release status issue: https://golang.org/issue/49344
2021/11/04 09:58:46 $ git rev-parse go1.16.10
2021/11/04 09:59:43 $ git tag go1.16.10 23991f50b34f8707bcfc7761321bb3b0e9dba10e
2021/11/04 09:59:43 $ git push origin go1.16.10
2021/11/04 09:59:45 $ go clean -modcache
2021/11/04 09:59:46 $ go install golang.org/x/build/cmd/release@latest
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target windows-386 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-386 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target windows-amd64-longtest -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-s390x -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-armv6l -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target darwin-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target freebsd-386 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target darwin-arm64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target freebsd-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-386-longtest -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-amd64-longtest -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target windows-amd64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-arm64 -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target src -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:00:00 $ /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/gopath/bin/release -target linux-ppc64le -user thanm -version go1.16.10 -staging_dir /usr/local/google/home/thanm/go-releasebot-work/go1.16.10/release-staging/23991f50b34f8707bcfc7761321bb3b0e9dba10e_3212890390 -rev 23991f50b34f8707bcfc7761321bb3b0e9dba10e -skip_tests
2021/11/04 10:01:12 release -target="src": build succeeded (after 0 retries)
2021/11/04 10:02:08 release -target="darwin-amd64": build succeeded (after 0 retries)
2021/11/04 10:02:41 release -target="linux-arm64": build succeeded (after 0 retries)
2021/11/04 10:02:58 release -target="linux-armv6l": build succeeded (after 0 retries)
2021/11/04 10:03:40 release -target="freebsd-386": build succeeded (after 0 retries)
2021/11/04 10:03:41 release -target="linux-386": build succeeded (after 0 retries)
2021/11/04 10:03:49 release -target="linux-amd64": build succeeded (after 0 retries)
2021/11/04 10:03:59 release -target="freebsd-amd64": build succeeded (after 0 retries)
2021/11/04 10:04:13 release -target="linux-ppc64le": build succeeded (after 0 retries)
2021/11/04 10:04:31 release -target="linux-amd64-longtest": build succeeded (after 0 retries)
2021/11/04 10:05:15 release -target="darwin-arm64": build succeeded (after 0 retries)
2021/11/04 10:05:52 release -target="linux-386-longtest": build succeeded (after 0 retries)
2021/11/04 10:07:02 release -target="windows-amd64-longtest": build succeeded (after 0 retries)
2021/11/04 10:09:40 release -target="windows-386": build succeeded (after 0 retries)
2021/11/04 10:10:52 release -target="windows-amd64": build succeeded (after 0 retries)
2021/11/04 10:24:49 release -target="linux-s390x": build succeeded (after 0 retries)
2021/11/04 10:24:53 creating milestone titled "Go1.16.11"
2021/11/04 10:24:53 changing milestone of issue 43941 to Go1.16.11
2021/11/04 10:24:54 changing milestone of issue 48115 to Go1.16.11
2021/11/04 10:24:54 closing milestone Go1.16.10
2021/11/04 10:24:55

The release stage has completed. Thanks for riding with releasebot today!

Please refer to the playbook for the next steps.


IIS Windows 10?

Can't find where to install IIS on windows 10
Andy Crawford
<EMAIL_ADDRESS>

I think you're in the wrong repo :)

Starting a new project, called Hello WWW.


Marketing API: Ads support for account operations and account insights.

Hello,
I started some work towards implementing Marketing API in Spring Social Facebook. This is the first part. It's adding support for account operations. I also just wanted to see if you have some issues with my way of integrating existing code with new Marketing API implementation.
I formatted code using your settings. I signed the individual contributor agreement.

Hi,
while create a adSet, a FacebookApiException occured, which said that 'When creating an ad set within a campaign using this objective, a promoted object must be specified.'. I think that u missing setting the Promoted Object, check this for reference: https://developers.facebook.com/docs/marketing-api/adset/v2.3

Hi,
I like your work and looking forward to more your splendid implements of Marketing API, I wonder that whether you have a schedule for the following work.

Hi,
first of all thank you for checking out my code. Secondly, you are right about the promoted_object field missing in ad set. I was focused on targeting field and missed the required field (in most cases I guess). I will add it in a moment.
In case of your second question: there is no schedule. As you may see I have finished core functionality (I have added ads support). I need to contact with Craig Walls and ask him to validate my work. In future I plan to add/refactor some things.. so stay in touch and please test this code ;-)

+1 for this

@sebast26 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@sebast26 Thank you for signing the Contributor License Agreement!


Assembly not strong named signed

In order to use the NuGet in a solution where the projects are signed to avoid assembly conflicts the assembly output must be signed.
https://docs.microsoft.com/en-us/dotnet/standard/assembly/strong-named

Hello @bubavanhalen,
We have released a signed version for Wallee 2.2.0 moving forward.
https://www.nuget.org/packages/Wallee/
Regards,
@vttn


Clicked event in CachedImage

Hi, I use your sample at "ListPage". I want show big picture when I click Image in listview, but I can't find event "Clicked" of CachedImage. How can I do it?
Thanks.

Just as any other Xamarin.Forms view - uou should just assign a new TapGestureRecognizer for it. Here: https://developer.xamarin.com/guides/xamarin-forms/user-interface/gestures/tap/


[SPARK-40621][PS] Implement numeric_only and min_count in GroupBy.sum

What changes were proposed in this pull request?
Implement numeric_only and min_count in GroupBy.sum
Why are the changes needed?
for API coverage
Does this PR introduce any user-facing change?
new parameter
In [2]: df = ps.DataFrame({"A": [1, 2, 1, 2], "B": [True, False, False, True], "C": [3, 4, 3, 4], "D": ["a", "a", "b", "a"]})

In [3]: df.groupby("A").sum(numeric_only=False).sort_index()
/Users/ruifeng.zheng/Dev/spark/python/pyspark/pandas/utils.py:975: PandasAPIOnSparkAdviceWarning: GroupBy.sum() can only support numeric and bool columns even ifnumeric_only=False, skip unsupported columns: ['D']
  warnings.warn(message, PandasAPIOnSparkAdviceWarning)

   B  C
A
1  1  6
2  1  8

In [4]: df._to_pandas().groupby("A").sum(numeric_only=False).sort_index()
Out[4]:
   B  C   D
A
1  1  6  ab
2  1  8  aa

In [5]: df.groupby("D").sum(min_count=3).sort_index()
Out[5]:
     A    B     C
D
a  5.0  2.0  11.0
b  NaN  NaN   NaN

In [6]: df._to_pandas().groupby("D").sum(min_count=3).sort_index()
Out[6]:
     A    B     C
D
a  5.0  2.0  11.0
b  NaN  NaN   NaN

How was this patch tested?
added UT

Merged to master.

@HyukjinKwon thank you for reviewing!


downloaded and deployed the loan-approval can't start an instance:  Form failure: Not Found

Hi,
I downloaded and deployed the loan-approval but everytime I want to start an instance:  Form failure: Not Found
any idea what could be wrong?
server 7.5.0 with tomcat on OS X -- nothing configured, all standard.. as by the tutorial
compare: http://stackoverflow.com/questions/39705594/downloaded-and-deployed-the-tutorial-but-cant-start-instance-form-failure-not

Hi, please raise this question in the forum (http://forum.camunda.org)


Uncaught SyntaxError: ambiguous indirect export

hi,
i'm using vite-plugin-commonjs with an established project, but what i find is that require()s of this form:
const { s6e } = require('./utils');

produce code which causes the following error:
Uncaught SyntaxError: ambiguous indirect export

if i change my code to:
const utils = require('./utils');
const s6e = utils.s6e;

then it works. is there a way vite-plugin-commonjs can handle this automatically, or do i need to modify all my code?
with thanks

Hi! 👋
Can you provide a minimal reproduction Demo? 👀

<!DOCTYPE html>
<html lang="en">
    <script type="module" src="/main.js"></script>
  </body>
</html>

// main.js

const { fred } = require('./one');
console.log(fred);

// one.js

module.exports = { fred: 4, jim: 6 };

// vite.config.js

import { defineConfig } from 'vite';

import commonjs from 'vite-plugin-commonjs';
import vitePluginRequire from 'vite-plugin-require';

export default defineConfig({
  plugins: [
    // vitePluginRequire.default(),  // transform require()s
    commonjs(),           // transform module.exports
  ],
});

then if i start vite and navigate to localhost:5173 i receive the error ambiguous indirect export: fred
if i navigate to localhost:5173/main.js i see that it has been transformed to:
import { fred } from '/one.js';
console.log(fred);

which doesn't work ...
HOWEVER, i've since discovered that i can use the vite-plugin-require to get this to work:
export default defineConfig({
  plugins: [
    vitePluginRequire.default(),  // transform require()s
    commonjs(),           // transform module.exports
  ],
});

it transforms the require() and commonjs transforms the module.exports.
vite-plugin-require transforms main.js so it looks like:
import vitePluginRequire_1668060469992_650 from "/one.js";
const {
  fred
} = (vitePluginRequire_1668060469992_650);
console.log(fred);

... and this works!

I will Debug it :)

Now, v0.6.0 is available :)

are there any options i need to provide to get this to work? I'm getting this same error currently and i stumbled upon this and tried with the latest version as of now ^0.10.1 but it doesn't work. still get
Uncaught SyntaxError: ambiguous indirect export: getErrorMessage
with this code
import { getErrorMessage } from "@app/utils";

when i change it to
import * as utils from "@app/utils";
const { getErrorMessage } = utils;

the error goes away (from this one at least. still happens in the many other places i try to import like that

@kyle-belle can you provide a minimal reproduction repo?

The issue isn't with this lib as im not sure it was ever meant to solve my specific issue
i found a way to get my imports to work when importing my other commonJs modules (written in typescript so really the source is more like esm really). since vite doesn't really need the built files i just redirect any request using import to use the source files using the package.json exports property.
{
  "name": "@app/utils",
  "private": true,
  "version": "1.0.0",
  "description": "App's util functions",
  "main": "build/index.js",
  "exports": {
    ".": {
      "types": "./index.ts",
      "require": "./build/index.js",
      "import": "./index.ts"
    },
    "./src/": {
      "types": "./src/",
      "require": "./build/src/",
      "import": "./src/"
    }
  },
  "scripts": {
    "clean-build": "yarn rimraf build",
    "build": "yarn tsc",
    "watch": "tsc --watch"
   }
}

Actually quick question. i now realize im using import rather than require. is it supposed to enable imports to to work with commonJs files or is it just not possible?

Your confusion exists, as ESM and CJS are not 💯% compatible.
Many times, fixed module-imterop can only be used, such as import * as lib from 'cjs-lib, even Vite can only do so.
See Vite source code 👉 https://github.com/vitejs/vite/blob/v5.0.2/packages/vite/src/node/plugins/importAnalysis.ts#L915

Hi! Got the same errors with this project https://github.com/anse-app/anse
Uncaught (in promise) SyntaxError: ambiguous indirect export: setProperty [Markdown.tsx:3:10](http://localhost:3002/src/components/Markdown.tsx) Uncaught (in promise) SyntaxError: ambiguous indirect export: setProperty 2 [SettingsApiKey.tsx:7:10](http://localhost:3002/src/components/ui/SettingsApiKey.tsx)


write: ensure id's are used with the correct table

Add a BaseId field to all tables and id types, and check these
match when using the id to access to a table entry.
Makes it easier to diagnose #377

Coverage decreased (-0.02%) to 87.162% when pulling 4413391e75bfa155bc6a446e81326e5a6cb9ba39 on philipc:base-id into c679a14781e40a937414c94ae30d691c5378fc86 on gimli-rs:master.


Synchronize ci.suse.de jobs with japi fetch-all

Does this mean people have been bypassing this git repo and changing the config on the server directly?  I thought we wanted to avoid that, but it's very likely I'm misunderstanding something ...

@aspiers Changing the jobs only in XML is cumbersome. We ususally change via webUI and then commit the changes to git. So the git repo is just the backup.

Well I backup the jobs to our internal backup as well. So this is kind of duplication. But it makes the jobs public (which our internal backups are not, obviously). Maybe we need to rethink this topic again.

OK I see, thanks for the info.  Looks like scripts/jenkins/ci.suse.de/cloud-mkcloud5-ovsvxlan-trigger.xml was the added trigger required by the story for adding VXLAN support.

So :+1:
But I think it would be better in the long run to have an automated machanism, that fetches the jobs and in case of changes puts them into a git repo (not necessarily this one, but we should include the job history of this repo).

Just for the record: There is jenkins-job-builder (https://pypi.python.org/pypi/jenkins-job-builder/1.1.0) which is used by openstack to define the jenkins jobs. it uses yaml for that. Seems to be a good alternative to the xml format.

Thanks for the link. We stopped building jobs via scripts a while ago (all trigger jobs for cloud 1 and 2 were generated). Anyhow I hope that we maintain and improve our infrastructure and CI setup in a way that we do not need a jenkins job creator in the first place.


Improve codegen performance

Requested feature: Compilation can take more time than the actual verification.
Use case: Users verifying harnesses where the potential reachable set of instructions is high despite the low harness coverage.
Link to relevant documentation (Rust reference, Nomicon, RFC):
Test case:
Cargo.toml:
# Copyright Kani Contributors
# SPDX-License-Identifier: Apache-2.0 OR MIT

[package]
name = "performance"
version = "0.1.0"
edition = "2021"

[dependencies]
anyhow = "1"

src/lib.rs
celinval@truffles:/tmp/assess/proof-works$ cat src/lib.rs
// Copyright Kani Contributors
// SPDX-License-Identifier: Apache-2.0 OR MIT

use anyhow::*;

#[kani::proof]
fn proof_using_anyhow() {
    let _ = Ok(()).context("words");
}

Running cargo kani takes about 35s to compile but around 6s to actually verify the code. Using the code from #1972
$ cargo kani --verbose 2>&1 | /bin/grep -e "Finished"
INFO kani_compiler::codegen_cprover_gotoc::compiler_interface Finished reachability analysis in 0.000000266s
INFO kani_compiler::codegen_cprover_gotoc::compiler_interface Finished reachability analysis in 0.18315084s
INFO kani_compiler::codegen_cprover_gotoc::compiler_interface Finished codegen in 6.1482673s
INFO kani_compiler::codegen_cprover_gotoc::compiler_interface Finished symtab2gb in 26.552908s
    Finished dev [unoptimized + debuginfo] target(s) in 35.06s
Finished cargo in 35.10514s
Finished goto-cc in 4.792684s
Finished goto-cc in 4.5120525s
Finished goto-instrument in 5.182001s
Finished goto-instrument in 5.2142944s
Finished goto-instrument in 4.422661s
Finished run_cmbc in 6.745211s

edit: Running with release version of Kani, the compilation time drops considerably and it's dominated by the call to symtab2gb.

The issue tracked here has been solved by #2205. I'll create another issue to track further compiler time optimizations


protostar can't build because of duplicated storage_variable in cairo_contracts

Protostar version

Name
Version

Protostar
PROTOSTAR_VERSION

Cairo-lang
CAIRO_LANG_VERSION

Git
GIT_VERSION

Current Behavior

(env) air:3sbt thomas$ protostar build
Building projects' contracts FAILED
19:23:40 [ERROR] Protostar couldn't compile 'merkle_nft' contract
/Users/thomas/workspace/starknetid/3sbt/lib/cairo_contracts/src/openzeppelin/introspection/erc165/library.cairo:13:6: Found more than one storage variable with the same name ('ERC165_supported_interfaces').
func ERC165_supported_interfaces(interface_id: felt) -> (is_supported: felt) {
     ^*************************^
/Users/thomas/workspace/starknetid/3sbt/lib/cairo_contracts/src/openzeppelin/introspection/erc165/library.cairo:13:6: Note: another definition appears here.
func ERC165_supported_interfaces(interface_id: felt) -> (is_supported: felt) {
     ^*************************^
19:23:40 [INFO] Execution time: 1.66 s

Expected Behavior

Steps to Reproduce

clone https://github.com/starknet-id/3sbt
protostar install
protostar build or test

I am not sure if Protostar can do something about this. IMO, this is a design issue of Cairo-lang or OZ library. Cairo 1 may fix this issue.