[Feature] Maven Central Publishing

Description
This introduces publishing via maven central.
Review checklist

[x] PR is split into meaningful commits for the ease of reviewing
[x] Description contains clear instructions on how to test the feature (where applicable)
[x] Tests have been written
[x] Appropriate labels have been applied

Codecov Report

Merging #35 (6636c0c) into main (e725d3a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6636c0c differs from pull request most recent head c22fa57. Consider uploading reports for the commit c22fa57 to get more accurate results

@@            Coverage Diff            @@
##               main      #35   +/-   ##
=========================================
  Coverage     100.0%   100.0%
  Complexity       39       39
=========================================
  Files             9        9
  Lines            61       61
  Branches          9        9
=========================================
  Hits             61       61


python311Packages.flask-restx: fix build on Darwin

Description of changes
https://hydra.nixos.org/build/253994454

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 299630 run on x86_64-linux 1

2 packages failed to build:

flexget
flexget.dist

6 packages built:

lacus
lacus.dist
python311Packages.flask-restx
python311Packages.flask-restx.dist
python312Packages.flask-restx
python312Packages.flask-restx.dist

flexget failure will be addressed with #299691.


New version: Microsoft.VCRedist.2015+.arm64 version 14.42.34433.0 (14.42.34433)

Created by 🥟 Dumplings in workflow run #9500.

Log
Updated: 14.40.33816 → 14.42.34433
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

We can only provide pipelines from the images that DaaS provides to us.

@wingetbot run

[Policy] Blocking-Issue

We can only provide pipelines from the images that DaaS provides to us.

Then could you manually validate and merge this PR?

Manually verified.


error occurring while running my motion detectioncode on jupyter notebook

usage: ipykernel_launcher.py [-h] [-v VIDEO] [-a MIN_AREA]
ipykernel_launcher.py: error: unrecognized arguments: -f C:\Users\HP\AppData\Roaming\jupyter\runtime\kernel-fb666fe6-3260-4858-b7c8-b37fb9759c42.json
An exception has occurred, use %tb to see the full traceback.
SystemExit: 2

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


Alternate relation adapter testcase

Hanami::DB::Relation will retain the ROM behavior of selecting an
alternate adapter with Relation[adapter_name] syntax, so this needs to
have test coverage.
Closes #3

@timriley Okay, the alias has been removed and I've added test coverage around selecting an alternate adapter.


Add failing test fixture for StaticDataProviderClassMethodRector with ignored abstract parent test case

Failing Test for StaticDataProviderClassMethodRector
Based on https://getrector.com/demo/9372e294-4277-4bb9-abeb-34764c0b053c
Explanation
Because the parent abstract class is skipped in rector config, their child classes should be ignored for this rector as well. Check the demo link please, thanks.
This test should be failing ❗
Spotted in

https://github.com/symfony/symfony/pull/48668

This is identical to already fixed https://github.com/rectorphp/rector-phpunit/pull/156
How is it different?

I told rector to skip the abstract class, which cannot be reflected in the failing test case

I see. It only works for explicit paths, no magic :)
Also, the __DIR__ . 'String might result into SomePathString

Btw, what is reason to ignore any files here? The upgrade must handle all files.

In Symfony all abstract cases in /Test/ namespace are under BC promise and can be used in username. All abstract testcases in /Tests/ namespace are considered internal and are only used for our codebase, which we can change but the ones in /Test/ need to have an upgrade path including deprecations we need to find manually.
But ofc our own tests in /Test/ are using the abstract testcases from /Test/
I hope I make it clear 😃 thanks for your time

I see :)  That's super specific use case that would be only useful for Symfony core project.
I think for that would be best just to fork Rector rule to custom one and apply this logic there.


Dosers

Hi there @tdragon Hope all is well with you :)
Integration has been working great! Just wondering if it is humanly possible to integrate the full or close to the full dosing api into Home Assistant? As i (in a nutshell) would love to be able to fully control and automate components by combination of either reef-pi and home assistant for controlling, scheduling, dosing etc and then use a combination macros in reef-pi and automations in Home Assistant that if x doser runs longer than x then to initiate a shutdown and notify message/sound etc etc.
Hope that makes sense :)
I am more than happy to donate to your beer or coffee fund :)

Hi!
Thank you for the idea, but currently I don't have any capacity to work on this project. I'll keep this ticket open, but cannot give any estimate when I can work on it.

That would be awesome thanks, totally understand :)
Sent from my iPhone
On 7 May 2023, at 4:47 am, Dmitrii @.***> wrote:

Hi!
Thank you for the idea, but currently I don't have any capacity to work on this project. I'll keep this ticket open, but cannot give any estimate when I can work on it.
—
Reply to this email directly, view it on GitHubhttps://github.com/tdragon/reef-pi-hass-custom/issues/21#issuecomment-1537220551, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMCDRZP2EWCNURLTCLPEYV3XE22EVANCNFSM6AAAAAAXYDE2EA.
You are receiving this because you authored the thread.Message ID: @.***>

Hey @tdragon just thought I’d touch base and hope you are doing well, just asking if you have had any chance to look at integrating the dosing component?

Hi @tdragon just seeing if you have had any time to have a look at this


Feat: for i18n document did translation into chinese language

Added all the doc folders files into docs/locale/zh_CN folder in Chinese translation
Related issue: https://github.com/hyperledger-labs/PerformanceSandBox/issues/16
Signed-off-by: sheetalj2205<EMAIL_ADDRESS>

@SamYuan1990 Please check this PR and suggest any changes if required.

@SamYuan1990 Please check now, I did all the suggested changes.

@sheetalj2205 , I just added a feel comments there, once those fixed, we can merge this pr.

@sheetalj2205 , I just added a feel comments there, once those fixed, we can merge this pr.

@SamYuan1990 I did all the changes, please check now


WIP: djql queries

Summary
Revisits https://github.com/DataJunction/dj/pull/336
Examples:
SELECT
  Sum(avg_repair_price),
  city
FROM
  (
    SELECT
      default.avg_repair_price avg_repair_price,
      default.hard_hat.country,
      default.hard_hat.city
    FROM
      metrics
    GROUP BY
      default.hard_hat.country,
      default.hard_hat.city
    LIMIT
      5
  )
GROUP BY city

SELECT default.hard_hat.country, default.hard_hat.city

SELECT
  default.avg_repair_price avg_repair_price,
  default.hard_hat.country,
  default.hard_hat.city
FROM
  metrics
GROUP BY
  default.hard_hat.country,
  default.hard_hat.city
ORDER BY
  default.hard_hat.country,
  default.hard_hat.city

Test Plan
So far, built and run queries manually. Tests wip

[ ] PR has an associated issue: #
[ ] make check passes
[ ] make test shows 100% unit test coverage

So much potential with this feature, both to provide an exploratory SQL interface directly to the server but also to build SQL connectors using other protocols/SDKs out there. I know this is a WIP but I have a question about this example:
SELECT
  default.avg_repair_price avg_repair_price,
  default.hard_hat.country,
  default.hard_hat.city
FROM
  metrics
GROUP BY
  default.hard_hat.country,
  default.hard_hat.city
ORDER BY
  default.hard_hat.country,
  default.hard_hat.city

Why would the GROUP BY need to be provided here? Shouldn't we be able to detect which items in the projection are metric nodes and which are dimension nodes? Then we just check if they're compatible and the existing server side logic will group appropriately, right?

@samredai the idea was to mimic the api and I figured it is intuitive to provide the group by for the dimensions, so dimensions are discovered by their presence in the group by and are actually optional in the projection. In that particular example I include them in the projection but if I hadn't they wouldn't appear in the final data.

@CircArgs this is real cool feature. I am still unsure where it can lead, but I do agree that a way to explore the DJ dag and query its data through a single DJQL prompt would be Amazing for SQL savvy users! Just not sure how many business users would actually ever see this feature. But scratching your own each is the best way to build good stuff!
@samredai I think this GROUP BY is useful because it is an indication of the intent. Of course DJ could figure out which are dimensions and which are metrics, but if you don't make this "SQL" similar to the other "SQLs" then it will be harder to use. I feel like we should require it to be even more proper SQL so people know better what to expect from it. Example:
SELECT
  AGG(default.avg_repair_price) avg_repair_price,
  default.hard_hat.country,
  default.hard_hat.city
FROM
  metrics
GROUP BY
  default.hard_hat.country,
  default.hard_hat.city
ORDER BY
  default.hard_hat.country,
  default.hard_hat.city

Side comment: why does Github not allow comments on other people comments. This copying down the whole reference is insane... :(

@CircArgs @agorajek makes sense! I agree it's a good idea to think about how we can make sure that some valid SQL syntax exists for each functionality since some connector SDKs do client side validation and will fail the query before it even gets to the DJ server. That being said it feels right to keep it very permissive (for now) the way it is in this PR and we can incrementally move towards a single optimal syntax.


Investigate nalgebra as replacement for collision and cgmath.

Cgmaths future remains uncertain and there is push towards nalgebra in the community. I do not feel any urgency,but it might make sense to investigate nalgebra.

Done in #415


[Bug]: Coverage calculation is off when a React.lazy line spans multiple lines

Version
27.4.3
Steps to reproduce
I have an SPA written in React v17.2.
Formatting of code in this codebase is done by Prettier v3.
Bundling of the app is done by Create-React-App v5
Throughout the app, there are various instances of lazy import:
const PageA = React.lazy(() => import('./PATH_TO_FOLDER/PageA'))
const ComponentB = React.lazy(() => import('./PATH_TO_FOLDER/ComponentB'))

Most of these lazy importing lines get ignored by Jest in the coverage report.
However, Jest will mark a line as "uncovered" in the Jest coverage report if that line is formatted to be multiple lines by Prettier:
// Shows up as uncoverage in Jest coverage report !!!
const ComponentWithLongNameOrPath = React.lazy(() =>
  import('./PATH_TO_FOLDER/ComponentWithLongNameOrPath')
)

Expected behavior
Multi-line lazy import should be ignored in the same way single-line lazy import is.
Actual behavior
Multi-line lazy import get marked as "uncovered"
Additional context
No response
Environment
System:
    OS: macOS 13.5
    CPU: (12) x64 Apple M2 Pro
  Binaries:
    Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.17.1/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.17.1/bin/npm

Does this happen with the latest version of Jest?

@SimenB I am not able to quickly update my codebase to Jest v29 (since Create-React-App is not longer maintained)
My understanding is that coverage information actually come from packages outside of Jest.
Therefore, I would guess this issue is still present in Jest v29, since the relevant packages have not changed that much
jest-reporters v29.7

collect-v8-coverage: "^1.0.0"
istanbul-lib-coverage: "^3.0.0"
istanbul-lib-instrument: "^6.0.0"
istanbul-lib-report: "^3.0.0"
istanbul-lib-source-maps: "^4.0.0"
istanbul-reports: "^3.1.3"

jest-reporters v27.5 has the same packages except for istanbul-lib-instrument, which was at v5.1.  I tried to update just istanbul-lib-instrument to v6, but the coverage report still has the same bug


must be a relative utf-8 path

hi,
I'm trying arx and get an error when I pass the input as an absolute path :
$ cd /tmp/
$ mkdir test.arx.d/
$ cp ./arx test.arx.d/

$ # OK
$ ./arx -vvv create --outfile ./test.arx ./test.arx.d/
[INFO  arx::create] Creating archive Some("./test.arx")
[INFO  arx::create] With files ["./test.arx.d/"]
[DEBUG arx::create] Saved place is 0
$ rm -f test.arx

$ # KO
$ ./arx -vvv create --outfile ./test.arx /tmp/test.arx.d/
[INFO  arx::create] Creating archive Some("./test.arx")
[INFO  arx::create] With files ["/tmp/test.arx.d/"]
Well, this is embarrassing.
arx had a problem and crashed. To help us diagnose the problem you can send us a crash report.
We have generated a report file at "/tmp/report-a142a59f-fe43-41af-ad9e-c5fc2f1541c6.toml". Submit an issue or email with the subject of "arx Crash Report" and include the report as an attachment.
- Homepage: https://github.com/jubako/arx
- Authors: Matthieu Gautier<EMAIL_ADDRESS>We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.
Thank you kindly!
$ cat /tmp/report-a142a59f-fe43-41af-ad9e-c5fc2f1541c6.toml
"name" = "arx"
"crate_version" = "0.2.1"
"explanation" = """
Panic occurred in file '/home/runner/work/arx/arx/libarx/src/create/fs_adder.rs' at line 146
"""
"cause" = "\"/tmp/test.arx.d/\" must be a relative utf-8 path."
"method" = "Panic"
"backtrace" = """
   0: 0x642f3c0fa4c5 - arx::create::create::h0d31a0a1c81133f8
   1: 0x642f3c09e6c0 - arx::main::h8e785563c91bb87e
   2: 0x642f3c10fd63 - std::sys_common::backtrace::__rust_begin_short_backtrace::h512139b71798be16
   3: 0x642f3c0a99d2 - main
   4: 0x75fe15335c88 - <unresolved>
   5: 0x75fe15335d4c - __libc_start_main
   6: 0x642f3c092255 - _start
   7:        0x0 - <unresolved>"""

the problem remains if I install arx with cargo.
regards, lacsaP.

Same issue:
`arx create -o irstea_documents.arx -r Documents
Compressed Cluster   : ############################################+ 515  / 516
Uncompressed Cluster : --------------------------------------------- 0    / 1   Well, this is embarrassing.
arx had a problem and crashed. To help us diagnose the problem you can send us a crash report.
We have generated a report file at "/tmp/report-ddf531c4-69ad-476d-9f5b-c602edea3b20.toml". Submit an issue or email with the subject of "arx Crash Report" and include the report as an attachment.

Homepage: https://github.com/jubako/arx
Authors: Matthieu Gautier<EMAIL_ADDRESS>
We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.
Thank you kindly!
then:
christo:~$ cat /tmp/report-ddf531c4-69ad-476d-9f5b-c602edea3b20.toml
"name" = "arx"
"operating_system" = "Ubuntu 22.04 (jammy) [64-bit]"
"crate_version" = "0.2.1"
"explanation" = """
Panic occurred in file 'libarx/src/create/fs_adder.rs' at line 88
"""
"cause" = ""/home/christo/Documents/PôleGD" must be a relative utf-8 path"
"method" = "Panic"
"backtrace" = """
0: 0x651652a4739c - libarx::create::entry_store_creator::DirEntry::add_entry::hfac430b68bc9369a
1: 0x651652a479d8 - libarx::create::entry_store_creator::DirEntry::add::h6a26588866a85f93
2: 0x651652a47c2d - libarx::create::entry_store_creator::DirEntry::add::h6a26588866a85f93
3: 0x651652a5eee1 - arx::create::create::h0d31a0a1c81133f8
4: 0x651652a036c0 - arx::main::h8e785563c91bb87e
5: 0x651652a74d63 - std::sys_common::backtrace::__rust_begin_short_backtrace::h512139b71798be16
6: 0x651652a0e9d2 - main
7: 0x7345bdc29d90 - __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58
8: 0x7345bdc29e40 - __libc_start_main_impl
at ./csu/../csu/libc-start.c:392
9: 0x6516529f7255 - _start
10:        0x0 - """
christo:~$
`

Thanks both of you for testing arx. I'm glade to see this project gain some attraction :)
I think this is two different issues. So @cchristofr I will move you comment in a new issue.

@patatetom I will fix the issue by better checking the input and print a better error message instead of crashing. Arx can only save relative path. We may infer a relative path from absolute but I think this is more tricky that we may think first.


PR 13757 follow-up: add missing with-discountOverlaps Similarity constructor variants, CHANGES.txt entries (#13845)

(cherry picked from commit dab731175c86cc25741f37845136d38a69a9d165)
(cherry picked from commit cbd8b5218addb7712452893cdfe2a3795dc9e05a)
Resolved Conflicts:
lucene/CHANGES.txt

Tentatively tagging to 10.0.0 milestone based on https://lists.apache.org/thread/sd0n1kmcz66bt8nspvflh6fbwpb527lq and https://lists.apache.org/thread/pfllhdhdphvgkv1gpngp1r56ydpbt7ov info.

I merged this to branch_10_0. Does this also need to backported to 9_12 for the next 9.12.1 patch release?

Heads up: I moved the CHANGES entry in main and branch_10x to the 10.0.0 section. See https://github.com/apache/lucene/commit/111fc6f07857f909ad2a253cdcd6e948222ecf63 .

Heads up: I moved the CHANGES entry in main and branch_10x to the 10.0.0 section. ...

Thanks!

... Does this also need to backported to 9_12 for the next 9.12.1 patch release?

That would be good, yes, #13891 opened for it.


User didn't understand why Verify was needed, would have preferred to phone the council

'Are they doing this so less people apply and it is cheaper for the Council?'

User stated that she did not expect all of this effort to apply for a bus pass

Aldo linked to #413


use bitset in bit_span::operator*

Change-Id: I34772c33111e073f58d75c7949bea68dc232353a

Codecov Report

Merging #84 (1ebc412) into master (62b38e9) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   99.57%   99.57%   -0.01%
==========================================
  Files          11       11
  Lines         238      237       -1
==========================================
- Hits          237      236       -1
  Misses          1        1

Files Changed
Coverage Δ

huffman/src/bit_span.hpp
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Sierra: Fresh Install - Issue with bundler not finding gems

OS: macOS Sierra
Fresh Install
Xcode Command line Tools (not full install)
Was simply following the bootstrapping section on the README, https://github.com/boxen/our-boxen/blob/master/README.md#L54 but when running boxen it'd error:
Jareds-MacBook-Pro:repo jared$ ./script/boxen
--> Preparing to auto-update...
--> Complete! Nothing new from upstream.
Could not find faraday-0.9.2 in any of the sources
find: bin: No such file or directory
Could not find rake-10.3.2 in any of the sources
Run `bundle install` to install missing gems.

Jareds-MacBook-Pro:repo jared$ bundle install
Fetching gem metadata from https://rubygems.org/........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Installing rake 10.3.2
Installing CFPropertyList 2.2.8
Installing addressable 2.3.8
Installing ansi 1.5.0
Installing json_pure 1.8.2
Installing hiera 1.3.4
Installing highline 1.6.21
Installing json 1.8.3 with native extensions
Installing thor 0.19.1
Installing librarian 0.1.2
Installing librarian-puppet 1.0.9
Installing multipart-post 2.0.0
Installing faraday 0.9.2
Installing sawyer 0.5.5
Installing octokit 2.7.2
Installing facter 2.4.4
Installing puppet 3.7.1
Installing boxen 2.9.0
Installing deep_merge 1.0.1
Installing diff-lcs 1.2.5
Installing metaclass 0.0.4
Installing mocha 1.1.0
Installing open4 1.3.4
Installing puppet-lint 0.3.2
Installing rspec-support 3.2.2
Installing rspec-core 3.2.3
Installing rspec-expectations 3.2.1
Installing rspec-mocks 3.2.1
Installing rspec 3.2.0
Installing rspec-puppet 1.0.1
Installing puppetlabs_spec_helper 0.4.1
Using bundler 1.10.6
Bundle complete! 12 Gemfile dependencies, 32 gems now installed.
Gems in the groups development and test were not installed.
Bundled gems are installed into ./.bundle.

Jareds-MacBook-Pro:repo jared$ ./script/boxen
--> Preparing to auto-update...
--> Complete! Nothing new from upstream.
...

From there everything worked without an issue.

Thanks for the report! :star:
I've seen this happen prior to the release of mac OS sierra so I don't think this is anything new however I still don't know exactly why it happens though.

Yup - also getting this since updating to boxen 2.9.0 (el capitan pre-sierra)

I couldn't work it out, but my state was stuffed in someway, so a full boxen nuke then rebuild on 2.8, then update to 2.9 worked flawlessly.

Went from El Capitan (with boxen) to Sierra and tried the latest boxen again, works fine, but when I tried a fresh install of macOS Sierra and run script/boxen it produces error something like json 1.8.3 missing. Still trying some ways on how to resolve this missing gem.

Hey there, so from what I understand Boxen caches all of the gems in the repo in order to make the initial bootstrap process as quick as possible. When the boxen gem was updated to 2.9.0 in #826, the Gemfile and lockfile were updated, and the older versions of boxen and faraday were removed from the cache, but the new versions weren't included.
#828 fixes this. :shipit:

@spacepants while the gems were missed, this is a longer standing issue and as I mentioned, has been present for a while prior to these updates.
I've merged the change to get the gems re-added however I'll need to find some time to investigate why this randomly happens with installations.


Use value-based "object" instead of "ref object" by default

Right now binarylang generates a ref type for the parser to store data in. I think that ref types are not needed in most of cases as they're allocated on the heap and are also ref-counted.
So I propose to make types "object" by default, with an option like isRef  for the parser so that then the type becomes ref object. I don't know what stability guarantees does binarylang have, and if it's undesirable to break existing code (that does echo data.toType()[] for example, isObj can be added instead.

I've been dealing with same problem here https://github.com/sealmove/binarylang/issues/12, where I've been using custom == equality operator to restore old tuple-based return types.
I'm not sure if objects are better than ref objects in this context as I'm quite happy with the current solution, but I think that docoded objects from same stream should be considered equal.

Thanks again for the suggestion. Default is now non-ref. I added the parser option reference which accepts the values y and n.


bug: Edititing posts doesn't work

Whenever I try to edit a post within the first 2 hours of posting it, I get a box that says "You are not allowed to do this"

I keep having to delete posts and resend myself things if I want to edit something such as a typo or incorrect markdown

Fixed, thank you!


:seedling: Rewrite fetch_target_logs.sh in Golang

What this PR does / why we need it: Running an sh file from go file will gives warning: G204: Audit use of command execution. In this PR I've rewritten the fetch_target_logs.sh in Go to avoid getting this warning.
Compared to the original: I've added kubect get pods -A
and removed the split between stdout and stderr in the logs. Some of the logs had warning
W0613 11:04:05.645729       1 options.go:215]
==== Removed Flag Warning ======================

logtostderr is removed in the k8s upstream and has no effect any more.

and based on further investigation it seems Kubernetes only has one API endpoint for logs and everything is logged into stdout.

/test ?

Let's also implement CAPI CollectInfrastructureLogs on our side in this PR.

/test ?

/test metal3-ubuntu-e2e-feature-test-main-features

/test metal3-ubuntu-e2e-feature-test-main-pivoting
After running this test there should be a k8_target_cluster directory in the logs. If it looks as it should (same as before except for a few minor changes) this PR's code is working correctly.

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-centos-e2e-integration-test-main
/test metal3-ubuntu-e2e-integration-test-main

metal3-ubuntu-e2e-feature-test-main-pivoting test is failing but it doesn't seem to me that it is related to the changes in this PR. Correct me if I'm wrong.
In the logs-jenkins-metal3-ubuntu-e2e-feature-test-main-pivoting-4-pivoting-based.tgz the logs in directory k8s_target_cluster are looking as they should. So to me it seems everything is working as it should.
Please take a look @adilGhaffarDev @mboukhalfa @Sunnatillo. This needs a lgtm and approve. Thank you!

/test metal3-e2e-clusterctl-upgrade-test-main

In the logs-jenkins-metal3-ubuntu-e2e-feature-test-main-pivoting-4-pivoting-based.tgz the logs in directory k8s_target_cluster are looking as they should. So to me it seems everything is working as it should.

It looks good. I want to see how this will work when we have multiple management clusters, like how we have in clusterctl tests.
Also if possible let's try to reuse CAPI's implementation of same functionality: https://github.com/kubernetes-sigs/cluster-api/blob/8f31a865b6cf562f8fe831ae603b6e27752d8525/test/framework/deployment_helpers.go#L152 , if its too much work lets merge this PR and do it in another PR.

Seems need to resolve some conflict I will take a look

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-pivoting

Periodic pivoting test has not passed in 27 days, not sure if its worth running unless it is specifically triggering and failing to somehting you created in this PR.

/test  metal3-ubuntu-e2e-integration-test-main

It's looking good. A few improvements that we made in the log collection:

Name folders according to the actual name of the cluster, preferably also the name of the test as the folder name. Like this:

Logs

k8s-target-cluster

cluster-name

machine-name

pod-name

pod-name.log

k8s-management-cluster

cluster-name

machine-name

pod-name

pod-name.log

Why is this needed, we have multiple target clusters in clusterctl tests, in future we might add tests where we have multiple clusters.

In logs describe yamls that are missing lets bring them back. If it's difficult to put the yamls in the same folder as logs(because we use capi code to collect logs) put them in a separate folder, you can add the same code as before to collect yamls. Let's keep the same structure as above:

pod-yamls

k8s-target-cluster

cluster-name

machine-name

pod-name

pod-name.yaml

k8s-management-cluster

cluster-name

machine-name

pod-name

pod-name.yaml

let's skip infrastructure logs for now.

/test metal3-ubuntu-e2e-integration-test-main

/test metal3-ubuntu-e2e-integration-test-main

/test ?

/test metal3-e2e-clusterctl-upgrade-test-main

/test metal3-e2e-clusterctl-upgrade-test-main

/test metal3-ubuntu-e2e-integration-test-main

/test metal3-ubuntu-e2e-integration-test-main

/lgtm
from my side

/test metal3-centos-e2e-integration-test-main

/test metal3-centos-e2e-integration-test-main

@mboukhalfa @mquhuy please take a look let's merge this one

I have checked the logs collected in this test: https://jenkins.nordix.org/view/Metal3/job/metal3-centos-e2e-integration-test-main/559/. It basically looks ok, but there are a few minor details I think we should fix:

CAPI config is empty
A lot of log files (mostly stderr) are empty. IMO it's worth to check if the content is empty, before creating the file.

Some other items, which would be nice (and hopefully not too troublesome) to fix:

Inside podman, there's only 1 directory called final_logs, in which there are logs of all containers. Do we expect to have initial_logs or something else? Otherwise, it's enough to put all container directories directly under "podman".
Same with "k8s_target_cluster", under which there is 1 directory "clusters", we should put all target clusters under the "k8s_target_clusters" and remove the intermediary.

Otherwise, LGTM. Good job, @peppi-lotta !

I have checked the logs collected in this test: https://jenkins.nordix.org/view/Metal3/job/metal3-centos-e2e-integration-test-main/559/. It basically looks ok, but there are a few minor details I think we should fix:
* CAPI config is empty

* A lot of log files (mostly `stderr`) are empty. IMO it's worth to check if the content is empty, before creating the file.

Some other items, which would be nice (and hopefully not too troublesome) to fix:
* Inside `podman`, there's only 1 directory called `final_logs`, in which there are logs of all containers. Do we expect to have `initial_logs` or something else? Otherwise, it's enough to put all container directories directly under "podman".

* Same with "k8s_target_cluster", under which there is 1 directory "clusters", we should put all target clusters under the "k8s_target_clusters" and remove the intermediary.

Otherwise, LGTM. Good job, @peppi-lotta !

@mquhuy I agree with you on these points but I think these should be done in a separate PR. The changes in this PR only relate to the k8s_target_cluster folder. Also the folder refined based on this suggestion https://github.com/metal3-io/cluster-api-provider-metal3/pull/1763#discussion_r1790648339.

@mquhuy I agree with you on these points but I think these should be done in a separate PR. The changes in this PR only relate to the k8s_target_cluster folder. Also the folder refined based on this suggestion #1763 (comment).

Thanks for the explanation @peppi-lotta . Now I understand the issue, this PR only deals with the target clusters logs, sorry for the confusion.
Anw, this flips the problem the other way around. The original fetch_target_logs.sh has logics to fetch the stderr as well, should that be addressed in the new solution?
Regarding the structure, I still think having clusters under k8s_target_cluster is unnecessary (maybe it should have been k8s_target_clusters, but that's an issue with another script). I could live with it though.
@adilGhaffarDev wdyt?

Regarding the structure, I still think having clusters under k8s_target_cluster is unnecessary (maybe it should have been k8s_target_clusters, but that's an issue with another script). I could live with it though.
@adilGhaffarDev wdyt?

I agree but k8s_target_cluster is coming from project-infra, let's change it there. Let's remove the clusters folder from here and change k8s_target_cluster to k8s_target_clusters in project-infra.

/test metal3-centos-e2e-integration-test-main
/test metal3-ubuntu-e2e-integration-test-main

/approve


Enable syntax highlighting for vue files using

Addresses the syntax highlighting issue raised in #2381

Thank you for the feedback. I attempted to address your suggestions in my latest commit. I'm also simplifying the <template> section by including the standard html rules. This seems to work better.


REFACTORING: Migrate SQLAlchemy models to new syntax

See https://docs.sqlalchemy.org/en/20/changelog/whatsnew_20.html#orm-declarative-models
It's more succinct and it fix the Pylance error with Column type when we want to access to attribute.

I don't understand this, can you giff an example pls?


adding coverage report

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d3a2461). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #8   +/-   ##
=========================================
  Coverage          ?   81.81%
=========================================
  Files             ?        4
  Lines             ?       99
  Branches          ?        0
=========================================
  Hits              ?       81
  Misses            ?       18
  Partials          ?        0

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 d3a2461...fa24972. Read the comment docs.


Upgrade astyanax for cassandra upgrading.

Ping @nzroller and @mikaellothman, thanks.

Looks all good @xiaodong-izettle :+1:

Thanks, @mikaellothman, that's fast. :-)


correct temperature conversions between t48 and t68

There's a note in obs_utils.t48tot68() questioning whether the conversion implemented is correct; the same equation is reported here and here; are there other conflicting references?

The problem in the equation in http://cfconventions.org/Data/cf-standard-names/27/build/cf-standard-name-table.html is that the final set of brackets says (100 - t - 48) rather than (100 - t48), which makes more sense. The second reference clears up an ambiguity so I will remove the warning messages from obs_utils.748to768(). Thanks for finding that @BillMills !

The change has been committed to master.


Hi ifvictr, just follow the README is enough to install on ghost(v3.2.0) ?

First of all, pretty thanks for your share.
My question: My ghost version is v3.2.0. I just follow the README, but i can't install it correct. So something should  be update? Honestly, I am a newbie in programming. Please give me more details for how to install this plugin for ghost~ :D  Thanks~

@BetterLuke Sorry, just saw this. Can you share more details about how you tried to install it? Any errors?

@BetterLuke I haven't released a new version yet, so anything you see in the README in master won't work for 1.0.2. Refer to this one instead: https://github.com/ifvictr/ghost-storage-github/blob/1.0.2/README.md


Unable to Tessellate shape for a valid Polygon according to GDAL/OGR and PostGIS

Description
Hello,
We recently have some issues with a Polygon geometry and the following error: "Unable to Tessellate shape” when we try to create a new document with the geo_shape type.
The error sends by Elasticsearch is:
{'error': {'root_cause': [{'type': 'document_parsing_exception',
    'reason': '[1:7350] failed to parse field [location] of type [geo_shape]'}],
  'type': 'document_parsing_exception',
  'reason': '[1:7350] failed to parse field [location] of type [geo_shape]',
  'caused_by': {'type': 'illegal_argument_exception',
   'reason': 'Unable to Tessellate shape. Possible malformed shape detected.'}},
 'status': 400}

Note that this is due to a Polygon which is valid according to other GIS tools such as GDAL/OGR or PostGIS.
How to reproduce
I have this Elastic mapping
{
    "mappings": {
        "properties": {
            "location": {
                "type": "geo_shape"
            }
        }
    }
}

Here a GeoJSON file with the Polygon which raises the error.
invalid-polygon.json
Version and environment details
I tried to reproduce this issue for different Elasticsearch versions: 7.17.24 and 8.15.1.
Elasticsearch 7.17.24 with Lucene 8.11.3
{"number": "7.17.24",
 "build_flavor": "default",
 "build_type": "tar",
 "build_hash": "fcf25fff740db6ab3ed5d145c58d70e4c3528ea7",
 "build_date": "2024-09-05T07:34:51.812485320Z",
 "build_snapshot": false,
 "lucene_version": "8.11.3"}

Elasticsearch 8.15.1 and Lucene 9.11.1
{"number": "8.15.1"
 "build_flavor": "default",
 "build_type": "tar",
 "build_hash": "253e8544a65ad44581194068936f2a5d57c2c051",
 "build_date": "2024-09-02T22:04:47.310170297Z",
 "build_snapshot": false,
 "lucene_version": "9.11.1"}

About my OS, I'm on MacOS Sequoia 15.0. The JVM used is the one which is included when I downloaded the .tar.gz from the Elastic website.
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment (build 22.0.1+8-16)
OpenJDK 64-Bit Server VM (build 22.0.1+8-16, mixed mode, sharing)

Thanks!

According to GeoJSONLint this polygon doesn't follow the "right-hand rule".

According to GeoJSONLint this polygon doesn't follow the "right-hand rule".
I don't think that matters as the tessellation algorithm would order the rings before any processing. I had a look and the problem is in the following check which is not correct: https://github.com/apache/lucene/blob/9359cfd32f1f2c9ec1fd7e3cabd75ada4fc91204/lucene/core/src/java/org/apache/lucene/geo/Tessellator.java#L463

This check as added to support shared edges by multiple holes like this example:

We need to improve that area to fix this.

Thank you for your answers from both of you.
It looks like a tricky issue :)
I'll keep on eye on this thread.

Thank you very much @iverase for your work!


ean13composite: honour dontdraw (issue #54)

This is an attempt at part-addressing issue #54 for ean13composite, returning a pixs array containing the composite, separator and linear, the latter multiplied out by 72 rows. When handed to renmatrix it does closely resemble the "native" rendering.
Marking this as a draft, any suggestions (including rejection) welcome.

It's not clean (due to the current architecture), but I'm happy to take something like that for the linear-composite symbologies since I can't think of something better that's achievable without a lot of re-engineering and a change in the data structures that are passed to the renderers (or out to the user).
Please consider the following:

I think that you can safely move the gsave into the condition.
Make it trivially possible to render the single matrix using a usematrix user option, e.g. this could be the guard for the current condition block to switch between multiple renders or a single matrix render.
Have the dontdraw option set the usematrix option, and then skip the actual render.

Nice work.

Thanks Terry, have implemented the suggestions. One thing this highlights is that the usematrix option doesn't render text. So it seems likely the whole thing as implemented here isn't of much use apart from third-party testing.

Thanks Terry, have implemented the suggestions.

Checking your force push, it looks like the commit message changed but the file contents remained the same as previously.

One thing this highlights is that the usematrix option doesn't render text. So it seems likely the whole thing as implemented here isn't of much use apart from third-party testing.

Understood, and that's fine. A small amount of extra bloat is well worth it if it enables you to more easily perform A-B tests against BWIPP.

Sorry not sure how I messed this up, will close and open a new PR. Re bloat, cool, thanks.


About AirQualityThreshold

The way I understood AirQualityThreshold when reading the documentation was something like a vector of:
[
  {
    "from": 0,
    "to": 10,
    "quality": "bad"
  },
  {
    "from": 11,
    "to": 31,
    "quality": "acceptable"
  },
  ...
]

I got surprised later not finding a vector but just an object ...
Might be I simply did not understand this.

closing issue as we are no longer capturing air quality thresholds


[sdc] Tune existing constraints

Description
This is a placeholder issue for any tuning work that needs to be done for M2.5.2.
Things to check for M2.5.2:

[x] Update JTAG frequency to at least 24MHz. #18847
[ ] Make sure that the mux on the problematic hold path described in #18687 is synthesized in a safe way.

@a-will: Do I understand correctly that the problematic hold path described in #18687 (item 2 above) got removed with the removal of generic mode? If so, do you agree that item 2 above can be checked off?


[JAVA] How to invoke RESTful web services in JAVA

Topic Suggestion
[JAVA] How to invoke RESTful web services in JAVA
Proposed article introduction
Java webservices are broadly used of late.  At the point when you associate with a site page, your program sends a solicitation, which is consequently delivered and shown in HTML. Web administrations use solicitation and reaction similarly, however as XML, JSON, or plain text.
RESTful Web Services are fundamentally REST Architecture based Web Services. In REST Architecture everything is an asset. RESTful web administrations are light weight, profoundly adaptable and viable and are usually used to make APIs for online applications. This instructional exercise will show you the nuts and bolts of RESTful Web Services and contains parts examining every one of the essential parts of RESTful Web Services with appropriate models.
Key takeaways

An introductory knowledge on Web Services Description Language
RESTful web service Endpoint interface
Web service Execution
RESTful API

Article quality
I intend to make the article simple and easy to understand for beginners. I will be giving bit by bit measure from making a few catalogs, creating hits for web administration and how to distantly get to web administrations, which most sites or articles frequently overlook. My main aim, I will be glad to make it more than mint to everyone who comes across it and hence comprehensible.
References
N/A

Sounds like a helpful topic @mulwasteveh, please make sure your article is unique and adds value to what is available online.
This is to avoid article closure in the PR section👍.

Just pinging you on this topic form - as I'm making some room in the topic queue.
No rush if you're still working on this one - if you need more time we can always re-open at a later date


fix: Correct default values which should be an array of strings

values should be an array of strings

Associated issue https://github.com/aws-ia/terraform-aws-eks-blueprints/issues/1060

@bryantbiggs I looked into the docs check and couldn't figure it out just yet, so we'll ignore that for now.

thanks @ksatirli - do you think you'll be able to cut a new release for this fix?

@bryantbiggs all done! New release candidate is live.
If we don't get any breaking changes, this will become 1.0.0 soon, thanks to your awesome contributions!


Change "IDENTIFERS" to "IDENTIFIERS"

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (7c896f5) compared to base (f402dac).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##               1.2      #807   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           45        45
  Lines         1915      1915
  Branches       321       321
=========================================
  Hits          1915      1915

Flag
Coverage Δ

production
100.00% <ø> (ø)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Make Reply feature more visible for regular users

At now Reply feature is implemented via #2390, but this feature is too badly searchable for regular users:

When users do tap on message, most of them don't see that placeholder text in bottom field is changed
If message is already typed, there are nothing changed.

So, most of users don't see implemented Reply feature and don't use it, before any other improved users show it.
As solution, we can add Reply item into 3-dot popup menu on message, that shows popup with description how to do this quickly.

Hi @MurzNN ,
Thanks for the feedback. This issue is globally tracked here: https://github.com/vector-im/riot-meta/issues/218
Benoît


Errors during setup - from the stdout logging...

I see the following errors during the initial setup, not sure if these are already addressed?
  Building wheel for multidict (PEP 517): started
  Building wheel for multidict (PEP 517): finished with status 'error'
  ERROR: Command errored out with exit status 1:
   command: /usr/bin/python3 /usr/lib/python3.9/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmpohanydcs
       cwd: /tmp/pip-install-8bhgcpmy/multidict_fffb5a7f135c472dbc4036c87159d568
  Complete output (40 lines):
  *********************
  * Accelerated build *
  *********************
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-3.9
  creating build/lib.linux-x86_64-3.9/multidict
  copying multidict/_multidict_py.py -> build/lib.linux-x86_64-3.9/multidict
  copying multidict/__init__.py -> build/lib.linux-x86_64-3.9/multidict
  copying multidict/_abc.py -> build/lib.linux-x86_64-3.9/multidict
  copying multidict/_multidict_base.py -> build/lib.linux-x86_64-3.9/multidict
  copying multidict/_compat.py -> build/lib.linux-x86_64-3.9/multidict
  running egg_info
  writing multidict.egg-info/PKG-INFO
  writing dependency_links to multidict.egg-info/dependency_links.txt
  writing top-level names to multidict.egg-info/top_level.txt
  reading manifest file 'multidict.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  warning: no previously-included files matching '*.pyc' found anywhere in distribution
  warning: no previously-included files found matching 'multidict/_multidict.html'
  warning: no previously-included files found matching 'multidict/*.so'
  warning: no previously-included files found matching 'multidict/*.pyd'
  warning: no previously-included files found matching 'multidict/*.pyd'
  no previously-included directories found matching 'docs/_build'
  adding license file 'LICENSE'
  writing manifest file 'multidict.egg-info/SOURCES.txt'
  copying multidict/__init__.pyi -> build/lib.linux-x86_64-3.9/multidict
  copying multidict/py.typed -> build/lib.linux-x86_64-3.9/multidict
  running build_ext
  building 'multidict._multidict' extension
  creating build/temp.linux-x86_64-3.9
  creating build/temp.linux-x86_64-3.9/multidict
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fomit-frame-pointer -g -fno-semantic-interposition -fomit-frame-pointer -g -fno-semantic-interposition -fomit-frame-pointer -g -fno-semantic-interposition -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/include/python3.9 -c multidict/_multidict.c -o build/temp.linux-x86_64-3.9/multidict/_multidict.o -O2 -std=c99 -Wall -Wsign-compare -Wconversion -fno-strict-aliasing -pedantic
  multidict/_multidict.c:1:10: fatal error: Python.h: No such file or directory
      1 | #include "Python.h"
        |          ^~~~~~~~~~
  compilation terminated.
  error: command '/usr/bin/gcc' failed with exit code 1
  ----------------------------------------
  ERROR: Failed building wheel for multidict
Failed to build multidict
ERROR: Could not build wheels for multidict which use PEP 517 and cannot be installed directly
fatal: not a git repository (or any of the parent directories): .git
busted 2.0.0 not found, installing via luarocks...

...
gcc -shared -o bit32.so lbitlib.o
Warning: unmatched variable LUA_LIBDIR
make[1]: Entering directory '/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726'
...

...
gcc -O2 -std=gnu99 -fPIC -g -Wall -Wextra  -Wno-missing-field-initializers  -Wno-override-init -Wno-unused -O2 -fPIC -D_REENTRANT -D_THREAD_SAFE -D_GNU_SOURCE -I"/usr/include" -I"/usr/include" -DSOCKET_DEBUG -DHAVE_CONFIG_H -DDNS_RANDOM=RAND_bytes -c -o /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.o /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c: In function 'dns_so_check':
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:6547:17: warning: array subscript -2 is below array bounds of 'unsigned char[1]' [-Warray-bounds]
 6547 |  so->query->data[-2] = 0xff & (so->query->end >> 8);
      |  ~~~~~~~~~~~~~~~^~~~
In file included from /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:83:
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.h:422:17: note: while referencing 'data'
  422 |   unsigned char data[1];
      |                 ^~~~
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:6548:17: warning: array subscript -1 is below array bounds of 'unsigned char[1]' [-Warray-bounds]
 6548 |  so->query->data[-1] = 0xff & (so->query->end >> 0);
      |  ~~~~~~~~~~~~~~~^~~~
In file included from /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:83:
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.h:422:17: note: while referencing 'data'
  422 |   unsigned char data[1];
      |                 ^~~~
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:6550:9: warning: array subscript -2 is below array bounds of 'unsigned char[1]' [-Warray-bounds]
 6550 |  qsrc = &so->query->data[-2] + so->qout;
      |         ^~~~~~~~~~~~~~~~~~~~
In file included from /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:83:
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.h:422:17: note: while referencing 'data'
  422 |   unsigned char data[1];
      |                 ^~~~
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:6576:10: warning: array subscript -2 is below array bounds of 'unsigned char[1]' [-Warray-bounds]
 6576 |   asrc = &so->answer->data[-2];
      |          ^~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:83:
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.h:422:17: note: while referencing 'data'
  422 |   unsigned char data[1];
      |                 ^~~~
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:6587:18: warning: array subscript -2 is below array bounds of 'unsigned char[1]' [-Warray-bounds]
 6587 |    alen = ((0xff & so->answer->data[-2]) << 8)
      |            ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:83:
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.h:422:17: note: while referencing 'data'
  422 |   unsigned char data[1];
      |                 ^~~~
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:6588:42: warning: array subscript -1 is below array bounds of 'unsigned char[1]' [-Warray-bounds]
 6588 |         | ((0xff & so->answer->data[-1]) << 0);
      |           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
In file included from /tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.c:83:
/tmp/luarocks_cqueues-20200726.51-0-558413/cqueues-rel-20200726/src/lib/dns.h:422:17: note: while referencing 'data'
  422 |   unsigned char data[1];
      |                 ^~~~

We do see
Successfully tagged kong-pongo-test:2.8.0
[pongo-INFO] image 'kong-pongo-test:2.8.0' successfully build

However next we see
Kong version: 2.8.0
[==========] Running tests from scanned files.
[----------] Global test environment setup.
[----------] Running tests from /kong-plugin/spec/myplugin/01-unit_spec.lua
2022/03/10 19:50:22 [warn] [Penlight 1.12.0] the contents of module 'pl.text' has moved into 'pl.stringx' (deprecated after 1.11.0, scheduled for removal in 2.0.0)
[ RUN      ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 18: myplugin: (schema) accepts distinct request_header and response_header
[       OK ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 18: myplugin: (schema) accepts distinct request_header and response_header (1.08 ms)
[ RUN      ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 28: myplugin: (schema) does not accept identical request_header and response_header
[       OK ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 28: myplugin: (schema) does not accept identical request_header and response_header (1.35 ms)
[----------] 2 tests from /kong-plugin/spec/myplugin/01-unit_spec.lua (981.70 ms total)

[----------] Running tests from /kong-plugin/spec/myplugin/02-integration_spec.lua
/kong-plugin/spec/myplugin/02-integration_spec.lua:28: Error: nginx configuration is invalid (exit code 1):
nginx: the configuration file /kong-plugin/servroot/nginx.conf syntax is ok
nginx: [emerg] chown("/kong-plugin/servroot/client_body_temp", 100) failed (13: Permission denied)
nginx: configuration file /kong-plugin/servroot/nginx.conf test failed

  Run with --v (verbose) or --vv (debug) for more details

stack traceback:
	/kong-plugin/spec/myplugin/02-integration_spec.lua:28: in function </kong-plugin/spec/myplugin/02-integration_spec.lua:11>

/kong-plugin/spec/myplugin/02-integration_spec.lua:28: 2022/03/10 19:51:00 [warn] Support for Cassandra is deprecated. Please refer to https://konghq.com/blog/cassandra-support-deprecated (deprecated after 2.7, scheduled for removal in 4.0)
2022/03/10 19:51:00 [warn] You are using Cassandra but your 'db_update_propagation' setting is set to '0' (default). Due to the distributed nature of Cassandra, you should increase this value.
Error: nginx configuration is invalid (exit code 1):
nginx: the configuration file /kong-plugin/servroot/nginx.conf syntax is ok
nginx: [emerg] chown("/kong-plugin/servroot/client_body_temp", 100) failed (13: Permission denied)
nginx: configuration file /kong-plugin/servroot/nginx.conf test failed

  Run with --v (verbose) or --vv (debug) for more details

stack traceback:
	/kong-plugin/spec/myplugin/02-integration_spec.lua:28: in function </kong-plugin/spec/myplugin/02-integration_spec.lua:11>

/kong-plugin/spec/myplugin/02-integration_spec.lua:28: Error: nginx configuration is invalid (exit code 1):
nginx: the configuration file /kong-plugin/servroot/nginx.conf syntax is ok
nginx: [emerg] chown("/kong-plugin/servroot/client_body_temp", 100) failed (13: Permission denied)
nginx: configuration file /kong-plugin/servroot/nginx.conf test failed

  Run with --v (verbose) or --vv (debug) for more details

stack traceback:
	/kong-plugin/spec/myplugin/02-integration_spec.lua:28: in function </kong-plugin/spec/myplugin/02-integration_spec.lua:11>

[----------] 0 tests from /kong-plugin/spec/myplugin/02-integration_spec.lua (41515.26 ms total)

[----------] Global test environment teardown.
[==========] 2 tests from 2 test files ran. (42497.91 ms total)
[  PASSED  ] 2 tests.
[  ERROR   ] 3 errors, listed below:
[  ERROR   ] /kong-plugin/spec/myplugin/02-integration_spec.lua @ 11: myplugin: (access) [#postgres] lazy_setup
[  ERROR   ] /kong-plugin/spec/myplugin/02-integration_spec.lua @ 11: myplugin: (access) [#cassandra] lazy_setup
[  ERROR   ] /kong-plugin/spec/myplugin/02-integration_spec.lua @ 11: myplugin: (access) [#off] lazy_setup

 3 ERRORS
rkazak@Rohintons-Mac-mini kong-plugin %

I cannot reproduce. I ran pongo run from the template plugin repo (https://github.com/Kong/kong-plugin)
This is on OSX. What environment are you using?

Yes I am on OSX (12.2.1).  I am using Rancher Desktop with the Docker under pinnings.

Same here. Looks like something changed in kong image in version 2.5.0. Steps to reproduce:

Clone latest kong-pongo master (or 1.0.0 tag, doesn't matter)
KONG_VERSION=2.4.1 ./pongo.sh build - no error (version 2.4.1)
KONG_VERSION=2.5.0 ./pongo.sh build - error as in description (version 2.5.0)
If you add python3-dev in Dockerfile - error dissapears

I am experiencing this behaviour as well. Intel, MacOS 12.3.1, using Rancher Desktop.
I have tried with different versions of kong but it does not change the behaviour for me.

@Tieske I also have issues running tests. Just integration tests, unit tests pass fine, same behaviour and permission issue as described in the original post.
I can confirm that the debug branch fixes the python issue in my environment. I see no change in the integration test behaviour.
I tried chmod -r 777 ./servroot in the project root to address the permissions issue but that had no effect. I'm somewhat new to the using kong and plugins for it, so it's entirely likely that was naive. I'll keep digging at it later today or early next week, and if there are any basic "turn it off and on again" type things that come to mind and you can share I'll give those a try too.
Thanks for the help and quick response!

I presume its permissions, but I frankly suck at unix permissions... so any helkp is appreciated

pongo strongly prefers the native linux docker driver,

@rdrimmie-miovision  what were you using that failed?

2.3 GHz 8-Core Intel Core i9, MacOS 12.3.1, using Rancher Desktop. Reproduced with a fresh clone of the template plugin repo. My setup sounds very similar to yours.

I've never used Rancher myself. But we've seen other problems with claimed docker compatibility before, iirc RHEL uses another container runtime again. Yet in the details that compatibility then fails.


UI Architecture

Decide on the UI architecture and document it in the WEP

What is the status on this one?

Any update on this?

@palemtnrider says we are close for this.  Much more description, which needs to be documented.

@jpellizzari and @palemtnrider can we close this out now that we are aligned on how to move forward with this?


fix: before fetching subscriptions, ensure modal is visible

Description
Several modal components were firing API calls to fetch Azure subscriptions even if they were not visible on screen. This PR adds a check for the visibility to ensure we aren't doing unnecessary fetches.
This will prevent weird popups from appearing when a token expires.
Task Item
fixes #8367

Coverage increased (+0.002%) to 55.775% when pulling 4cd99a3d9048c845f532497bd52d10355072a76f on benbrown/extrasubs into 402f6a72086b5a275ba729bebd60e2d97480af2a on main.


Update README.md

The alternative import statement in the Usage section should be:
import assert from 'assert/strict'  // Node >=16

instead of:
import { equal } from 'assert/strict'  // Node >=16

For the following code to work:
export function testAdd() {
  assert.equal(1 + 2, 3)
}

Thanks for the feedback. I wanted to convey that it's possible to use directly equal and other assert's functions:
import { equal } from 'assert/strict'

function testSomething() {
  equal(a, b)
}

That said, I agree it might actually be confusing and not a lot better than assert.equal.


Add random color option for detections

I think we should actually just forego the idea of random colors just being a special case of the Color class. Its clearer and more discoverable to have random colors be a function argument.


Shell check info in README.md

@tisnik Your image is available in the registry: docker pull registry.devshift.net/fabric8-analytics/f8a-api-gateway:SNAPSHOT-PR-28


Getter for name of CollisionDetectorAllocator

Description
Here is the PR to change the interface for the CollisionDetectorAllocator objects to have a simple getter method for the name.  Please test this to see if it works for you.

closing and re-opening to trigger the new CI as well! I had to add some on: ... conditions. Thanks for the PR :tada:

Please add a short MIGRATIONS.md entry for this change.

@v4hn Done, what do you think of what I wrote in the migration notes for this?  Do we pre-pend to the lists there or do we add the newest changes to the end of the list?

Please keep a clean history for the Windows-Support PR though. I don't think we need to keep the EXPORT/IMPORT helper commits at all.

@wolfv do you understand how to do this?  If not I can walk you through it or do it for you.  The steps I would do to do this would be to edit the commits where those lines come with an interactive rebase and cherry pick this commit at the end (you'll probably need to do a merge conflict when you do that).

Done, what do you think of what I wrote in the migration notes for this?

:+1:

Do we pre-pend to the lists there or do we add the newest changes to the end of the list?

I would append at the bottom, but I'm not sure we were consistent in the past.
In the future we want to prepend for sure because there will be no regular ROS distributions for ROS anymore.


Fix ASAN flake

Properly track lifetime and ownership of acceptor, leading to
the elimination of a flake we're seeing in prod.

Failures: #24375


perf: test-suit loader improvement - [INS-4400]

Issue
When the nesting levels are deeper or there are too much children under workspace. The withDescendants will take a long time to find all requests.
Changes

[x] Add a queryType param for withDescendants function to limit the types of database queries
[x] pass stopType and queryType when call the withDescendants function in test-suit loader

An alternative implementation would look like replacing stopType with queryType as they have overlapping behaviour.
Note: there are only 3 usages of stopType in the code and they all stop on request type, you could just set request as the query type and remove that argument completely.

An alternative implementation would look like replacing stopType with queryType as they have overlapping behaviour.
Note: there are only 3 usages of stopType in the code and they all stop on request type, you could just set request as the query type and remove that argument completely.

@jackkav The request may not be a direct child of workspace, but a child of requestGroup. So we need to include both request and requestGroup in queryType, and let the query stop at reques type.


vsCode not recognizing --args from npm

creating an NFT (non-fungible tokens) collection with CodeSTACKr v.2.0.0 repo on vscode (https://github.com/codeSTACKr/create-10k-nft-collection), as per following tutorial (https://www.youtube.com/watch?v=quGdJweadFM). been able to generate our images and do the NFTs minting but command does not respond well and doesn’t read the arguments,  i.e. the -- (dash dash) “flags”, and ignores anything that comes after.
Example of commands:
a) WHEN MINTING : npm run mint --start=1 --end=100
b) TO CONFIRM TRANSACTIONS: npm run check_txns --dir=minted
vsCode is unable to read/understand the “flags”, i.e. the -- (dash dash). FYI, in mint.js the argument in question defines the range of NFTs to mint, and checkTxns.js points to the directory where files are.
I understand that my arguments are handled by npm, instead of my script and to try npm run-script -- --args instead. (https://docs.npmjs.com/cli/v8/commands/npm-run-script#description). I tried entering  npm run-script mint --start=1 --end=100
To no avail.
I do understand conceptually that the Terminal will execute the command as per the script of each node/package, but as far as I can tell, these scripts are already specified in the two js files in questions.
Error logs below.
When running npm run check_txns --dir=minted
Please specify the directory to check. Use "minted" or "revealed"
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>check_txns: node utils/nftport/checkTxns %npm_config_dir%
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>check_txns script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
When minting npm run mint --start=1 --end=100
Minting works, but ignores the --flags and mints everything (i.e. does not respect the range I indicated).
Working on:
VS Code Version: 1.65.2
OS Version: macOS Monterey 12.2 (running on a Mac M1
chckTxns.docx
mint.docx
)

See also #145167

were you able to fix this error???

No, since this is not a VS Code problem.
Please read #145167

Then I can't reveal my nfts?

I got the minting done but check_txns command is not working

As said before: your problems have nothing to do with VS Code. Please find help elsewhere.


pkg/barback should be a normal (not dev) dependency

Right?

Was fixed in 980d28d6 (quite a while ago)


Resolves #1796

Provide more examples
https://github.com/MicrosoftDocs/windows-powershell-docs/issues/1796

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

File
Status
Preview URL
Details

docset/windows/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012-ps/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/storage/New-Partition.md
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

docset/windows/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012-ps/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/storage/New-Partition.md
:white_check_mark:Succeeded

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

@dariomws @get-itips @tseward
Peer review needed for this PR. Thanks.
@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

Docs Build status updates of commit ca71bbd:
:clock10: Pending: waiting for processors (23 builds ahead of you)
:warning: Docs Build is busy, currently there are 23 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

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

File
Status
Preview URL
Details

docset/windows/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012-ps/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/storage/New-Partition.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 5b99638:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012-ps/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/storage/New-Partition.md
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

docset/windows/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012-ps/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/storage/New-Partition.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 643e9b3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012-ps/storage/New-Partition.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/storage/New-Partition.md
:white_check_mark:Succeeded

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


person: Add null safety to update daily rates

As described in the issue this pull request introduces security for null values. Furthermore incorrect DailyRates are no longer saved in the PersonEntity.
This solution provides a current solution. In the future such logics should be mapped in a service for the repository.
Closes #426

No further ideas from my side and no idea to reproduce by system tests.
@acetous?

@acetous not being available before Thursday, just go ahead with it


2.0.1

Release notes - Planorama - Version 2.0.1
Bug
PLAN-739 Back of Badge report space adjustment
PLAN-738 REPORT - virtual people marked report needs all the other people too
PLAN-736 People flyout is not showing the correct values for livestream-permission or recording-permission
PLAN-735 In the publish->current DIFF, Add/Drop tab is not showing all sessions that had a participant who became dropped.
PLAN-734 Update tags being sent to conclar: social media and streamed
PLAN-733 Rerunning an older pub->pub DIFF, after other changes made later, Sessions Added tab doesn't show the moderators and participants who were assigned at the older time
PLAN-732 New problem: can't run DIFF report between publish and live.
PLAN-731 Running an older DIFF between 2 publishes shows Participants Dropped who were not dropped until after the 2nd publish
PLAN-730 DIFF between publish and current state showing false add for a partially scheduled session
PLAN-724 DIFF between publish and current state still shows false drops/adds, and some added participants are showing twice
PLAN-719 Incorrect issues with DIFF report between a publish and current state (live), and also between 2 publishes
PLAN-717 the anchors on the reports page do not do the right thing
PLAN-716 Daily Grid Report should get moved into Program Op...
PLAN-715 Getting SessionAssignment gibberish trying to run a diff between 2 publishes
PLAN-714 In publish->publish DIFF, a participant who is no longer assigned to any sessions (but has not officially dropped from con) should not appear in the Participants Dropped tab
PLAN-713 In DIFF between publish and live, some participants are still showing twice in the add column of add/drop tab.
PLAN-712 In DIFF between publish and live, some draft sessions are appearing incorrectly on Sessions Removed tab
PLAN-706 Diff report comparing 2 publishes does not list participants from removed sessions, on participants add/drop tab
PLAN-705 DIFF between a publish and live shows added participants twice
Story
PLAN-721 REPORT - all the people with all the virtual people marked
PLAN-708 Airmeet Integration - Settings
PLAN-543 Airmeet Integration - Sync
Task
PLAN-727 Improve Cache for Conclar in Plano
What's Changed

Merge pull request #629 from ChicagoWorldcon/staging by @Gailbear in https://github.com/ChicagoWorldcon/planorama/pull/630
update brakeman exceptions by @balen in https://github.com/ChicagoWorldcon/planorama/pull/632
plan-712, plan-713, plan-714, plan-715 Change report fixes by @balen in https://github.com/ChicagoWorldcon/planorama/pull/634
Change report fixes by @balen in https://github.com/ChicagoWorldcon/planorama/pull/635
fix tests for room and start time by @balen in https://github.com/ChicagoWorldcon/planorama/pull/636
Plan 719 fix diff with current by @balen in https://github.com/ChicagoWorldcon/planorama/pull/637
fix for missing session test by @balen in https://github.com/ChicagoWorldcon/planorama/pull/638
PLAN-716 PLAN-717 fix report page headings by @Gailbear in https://github.com/ChicagoWorldcon/planorama/pull/639
PLAN-727 cache for conclar requests (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/640
PLAN-724 various fixes to diff logic (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/641
fix for cache config. Use memory for now as we do no cache much by @balen in https://github.com/ChicagoWorldcon/planorama/pull/643
handle case of new scheduled sessions (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/646
fix typo (should not call id on id) (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/647
fix pub to pub diff status check (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/649
fix diff issue for current (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/652
PLAN-732 PLAN-731 Stag diff dropped people (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/656
ignore declined to drop (and vice versa) in the drop report (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/657
fix typo by @balen in https://github.com/ChicagoWorldcon/planorama/pull/659
fix for session titles (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/660
Update streamed tag to use Environment filter (2.0.1) by @LVerhulst4321 in https://github.com/ChicagoWorldcon/planorama/pull/662
plan-733, plan-735 fixes for pub diffs getting old state of relations… (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/663
plan-721 virtual people report (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/664
Add description lines to PLAN-721 report by @dcterman in https://github.com/ChicagoWorldcon/planorama/pull/666
PLAN-739 Shorten abbrev for minutes to save output space by @dcterman in https://github.com/ChicagoWorldcon/planorama/pull/669
Change people flyout for stream & record & photo by @dcterman in https://github.com/ChicagoWorldcon/planorama/pull/670
Modify description for virtual report by @dcterman in https://github.com/ChicagoWorldcon/planorama/pull/671
PLAN-738 change to include all participants on pub sessions and add is virtual… (2.0.1) by @balen in https://github.com/ChicagoWorldcon/planorama/pull/673
PLAN-543 Airmeet Integration by @Gailbear in https://github.com/ChicagoWorldcon/planorama/pull/674

Full Changelog: https://github.com/ChicagoWorldcon/planorama/compare/v2.0.0...v2.0.1

Reviewed myself - looks fine? lol


Support watermark/placeholder text

When embedding Monaco editor as a in-line control, we'd like to show a placeholder text before any value is entered, similar to how textbox works, so user sees an example of the expected value for the said parameter.
Derek, Azure Logic Apps

Did you find something?

anything updated?

need this feature too

Here is my solution: add another element to simulate placeholder
https://codesandbox.io/s/monaco-editor-placeholder-vue-1lurc?file=/src/components/MonacoPlaceholder.vue

The solution is a simple overlay element linked to the basic Monaco events like:

onDidBlurEditorWidget
onDidFocusEditorWidget

You can check my simplified version of Monaco build (added ES modules support) repo where I have placeholder example:
Demo:
https://bultas.github.io/monaco-component/dist/placeholder.html
Source:
https://github.com/bultas/monaco-component/blob/master/dist/placeholder.js
Repo:
https://github.com/bultas/monaco-component

Is this feature now supported?

is placeholder supported?

Based on the VSCode implementation, i've come up with the following IContentWidget:
/**
 * Represents an placeholder renderer for monaco editor
 * Roughly based on https://github.com/microsoft/vscode/blob/main/src/vs/workbench/contrib/codeEditor/browser/untitledTextEditorHint/untitledTextEditorHint.ts
 */
class PlaceholderContentWidget implements monaco.editor.IContentWidget {
    private static readonly ID = 'editor.widget.placeholderHint';

    private domNode: HTMLElement | undefined;

    constructor(
        private readonly placeholder: string,
        private readonly editor: monaco.editor.ICodeEditor,
    ) {
        // register a listener for editor code changes
        editor.onDidChangeModelContent(() => this.onDidChangeModelContent());
        // ensure that on initial load the placeholder is shown
        this.onDidChangeModelContent();
    }

    private onDidChangeModelContent(): void {
        if (this.editor.getValue() === '') {
            this.editor.addContentWidget(this);
        } else {
            this.editor.removeContentWidget(this);
        }
    }

    getId(): string {
        return PlaceholderContentWidget.ID;
    }

    getDomNode(): HTMLElement {
        if (!this.domNode) {
            this.domNode = document.createElement('div');
            this.domNode.style.width = 'max-content';
            this.domNode.textContent = this.placeholder;
            this.domNode.style.fontStyle = 'italic';
            this.editor.applyFontInfo(this.domNode);
        }

        return this.domNode;
    }

    getPosition(): monaco.editor.IContentWidgetPosition | null {
        return {
            position: { lineNumber: 1, column: 1 },
            preference: [monaco.editor.ContentWidgetPositionPreference.EXACT],
        };
    }

    dispose(): void {
        this.editor.removeContentWidget(this);
    }
}

Should be initialized with
 new PlaceholderContentWidget('The value for placeholder', editorReference);

Thanks @stefan-lacatus!
You can try it out in the playground.
I recommend to use injected text though or to disable cursor interaction, as clicking on the placeholder won't focus the editor though.
Closing this issue, as this can be easily implemented.

I recommend to use injected text though or to disable cursor interaction, as clicking on the placeholder won't focus the editor though.

Correct, I fixed this a while back by just setting pointerEvents = 'none' on the dom node. Seems to create a good enough UX.
I've updated the post above.


8.1.1 cannot import appWithTranslation anymore

Describe the bug
In _app.tsx:
import { appWithTranslation } from 'next-i18next'
throws an error that it cannot find appWithTranslation. It does find withTranslation though.
Occurs in next-i18next version
8.1.1
Expected behaviour
We should be able to import this, or the docs are outdated. Version 8.1.0 does not have this problem.
OS (please complete the following information)

Device: [MBP 2016 15"]

Hi @LeunensMichiel – if you check the link below, you'll see a TS example running<EMAIL_ADDRESS>in strict mode without any issues.
If you can provide a reproducible repo, please do let me know.

Hi @LeunensMichiel – if you check the link below, you'll see a TS example running<EMAIL_ADDRESS>in strict mode without any issues.

@LeunensMichiel  I can't see any link here, could you please point me to a link that uses TS, I'm using it and I'm having issues.


Make all the timestamps appear in the user's local timezone

It would be really neat if all the times displayed used the local timezone I'm in.

Definitely. Could even call this a serious bug that they don't!


Enet rewrite + some enum fixes

UDP is out and enet is in.
Some enums went wrong so I've fixed those as well.
Won't merge to main until @MadByteDE is convinced we're good to go.

Fixes #184

Code refactor to make it tidy will be the next iteration.

Not expecting a code review. This took me 6 hours to research and write.
Just wanted to clear other PR's before processing this one.

PR to be merged

after asset loader
before rangefinder fix

This branch was working but now it's bugged. It's not important to the v0.11 release so I'll park this for a day or two and merge other PR's first.

Closing this and starting a new enet branch.


IE11 crashes when source is loaded before Promises polyfill

Hi,
I've seen that in your latest release you changed the isDefined checking from this:
if (typeof Promise === 'undefined') {

to this:
if (!isDefined(Promise)) {

That line of code crashes on IE11 and stops the file being loaded, forcing us to always load the Promise polyfill before.
My source code is bundled together in one single file and it has a method that loads polyfills on demand after checking the navigator features. Now, I can't do that with Promises due to the crash I've reported.
I would like to know if this is ok for you, or have plans on adressing this issue, because if not, I need to change some things in my code (I think I will end adding the Promise polyfill to the source bundle before your source is added to it)
Thanks for your response

@limonte Hm, I'm surprised that we use a function here because simply referencing Promise alone will make all runtimes crash if it's not defined, hence the typeof check which is a language construct that permits to address undefined symbols safely.
See:

My bad :man_facepalming: will fix asap

Fixed in v7.0.10, thanks @aitorllj93 for reporting and @toverux for explaining my fuckup


Publish 1.1.0

This pull request has been deployed to Vercel.

✅ Preview:
https://matou-technologies-purrfect-ui-storybook-76.vercel.app

🔍 Inspect:
https://vercel.com/matou-technologies/purrfect-ui/kJ1SSDuSpaqSP7U58i1s7tKQVv3K


Add .nox to GitHub's .gitignore

Thank you for nox. I made a PR to add .nox to GitHub's .gitignore file. But, I couldn't find a place in the documentation where it talks about it. Is that correct? if so, would a PR be welcome?

Thanks for doing this! The .nox directory is documented here: http://nox.readthedocs.io/en/latest/usage.html#storing-virtualenvs-in-a-different-directory
Let me know if you need anything else.


Inaccurate depth count after readError

It seems like DiskQueue does not accurately update depth when a read error occurs (in handleReadError()) or in the scenario where the machine finishes reading a file, deletes a file, but crashes before writing to the MetaData file.

Yes, those edge cases are possible. What we do is perform checks when you reach the tail of the queue:
https://github.com/nsqio/go-diskqueue/blob/master/diskqueue.go#L521-L536

Hello, I'm not sure if I should make a new issue or respond here. I found that in the case where the user is reading all of the messages in the queue and the last file is corrupted, the depth never becomes 0. Within the if clause in line 579, the readFileNum == the writeFileNum and writePos is set to 0 as is the readPos later on in the function. After the readPos is set to 0, shouldn't checkTailCorruption be called or depth be set to 0?
https://github.com/nsqio/go-diskqueue/blob/99f6193f1106cefd16bca4d5727a62a2a7c19c7d/diskqueue.go#L579-L605

Yea, you're right, we should call d.checkTailCorruption(d.depth) at the end of handleReadError(), want to open a PR?

Yes I would love to open a PR and add the change: call ‘d. checkTailCorruption(d.depth)’ at the end of ‘handleReadError()’


Provide parameters in test failure message for Triangle exercise

Why?

To make it possible to see from the failure message which triangle is being tested/failing.  #653
What?

Provided the parameters that are being tested in the error message for a more informative message.
So instead of:
  1) Failure:
TriangleTest#test_equilateral_triangle_sides_may_be_floats [ruby/triangle/triangle_test.rb:36]:
Expected 'true', triangle is equilateral.

You would see:
Expected 'true', triangle [0.5, 0.5, 0.5] is equilateral.

How Has This Been Tested?

Created a Triangle class that would fail the tests to produce the errors. Please see the screen shot below for the outputs.
Screenshots (if appropriate):

Types of changes

n/a Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (non-breaking change which adds functionality)
n/a Breaking change (fix or enhancement that would cause existing functionality to change)
n/a Gardening (code and/or documentation cleanup)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My change relies on a pending issue/pull request
n/a My change requires a change to the documentation.
n/a I have updated the documentation accordingly.
n/a I have added tests to cover my changes.
[x] All new and existing tests passed.

Edit: removed empty checkboxes.

Thanks for this @deohtee.
Great description post, and thanks for adding a screenshot.
What you've done here looks great, unfortunately because this is a Generated test suite these changes will be overwritten next time the tests are regenerated.
The other file that you need to change is: https://github.com/exercism/xruby/blob/master/exercises/triangle/.meta/generator/triangle_case.rb
And then you can regenerate the test suite file by running: bin/generate -f triangle
Please ask if you have any questions, either here or in the xruby Gitter chat room

Just put another commit in that fixed the triangle sides showing up in the test names. Let me know what you think! Always open for feedback. 😄

This looks good, thanks 👍

@deohtee it looks great... thank you!


Fix fallback of data attribute in query result

Related to #127.
As described in https://www.apollographql.com/docs/react/essentials/queries#props, the data object is either the actual query result, or the empty object {} when the data is not (yet) available.
The type of QueryHookResult should match that.

Alright, it seems it's more complicated than this. I guess we'd need a type union to differentiate between loading and/or failed queries (that have data of {}) and completed queries (that have actual data).
And then there's partial queries also …


Add thrift gen files

Add thrift gen files, such as gen-py.

Sorry for vim,I didn't notice the file of Vim.gitignore.
As for Thrift,this is the official website:http://thrift.apache.org/. After write a *.thrift file, I run "thrift --gen py ",then a catalog named gen-py generated.
That's all.I hope I have not misunderstood what you mean.

Sorry for the delay in getting back to you. From what I can tell, it looks like thrift is generic across several languages rather than something specific to python. As such it would probably be better off in its own (global?) template.


Refactor how we store group_ids on conversations and agent_configurations

Today's group_ids on conversations and agent_configurations performs a conjunction on all group ids, this is too limiting as one space can have more than one group, we should perform disjunction between a space's groups.
To achieve this we need to update the way we store those to store a List of List of groupIds.

I don't understand the problem (and therefor, the solution).

The problem is that a space can have more than one group (we apply a disjunction/OR on the groups of a space). At the moment we only store a simple array of group ids on the agent_configurations and conversations on which we run a conjunction/AND. This does not work as a user is not expected to be in all space's group only one is enough.
We want to move towards a pattern that makes this easy to apply the same logic on agent_configurations and conversations.


How to refresh hidden table in swipe mode?

I believe I'm experiencing a similar issue as noted in #163, but unclear on the proper way to refresh a table.
On my page I have several tables, hidden on page load. The user can then toggle these tables, but often only one column is visible until the window is resized (desktop) or one scrolls on a phone.
Now I have an unconventional implementation as the site is using an antiquated version of jQuery. Thus I'm not using the jQuery version of Tablesaw. However, I would like to trigger a Tablesaw refresh within jQuery code.

FYI: In my jQuery code I'm identifying the ID of the table in question (for example: tablesaw-5652) and passing to the following function where I've confirmed that $ is an alias for 'shoestring':
function table_refresh(id) {   $("#" + id).data('table').refresh(); }
However, I'm getting the following error: Uncaught TypeError: Cannot read property 'refresh' of undefined

For the error noted in my previous comment, I resolved this by using 'tablesaw' instead of 'table'. This caused the number of visible columns to be fixed, but unfortunately limited it to only one non-persistent column when viewing on my phone where I knew additional columns could fit.
What seems to be working for me, after re-reading the documentation, is to not include tablesaw-init.js and use trigger("enhance.tablesaw") when showing a hidden table instead of refresh().


Enabling ssl on titan 1.0 with gremlin-server errors out

I'm getting the following exception when trying to start gremlin-server with ssl enabled with titan 1.0:
6611 [main] WARN  org.apache.tinkerpop.gremlin.server.AbstractChannelizer  - Enabling SSL with self-signed certificate (NOT SUITABLE FOR PRODUCTION)
Exception in thread "main" java.lang.NoClassDefFoundError: io/netty/handler/ssl/SslContextBuilder
	at org.apache.tinkerpop.gremlin.server.AbstractChannelizer.createSSLContext(AbstractChannelizer.java:207)
	at org.apache.tinkerpop.gremlin.server.AbstractChannelizer.init(AbstractChannelizer.java:114)
	at org.apache.tinkerpop.gremlin.server.channel.WebSocketChannelizer.init(WebSocketChannelizer.java:55)
	at org.apache.tinkerpop.gremlin.server.GremlinServer.start(GremlinServer.java:143)
	at org.apache.tinkerpop.gremlin.server.GremlinServer.main(GremlinServer.java:291)
Caused by: java.lang.ClassNotFoundException: io.netty.handler.ssl.SslContextBuilder
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 5 more

It appears that this is because Titan only includes netty version 4.0.25 and SslContextBuilder was added to netty in version 4.0.28.  It's not a problem for the TinkerPop project because it appears to include netty 4.0.28, so it looks like a dependency problem with Titan as it's pulling in TinkerPop?

If I copy the netty-all-4.0.28-Final.jar to the titan lib directory (and mv the existing netty-all-4.0.25-Final.jar to netty-all-4.0.25-Final.jar.backup), the server starts with ssl enabled.

Fixed via 2df21d5b0becc731471423018234126a781c6534 - tested ssl manually - seems to be all good.


kbfsfuse keeps crashing on my Linux machine

Hi! I just started using Keybase. Today, my laptop was running real slow. I checked iotop, and noticed that kbfsfuse was performing a lot of IO. So I killed it, using the same procedure that the run_keybase script does:
fusermount -uz /keybase
killall kbfsfuse

Now I'm trying to use Keybase to transfer some information among two of my laptops, but kbfsfuse just won't start.
Hope you guys can find what's wrong from my log id: ba34c3bb1a6f6ed29acc681c
I've found some errors on keybase.kbfs.log, related to a "merge conflict" or something? It ends with:
2017-10-09T18:58:59.519607-03:00 ▶ [DEBU kbfs(CR a6b56b0e) conflict_resolver.go:3172] 2b3 Recreate ops: [] [tags:CRID=CiULk7kBqREqE71X19r-Yg]
2017-10-09T18:58:59.520826-03:00 ▶ [DEBU kbfs(CR a6b56b0e) asm_amd64.s:509] 2b4 Finished conflict resolution: <nil> [tags:CRID=CiULk7kBqREqE71X19r-Yg]
panic: runtime error: index out of range

goroutine 367 [running]:
github.com/keybase/kbfs/libkbfs.path.tailName(...)
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/path.go:122
github.com/keybase/kbfs/libkbfs.(*setAttrOp).checkConflict(0xc420ae2200, 0x1e6ea60, 0xc422aa2e00, 0x1e63ce0, 0xc420044590, 0x1e7b140, 0xc42466ae00, 0x0, 0x0, 0x0, ...)
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/ops.go:1135 +0x98d
github.com/keybase/kbfs/libkbfs.(*crChain).getActionsToMerge(0xc4204316c0, 0x1e6ea60, 0xc422aa2e00, 0x1e63ce0, 0xc420044590, 0x82ae8d540e6bb5a6, 0x160d37b5d485aeb4, 0x0, 0x0, 0xc423cdde00, ...)
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/cr_chains.go:203 +0x16b
github.com/keybase/kbfs/libkbfs.(*ConflictResolver).getActionsToMerge(0xc4202357a0, 0x1e6ea60, 0xc422aa2e00, 0xc422aab2c0, 0xc422aaa3c0, 0xc4220d7d10, 0x20, 0xc4220dc2d0, 0x46)
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/conflict_resolver.go:1938 +0x342
github.com/keybase/kbfs/libkbfs.(*ConflictResolver).computeActions(0xc4202357a0, 0x1e6ea60, 0xc422aa2e00, 0xc422aab2c0, 0xc422aaa3c0, 0xc4206c2200, 0x9, 0x9, 0xc4220d7d10, 0x0, ...)
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/conflict_resolver.go:2093 +0x2b2
github.com/keybase/kbfs/libkbfs.(*ConflictResolver).doResolve(0xc4202357a0, 0x1e6ea60, 0xc422aa2e00, 0x8, 0x0)
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/conflict_resolver.go:3189 +0x11fc
github.com/keybase/kbfs/libkbfs.(*ConflictResolver).processInput.func3(0xc4202357a0, 0xc420b14180, 0xc4220c6c00, 0x8, 0x0, 0xc420aadb60)
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/conflict_resolver.go:217 +0x229
created by github.com/keybase/kbfs/libkbfs.(*ConflictResolver).processInput
	/root/build/gopaths/amd64/src/github.com/keybase/kbfs/libkbfs/conflict_resolver.go:205 +0x278

Thanks for the report!  Already looking through your logs, will update when I figure it out or have a workaround.  Sorry for the bad experience!

Thanks :) BTW, for now, everything I have in my private folder is a copy... So I won't mind if one of the workarounds is to reset the folder entirely.

@fabiob: I think the workaround is to stop Keybase on this machine, and blow away the local commits that haven't made it to the server yet:
rm -rf /home/$USER/.local/share/keybase/kbfs_journal/v1/01208b089f86dfff40f1adfbaedcf1b2056f-a6b56b0e548dae82

Then restart Keybase, and copy the files back into the shared folder.
If I'm reading the logs right, it looks like you wrote a bunch of files from two different devices at the same time, and managed to get this device into a weird, broken state.  Nothing wrong with that, it should work, but you managed to trip an edge case.  I'll work on fixing it.  But for now, let me know if the workaround fixes things.

It worked! Thanks for your help, @strib!
What actually happened is that I've sent a bunch of files to my private folder yesterday from my "Computer A", then shut it down.
Today I tried to send some more from "Computer B". When I opened my private folder on "Computer B", I noticed that some of the files were missing, so I just sent those again.
When I was done, I opened "Computer A" again, and the bug kicked in.

Ah got it, that makes sense.  Thanks for the explanation.  I'll work on finding the bug to prevent this from happening again in the future.


Weird results when translating english to finnish (using EasyNMT with opus-mt)

While translating English to Finnish using your model via EasyNMT, I noticed something weird. Check this code and the results.
from easynmt import EasyNMT
model = EasyNMT('opus-mt')

text='''Religion and theology is the study of religious beliefs, concepts, symbols, expressions and texts of spirituality.
Programmes and qualifications with the following main content are classified here:
Religious history
Study of sacred books
Study of different religions
Theology
=== Inclusions
Included in this detailed field are programmes for children and young people.'''

print(model.translate(text,target_lang='fi'))

The output is:
'Uskonto ja teologia tutkivat uskonnollisia käsityksiä, käsitteitä, symboleja, ilmaisuja ja tekstejä hengellisyydestä.
Ohjelmat ja tutkinnot, joiden pääsisältö on seuraava:
Uskonnollinen historia
Pyhien kirjojen tutkiminen
Eri uskontojen tutkiminen
Teologia
Suomennos: Michael T. Francis Pinmontagne SUBHEAVEN.ORG
Tähän yksityiskohtaiseen kenttään kuuluvat lasten ja nuorten ohjelmat.'

So "=== Inclusions" is translated into "Suomennos: Michael T. Francis Pinmontagne SUBHEAVEN.ORG".
What is going on here? Is this a problem with Opus-MT model or its EasyMT implementation?
PS. The sample text is from ESCO ontology

Yes, that looks a bit weird. The model at huggingface does not seem to handle that kind of input well. At least a newer OPUS-MT model does not do that anymore. You can try it here: https://translate.ling.helsinki.fi/ui/memad
It should be from this model: https://object.pouta.csc.fi/Tatoeba-MT-models/eng-fin/opusTCv20210807+bt-2021-12-08.zip

Thanks for the reply. I was able to solve the problem by using the new Tatoeba model.
Just in case someone has the same problem, just follow these instructions to convert Tatoeba models into Hugginface format:
https://github.com/huggingface/transformers/tree/master/scripts/tatoeba
Then you can use the model with this code (copied from here):
from transformers import AutoTokenizer, AutoModelForSeq2SeqLM
# Initialize the tokenizer
tokenizer = AutoTokenizer.from_pretrained(PATH_TO_CONVERTED_MODEL)
# Initialize the model
model = AutoModelForSeq2SeqLM.from_pretrained(PATH_TO_CONVERTED_MODEL)
# Tokenize text
text = "Hello my friends! How are you doing today?"
tokenized_text = tokenizer.prepare_seq2seq_batch([text], return_tensors='pt')
# Perform translation and decode the output
translation = model.generate(**tokenized_text)
translated_text = tokenizer.batch_decode(translation, skip_special_tokens=True)[0]
# Print translated text
print(translated_text)

PS. Conversion worked only for "eng-fin" model, while "fin-eng" failed because of some dimension mismatch error: "raise ValueError(f"Hidden size {hidden_size} and configured size {cfg['dim_emb']} mismatched or not 512") KeyError: 'dim_emb'"


Update invite rewards copy, fixes typo and backwards compat

Description
As the title says
Other changes
N/A
Tested
Manually
How others should test
N/A
Related issues
N/A
Backwards compatibility
Yes

Hey @MuckT since NA is mentioned in how other should test , we are skipping this PR
Thanks
Cc: @kathaypacific