The node-role.kubernetes.io/master taint is deprecated and will be removed in kubeadm version 1.25

The node-role.kubernetes.io/master taint is deprecated and will be removed in kubeadm version 1.25.
It would be replace by node-role.kubernetes.io/control-plane. like:
https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/manifests/vanilla/vsphere-csi-driver.yaml#L220

@yankay Thanks for your suggestions.
We have noticed this problem, and we will fix this in the next release version.

duplicated with https://github.com/hwameistor/hwameistor/issues/230

fixed at:https://github.com/hwameistor/hwameistor/pull/281, https://github.com/hwameistor/hwameistor/pull/283


Smoke Test Changes

Codecov Report

Merging #449 (408b6c8) into main (fd123f7) will increase coverage by 2.37%.
The diff coverage is n/a.

:exclamation: Current head 408b6c8 differs from pull request most recent head f52a86c. Consider uploading reports for the commit f52a86c to get more accurate results

@@            Coverage Diff             @@
##             main     #449      +/-   ##
==========================================
+ Coverage   47.01%   49.38%   +2.37%
==========================================
  Files         233       82     -151
  Lines       11652     9284    -2368
  Branches      604        0     -604
==========================================
- Hits         5478     4585     -893
+ Misses       5217     3915    -1302
+ Partials      957      784     -173

Impacted Files
Coverage Δ

...es/app/details/TrixoQuestionnaire/TrixoEditForm.js

web/gds-admin-ui/src/redux/vasp-details/sagas.js

web/gds-admin-ui/src/routes/index.js

web/gds-admin-ui/src/constants/index.js

web/gds-admin-ui/src/redux/store.js

.../src/pages/app/details/CertificateDetails/index.js

web/gds-admin-ui/src/components/TimelineItem.js

web/gds-admin-ui/src/pages/app/dashboard/Tasks.js

web/gds-admin-ui/src/helpers/api/auth.js

web/gds-admin-ui/src/pages/app/details/index.js

... and 141 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 fd123f7...f52a86c. Read the comment docs.


WIP: implement ics-721-nft-transfer

Description

closes: #1444

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #1486 (09dbed7) into carlos/sdk-0.46-rc1 (c7c1152) will decrease coverage by 0.69%.
The diff coverage is 42.65%.

@@                   Coverage Diff                   @@
##           carlos/sdk-0.46-rc1    #1486      +/-   ##
=======================================================
- Coverage                79.41%   78.71%   -0.70%
=======================================================
  Files                      150      157       +7
  Lines                    10870    11081     +211
=======================================================
+ Hits                      8632     8722      +90
- Misses                    1812     1927     +115
- Partials                   426      432       +6

Impacted Files
Coverage Δ

modules/apps/nft-transfer/types/ack.go
0.00% <0.00%> (ø)

modules/apps/nft-transfer/types/keys.go
0.00% <0.00%> (ø)

modules/apps/nft-transfer/types/packet.go
32.35% <32.35%> (ø)

modules/apps/nft-transfer/types/trace.go
35.63% <35.63%> (ø)

modules/apps/nft-transfer/types/codec.go
55.55% <55.55%> (ø)

modules/apps/nft-transfer/types/genesis.go
66.66% <66.66%> (ø)

modules/apps/nft-transfer/types/msgs.go
70.21% <70.21%> (ø)

Is this PR considered to be out of scope?  or was it just closed automatically because the branch it references was deleted?

Is this PR considered to be out of scope? or was it just closed automatically because the branch it references was deleted?

Yes, it was closed automatically because I merged this PR. This branch can now be used.


Update readme to indicate specifying false for dist prior behavior

To match behavior prior to adding of dist argument (411c12a19879d06c822a0047f9db78ad7bbc39e0), false must be specified for the argument or else the CLI asks for the value and hangs when an empty string is entered.

Rebased my branch so the commit structure here is a bit messy. Happy to cherry-pick the 2 commits to a clean branch and replace the PR if desired.

We don't need this PR anymore right?

I think it's best to move forward with this PR. It's related to the dist arg (not related to the app_identifier PR).
The dist argument addition made it so that users needed to add dist: false to their call to sentry_upload_file to match previous behavior, which isn't obvious at first glance. Without providing a value, the argument defaults to '' (empty string), which causes the CLI to prompt for the arg. The CLI has a separate bug in which it hangs if no text is entered in the prompt.
I think the best solution is this PR, which makes the fastlane plugin signature match the CLI signature of the dist arg being optional, which prevents users from having to provide false as a value to the string argument to prevent being prompted for a value.
I'll rebase and resolve conflicts.

Replaced by #27 since things have changed a bit since this was opened.


Support Carthage

I not use CocoaPods but Carthage.
Are you supported?

Carthage is not supported at the moment, but I am planning on looking into it. If you want to, you are welcome to create a PR with Carthage support.


Currency calculator

I am a GSSOC 2022 participant and would like to add a currency calculator to this project which would help in the conversion of currencies of different region. I would request you to assign me this work.
Thank you.

I am a GSSOC 2022 participant and would like to add a currency calculator to this project


Add NodeJS v10 to nixos-small channel

v10 is the LTS but it is a breaking change to make it the default on 18.03 so it would be good to add it as build.
This will increase the build time and closure size of nixos-small, but it would be useful for at least my servers.

Argh! Should we revert on 18.03?
Wout.
On Sat., Jul. 27, 2019, 9:27 p.m. Samuel Dionne-Riel <
<EMAIL_ADDRESS>wrote:

@samueldr requested changes on this pull request.
This targets 18.03, which is not supported anymore, and wasn't for a while
when this PR was opened! Should this have targeted 19.03 instead?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/63605?email_source=notifications&email_token=AAANNFQS2IXYDA4CTXAE2LTQBSOSFA5CNFSM4H2PBSP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB7YWVBI#pullrequestreview-267479685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAANNFRJCNACEK7MVCGS543QBSOSFANCNFSM4H2PBSPQ
.

I'm not sure I follow.
Adding anything to the small release for 18.03 would be a no-op, since it was last updated 157 days ago, and will not (should not) receive any more updates.

Closing as this targets the old release-18.03 brach which is not supported anymore.


Merge actions charlie

Merge-in of Github Action to handle file filtering and building the website archive
This:

Grabs PR's marked with ``submission'' label
Runs regex filters on every modified/added/removed files. This file is in `bin/filterpaths.py'
If filters fail, writes a comment on the PR. TODO: make comment say exactly which files are offending. Interrupts the action's flow and marks the PR with a red X to indicate a failure mode.
If filters succeed, downloads the submission's code, builds it (`bin/build'), and uploads it to the github action's artefacts.
TODO: push the artefact to AWS/some other server. Marks the PR with a green checkmark to indicate a successful submission.

Recap of TODOs:

Prevent the default Al_folio from deploying the website upon PRs
Extract offending file information from `filterpaths.py' and push it to the comment
Push website archive to AWS/some other server

TODO #2 is DONE

Thanks @Velythyl ! I suggest we do the last TODO (push to AWS) in a different PR.
For the TODO 1: I suspect that perhaps we need to remove the "on: pull_requests:" part of https://github.com/iclr-blogposts/2024/blob/main/.github/workflows/deploy.yml ?


[SPARK-7715] [mllib] [ml] [doc] Updated MLlib programming guide for release 1.4

Reorganized docs a bit.  Added migration guides.
Q: Do we want to say more for the 1.3 -> 1.4 migration guide for spark.ml?  It would be a lot.
CC: @mengxr

Merged build triggered.

Merged build started.

Test build #35229 has started for   PR 6897 at commit 6cd5c78.

Oops, there are formatting mistakes.  I'll fix them early tomorrow.

Test build #35229 has finished for   PR 6897 at commit 6cd5c78.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
   * *(Breaking change)* Theapplyandcopy methods for the case class [BoostingStrategy](api/scala/index.html#org.apache.spark.mllib.tree.configuration.BoostingStrategy) have been changed because of a modification to the case class fields.  This could be an issue for users who use BoostingStrategy to set GBT parameters.
* *(Breaking change)* The return value of [LDA.run](api/scala/index.html#org.apache.spark.mllib.clustering.LDA.run) has changed.  It now returns an abstract class LDAModelinstead of the concrete classDistributedLDAModel.  The object of type LDAModel can still be cast to the appropriate concrete type, which depends on the optimization algorithm.
   * InDecisionTree, the deprecated class method trainhas been removed.  (The object/statictrain methods remain.)

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #35298 has started for   PR 6897 at commit 4bf26d6.

Test build #35298 has finished for   PR 6897 at commit 4bf26d6.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
   * *(Breaking change)* Theapplyandcopy methods for the case class [BoostingStrategy](api/scala/index.html#org.apache.spark.mllib.tree.configuration.BoostingStrategy) have been changed because of a modification to the case class fields.  This could be an issue for users who use BoostingStrategy to set GBT parameters.
* *(Breaking change)* The return value of [LDA.run](api/scala/index.html#org.apache.spark.mllib.clustering.LDA) has changed.  It now returns an abstract class LDAModelinstead of the concrete classDistributedLDAModel.  The object of type LDAModel can still be cast to the appropriate concrete type, which depends on the optimization algorithm.
   * InDecisionTree, the deprecated class method trainhas been removed.  (The object/statictrain methods remain.)

Merged build finished. Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #35342 has started for   PR 6897 at commit 4bf26d6.

Test build #35342 has finished for   PR 6897 at commit 4bf26d6.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
   * *(Breaking change)* Theapplyandcopy methods for the case class [BoostingStrategy](api/scala/index.html#org.apache.spark.mllib.tree.configuration.BoostingStrategy) have been changed because of a modification to the case class fields.  This could be an issue for users who use BoostingStrategy to set GBT parameters.
* *(Breaking change)* The return value of [LDA.run](api/scala/index.html#org.apache.spark.mllib.clustering.LDA) has changed.  It now returns an abstract class LDAModelinstead of the concrete classDistributedLDAModel.  The object of type LDAModel can still be cast to the appropriate concrete type, which depends on the optimization algorithm.
   * InDecisionTree, the deprecated class method trainhas been removed.  (The object/statictrain methods remain.)

Merged build finished. Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #35347 has started for   PR 6897 at commit 4bf26d6.

Test build #35347 has finished for   PR 6897 at commit 4bf26d6.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
   * *(Breaking change)* Theapplyandcopy methods for the case class [BoostingStrategy](api/scala/index.html#org.apache.spark.mllib.tree.configuration.BoostingStrategy) have been changed because of a modification to the case class fields.  This could be an issue for users who use BoostingStrategy to set GBT parameters.
* *(Breaking change)* The return value of [LDA.run](api/scala/index.html#org.apache.spark.mllib.clustering.LDA) has changed.  It now returns an abstract class LDAModelinstead of the concrete classDistributedLDAModel.  The object of type LDAModel can still be cast to the appropriate concrete type, which depends on the optimization algorithm.
   * InDecisionTree, the deprecated class method trainhas been removed.  (The object/statictrain methods remain.)

Merged build finished. Test PASSed.

Ping @mengxr  What do you think?

LGTM. We don't need to mention detailed 1.3 -> 1.4 changes. Merged into master and branch-1.4. Thanks!


MFC Recorder (windows mfc2.exe error)

When i start mfc2.exe on win7 receive this error:
[08:31:26] [Server listening on: [<IP_ADDRESS>:8888]
[2019/03/24 - 08:31:27] >>> Connecting to MyFreeCams chat server [xchat85]
[08:31:28][Error: Command failed: "C:\nm-mfc2\mfc2.exe" -e "setTimeout(function () { return true; }, 2000);"
internal/modules/cjs/loader.js:594
throw err;
^
Error: Cannot find module '-e'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:592:15)
at Function.Module._resolveFilename (pkg/prelude/bootstrap.js:1278:46)
at Function.Module._load (internal/modules/cjs/loader.js:518:25)
at Function.Module.runMain (pkg/prelude/bootstrap.js:1307:12)
at startup (internal/bootstrap/node.js:274:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:608:3)
Any sugestion?
Used package.json:
{
"name": "mfc2",
"license": "ISC",
"bin": "main.js",
"pkg": {
"scripts": ["main.js"],
"assets": ["index.html","favicon.ico"],
"targets":["node10"]
}
}
This error is only for MFC Recorder v.3.0.6 who uses MFCAuto, I haven't this problem with v.1.0.7 who uses WebSocket

Successfully resolved.
The problem was the 'system-sleep' module which I removed now.


importing matplotlib seems to error in ci

It seems like the ci fails when it tries to import matplotlib from tester.py.
The pyplot is not used in the continuous integration test, so we can make a workaround where there is a separate module called plotter, and delete the plotting function from tester.py.
related to #146 .

#150 is a workaround


bibxml citation URLs?

Description
Not sure where to officially ask for this, but I understand the ietf is moving all the bibxml citation indices to new URLs. Mmark has been using xml2rfc.ietf.org for a while now, but it seems that https://www.rfc-editor.org/refs/bibxml should be used for RFCs and I-Ds directly from the data-tracker?
Tried searching authors.ietf.org but could not quickly find it?
What are the correct URLs currently?
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

Here is what kramdown-rfc uses as of 1.6.17 (default settings):

RFC: https://www.rfc-editor.org/refs/bibxml
I-D: https://datatracker.ietf.org/doc/bibxml3
STD, BCP: https://bib.ietf.org/public/rfc/bibxml-rfcsubseries
DOI: uses internal engine (bib.ietf.org engine is unreliable)
Everything else: https://bib.ietf.org/public/rfc/(insert computed path):
"W3C" => "bibxml4",
"3GPP" => "bibxml5",
"SDO-3GPP" => "bibxml5",
"ANSI" => "bibxml2",
"CCITT" => "bibxml2",
"FIPS" => "bibxml2",
"IEEE" => "bibxml6",
"ISO" => "bibxml2",
"ITU" => "bibxml2",
"NIST" => "bibxml2",
"OASIS" => "bibxml2",
"PKCS" => "bibxml2",
"IANA" => "bibxml8",

Thanks for that list!
it may also be nice if xml2rfc would just insert the xi:incudes (at least that's what mmark now generates) itself? Guess kramdown-rfc and mmark now use generate the same xref tag/content anyway, so why can't xml2rfc inject this when it sees an ?

Well, one problem is that xml2rfc cannot be as opinionated at the author tools.
E.g., for my list, I decided to give up on the DOI source in bib.ietf.org.
I'm not sure that the official LLC will want to do that.
Similar for Rfc-editor and datatracker vs. bib.

(Oh, please edit the comment to reveal what is behind "an ?".
Do not use full XML tags in running text in github...)

I see, had similar issues with pandoc2rfc so decided to play dumb in mmark and only do references that are contained in the IETF space (and w3c, but that broke somewhere in the last months, proving my point).
However if the ietf hosts these lists, why do I need to figure out where they live and track how they are moved around? Much easier to have an ietf tool (=xml2rfc) do it.

It seems to me that the set of sources outside I*TF/RFC-Editor needs to be rethought at some point.
That was not part of the current bib.ietf.org project as far as I can tell.
Any reorganization requires a sync between the server space and the xml2rfc version in use, which may be locally installed and thus update on a separate timeline...
(The XML grammar does not allow to reference undefined IDs, so there is another technical hurdle.)

The authors site has a page on XML references at https://github.com/ietf/authors.ietf.org/blob/main/references-in-rfcxml.md
If one of you added a section describing where to look for various kinds of references I expect many authors would be grateful.

maybe this issue would be better homed at bibxml-service? If there's anything xml2rfc specific to split out, we could do so.

What Miek proposed is that xml2rfc should act on missing reference imports and figure out how to get them and just integrate them.  This is to a certain extent what kramdown-rfc does.  xml2rfc has the problem with unresolved IDREFs, so the document would fail to validate.  But maybe we can validate after the reference fill-in?  (The problem with indicating normative vs. informative remains, but that is really a limitation in RFCXML -- each citation should say whether it is normative, and the processor can then figure out where to put it.)

For ID submission we're going to move to requiring a self-contained document (with a user-friendly way to retain source that has external references to things that can change of course). The gearing to help support that could be leveraged for "validate after reference fill-in". Maybe we create a "This is a bad reference" special reference target to assist?

The goal for bibxml.ietf.org would be to make it such that tools like kramdown could use it for everything it needs. We will be working to close the gaps that Carsten experienced for e.g. DOI,

That is one possible goal.  One other way to handle this is to have the authoring tools as trailblazers, and only integrate something into the broader offering once it starts to stabilize.  That had happened with the doilit tool in 2016 (well, there still have been substantial fixes).  See #326 for the discussion at the time.  bibxml7 was easier to maintain than xml2rfc support, because it could be updated in a centralized manner.

What Miek proposed is that xml2rfc should act on missing reference imports and figure out how to get them and just integrate them.

Yes this (and +1 to the rest of that comment)

The authors site has a page on XML references at https://github.com/ietf/authors.ietf.org/blob/main/references-in-rfcxml.md

ah, yes, but lacks how to actually pull out the reference and how to piece together the xi:include -  which, I see, is what you propose I add, except I don't know either, think @cabo has reversed engineered this.
Coming back to @cabo's comment: yes xml2rfc can just generate these, just like kramdown-rfc and mmark do now, that would move common code into xml2rfc. Can't speak for kramdown-rfc, but mmark will just put out the Normative vs Informative just fine (having it in the xref tag would be even better). This would be the ask for xml2rcfc - for authors.ietf.org we would only need to tell how to format each reference, or abstract that even, as xml2rfc is in full control


Want to merge this in to the main repo?

Thanks for the contribute- would love to see this merged in 👍

Thanks for putting my changes in, I'm glad I was able to contribute!


Original d&d character sheet

Changes / Comments
One more try.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Still getting the issue with Moldvay. Please delete this branch.


Add CentOS Stream 9 support

This pull request includes:

[x] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

I put the wrong usernames for the CI runners in the terraform config.  The images were created with cloud-user for openstack and ec2-user for AWS.
Fix PR: https://github.com/osbuild/gitlab-ci-terraform/pull/39

FTR so far I did these changes:

fixed mockbuild so it supports centos stream 9
rebase to latest main to pickup the terraform runner changes

schutzbot/terraform conflict: the new hash in main points to a commit in the gitlab-ci-terraform repo that's on a branch (rhos-01).  Will this be merged into gitlab-ci-terraform/main?
Manifest tests: I used the latest production repos [0] for the tests.  This will cause issues with changing package versions.  We're going to need a repo snapshot.
[0] -https://composes.stream.centos.org/production/latest-CentOS-Stream/

schutzbot/terraform conflict: the new hash in main points to a commit in the gitlab-ci-terraform repo that's on a branch (rhos-01). Will this be merged into gitlab-ci-terraform/main?

Not necessarily, main is currently used for projects that use RHOS-D (image-builder, osbuild), whereas rhos-01 is used in osbuild-composer that uses RHOS-01. If you need to make any changes in rhos-01, feel free to send a PR. @lavocatt knows everything if you need help. :)

schutzbot/terraform conflict: the new hash in main points to a commit in the gitlab-ci-terraform repo that's on a branch (rhos-01). Will this be merged into gitlab-ci-terraform/main?

Not necessarily, main is currently used for projects that use RHOS-D (image-builder, osbuild), whereas rhos-01 is used in osbuild-composer that uses RHOS-01. If you need to make any changes in rhos-01, feel free to send a PR. @lavocatt knows everything if you need help. :)

oh, okay.  I thought the new flavour ID was necessary in general because I saw some failures in the previous run with message Flavor could not be found [0].
[0] - https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1904731287

Updates

Added s390x for CS9
Changed test repositories (test/data/repositories/centos-9.json) and test case generator repositories (tools/test-case-generators/repos.json) to use the new rpmrepo snapshots.

Main repositories (repositories/centos-9.json) still point to latest production repos.

(Re)generated all test cases, including s390x, for the new repos.

Moved all CS9 tests to internal network for
https://github.com/osbuild/osbuild-composer/blob/0faf8a2ec291f0582a12e6f88749e97c31091bfc/tools/provision.sh#L14-L18

OSTree tests are failing with
curl: error downloading {'url': '...'}: error code 23

which likely means they runner is out of space (some tests even say so).
Is this an issue with the image in openstack?  What controls the instance storage size?

@lavocatt any ideas on the disk space in RHOS-01?

Hey! Yes Ladislav gave us the properties of the machines https://docs.google.com/spreadsheets/d/18IznFSzRDRPwdV9cAlz4L1OhnCWQ8S6l3F5L2HieyII/edit#gid=0 I think that we still need to use the ssd flavor for ostree tests, but we can bump from to medium or large for the one that is crashing ? You can also have a try with a disk focused flavor if you want.

Which flavor do we use now?

openstack/rhel-8.5-ga-x86_64 and openstack/rhel-8.6-nightly-x86_64 are using the flavor f2c4469b-f516-46d1-8b87-1dcca68fb3d9 which is ci-ssd.standard.medium I've just notice however that we could use 77f58261-d373-4749-8781-aff678329d57 which is ci-ssd.disk.medium that gives us 60 gigs of storage instead of 40.

I already added c3ec7a0a-0443-4253-a6ab-040cc0278ced to the Terraform config as centos-stream-9-large, which corresponds to ci-ssd.standard.large.  That's 60 GB.
That was meant for OSTree tests and I accidentally added the standard to one to all of them.  Running with large noe.

@achilleas-k I re-build installer ISO file with function. Everything works well.
I suspect the Volume id in the ISO file. I checked CentOS-Stream-9-latest-x86_64-boot.iso and got the following info.
I can't find volume id for centos.
$ isoinfo -d -i CentOS-Stream-9-latest-x86_64-boot.iso
CD-ROM is in ISO 9660 format
System id:
Volume id: CentOS-Stream-9-BaseOS-x86_64
Volume set id:
Publisher id:
Data preparer id: XORRISO-1.5.4 2<IP_ADDRESS>001, LIBISOBURN-1.5.4, LIBISOFS-1.5.4, LIBBURN-1.5.4
Application id:
Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 388096
El Torito VD version 1 found, boot catalog is in sector 40
Joliet with UCS level 3 found
Rock Ridge signatures version 1 found
Eltorito validation header:
    Hid 1
    Arch 0 (x86)
    ID ''
    Key 55 AA
    Eltorito defaultboot header:
        Bootid 88 (bootable)
        Boot media 0 (No Emulation Boot)
        Load segment 0
        Sys type 0
        Nsect 4
        Bootoff 161D 5661

@henrywang thanks for looking into this.
Looks like the volume ID should be CentOS-Stream-9-BaseOS-$arch.  I had reused/adapted the one from the CentOS Stream 8 which was CentOS-Stream-8-$arch-dvd.

I think we should switch to using the development repositories for CS9 for now:
https://github.com/osbuild/rpmrepo/pull/20

@achilleas-k I upgraded my CS9 test VM, and run test again. Everything works great!
[admin@centos-stream-9-220110 rhel-edge]$ rpm -q osinfo-db
osinfo-db-20211216-1.el9.noarch
[admin@centos-stream-9-220110 rhel-edge]$ sudo osinfo-detect 6d7dfb07-e80f-4300-8ee3-1454ff8bf613-installer.iso
Media is bootable.
Media is an installer for OS 'CentOS Stream 9 (x86_64)'

Resolved merge conflicts
Made a new rpmrepo snapshot and switched the repo configs for the tests
Updated the cs9 manifests

CS9 New OSTree test was hit by rhbz#2046612.  Fixed by updating repos, but that means updating the greenboot packages, so we're either blocked on #2196 or we absorb it into this one.
I don't know why the F35 OSTree test is failing.

Rebased on #2196

Rebased on main.


DUPLO-21304 DUPLO-21209 Aurora/v2: replica tries to set value as nil for inplace update and inplace update fixes

Overview
Fixed aurora db updation for performance insights state and plan issues
Summary of changes
Fixed plan issues,
Fixed replica performance insights issue,
Updated doc example
This PR does the following:

Fixed logic at read replica's create and update context for aurora cluster performance insights
Fixed plan issues
updated documentation

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[✓ ] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-21209 TF:RDS: Update of 'Performance Insight' to false along with 'Retention Period' shows update in place  for plan
Task linked: DUPLO-21304 Aurora/v2: replica tries to set value as nil for inplace update


Setup basic CI worflow

Changes:

require exact SOEM version (v1.4.0) in CMakeLists
add pre-commit config
add CI workflow (format + build tests)
refractor / general clean-up

TODO: add basic build tests.
At least with to build and run an executable that uses the SOEM lib (e.g., get current version).

Ok ça me paraît un bon programme.


Generate charts

Hey,
Do you have plans about generating charts from a query's result?
Like Hue for example.
Thanks.

Not at the moment, but i thought about adding a very basic charting feature in the past.

I think it should be great to have this kind of feature even it's really basic. If people want more they always are able to customize it (and make a PR).

Im going to keep the issue open in case i have time to work on it or someone else decides to contribute.


F1-001-fix-turn-transition

Fix turn transition issue
Max speed will be around 10 for now but unsure if this will change later
Working on keeping track of laps but might put that in a separate PR.
I added more drivers
I resolved the flickering pixels of the objects but, as a result of this fix I am getting the lines again which are OK for the meantime while I test.
Planning on writing some integration tests once I get all drivers successfully doing some laps.

Transitioning through turns is better now for all drivers. I'm now keeping track of the number of laps done for each driver.
Still need to work on maximum laps.


#rrggbbaa Color format not working for borderTopColor.

I am trying to use #rrggbbaa formatted color code for borderTopColor property of my view and it's not working.
e.g. I am using below style,
borderTopColor: "#e8e8e85a" for 35% opacity but it has no effect on opacity. When I use same style for backgroundColor, it works as expected.
I found this problem on IOS 9.3.
Thanks!

iOS or Android?

I faced this problem on IOS. Haven't tried on Android.
IOS version: 9.3
Device: Iphone 5s.

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.


Not able to parse structure variables having the same name as a user defined type using typedef

Consider the below structure,
typedef struct
{
int number;
}Number;
struct XYZ
{
Number Number[10];
}xyz;
PyCParser is not able to parse the 2nd structure, its complaining about Number[10]. The above is a valid C declaration.

This is already fixed. (See a33fce5e.) (Better late than never.)


Feature request: Exclude layers from 3D right-click navigation

I love neuroglancer's right-click behavior in the 3D view, which quickly jumps to an object when I click on it.  However, there's a common situation in which that feature is impaired.
When a neuron is visualized in the 3D view within a compartment mesh, then the compartment mesh "gets in the way" when I try to quickly navigate to a point on the neuron.  For example, try clicking on a neuron mesh in this view.  Here's a similar example. The viewer navigates to the compartment exterior, not to the neuron.
I propose an extra checkbox in the render tab to enable/disable right-click navigation.
Alternatively, it might suffice to simply assume that if spatial object selection is disabled for a layer, then it should also be excluded from right-click navigation in the 3D view.  That would work well when the layer represents whole compartments, but I'm not completely sure if it's desirable when the layer represents internal organelles.  Maybe it depends on each use-case.

This is actually a recent change introduced by this commit:
https://github.com/google/neuroglancer/commit/125da1b835b310171161b1a57901bf08cf837d70
That commit was intended to solve the problem that annotations (which are opaque) inside transparent meshes could not be picked except by disabling spatial object selection on the layer responsible for the transparent mesh, which may not be desirable.
However I didn't think about the impact on the case where you have transparent neuron meshes inside transparent ROI meshes.
One option could be to treat layers with "spatial object selection" disabled as lower priority (i.e. only picked if there is nothing from a layer with spatial object selection enabled along the same day), as they were prior to that commit.  That way an additional option isn't needed.  But in general it seems like some explicit priority option might be needed.

Ah!  Thanks for the link; that explains what's going on.  I didn't realize the opacity of the mesh was a factor in the selection.

One option could be to treat layers with "spatial object selection" disabled as lower priority

Yeah, this would work for ROI meshes, but I'm still not sure exactly how to treat organelle layers.  In the examples above, mitochondria aren't explicitly spatially-selectable (instead, they're implicitly selected via their linked neuron layer), but I do want to be able to navigate to them.  Are you suggesting the following priority ordering?

opaque and selectable
opaque and not selectable
transparent and selectable
transparent and not selectable

That makes sense to me.
I guess there are still edge cases, but I don't know if they're worth worrying about.  For instance: If I want to navigate to a neuron, but there happens to be an unrelated mitochondria lurking directly behind it by chance, then the ray might catch that one, even if it's far in the background.  But, that's unlikely, and no simple solution to that comes to mind that could work in every conceivable scenario.

The priority I imagined would be:

Opaque objects
Transparent with spatial object selection enabled
Transparent with spatial object selection disabled

That would still have the stray mitochondria problem unless you change the mitochondria to be transparent as well.
I suppose instead it could be:

Opaque objects with object selection enabled
Transparent objects (in front of any opaque objects) with object selection enabled
Opaque objects with object selection disabled
Transparent objects with object selection disabled

That would fix the mitochondria.
Priority between two different opaque objects would not be relevant since you could never pick anything but the front-most opaque object (I don't think it makes sense to pick something you can't see).

I guess either ordering is fine for me.
If you decide on the second ordering, I'll have to make sure I enable spatial selection in the hemibrain mito layer.  It's currently disabled, but enabling it isn't a problem.  Since it's linked to the segmentation layer, I get the proper behavior in either case.  If I don't enable it, I won't be able to jump directly to mitos any more.

With your recent fix, the situation is improved, thanks.  But after using it for a while now, I think we still need explicit layer setting to disable right-click navigation for ROI meshes.
In my example above, it's still too easy to accidentally "grab" the ROI mesh.  Yes, if I position my mouse very precisely over the neuron I'm aiming for, I can jump to it.  But if the ROI mesh is visible, then I'm likely to jump to the ROI instead.  Navigation is smoother for me when the ROI is hidden. In that case, some imprecision in my mouse position is tolerated, and it still jumps to the correct neuron.  (Or, if my positioning is too imprecise, at least the view doesn't jump at all, in which case I can just click again.)
Perhaps that might sound like I'm just uncoordinated with my mouse. :-)  But when rapidly navigating a 3D structure (e.g. for proofreading purposes), it really helps to have some tolerance for imprecise clicks.  The response is excellent when the ROI mesh is hidden, but I'd love to have the same experience when the ROIs are visible.
Do you mind if I re-open this issue?

Yeah, certainly if the mesh is thin it can be hard to click on it, which is why the current tolerance for picking was added (first implemented by the seung lab in their fork).
The way the tolerance is implemented is that neuroglancer checks a 11 pixel diameter circle centered on the mouse position, and chooses the position closest to the center with picking information.
A simple solution implementation-wise would be to just add an option that prevents the layer from affecting the pick buffer at all.  That would mean hovering over the roi mesh also would not highlight the mesh either.
An alternative would be to also take picking priority (i.e. whether spatial object selection is enabled, and possibly whether the object is transparent or opaque) into account when choosing the best position within the 11 pixel diameter region, rather than just distance to the center.

A simple solution implementation-wise would be to just add an option that prevents the layer from affecting the pick buffer at all.

I think that would be easiest for users to understand and control.

That would mean hovering over the roi mesh also would not highlight the mesh either.

That would be desirable, too.


Update hexkit and other dependencies

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 85.283%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
452

Relevant Lines:
530

💛  - Coveralls


[Runtime API] Implement Resource watch mechanism for k8s resource create/delete/update operations

Description:
This issue is created to track the progress of the resource watching mechanism for k8s resource create, update, delete operations.
As we discussed we will be using Informer in client-go library.

I have done a POC on this and the details can be find in : https://docs.google.com/document/d/1SFjyG9I495pW40dziXQVnN_deIx3AIXkD1oSDhqIPos/edit#

Closing this as the work related to this scope is completed..


Feature/add git aliases

With this pull-request two new git aliases will be introduced and the .gitignore file will be updated:

Add alias gfa to fetch all changes easily
Add alias gla to easily access git lola (http://blog.kfish.org/2010/04/git-lola.html)

This PR is very stale, so I close it. Thanks for contributing and posting!


CI / docker improvements

Right now we use pytest-docker to start ancillary containers for testing, namely a slurm-cluster-in-docker to submit jobs to.
Currently the fixtures

tar the server code
pre-install hardcoded server dependencies to create a cached layer
build the docker images, installing the dev version of the server
start the containers
typically do not cleanup the containers if the test suite is keyboard interrupted.

We should

[ ] only create a new tar if there were changes with respect to the last run
[ ] avoid hardcoding the dependencies, possibly by automating a call to poetry export --without-hashes -E slurm and caching its hash, so that we rebuild the layer only when needed.
[ ] find a way for docker to exit gracefully

Cache of the environment can be obtained as in https://github.com/fractal-analytics-platform/fractal-tasks-core/blob/main/.github/workflows/ci.yml

Concerning the hardcoded requirements.txt, there doesn't seem to be any relevant speedup in having this cached layer.  See for instance:

https://github.com/fractal-analytics-platform/fractal-server/actions/runs/3795129574
https://github.com/fractal-analytics-platform/fractal-server/actions/runs/3794999005

Let's just remove this feature, since it also means a higher complexity - see #389.

Re: "only creating a new tar if something changed", this does not appear as a way to significantly reduce runtimes.
Re: "proper cleanup", this is in principle already implemented.
Closing for now.


[Feature request] Docker support

Would be a pretty easy way to keep it alive for people who have servers.

Tried to do it myself. It starts up with an error (due to systray) but it works.
Try:
docker run -v /my/dir/:/root/.local/share/PimpMyStremio/ fidelix/pimpmystremio
Then check http://localhost:7777
This would become a lot cleaner if PimpMyStremio adds an option to specify port, location of settings directory and a "headless" mode on the startup command (to avoid tray and opening the browser).

What Dockerfile did you use to build it?

This would become a lot cleaner if PimpMyStremio added an option to specify port, location of settings directory and a "headless" mode on the startup command (to avoid tray and opening the browser).

I can add command line arguments to specify the port, location of settings directory and a headless mode, it shouldn't be hard.
I'm up to making a docker image.

FROM lsiobase/ubuntu:bionic
WORKDIR /app
RUN apt-get update
RUN DEBIAN_FRONTEND=noninteractive apt-get install -qq -y unzip curl
RUN curl -L -O https://github.com/sungshon/PimpMyStremio/releases/download/v1.2.2/PimpMyStremio-linux.zip
RUN unzip -j PimpMyStremio-linux.zip
RUN ls -la /app/
RUN chmod +x /app/PimpMyStremio
EXPOSE 7777
VOLUME /root/.local/share/PimpMyStremio/
ENTRYPOINT ["/app/PimpMyStremio"]

Super interested in this, I run my home server and it would be really easy to manage as a docker container that can be accessed remotely.

Tried Alpine, but it simply doesn't work. It gives a bizarre error when executing the entrypoint.
"standard_init_linux.go:211: exec user process caused "no such file or directory"

That's because the PMS linux binary is linked against GNU libc and Alpine uses musl libc, so it will not work. You can confirm this by installing and running file on the binary:
/app # file PimpMyStremio
PimpMyStremio: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=05ec200467657de71de5edd9f18e14bee2ec9a83, with debug_info, not stripped

See this issue on the Alpine repo for more info.

PimpMyStremio's packager supports alpine as a build target out of the box, so if my PR gets approved and a new build published, we could get it to work on Alpine without any workarounds :)

Forget that, I got it working using an alpine-glibc image. Execute docker run -p 7777:7777 sleeyax/pimpmystremio to give it a spin.

@sleeyax Any chance you could make a PR with the Dockerfile? I could publish an official Docker image for PMS if u make a PR.

@sungshon sure, Ill create a PR in a moment

For reference: PR https://github.com/sungshon/PimpMyStremio/pull/85 opened.

@sleeyax thanks!


Usage of endDelimiter in scripts now require spacing

Environment
Liquibase Version: 3.10.3
Liquibase Integration & Version: maven
Liquibase Extension(s) & Version:
Database Vendor & Version: MySQL
Operating System Type & Version: OSX 10.15.7
Description
We are in the process of upgrading Liquibase from 3.3.1 to 3.10.3.  The following worked correctly in 3.3.1.
We have stored procedures that are created via Liquibase.  Given the following changeset definition:
<changeSet author="xxx" id="123" runOnChange="true">          <sqlFile path="xxx/xxx/db/changelog/stored_procedures/xxx/storedProcedure.sql" relativeToChangelogFile="false" endDelimiter="\$\$" /> </changeSet>
Liquibase fails on the following line:
`DELIMITER $$
DROP PROCEDURE IF EXISTS storedProcedure$$`
If we modify the statement to have a space between the stored procedure name and end delimiter it works correctly.
`DELIMITER $$
DROP PROCEDURE IF EXISTS storedProcedure $$`
Steps To Reproduce
List the steps to reproduce the behavior.
We are executing Liquibase using the liquibase-maven-plugin
Actual Behavior
Statements executed where there is no space between a statement and the end delimiter fail with the following error:
[ERROR] Error setting up or running Liquibase: [ERROR] Migration failed for change set storedProcedure.xml::123::xxx: [ERROR]      Reason: liquibase.exception.DatabaseException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CREATE PROCEDURE at line 3 [Failed SQL: (1064) DROP PROCEDURE IF EXISTS storedProcedure$$
Expected/Desired Behavior
MySQL allows no spacing between and end delimiter and statement so we feel that this functionality should be restored
┆Issue is synchronized with this Jira Bug by Unito

Hi @kraymondksc Thanks for writing up this issue.  We will add it to the list of issues that we are processing.

Hi @kraymondksc Thanks for writing up this issue.  We will add it to the list of issues that we are processing.

The reason the problem comes up now is because we 3.10 we use a smarter, tokenizing parser for splitting vs. the simple string regular expression we had in 3.3. That lets us do things like "it doesn't split on $$'s that occur inside comments or strings".
Unfortunately, the tokenizing happens on spaces, so we now see a token as DELIMITER$$ and our "is X a delimiter" is checking "does it completely match "$$" fails on that. The space makes it see it as two separate tokens and it correctly identifies the delimiter".
I don't think we can easily change the tokenizing logic, because there are databases with tokens that end with $'s and we need to respect that too.
The easiest fix for you may be to just remove the DELIMITER$$ lines from all your scripts. Liquibase doesn't actually need it, since we use the endDelimiter attribute to know how to split statements. We'd just be passing the DELIMTER statement to the underlying database which just ignores it since the database doesn't care either. It's just the mysql client that uses DELIMITER.

The reason the problem comes up now is because we 3.10 we use a smarter, tokenizing parser for splitting vs. the simple string regular expression we had in 3.3. That lets us do things like "it doesn't split on $$'s that occur inside comments or strings".
Unfortunately, the tokenizing happens on spaces, so we now see a token as DELIMITER$$ and our "is X a delimiter" is checking "does it completely match "$$" fails on that. The space makes it see it as two separate tokens and it correctly identifies the delimiter".
I don't think we can easily change the tokenizing logic, because there are databases with tokens that end with $'s and we need to respect that too.
The easiest fix for you may be to just remove the DELIMITER$$ lines from all your scripts. Liquibase doesn't actually need it, since we use the endDelimiter attribute to know how to split statements. We'd just be passing the DELIMTER statement to the underlying database which just ignores it since the database doesn't care either. It's just the mysql client that uses DELIMITER.

Thanks for taking a look.  We have a few different options to move forward with given that this only happens with a handful of our scripts.

Thanks for taking a look.  We have a few different options to move forward with given that this only happens with a handful of our scripts.


KNOX-2262 Accessing hbase logs through knox exposes hbase endpoint ur…

…l instead of routing through knox

Add redirect filter for HBase webu /logs location
Perform Request URL trailing space correction in HBase dispatch
Remove deprecation from HBase dispatch
Add HA dispatch for HBase ( identical functionality to non-HA)
Refer HA dispatch in service.xml
Refactor common dispatch logic into HBaseRequestUtil.java

How was this patch tested?
Deployed patched Knox on a live HBase cluster
checked that I can access the directories, and the files in the subdirectories
checked that the links and redirects all go to Knox proxied URLs

Sorry @stoty this definitely fell off my radar after I initially looked at it.

Thanks for the review @risdenk, it happens.
Actually I don't think that the decodeUrl() method does anything useful (anymore) either, considering that a lot of folks were running without the old dispatch, since it didn't apply to the HA setup.
However that was not a can of worms I wanted to open, so I left it alone.

Thanks @stoty I made some slight changes locally, but planning to commit this today.
I created HBaseUIDispatch and HBaseUIHADispatch so we can avoid the deprecated HBaseDispatch. I made the newer UI dispatches not use the decodeUrl since that isn't needed.

Thanks for the review and cleanup @risdenk


Automatic Start

I need always use ctrl+alt+o to activate. I would like activate it automatically.

Add this line to your init.coffee: (Edit>Init script)
atom.commands.dispatch(atom.views.getView(atom.workspace), 'activate-power-mode:toggle')

In the package settings you can select the autoToggle checkbox.


Battery level and ringing sensor stopped working when upgrading from 1.1.0 to 2.2.x

Describe the bug
Since upgrading from 1.1.0 to 2.2.0 and then 2.2.2 the battery reports 0% and the ringing sensor never changes from False
To Reproduce

View battery sensor entity, always 0%
Press doorbell, ringing sensor never changes from False

Expected behavior
Battery should report value
Doorbell ringing should go True when pressed
**Hardware Information about Home Assistant
**Hardware Information about Cameras

Eufy 2k Battery

Additional context
All was working fine in 1.1.0
I updated to 2.2.0 when I saw the new version and from then it was broken. I've completely removed the configuration and HACS integration and readded it, but its still the same.
The doorbell does ring, the homebase works, my Eufy app sends me a push etc.
Let me know what additional debug I can provide and I will
Thanks

I need error logs if any, if not, debug logs please, at least for ringing sensor.
For battery, there is an open issue here: https://github.com/bropat/eufy-security-ws/issues/57

Sorry, can you humour me on how to provide these?
Also, it is possible for me to downgrade to 1.1.0 to see if it starts working agian? its not available in the release list inside HACS, only 2+ is
Re new tickets, will move converstaion there 👍

Linking issue #324 here.


[UI] Move reset/load/restore buttons into timeline

See commit message of closing commit for why this wasn't realized


Task - comprehensive specimen - repository

Add repository field (same as in the New Type specimen task). I would like to use this form to add new type specimen from the literature.

My fault, it is already there :)


repeat in queryParam in RAML 0.8 when generating controllers

Hi!
I'm wondering, why an query parameter with
repeat: true

does not work somehow if generating controllers for Spring etc. - did this ever do or is the implementation not finished? Does somebody have an example how to specify it in a RAML file then if it should be working with 0.8?

If memory serves,  this should generate an array of whatever the type is specified. I'll check in more detail tomorrow

Thanks. To be a bit more precise after rereading my post - yup I would also expect the Controller "header" to be
´´´
String[] foo
´´´
instead of
´´´
String foo
´´´
for these params

This should be included in the next release


protocol support > 14

Hi,
is there any planned protocol upgrade, like Lima or Mumbai? We have one tezos (octez) node with Limanet and crawler ended up with store.metadata_not_found
log file ended up like this
2023/01/09 11:58:43.252880 INFO BLOC Processed 132 blocks in 10.09s (34599 transactions, height 2793352, 2022-10-13 23:46:44 +0000 UTC, q=0, t=37.833849ms, s=syncing
)
2023/01/09 11:58:52.197086 WARN BLOC crawler: RPC: tezos: kind = "permanent", id = "store.metadata_not_found"
2023/01/09 11:58:58.375710 INFO BLOC Reorg at height 2793471: parent BMDMopLtrwUTSG3PCBKryKRoQgQGKZJi27KRW1pjyqgvq8fJWwZ is not on our main chain, have BLqfmdk3he2DoiaoR8U8CPubefpFq4EkaP9VmhK8P9NjVGKJaQ1
2023/01/09 11:58:58.375734 INFO BLOC REORGANIZE: searching fork point side=BLqfmdk3he2DoiaoR8U8CPubefpFq4EkaP9VmhK8P9NjVGKJaQ1 main=BKjV8TaCuygYuh5jiSSG8bpX1nhsNHA1xwhdoMgG9pE6zakgKgc
2023/01/09 11:58:58.418870 ERRO BLOC Reorg failed: cannot find fork point in last 100 blocks
2023/01/09 11:58:58.420990 INFO BLOC Stopping blockchain sync due to too many errors at 2793472.
2023/01/09 11:58:58.441063 WARN BLOC crawler: RPC: tezos: kind = "permanent", id = "store.metadata_not_found"
2023/01/09 11:58:59.512891 INFO BLOC Stopping blockchain ingest on cancel.

Thanks

Hi, the store.metadata_not_found error looks like the node is not an archive node and has pruned older blocks already (this happens with rolling nodes, they only keep block metadata for 5 cycles). If it is an archive node it is probably not running with --metadata-size-limit unlimited. In that case there's not much to do other than resync or temporarily use another archive node like rpc.tzstats.com
Oh the Lima upgrade, sorry for the lag. Our PRO version is updated, but there was no time and no funding to also update the open source release yet. I see if I can get this done early next week. Mumbai work is waiting for funding too.

Thanks, @echa will check once again our tezos nodes

@echa,
hmm, so checked - we're running with --network mainnet --history-mode archive --metadata-size-limit unlimited. Is there any other way I can validate the data and metadata in tezos itself?
when I try octez rpc get /chains/main/checkpoint I get
{ "block":
   { "level": 3047425, "proto": 15,
     "predecessor": "BLT6NBvmGXF7wvMtCrxzitnmVc9stZobjbx2zcxHBDRYkfYa9rG",
     "timestamp": "2023-01-11T06:27:14Z", "validation_pass": 4,
     "operations_hash":
       "LLoadpZD3TVk6ZQyos12NRS43tBaaD4hp5WDtnFN3gsETNHwo95EP",
     "fitness": [ "02", "002e8001", "", "ffffffff", "00000000" ],
     "context": "CoVSu2ruJvYmoqaCF5JK4gnWRrLPBUgFUfsWui4QquGWTxziTPGS",
     "protocol_data":
       "dfba531e7820aafc63b539562a895ed18d7c46ea9ff796577264b11e2643aef400000000763259c59f7002000000ffa3a61e5506db123d56ae5b81e84e8d38e23521cb8fe4c5988b9923c96656555935d1db585eb82f9de149ab318921221123b3137f54c99c71bcfada3672a104" },
 "savepoint": 0, "caboose": 0, "history_mode": "archive" }

Can you successfully fetch blocks 2793471 BKjV8TaCuygYuh5jiSSG8bpX1nhsNHA1xwhdoMgG9pE6zakgKgc and 2793472 BLqfmdk3he2DoiaoR8U8CPubefpFq4EkaP9VmhK8P9NjVGKJaQ1 (the should contain metadata). You can also append ?metadata=always to the URL (don't know about octez-client) to make the node reconstruct pruned/missing metadata for that block and its operations.

{ "protocol": "PtKathmankSpLLDALzWw7CGD2j2MtyveTwboEYokqUCP4a1LxMg",
  "chain_id": "NetXdQprcVkpaWU",
  "hash": "BKjV8TaCuygYuh5jiSSG8bpX1nhsNHA1xwhdoMgG9pE6zakgKgc",
  "header":
    { "level": 2793471, "proto": 14,
      "predecessor": "BMDMopLtrwUTSG3PCBKryKRoQgQGKZJi27KRW1pjyqgvq8fJWwZ",
      "timestamp": "2022-10-14T00:46:14Z", "validation_pass": 4,
      "operations_hash":
        "LLob34Tbeu32x3eVYAvZ3ZL3T81h8eGEUuCDh1WeWG2AjG7eWBcTB",
      "fitness": [ "02", "002a9fff", "", "ffffffff", "00000000" ],
      "context": "CoVf7AicBNaAYDFqGm4Yv5buqPrFtRp6VqoS7yfTczDJ7fxPhasd",
      "payload_hash": "vh2oVz4oBdXkH3RTTZejGvRuzqsHp7dYqL6nkyhb65chYv9XzyaQ",
      "payload_round": 0, "proof_of_work_nonce": "4ca331941c230100",
      "liquidity_baking_toggle_vote": "pass",
      "signature":
        "sigb2xSZQwZSFhoritnbAMmPjF1WTG7RoWn2SuZ86bSEkjtqRtkrzbwG1BuNRUKsga4Grc6GWRnRmDKCNZnvZP2M1mcv5P5Y" },
  "metadata":
    { "protocol": "PtKathmankSpLLDALzWw7CGD2j2MtyveTwboEYokqUCP4a1LxMg",
      "next_protocol": "PtKathmankSpLLDALzWw7CGD2j2MtyveTwboEYokqUCP4a1LxMg",
      "test_chain_status": { "status": "not_running" },
      "max_operations_ttl": 120, "max_operation_data_length": 32768,
      "max_block_header_length": 289,
      "max_operation_list_length":
        [ { "max_size": 4194304, "max_op": 2048 }, { "max_size": 32768 },
          { "max_size": 135168, "max_op": 132 }, { "max_size": 524288 } ],

and
{ "protocol": "PtKathmankSpLLDALzWw7CGD2j2MtyveTwboEYokqUCP4a1LxMg",
  "chain_id": "NetXdQprcVkpaWU",
  "hash": "BLqfmdk3he2DoiaoR8U8CPubefpFq4EkaP9VmhK8P9NjVGKJaQ1",
  "header":
    { "level": 2793472, "proto": 14,
      "predecessor": "BKjV8TaCuygYuh5jiSSG8bpX1nhsNHA1xwhdoMgG9pE6zakgKgc",
      "timestamp": "2022-10-14T00:46:44Z", "validation_pass": 4,
      "operations_hash":
        "LLob82DESKwKeZUgFsAAgmggosSHGhoKXe7iwT6nJGpzgdd6G947r",
      "fitness": [ "02", "002aa000", "", "ffffffff", "00000000" ],
      "context": "CoVKFuKrXvWnp3tPN8H6ouenziAktdWsPc5B4eFiqhUDF6fnRF3G",
      "payload_hash": "vh3LxXXS4F2hkeC5Famuzq8pjSpiR3K4UW8QiLuyErUo8mERoqri",
      "payload_round": 0, "proof_of_work_nonce": "073ae29554340200",
      "seed_nonce_hash":
        "nceVVvpcouW8ZibtayKQkk6wDxZrEmPM1ime3aF1D7ZZ4cXtdRRF8",
      "liquidity_baking_toggle_vote": "off",
      "signature":
        "sigcf21V6pQS4Lc6whsejJ55PB93DsjN42srvY4bVwPayWpzGRF2V7gbc7T7dCmfCr7fYqCzBxfPLQptru2Mj78d2mxWrisz" },
  "metadata":
    { "protocol": "PtKathmankSpLLDALzWw7CGD2j2MtyveTwboEYokqUCP4a1LxMg",
      "next_protocol": "PtKathmankSpLLDALzWw7CGD2j2MtyveTwboEYokqUCP4a1LxMg",
      "test_chain_status": { "status": "not_running" },
      "max_operations_ttl": 120, "max_operation_data_length": 32768,
      "max_block_header_length": 289,
      "max_operation_list_length":
        [ { "max_size": 4194304, "max_op": 2048 }, { "max_size": 32768 },
          { "max_size": 135168, "max_op": 132 }, { "max_size": 524288 } ],

Argh. TzIndex v14 already calls with /chains/main/blocks/2793474?metadata=always, so it looks like the node has corrupt storage. This happened to some of our archive nodes before when they went out of disk space during a database merge (the new Octez versions since v15 or v14 seem to no longer gracefully handle this case).
Your best paths going forward are

reconstruct the node off a tarball from https://xtz-shots.io/ as resync from scratch will take weeks
sync tzindex against https://rpc.tzstats.com then switch to your local rolling node

Please keep in mind TzTindex v14 will stop at the Lima migration as it does not know the new protocol hash. I'll squeeze in some time Monday to make the v15 release ready.

We didn't run ouf of space (few TBs left). Node was started from archive tarball (redownloaded it yesterday once again, 600GB+), started and let it sync, but ended up on the same. tzindex stopped with 2793473, curl to 2793474 is the same about missing metadata.
About v14 it's all clear, will wait to your spare time. But I need to resolve that weird issue - we have three nodes with the same result, all from archive tarball...

The Lima version is available now. Thanks for your patience.

Thanks!


Browser updates

Q
A

Bug fix?
no

New feature?
yes

New sample?
no

Related issues?

What's in this Pull Request?
The following code changes to the sample browser:

Now reads from local samples.json unless host name is pnp.github.io (production)
Now handles multiple query terms (implied "AND"); handles double quotes to allow spaces in a query term
Updated the display of the word "Features" to "Capabilities" per recent doc updates by Teams engineering

@BobGerman that's a great update!!! I already implemented it on the webparts, extensions, and power platform sample repos.


There seems to be a problem with the MobilNetV3 structure

Hello, the network structure of MobileNetV3 seems to be different from that of the original author. The SE module of V3 is not a module that uses SENet. The author changed nn.Line to nn.Conv

Hey @Daming-TF
Thanks for the issue, we are opening a bug and it will be fixed soon.

Hi @Daming-TF , there are some Squeeze & Excite versions which uses Conv op insteaf of Linear.
Conv and Linear are equivalent when applied upon an input tensor with only one neuron per channels, which is the output after the Global average pooling operator. (BxCx1x1 or simply BxC).
In both cases the layers num MAC is represented by Cin x Cout.
There are indeed some hardware accelerators which prefer the Convolution instead of the fully connected one, so in some cases the convolution operation might run faster.

Hello@lkdci oh  that's true😄, thanks I got it


[feature request] Setting Limits on channels also considering their outgoing HTLCs

This tool is awesome to prevent some severe attacks like floot and loot. Therefore I understand why you are only focusing on the incoming HTLCs on channels.
I would also like to have the control of outgoing HTLCs I put onto a channel. So what I mean by that is, that this tool could maybe provide the possibility for users to also rate-limit channels regarding the Offered HTLCs I put onto the Channel. This does not correspond to the floot and loot attack but could be interesting in preventing costly FCs. Current setup would allow an attacker in the worst case scenario when he has 100 Channels with the standard setting to fill up one channel (with the default setting of 5) to 483 HTLCs (100*5).
So I propose introducing separate limits for outgoing HTLCs for channels, which are separate from the incoming limits. I thought of  mimicking some kind of nftables design here.
An HTLC arrives at your node first the Incoming Channel Limits are expected. Further the whole amount of HTLCs (including Incoming and Outgoing HTLCs) are inspected, so we do not fill up the incoming channel when the limit is already reached. Then we could take also the Expiry Time into account which could provide the user with a more fine granular setting when he wants to allow no HTLC at all on this channel in case one of the HTLCs times out in maybe 5 blocks or even less .
After passing the incoming Channel, the Outgoing Channel is evaluated. So first check if the outgoing HTLC limit would be exceeded in case we add this HTLC, and further also check for the whole number of HTLCs (outgoing+incoming) whether they reach our limit. The outgoing HTLC could also take the SENDS into account not only the FORWARDs. One implementation hurdle  is that non-strict-routing means we need to evaluate every channel of the same peer for the specific limits, and if one of them fails the limits the HTLC fails. Moreover because the interceptor can only influence FORWARDS not SENDS, it would mean that rebalance software could potentially always block all Outgoing HTLCs slot on channels preventing routing. But thats exactly the usecase for this feature, preventing the filling-up of HTLCs, without the user knowing or being aware, costing him a lot of sats when he needs to resolve everything on chain.
I would like to work on this, if anybody is interested in this feature?

Very good proposal. Not only controling the incoming but also the outgoing htlcs. Sometimes I had the weird situation of accumulating up to 10 outgoing htlcs for one channel, although circuitbreaker was limited to allow a maximum of 2 incoming htlcs per channel. The accumulation occurs because I got the incoming htlcs on different channels but all with the same target of using one specific outgoing channel. In case of FC it gets quite expensive.
@ziggie1984 Do you think you can implement the modifications also for a non-docker linux environment? The recent new modifications is only suitable for docker environments.

I've considered this when I first started working on CB, but decided to keep it simple initially. Can definitely see the value of an outgoing limit to manage the cost of potential force closes.
Another idea that takes it one step further is to apply pair-wise limits. So specific limits for a combination of in and outgoing peer.

Ok cool, I see your idea definitely something one can think about. I will give the idea with considering the Outgoing HTLCs a shot. Lets see where it brings us. Thanks all for your comments so far :)
@M1ch43lV the problem seems to be locally on your system. The changes are available for all systems. So mine will be too. Just follow jager's advice in just using the build commands from the docker file. For the frontend just cd in the web dir and execute:
yarn install --frozen-lockfile --network-timeout 1000000 && yarn build-export then you should find the build in the webui-build

Interested to see how it goes!

I just had a chat with @ziggie1984 about this, and I find out now this issue basically covers what I was wishing to see implemented in CB.
My scenario:  I'd like to have tops  N outgoing htlcs on a channel, be them forwards or rebalances. My own rebalance logic is already checking if and how many pending htlcs are on a channel, and will tailor its activity based on that. So, the rebalance side is taken care of, and rebalancer would fill the remaining slots of the allowed N. Where CB comes into play, is to allow or reject an incoming htlc depending on the same metric, so if max is 3 in CB, and I have 2 forwards and 1 rebalance pending, CB will not allow any more incoming htlcs.
But I also find very useful the "do not allow any more htlc that will be outgoing to a channel where another htlc is about to expire".
Possibilities are endless, and as far as I understand this shouldn't impact significantly the code complexity.


Keep task name precedence consistent

Looking into the way that Undertaker handles task metadata... I can't help but feel that this is slightly fragmented?
This particular PR fixes what I'm pretty sure is just an honest mistake.
Would it make sense to have a shared util for things like mapping task arguments fn to name and label metadata?

Thanks, this definitely needs to stay consistent across the project.  I would be open to an implementation as a helper function.


Update Python script

Fixing help messages

Message shown by the --help option and message shown while starting run.py w/o (or with wrong) parameters are different, e. g. w/ and w/o "[build_path]" in the end. As "build_path" is required, removing square brackets.

Extending functionality:

Developer may wish to back up some test binaries to compare their behavior with modified version later or just pass current version to QA team.
Expected: can start from backed up sources using run.py script
Actual: run.py looks for an old binaries path from CMakeCache.txt and tests are used from the old location (if exists)
Adding of --move_tests option allows to specify new location, create back up and run tests from it. Command line should look like the following:
>> run.py --move_tests "new location" "current location"
This command copies test binaries and CMakeCache.txt file (that file is required by the script) and updates CMakeCache.txt with a new binaries path value.
After that you may start run.py for the new location with "Expected" result

Also, I'd like to suggest updating of this help page http://code.opencv.org/projects/opencv/wiki/HowToUsePerfTests with the following:
<...>
Creating of usable tests backup with run.py
Script run.py with --move_tests option may be used to create runnable backup of the tests built.
Usage exapmles:
cd opecv/build
run.py --move_tests "new tests location" "current tests binaries location"

This copies tests binaries and CMakeCache.txt (run.py make use of this file) and also updates CMakeCache.txt with the proper binaries path

Hi, could you please to look into the build failure described below?
Received Docs build failure while build portal was unavailable on the web.
Failure step: "Merge opencv with test branch"; Link
Logs: "fatal: unable to access 'https://github.com/MSOpenTech/opencv.git/': SSLRead() return error -9806"; Link
Was it portal or git failure? If so, could you please restart the build?

Updating of the PR triggered rebuild and builds are green now

:+1:

General note:
Did you try to solve problem of creating test package via CMake "install" target? It is a general/natural way to create binary packages (with or without tests) on all platforms.

@alalek In case of using install directory out of OCV build structure (no CMakeCache.txt on the upper levels) run.py cannot start the tests.
Even if we update install target with CMakeCache.txt file copying and path updating, user will need to rerun CMake with the new path, rebuild projects and execute install target to create new version in another location

ABI incompatibility looks the same as we had here

Right, run.py is unable to launch tests from the install binary packages.

Thanks!
:+1:


Tutorial Island Script

Good Afternoon, after multiple requests - I have updated the tutorial island script..
Fixes Survival Guide, Combat Tutor, Quest Guide, Mage Guide, Character Randomization & Name Generation..
I have also made a few adjustments to the Rs2Setting Classes to help work better with this & close Issue #77 as this adds config options to set the in-game settings for 'toggle music', 'toggle roofs', 'toggle disable level-up' & 'toggle shift dropping'.
One other small adjustment, for the proxy message change I have shortened this to only show the IP & Port to avoid showing the password in the titlebar...

I just added a few recommendations from others in the discord..

No more :)

Alright, I have used my last account - I purchased 20 of these to get this far... At this point, I'll see how others do & maybe improve from there...

Thanks for the contribution, this was one of the first scripts, good to see it improved :D


[Bug]Deletion of Tab from entity explorer is not working

Steps:
1.Delete one of the 2 default tabs in the tab widget from entity explorer.
2.Tab deleted message is seen but it's not reflecting in the widget and also in the property pane.

@NandanAnantharamu this seems to be working, can you verify?

@NandanAnantharamu this seems to be working, can you verify?
This issue still exists on release

This issue still exists in the release,
https://user-images.githubusercontent.com/67676905/110006775-0b8b7580-7d40-11eb-81b3-6b867bb0be42.mov

@NandanAnantharamu This as it seems to be working now. Please verify.


Keep legacy version compliance checks in place for non-SemVer2 versions

@scottbommarito @ryuyu any :eyes: to spare on this PR? :)


Update gulp-git version

This makes it possible to build on Node v8 (see stevelacy/gulp-git#164).

Oops. This was taken care of in b2ce73381b4c8ca49cb41a6e6aa0d20f97291c5e, release was published today


Delete ignored key from config.json

Since the exercise implementations are all in the exercises directory
we no longer need to ignore any non-exercise directories in the root
of the track.
See https://github.com/exercism/meta/issues/3 for context.

I've created another PR, #328, which normalizes all of the whitespace in the config.json so
that the change in this PR is minimized and easier to see.
If you merge the other PR first, I'll go ahead and rebase this one onto master.
Sorry about the noise!

Closed by #328.


Added datasource and provider for grafana_dashboard

Hello team,
Here is an proposition for the logzio_dashboard terraform resource. This loads a json dashboard from a local file and applies it on logzio.
For the moment it's still a WIP because :

the non-idempotent field version gets updated after each run and will always differ from the json version field
the json dashboard id field cannot be present (in the file) when "Create" (API call CreateUpdateGrafanaDashboard failed with missing dashboard 300661, data: {"message":"Dashboard not found","status":"not-found"}), but is required in the json file for "Update". That makes for a perpetual change because the json's id field will always differ from the state's id.

Would you have any idea on how to workaround this ?
Note : this works with this code
Thanks,

Hi @etiennejournet thank you for your contribution.
I made a few changes to your code. Now, when applying a plan, the fields id and version are remove from the state. That way there are no diffs.

Hello @mirii1994, thx for your insights and this opportunity to navigate through properly-structured code 👍
Good job with the grafanaDashboardsFieldsToDelete variable !
Regards,


Support customize an uri translator

Is your feature request related to a problem? Please describe.
We can config MASTER_URI_TRANSLATOR_IMPL to a customized implementation which can translate the uri to a alluxio uri. For example:

If we access /alluxio1, we can hash & mode and redirect this to /alluxio1.subdir1 or /alluxio1.subdir2.
If we access /alluxio1, we can redirect this to /alluxio1.subdir1 or /alluxio1.subdir2 which is not busy than the other.
As conclusion, we want to extent to add some customized implementation for uri translator to translate the uri to which we want.

Describe the solution you'd like
Define a UriTranslator#Factory to create a customized uri translator, use the translator to translate the uri to another one by a specific implementation of UriTranslator
Urgency
Normal
Additional context
https://github.com/Alluxio/alluxio/pull/14718

@apc999 @madanadit PTAL this feature request and @maobaolong  has created a PR for it

Hi @maobaolong. Thx for creating the issue and the PR.
I'm unable to follow the description; a few clarifying questions:

is /alluxio1 a path in the Alluxio FS namespace?
what is the goal of the redirection, is it load balancing? i'm not sure what is the resource that is "busy": master or worker or under storage node

Thank you

@madanadit Thanks for your reply.

Yeah, /alluxio1 is a path in alluxio FS namespace
/alluxio1.subdir1 is a mount point which mapping to hdfs ns1, and /alluxio1.subdir2 is another mount point which mapping to hdfs ns2.

@madanadit do you have any comments here?


Pie Menu Inaccessible

Even forcing it manually on the keymap, i can´t use the pie menu.
Shortcut doesn´t work, press the same key as the operator ( hard to find on the documentation ) doesn´t work either
addon version 1.3.3
blender version 3.4 alpha

Hi!
So, you are not supposed to add another keymap, just use the existing one, the one displayed in the addon preferences.
The operator will open the pie menu when the same keymap is pressed. So there is no need to use two different keymaps for the tool.
Anyway... When I try to bind any action to Ctrl+F1 in the keymap preferences, the input just does not work. I think that it is just a combination that you cannot use in Blender. Did you try with another combination of keys?
Here a small video showing that Ctrl+F1 is just not picked by blender (That seem to be the case for any keymap), same for Ctrl+F3, for some reason. But if I try with Shift+F1 for example, blender picks the hotkey properly, and the pie menu works without issue.
https://user-images.githubusercontent.com/35562774/197157227-8786ed34-82f1-44b7-8fd0-394e20541ee6.mp4

press the same key as the operator ( hard to find on the documentation )

Hard to find, really? It is written twice in the readme page, and also clearly listed in the addon preferences.

How else do you think it should be presented?

The same shorcut doesn´t trigger the pie menu, it only trigger the operator for me
this isnt working in 3.4 alpha, i´ve not tried on earlier blender version

Alright, I will give it a try with 3.4a and see if there is an issue there.
What key combination did you use, so I can try with the same?

CTRL + SHIFT + A works triggering the operator

Sometimes i´ve issues with other pie menus, it can be the monitor DPI stuff, can you share your settings for them?
this are mines :

I have the exact same PIE settings as you in Blender. So that should not be the problem.

you´re supposed to do the gesture for the pie menu just after the operator is active right?

Yes, but you don't have to do it straight away, you just have to keep the hotkey pressed, move the mouse cursor where you want and then release the hotkey.
So, I tried with your hotkey (Ctrl+Shift+A), on blender 3.4alpha, and had no issue.
I also tried creating a new keymap like you, calling the wm.call_menu_pie operator with VIEW3D_MT_PIE_quicksnap as the pie name, and the pie menu did show up. So, it looks like it's the pie menu itself the issue and not the key binding.
Just to check, could you download the latest version on github here (Instructions in the readme), and do the following:

Start the tool using your keymap (Have a single box selected)
Press CTRL+SHIFT+TAB once, you should see a notification at the bottom of the window saying that it is changing the debug mode.
Press escape to terminate the tool
Start the tool again, and hit the same keymap again (which normally opens the pie menu)
Then look in the logs (Menu Window - Toggle System Console)

You should see something like this:
[INFO] 2022-10-21 15:34:09,502 Detecting current hotkey
[INFO] 2022-10-21 15:34:09,502 Tool hotkey stored: Ctrl:1 - Shift:1 - Alt:0 - Key:A
[INFO] 2022-10-21 15:34:09,788 Pie menu called.

Tell me if you do, or if you see any error.
If you see Pie menu called, then the issue is indeed with the pie menu itself, and to be honest I do not know what could be the issue, it really is a super basic menu, I am not doing anything unusual in the code there.

Really sorry for the troubleshooting man, i´ve finally found what was causing my issue, it wasn´t the addon itself!
My workspace was configured to filter the addons, and i forgot to activate QuickSnap there... now the pie menu works too!
Thanks for the patience, very good addon indeed ;)

Haha, alright no problem, good to hear that the problem is solved!
Have a nice weekend!
I will set this issue as solved.


Problems with \n or \r

Hi,
I am using this tool for an addon to export the results to excel - when i assign those values in the like thisworksheet.getCell ("C2").value = "My Text with \na line break" on multiple cells i get a strange behaviour. In Chrome this works in some cases (in others not).
In IE this is not working at all.
What is needed to be able to debug it ?
Is there a method to export an worksheet Object in Javascript ?
Thank you for your excellent work !
I am using the latest source (5 days ago ...)
Best regards
Manfred

This is the new endpoint that points directly to npm<EMAIL_ADDRESS>Its automatically updated and works great

i've seen the entry that it should have been fixed - therefore i am wondering what i did wrong !
I used the npm way ?? is there a problem ? i will try the exceljs.min.js link that you've send me

@jimaek I think npmjs is the problem - it sometimes reports different versions for the listings and the actual entries - there's an open issue regarding it that will hopefully get fixed at some point :-)
@Mafi78 Second thing I'd try is adding the normal MS newline stuff, and putting "\r\n" instead (I think that's what I do where I use this) - not sure if it's necessary at all, but worth trying ;-)

@Rycochet any chance you got a link to the mentioned issue?

Hi, i tried it with the new link.
i switched my linebreak now to the suggested " \r\n" and it seems to work now (at least in Firefox). Internet Explorer shows me a linebreak in the console, but when the excel is generated i can see only a space character and no line break ??
I experienced also one non IE javascript line in the exceljs source
line 3351 ->     } else if (reference.startsWith('#')) {
i have to replace it with
} else if (reference.startsWith('#')) {

otherwise my IE will get an exception

@MartinKolarik https://github.com/npm/registry/issues/174
@Mafi78 Which version IE?
Almost seems like this needs to find and replace newlines to \r\n on setting values (so it's correct when saved and when re-reading it stays consistent). An alternative would be transparent set/get so internally it's \r\n but all reading / writing uses plain \n (I always have to check the correct order because I don't do it often - and I can't be the only one).

@Rycochet: IT is IE 11.0.9600 (on Windows 7) it is the actual version available (at least when you trust Windows Update)
I don't get your last comment ? should i update my string with \n\r instead of \r\n ?? I am sorry :)
I've also read that a special setting (i think it was a style of the worksheet itself) was necessary - should i try that out ?

@Rycochet: as in issue 296 described (https://github.com/guyonroche/exceljs/issues/296) i tried to set the style of the workbook.
But i am not using a WorkbookWriter ?
I instantiate a new Workbook Object and don'T know how to set the correct attribute
that.workbook = new Excel.Workbook();

Putting \r\n in is correct - I'm just wondering if ExcelJS should automatically handle it so it's not needed (MS does seem to love \r\n even if nobody else does :-P )
I did read elsewhere that there is a flag related to multi-line, but I honestly can't remember what it is (check the other issues maybe?), or what it does.
Hopefully someone gets the time to look at that specific error on IE - though it's most likely the use of string.startsWith() which isn't supported on IE at all, and needs either polyfill or a simple workaround -
function startsWith(str, prefix, position) {
   if (str.startsWith) {
      return str.startsWith(prefix, position);
   }
   return str.substr(position || 0, prefix.length) === prefix;
}

Another thing that IE does not love is the asignment of objects wirh
This
/var worksheetOptions = Object.assign({}, options, {
id: id,
name: name,
workbook: this
});/
gave me also an error ... after changing it to this
var worksheetOptions = {
id: id,
name: name,
workbook: this
};
it worked :) IE javascript behaviour and the rest of the world is really nasty - so much work to do twice. Not good.
I made some more tests ... and luckily found my solution. If i replace my  in html with " \n" also IE is able to understand it !! I have no clue why ? There should be no difference between "\n" and the same with one space more " \n" ??

the flag for the multiline is this setting:
worksheet.getCell("A1").alignment = { wrapText: true };
then the content is also shown on multiple lines. If this is not set the cell has the height of 1 line and you can see the second (or third) line when you manually click in the cell and hit enter
But this does not help in my IE problem :(
Do you have another idea ?

i tested it with firefox - and there are also problems with assigning the \n character ??

Not sure about Firefox, but you could add ES6 shims for IE - https://github.com/paulmillr/es6-shim - Object.assign also copies over (like jQuery.extend()), and it also needs some string ones. That repo has standalone ones too if you want to look at them instead of a bigger (but easier) "everything" fix for IE.

ES6-Shim was a very good tip - now i can use exceljs.js without modifications !
I found an example and will try to upload it (webcontent.zip)
It includes a requirejs base with an error1.html that behaves different on chrome and IE and Firefox.
With chrome i can see always newlines and in IE and firefox for the cells C1 to H1 there is no newline ?!
I used the following value for this 'My text with two \n\n newlines' if i change it to 'My text with two \n \n newlines' it works - also in IE.
Due to the fact that my application is embedded in an application it is hard for me to reproduce the error. Is it possible to save the workbook object with javascript (stringify it JSON.stringify) and read this text on my other application with JSON.Parse ?
Then i would make sure it has something todo with the other application !
Thanks

WebContent.zip

A general search shows a lot of people complaining about inconsistent newlines, but nothing definitive on what any actual problem is - hopefully someone else has more time to look into it :-/

I would love an option to use windows carriage returns instead of the standard \n. The app I wrote to transform data and output to CSV generates the files with \n newlines and I have to open in excel and save to get windows newlines because the ingestor that reads the files just has to have windows newlines, apparently. So it's not a huge deal - exceljs already did 99% of the work :) - but it would be nice to have it as an option in CsvWriteOptions.

For some reason I still have this issue with 4.1.1 (unless I'm just doing something else wrong):
None of the fixes here or in #296  worked for me. What finally worked was to create a string with backticks and then hit the enter key between them, store as a const, and then add to whatever string where I needed a break.
const lineBreak = `
`;

const myText = `This is my text.${lineBreak}`;

I don't know enough to know if there's a better way, but it worked.


fix: add a retry to pushing the git source

in case the git provider is not yet ready to take a git push yet
we've seen failures in our BDD tests when sometimes despite the git
repository being created we need to wait a little before we can push

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan 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

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

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


Pool statistics graph shows two sets of data when switching tabs

Fixes #691.
Changes proposed in this PR:

Fix pool statistics show the same statistics graphic twice when switching tabs

Tested it with and without a wallet connected and the statistics graphic is displayed correctly in both cases. Looks good to me!

Just comparing graphs between live and preview and while PR fixes the original issue I find some graphs to be completely different with this preview, while some like DataUnion are the same.
Some differences, do we know why this happens and if the new graphs are the correct ones then?

https://market.oceanprotocol.com/asset/did:op:b07a8bb80242752ce164560ABCb6517DA90a4F65

https://market-git-feature-issue691-pool-statistics-graph-oceanprotocol.vercel.app/asset/did:op:b07a8bb80242752ce164560ABCb6517DA90a4F65

https://market.oceanprotocol.com/asset/did:op:a2B8b3aC4207CFCCbDe4Ac7fa40214fd00A2BA71

https://market-git-feature-issue691-pool-statistics-graph-oceanprotocol.vercel.app/asset/did:op:a2B8b3aC4207CFCCbDe4Ac7fa40214fd00A2BA71

I think in the preview all the data points all stop at Nov. 2020 although there're many more data points in reality

Good point, I tested some assets and looked fine, should have tested more

It should be fine now

awesome, thanks, indeed all good now. And it felt so nice seeing all this state handling removed initially but I guess now we know why this is all there


New Video Player block for Adobe x Meta

Feat: MWPW-112014
Test URLs:

Before: https://main--express-website--adobe.hlx.page/drafts/qiyundai/edu-video-block?lighthouse=on
After: https://mwpw-112014--express-website--webistry-development.hlx3.page/drafts/qiyundai/edu-video-block?lighthouse=on

On Slow 3G network throttling, there are some CLS issues here:

We should try to find a way to hide the block until the carousel is finished loading.
After looking into it a little bit, I realize it's a problem with the buildCarousel(); function not being a Promise, this issue is there for other blocks that also use buildCarousel();. So this should probably be fixed in a separate pull request in order to test the other pages as well and QA to make sure it doesn't break anything.


Please update the Visual Studio extension

It would be great to add the photino Blazor template to Visual Studio

We'll try to add it on the next update to the templates.


Index sources generated by source generators

Need to tell the workspace to write generated source to disk and index that source?

This is where the Roslyn workspace is created:
https://github.com/KirillOsenkov/SourceBrowser/blob/e517b8023bc124839622543903297075a4872a54/src/HtmlGenerator/Pass1-Generation/SolutionGenerator.cs#L132

prob just needs to set the property EmitCompilerGeneratedFiles to true.

This is how you control emit location:
https://github.com/dotnet/roslyn/blob/86ff365d5d28fddd4a4738cf1d9d101522dffd50/src/Compilers/Core/MSBuildTask/Microsoft.Managed.Core.targets#L312


error message suggests using conditions before the user learned it.

When you try to attack "null" reference the error says to try to use "if" statements' even though the user didn't learn conditions in the early stages.
Maybe it would be better to change the error message :)
@hibukki

In which levels does this happen? Some context would be nice to determine whether this is a common occurrence.
In the other hand, error messages which make no sense to reader at first glance are part of a coder's daily life. :smile:

@Zerrien fixed this, right?


Territory Battle configurations use an outdated format for the player blocks field

As of NucleoidMC/Territory-Battle@6f99d9f9217e8941011ef2d27a071be7d68a97a0, the player blocks field format has changed to accept a registry entry list and use snake case:
  {
    "type": "territorybattle:territory_battle",
    "map": {
      "x": 36,
      "z": 36
    },
    "players": {
      "min": 1,
      "max": 32,
      "threshold": 2
    },
-   "playerBlocks": "minecraft:coral_blocks",
+   "player_blocks": "#minecraft:coral_blocks",
    "icon": "brain_coral_block"
  }

This is no longer an issue as the game configuration is now in the minigame's repository


java

In the main method ask the user to input the size of an array then create and fill the array with random integer numbers each of which is in the range of [32 - 126].

In the main method ask the user to input the size of an array then create and fill the array with random integer numbers each of which is in the range of [32 - 126].


docs: update README.md

Signed-off-by: Siggi Skulason<EMAIL_ADDRESS>

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-cli/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)  N/A
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?) N/A
[ ] I have opened a PR for the related docs change (if not, why?) N/A

Testing Instructions

N/A
New Dependency Instructions (If applicable)

It is useful for the developers to know what are the functional CLI limitations, i.e. for what actions they still need to rely on the networking APIs. I suggest adding a section to list the limitations and link to appropriate issues. If the list is long, it could instead be a link to enhancement issues for the sake of maintainability.

@farshidtz / @MonicaisHer I added a 2nd commit with a couple of changes as per the comments. Please re-review, thanks!

command-line should have a hyphen (	https://en.wikipedia.org/wiki/Command-line_interface ), whereas "EdgeX CLI" doesn't and edgex-cli does (being the actual command name)