[ADAM-1517] Move to Parquet 1.8.2 in preparation for moving to Spark 2.2.0

Bumps Parquet version to 1.8.2. Relocates org.apache.avro to org.bdgenomics.avro. Resolves #1517 pending release of and bump to Spark 2.2.0.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1980/Build result: FAILURE[...truncated 16 lines...] > /home/jenkins/git2/bin/git rev-parse origin/pr/1518/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains add8189a144f110fa5fb3ee371340b388995c31f # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1518/merge^{commit} # timeout=10Checking out Revision add8189a144f110fa5fb3ee371340b388995c31f (origin/pr/1518/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f add8189a144f110fa5fb3ee371340b388995c31fFirst time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result SUCCESSADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result SUCCESSADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result SUCCESSNotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

From Spark 1.6.1 Jenkins test failure:
java.lang.NoSuchMethodError: org.apache.parquet.io.api.Binary.fromCharSequence(Ljava/lang/CharSequence;)Lorg/apache/parquet/io/api/Binary;
	at org.apache.parquet.avro.AvroWriteSupport.fromAvroString(AvroWriteSupport.java:367)
	at org.apache.parquet.avro.AvroWriteSupport.writeValueWithoutConversion(AvroWriteSupport.java:342)
	at org.apache.parquet.avro.AvroWriteSupport.writeValue(AvroWriteSupport.java:274)
	at org.apache.parquet.avro.AvroWriteSupport.writeRecordFields(AvroWriteSupport.java:187)
	at org.apache.parquet.avro.AvroWriteSupport.write(AvroWriteSupport.java:161)
	at org.apache.parquet.hadoop.InternalParquetRecordWriter.write(InternalParquetRecordWriter.java:121)
	at org.apache.parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:123)
	at org.apache.parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:42)
	at org.apache.spark.rdd.InstrumentedRecordWriter$$anonfun$write$1.apply$mcV$sp(InstrumentedOutputFormat.scala:55)

That InstrumentedRecordWriter is ours from bdg-utils, right?

@heuermh I believe this error indicates that moving to Parquet 1.8.2 breaks backwards compatibility with Spark 1.x.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2224/Build result: FAILURE[...truncated 15 lines...] > /home/jenkins/git2/bin/git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ # timeout=15 > /home/jenkins/git2/bin/git rev-parse origin/pr/1518/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a -v --no-abbrev --contains 695be809b4ceb2e71f851ecf1d400cdab9b7ce3f # timeout=10Checking out Revision 695be809b4ceb2e71f851ecf1d400cdab9b7ce3f (origin/pr/1518/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 695be809b4ceb2e71f851ecf1d400cdab9b7ce3fFirst time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2226/Build result: FAILURE[...truncated 15 lines...] > /home/jenkins/git2/bin/git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ # timeout=15 > /home/jenkins/git2/bin/git rev-parse origin/pr/1518/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a -v --no-abbrev --contains 7dc8012a419fd3b690398efd2f4380511e4b258a # timeout=10Checking out Revision 7dc8012a419fd3b690398efd2f4380511e4b258a (origin/pr/1518/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 7dc8012a419fd3b690398efd2f4380511e4b258aFirst time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2326/Build result: FAILURE[...truncated 15 lines...] > /home/jenkins/git2/bin/git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ # timeout=15 > /home/jenkins/git2/bin/git rev-parse origin/pr/1518/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a -v --no-abbrev --contains b1854a63487857748b082c9067790865eba04796 # timeout=10Checking out Revision b1854a63487857748b082c9067790865eba04796 (origin/pr/1518/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f b1854a63487857748b082c9067790865eba04796First time build. Skipping changelog.Triggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,2.1.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.1.0,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.1.0,centosADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.1.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.1.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.1.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.1.0,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Coverage decreased (-0.4%) to 82.957% when pulling 7f76693c1e8c0b726f59dc5f75e351b4762aef51 on fnothaft:issues/1517-parquet-1.8.2-shade-avro into 9b51df59891abfe0e544ff038c216636be835dd2 on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2329/
Test PASSed.

The bad things are to depend on 1.8.2 and shade 1.8.1 to include at runtime?    :)

Yeah, I'm not proud of what I've done. It's a real mess; there's a lot going on. Here's the big four:

spark-sql depends on parquet-column and whatnot, but doesn't depend on parquet-avro, but spark-core also depends separately on avro. Since they depend on avro but don't depend on parquet-avro, there's effectively a transitive dependency conflict that exists, but Spark doesn't notice it. spark-sql does include parquet-avro in test scope, but then pins parquet-avro to 1.8.1 even after parquet-column moved to 1.8.2 (iirc, I'd need to double check this).
parquet-avro kinda broke binary compat going 1.8.1 to 1.8.2. I feel a bit weird calling it "breaking binary compat" because parquet-avro 1.8.2 relies on a new public method in parquet-column 1.8.2, and thus cannot be linked to parquet-column 1.8.1. Also, it is an interface that is logically wholly contained inside of parquet (see below). shrug I don't fault the parquet folks—this is fairly reasonable behavior—but there's a dependency management story between Parquet and Spark and Avro that people haven't really thought through.
We've depended on a higher version of Avro for a while. The one thing this seems to break is persisting the sorted partition map to disk; otherwise this seems to work OK. I'm not 100% sure how we're getting away with this, but, we have been.
Arguably, the least bad solution to all of the above problems is to relocate both Parquet and Avro in a shaded JAR before building adam-core; then we don't have the dependency version mismatches in test scope (this is bad, right?). Again, this is a pretty bad "least bad" solution, but I digress. However, if you try to do this, you need to relocate both parquet-avro (and it's transitive dependencies) and parquet-scala. However, relocating parquet-scala appears to break the org.apache.parquet.filter2.dsl.Dsl companion object link, which means that you can't create predicates.

WRT the last point, we wind up relocating parquet in the shaded überjar, which is probably a bad thing for people who are using just adam-core, or alternatively, a bad thing for people who are using the adam-assembly überjar.
Here's the parquet binary compat issue. Parquet 1.8.2 relies on a method that's not present in Parquet 1.8.1:
java.lang.NoSuchMethodError: org.apache.parquet.io.api.Binary.fromCharSequence(Ljava/lang/CharSequence;)Lorg/apache/parquet/io/api/Binary;
 at org.apache.parquet.avro.AvroWriteSupport.fromAvroString(AvroWriteSupport.java:367)
 at org.apache.parquet.avro.AvroWriteSupport.writeValueWithoutConversion(AvroWriteSupport.java:342)
 at org.apache.parquet.avro.AvroWriteSupport.writeValue(AvroWriteSupport.java:274)
 at org.apache.parquet.avro.AvroWriteSupport.writeRecordFields(AvroWriteSupport.java:187)
 at org.apache.parquet.avro.AvroWriteSupport.write(AvroWriteSupport.java:161)
 at org.apache.parquet.hadoop.InternalParquetRecordWriter.write(InternalParquetRecordWriter.java:121)
 at

Closing in favor of #1722


fixing bugs

In the output table it was showing attribute error as "country does not contain city attribute" whenever the object name was clicked. FIXED NOW.

backward relation issue


Readme.me Demo video is not working

Tried to access the demo video of the HMS project. The demo video was not found.
Recommend fixing it ASAP

Sorry for the late reply. Actually, I wasn't able to record the video for some of my personal issues. However, I will record the video soon and share it first with you. I promise. 🤞


airflow scheduler process and web server runs on separate containers

for https://github.com/datagovsg/airflow-pipeline/issues/3


Fix issues with NPL unit tests

The unit tests were fundamentally broken: they were not independent from
each other and assumed a specific execution. It was not possible to run
a single unit test in isolation with the others. The tests were also
modifying the environment, with no cleanup logic.
This commit also tries to improve readability of the tests and reduce
their verbosity.

See discussion in https://github.com/vmware-tanzu/antrea/pull/1814#discussion_r570737994

Codecov Report

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

@@           Coverage Diff           @@
##             main    #1826   +/-   ##
=======================================
  Coverage        ?   42.89%
=======================================
  Files           ?      111
  Lines           ?    13651
  Branches        ?        0
=======================================
  Hits            ?     5856
  Misses          ?     7300
  Partials        ?      495

Flag
Coverage Δ

unit-tests
42.89% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

/test-all


The webpage displays "404 Not Found" after deploying a .NET 5 project to a Linux Function App created with .NET 5 and Consumption hosting plan

OS: All
Build Version: 20210304.14
Repro Steps:

Create a Linux Function App with .NET 5 and Consumption hosting plan.
Deploy a .NET 5 project to the Linux Function App -> Expand the function app -> Right click the function "HttpTriggerCSharp1" -> Select "Copy Function Url".
Add &name=friend to the end of the URL and paste it in browser.
Check whether open the webpage successfully.

Expect:
Open the webpage successfully.
Actual:
The webpage diaplays "404 Not Found".

 You can ignore this scenario for now and I'll update this thread when I have a region that works

This has since rolled out to other regions and no longer repros for me


Android Studio building Error

Required Info

Camera Model
{ZR300  }

Firmware Version

Operating System & Version
Ubuntu 16

Kernel Version (Linux Only)
4.14.13)

Platform
Android

SDK Version
2.11.1

<While following the instructions here, getting the following runtime error
org.gradle.internal.UncheckedException: Build command failed.

I changed my NDK TO 16Bb and this fix the problem. Hope somebody can explain why?

I cahnged my NDK from 17 to 16b and this fix the problem. Hope somebody can explain me why

It is most likely the same issue as #1776, we will try to add switch to support both

[Realsense Customer Engineering Team Comment]
@fotsing365 Is the issue resolved?

Hi  Excuse me .I have had fixed this error just by adding     #include   in the native-lib.cpp it seems like you have forgotten.


[MM-30595] Add support for relative icon path to bindings and forms

Summary
With this PR apps can define Icon for both bindings and forms using a relative path.
Please note that no validation of the asset is done due to performance concerns. Invalid icon with show as invalid in the UI. Only malformed path containing e.g. /../ are logged and ignored.
Tested with hello-world app.
Ticket Link
https://mattermost.atlassian.net/browse/MM-30595

Codecov Report

Merging #197 (40c5c19) into master (cb322d1) will increase coverage by 0.94%.
The diff coverage is 48.71%.

@@            Coverage Diff             @@
##           master     #197      +/-   ##
==========================================
+ Coverage   24.19%   25.14%   +0.94%
==========================================
  Files          33       33
  Lines        1554     1555       +1
==========================================
+ Hits          376      391      +15
+ Misses       1149     1131      -18
- Partials       29       33       +4

Impacted Files
Coverage Δ

server/proxy/expand.go
10.90% <0.00%> (ø)

server/proxy/install.go
0.00% <0.00%> (ø)

server/proxy/proxy.go
23.89% <40.00%> (+1.67%)
:arrow_up:

server/proxy/bindings.go
80.43% <50.00%> (-2.90%)
:arrow_down:

server/utils/path.go
69.23% <69.23%> (ø)

server/httpin/gateway/oauth2.go

server/httpin/gateway/gateway.go

server/httpin/gateway/webhook.go

server/utils/errors.go
40.00% <0.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

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

Docs PR: https://github.com/mattermost/mattermost-developer-documentation/pull/840

@DHaussermann QA review for a downstream PR was done by @jfrerich in https://github.com/mattermost/mattermost-app-zendesk/pull/60#issuecomment-853968843. Do you still want to test this?


tinycc: fix build on x86_64-darwin

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] 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.11 Release Notes (or backporting 23.11 and 24.05 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.

tcc or tinycc?

Result of nixpkgs-review pr 315922 run on x86_64-darwin 1

4 packages built:

nrpl
tinycc
tinycc.info
tinycc.man

Result of nixpkgs-review pr 315922 run on aarch64-darwin 1

4 packages marked as broken and skipped:

nrpl
tinycc
tinycc.info
tinycc.man

We could possibly bump the package to see if things change. 0.9.27-unstable-2022-07-15 also looks a bit old.

That's a possibility, @wegank, thanks for the suggestion. Personally I see too little value it in and think the trade-off between unstable support on darwin vs. stable version without support on darwin isn't worth it.

I have tried but failed miserably.


Include reset_default_graph in the public API

ops.reset_default_graph is a very useful function that resets the current graph. It's particularly important in interactive sessions where loading data and setting up the kernel may take a long time, and having to restart the kernel every time one wants to start over is a hassle.

Derek, I think you looked at this last, feel free to reassign back to me if you got too much on your plate


Qt5: qtdeclarative pkg-config missing an include path

Issue description
The pkg-config Cflags for qtdeclarative is missing -I${includedir}. It only has -I${includedir}/QtQuick. It appears that conventionally both of these paths appear in the include path, so that people write code like:
#include <QQmlParserStatus>
#include <QtQml/QQmlParserStatus>

where they can choose to put the "package" name in the include path.
qtbase already allows for this. The same problem may apply to all the other qt packages.
Steps to reproduce
Note the Cflags in both files below:
➜  cat /nix/store/g6mfmwspn1n5gcryar0b8401fq6livsc-qtdeclarative-5.11.1-dev/lib/pkgconfig/Qt5Quick.pc
prefix=/nix/store/fsr4yhp9ks67bdrl24g34bh7vhvxv6a4-qtdeclarative-5.11.1
exec_prefix=/nix/store/lvxw5wal0flf1s1iqmrrnw33h6g7llky-qtdeclarative-5.11.1-bin
libdir=${prefix}/lib
includedir=/nix/store/g6mfmwspn1n5gcryar0b8401fq6livsc-qtdeclarative-5.11.1-dev/include

Name: Qt5 Quick
Description: Qt Quick module
Version: 5.11.1
Libs: -lQt5Quick
Cflags: -DQT_QUICK_LIB -I${includedir}/QtQuick
Requires: Qt5Core Qt5Gui Qt5Qml

➜  cat /nix/store/x2bdpznvin39baq9wif47ajcgf8in05w-qtbase-5.11.1-dev/lib/pkgconfig/Qt5Core.pc
prefix=/nix/store/azldmypwnamkxnm8hdggsf515i8x8b47-qtbase-5.11.1
exec_prefix=${prefix}
libdir=${prefix}/lib
includedir=/nix/store/x2bdpznvin39baq9wif47ajcgf8in05w-qtbase-5.11.1-dev/include

host_bins=/nix/store/x2bdpznvin39baq9wif47ajcgf8in05w-qtbase-5.11.1-dev/bin
qt_config=shared release c++11 c++14 c++1z concurrent dbus reduce_exports release_tools stl properties animation textcodec big_codecs codecs textdate datestring doubleconversion filesystemiterator filesystemwatcher gestures itemmodel proxymodel identityproxymodel library mimetype process statemachine regularexpression settings sharedmemory sortfilterproxymodel stringlistmodel systemsemaphore temporaryfile translation xmlstream xmlstreamreader xmlstreamwriter

Name: Qt5 Core
Description: Qt Core module
Version: 5.11.1
Libs: -L${libdir} -lQt5Core
Cflags: -DQT_CORE_LIB -I${includedir}/QtCore -I${includedir}

Technical details

system: "x86_64-darwin"
host os: Darwin 18.2.0, macOS 10.14.1
multi-user?: no
sandbox: no
version: nix-env (Nix) 2.1.3
channels(lukeworth): "nixpkgs-19.03pre161900.61c3169a0e1"
nixpkgs: /Users/lukeworth/.nix-defexpr/channels/nixpkgs

I ran into this problem as well while moc-ing.
Note that the Qt Headers themselves mainly use the include form <QTMODULE/QTHEADER> so Qt itself expects the include path $prefix/include.
Is this an upstream issue?

Yeah, this looks like boog – Arch package has -I${includedir} in the .pc files and it does not look like they do anything special.

Looking at https://archive.archlinux.org/packages/q/qt5-declarative/, the key is present even in 5.12.4 so we must be breaking it somewhere.

CentOS 8 also adds -I{includedir} (using Qt-base as an example here).

Likely caused by this line: https://github.com/qt/qtbase/blob/b4e17a48646a1d2156b7d56ab6003db46af79cec/qmake/generators/makefile.cpp#L3391-L3392

@jtojnar: Do you think we can build Qt differently so that the .pc-files are generated correctly?
It's not clear to me how the files are created.

So when the ¿nixpkgs’s cc-wrapper passes -isystem ${dev}/include to the compiler? (I thought it only does this for dependencies, maybe it comes from other place), Qt marks it as a system include path:
https://github.com/qt/qtbase/blob/3b4211ec47c98c09e2b96c77df1f8f0833c92793/mkspecs/features/toolchain.prf#L77-L82
and qmake’s pkg-config generator considers it unnecessary to add to the .pc file since it will be available anyway:
https://github.com/qt/qtbase/blob/b4e17a48646a1d2156b7d56ab6003db46af79cec/qmake/generators/makefile.cpp#L3391-L3392
And it is in fact right, the cc-wrapper will add -isystem ${dev}/include
https://github.com/NixOS/nixpkgs/blob/f7ac956a2b5b8c7f3a50c63547af493c68372169/pkgs/build-support/cc-wrapper/setup-hook.sh#L71-L73
so C/C++ compilers should have no problem finding the headers.

Confirmed using the patch below that cc-wrapper only includes the dependency include paths, not qtsvg’s own include path so I am still not sure how it gets into QMAKE_DEFAULT_INCDIRS.
--- a/pkgs/development/libraries/qt-5/qtModule.nix
+++ b/pkgs/development/libraries/qt-5/qtModule.nix
@@ -33,6 +33,7 @@ mkDerivation (args // {

     fixQtBuiltinPaths . '*.pr?'
   '';
+  preBuild = ''echo $NIX_CFLAGS_COMPILE; die'';

   postFixup = ''
     if [ -d "''${!outputDev}/lib/pkgconfig" ]; then

@jtojnar: Do you think we can build Qt differently so that the .pc-files are generated correctly?
It's not clear to me how the files are created.

There are two things I do not understand:

How does the ${qtsvg}/dev get into the QMAKE_DEFAULT_INCDIRS variable when building qtsvg? (Assuming, I diagnosed the correct qmake line, maybe try patching the line to run unconditionally to verify.)
What causes a problem for you. The cc-wrapper make sure the includedir is visible to the compiler, even when -I ${includedir} is omitted from the .pc file (or there is no .pc file at all). Does MOC use something else than the compiler from $CXX? What is the error message?

I am not familiar with Qt at all so for further debugging, someone like @ttuegel will be needed.

What causes a problem for you.

The moc-compiler has its own parser et.c. so is completely independent from $CXX AFAIK. What we do is to pass all include flags explicitly, as found using pkg-config. Which works on CentOS but not in Nix.
Actually, this applies in general for us as our internal packages are quite big, so we want to cherry-pick from buildInputs using things like pkg-config only the necessary bits for each library. I haven't managed (yet) to provide an unwrapped gcc with a standard environment, but that's the goal.

Actually, this seems to work (at least in terms of adding the missing include path, I haven't tested it more):
diff --git a/pkgs/development/libraries/qt-5/modules/qttools.nix b/pkgs/development/libraries/qt-5/modules/qttools.nix
index 573472a8b5a..9a30ca3c845 100644
--- a/pkgs/development/libraries/qt-5/modules/qttools.nix
+++ b/pkgs/development/libraries/qt-5/modules/qttools.nix
@@ -13,6 +13,7 @@ qtModule {
         -e '/^cmake_linguist_config_version_file.input =/ s|$$\[QT_HOST_DATA.*\]|${getDev qtbase}|'
   '';

+  qmakeFlags = [ "QMAKE_DEFAULT_INCDIRS=" ];
   devTools = [
     "bin/qcollectiongenerator"
     "bin/linguist"

As @jtojnar discovered, this is caused by the lack of a unified system include path in Nixpkgs. We could try to patch that statement so that -I${includedir} is added unconditionally; I doubt it would hurt anything.

@ttuegel: I'll update #86317 to patch makefile.cpp instead, ok?

@xbreak Sounds great, thanks!

@lrworth: Did you ever try the fix from #86317?

@xbreak Thanks for following up on this :) Unfortunately (fortunately?) I no longer work on Qt applications so I haven't needed to address this.

@lrworth, this was likely fixed in #86317, unless you disagree I think you can close this ticket.

Thanks 😃


Implementation of stock inventory

The implementation is as follows:

Count is maintained, corresponding to each item.
The product is added to basket only if it's available, otherwise an error stating "Stock Out" is shown.
The product quantity is decreased when the user checks out successfully.

Also, few frontend tests are removed as they are no longer required(due to change in the behaviour of error in this PR).

Hi @agrawalarpit14, I didn't check the code yet, but I saw two API tests failing: https://travis-ci.org/bkimminich/juice-shop/jobs/532976262
Unfortunately they are always ahowing green on Travis at the moment, a problem we had before and thought fixed, but it seems to be back. So please always check the result of Integration stage manually, ok? Thanks!

Hi @agrawalarpit14, I didn't check the code yet, but I saw two API tests failing: https://travis-ci.org/bkimminich/juice-shop/jobs/532976262
Unfortunately they are always ahowing green on Travis at the moment, a problem we had before and thought fixed, but it seems to be back. So please always check the result of Integration stage manually, ok? Thanks!

Sure, I will manually check the logs and fix this. Thank You for your feedback.😁😆

Adding feature without adding e2e and api tests for the new features isn't good. 😕
Would be cool if you could add some before we merge this PR.

Sure @J12934. I will update tests and all the points in your review.
Thank you for your feedback.😁😁

Adding feature without adding e2e and api tests for the new features isn't good. 😕
Would be cool if you could add some before we merge this PR.

Hi!! @J12934. I have tried to make the code better and also added tests. Please let me know your feedback and also if I am missing any tests that have a need to be added.
Thank You!!😁✌🏻

To be fair, existing e2e tests also do not cover any functionality that is not needed while solving a challenge. Functional testing is currently only located in unit and integration tests.

Hi @J12934 and @bkimminich. Then should we start to write e2e tests for functional testing as well. And also, make boosting coverage a milestone(for unit tests at min, I am adding output of coverage summary for quick reference below).
npm test
=============================== Coverage summary ===============================
Statements   : 24.88% ( 356/1431 )
Branches     : 26.93% ( 220/817 )
Functions    : 20.68% ( 67/324 )
Lines        : 24.8% ( 343/1383 )
================================================================================

npm run frisby
=============================== Coverage summary ===============================
Statements   : 77.5% ( 1109/1431 )
Branches     : 67.56% ( 552/817 )
Functions    : 73.77% ( 239/324 )
Lines        : 77.66% ( 1074/1383 )
================================================================================

To be fair, existing e2e tests also do not cover any functionality that is not needed while solving a challenge. Functional testing is currently only located in unit and integration tests.

Oh right good point, forgot about that 😅

Hi @J12934. I have followed all the points and updated the PR. Although, I still found the need to use let result = utils.parseJsonCustom(req.rawBody) as for the particular query used to solve the challenge, req.body.<property> turns out to be undefined, otherwise.
Please let me know your feedback.
Thank You!!😁😁

Hi @J12934. I have followed all the points and updated the PR. Although, I still found the need to use let result = utils.parseJsonCustom(req.rawBody) as for the particular query used to solve the challenge, req.body.<property> turns out to be undefined, otherwise.
Please let me know your feedback.
Thank You!!😁😁

Okay not worries.
You can see what i meant in Commit: https://github.com/bkimminich/juice-shop/pull/982/commits/1712ca7a0f31222627393bb7f0b5c606042b187b
Did some other smaller cleanups. See the other commits. Sorry for the force pushing I had some weird char slipping in the commit message, don't know how that happened.

Hi @J12934. Thanks for the help. I tried the change done by you in the commit 1712ca7 but a test was failing. Now, I understand it was because of wrong content type.😅
But in your commit, you changed describe --> fdescribe. This is unintended ryt, shall I modify?
Thank You!! very much😁😁

Hi @J12934. Thanks for the help. I tried the change done by you in the commit 1712ca7 but a test was failing. Now, I understand it was because of wrong content type.😅
But in your commit, you changed describe --> fdescribe(I got to learn a new thing, I used to comment all other tests to run only one😅). This is unintended ryt, shall I modify?
Thank You!! very much😁😁

Oh good catch. Should have looked at the diff before commiting.
Thanks for catching and fixing it 👍


add PHOSPHO feature meta

ACETYL, PHOSPHO, PROT: mawg-data/pass1b-06/prot-*/mapping/*feature-mapping*
UBIQ: mawg-data/pass1b-06/prot-ub/data/*feature-annot*

ACETYL and PROT are just gene ID info

UBIQ should be added and has consistent formatting. PHOSPHO should be added but is missing site and ascore for some tissues

also added TRNSCRPT feature annotation. see *_FEATURE_ANNOT


[Dev] GetBittr: Change the email verification URL from GetBittr

The email verification URL should be changed to Hexa Wallet format.
https://hexawallet.io/app/*

Closing. Not required anymore.


[Enhancement] Allow filtering by year (in addition to title)

In some cases the search by title yields many results and it is difficult to find the movie you are looking for. As an example the movie "Identity" from 2003.
It would be interesting to be able to filter also by year in the same way as in TMDB using y:xxxx. So to search for this movie it would be Identity y:2003.

Hey @simonbcn, cool idea, I'm sure we could add a few of these filtering options to help out with searches. Thanks for making this issue!


Girl panel fix

Almost everything should be working fine on mobile now, functionality wise.
There is a slight z-index issue on hifumi's (long) descriptions. Not entirely sure if we should completely make it not overlap with the images or fix the readability issue in some other way.
We should definitely be changing the colors of some of these panels though

The lighting for the blue-haired girl's image from the anime is making it look like trash, maybe we should change the color for that one while we're at ui changes.

The lighting for the blue-haired girl's image from the anime is making it look like trash, maybe we should change the color for that one while we're at ui changes.

That was kind of a meme by @Shensd so you might want to ask him to update, not sure where he got that from

yeah, fair enough w
so whos gonna merge from master

yeah, fair enough w
so whos gonna merge from master

someone probably

woosh

this is something
i can do```

||another thing||


RDART-1016: Cleanup iOS podspec

Had a fruitful discussion with @tgoyne
This PR removes some cruft from our ios podspec pod_target_xcconfig
In particular 'VERSIONING_SYSTEM' => 'apple-generic'.
This will cause a realm_privacy_vers.c file to be formed and hence an exe to be build, which will cause trouble on app store connect.
Fixes: #1656

Nice, should we do something similar for the JS podspec? cc @kneth


The problem about the train loss can't converge

Thank you for your work！I want to try to train your code. In the process of trying, I trained one scene data from the  3DMatch‘  preprocessed data, but after iterating many times, I found  the loss could not converge(exactly ，it has been stuck around 2.0), how did you deal with this problem? Or, have you encountered such a problem? thank you for your reply！

My training on 3DMatch also stuck around 2.0-1.9. How did you resolve it?


Different behaviour when invoking .py script as symlink

When calling a Python script via its shebang line, the following part in the python shim kicks in:
  if [ -f "$arg" ]; then
    export PYENV_DIR="${arg%/*}"
    break
  fi

However, that should resolve symlinks probably:
    arg=$(readlink -f $arg)

Otherwise calling it via a symlink from e.g. ~/bin pyenv-version-file will not pick up a .python-version file from the final destination, but only from ~/bin.
The current behaviour could be seen as a feature: by using symlinks you could have different Python versions (depending on where the symlink's file is), but I think it makes more sense to use the real script's dir.
btw: this code currently does not handle python2/python3 in the shebang line properly (https://github.com/yyuu/pyenv/pull/379) - I will re-open that PR.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/23940780-different-behaviour-when-invoking-py-script-as-symlink?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github).

I've added a proposed fix for this to #379: https://github.com/blueyed/pyenv/commit/dab47426519ac48900c80fc9de8751286a02cfe8

If that's the way to go there should be some test for this then.

Thanks for reporting. Please provide me some minimum script to reproduce the issue (or, test case) if you're available.

Create a test.py file that you call then with the full path or it's symlink,
with a local version at the symlink target and symlink's place:
% cd /tmp
% cat > test.py
#!/usr/bin/env python
import sys

print(sys.version_info)

% chmod +x test.py
% pyenv local 2.7.10

% cd ~/tmp
% pyenv local 3.4.3

% /tmp/test.py
sys.version_info(major=2, minor=7, micro=10, releaselevel='final', serial=0)

% ln -s /tmp/test.py
% ./test.py
sys.version_info(major=3, minor=4, micro=3, releaselevel='final', serial=0)


Edit project setup

Changes:

Update .gitignore
Add .classpath to remove bin folder from regenerating
Add default application.properties

Closed to rename commits


when host is only used for gateway it's showing "No Access" label in green color

Environment info

Version: 1.12
Deployment: AZURE|ESX|AWS|GCLOUD|DEV|VBOX
Customer: NAME

Actual behavior

when host is only used for gateway it's showing "No Access" label in green color

Expected behavior

When a node has only S3 gate the access should be "No access- Used as S3 gateway only"

Steps to reproduce

deactivate storage and enable s3

Screenshots or Logs or other output that would be helpful

 Standalone endpoints

Relates to #5825 5825

 Endpoint UI/UX


Add callout for clearing spec.serviceAccount alias from workload templates

This concern around how to remove a service account from a specified workload template has been raised in a number of issues and is currently not mentioned in the documentation. See the following discussions:

https://github.com/kubernetes/kubernetes/issues/72519#issuecomment-451292986
https://github.com/argoproj/argo-cd/issues/7645#issuecomment-1175071814
https://github.com/helm/helm/issues/10183#issue-1006705241

The API documentation for this serviceAccount field calls it a deprecated alias, but does not call out the need to remove the alias to undo this field value:
   serviceAccount	<string>
     DeprecatedServiceAccount is a depreciated alias for ServiceAccountName.
     Deprecated: Use serviceAccountName instead.

This PR would update the documentation to provide some assistance to users when attempting to remove the serviceAccountName field from a workload.

/assign @kcmartin

Reviewers / approvers: if this PR doesn't progress, I recommend merging it as-is and then logging a “good first issue” issue with clear instructions about how to fix the spelling error and sort the wrapping.

Getting to the feedback today

If this PR doesn't progress, I recommend merging it as-is and then logging a “good first issue” issue with
clear instructions about how to fix the spelling error and sort the wrapping.

This PR is simple and straightforward. It is only adding a callout. I'd insist we merge new contents when they are ready.
In the comment I provided, I showed the author how to revise the proposed text.
As a side note, what is the benefit to merge a simple change like this in two PRs? (one for adding text, the other
one to fix typo and line wrapping).
We have seen too many times an author says that he/she will log an issue and fix an obvious defect in his/her PR,
and then that amendment PR is never proposed?

@tengqm could you trigger a retest, looks like some external issues occurred during the test run

/ok-to-test

/retest

I am unable to trigger a test. Maybe the author has to do another commit? There are two commits in this PR. It would be desirable to squash them anyway.

I agree - please squash commits if you know how @jmcshane (it's OK to say that you don't)

Rebased and pushed

ok, rebased to a single commit


Feat: onchain impacts and proof generation

Centralize the creation of the proof in the X2EarnRewardsPool contract. Apps now only need to pass:

proof types (link, image, video, text)
proof data (the URL to the proof)
the impacts
description of the action

This will allow easier integration from apps and fewer errors, and it will open up the possibility of using impacts to do calculations.
A new version of the proof is created now, and indexers will need to align (by checking the version number, if no version is present then it should be treated as version 1):
{
   version: 2,
   description: 'The description of the action',
   proof: { image: 'https://image.png', link: 'https://twitter.com/tweet/1' },
   impact: { carbon: 100, water: 200 }
}

The new function to call is called distributeRewardWithProof().
The original distributeReward() function will now only distribute the reward without emitting any proof (the proof param was deprecated, but left there for retro compatibility).
A new distributeRewardDeprecated can be called to distribute rewards + provide a json proof built by you, but it will removed as well in the future.
The available impacts are:
"carbon",
"water",
"energy",
"waste_mass",
"education_time",
"timber",
"plastic",
"trees_planted"

The deprecated impacts are:
waste_items
people
biodiversity

An additional buildProof() function was added allowing devs to preview what their proof will look like.
Impacts can be added or removed by an address that has the IMPACT_KEY_MANAGER_ROLE.
Proofs and Impact
      ✔ Json proof is created by the contract (1439ms)
      ✔ App can provide multiple proofs (305ms)
      ✔ App can provide only proofs without impact (296ms)
      ✔ App can provide only impact without proofs (301ms)
      ✔ If only description is passed, without proofs and impact, nothing is emitted (301ms)
      ✔ Description is not mandatory if proof or impact is passed (316ms)
      ✔ If no proof, nor impact, nor description is passed, nothing is emitted (320ms)
      ✔ If a non valid proof type is passed, it reverts (318ms)
      ✔ Only valid proofs are image, text, link, video (451ms)
      ✔ If a non valid impact type is passed, it reverts (333ms)
      ✔ If impact values length differs from codes length, it reverts (324ms)
      ✔ If proof values length differs from types length, it reverts (329ms)
      ✔ Anyone can index available impact codes (332ms)
      ✔ IMPACT_KEY_MANAGER_ROLE and DEFAULT_ADMIN can remove an impact code (347ms)
      ✔ IMPACT_KEY_MANAGER_ROLE and DEFAULT_ADMIN can add an impact code (359ms)
      ✔ Non admin users cannot add and remove impact codes (344ms)

Gas increase
Current mainnet gas usage:
distributeReward 98959
This PR:
distributeRewards 99519
distributeRewardWithProof 115531 (14.89% increase)

Codecov Report
Attention: Patch coverage is 76.96970% with 38 lines in your changes missing coverage. Please review.

Project coverage is 94.50%. Comparing base (d2eab62) to head (05f55cf).

Files with missing lines
Patch %
Lines

contracts/deprecated/V1/X2EarnRewardsPoolV1.sol
50.68%
36 Missing :warning:

contracts/X2EarnRewardsPool.sol
97.82%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   96.06%   94.50%   -1.57%
==========================================
  Files          38       39       +1
  Lines        2440     2601     +161
  Branches      515      561      +46
==========================================
+ Hits         2344     2458     +114
- Misses         95      142      +47
  Partials        1        1

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


Fix Split method Errror on Resolve-DbaNetworkName

Change from Object to DbaInstanceParameter
Added validation of object type and get the ComputerName correctly
thanks to @FriedrichWeinmann

Thanks, @ClaudioESSilva ! Since the ComputerName is cast as a dbainstanceparameter, is it possible that that gettype check will ever fail? I think it was useful when it was [object] but now that it's not generic, that check is no longer needed.


Implement remote RepositoryService supporting general process definition query.

I very much like this client, but is this project still ongoing? Sadly I am not familiar at all with Kotlin and cannot contribute.

Hi, sure... is there any feature you are missing? Just make a wish...

Hi Simon,
Wow, that is very kind of you. The use case I need to implement is to check if a certain process defitionen is deployed on the remote Camunda BPM and if not, to deploy it. That means I need to:

Find a process definition by key and version tag
Deploy process definition

Expressed in the Camunda Java API it would be something as follows:
import java.util.List;
import org.camunda.bpm.engine.RepositoryService;
import org.camunda.bpm.engine.repository.ProcessDefinition;
import lombok.RequiredArgsConstructor;

@RequiredArgsConstructor
public class ProcessDeployer {

	private final RepositoryService repositoryService;

	/**
	 * Check of the current version of myProcess.bpmn20.xml is deployed. If not, deploy it.
	 */
	public void assertProcessDeployment() {
		List<ProcessDefinition> processDefinitions = repositoryService.createProcessDefinitionQuery()
				.processDefinitionKey("myProcess").versionTag("1.0.0").list();
		if (processDefinitions.isEmpty()) {
			repositoryService.createDeployment().addClasspathResource("processes/myProcess.bpmn20.xml").deploy();
		}
	}
}

I'll split out the deployment to a separate issue.

ok, thx

Has this been implemented in v0.0.5?


[NDM] Add rawId/rawIdType to agent payload, omit empty

What does this PR do?
Adds new fields to the interface metadata payload to keep consistency with the server representation of interface metadata.

Motivation
Keep consistency with the back end

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Double check that these fields aren't getting used and interfaces still show up properly in the Datadog UI.

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge

/merge -c

/merge

/merge


Reduce Embedding size

I'm trying to replicate this example of langchain. I'm using ElasticSearch as the database to store the embedding. In the given example I have replaced embeddings = OpenAIEmbeddings() with oembed = OllamaEmbeddings(model="llama2") which one can import from langchain.embeddings import OllamaEmbeddings. I'm running Ollama locally. But, I'm running into below error:
raise HTTP_EXCEPTIONS.get(status_code, TransportError)(
elasticsearch.exceptions.RequestError: RequestError(400, 'mapper_parsing_exception', 'The number of dimensions for field [vector] should be in the range [1, 2048] but was [4096]')

The Ollama model always create the embedding of size 4096 even when I sat the chunk size of 500. Is there any way to reduce the size of embedding?

Hi @Mohit0928 the output size of the embedding is determined based on how the model was trained rather than the size of the input, it is a constant. The way to deal with this normally is to use a different model. Ollama doesn't have any embedding specific models in its library at the moment though, so I can't make a great recommendation on a good one to use.


New IMU API angular velocity wraps around

I have an op mode that essentially calls imu.getRobotAngularVelocity(AngleUnit.RADIANS) in a loop as voltage applied to the motors slowly ramps. Here's the plot:

I wouldn't expect the velocity here to wrap around.
I haven't had the chance to investigate in detail. I'm not sure if the issue is with the imu -> robot transform or is with the hardware (I'm actually not sure if this data is from a BNO or BHI).

Yes.  Weird that it seems to be wrapping at PI.  Might be normal for angle, but not angular velocity.

This was fixed in v10.0


Japanese input (IME) fails at the first character

Jodit Version:  3.3.7
Browser:  Chrome/IE11/FF
OS:  Windows
Expected behavior:
Display IME (Japanese) text input while typing
Actual behavior:
When I add a line the first character to type does not show IME (Japanese) text input, it only displays after I type the second character

You can see the problem when I add the 2nd and 3rd lines.

Does anyone help me solve this problem?


Update pypy to 5.1.1

thanks!
the failure is unrelated (ansible 2.1 is behaving differently for whatever reason) and I tested it independently, so we're good to go.

I'm in progress of moving to 2.1 do you know what should be converted in the role?
Looks your role is only one that allows to setup to /opt not core's home

@andypost I'm tracking this in issue #5
I think the role is fine for the most part, it's the pattern for setting the non-standard python location in the inventory that's not.


checkstyle: 8.44 -> 8.45

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/checkstyle/checkstyle/releases.
meta.description for checkstyle is: "Checks Java source against a coding standard"
meta.homepage for checkstyle is: "http://checkstyle.sourceforge.net/"
meta.changelog for checkstyle is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/dcmshsks0inzwkvqdag85xdbj2bn359k-checkstyle-8.45/bin/checkstyle passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 8.45 with grep in /nix/store/dcmshsks0inzwkvqdag85xdbj2bn359k-checkstyle-8.45

found 8.45 in filename of file in /nix/store/dcmshsks0inzwkvqdag85xdbj2bn359k-checkstyle-8.45

directory tree listing: https://gist.github.com/0c5595fe4295f8c973d314595f308ff1

du listing: https://gist.github.com/b27ba1021f1f9922e5664dadaa093b56

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
checkstyle

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dcmshsks0inzwkvqdag85xdbj2bn359k-checkstyle-8.45 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A checkstyle https://github.com/r-ryantm/nixpkgs/archive/b8f14c331176c1fde5740b29fe8a27a2957a7bb4.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dcmshsks0inzwkvqdag85xdbj2bn359k-checkstyle-8.45
ls -la /nix/store/dcmshsks0inzwkvqdag85xdbj2bn359k-checkstyle-8.45/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

checkstyle

Maintainer pings
cc @pSub for testing.

Result of nixpkgs-review pr 132376 at b8f14c33 run on x86_64-linux 1

1 package built successfully:

checkstyle

1 suggestion:

warning: unclear-gpl
lgpl21 is a deprecated license, please check if project uses lgpl21Plus or lgpl21Only and change meta.license accordingly.
Near pkgs/development/tools/analysis/checkstyle/default.nix:33:5:
   |
33 |     license = licenses.lgpl21;
   |     ^

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

1 package built:

checkstyle


Same input gives different hashes if it's run in docker

Hello,
I have the following piece of code:
fn main() {
    let hash = argonautica::Hasher::default()
        .with_password("qwerty123")
        .with_secret_key("my_secret_that_must_be_at_least_thirty_two_bytes_long")
        .hash()
        .unwrap();
    println!("{}", hash);
}

I noticed that it prints different results when running in different environments. For instance on my machine it prints:
$argon2id$v=19$m=4096,t=192,p=8$EvpazrlY0ApjLxAXz/Xgv301w1BVvpf8iACX57If9/I$uQFyf1OfHwfuoNNt4RwR1p9Esbtqh8mfPY8B66N9rLY

But when I run it in a docker container I get
$argon2id$v=19$m=4096,t=192,p=8$na6G3tOLyjQOZLfQkNFPJagLKzNkCX1sTtn0L9TJN0s$8C0R7jRHbUrck67r0wneJxG2g2U1phUW1ObK1UNd+eY

I thought that given the same secret and input, the hash function would give the same output. Am I misunderstanding something about how to use this library?
If you need to reproduce, I set up a repo here: https://github.com/little-dude/argonautica-issue.

Oh so this is actually due to the random salt being used. Sorry for not reading the docs more carefully.


Data are far larger in V2

Hello,
I've upgraded to V2 (2021 branch) to test it. It seems messages of "max message size" length are always sent, instead of only what is necessary.
Edit : this is only the case on reception side, i.e. messages of appropriate size are sent through the network, but OnData returns a message a max message size at the reception.
BR,
Jaze

Ok, I know understand what happens. This is due to Pool allocating byte[max_message_size] arrays. This is not too bad for a few messages due to the reuse system of the Pool class, however if a burst of messages happens, a lot of bytes are allocated and stay in the pool indefinitely for nothing.

This is definitely a problem in our and many other use cases.
We run a server with 250+ players at peak hours with Tons of packets actively being sent, Highest packet count we have seen at once time was about 2000 packets! with the max packet being in the MB's since the server sends Map data and everything to the client this, in theory, could allocate 20+ GB of data then just leave it in memory?
We're currently using a very old version of Telepathy back from early 2020, we're gonna upgrade anyway and for the time being remove the Pool.


[ARM] az group delete: Add new option Microsoft.Databricks/workspaces for --force-deletion-types parameter

Related command

az group delete
Description

Close: #28923
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Resource

Thanks for taking care of this, do you know when this will be released?

Official Release: 05/21/2024
Azure CLI version: 2.61.0


Splitting duplex

Duplex read ids seem to be a combination of their parents read_ids, joined by a semi colon.
So we would compare both halves of the read_id in turn to the unblocked readids hashset.
If there is a match from either we would consider that read unblocked.

Just adding a comment - really we shouldn't have any of these. If we have unblocked the first read then the second read should not be related - i.e it should not be a duplex read.
If we had not unblocked the first read we should always accept the second read.
It would be interesting to look at any reads like this that are unblocked as they would be examples of things we didn't want happening....

See https://github.com/LooseLab/readfish/pull/324 for discussion!


Disabling token endpoint security autoconfiguration in java config? (REOPENED)

I reopen this: https://github.com/spring-projects/spring-security-oauth/issues/756
as my last question is unanswered.
My point is that in AuthorizationServerConfigurer there are three responsibilities tightly bound and either you get everything or you have to do everything by hand. There's no way AFAIU to leverage the endpoints configurer and provide you own custom security config without having a unused spring-security filter chain lying around.
My changes to the security configuration are minimal:
add additional authentication filters (but having control on the ordering not only in relation to the BasicAuthenticationFilter, and AFAIU this cannot be done with AuthorizationServerSecurityConfigurer)
enable OPTIONS on the token endpoint for unauthenticated clients
add a CORS filter
I was already doing this in a separate WebSecurityConfigurerAdapter but then I found out that my config was never triggered because the default one created by AuthorizationServerConfigurer was triggered instead.
Is there a way to leverage the AuthorizationServerConfigurer for configuring the endpoints and disable the automatic security configuration?
If the answer is no, as I expect, are there plans to introduce this possibility in the future?
Thanks

@rwinch since you asked to reopen the issue, in case I thought my former question (#756) was unanswered, could you please comment?
Thanks in advance

Hi @rwinch, reviving this as I am still affected by this issue.


Does not work correctly on Windows

This package uses hardcoded forward slashes with plain string matching, mixed with path.resolve uses that will return backslashes on Windows, thus imports do not resolve correctly.
It works correctly if ran via WSL on Windows.
Recommend adding this to the README?

Windows can cope with forward slashes. The only place where that doesn't work is in a terminal, because forward slashes are used a terminal command parameters.
And even a mix style (foward and back slash) shouldn't cause problems. What exactly are you seeing?

If I had to guess, it's this issue that I'm seeing as well.
public static fromFile = (source: string, target: string, packageRoot: string,
        replacements?: Map<RegExp, string>): PackageSource => {
        // Construct a package name for lookup from the given paths.
        if (!source.startsWith(packageRoot)) {
            throw new Error("The full path must specify a file within the given package root.");
        }

The source string and package root string might not have consistent slash direction on windows, so the startsWith check always fails for me. Haven't been able to verify, but that's what I'm suspicious of right now.


Why are the hash of crx files are different using the same private key

I'm packing a directory using the same private key twice, but two output files have the different hash. However, packing crx in Chrome will generate two identical crx. No matter which packing methods I choose, those crx are all working as expected but I'd like to know the reason for the different hash.
crx pack src -p key.pem -o src1.crx
crx pack src -p key.pem -o src2.crx
md5sum src1.crx src2.crx

Cheers

Good question!
I suspect a time based metadata changes  somewhere but I can be wrong.


tenant_route method does not use the correct domain

Describe the bug
When I manually initialize tenancy, the tenant_route() method does use the tenant domain. Instead, the route is generated by the global APP_DOMAIN environment variable.
Steps to reproduce

Manually initialize tenancy in tinker
Use tenant_route() to generate a route

Expected behavior
The correct tenant domain should be used to generate the url.
Your setup

Laravel version: 6.9.0
stancl/tenancy version: 2.2.4

tenant_route() is not meant to be used with tenancy initialization. It's to get a route with tenant domain name from central context.
Your tenants can have an unlimited amount of domains. How would the helper know which one to use?

Hmm, I see what you mean. Seems like there is no way to implement my expected behaviour. Thank you anyway!

There definitely is. Tell me where & how you're initializing tenancy and what you need the route for.

I am generating QR codes in an application based on the tenant url. This works perfectly fine using the tenant_route() method in a controller. Tenancy gets initialized using the domain and just works.
Now I want to generate a code programmatically. Therefore I wanted to manually initialize tenancy. My code look like this.
$tenant = tenancy()->all()->first();
tenancy()->initializeTenancy($tenant);

QrCodeGenerator::format('png')
            ->size(250)
            ->generate(tenant_route('qrCode.redirect', $id);

Does this help you?

First of all I think you don't need to initialize tenancy for this unless you're also persisting the data into tenant storage. In which case, I suggest using
$tenant->run(function ($tenant) {
    // runs inside that tenant's environment
});

instead of manually initializing tenancy.
If you only use one domain for your tenants, you could do something like tenant_route('qrCode.redirect', $id, $tenant->domains[0]).

If you only use one domain for your tenants, you could do something like tenant_route('qrCode.redirect', $id, $tenant->domains[0]).

Yes, I use only one domain. I think this works for me. Thank you!

You're welcome :)


update booster parent and Swarm to latest releases

This commit also removes explicit configuration of the health check
enricher, because the default configuration (targetting /health)
is more appropriate.

Thanks @mkouba, I pushed one more change, but I promise that's all :-)

Reverted that change as discussed on IRC :-)


Setup github actions to automatically build package on tagged commit

Remind me guys, remind me...
Notes:
Reference and example info: https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#creating-a-workflow-definition
Keep in mind: Replace pep517 approach with default one
Commands i'm too lazy to finally memorize...
sudo bash -cl "/home/nameless/Work/Development/OSS/HiddenEyeReborn/venv/bin/python /home/nameless/Work/Development/OSS/HiddenEyeReborn/setup.py sdist bdist_wheel"
======================================
twine upload dist/*
#REMEMBER
On ArchLinux you need to use sudo pip when installing (Probably, gotta do more tests)

el ejecutable .py solo dice unas lineas de agradecimiento , no hace nada, ?que tipo de cosa es esta ? ... no hay manera de usar.,

@Blacksorceres English only please

when opening it only says a few words of thanks it does not work you can correct it

That's because they're still working on the project

thanks friend I didn't know

Thank you


(fix): Fixed bugs in Row Detail feature  when virtual scrolling is not set

What kind of change does this PR introduce? (check one with "x")

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
#210
What is the new behavior?
Row height cache is only initialized when virtual scrolling is enabled.   In all other scenarios row calculations are automatically done.   Also takes this takes care of the bug mentioned in pull request #208.
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
…t present.

Awesome!


Wrong documentation for http_sd_config / authorization / type

What did you do?
Configured http_sd_config with Bearer authorization type. Didn't specify authorization.type since docs say it defaults to Bearer. The Authorization header value is missing the type; it contains only the authorization.credentials string.
Manually adding authorization.type: Bearer works.
What did you expect to see?
List of discovered targets.
What did you see instead? Under which circumstances?
No targets and HTTP 401 in server logs.
System information
Linux 6.2.0-1010-aws aarch64
Prometheus version
prometheus, version 2.46.0 (branch: HEAD, revision: cbb69e51423565ec40f46e74f4ff2dbb3b7fb4f0)
  build user:       root@42454fc0f41e
  build date:       20230725-12:37:33
  go version:       go1.20.6
  platform:         linux/arm64
  tags:             netgo,builtinassets,stringlabels

Prometheus configuration file
- job_name: gate-icmp
  http_sd_configs:
  - authorization:
      credentials: super_secret_token
    refresh_interval: 3600s
    url: https://some.protected.url.com/prom_sd

Alertmanager version
n/a

Alertmanager configuration file
n/a

Logs
prometheus[5970]: ts=2023-08-28T14:31:06.951Z caller=refresh.go:80 level=error component="discovery manager scrape" discovery=http config=gate-icmp msg="Unable to refresh target groups" err="server returned HTTP status 401 Unauthorized"

the documentation is correct, it is a bug

#12785


Determine whether COVIDCast jhu-csse adequately represents the state data used by Reich

Ok, so I'm still not sure what the right answer is then. We want to predict the "truth". If the truth is XX000, then great. But if XX000 = JHU's province_state, and we don't have JHU's province_state signal, then we need a fix. I don't believe that we actually need the bins separately. (@bnaras or @capolitsch can be more definitive)

[...] long term, wrapped up in some of the anomaly detection or data checking, we should make sure that our truth and their truth is the same (unless Delphi doesn't believe their truth)

Originally posted by @dajmcdon in https://github.com/cmu-delphi/covidcast-indicators/pull/328#issuecomment-713782551

@dajmcdon Just want to clarify that regardless of how we solve the JHU Out of State and Unassigned state signal binning, our state geo level signal should match the Reich Lab's state geo level signal. Our county level XX000 bin is essentially a granular "probably and miscellaneous" counts bin. But in terms reproducing truth, our JHU state signal should be identical to Reich Lab's. We can double check this once JHU is healthy again.


Why define an exception handler needed async?

with tests/test_exceptions_handler.py define an exception handler like this:

@exception_handler_app.exception(NotFound, ServerError)
def handler_exception(request, exception):
return text("OK")

but in docs https://sanic.readthedocs.io/en/latest/sanic/exceptions.html

@app.exception(NotFound)
async def ignore_404s(request, exception):
return text("Yep, I totally found the page: {}".format(request.url))

what is the difference? And is async def needed?

In general all handlers in Sanic can be async or normal functions. You are free to use either even though in documentation async def is generally preferred even if the function doesn't need to be async.
In the current version there is a limitation that async error handlers might not work in some contexts (protocol errors), so a normal function is actually a safer choice there. This is due to be fixed in a future version.

thx~I do meet unexcepted exception with async def in exceptions handler. And it works good with def only.

@matianjun1
Yes, this issue has come up a few times. The documentation needs to be changed.
The confusion comes from the fact Sanic request handler does support async exception handlers, see here: https://github.com/huge-success/sanic/blob/60b4efad67ba3b22dfaf83820c772cd7f5ff137c/sanic/app.py#L1015
But the sanic asyncio server implementation does not support async exception handlers.
https://github.com/huge-success/sanic/blob/60b4efad67ba3b22dfaf83820c772cd7f5ff137c/sanic/server.py#L577
So I think for now we should remove any mention of async exception handlers in the documentation, and look at how we can get async exception handlers working at the asyncio server level.

Agreed, it would be best not to mention async exception handlers in documentation for now. This is one of the problems fixed in #1791 but it will take a few more months until that can ship, and there is no quick and easy way to fix this otherwise.

Is is just the docs at https://sanic.readthedocs.io/en/latest/sanic/exceptions.html that show an async error handler? Are there any other mentions anywhere else that need changing?


Datepicker not working

Hi guys,
Having this problem when trying to add the datepicker or datepickertime to widget.xml
"Only 'data' node can be child of 'block' node, #comment found";i:1;s:11425:"#0"

did you use this format? https://github.com/inviqa/mx-widgetcomponent#date-picker-1

Yess, I got it working now. Just a question, I changed the dateformat to d-m-Y and I can add the date correctly to the widget, but when I edit it the month is always 0.
So if I set the date as 3rd of November (3-11-2017) and insert the widget, when I edit it shows as (3-0-2017)

@SamiAssasi Hi, Sorry I didn't notice your comment. As far as I know Magento2 uses the IntlDateFormatter, where "m" is the minute. So you need to use "d-M-Y" to get "3-11-2017". (see http://userguide.icu-project.org/formatparse/datetime). This is my guess.

This issue should be fixed in https://github.com/inviqa/mx-widgetcomponent/releases/tag/v2.2.1


SubmissionConfigReader and DCInputsReader refactoring

The reading of the submission form configuration files is not managed centrally using specific Spring beans but with classes (SubmissionConfigReader and DCInputsReaderConfiguration) to be instantiated if to be used. This can lead to sequential reads on the file system even if not necessary and a degradation of the performance. Furthermore, the two classes make a lot of use of checked exceptions and this makes their use more annoying.
To improve the reading of the configurations related to the submission form, I propose to refactor these two classes to make them bean of Spring: the parsing of the files could be done during the startup phase of the context (immediately highlighting any inconsistencies) and the result of the parsing could be kept in memory (perhaps by modeling xml with JAXB). This would allow to save time during subsequent reads and not have to manage any file reading errors every time.
To allow you to update the files and read the changes made, we could think of some mechanism to force the update of the data in memory reading again the configuration (a bit like it is done with the @RefreshScope scope). This would allow to read any new configurations without having to restart the application.

@LucaGiamminonni : These ideas all sound reasonable to me.  However, I don't see them as high priority at this time...while I understand the benefits, it doesn't seem required at this time to enhance any existing or add new ones feature.

Related with the work I done in #8855, I also encounter an issue that relates with this.
I found out that is possible SubmissionConfigReader could be read into memory several times and in different code places leading us to the performance degradation referred.
I'm not planning to entirely refactor those classes and to use JAXB for configurations as the issue suggests, but I understand that the practical result of the WIP will be the same that created the need of this issue.
The WIP will create a way to load SubmissionConfigReader into memory and to make available methods to reload it when necessary.

Bumping up the priority as this is necessary for auto-reloading the submission configs to support #8855.

Decreased priority as we've implemented a way to auto-reload these configs (see prior comment)


add pipe2 to non-OSX BSD's

https://github.com/rust-lang/libc/issues/500

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+
Thanks!

:pushpin: Commit 7c06730 has been approved by alexcrichton

:hourglass: Testing commit 7c06730 with merge bce927b...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing bce927b36878cd7ed708447b79b4e8ad87b39246 to master...


Change require-dev.mikey179/vfsStream to lowercase characters

Composer is throwing

Deprecation warning: require-dev.mikey179/vfsStream is invalid, it should not contain uppercase characters. Please use mikey179/vfsstream instead. Make sure you fix this as Composer 2.0 will error.

Fixed in v2.2.0


Is this usable with shaders?

I am still new to shaders and the library Pixels, but currently I'm running my shader pipeline off the encoder from pixels.

let _ = pixels.render_with(|encoder, surface_texture, context| {
                    context
                        .scaling_renderer
                        .render(encoder, &post_process.texture1);

                    post_process.render(encoder, surface_texture);

Are we able to use shaders with this plugin?

Not yet. This library currently controls the render process without a way to override it. In the future I can allow the user to disable the default render system and define their own, this way you can add shaders like your example.

Appreciate the response! I'll be awaiting that feature :) thanks for your work on this

Hi @lecoqjacob, I've just released 0.10.0 and it adds a new default render cargo feature that controls the render system. Specify bevy_pixels = { version = "0.10", default_features = "false" } in your Cargo.toml to disable it.
See the custom_render example for how to specify your own render system. You should be able to configure any shaders you want here.


Confirm URL to use for GraphQL queries

Token front end needs to speak to the Vega network to which it corresponds. For example, our https://staging.token.vega.xyz needs to point to stagnet, to fetch the list of current validators. The problem with this is that hard coding every network that we might want to communicate with is impossible: for some networks, we don’t know what node to query to fetch the lists of… nodes we can query. It’s easy in stagnet - we set the host names.
Long term solution
The Inventivised Data Node specification contains a rich API for discovering other nodes on the network. This will be the proper source of data node lists
Short term solution
Right now, go-wallet, token-frontend and console all have to speak to Vega nodes. Currently, go-wallet relies on editing the config directly, and token-frontend relies on a hard coded list. However, go-wallet (as part of ticket x) is moving to fetch a list from Github. This list will be committed in the networks repo, and will also be enough for us to bootstrap the token front end. So lets use that.
Shorter term solution
See comments

another update: this also exists: https://graphql.vega.community

There is another option for Token Front End connecting to mainnet nodes, https://github.com/vegaprotocol/token-frontend-api-proxy. it doesn't currently rotate
So that leaves us with:
https://graphql.vega.community which does rotate
https://github.com/vegaprotocol/token-frontend-api-proxy as an option if ☝ fails
followed by some other bridges we can cross if/when we get to them

I began prepping a release for this, however I do not have the new ERC20 bridge address so this is currently blocked by that

Hi @campbellssource @dexturr - Does this needs to be QA'ed ? Doesn't look like but still wanted to confirm with you both.


Do not prevent POP transitions based on startingIndex

@Traviskn Hey! Just trying to understand the motivation for preventing transitions if the current index is less than the starting index. If we perform any history.replace() and then history.go(-n) we end up out of sync with our startingIndex and subseqently block the back transition!
Is there a chance we could remove this or is there good reason for this?
https://github.com/Traviskn/react-router-native-stack/blob/4d02ee75d994fd7eeaa47ebedd2fc736bee04d29/lib/StackTransitioner.js#L166

The main issue I was trying to solve with the starting index was to know if I should allow swipe to go back.
The situation I was imagining is you have something like a login screen. After logging in, you push to the main screen of your app with has a Stack component. You wouldn't want the user to swipe back to go to the login screen, only logging out out navigate you back to the first route.  So in this case the Stack allows swiping back only through the routes that it pushed onto the route stack.
A related problem I was hoping to solve is on which screens to show a back button in the header.  Unfortunately I haven't had much time recently to finish a transitioning header for the stack 😞 but I imagined I could use the starting index to know if I should show a back button in the header or not.
There's probably a better way to approach this though, totally open to new ideas! Sounds like there are some more dynamic use cases that the "startingIndex" doesn't work well for.

The code that prevents the swipe back gesture if the current route index is less than the starting index is here:
https://github.com/Traviskn/react-router-native-stack/blob/master/lib/StackTransitioner.js#L55

Thanks @Traviskn. Yes I've also spotted it on the pan responder. It absolutely makes sense to 'lock' us into the starting route at the intial index. I may have been too eager to open this issue! Closing for now.


Session keeps on getting expired with message 'ERROR: session expired, please login again'

Installed it on bash on osX.
After logging in with lc user -l, the command succeeds with a Successfully logged as <username> message.
But the session expires almost immediately. Any other command fails with a ERROR: session expired, please login again message.
Logging in again does not change the behavior.

please try the latest release 0.7.0 to see if this issue still exists?

I ran npm uninstall leetcode-cli yesterday and installed this again. But it did not fix the issue. Should I do this again or is there a different procedure to get the latest version?

Its working now, thanks!


oci_push to GCP broken

oci_push doesn't seem to work with GCP Artifact Registry (or maybe I am doing something wrong).
GCP quick start instructions here https://cloud.google.com/artifact-registry/docs/docker/store-docker-container-images say that when using docker, the pattern for pushing an image is:
docker push <REGION>-docker.pkg.dev/<PROJECT>/<REPO>/<IMAGE>:<TAG>
# Example: docker push us-central1-docker.pkg.dev/my-project/quickstart-docker-repo/quickstart-image:tag1

If I follow this with oci_push
oci_push(
    name = "push_gcp",
    image = ":image",
    repository = "us-central1-docker.pkg.dev/my-project/quickstart-docker-repo",
    remote_tags = ["tag1"],
)

I get an error
NAME_INVALID: Missing image name. Pushes should be of the form docker push HOST-NAME/PROJECT-ID/REPOSITO
RY/IMAGE

Looking at the generated push script, indeed crane doesn't seem to follow the above pattern
"${CRANE}" push "${IMAGE_DIR}" "${REPOSITORY}@${DIGEST}" "${ARGS[@]+"${ARGS[@]}"}" --image-refs "${REFS}"

In oci_push when I change the repository argument to include the image name us-central1-docker.pkg.dev/my-project/quickstart-docker-repo/quickstart-image, pushing seems to work. However, repository is no longer accurate description of the argument. Furthermore, tagging operations run by crane at the end of the script don't seem to be supported on GCP and I get unexpected status code 405 Method Not Allowed (HEAD responses have no body, use GET for details).
P.S. Definitely not an authentication issue since I can push the image without a problem using docker push

Correct use of repository is to include everything including the image name. distribution-spec doesn't say anything about image name and that what we conform to here.
Image name seems to be a distinction made by AR.

Thanks. In that case, what's the correct way of tagging the image as the separate crane tagging commands don't seem to work with GCP.

Yea, GCP Artifact Registry is PITA right now. I resorted to using the GitHub container registry instead because I couldn't figure out the correct way of formatting the repo string. A working example would be great, if anyone was able to make this work.

After a bit of back and forth, here is the correct BUILD config to push to GCP Artifact Registry:
Assuming:

Region: asia-northeast1
GCP project: my-project
repo: bazel-containers
container name: moby

# Publish image to registry
oci_push(
    name = "push",
    image = ":image",
    repository = "asia-northeast1-docker.pkg.dev/my-project/bazel-containers/moby",
    remote_tags = ["latest"],
    visibility = ["//visibility:public"],
)

That way, push works as expected. There is absolutely nothing broken, afaik.
Only the documentation could need an example.


Is this cookbook still maintained?

Hi,
It has been a while since there was any activity on this cookbook, and the kitchen tests are failing, so i was wondering if this cookbook was still maintained?

Yes. I'd like to help if you can add more details about failure of kitchen tests.

Failures seems to be on ubuntu-13.10 target on kitchen tests. We should answer #28 first.

testing ubuntu 13.10 to get some feedback

the root cause of kitchen test failure on ubuntu 13.10 is apt-get update failed:
Recipe: apt::default
         * file[/var/lib/apt/periodic/update-success-stamp] action nothing (skipped due to action :nothing)
         * directory[/etc/apt/apt.conf.d] action create (up to date)
         * cookbook_file[/etc/apt/apt.conf.d/15update-stamp] action create
           - create new file /etc/apt/apt.conf.d/15update-stamp
           - update content in file /etc/apt/apt.conf.d/15update-stamp from none to 174cdb
           --- /etc/apt/apt.conf.d/15update-stamp	2015-06-24 14:21:37.544607331 +0000
           +++ /etc/apt/apt.conf.d/.15update-stamp20150624-1401-1041oej	2015-06-24 14:21:37.544607331 +0000
           @@ -1 +1,2 @@
           +APT::Update::Post-Invoke-Success {"touch /var/lib/apt/periodic/update-success-stamp 2>/dev/null || true";};
         * execute[apt-get-update] action run[2015-06-24T14:21:59+00:00] ERROR: execute[apt-get-update] (apt::default line 62) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '100'

and:
STDERR: E: There are problems and -y was used without --force-yes
           ---- End output of apt-get -q -y install bsdtar=3.1.2-5ubuntu1 ----
           Ran apt-get -q -y install bsdtar=3.1.2-5ubuntu1 returned 100

closed since kitchen test works on supported platforms.


Apache HTTP client 5 support

Is there a possibility of supporting http client 5 (async)

Yes. It's possible. Will take to work.


[boost] fix emscripten build

fixes #27641
fixes #28423
fixes #29470
this PR adds support for non-header-only Boost libraries build under Emscripten
tested with:

vcpkg install boost-exception[core]:wasm32-emscripten -- issue discovered here
vcpkg install boost-outcome[core]:wasm32-emscripten -- depends on boost-exception
vcpkg install boost-regex[core]:wasm32-emscripten -- there is an issue for this failure

proven .a files in /lib and /debug/lib and headers in /include
while my changes seem to work, I'm looking forward to your review. I'm not familiar with b2 so I probably did in CMake too much
see also
https://github.com/boostorg/build/blob/develop/src/tools/emscripten.jam
https://www.boost.org/doc/libs/1_81_0/tools/build/doc/html/index.html#bbv2.extending.toolset_modules

@Pospelove Maybe you could take a look at this new emscripten boost build failure that just popped up? https://github.com/microsoft/vcpkg/issues/29529

@tobbi Yeah, I think so, I'll take a look.
Did my PR break boost-filesystem:wasm32-emscripten or just changed error?

@tobbi Yeah, I think so, I'll take a look. Did my PR break boost-filesystem:wasm32-emscripten or just changed error?
I actually don't know. I think we never got that far with installing the dependencies, so I can't tell.

@tobbi ok I see, thanks


.Net: New Feature: Add prompty file based functions from Kernel Builder

name: Feature request
about: Currently, there is no way to add prompty based prompt functions into the kernel when building. This makes uses them via DI or similar difficult and they need to be created on the fly

Currently, there is no way to add prompty based prompt functions into the kernel when building. This makes uses them via DI or similar difficult and they need to be created on the fly
var  function =  kernel.CreateFunctionFromPromptyFile(promptyFilePath, fileProvider, promptTemplateFactory);
it would be good if we had a similar functionality to 'importpluginfrompromptdirectory'
https://learn.microsoft.com/en-us/dotnet/api/microsoft.semantickernel.kernelextensions.importpluginfrompromptdirectory?view=semantic-kernel-dotnet

Hi @christasmithgit thanks for creating this issue. The team have a number of deliverables for Ignite so won't get to this until after that. However if you are interested in contributing this to the SK Prompty package we can review.


Comp: Input field

[ ] Create modifier
[ ] Create View Component

Where should we handle the state?

Inside the component OR
Where ever the component is used

Question: What impacts does both situation have on UI re creation,
import SwiftUI
struct InputFieldComponent: View {
@State var title: String
@State var text: String
    var body: some View {
        VStack(alignment: .leading) {
            Text(title)
            TextField(title, text: $text)
        }
        .modifier(inputFieldModifier())
    }

}
struct InputFieldComponent_Previews: PreviewProvider {
static var previews: some View {
InputFieldComponent(title: "Email address", text: "ff")
}
}

Lets try to get afew minutes of Juhas time to get his view/advice.


Dedicated Server not available- Timeout

Describe the bug
The dedicated server of the cluster aren't available.
To Reproduce
Steps to reproduce the behavior:

Go to ki.fh-swf.de
Click on Jupyterhub
Select Deep Learning and Data Science
Open dropdown and select a dedicated server and click start on the bottum of the webpage.

Expected behavior
Availability of a dedicated server.
Screenshots

Thanks in advance.
Best regards
Christian

the dedicated gpus will return in early feburary


Use of a local scope inside another scope definition is not allowed

Larastan Version: 1.7.13
--level used: 8
Pull request with failing test: https://github.com/pacoorozco/gamify-laravel/pull/268

Description
Using a already defined local scope in another scope is raised as error.
------ -----------------------------------------------------------------------------
  Line   app/Models/Badge.php
 ------ -----------------------------------------------------------------------------
  109    Call to an undefined method Illuminate\Database\Eloquent\Builder::active().
 ------ -----------------------------------------------------------------------------

Laravel code where the issue was found
102: public function scopeActive(Builder $query): Builder
103:    {
104:        return $query->where('active', true);
105:    }
106:
107:    public function scopeWithActuatorsIn(Builder $query, array $actuators): Builder
107:    {
109:        return $query
110:            ->active() 👈🏻
111:            ->hasAnyFlags('actuators', $actuators);
112:    }

Thank you for your report!
What does PHPStan say to this?
109:        return $query
110:            ->where('active', true)
111:            ->hasAnyFlags('actuators', $actuators);

------ ----------------------------------------------------------------------------------
  Line   app/Models/Badge.php
 ------ ----------------------------------------------------------------------------------
  109    Call to an undefined method Illuminate\Database\Eloquent\Builder::hasAnyFlags().
 ------ ----------------------------------------------------------------------------------

The phpstan.neon file includes the BenSampo integration:
includes:
    - ./vendor/nunomaduro/larastan/extension.neon
    - ./vendor/bensampo/laravel-enum/extension.neon

parameters:

    paths:
        - app
        - config
        - database
        - routes

    # The level 9 is the highest level
    level: 8

    excludePaths:
        - ./*/*/FileToBeExcluded.php

    checkMissingIterableValueType: false
    checkGenericClassInNonGenericObjectType: false

I see!
Try to add generics to https://github.com/BenSampo/laravel-enum/blob/master/src/Traits/QueriesFlaggedEnums.php
or create a stubs file that has it.

Sorry, I have not understood your suggestion.
I'm already using this trait
class Badge extends Model
{
    use SoftDeletes;
    use HasFactory;
    use QueriesFlaggedEnums;

// ....
}

Builder is a generic class: https://github.com/nunomaduro/larastan/blob/f0305d6f8f02d25144150160306badd51b7f2627/stubs/EloquentBuilder.stub#L6
You convince the package maintainer to use PHP generics or add a stubs file to your PHPStan config.
    /**
     * @param \Illuminate\Database\Eloquent\Builder<TModelClass> $query
     * @param string $column
     * @param int[] $flags
     * @return \Illuminate\Database\Eloquent\Builder<TModelClass>
     */
    public function scopeHasAnyFlags($query, $column, $flags) {}

Stubs are for overwriting PHPDocs in dependent packages.

I'm not good at explaining technologies to others.

Hi!
Thanks for the explanation. I'm going to open a PR to laravel-enum repository in order to use generics.
Thanks a lot @szepeviktor


With appropriate journalling, you should be able to track errors without running exceptions. The trials are supposed to be silent, with the control being the only one the user knows is executed. If the trails run exceptions then this library doesn't do its job.

This PR is for feature parity with the github/scientist implementation.
From my understanding, the use case would be for when you have existing integration tests. You can use scientist to perform your experiments in the tests.

I've got a local branch for something similar to this. I think it could be useful, but I thought it might be worth mentioning that I'm not aiming for parity with github's implementation. It was very much an inspiration, but I think we've got some freedom to try different stuff here. :)


compute method on primitive maps cause boxing/unboxing

The compute method on the maps require unboxing and boxing since the rely on the standard JDK 8 BiFunction instead of generating primitive type specific a BiFunction for each use case.
For example, Object2LongMap#computeLong
For example compare with Koloboke ObjLongMap#compute
It good that it is solved with Object2LongMap#computeLongIfAbsent, shame about computeLong

The problem here is the parameter space explosion. Having type-specific BiFunctions is totally possible, but would require 8*8*8 = 512 additional classes (or maybe even 9*9*9). Moreover, this would require non-trivial changes to the way the sources are generated (since we need a triple of types instead of a key-value tuple).
If we only add the BiFunctions for this specific use case, we could restrict ourselves to Key x Key -> Value and Key x Value -> Value, I think - potentially, something like Key x Key -> ValueObject and Key x Value -> ValueObject should be added, too. This would still be a lot of classes but less work since one does not have to change the source generation too much.

Right. How does Koloboke do it? Hundreds of function classes?

Koloboke API 1.0.0 has a function package with 281 classes in it.


Support port range in RUST implementation

Currently as far as I understand, there is no limit about port range that can be passed

Hi,
The actual requirmenet is creation of static export in docker file from issue #14 .
Thanks,
Assaf

Aah, yes, we will need that.

I have modified your implementation to scan for the next available port, in case there is something else with a port open in the range. It will now skip over those.


styl error

Describe the bug
styl file : src/css/range.styl
tui-image-editor-disabled{backbround-color:#f00}
Should be
background-color

@mvpyb
Thank you for the information. I'll fix it.

Thanks for the fix. I would like to know when the next version will be. Do you have an ETA? I'm using it for a project but when I build I got a warning. Thanks very much!

@Pascal1132
I'm sorry I'm late. I'm going to work on it soon. It will be released after that.

@lja1018
Are there still plans to correct this warning ?


Trailer headers key is unsafe

Since the same key is shared for all F[_] this can go badly wrong if there's a translate or mapK along the line ...
https://github.com/http4s/http4s/blob/77e4f3adc73875ac62ea9def48542bdb58365868/core/shared/src/main/scala/org/http4s/Message.scala#L295-L296

The best solution I see after thinking for a whopping 1 minute: seems like this should become directly part of the Message model instead of an attribute, such that it is bound to the F of the Message (and thus subject to any subsequent effect changes).


Please provide more info about "Number of users" and "Number of runs"

The "Number of users" and "Number of runs" seem ambiguous to me. Does number of users refer to how many users would author using this template, the number of users that would be impacted by using the template, or something else? Is the number of runs over a certain time period or in a certain context?
Depending on the context, the answers to these questions could vary wildly.

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

ID: 3bf8d0d2-3a6f-c3f1-494d-b0ea73c22f9b
Version Independent ID: 41bc35b2-5a4d-7406-1ae7-27b292033fcd
Content: Submit a flow template - Power Automate
Content Source: articles/publish-a-template.md
Service: flow
GitHub Login: @sunaysv
Microsoft Alias: sunayv

Hi @redmondChris . Thanks for submitting docs feedback. I think the point you are raising should be addressed in the UI. Where "number of runs" should probably be "run frequency". The descriptive text in those fields does provide guidance, and it's up to the submitter to describe whether it runs "every x minutes",  "x times daily", or "x times per month". This could vary depending on circumstance, so I don't think we should define this in docs.
@sunaysv can you please evaluate whether this warrants a UI update? Thanks!


Initial Lan Mode Support

Relates to issue #41 .
This PR adds initial support for Lan mode, for devices which identify themselves as "plug". While there are references and code to support "strip" type devices, this is not currently working. I think this is something to do with the way that devices with multiple channels are currently handled (this is going to need a bit of refactoring to sort out I think).
This only supports getting and setting the power state for a device, and has been tested against an S26 plug.
This is currently hidden behind an additional configuration setting. To enable support for the lan client the following needs added to the platform configuration.
"experimentalLanClient": true

Thanks for the contribution! As the LAN client is hidden behind a flag in configuration I think it should be safe to merge and release for the general public to test. Merging now :)


Arabic language

For "ar-AR" language, textarea must have:
direction: rtl;

Thanks!

Also for "he-IL" and "fa-IR"


Surface closed bugs in which users comment that they are still affected

This issue is based on the autonag feedback survey.

example: https://bugzilla.mozilla.org/show_bug.cgi?id=1751363#c71

Another such case: https://bugzilla.mozilla.org/show_bug.cgi?id=1619550#c18.