Wandb Logger does not work unless pytorch is installed

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing feature)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes

PLwandb logger initialization in getter only when it's needed
Related Issue

Closing issues

closes #335

https://colab.research.google.com/drive/1heiAllLriCf5JKjr4R9gbSmAWg5SEaWG?usp=sharing

Codecov Report

Merging #340 (472b096) into master (af51f3e) will decrease coverage by 33.50%.
The diff coverage is 16.66%.

:exclamation: Current head 472b096 differs from pull request most recent head 05fb5b5. Consider uploading reports for the commit 05fb5b5 to get more accurate results

@@             Coverage Diff             @@
##           master     #340       +/-   ##
===========================================
- Coverage   87.67%   54.17%   -33.51%
===========================================
  Files          98       98
  Lines        4820     4818        -2
===========================================
- Hits         4226     2610     -1616
- Misses        594     2208     +1614

Impacted Files
Coverage Δ

etna/loggers/wandb_logger.py
32.18% <0.00%> (-1.53%)
:arrow_down:

etna/loggers/__init__.py
100.00% <100.00%> (ø)

etna/commands/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

etna/commands/backtest_command.py
0.00% <0.00%> (-96.43%)
:arrow_down:

etna/commands/forecast_command.py
0.00% <0.00%> (-92.00%)
:arrow_down:

etna/commands/__main__.py
0.00% <0.00%> (-87.50%)
:arrow_down:

etna/commands/resolvers.py
0.00% <0.00%> (-80.00%)
:arrow_down:

etna/analysis/outliers/density_outliers.py
22.72% <0.00%> (-75.00%)
:arrow_down:

etna/transforms/fourier.py
27.08% <0.00%> (-72.92%)
:arrow_down:

etna/transforms/statistics.py
27.50% <0.00%> (-71.67%)
:arrow_down:

... and 60 more

Continue to review full report at Codecov.

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


chore: upgrade chalk to v4

Summary
Chalk 4 removed the LevelEnum which caused a TS error when using --isolatedModules see: https://github.com/chalk/chalk/pull/373
Test plan
Green CI

Seems chalk 4 drops compatibility with node < 10 :(

Yup, this'll have to wait for Jest 26. Would love to add isolatedModules to our own config at that point, chalk was the only blocker for us


Installation Skyopolis 4 via Curseforge gives mismatched mod channel list

Downloaded the server files archive for https://www.curseforge.com/minecraft/modpacks/skyopolis-4/files and placed in a modpack volume. The server boots up, but it appears to not have any mods in it (/mods folder empty). When connecting to the server the mismatched mod channel list error is given.
Have tried the server archive locally on windows machine and works correctly.

Well, this is a new variant...the modpack includes an install.sh that is very helpful but new to me:
#!/bin/sh

wget -O forge.jar https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.16.5-36.0.46/forge-1.16.5-36.0.46-installer.jar

java -jar forge.jar --installServer

clear

rm forge.jar
rm installer.log

mkdir -p mods

wget -O mods/jei-1.16.4-<IP_ADDRESS>.jar https://edge.forgecdn.net/files/3136/600/jei-1.16.4-<IP_ADDRESS>.jar
wget -O mods/AppleSkin-mc1.16.2-forge-1.0.14.jar https://edge.forgecdn.net/files/3035/787/AppleSkin-mc1.16.2-forge-1.0.14.jar
wget -O mods/ftb-backups-<IP_ADDRESS>.jar https://edge.forgecdn.net/files/3038/811/ftb-backups-<IP_ADDRESS>.jar
wget -O mods/woodenutilities-1.0.6-1.16.4.jar https://edge.forgecdn.net/files/3109/27/woodenutilities-1.0.6-1.16.4.jar

I'll have to add support for that.

I added support for the install.sh however with https://www.curseforge.com/minecraft/modpacks/skyopolis-4/files/3271144 mine crashes on startup, so I was wondering what version of the modpack worked for you.
Fails with:
[15:38:16] [Server thread/ERROR] [minecraft/MinecraftServer]: Encountered an unexpected exception
java.util.ConcurrentModificationException: null
	at java.util.LinkedHashMap$LinkedHashIterator.nextNode(Unknown Source) ~[?:?] {}
	at java.util.LinkedHashMap$LinkedEntryIterator.next(Unknown Source) ~[?:?] {}
	at java.util.LinkedHashMap$LinkedEntryIterator.next(Unknown Source) ~[?:?] {}
	at net.minecraftforge.common.ForgeConfigSpec.correct(ForgeConfigSpec.java:236) ~[forge:?] {re:classloading}
	at net.minecraftforge.common.ForgeConfigSpec.isCorrect(ForgeConfigSpec.java:139) ~[forge:?] {re:classloading}
	at net.minecraftforge.common.ForgeConfigSpec.setConfig(ForgeConfigSpec.java:85) ~[forge:?] {re:classloading}
	at net.minecraftforge.fml.config.ModConfig.setConfigData(ModConfig.java:86) ~[forge:?] {re:classloading}
	at net.minecraftforge.fml.config.ConfigTracker.openConfig(ConfigTracker.java:105) ~[forge:?] {re:classloading}
	at net.minecraftforge.fml.config.ConfigTracker.lambda$loadConfigs$1(ConfigTracker.java:83) ~[forge:?] {re:classloading}
	at java.lang.Iterable.forEach(Unknown Source) ~[?:?] {}
	at java.util.Collections$SynchronizedCollection.forEach(Unknown Source) ~[?:?] {}
	at net.minecraftforge.fml.config.ConfigTracker.loadConfigs(ConfigTracker.java:83) ~[forge:?] {re:classloading}
	at net.minecraftforge.fml.server.ServerLifecycleHooks.handleServerAboutToStart(ServerLifecycleHooks.java:95) ~[forge:?] {re:mixin,re:classloading}
	at net.minecraft.server.dedicated.DedicatedServer.func_71197_b(DedicatedServer.java:166) ~[?:?] {re:classloading,pl:accesstransformer:B}
	at net.minecraft.server.MinecraftServer.func_240802_v_(MinecraftServer.java:621) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:the_bumblezone.mixins.json:entities.MinecraftServerMixin,pl:mixin:APP:globaldataandresourcepacks.mixins.json:MinecraftServerMixin,pl:mixin:APP:jaopca.mixins.json:MinecraftServerMixin,pl:mixin:A,pl:runtimedistcleaner:A}
	at net.minecraft.server.MinecraftServer.lambda$startServer$0(MinecraftServer.java:232) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:the_bumblezone.mixins.json:entities.MinecraftServerMixin,pl:mixin:APP:globaldataandresourcepacks.mixins.json:MinecraftServerMixin,pl:mixin:APP:jaopca.mixins.json:MinecraftServerMixin,pl:mixin:A,pl:runtimedistcleaner:A}
	at java.lang.Thread.run(Unknown Source) [?:?] {}

I added support for the install.sh however with https://www.curseforge.com/minecraft/modpacks/skyopolis-4/files/3271144 mine crashes on startup, so I was wondering what version of the modpack worked for you.

nm, maybe it's because I was using java 11

I've downloaded and tested the java8 branch, the project now runs. Thank you for quick thinking and off course the fix. Keep up the good work!


provide median() operator or note how to get it with quantile(0.5)

Currently, the quantile operator is provided, but there's no median. The median according to https://prometheus.io/docs/practices/histograms/ is trivially quantile(0.5, ...). Can you please consider either adding a new median operator to do this, or adding a note to quantile in the docs https://prometheus.io/docs/prometheus/latest/querying/operators/ for users that don't know this?
Thank you.

Since it's so easy to do with the existing quantile function, I don't think
we need a new one.
For mentioning this, can you please make a PR in <
https://github.com/prometheus/docs>?
On Sat, Feb 3, 2018, 20:08 Ted Zlatanov<EMAIL_ADDRESS>wrote:

Currently, the quantile function is provided, but there's no median. The
median according to https://prometheus.io/docs/practices/histograms/ is
trivially quantile(0.5, ...). Can you please consider either adding a new
median function to do this, or adding a note to quantile in the docs
https://prometheus.io/docs/prometheus/latest/querying/operators/ for
users that don't know this?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/3791, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAICBhBikTUUqIawd3NmX2BDyzTYqrnOks5tRK69gaJpZM4R4SUq
.

The operators.md reference was not in the docs repo so I created https://github.com/prometheus/prometheus/pull/3792 which should resolve it trivially.
Thanks.

With #3792 closed, I'll try to craft a docs PR that might find more acceptance.


Fix target reference secrets

This addresses the comment in #27794  regarding secret reference targets.
Refs #28516

/cc @stevvooe

/cc @diogomonica

This was the change I was looking for. LGTM

sweet thx

LGTM

Merging this PR into another change related here: https://github.com/docker/docker/pull/28556
Closing this one.


[BEAM-13666] Stuck inventory jobs should be cancelled and rescheduled for next run

As Valentyn mentioned on the Jira Ticket, if a worker is marked as temporarily offline and an Inventory job started during that process, then the job is going to stuck and it's necessary to cancel it manually and run it again later, even if the worker is back online it can not retake the job.
The reason behind that was the eligibility option set in the code, Eligibility options , by changing it to all nodes the job will continue it's execution after the worker is online again.
This change doesn't affect the stablished workers-job mapping, as the allowed nodes and default node options are already set.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Thank you!


Unable to list individual directory

akamai netstorage list "/xxxx/roy/", is not listing the contents of the "roy" directory. Instead, it lists all

I see this issue too, and actually it looks like what is listed is the directory you provide plus all the directories after it in alphabetical order. Is there an ETA?


[Improvement](bloom filter) inline function call

Proposed changes
before：

after：

Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Cluster build is failing on Mac

Below is the error I get when I try to build cluster on a Mac using UEFI_SUPPORT branch.
#### Cobbler Boot
+ printf 'Snapshotting pre-Cobbler and booting (unless already running)\n'
Snapshotting pre-Cobbler and booting (unless already running)
+ vms_started=False
+ for i in 1 2 3
+ vboxmanage showvminfo bcpc-vm1
+ grep -q '^State:.*running'
+ vms_started=True
+ vboxmanage showvminfo bcpc-vm1
+ grep -q '^State:.*running'
+ VBoxManage snapshot bcpc-vm1 take Shoe-less
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 8516c2f2-7248-4fa4-b029-28da7e577e70
+ vboxmanage showvminfo bcpc-vm1
+ grep -q '^State:.*running'
+ VBoxManage startvm bcpc-vm1 --type headless
Waiting for VM "bcpc-vm1" to power on...
VM "bcpc-vm1" has been successfully started.
+ for i in 1 2 3
+ vboxmanage showvminfo bcpc-vm2
+ grep -q '^State:.*running'
+ vms_started=True
+ vboxmanage showvminfo bcpc-vm2
+ grep -q '^State:.*running'
+ VBoxManage snapshot bcpc-vm2 take Shoe-less
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 18a88a67-6a9c-4608-a9a9-be6e1c9c91fe
+ vboxmanage showvminfo bcpc-vm2
+ grep -q '^State:.*running'
+ VBoxManage startvm bcpc-vm2 --type headless
Waiting for VM "bcpc-vm2" to power on...
VM "bcpc-vm2" has been successfully started.
+ for i in 1 2 3
+ vboxmanage showvminfo bcpc-vm3
+ grep -q '^State:.*running'
+ vms_started=True
+ vboxmanage showvminfo bcpc-vm3
+ grep -q '^State:.*running'
+ VBoxManage snapshot bcpc-vm3 take Shoe-less
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Snapshot taken. UUID: 1cb36c34-0754-4043-a7b8-ac96fa96e798
+ vboxmanage showvminfo bcpc-vm3
+ grep -q '^State:.*running'
+ VBoxManage startvm bcpc-vm3 --type headless
Waiting for VM "bcpc-vm3" to power on...
VM "bcpc-vm3" has been successfully started.
+ echo 'Checking for GNU screen to watch serial consoles'
Checking for GNU screen to watch serial consoles
+ hash screen
+++ dirname tests/automated_install.sh
++ readlink -f tests
readlink: illegal option -- f
usage: readlink [-n] [file ...]
+ pushd
tests/automated_install.sh: line 79: pushd: no other directory

Mac OS X likely does not support readlink.

Not a great answer but perhaps a Mac user can try: Stack Overflow #4031502?


[BugFix][Cherry-pick][Branch-3.0] Fix incorrect estimation of average row size when doing partial update (#27485)

When we do partial update, we first write a partial rowset and we will load the left columns data into memory during the following apply phase and we process the rowset data by segment. So if one segment file has too many rows, a large memory is needed. So we will get the average row size of historical data to avoid large memory alloc.
The following code is how we get the average row size. However, when we do partial update, the data_size is the compressed partial rowset data size which far less than total row size, so the average_row_size may far less than real average row size. So we may write too many rows into one segment which cause large memory alloc.
int64_t TabletUpdates::get_average_row_size() {
    TTabletInfo info;
    get_tablet_info_extra(&info);
    int64_t total_row = info.row_count;
    int64_t total_size = info.data_size;
    if (total_row != 0) {
        return total_size / total_row;
    } else {
        return 0;
    }

This pr fix the issue and return the correct average row size of historical data.

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)


[cdk-connected-overlay] add animation support on opening and closing

Feature Description
Reference to closed issue [cdk-connected-overlay] add animation support on opening and closing #5127
Provide a brief summary of the feature you would like to see.
Use Case
Describe the use case(s) that the proposed feature would enable.
Currently it is not possible to animate an open and close transition when using cdk-connected-overlay. While you can animate the content inside the overlay you can't animate the cdk overlay transition itself so it looks pretty wonky and unappealing. The overlay itself is what should be animated not the content.
Maybe something like this would be great!
[cdkConnectedOverlayTransitionIn]="180ms ease-in "
[cdkConnectedOverlayTransitionOut]="200ms ease-out "

It's already possible to animate it using Angular animations. You can see an example in the mat-select component.

Closing because this issue has been inactive for 2 weeks or more after follow up was requested.


[PostgreSQL] New api version 2023-03-01-preview - Migrations API property update, enum values update. Network property changes ported.

ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[X ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

Added fix for network property update from the earlier version to new api version 2023-03-01-preview for which SDK is not yet published.

Migrations api enum property values are being updated from Enabled / Disabled to True / False.

Added 2 new string properties to SecretParameters object for Migrations api.

Added breaking change review => Scenario 23568995: [PostgreSQL] Breaking changes - Add changes to new preview api version for which there is no SDK yet

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. ASAP
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[X ] I commit to follow the Breaking Change Policy of "no breaking changes"
[X ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Hi @ambrahma, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback. Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

Added breaking change review => Scenario 23568995: [PostgreSQL] Breaking changes - Add changes to new preview api version for which there is no SDK yet

@konrad-jamrozik can we approve the Avocado error?

@konrad-jamrozik Konrad Jamrozik FTE can we approve the Avocado error?

Avocado provides guidance how to address failures it reported, here:

https://github.com/Azure/azure-rest-api-specs/pull/24087/checks?check_run_id=13682788071
https://github.com/Azure/azure-rest-api-specs/pull/24087#issuecomment-1558618327

@ambrahma can you follow the guidance provided above and if you think it is incorrect or doesn't apply, clarify why? Thanks!

@konrad-jamrozik Konrad Jamrozik FTE can we approve the Avocado error?

Avocado provides guidance how to address failures it reported, here:

https://github.com/Azure/azure-rest-api-specs/pull/24087/checks?check_run_id=13682788071
[PostgreSQL] New api version 2023-03-01-preview - Migrations API property update, enum values update. Network property changes ported. #24087 (comment)

@ambrahma can you follow the guidance provided above and if you think it is incorrect or doesn't apply, clarify why? Thanks!

Guidance says that I need to consult API review team (which is essentially a group I need to join and get approval) to take up this change. I am worried how long will this take overall for approval etc. The fixes in this PR are required for SDK release for api version 2023-03-01-preview and I do not want to miss current cycle. I am also checking with my team if this is ok and what will be implications for the end users who would already be using the same SDK for different services?

@konrad-jamrozik Konrad Jamrozik FTE can we approve the Avocado error?

Avocado provides guidance how to address failures it reported, here:

https://github.com/Azure/azure-rest-api-specs/pull/24087/checks?check_run_id=13682788071
[PostgreSQL] New api version 2023-03-01-preview - Migrations API property update, enum values update. Network property changes ported. #24087 (comment)

@ambrahma can you follow the guidance provided above and if you think it is incorrect or doesn't apply, clarify why? Thanks!

Guidance says that I need to consult API review team (which is essentially a group I need to join and get approval) to take up this change. I am worried how long will this take overall for approval etc. The fixes in this PR are required for SDK release for api version 2023-03-01-preview and I do not want to miss current cycle. I am also checking with my team if this is ok and what will be implications for the end users who would already be using the same SDK for different services?

hi @konrad-jamrozik , I have started another PR for this folder structure change. Basically we want to make sure that same python SDK gets generated for both postgresql single server and postgresql flexible server. This is to avoid downstream issues like letting customers know that there is separate (python SDK) package created for postgresql flexible server vs single server. Also then we need to worry about consuming multiple packages for CLI as currently even our CLI releases are couple together. Moreover currently MySQL single server and MySQL flexible servers are also using same packages. This would be a bigger item. Hence requesting you to allow this current PR to be merged manually, while the issues get ironed out in another PR. Also this will ensure that we do not miss the deadline for the current SDK release and make packages and CLI available to our end users as per our commitments

Hi @konrad-jamrozik , thanks for reviewing this pr, however, the multiple tag is not introduced in this pr, we support both single server and flexible server so we have two tags for both scenario. Could you kindly help to approve this avocado errors? Many thanks.

@rkmanda @weshaggard can you advise with priority?

@ambrahma I'm going to merge your PR but please continue your work on fixing the errors otherwise this will continue to come up and eventually end up blocking you.


Make standalone APK available from the Github releases page

Feature request.

To support this issue, a request for packaging has been made at F-Droid, please see https://gitlab.com/fdroid/rfp/issues/604

Unfortunately, there are too many binaries as you can see via the link above. An alternative is to setup an F-Droid for this app like e.g. http://www.cgeo.org/ has done.

@PanderMusubi we are discussing this matter today, thank you.

Gutyn closed this on Jun 13, 2018

@Gutyn will you please not close issues until they are solved, especially when it's not settled for 2+ years afterwards? Thank you. I'm requesting a re-opening.

@leafcutterant If your original request is still unresolved, open a new issue and we can discuss it.  Please be descriptive as it's unclear what you're requesting here.  If this is about F-Droid/Play Services then see here.


Download stories when --load-cookies is used

Fixes #2259.
Stories could only be downloaded if --login was used. I changed this to either --login or --load-cookies, which also logs the user in.
Otherwise the user needed to run Instaloader first just to import the cookies, and a second time (using the saved session) to actually download stories.
I've also changed error messages and the documentation in several places to refer to the process of logging in rather than to --login directly, but if you think that is too confusing, feel free to discard that commit.

Is it just a proof of concept? No
Is the documentation updated (if appropriate)? Yes
Do you consider it ready to be merged or is it a draft? Ready
Can we help you at some point? There's nothing I need help for, but I'm open to suggestions.

Thanks!
I also like the changes to the documentation and the wordings in output messages. To me it seems they make the program easier to understand and more user-friendly.


(v1.1.2) strings_en.arb is generated for non dart/flutter projects

After updating the plugin to V1.1.2, the plugin creates strings_en.arb for all Android Studio projects, even a new blank android project without dart or flutter. The file gets instantly regenerated after deleting.

Thanks for the heads up! I'll check this asap and submit a new version.

This is now fixed in #107 and submitted to JetBrains plugins repo. Hopefully it'll appear by tomorrow and you can upgrade.

Still exists on version v.1.1.4-191

Something in your environment is different than mine then because it doesn't happen here. I tested with many Android projects... There's a strict check in the Kotlin code for a Flutter-only project.
Can you check if a Flutter or Dart module is listed inside .idea/modules.xml file?

Hi, i am facing the same issue, any suggestion?

@noordawod ,when open Flutter project's android module, it creates strings_en.arb on /android/res/values/。I think it's not issues, but I can't build my Flutter project in Android platform. And can i close auto generate by another menu.


Removed space in arguments, changed assistant intent's condition

Found your gem in some twitter daily news. Went through code to find how it was implemented and found some strange space between hash variable and key. Was a bit surprised that it's working, but created a PR so you can notice that place.
Shouldn't it have the same check as line 118 ?
https://github.com/armilam/google-assistant-ruby/blob/master/lib/google_assistant.rb#L126

Hi @AKovtunov, thanks for contributing! The [] syntax is technically an operator, and operators allow whitespace, which explains why this is working as-is. That said, I do prefer the style without the space as you have here, so I'm happy to merge.
And as for the switch to .empty?, that's great, too. Thanks!

@armilam you are welcome! I'm glad to help :)


Error with GraphQL models

I am having some issues with using ash_papertrail and on a model that uses GraphQL.  I copied the example from the README, and this is the issue I am seeing
The following code gives me this error:
== Compilation error in file lib/myapp/myapi/resources/sample.ex ==
** (Spark.Error.DslError) [MyApp.Sample]
Multiple values for key :action
deps/ash_paper_trail/lib/resource/transformers/create_version_resource.ex:157: anonymous fn/4 in :elixir_compiler_10.MODULE/1
(elixir 1.15.4) lib/keyword.ex:1048: Keyword.do_merge/6
deps/ash_paper_trail/lib/resource/transformers/create_version_resource.ex:157: (module)
(spark 1.1.22) .../resources/sample.ex:20: Spark.Dsl.before_compile/1
If I remove the mixin, I get this error:
** (Absinthe.Schema.Error) Compilation failed:
Locations
/Users/danieljacobs/git/api/deps/ash_graphql/lib/resource/resource.ex:2326
In field Paper_trail_versions, :_filter_input is not defined in your schema.
Types must exist if referenced.
`
defmodule MyApp.Sample.PaperTrailMixin do
defmacro using(_) do
quote do
graphql do
type :sample_versions
    queries do
      list :list_versions, action: :read
    end
  end

end

end
end
defmodule MyApp.Sample do
use Scribble.Resource,
api: MyApp,
extensions: [AshGraphql.Resource, AshPaperTrail.Resource],
authorizers: [Ash.Policy.Authorizer]
attributes do
  uuid_primary_key :id
  attribute :name, :uuid, allow_nil?: false
  create_timestamp :inserted_at
  update_timestamp :updated_at
end

graphql do
  type :sample
end

paper_trail do
  mixin MyApp.Sample.PaperTrailMixin

  version_extensions extensions: [AshGraphql.Resource]

end

actions do
defaults [:read]
end
end
`
Does this look familiar?

So the first error is the list call should look like this:
      list :list_versions, :read

The second is usually what happens when there is a resource somewhere that uses the ash graphql extension but doesn't define a type. Could that be the case for one of your resources?

Ok - I fixed  this
  list :list_versions, :read

and now it works without complaining . The other error was only happening when I removed GraphQL from the mixin - and as it happens, I need graphQL, so I am going to not worry about it for now and will investigrate further if it comes up.
HOWEVER - now I run into this issue when I try to actually do a write.  Any ideas?
`[error] GenServer #PID<0.1341.0> terminating
** (Ash.Error.Invalid) Context: resolving data on perform MyApp.MyAPI.Sample.create
Input Invalid

No such attribute inserted_at for resource Scribble.Scribe.Sample.Version
(ash 2.14.0) lib/ash/api/api.ex:2167: Ash.Api.unwrap_or_raise!/3
(ash_paper_trail 0.1.0) lib/resource/changes/create_new_version.ex:75: anonymous fn/2 in AshPaperTrail.Resource.Changes.CreateNewVersion.create_new_version/1
(ash 2.14.0) lib/ash/changeset/changeset.ex:2149: anonymous fn/2 in Ash.Changeset.run_after_actions/3
(elixir 1.15.4) lib/enum.ex:4830: Enumerable.List.reduce/3
(elixir 1.15.4) lib/enum.ex:2564: Enum.reduce_while/3
(ash 2.14.0) lib/ash/changeset/changeset.ex:1854: anonymous fn/2 in Ash.Changeset.transaction_hooks/2
(ash 2.14.0) lib/ash/changeset/changeset.ex:1775: Ash.Changeset.with_hooks/3
(ash 2.14.0) lib/ash/actions/create/create.ex:328: anonymous fn/11 in Ash.Actions.Create.as_requests/5
(ash 2.14.0) lib/ash/engine/request.ex:1111: Ash.Engine.Request.do_try_resolve_local/4
(ash 2.14.0) lib/ash/engine/request.ex:284: Ash.Engine.Request.do_next/1
(ash 2.14.0) lib/ash/engine/request.ex:213: Ash.Engine.Request.next/1
(ash 2.14.0) lib/ash/engine/engine.ex:712: Ash.Engine.advance_request/2
(ash 2.14.0) lib/ash/engine/engine.ex:637: Ash.Engine.fully_advance_request/2
(ash 2.14.0) lib/ash/engine/engine.ex:578: Ash.Engine.do_run_iteration/2
(elixir 1.15.4) lib/enum.ex:2510: Enum."-reduce/3-lists^foldl/2-0-"/3
(ash 2.14.0) lib/ash/engine/engine.ex:307: Ash.Engine.run_to_completion/1
(ash 2.14.0) lib/ash/engine/engine.ex:252: Ash.Engine.do_run/2
(ash 2.14.0) lib/ash/engine/engine.ex:148: Ash.Engine.run/2
(ash 2.14.0) lib/ash/actions/create/create.ex:99: Ash.Actions.Create.do_run/4
(ash 2.14.0) lib/ash/actions/create/create.ex:38: Ash.Actions.Create.run/4`

Just pushed something to main, if you want to give it a shot :)

That fixed that problem, we are getting there!  Here is the next issue
I have my resources backed by postgres, and its complaining that tables don't exist. I am trying to run ash_postgres.generate_migrations but it's not working.  See code below:

[nix-shell:~/git/api]$ mix ash_postgres.generate_migrations --name add_samples_and_version
Compiling 9 files (.ex)

Generated MyApp app
** (ArgumentError) `nil` is not a Spark DSL module.

    nil.spark_dsl_config()
    (spark 1.1.22) lib/spark/dsl/extension.ex:135: Spark.Dsl.Extension.dsl!/1
    (spark 1.1.22) lib/spark/dsl/extension.ex:153: Spark.Dsl.Extension.get_entities/2
    (ash 2.14.0) lib/ash/resource/info.ex:575: Ash.Resource.Info.attribute/2
    (ash_postgres 1.3.40) lib/migration_generator/migration_generator.ex:2622: anonymous fn/4 in AshPostgres.MigrationGenerator.find_reference/3
    (elixir 1.15.4) lib/enum.ex:4307: Enum.find_value_list/3
    (ash_postgres 1.3.40) lib/migration_generator/migration_generator.ex:2612: anonymous fn/3 in AshPostgres.MigrationGenerator.attributes/2
    (elixir 1.15.4) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2

defmodule MyApp.MyApi.Sample.PaperTrailMixin do

  defmacro __using__(_) do
    quote do
      graphql do
        type :sample_versions

        queries do
          list :list_versions,  :read
        end
      end

    end
  end
end

defmodule MyApp.MyApi.Sample do
  use Scribble.Resource,
    api: MyApp.MyApi,
    data_layer: AshPostgres.DataLayer,

    extensions: [AshGraphql.Resource, AshPaperTrail.Resource],
    authorizers: [Ash.Policy.Authorizer]

    attributes do
      uuid_primary_key :id
      attribute :name, :string, allow_nil?: false
      create_timestamp :inserted_at
      update_timestamp :updated_at
    end

    graphql do
      type :sample
    end

    paper_trail do
      mixin MyApp.MyApi.Sample.PaperTrailMixin

      version_extensions extensions: [AshGraphql.Resource]

    end

  actions do
    defaults [:read,  :update, :create]

  end

  postgres do
    table "samples"
    repo Scribble.Repo

  end

end

Ah, yes, interesting...I think you'll need to put the generated resource into your api/ registry. Are you using a registry? If not you can switch to a registry and then there is a registry extension in this repo to add version resources.

I am using a registry, but maybe I didn't add the extension correctly? Is this what you mean?
defmodule Scribble.Scribe.Registry do
  use Ash.Registry,
    extensions: [Ash.Registry.ResourceValidations,
    AshPaperTrail.Registry
  ]

  entries do
    entry MyApp.MyAPI.Sample
    entry MyApp.MyAPI.Sample.Version. # add this line
  end
end

🤔 you shouldn't need to add that line, as the registry extension should do it. Not sure where this is going wrong. If you could push up a reproduction repo, I'm sure I can get to the bottom of it. Hopefully this is the last roadblock, sorry its been rocky, this package is still a bit experimental.

Ok I think I have a repro. I modified the test to use the Postgres data layer instead of ets ( and put in a littl ebit of configuration so that we could connect to postgres) , and that was basically enough to reproduce the bug.
https://github.com/djacobs7/ash_paper_trail/tree/bug__postgres_data_layer
Then, just run these steps:
MIX_ENV=test mix ecto.create
MIX_ENV=test mix ash_postgres.generate_migrations

Should be fixed now :)


Allow dynamic inclusion of JSON files

As the system grows, the data managed in a single JSON with the estimations of all the activities can be complicate. Allow the possibility of including other JSON filed
{   .....   "_include" : url }

Implemented but not in a recursive fashion (so if an included file has _includes it is ignored)


Apply the Bionic reading after the js code is applied

Describe your suggested feature
Apply the Bionic reading after the js code is applied
Why
https://github.com/LNReader/lnreader/assets/75091899/79c30545-4400-403c-ba6c-a6aa7fe80eaf
and this:

Other details
Load the js code before the bionic reading.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.14.
[X] I will fill out all of the requested information in this form.

Custom JS must be applied after app default option.


disable caliper-fabric-gateway-enabled in 4.2 version

Which Caliper version are you using?
0.4.2
Which Node.JS version are you using?
docker
Which operating system are you using?
docker
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
when I try to start caliper in k8s as
      containers:
      - name: main
        image: hyperledger/caliper:0.4.2
        env:
          - name: CALIPER_BIND_SUT
            value: fabric:2.2
          - name: CALIPER_BENCHCONFIG
            value: /tmp/myAssetBenchmark.yaml
          - name: CALIPER_NETWORKCONFIG
            value: /tmp/networkConfig.yaml

caliper starts fail with old configuration.(before gateway)
What was the observed incorrect behavior?
I am not sure... if we are developing caliper 0.5+ version, then why it blocking 0.4.2 with gateway option and it enabled by default.
I tried 0.4.1 and others even 1.4 won't works.
Please provide the error logs and their surroundings.
2022.03.13-08:10:29.118 error [caliper] [cli-launch-manager] 	Unexpected error during benchmark execution: Error: Caliper currently only supports gateway based operation using the 2.2.3 Fabric-SDK. Please retry with the gateway flag
Usage:
 caliper launch manager --caliper-bind-sut fabric:1.4 [other options]

Options:
  --help, -h           Show usage information  [boolean]
  --version            Show version information  [boolean]
  --caliper-bind-sut   The name and version of the platform to bind to  [string]
  --caliper-bind-cwd   The working directory for performing the SDK install  [string]
  --caliper-bind-args  Additional arguments to pass to "npm install". Use the "=" notation when setting this parameter  [string]
  --caliper-bind-file  Yaml file to override default (supported) package versions when binding an SDK  [string]

Error: Caliper currently only supports gateway based operation using the 2.2.3 Fabric-SDK. Please retry with the gateway flag
    at _loadAppropriateConnectorClass (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/node_modules/@hyperledger/caliper-fabric/lib/FabricConnectorFactory.js:79:19)
    at CaliperEngine.connectorFactory [as adapterFactory] (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/node_modules/@hyperledger/caliper-fabric/lib/FabricConnectorFactory.js:122:62)
    at CaliperEngine.run (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-core/lib/manager/caliper-engine.js:93:36)
    at Function.handler (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/lib/launch/lib/launchManager.js:62:43)
    at process._tickCallback (internal/process/next_tick.js:68:7)

### Please provide your benchmark configuration file content, if possible.

_No response_

### Please provide your network configuration file content, if possible.

_No response_

### Please provide your workload module content, if possible.

_No response_

### Please provide any additional information you deem relevant to the error.

are we able to roll back the tag to a stable version?

I hope before we migrate caliper with gateway approach, there is a stable version for caliper able to be use.

@SamYuan1990 for caliper 0.5.0 the need to specify --caliper-fabric-gateway-enabled has been removed when using fabric SUT 2.2 as it's unnecessary (I presume that there was a plan to try to write a connector that used the fabric-common package for 2.2 but it was never done). It is still available in the 1.4 SUT because if you don't specify it, it will use the fabric-client apis and if you do specify it, it will use the fabric-network apis.
If you want to try, then you can use the latest docker and npm builds of 0.5.0 (although listed as unstable, I would say they are a better version to use than 0.4.2)

022.03.13-10:14:06.143 info  [caliper] [cli-launch-manager] 	Binding specification is present, performing binding for "fabric:1.4"
2022.03.13-10:14:06.147 warn  [caliper] [bind] 	Working directory not specified. Using "/hyperledger/caliper/workspace"
2022.03.13-10:14:06.148 info  [caliper] [bind] 	User-provided arguments for npm: "-g"
2022.03.13-10:14:06.148 info  [caliper] [bind] 	Binding for<EMAIL_ADDRESS>This might take some time...
2022.03.13-10:14:06.148 info  [caliper] [bind] 	Using working directory: /hyperledger/caliper/workspace
2022.03.13-10:14:06.148 info  [caliper] [bind] 	Calling npm with: install -g<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>This library will not receive further updates other than security fixes. We recommend using @grpc/grpc-js instead.
npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>This package is no longer maintained.
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>This library will not receive further updates other than security fixes. We recommend using @grpc/grpc-js instead.
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"^10.15.3 || ^12.15.0","npm":" ^6.4.1"} (current: {"node":"14.19.0","npm":"6.14.16"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"^10.15.3 || ^12.15.0","npm":"^6.4.1"} (current: {"node":"14.19.0","npm":"6.14.16"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"^8.9.0 || ^10.15.3 || ^12.13.1","npm":"^5.5.1 || ^6.4.1"} (current: {"node":"14.19.0","npm":"6.14.16"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"^10.15.3 || ^12.15.0","npm":"^6.4.1"} (current: {"node":"14.19.0","npm":"6.14.16"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"^10.15.3 || ^12.15.0","npm":"^6.4.1"} (current: {"node":"14.19.0","npm":"6.14.16"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>
npm ERR! code EROFS
npm ERR! syscall mkdir
npm ERR! path /tmp/npm-17-0efbf6ad
npm ERR! errno -30
npm ERR! rofs EROFS: read-only file system, mkdir '/tmp/npm-17-0efbf6ad'
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2022-03-13T10_18_44_396Z-debug.log
2022.03.13-10:18:44.425 error [caliper] [bind] 	Failed to execute "npm" with return code 226.
Usage:
 caliper launch manager --caliper-bind-sut fabric:1.4 [other options]

Options:
  --help, -h           Show usage information  [boolean]
  --version            Show version information  [boolean]
  --caliper-bind-sut   The name and version of the platform to bind to  [string]
  --caliper-bind-cwd   The working directory for performing the SDK install  [string]
  --caliper-bind-args  Additional arguments to pass to "npm install". Use the "=" notation when setting this parameter  [string]
  --caliper-bind-file  Yaml file to override default (supported) package versions when binding an SDK  [string]

Error: Failed to execute "npm" with return code 226.
    at ChildProcess.<anonymous> (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-core/lib/common/utils/caliper-utils.js:456:35)
    at ChildProcess.emit (events.js:400:28)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)

with
      - name: main
        image: hyperledger/caliper:0.5.0-unstable-20220311182403
        env:
          - name: CALIPER_BENCHCONFIG
            value: /tmp/myAssetBenchmark.yaml
          - name: CALIPER_NETWORKCONFIG
            value: /tmp/networkConfig.yaml
        command:
          #- ls
          #- /tmp
          - caliper
          - launch
          - manager
          - --caliper-bind-sut
          - fabric:1.4

2022.03.13-10:19:56.334 info  [caliper] [cli-launch-manager] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:19:56.336 info  [caliper] [cli-launch-manager] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:19:56.336 info  [caliper] [cli-launch-manager] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:19:56.336 info  [caliper] [cli-launch-manager] 	Set SUT type: fabric
2022.03.13-10:19:56.343 info  [caliper] [benchmark-validator] 	No observer specified, will default to `none`
2022.03.13-10:19:56.344 info  [caliper] [caliper-engine] 	Starting benchmark flow
2022.03.13-10:19:56.344 info  [caliper] [caliper-engine] 	Network configuration attribute "caliper.command.start" is not present, skipping start command
2022.03.13-10:19:56.382 error [caliper] [caliper-engine] 	Error while performing "test" step: Error: Unable to detect required Fabric binding packages
    at _determineInstalledNodeSDKVersion (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/node_modules/@hyperledger/caliper-fabric/lib/FabricConnectorFactory.js:39:15)
    at CaliperEngine.connectorFactory [as adapterFactory] (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/node_modules/@hyperledger/caliper-fabric/lib/FabricConnectorFactory.js:98:37)
    at CaliperEngine.run (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-core/lib/manager/caliper-engine.js:109:64)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Function.handler (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/lib/launch/lib/launchManager.js:62:30)
2022.03.13-10:19:56.383 info  [caliper] [caliper-engine] 	Network configuration attribute "caliper.command.end" is not present, skipping end command
2022.03.13-10:19:56.383 error [caliper] [cli-launch-manager] 	Benchmark failed with error code 6
Usage:
 caliper launch manager --caliper-bind-sut fabric:1.4 [other options]

Options:
  --help, -h           Show usage information  [boolean]
  --version            Show version information  [boolean]
  --caliper-bind-sut   The name and version of the platform to bind to  [string]
  --caliper-bind-cwd   The working directory for performing the SDK install  [string]
  --caliper-bind-args  Additional arguments to pass to "npm install". Use the "=" notation when setting this parameter  [string]
  --caliper-bind-file  Yaml file to override default (supported) package versions when binding an SDK  [string]

Error: Benchmark failed with error code 6
    at Function.handler (/home/node/.npm-global/lib/node_modules/@hyperledger/caliper-cli/lib/launch/lib/launchManager.js:70:23)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

with
 - name: main
        image: hyperledger/caliper:0.5.0-unstable-20220311182403
        env:
          - name: CALIPER_BENCHCONFIG
            value: /tmp/myAssetBenchmark.yaml
          - name: CALIPER_NETWORKCONFIG
            value: /tmp/networkConfig.yaml
        command:
          #- ls
          #- /tmp
          - caliper
          - launch
          - manager

kubectl logs -f caliper-5cc457d95d-wh5cb      -c main
2022.03.13-10:22:46.112 info  [caliper] [cli-launch-manager] 	Binding specification is present, performing binding for "fabric:2.2"
2022.03.13-10:22:46.116 warn  [caliper] [bind] 	Working directory not specified. Using "/hyperledger/caliper/workspace"
2022.03.13-10:22:46.117 info  [caliper] [bind] 	User-provided arguments for npm: "-g"
2022.03.13-10:22:46.117 info  [caliper] [bind] 	Binding for<EMAIL_ADDRESS>This might take some time...
2022.03.13-10:22:46.117 info  [caliper] [bind] 	Using working directory: /hyperledger/caliper/workspace
2022.03.13-10:22:46.118 info  [caliper] [bind] 	Calling npm with: install -g<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js
> node-gyp rebuild

make: Entering directory '/home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js/build'
  CXX(target) Release/obj.target/pkcs11/src/main.o
In file included from ../../nan/nan.h:58,
                 from ../src/main.cpp:1:
/home/node/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka 'void (*)(v8::Local<v8::Object>)'} to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
  793 |       (node::addon_register_func) (regfunc),                          \
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/node/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro 'NODE_MODULE_X'
  827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/main.cpp:27:1: note: in expansion of macro 'NODE_MODULE'
   27 | NODE_MODULE(pkcs11, init)
      | ^~~~~~~~~~~
  CXX(target) Release/obj.target/pkcs11/src/dl.o
  CXX(target) Release/obj.target/pkcs11/src/const.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/error.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/v8_convert.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/template.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/mech.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_aes.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_rsa.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_ecdh.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/pkcs11.o
  CXX(target) Release/obj.target/pkcs11/src/async.o
  CXX(target) Release/obj.target/pkcs11/src/node.o
  SOLINK_MODULE(target) Release/obj.target/pkcs11.node
  COPY Release/pkcs11.node
make: Leaving directory '/home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js/build'

><EMAIL_ADDRESS>postinstall /home/node/.npm-global/lib/node_modules/fabric-network/node_modules/protobufjs
> node scripts/postinstall

+<EMAIL_ADDRESS>added 82 packages from 117 contributors in 60.685s
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:47.767 info  [caliper] [cli-launch-manager] 	Set SUT type: fabric
2022.03.13-10:23:47.775 info  [caliper] [benchmark-validator] 	No observer specified, will default to `none`
2022.03.13-10:23:47.776 info  [caliper] [caliper-engine] 	Starting benchmark flow
2022.03.13-10:23:47.776 info  [caliper] [caliper-engine] 	Network configuration attribute "caliper.command.start" is not present, skipping start command
2022.03.13-10:23:49.118 info  [caliper] [FabricConnectorFactory] 	Initializing gateway connector compatible with installed SDK: 2.2.11
2022.03.13-10:23:49.146 info  [caliper] [IdentityManager] 	Adding User1 (admin=false) as User1 for organization Org1MSP
2022.03.13-10:23:49.150 info  [caliper] [connectors/v2/FabricGateway] 	Fabric SDK version: 2.2.11; TLS based on Org1MSP: server
2022.03.13-10:23:49.150 info  [caliper] [caliper-engine] 	Executed "init" step in 0.001 seconds
2022.03.13-10:23:49.151 warn  [caliper] [connectors/v2/FabricGateway] 	Install smart contract not available with Fabric SDK version: 2.2.11
2022.03.13-10:23:49.151 info  [caliper] [caliper-engine] 	Executed "install" step in 0 seconds
2022.03.13-10:23:49.155 info  [caliper] [monitor.js] 	No resource monitors specified
2022.03.13-10:23:49.157 info  [caliper] [default-observer] 	Observer interval set to 5000 milliseconds
2022.03.13-10:23:49.162 info  [caliper] [round-orchestrator] 	Preparing worker connections
2022.03.13-10:23:49.162 info  [caliper] [worker-orchestrator] 	Launching worker 1 of 2
2022.03.13-10:23:49.173 info  [caliper] [worker-orchestrator] 	Launching worker 2 of 2
2022.03.13-10:23:49.180 info  [caliper] [worker-orchestrator] 	Messenger not configured, entering configure phase...
2022.03.13-10:23:49.181 info  [caliper] [worker-orchestrator] 	No existing workers detected, entering worker launch phase...
2022.03.13-10:23:49.183 info  [caliper] [worker-orchestrator] 	Waiting for 2 workers to be connected...
2022.03.13-10:23:49.945 info  [caliper] [cli-launch-worker] 	Worker is a locally forked process, skipping binding step already performed by the manager process
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set SUT type: fabric
2022.03.13-10:23:49.964 info  [caliper] [cli-launch-worker] 	Worker is a locally forked process, skipping binding step already performed by the manager process
2022.03.13-10:23:49.967 info  [caliper] [cli-launch-worker] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:49.967 info  [caliper] [cli-launch-worker] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:49.968 info  [caliper] [cli-launch-worker] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:49.969 info  [caliper] [cli-launch-worker] 	Set SUT type: fabric

then pod restart with unknown reason.
      - name: main
        image: hyperledger/caliper:0.5.0-unstable-20220311182403
        env:
          - name: CALIPER_BENCHCONFIG
            value: /tmp/myAssetBenchmark.yaml
          - name: CALIPER_NETWORKCONFIG
            value: /tmp/networkConfig.yaml
        command:
          #- ls
          #- /tmp
          - caliper
          - launch
          - manager
          - --caliper-bind-sut
          - fabric:2.2

kubectl logs -f caliper-5cc457d95d-wh5cb      -c main
2022.03.13-10:22:46.112 info  [caliper] [cli-launch-manager] 	Binding specification is present, performing binding for "fabric:2.2"
2022.03.13-10:22:46.116 warn  [caliper] [bind] 	Working directory not specified. Using "/hyperledger/caliper/workspace"
2022.03.13-10:22:46.117 info  [caliper] [bind] 	User-provided arguments for npm: "-g"
2022.03.13-10:22:46.117 info  [caliper] [bind] 	Binding for<EMAIL_ADDRESS>This might take some time...
2022.03.13-10:22:46.117 info  [caliper] [bind] 	Using working directory: /hyperledger/caliper/workspace
2022.03.13-10:22:46.118 info  [caliper] [bind] 	Calling npm with: install -g<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js
> node-gyp rebuild

make: Entering directory '/home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js/build'
  CXX(target) Release/obj.target/pkcs11/src/main.o
In file included from ../../nan/nan.h:58,
                 from ../src/main.cpp:1:
/home/node/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka 'void (*)(v8::Local<v8::Object>)'} to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
  793 |       (node::addon_register_func) (regfunc),                          \
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/node/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro 'NODE_MODULE_X'
  827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/main.cpp:27:1: note: in expansion of macro 'NODE_MODULE'
   27 | NODE_MODULE(pkcs11, init)
      | ^~~~~~~~~~~
  CXX(target) Release/obj.target/pkcs11/src/dl.o
  CXX(target) Release/obj.target/pkcs11/src/const.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/error.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/v8_convert.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/template.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/mech.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_aes.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_rsa.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_ecdh.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/pkcs11.o
  CXX(target) Release/obj.target/pkcs11/src/async.o
  CXX(target) Release/obj.target/pkcs11/src/node.o
  SOLINK_MODULE(target) Release/obj.target/pkcs11.node
  COPY Release/pkcs11.node
make: Leaving directory '/home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js/build'

><EMAIL_ADDRESS>postinstall /home/node/.npm-global/lib/node_modules/fabric-network/node_modules/protobufjs
> node scripts/postinstall

+<EMAIL_ADDRESS>added 82 packages from 117 contributors in 60.685s
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:47.767 info  [caliper] [cli-launch-manager] 	Set SUT type: fabric
2022.03.13-10:23:47.775 info  [caliper] [benchmark-validator] 	No observer specified, will default to `none`
2022.03.13-10:23:47.776 info  [caliper] [caliper-engine] 	Starting benchmark flow
2022.03.13-10:23:47.776 info  [caliper] [caliper-engine] 	Network configuration attribute "caliper.command.start" is not present, skipping start command
2022.03.13-10:23:49.118 info  [caliper] [FabricConnectorFactory] 	Initializing gateway connector compatible with installed SDK: 2.2.11
2022.03.13-10:23:49.146 info  [caliper] [IdentityManager] 	Adding User1 (admin=false) as User1 for organization Org1MSP
2022.03.13-10:23:49.150 info  [caliper] [connectors/v2/FabricGateway] 	Fabric SDK version: 2.2.11; TLS based on Org1MSP: server
2022.03.13-10:23:49.150 info  [caliper] [caliper-engine] 	Executed "init" step in 0.001 seconds
2022.03.13-10:23:49.151 warn  [caliper] [connectors/v2/FabricGateway] 	Install smart contract not available with Fabric SDK version: 2.2.11
2022.03.13-10:23:49.151 info  [caliper] [caliper-engine] 	Executed "install" step in 0 seconds
2022.03.13-10:23:49.155 info  [caliper] [monitor.js] 	No resource monitors specified
2022.03.13-10:23:49.157 info  [caliper] [default-observer] 	Observer interval set to 5000 milliseconds
2022.03.13-10:23:49.162 info  [caliper] [round-orchestrator] 	Preparing worker connections
2022.03.13-10:23:49.162 info  [caliper] [worker-orchestrator] 	Launching worker 1 of 2
2022.03.13-10:23:49.173 info  [caliper] [worker-orchestrator] 	Launching worker 2 of 2
2022.03.13-10:23:49.180 info  [caliper] [worker-orchestrator] 	Messenger not configured, entering configure phase...
2022.03.13-10:23:49.181 info  [caliper] [worker-orchestrator] 	No existing workers detected, entering worker launch phase...
2022.03.13-10:23:49.183 info  [caliper] [worker-orchestrator] 	Waiting for 2 workers to be connected...
2022.03.13-10:23:49.945 info  [caliper] [cli-launch-worker] 	Worker is a locally forked process, skipping binding step already performed by the manager process
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set SUT type: fabric
2022.03.13-10:23:49.964 info  [caliper] [cli-launch-worker] 	Worker is a locally forked process, skipping binding step already performed by the manager process
2022.03.13-10:23:49.967 info  [caliper] [cli-launch-worker] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:49.967 info  [caliper] [cli-launch-worker] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:49.968 info  [caliper] [cli-launch-worker] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:49.969 info  [caliper] [cli-launch-worker] 	Set SUT type: fabric

then pod restart with unknown reason.

kubectl logs -f caliper-5cc457d95d-wh5cb      -c main
2022.03.13-10:22:46.112 info  [caliper] [cli-launch-manager] 	Binding specification is present, performing binding for "fabric:2.2"
2022.03.13-10:22:46.116 warn  [caliper] [bind] 	Working directory not specified. Using "/hyperledger/caliper/workspace"
2022.03.13-10:22:46.117 info  [caliper] [bind] 	User-provided arguments for npm: "-g"
2022.03.13-10:22:46.117 info  [caliper] [bind] 	Binding for<EMAIL_ADDRESS>This might take some time...
2022.03.13-10:22:46.117 info  [caliper] [bind] 	Using working directory: /hyperledger/caliper/workspace
2022.03.13-10:22:46.118 info  [caliper] [bind] 	Calling npm with: install -g<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js
> node-gyp rebuild

make: Entering directory '/home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js/build'
  CXX(target) Release/obj.target/pkcs11/src/main.o
In file included from ../../nan/nan.h:58,
                 from ../src/main.cpp:1:
/home/node/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from 'void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka 'void (*)(v8::Local<v8::Object>)'} to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
  793 |       (node::addon_register_func) (regfunc),                          \
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/node/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro 'NODE_MODULE_X'
  827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/main.cpp:27:1: note: in expansion of macro 'NODE_MODULE'
   27 | NODE_MODULE(pkcs11, init)
      | ^~~~~~~~~~~
  CXX(target) Release/obj.target/pkcs11/src/dl.o
  CXX(target) Release/obj.target/pkcs11/src/const.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/error.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/v8_convert.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/template.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/mech.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_aes.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_rsa.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/param_ecdh.o
  CXX(target) Release/obj.target/pkcs11/src/pkcs11/pkcs11.o
  CXX(target) Release/obj.target/pkcs11/src/async.o
  CXX(target) Release/obj.target/pkcs11/src/node.o
  SOLINK_MODULE(target) Release/obj.target/pkcs11.node
  COPY Release/pkcs11.node
make: Leaving directory '/home/node/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js/build'

><EMAIL_ADDRESS>postinstall /home/node/.npm-global/lib/node_modules/fabric-network/node_modules/protobufjs
> node scripts/postinstall

+<EMAIL_ADDRESS>added 82 packages from 117 contributors in 60.685s
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:47.766 info  [caliper] [cli-launch-manager] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:47.767 info  [caliper] [cli-launch-manager] 	Set SUT type: fabric
2022.03.13-10:23:47.775 info  [caliper] [benchmark-validator] 	No observer specified, will default to `none`
2022.03.13-10:23:47.776 info  [caliper] [caliper-engine] 	Starting benchmark flow
2022.03.13-10:23:47.776 info  [caliper] [caliper-engine] 	Network configuration attribute "caliper.command.start" is not present, skipping start command
2022.03.13-10:23:49.118 info  [caliper] [FabricConnectorFactory] 	Initializing gateway connector compatible with installed SDK: 2.2.11
2022.03.13-10:23:49.146 info  [caliper] [IdentityManager] 	Adding User1 (admin=false) as User1 for organization Org1MSP
2022.03.13-10:23:49.150 info  [caliper] [connectors/v2/FabricGateway] 	Fabric SDK version: 2.2.11; TLS based on Org1MSP: server
2022.03.13-10:23:49.150 info  [caliper] [caliper-engine] 	Executed "init" step in 0.001 seconds
2022.03.13-10:23:49.151 warn  [caliper] [connectors/v2/FabricGateway] 	Install smart contract not available with Fabric SDK version: 2.2.11
2022.03.13-10:23:49.151 info  [caliper] [caliper-engine] 	Executed "install" step in 0 seconds
2022.03.13-10:23:49.155 info  [caliper] [monitor.js] 	No resource monitors specified
2022.03.13-10:23:49.157 info  [caliper] [default-observer] 	Observer interval set to 5000 milliseconds
2022.03.13-10:23:49.162 info  [caliper] [round-orchestrator] 	Preparing worker connections
2022.03.13-10:23:49.162 info  [caliper] [worker-orchestrator] 	Launching worker 1 of 2
2022.03.13-10:23:49.173 info  [caliper] [worker-orchestrator] 	Launching worker 2 of 2
2022.03.13-10:23:49.180 info  [caliper] [worker-orchestrator] 	Messenger not configured, entering configure phase...
2022.03.13-10:23:49.181 info  [caliper] [worker-orchestrator] 	No existing workers detected, entering worker launch phase...
2022.03.13-10:23:49.183 info  [caliper] [worker-orchestrator] 	Waiting for 2 workers to be connected...
2022.03.13-10:23:49.945 info  [caliper] [cli-launch-worker] 	Worker is a locally forked process, skipping binding step already performed by the manager process
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:49.948 info  [caliper] [cli-launch-worker] 	Set SUT type: fabric
2022.03.13-10:23:49.964 info  [caliper] [cli-launch-worker] 	Worker is a locally forked process, skipping binding step already performed by the manager process
2022.03.13-10:23:49.967 info  [caliper] [cli-launch-worker] 	Set workspace path: /hyperledger/caliper/workspace
2022.03.13-10:23:49.967 info  [caliper] [cli-launch-worker] 	Set benchmark configuration path: /tmp/myAssetBenchmark.yaml
2022.03.13-10:23:49.968 info  [caliper] [cli-launch-worker] 	Set network configuration path: /tmp/networkConfig.yaml
2022.03.13-10:23:49.969 info  [caliper] [cli-launch-worker] 	Set SUT type: fabric

then pod restart with unknown reason.
      - name: main
        image: hyperledger/caliper:0.5.0-unstable-20220311182403
        env:
          - name: CALIPER_BENCHCONFIG
            value: /tmp/myAssetBenchmark.yaml
          - name: CALIPER_NETWORKCONFIG
            value: /tmp/networkConfig.yaml
        command:
          #- ls
          #- /tmp
          - caliper
          - launch
          - manager
          - --caliper-bind-sut
          - fabric:2.2

@SamYuan1990 for caliper 0.5.0 the need to specify --caliper-fabric-gateway-enabled has been removed when using fabric SUT 2.2 as it's unnecessary (I presume that there was a plan to try to write a connector that used the fabric-common package for 2.2 but it was never done). It is still available in the 1.4 SUT because if you don't specify it, it will use the fabric-client apis and if you do specify it, it will use the fabric-network apis.
If you want to try, then you can use the latest docker and npm builds of 0.5.0 (although listed as unstable, I would say they are a better version to use than 0.4.2)

@davidkel as you can see from logs above, I had attempted with serval times,  please kindly advise.
Or, please let me know once there is new release version been announced.

https://github.com/hyperledger-labs/PerformanceSandBox/pull/30 code parts if you interested. @davidkel

@SamYuan1990 So your last attempt had some of the correct setup, ie you have to bind an sut in order to use the docker image, however I've never tested the docker image in a K8s environment so don't know if it will work especially when using forked processes. I don't know why it would fail. Interestingly someone else posted a similar issue with using the 0.4.2 docker container here https://github.com/hyperledger/caliper/issues/1248 but I wasn't able to recreate when running a docker image locally. 0.5.0 probably won't be tested in a K8s environment before it's released so any insight you can give into what the issue may be that you are experiencing would be great.

@SamYuan1990 The author of #1248 said that he didn't have enough memory to run caliper which is why it failed. So I would suggest that you check you have enough resources to run caliper and 2 workers in the same container in K8s.

@SamYuan1990 The author of #1248 said that he didn't have enough memory to run caliper which is why it failed. So I would suggest that you check you have enough resources to run caliper and 2 workers in the same container in K8s.

I suppose I use default setting for k8s, so memory is no limited? btw, how many memory will it cost?
apiVersion: apps/v1
kind: Deployment
metadata:
  name: caliper
  annotations:
    "sidecar.jaegertracing.io/inject": "true"
spec:
  replicas: 1
  selector:
    matchLabels:
      app: caliper
  template:
    metadata:
      labels:
        app: caliper
    spec:
      containers:
      - name: main
        image: hyperledger/caliper:0.5.0-unstable-20220311182403
        env:
          - name: CALIPER_BIND_SUT
            value: fabric:2.2
          - name: CALIPER_BENCHCONFIG
            value: /tmp/myAssetBenchmark.yaml
          - name: CALIPER_NETWORKCONFIG
            value: /tmp/networkConfig.yaml
        command:
          #- ls
          #- /tmp
          - caliper
          - launch
          - manager
        imagePullPolicy: IfNotPresent
        volumeMounts:
          - name: configmap-volume
            mountPath: /tmp
      volumes:
        - name: configmap-volume
          configMap:
              name: fabric-caliper-sample-config
  #restartPolicy: Always

@davidkel , I am not in hurry, I am able waiting for a stable version to have a try once.

@SamYuan1990 0.5.0 unstable is actually a pretty stable release, just not labelled as such. It would be really good to understand what the problem is in case there is something that could be fixed for a K8s environment otherwise the official release won't get any further changes around this area. The other thing to try would be to use mqtt and launch the workers as separate containers. See https://hyperledger.github.io/caliper/vNext/architecture/#multi-platform-support for more details


Add info in image list

closes #96

The table is taking a bit too much space. This part of the table can be made smaller. I would suggest that:

Those 3 columns are merged into one
The color model already contains information about the number of channels so that could be displayed as a tooltip on the color model icon. Bit depth could also be shown there.
I think you can show something additional only when the image is not 8 bit, which is what a "regular" image would be.

Additional recommendation to gain some space: the column with the close button probably does not require a header

Thank you, nice work!


Add python built-in types support for tf.as_dtype

This fix tries to address the issue raised in #17641 where it was not possible to use tf.as_dtype(float) the same way as numpy np.dtype(float).
This fix adds the built-in types support for tf.as_dtype, so that it is possible to specify:
dtypes.as_dtype(float)   # dtypes.float64
dtypes.as_dtype(int)     # dtypes.int64
dtypes.as_dtype(complex) # dtypes.complex128
dtypes.as_dtype(bool)    # dtypes.bool

This fix fixes #17641.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Nagging Assignee @mrry: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Thanks @mrry. I take a second and noticed that there are some discrepancies between np and tf:
>>> import numpy as np
>>> np.dtype('int')
dtype('int64')
>>> np.dtype('float')
dtype('float64')
>>> np.dtype('complex')
dtype('complex128')
>>> np.dtype('bool')
dtype('bool')

The above matches the internal data types in python to C.
For tf, the canonical alias only defines half, float, and double (and bool):
https://github.com/tensorflow/tensorflow/blob/d57f0213bff0c676b06f4b3f0842ac282738c254/tensorflow/python/framework/dtypes.py#L501-L511
There are no canonical definitions pointing to int or complex. Also, the mappings are:
>>> import tensorflow as tf
>>> tf.as_dtype('half')
tf.float16
>>> tf.as_dtype('float')
tf.float32
>>> tf.as_dtype('double')
tf.float64
>>> tf.as_dtype('bool')
tf.bool

@mrry Given the discrepancies mentioned above, I think it might make sense to support
dtypes.as_dtype(float) => float32
dtypes.as_dtype(bool) => bool

For int and complex maybe we should defer to not add the support for now?

Yep, that sounds fine to me!

Thanks @mrry. The PR has been updated. Please take a look.


Document /v5/release_tag API

The (newish) release tag API is missing from the resource documentation:
https://www.balena.io/docs/reference/api/resources/release/
See the following issue for the changes:
https://github.com/balena-io/balena-sdk/issues/622

This is resolved by this pending PR: https://github.com/balena-io/docs/pull/1232


[BUG] copa overwrites /usr/sbin symlink for mariner distroless/debug

Version of copa
v0.9.0
Expected Behavior
copa should not change the existing directory structure and symlinks
Actual Behavior
copa overwrites the existing symlink
Steps To Reproduce

Check config for original image https://oci.dag.dev/layers/mcr.microsoft.com/cbl-mariner/distroless/debug@sha256:960d95cc274484fc72b33d4b5720857fbb1c9a5f35b93a39f8e161557236fd4d/
70a0cf87 lrwxrwxrwx 0/0               0 2024-01-23 18:52 sbin -> usr/sbin

copa patch -i mcr.microsoft.com/cbl-mariner/distroless/debug:2.0.20241029

Check config for patched image: https://oci.dag.dev/layers/sertacacr.azurecr.io/debug:2.0-patched@sha256:ffb2188eb72313a86dc3b0a00e903c2cbd0eda565a50bbc47038ec04b8b0b174/
d0a2b129 drwxr-xr-x 0/0               0 2024-11-26 19:04 sbin

Mariner 2 spec provides /sbin as the path and copa is extracting to that path since that's the path in the rpm. Copa should check if existing path is a symlink and follow the path instead of dropping the files
https://github.com/microsoft/azurelinux/blob/2.0/SPECS/busybox/busybox.spec#L94
Are you willing to submit PRs to contribute to this bug fix?

[ ] Yes, I am willing to implement it.

related #809
https://github.com/project-copacetic/copacetic/blob/ddd8edd1d0d0b9f001bf6c20a4427c6d0af3724b/pkg/pkgmgr/rpm.go#L634C2-L638C1


Package request: Scrapegraph-ai

Project description
Python scraper based on AI
Metadata

homepage URL: https://scrapegraphai.com/
source URL: https://github.com/ScrapeGraphAI/Scrapegraph-ai
license: mit
platforms: unix, linux, darwin

Add a :+1: reaction to issues you find important.

I've closed, I see this is not used as a cli-tool rather imported for python usage. Still playwright has issues using it in NixOS as the binary is dynamically linked.


Add initial opencensus instrumentation code in Cloud Storage.

This PR adds OpenCensus-Java instrumentation in to monitor and record events in Cloud Storage client.
Note that there is another PR to instrument underlying library google-http-java-client is also instrumented so as to provide detailed span break down. In case that we don't catch up new release of google-http-java-client, in this PR I still added helper class to do context propagation.
There are 3 major changes in this PR:

Added a helper class CensusHttpModule to do trace context propagation through HttpHeaders. (might be temporary - can be removed if google-http-java-client release new version)
Added a helper class HttpStorageRpcSpans, which contains all span names and  a method to register them all for collection.
Added instrumentation code in HttpStorageRpc.  The instrumented code starts a new Span the main logic of the method begins, set it as current span with Tracer.withSpan. If exception occurs during the execution, the span status will be set to Status.UNKNOWN to indicate unparsed exception. The span and its scope will be ended before method exits.

All the above Spans will be stored into local span store, and can be optionally exported if user explicitly configure an exporter (e.g. stackdriver exporter).
Please @hzyi-google and @bogdandrutu kindly help review.

@HailongWen I see the WIP in the title. Is this ready to review now?

@pongad Yes. Sorry for the confusion. I have changed the title.

LGTM +1

Thank you all for the help and support!


react-three-fiber: manually have to set manager.state.models[modelID] before createSubset + removeSubset not working

Description
In my react-three-fiber project, I have to manually set ifcManager.state.models[modelId] before making a call to ifcManager.createSubset(). I thought the createSubset method would handle this on it's own:
const [highlightedModel, setHighlightedModel] = useState({ id: -1 });

function highlight(intersection: Intersection<IFCModel<Event>>, material: Material) {
    const { faceIndex } = intersection;
    const { modelID, geometry } = intersection.object;
    const id = manager.getExpressId(geometry, faceIndex);

    setHighlightedModel({ id: modelID });

    manager.state.models[modelID] = intersection.object;

    manager.createSubset({
      modelID,
      ids: [id],
      material,
      scene,
      removePrevious: true,
    });
  }

Without the call to manager.state.models[modelID] = intersection.object; I get the following error:
Uncaught TypeError: this.state.models[modelID] is undefined
    getGeometry ItemsMap.ts:117
    generateGeometryIndexMap ItemsMap.ts:94
    createSubset SubsetCreator.ts:79
    createSubset BasePropertyManager.ts:9
    createSubset web-ifc-three_IFCLoader.js:54214
    highlight IFCContainer.tsx:44
    handleDblClick IFCContainer.tsx:32
    handlePointer react-three-fiber.esm.js:414
    handleIntersects react-three-fiber.esm.js:289
    handlePointer react-three-fiber.esm.js:376
    connect react-three-fiber.esm.js:1465
    connect react-three-fiber.esm.js:1463
    Provider react-three-fiber.esm.js:1807
    invokePassiveEffectCreate react-reconciler.development.js:16054
    callCallback2 react-reconciler.development.js:12184
    invokeGuardedCallbackDev react-reconciler.development.js:12233
    invokeGuardedCallback react-reconciler.development.js:12292
    flushPassiveEffectsImpl react-reconciler.development.js:16141
    unstable_runWithPriority scheduler.development.js:468
    runWithPriority react-reconciler.development.js:2495
    flushPassiveEffects react-reconciler.development.js:16014
    commitBeforeMutationEffects react-reconciler.development.js:15891
    workLoop scheduler.development.js:417
    flushWork scheduler.development.js:390
    performWorkUntilDeadline scheduler.development.js:157
    js scheduler.development.js:180
    js scheduler.development.js:644
    __require2 chunk-UC7LELEO.js:48
    js index.js:6
    __require2 chunk-UC7LELEO.js:48
    React 2
    __require2 chunk-UC7LELEO.js:48
    js React
    __require2 chunk-UC7LELEO.js:48
    <anonymous> react-dom:1
ItemsMap.ts:117:9

Additionally, when I call removeSubset(modelID, highlightMaterial) visually it appears the highlight remains on the model:
  function handleDblClick(event: Intersection<IFCModel<Event>>) {
    if (Object.keys(manager.state.models).length) {
      manager.removeSubset(highlightedModel.id, highlightMaterial);
    }
    highlight(event, highlightMaterial);
  }

Steps to Reproduce
I have a repo where I reproduce this issue here.
git clone git@github.com:Amar-Gill/r3f-model-highlight-repro.git
cd r3f-model-highlight-repro/
npm i && npm run dev

Double click any mesh, it will be highlighted. Double clicking a new mesh will highlight it also, but the highlight on the previously clicked mesh will remain:

Next, comment out the line for manager.state.models[modelID] = intersection.object; and double click a mesh. The mesh will not highlight and error will appear on console:
Uncaught TypeError: this.state.models[modelID] is undefined

I'having the same issue, which was not present in previous versions.

Hi! What version of IFC.js are you using? Are you accessing / changing ifcManager.state.models somewhere else? Are you using the version of Three.js specified by the peer dependency of IFC.js? 🤔

In my case, I have these dependencies:
"node_modules/web-ifc-three": {
      "version": "0.0.102",
      "resolved": "https://registry.npmjs.org/web-ifc-three/-/web-ifc-three-0.0.102.tgz",
      "integrity": "sha512-Mxx4tN89Lb4dZd/....",
      "dependencies": {
        "three-mesh-bvh": "^0.5.2",
        "web-ifc": "^0.0.32"
      },
      "peerDependencies": {
        "three": "^0.135.0"
      }
    },
 "node_modules/web-ifc-viewer": {
      "version": "1.0.127",
      "resolved": "https://registry.npmjs.org/web-ifc-viewer/-/web-ifc-viewer-1.0.127.tgz",
      "integrity": "sha512-0K4ivXDoGXiP3Q8/...",
      "dependencies": {
        "camera-controls": "^1.33.1",
        "dat.gui": "^0.7.7",
        "gsap": "^3.7.1",
        "postprocessing": "^6.23.1",
        "three-mesh-bvh": "^0.5.2",
        "web-ifc": "^0.0.32",
        "web-ifc-three": "^0.0.102"
      },
      "peerDependencies": {
        "three": "^0.135.0"
      }
    },

And in package.json
    "three": "^0.135.0",
    "three-mesh-bvh": "^0.5.2",
    "web-ifc": "^0.0.32",
    "web-ifc-three": "0.0.102",
    "web-ifc-viewer": "^1.0.127",

package.json
"dependencies": {
    "@react-three/drei": "^8.6.3",
    "@react-three/fiber": "^7.0.25",
    "@types/three": "^0.136.1",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "three": "^0.136.0",
    "web-ifc-three": "0.0.102"
  },

In node_modules, web-ifc-three shows
  "peerDependencies": {
    "three": "^0.135.0"
  }

I'll try downgrading to 0.135

I'm also not changing ifcManager.state.models anywhere else

@agviegas still same error after downgrading to<EMAIL_ADDRESS>which matches peer dependancy of web-ifc-three version I installed.

Do you think it's because I'm using useBVH hook from @react-three/drei and not three-mesh-bvh used in examples?
import { useBVH } from '@react-three/drei';

Hum. Two questions:

You are using the IFCLoader from web-ifc-three and not the one from Three / react-three-fiber, right?
Are you using web-workers?
If you have an example I can debug (either a small repo or a live example) I will happily look into it.

Correct I'm using IFCLoader from web-ifc-three. So I was talking with r3f team, and was able to use the useLoader hook from r3f package to load the load the ifc model. It seems to fix my first issue, where I need to manually set manager.state.models[modelID]. However, the removeSubset functionality is still not working. I will close this issue and make a separate issue for that.
I've updated my git repo to show this working. I'll share the code here as well.

// IFCContainer.tsx
import { useBVH } from '@react-three/drei';
import { useLoader, useThree } from '@react-three/fiber';
import React, { useRef, useState } from 'react';
import { Intersection, Material, MeshLambertMaterial } from 'three';
import { IFCManager } from 'web-ifc-three/IFC/components/IFCManager';
import { IFCModel } from 'web-ifc-three/IFC/components/IFCModel';
import { IFCLoader } from 'web-ifc-three/IFCLoader';

let manager: IFCManager;

export default function IFCContainer() {
  const ifc = useLoader(IFCLoader, 'test-file.ifc', (loader: any) => {
    manager = loader.ifcManager;
    manager.setWasmPath('resources/');
  });
  const [highlightedModel, setHighlightedModel] = useState({ id: -1 });

  const mesh = useRef(null!);
  useBVH(mesh);

  const scene = useThree((state) => state.scene);

  const highlightMaterial = new MeshLambertMaterial({
    transparent: true,
    opacity: 0.6,
    color: 0xff00ff,
    depthTest: false,
  });

  function handleDblClick(event: Intersection<IFCModel<Event>>) {
    manager.removeSubset(highlightedModel.id, highlightMaterial);
    highlight(event, highlightMaterial);
  }

  function highlight(intersection: Intersection<IFCModel<Event>>, material: Material) {
    const { faceIndex } = intersection;
    const { modelID, geometry } = intersection.object;
    const id = manager.getExpressId(geometry, faceIndex);

    setHighlightedModel({ id: modelID });

    manager.createSubset({
      modelID,
      ids: [id],
      material,
      scene,
      removePrevious: true,
    });
  }

  return <primitive ref={mesh} object={ifc} onDoubleClick={handleDblClick} />;
}

Thanks a lot for sharing it! 💛

Hi @iserranoe! Just FYI, right now IFC.js is not supposed to be destroyed / reinitialized multiple times during the execution of the application. This might change in the near future, but right now this is how it is. Are you destroying / reinitializing it?

Hi @agviegas! I don't think I am destroying or reinitializing it

Are you sure @iserranoe? I mention this because I am aware that when libraries/frameworks like react or angular do this automatically. For instance, if you are initializing IFC.js in a component, it is destroyed whenever that component is removed from the DOM (e.g. the user navigates away from the viewer).

The plan is to support this destruction / reinitialization very soon (hopefully before the end of next week). Until then, you can try locating IFC.js somewhere that doesn't get automatically destroyed. If that's not your case, let us know and we'll investigate further!

I finally made it work using @Amar-Gill sugestion and making model.id=0:
When I set 'ifc.state.models[model.id] = found.object' I had problems with 'ifc.getItemProperties'. As before, this was happening when I changed pages. I found that model.id was 0 in the first case and an int number in the second case, so I just set model.id to 0, but I really don't know what is going on, just that it works so far!
const highlight = async (event, material, model) => {
      const found = cast(event)[0];
      if (found){
          // Gets model ID
          model.id = found.object.modelID;

          const index = found.faceIndex;
          const geometry = found.object.geometry;
          let id = await ifc.getExpressId(geometry,index);

          ifc.state.models[model.id] = found.object

          // Creates subset
          ifc.createSubset({
              modelID: model.id,
              ids: [id],
              material: material,
              scene: scene,
              removePrevious: true,
          })

          model.id=0
          const properties_new = await ifc.getItemProperties(model.id, id, true);
          setProp(properties_new)
          setMessage(true)
        }
      else {
          // Removes previous highlight. Para que funcione hay que quitar scene
          ifc.removeSubset(model.id, material);
          setMessage(false)
      }
    }

This new tutorial might be relevant. 🙂


Pin the espresso-systems-common dependency to a particular revision

This is the only dependency in jellyfish that references the main branch. We should ideally pin it to a particular revision/tag. It might lead to builds failing, like now, when the common repo moves forward but jellyfish hasn't yet caught up. Thoughts?
@EspressoSystems/jellyfish @jbearer

yes, we should pin a version. Let's add a tag to the latest commit on espresso-systems-common and pin to it?

Closed in https://github.com/EspressoSystems/jellyfish/pull/148


$message->getSize() throws an exception

Describe the bug
A call to $message->getSize() fails with:
Uncaught exception: Cannot use object of type stdClass as array, code=0, file=F:\Apache2\HTDOCS\GMX-Transix\includes\vendor\webklex\php-imap\src\Connection\Protocols\LegacyProtocol.php, line=339
Used config
Code to Reproduce
The troubling code section which produces the reported bug.
$size = $message->getSize();

Expected behavior
I expect it to return the size of the message body.
Screenshots
Desktop / Server (please complete the following information):

OS: Windows 10
PHP: 8.2.5
Version 5.2
Provider Office365

Additional context

Hi @TonyMarston,
many thanks for your report. I was able to reproduce the issue and pushed a fix.
If you have any more questions or need further assistance, feel free to let me know.
Best regards and happy coding!


Ubuntu 20 and YOLO on ROS Noetic possible?

Is there a way to get darknet_ros working in Ubuntu 20? So far I see it's only tested for  Ubuntu 18
Many errors when trying to compile. Any tutorial or tips to work around the errors?

I followed the procedure given by bigrobinson here.  It worked !


Japanese

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind content

/kind transalation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area documentation

What this PR does / why we need it:
I translated some document to Japanese.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3823160 Translated to Japanse _index.md
53e4991 work at 12th March.
523672a updated 2 on 12th March

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Welcome @TakaoShimizu! It looks like this is your first PR to falcosecurity/falco-website 🎉

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3823160 Translated to Japanse _index.md
53e4991 work at 12th March.
523672a updated 2 on 12th March

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


dark mode doesn't work

Description

dark mode doesn't work.
Steps To Reproduce

Code sample

https://github.com/kimmy214/flutter_boilerplate_ns

Expected behavior

Screenshots

Logs

Logs

[✓] Flutter (Channel stable, 3.3.1, on macOS 12.5.1 21G83 darwin-x64, locale zh-Hans-CN)
    • Flutter version 3.3.1 on channel stable at /Users/ying/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4f9d92fbbd (3 days ago), 2022-09-06 17:54:53 -0700
    • Engine revision 3efdf03e73
    • Dart version 2.18.0
    • DevTools version 2.15.0

Checking Android licenses is taking an unexpectedly long time...[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/ying/Library/Android/sdk
    • Platform android-32, build-tools 32.0.0
    • ANDROID_SDK_ROOT = /Users/ying/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Ultimate Edition (version 2022.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 70.0.5
    • Dart plugin version 222.3739.24

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 12.5.1 21G83 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 105.0.5195.102

HTTP Host availability check is taking a long time...[!] HTTP Host Availability
    ✗ HTTP host "https://maven.google.com/" is not reachable. Reason: An error occurred while checking the HTTP host: Operation timed out
    ✗ HTTP host "https://cloud.google.com/" is not reachable. Reason: An error occurred while checking the HTTP host: Operation timed out

Hi @kimmy214, thanks for filing this issue. Which version of macos_ui are you using? Also, can you provide a minimum reproducible sample? Something in one code file would be best. Cheers!

As this issue has gone stale with no response, I'm closing it.


Missing a Coderwall badge on 24PR

On https://coderwall.com/hugovk I have both 2013 and 2014 24PR badges.
But on http://24pullrequests.com/users/hugovk I only have the 2014 24PR badge
Do I need to do something to sync them?

I see this too on my account http://24pullrequests.com/users/wadtech

My account is displaying this issue as well.

Assembly, the company that owns coderwall is shutting down in a couple days so it's not even clear if coderwall will continue to work after 6th December, so let's leave this issue until the dust has settled and see if the api still works then!

they should make coderwall code public if they are shutting down!

@arthurnn they have: https://github.com/assemblymade/coderwall

❤  hahah nice

If Coderwall no longer works after the 6th, please will you consider http://openbadges.org for badges?
The badges just need to be PNGs with a blob of metadata inside them.

@hugovk - Can you port Coderwall's badges to OpenBadges.org?

Found this related to above question:

https://twitter.com/openbadges/status/286878439036829696
https://wiki.mozilla.org/Badges/Team_and_Tools
Code: https://github.com/mozilla/openbadges-backpack

Closing this issue as #1646 supersedes it. We may remove Coderwall integration entirely depending on the discussion in that thread. Thanks for reporting!


v8: 5.4.232 -> 7.4.255

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@matthewbauer this broke the qtwebengine build: https://hydra.nixos.org/build/94333051

@matthewbauer this broke the qtwebengine build: https://hydra.nixos.org/build/94333051

Thanks! Addressed in c4fc74b19cae7f30151be743f3e2dca43f33ca0f