[WIP] Release 1.7.0

This release is built on top of OpenTelemetry Go v1.16.0/v0.39.0 and OpenTelemetry Go Contrib v1.17.0/v0.42.0/v0.11.0.
Added

Add the github.com/signalfx/splunk-otel-go/instrumentation/github.com/confluentinc/confluent-kafka-go/v2/kafka/splunkkafka instrumentation for the github.com/confluentinc/confluent-kafka-go/v2/kafka package. (#2301)

Codecov Report
Patch coverage has no change and project coverage change: +4.08 :tada:

Comparison is base (61ea825) 78.68% compared to head (45b06f1) 82.76%.

:exclamation: Current head 45b06f1 differs from pull request most recent head e1b1641. Consider uploading reports for the commit e1b1641 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2317      +/-   ##
==========================================
+ Coverage   78.68%   82.76%   +4.08%
==========================================
  Files          81       81
  Lines        3157     3157
==========================================
+ Hits         2484     2613     +129
+ Misses        601      475     -126
+ Partials       72       69       -3

Flag
Coverage Δ

Linux
82.76% <ø> (?)

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 11 files with indirect coverage changes

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


antirush zones doesn't disabled after certain time

Hello,
I have configured to expire after X seconds, I use detailed message and in chat the timer is counting down until it say "Antirush disabled" and when I try to pass trough a zone, I die (because I set it to kill).
Also would be great/better just to remove the zones after the specific time is met (or bomb planted). This way would be less confusing for new players.
P.S. I have tried the latest plugin but also a lot of commits from 1.0.3 when you introduced messages, I have tried almost all commits 1 by 1 and nothing worked.
Thank you,
Sebastian.

https://github.com/oscar-wos/AntiRush/commit/7d251dc907e4c60be50a4d6dfe1a3c3ce161b3f7
Delete your config to regenerate new file
{
  "CampZones": [ 1 ],    // 0 - Bounce, 1 - Hurt, 2 - Kill, 3 - Teleport
}


Windows: Remove TP4 support from main codebase

Signed-off-by: John Howard<EMAIL_ADDRESS>This is the next step to removing TP4 support from the docker master codebase. This updates the remainder of the main codebase (see #21777 also). There are more TP4 references still to work on in future PRs in test code and in vendor code (HCSShim).

LGTM

LGTM 🐰

LGTM


scribusUnstable: init at 2018-10-13

Motivation for this change
For more than three years, Scribus 1.5 has been around as the next major release. E.g. in Debian, this appears to be available as scribus-ng. In general, I'd recommend people learning Scribus to take the 1.5 version.
Things done
Packaged Scribus from the most recent svn commit. I'd rather packaged the 1.5.4 release, but they had some compile failure und I failed to cherry-pick the fix. As soon as 1.5.5 comes out, I'd switch to the release to have a definite version.

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

I'm still not sure about GitHubs notification system, so I'll will ping you also here, @nlewo.

@GrahamcOfBorg build scribusUnstable

Success on aarch64-linux (full log)
Attempted: scribusUnstable
Partial log (click to expand)
shrinking /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13/lib/scribus/plugins/libxpsexplugin.so
shrinking /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13/lib/scribus/plugins/libsvgexplugin.so
shrinking /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13/lib/scribus/plugins/libscribusexportpixmap.so
shrinking /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13/bin/scribus
gzipping man pages under /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13/lib  /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13/bin
patching script interpreter paths in /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13
checking for references to /build in /nix/store/2sc68x2xv6s7zwq2j5krysi1xrm50vib-scribus-unstable-2018-10-13...
postPatchMkspecs

Timed out, unknown build status on x86_64-linux (full log)
Attempted: scribusUnstable
Partial log (click to expand)
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/imagedataloaders/scimgdataloader_ps.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/imagedataloaders/scimgdataloader_psd.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/imagedataloaders/scimgdataloader_qt.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/imagedataloaders/scimgdataloader_tiff.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/imagedataloaders/scimgdataloader_wpg.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfcolor.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfcolorspecification.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfdocument.cpp.o
building of '/nix/store/442cvxwzqg7bnyzrfsxk1hfl28zkws3z-scribus-unstable-2018-10-13.drv' timed out after 3600 seconds
error: build of '/nix/store/442cvxwzqg7bnyzrfsxk1hfl28zkws3z-scribus-unstable-2018-10-13.drv' failed

Mh, ofborg did a timeout. Is there a way to prevent this?

@GrahamcOfBorg build scribusUnstable
@erictapen I don't think we can change the timeout value. Let's see if it timeouts again.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: scribusUnstable
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Timed out, unknown build status on x86_64-linux (full log)
Attempted: scribusUnstable
Partial log (click to expand)
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfcolor.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfcolorspecification.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfdocument.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfobject.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfmeasurementspec.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxftristimulusspec.cpp.o
[ 63%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfutils.cpp.o
[ 63%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/paletteloader.cpp.o
building of '/nix/store/vgncn2vvs27mz7hi8pk64439j7q8g3f3-scribus-unstable-2018-10-13.drv' timed out after 3600 seconds
error: build of '/nix/store/vgncn2vvs27mz7hi8pk64439j7q8g3f3-scribus-unstable-2018-10-13.drv' failed

Local build:
 → user: 0.61, system: 0.57, elapsed: 10:13.89

@GrahamcOfBorg build scribusUnstable
Let's hope whatever caused timeouts was shaken off!

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: scribusUnstable
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: scribusUnstable
Partial log (click to expand)
shrinking /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13/lib/scribus/plugins/libxpsexplugin.so
shrinking /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13/lib/scribus/plugins/libsvgexplugin.so
shrinking /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13/lib/scribus/plugins/libscribusexportpixmap.so
shrinking /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13/bin/scribus
gzipping man pages under /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13/share/man/
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13/lib  /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13/bin
patching script interpreter paths in /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13
checking for references to /build in /nix/store/qjwhw5b9n4dhcdlhs0za197rl12lpvn6-scribus-unstable-2018-10-13...
postPatchMkspecs

Timed out, unknown build status on x86_64-linux (full log)
Attempted: scribusUnstable
Partial log (click to expand)
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/imagedataloaders/scimgdataloader_wpg.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfcolor.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfcolorspecification.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfdocument.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfobject.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfmeasurementspec.cpp.o
[ 62%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxftristimulusspec.cpp.o
[ 63%] Building CXX object scribus/CMakeFiles/scribus.dir/palettes/cxfutils.cpp.o
building of '/nix/store/5ipywzr63x0zxw8zrkmg776wm9s82rrb-scribus-unstable-2018-10-13.drv' timed out after 3600 seconds
error: build of '/nix/store/5ipywzr63x0zxw8zrkmg776wm9s82rrb-scribus-unstable-2018-10-13.drv' failed

@samueldr you seem to have a fast machine ;)
real    49m13.427s

Thanks ;)


Stretchy spaces?

One of my favourite viscose addons is called stretchy spaces - it allows re-defining how much space a indentation-space takes up, kinda like the customisability of tabs, but in a codebase using spaces.
I've tried to manually install this add-on from the vscode marketplace (it's not on open VSX), and as expected, it doesn't work (it's quite niche and affects the rendered code, so I didn't expect it would work at this stage in the development of Onivim 2).
However, I did wonder if there would be any interest in supporting this kind of feature, essentially, allowing a single space of indentation to be displayed as indentation of an arbitrary number of spaces. For example, the code base I work on is 2 space indent, but I much prefer 4 space and I can handle that in VSCode without bothering my teammates. However, since switching to onivim 2 full time, I've lost this feature 😢
WDYT? Could this type of add-on (technically) eventually be supported, if not, could this make sense as a native feature? :)

Thanks for logging the issue @lougreenwood !

Could this type of add-on (technically) eventually be supported,

Yep, this would be related to the #3189 implementation - the extension uses the letterSpacing property https://github.com/kylepaulsen/vscode-stretchy-spaces/blob/e1bb545a701989a2ce01a44759f04142d304a70c/extension.js#L121
Essentially, it involves wiring up the text decoration API, and then setting up some custom calculation and measurement for the characters. That extension uses kind of an obscure unit of ch: https://css-tricks.com/the-lengths-of-css/#ch - but it seems like we can calculate this based on our font metrics.


Vulnerability roundup 88: openexr-2.3.0: 3 advisories [5.5]

search, files

[ ] CVE-2020-15304 CVSSv3=5.5 (nixos-20.03)
[ ] CVE-2020-15305 CVSSv3=5.5 (nixos-20.03)
[ ] CVE-2020-15306 CVSSv3=5.5 (nixos-20.03)

Scanned versions: nixos-20.03: 6a00eba02a3. May contain false positives.

See also: #88358

20.03 is Frozen and EOL.
As such, issue is closed.


Component: Callout

Stories

As a reader of a guide, I want to easily see important information so that I make sure to read what is most important.

Notes

See the component doc for more information
This ticket covers both design and development tasks. Change assignee of the ticket based on who has the next action, and remove the person or people that no longer have an action. It's expected that a ticket will get passed back and forth a few times.

Done When

[ ] UX: Component design is drafted and shared for review
[ ] Dev: Component design is reviewed and approved
[ ] Peer UX: Compontent design is reviewed and approved
[ ] Dev: Component style and markup is developed and shared for PR review
[ ] Dev: Documentation on how to use component is drafted
[ ] UX: Component style and markup is reviewed and approved
[ ] Peer Dev: Component style and markup is reviewed and approved
[ ] Component is available for use

Callout
From the GDoc https://docs.google.com/document/d/1yC4y262CSiQ1iBqxjXPxFsOJJ1y0Z6WcDdnqY7sKnco/edit:

This component styles the playbook’s “lightbulb” sections, but it’s extensible to any paragraph we want to give special emphasis.

Assumptions I'm making

We want to let authors swap out the lightbulb icon in this component for something else, depending on the context.

Visual design
Here's what I have:

Markup
At first, I thought an <aside> might be appropriate here. But the lightbulb sections seem like they're directly related to the main content: you can't pull them out without losing important context. So I'm just using a <section> tag instead.
For screen readers, I added a visually hidden <h3> to distinguish this component from the main content. Alternatively, we could add a title attribute to the icon SVG.
Component API
How might we make this component easy for non-engineers to edit?
Letting authors swap out icons raises some questions here. Where will the icons come from?
Idea 1
I've been using Bootstrap Icons for this project thus far. We could:

Import the bootstrap-icons NPM package into the guides repo
Write in our documentation that authors can search the Bootstrap Icons site for the symbol they'd like to use
Let them reference the icon like so:

{% callout "This is the content of my callout.", "box2-heart" %}

Idea 2
We could simplify things by:

Choosing 3-5 icons we might want to use with callouts
Adding them to our /assets/ folder
Mentioning the icon choices in our documentation

Idea 3
We could move icon customization out of scope.
@jeffmaher @SMakaiTakori Let me know what you think!

Forgot to mention the status of this on my end:
I've committed an example of a Callout to the storybook branch. I've also created a Nunjucks template locally in an 11ty instance (although we still need to decide upon the component API above.)
I can open a PR with just these components once #5 and #6 are done.

Awaiting review from assignees ( @SMakaiTakori , @jeffmaher )

For screen readers, I added a visually hidden <h3> to distinguish this component from the main content. Alternatively, we could add a title attribute to the icon SVG.
If we can, I would prefer to add a title attribute directly to each SVG rather than the hidden <h3> just to keep with common accessibility practices.

Question for @jrubenoff and @SMakaiTakori : Would would it look like for a document author to add this into a Markdown file? Would it be the Nunjucks component or some other markup?

@LynnHerrick9 to handle merge conflicts, then done!

@SMakaiTakori will handle these conflicts.


Custom date ticks

This PR requires a version of D3 more recent than the version currently included with mpld3.

I have not been following d3js development closely enough... it looks like we have d3 version 3.4.2 in our repo, and presumably this is the version that the urls.py links to on the mpld3.github.io website as well.
Should we upgrade to 3.5.12?  That appears to be the most recent.
@jakevdp : your thoughts on this particularly solicited.

3.5.12 works for me.

I've confirmed that this works for me, and requires a d3.js upgrade (e.g. #339).  I'm going to merge.


Reduce size of default PATH or provide mechanisms to configure it easily?

Description
We ran into a hard-to-find bug with python's setuptools that runs vcvarsall.bat internally and fails because of the very long default PATH that the windows-latest runner provides. Yes, we add a few entries but nothing compared to the huge default. I looked through the entries and we need only 10% of what is inside there. Is there any suggestion on how to handle this without hard-coding an own path or removing certain wildcard patterns (which may crash with updates to the runner)?
Area for Triage:
Scripting and command line
Question, Bug, or Feature?:
Question
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Ubuntu 20.04 LTS
[ ] Windows Server 2016 R2
[X] Windows Server 2019

Expected behavior
I would like to have better control of the PATH and preferably a smaller default PATH.
Actual behavior
See discussion in https://github.com/OpenMS/OpenMS/pull/4779. Starting from https://github.com/OpenMS/OpenMS/pull/4779#issuecomment-679384753
Repro steps
https://github.com/OpenMS/OpenMS/pull/4779
Probably adding a few additional entries to the default path and then calling vcvarsall.bat is enough.

Hello @jpfeuffer! Unfortunately now we have no opportunity to reduce size of default PATH. But after some investigation of your issue we have found that:

We have LongPathsEnabled parameter enabled on Windows Server 2016/2019. See details in this comment (https://github.com/actions/virtual-environments/issues/1052#issuecomment-644212560);

You can try to use this function to remove one path from PATH:

function RemoveFrom-Path ($pathToRemove) {
    $parts = $env:PATH.Split(";") | Where-Object { -not ( $_ -match $pathToRemove) }
    $newPATH = [string]::Join(";", $parts)
    $env:PATH = $newPATH
    Write-Host "::set-env name=PATH::$newPATH"
}
RemoveFrom-Path "Google\\Cloud SDK"
RemoveFrom-Path "Microsoft SQL Server"

This code will continue to work in future image releases.
If you still have any issues please let us know.

Hi!
Thank you for your comment. While I think 1) does not help much because of vcvarsall.bat calls a batch command to extend the path and therefore reaches the command line length limit, 2) is a nice temporary solution.
I think there should also be some work done on the Visual Studio (not using batch to setup the environment) and setuptools (only setup the environment, if not yet done) side.

Closing this for now since we can't reduce size of default PATH. @jpfeuffer please let us know if you have any concerns.


Elasticsearch-Spark read data contains fields of IP type, triggering type cast error.

What kind an issue is this?

[x] Bug report. If you’ve found a bug, please provide a code snippet or test to reproduce it below.
The easier it is to track down the bug, the faster it is solved.
[x] Feature Request. Start by telling us what problem you’re trying to solve.
Often a solution already exists! Don’t send pull requests to implement new features without
first getting our support. Sometimes we leave features out on purpose to keep the project small.

Issue description
The target index's data contains an IP field. If using Elasticsearch Spark to read the data,
the returned Spark data schema of the IP field is String, while it actually parsed as Integer (Long) when
the data is retrieved from Elasticsearch. Thus, the real datatype and the Spark schema does not match,
which results in scala.MatchError:<PHONE_NUMBER> (of class java.lang.Long).
Steps to reproduce
The elastic data source contains come fields of IP type, like
"collect_ip": "<IP_ADDRESS>",

and the corresponding definition of mapping is:
"dev_ip": {
    "type": "ip",
    "include_in_all": false
},

I try to read the index from pyspark:
df = spark.read.format("org.elasticsearch.spark.sql")
               .options(nodes="es_nodes", port=9200)
               .load("index_name")

and the spark DataFrame is successfully loaded, and we can inspect its schema:
root
  ......
  |-- collect_ip: string (nullable = true)
  |-- end_time: timestamp (nullable = true)
  |-- response_type: integer (nullable = true)
  ......

Then I try to have a preview of the data by calling df.show(), The following exception (scala.MatchError) is triggered.
Strack trace:
Caused by: scala.MatchError:<PHONE_NUMBER> (of class java.lang.Long)
        at org.apache.spark.sql.catalyst.CatalystTypeConverters$StringConverter$.toCatalystImpl(CatalystTypeConverters.scala:277)
        at org.apache.spark.sql.catalyst.CatalystTypeConverters$StringConverter$.toCatalystImpl(CatalystTypeConverters.scala:276)
        at org.apache.spark.sql.catalyst.CatalystTypeConverters$CatalystTypeConverter.toCatalyst(CatalystTypeConverters.scala:104)
        at org.apache.spark.sql.catalyst.CatalystTypeConverters$$anonfun$createToCatalystConverter$2.apply(CatalystTypeConverters.scala:386)
        at org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$3.apply(ExistingRDD.scala:60)
        at org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$3.apply(ExistingRDD.scala:57)
        at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
        at org.apache.spark.sql.catalyst.expressions.GeneratedClass$GeneratedIteratorForCodegenStage1.processNext(Unknown Source)
        at org.apache.spark.sql.execution.BufferedRowIterator.hasNext(BufferedRowIterator.java:43)
        at org.apache.spark.sql.execution.WholeStageCodegenExec$$anonfun$10$$anon$1.hasNext(WholeStageCodegenExec.scala:614)
        at org.apache.spark.sql.execution.SparkPlan$$anonfun$2.apply(SparkPlan.scala:253)
        at org.apache.spark.sql.execution.SparkPlan$$anonfun$2.apply(SparkPlan.scala:247)
        at org.apache.spark.rdd.RDD$$anonfun$mapPartitionsInternal$1$$anonfun$apply$25.apply(RDD.scala:830)
        at org.apache.spark.rdd.RDD$$anonfun$mapPartitionsInternal$1$$anonfun$apply$25.apply(RDD.scala:830)
        at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
        at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324)
        at org.apache.spark.rdd.RDD.iterator(RDD.scala:288)
        at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
        at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324)
        at org.apache.spark.rdd.RDD.iterator(RDD.scala:288)
        at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87)
        at org.apache.spark.scheduler.Task.run(Task.scala:109)
        at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:345)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        ... 1 more

In particular, the long integer in the error message<PHONE_NUMBER> actually is the integer value of IP address <IP_ADDRESS>, which I have listed above.
Version Info
OS: CentOS Linux 7 (Core), Linux 3.10.0-693.el7.x86_64
JVM         :  1.8.0_40
Hadoop/Spark:  <IP_ADDRESS>/2.3.1
ES-Hadoop   :  5.6.0
ES          :  5.1.1
Feature description
The feature should also address the aforementioned issue.
Before reading the data from Elasticsearch, one can add a group of options to specify the desired datatype for fields, in case that there is no corresponding data type in Java, or the auto guess procedure of data type has some flaws.
This option should work like es.read.field.as.array.include, which convert a field to array type.
For example, assume there is an option
es.read.field.as.string.include    collect_ip

and then, the obtained schema should set of type of collect_ip to String as there is no IP type in Java. When parsing data from Elasticsearch, this option specifies that the collect_ip field should be converted to String from its original type (may be long integer). In this way, the returned data will match the spark schema.

Hi @garylavayou. Can you give exact steps for reproducing this? Here is what I did, but I did not reproduce it. First I created the mapping in Elasticsearch:
curl -XPUT "http://localhost:9200/test" -H 'Content-Type: application/json' -d'
{
  "mappings": {
    "properties": {
      "dev_ip": {
        "type": "ip"
      }
    }
  }
}'

And added a document:
curl -XPOST "http://localhost:9200/test/_doc" -H 'Content-Type: application/json' -d'
{
  "dev_ip": "<IP_ADDRESS>"
}'

Then in pyspark I did
>>> df = spark.read.format("org.elasticsearch.spark.sql").load("test")
>>> df.printSchema()
root
 |-- dev_ip: string (nullable = true)

>>> df.show()
+-------------+
|       dev_ip|
+-------------+
|<IP_ADDRESS>|
+-------------+

@masseyke I have retry the procedure on my environment, and the problem is not reproduced. I noticed that I previously use ES-Hadoop version 5.6.0, which does not match the ES version 5.1.1. Now, I switch to use ES-Spark version 5.1.1 and the problem might be resolved.

@masseyke I have retry the procedure on my environment, and the problem is not reproduced. I noticed that I previously use ES-Hadoop version 5.6.0, which does not match the ES version 5.1.1. Now, I switch to use ES-Spark version 5.1.1 and the problem might be resolved.


Scaled integer rounding

Hello John, thanks for the great library!
Are the failed travis tests worrying ?

Hi Liarokapis. Thanks for getting in touch. If you look at the Travis
reports you can see that only jobs invoking clang-tidy are failing and that
it's a segfault in selected build steps. This is due to a crash in that
tool. I've filled a bug with
LLVM which hasn't been picked up yet. But version 10 was released in the
last few days so I'm going to revisit this very soon as I build a new
docker image. I don't believe it'll fix the problem but it'll be able to
update the bug and I'll mark those jobs as 'can fail'.
On Tue 31 Mar 2020, 07:21 Liarokapis Alexandros<EMAIL_ADDRESS>wrote:

Hello John, thanks for the great library!
Are the failed travis tests worrying ?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/johnmcfarlane/cnl/pull/545#issuecomment-606424691,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFTGN5WCB25ZYMYR562T2DRKGDV5ANCNFSM4KCN5Y6A
.

Alex,
Build is green once more.
Thanks,
John
On Tue, 31 Mar 2020 at 08:56, John McFarlane<EMAIL_ADDRESS>wrote:

Hi Liarokapis. Thanks for getting in touch. If you look at the Travis
reports you can see that only jobs invoking clang-tidy are failing and that
it's a segfault in selected build steps. This is due to a crash in that
tool. I've filled a bug
with LLVM which hasn't been picked up yet. But version 10 was released in
the last few days so I'm going to revisit this very soon as I build a new
docker image. I don't believe it'll fix the problem but it'll be able to
update the bug and I'll mark those jobs as 'can fail'.
On Tue 31 Mar 2020, 07:21 Liarokapis Alexandros<EMAIL_ADDRESS>wrote:

Hello John, thanks for the great library!
Are the failed travis tests worrying ?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/johnmcfarlane/cnl/pull/545#issuecomment-606424691,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFTGN5WCB25ZYMYR562T2DRKGDV5ANCNFSM4KCN5Y6A
.


Bug gives error "newProps is not defined"

I think the variable names props and newProps should be the same in lines 456 and 460 of the function clickable in core/src/Native/Graphics/Input.js:
		var element = wrappedElement._0;
		var props = Utils.update(element.props, { click: onClick });
		return {
			ctor: wrappedElement.ctor,
			_0: {
				props: newProps,
				element: element.element
			}
		};

Comparing with the function before that one (hoverable) it looks like there's a typo on line 456, and it possibly was meant to be:
var newProps = Utils.update(element.props, { click: onClick });

@evancz, is this another case of props changes needed, like in the last minute changes earlier today?

Should be fixed now. Clear out elm-stuff/ and try again.

Thanks a million!


adding PCDMFile

Should be straight forward, except repo.create() looks for a NonRDFSource class for continuing with binary data prepping, which sets the resource as a file type in Fedora.
It would work to add a check for pcdm.models.PCDMFile just like NonRDFSource, but that would not maintain PCDM as a plugin.
Ah ha!  if PCDMFile extends NonRDFSource, then it's possible to look for that class in the inheritance chain?  That might work...

Added, per approach above.


Add WRAP_SECRETS constant to control wrapping

Maybe we should make secret wrapping the default for the CLI.  Then the environment variable could be NAKED_SECRETS for disabling wrapping.

Maybe we should make secret wrapping the default for the CLI. Then the environment variable could be NAKED_SECRETS for disabling wrapping.

I have the crypto working, but have not integrated the crypto into processing the REST responses.


(PUP-11654) Allow for omission of unchanged resources from the report

@joshcooper I think all comments addressed, let me know if I missed anything.


install & uninstall commands use --namespace flag

This update the argo cli commands for install and uninstall to use the same --namespace flag as all other commands instead of the installation-specific flag --install-namespace (removing it entirely).
Closes #812

The original reason for having --install-namespace separate from --namespace was because I did not think it was possible to distinguish when a user did not specify the namespace and we did not want argo to install into the default namespace. But the clientConfig.Namespace() allows us to distinguish the intent. This is much better behavior. Thank you for the fix!


Drop broken link README.md

Just found broken link in README. I think you rearranged repository and now it is not available. I think you have forgotten to update readme

It will be eventually be alive again. We’re experimenting with monorepo rn, and it will most certainly be the one.


Release 3.3.0 fails to receive banner ads with error "banner height is invalid"

I just updated to SDK 3.3.0 and I am no longer receiving banner ads in my app. Something in the SDK appears to be setting the banner height to zero, or just not setting the height.
Here is my code for creating the ad instance:
CGRect bannerFrame = CGRectMake(0, 0, 320, 50);
self.banner = [[MobFoxAd alloc] init:invh withFrame:bannerFrame];
self.banner.delegate = self;
[self.viewController.view addSubview:self.banner];
[self.banner loadAd];

Log file:
(You can see in the MobFox Ad Request that adspace_height is 0)
2017-12-19 11:10:31.407387+0100 LifeTotal[863:323122] Showing banner ad...
2017-12-19 11:10:31.407873+0100 LifeTotal[863:323122] dbg: ### MobFoxPlugin >> showBanner
2017-12-19 11:10:31.408254+0100 LifeTotal[863:323122] Starting refresh timer (30secs)
2017-12-19 11:10:31.409074+0100 LifeTotal[863:323122] dbg: ### MobFoxPlugin >> createBanner(5a4c16612c0a289489e91b9c37a2cbc1)
2017-12-19 11:10:31.409302+0100 LifeTotal[863:323122] dbg: ### MobFoxPlugin: position: bottom-center
2017-12-19 11:10:31.409493+0100 LifeTotal[863:323122] dbg: ### MobFoxPlugin: bannerWidth: 320
2017-12-19 11:10:31.409646+0100 LifeTotal[863:323122] dbg: ### MobFoxPlugin: bannerHeight: 50
2017-12-19 11:10:31.464730+0100 LifeTotal[863:323122] dbg: ### MobFoxPlugin >> loadBannerContent
2017-12-19 11:10:31.789351+0100 LifeTotal[863:323203] WF: === Starting WebFilter logging for process LifeTotal
2017-12-19 11:10:31.790093+0100 LifeTotal[863:323203] WF: _userSettingsForUser mobile: {
    filterBlacklist =     (
    );
    filterWhitelist =     (
    );
    restrictWeb = 1;
    useContentFilter = 0;
    useContentFilterOverrides = 0;
    whitelistEnabled = 0;
}
2017-12-19 11:10:31.791133+0100 LifeTotal[863:323203] WF: _WebFilterIsActive returning: NO
2017-12-19 11:10:32.585684+0100 LifeTotal[863:323122] MobFox Ad Request >>> : {
    adFormat = banner;
    "adspace_height" = 0;
    "adspace_strict" = 0;
    "adspace_width" = 320;
    autoplay = true;
    "banner_pos" = 1;
    "dev_js" = 1;
    "hide_mute" = true;
    "o_iosadvid" = "165BA89A-EADD-4A00-858A-25A8CA294848";
    rt = "iphone_app";
    s = 5a4c16612c0a289489e91b9c37a2cbc1;
    skip = "";
    "sub_bundle_id" = "com.snowleopardgames.lifetotal";
    type = waterfall;
    v = "Core_3.3.0_static_core";
}
2017-12-19 11:10:33.678972+0100 LifeTotal[863:323122] MobFox ad response: {
    customEvents =     (
                {
            class = Amazon;
            id = stack393247;
            parameter = b2ce9c95c3f94900a98802f3d47ad6e1;
            pixel = "http://nvirginia-callbacks.mobfox.com/customevent.pixel.php?h=760019869aa519675cf35cff060ba56d&custom_event_id=stack393247";
        },
                {
            class = Conversant;
            id = stack393249;
            parameter = "675e31fc-3465-11e4-b31e-15f4fced7073";
            pixel = "http://nvirginia-callbacks.mobfox.com/customevent.pixel.php?h=760019869aa519675cf35cff060ba56d&custom_event_id=stack393249";
        },
                {
            class = Facebook;
            id = stack393248;
            parameter = "1379767115623780_1607430786190744";
            pixel = "http://nvirginia-callbacks.mobfox.com/customevent.pixel.php?h=760019869aa519675cf35cff060ba56d&custom_event_id=stack393248";
        },
                {
            class = Conversant;
            id = stack393250;
            parameter = "675e31fc-3465-11e4-b31e-15f4fced7073";
            pixel = "http://nvirginia-callbacks.mobfox.com/customevent.pixel.php?h=760019869aa519675cf35cff060ba56d&custom_event_id=stack393250";
        },
                {
            class = AdColony;
            id = stack393209;
            parameter = "";
            pixel = "http://nvirginia-callbacks.mobfox.com/customevent.pixel.php?h=760019869aa519675cf35cff060ba56d&custom_event_id=stack393209";
        }
    );
}
2017-12-19 11:10:33.696767+0100 LifeTotal[863:323122] MFCustomEventAdDidFailToReceiveAdWithError: Error Domain=Invalid height of 0 Code=0 "(null)"
MFCustomEventAdDidFailToReceiveAdWithError: Error Domain=No fill Code=2 "(null)"
2017-12-19 11:10:34.146525+0100 LifeTotal[863:323122] MFCustomEventAdDidFailToReceiveAdWithError: Error Domain= Code=0 "Banner height is invalid. it has to be equal to 50pt, 90pt or 250pt" UserInfo={NSLocalizedDescription=Banner height is invalid. it has to be equal to 50pt, 90pt or 250pt}
2017-12-19 11:10:34.265485+0100 LifeTotal[863:323122] MFCustomEventAdDidFailToReceiveAdWithError: Error Domain=No fill Code=2 "(null)"
2017-12-19 11:10:34.268241+0100 LifeTotal[863:323122] MobFox>> Custom Event Class Not Found: MobFoxCustomEventAdColony
2017-12-19 11:10:34.269157+0100 LifeTotal[863:323122] dbg: ### MobFoxPlugin >> MobFoxAdDidFailToReceiveAdWithError: Error Domain=no ad could be found for this request (no fill) Code=0 "(null)"

In an attempt to work around the issue, I tried adding the following lines to my ad instance creation:
self.banner.adspace_width = @320;
self.banner.adspace_height = @50;

and it did change the adspace_height shown in the request, but the same error still occurs.
Looking at in the debugger, when -requestAdWithSize is called on my CustomEvent objects, it is always of the size (320,0). This causes all CustomEvent Adapters to either throw errors or request ads with an invalid size.
Please take a look at this ASAP!
(Also interesting, the response is coming back with a banner for Ad Colony but we don't have that provider in our mediation stack.)

Thanks, looking at it now.

In our demo app (just updated as it was out of date) in the project it appears to work correctly:
    self.bannerAdRect = CGRectMake((screenWidth-bannerWidth)/2, SCREEN_HEIGHT - bannerHeight , bannerWidth, bannerHeight);
    self.mobfoxAd = [[MobFoxAd alloc] init:MOBFOX_HASH_BANNER_TEST withFrame:self.bannerAdRect];
    self.mobfoxAd.delegate = self;
    self.mobfoxAd.refresh = [NSNumber numberWithInt:AD_REFRESH];
    //self.mobfoxAd.adspace_strict = false;
    [self.view addSubview:self.mobfoxAd];

We are still looking into it. Also this part wasn't changed this version. Do you have any more data that can help us track this?
Thanks

Try using any CustomEvent Adapter maybe? As I mentioned, the size is coming in wrong in -requestAdWithSize.

Also sample project would be helpful.
Thanks.

Strange, as it's also 0 in the request params:
MobFox Ad Request >>> : {
    adFormat = banner;
    "adspace_height" = 0;
...

Ok, we'll try it with custom events. As Shimi said, if you have a sample project that reproduces this it will be best.
Thanks

After further work on this issue, I think it may be my fault and nothing to do with the SDK.
I have been trying to use view constraints to pin the banner to the top or bottom of the screen (instead of using X/Y coordinates) and I believe I messed something up there and the banner view is being resized to 0 height despite being created with the appropriate size. Perhaps your SDK is pulling the view's height information at the time of the request, instead of using the size upon creation. That would explain things.
Apologies for potentially wasting your time.

Yup it's totally my fault. Sorry!

Great to hear it solved itself (:


kore-repl: Do not run stepper for try command

Running the try command through the stepper produces confusing output. Running unification directly makes the result clearer and also doesn't modify the execution graph.
Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock
[ ] Style conformance: stylish-haskell

The problem with this approach is that it will no longer allow users to circumvent the auto (step) prover by forcing certain axioms/claims to be used at a specific step. To me, this is the main use of this command. The fact that it shows you the unification error if one exists is just a nice bonus.
If we need such a command, perhaps it might be better to just add one, such as unify?

As discussed in the daily meeting, we created a card for a "force" command which addresses my comment above.


chore(master): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2024-02-09)
Features

publish new version (c8ed853)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/metailurini/psmgmt/releases/tag/v1.0.0 :sunflower:


Fix support for BAI2 files with trailing whitespaces and blank lines

Description
Related to https://github.com/ministryofjustice/bai2/issues/32
I've seen banks sending files with trailing whitespaces and blank lines, which the current version of the library fails to parse, raising an error.
Solution
Added a strip call alongside a conditional to only add lines that have any content.
Testing
Added two unit tests with the cases specified.

sorry for the long wait! seems reasonable to me, though i know very about the bai2 format. since existing tests pass, i'm fine with this change – just made a tiny stylistic change so that a line isn’t stripped twice


Non asci characters

Thanks for a great library! It was the only one which worked with my display.
I want to display characters with umlauts which are not in the asci character set. Do you know how to do that?
Example:
  lcd.print("ä ö");

you must create the characters bitmap and then upload these to the 8 special characters.
See createChar() function and samples you can find on the internet.
because all characters will come through the write function of the library you can modify this function in the library for you to replace ascii umlaute to these special characters.


Increase the width of ListPane.

Which is not possible in the latest WinUI/WindowsAppSDK, Until the fix (https://github.com/CommunityToolkit/WindowsCommunityToolkit/pull/4817) is accepted

#36 Use customized ListDetailsView to resolve the issue.


APK Issue

I did everything right but when i try to connect on the yt app it displays this on cmd:
() sg32eS1XDi8 clean fetch<PHONE_NUMBER>298
[yt2009_error] comments parser error TypeError: Cannot read properties of undefined (reading 'forEach')
at Object.comments_parser (C:\Users\Admin\yt2009\back\yt2009utils.js:73:50)
at C:\Users\Katika\yt2009\back\yt2009html.js:2386:37
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[yt2009_error] comments parser error TypeError: Cannot read properties of undefined (reading 'forEach')
at Object.comments_parser (C:\Users\Admin\yt2009\back\yt2009utils.js:73:50)
at C:\Users\Katika\yt2009\back\yt2009html.js:2389:37
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Then the app says there was a problem with your network?

Is the host set up correctly in the config?


ui-router v1.0.0.beta.2 & Angular 1: ui-router hangs if you change state during resolve

How to reproduce

In your state, add a route that depends on an async(es6) resolve. Add a artificial timeout of 10 seconds.
Navigate to that state
Before the resolve completes, navigate somewhere else.
After the artificial timeout, note that the URL changed but you are in state #3.
See that you are unable to change states until you hard refresh.

I will make a plunkr for this soon, unless someone else has time. :)

I think this is fixed in upcoming beta.3.   #2972
Try adding this to your app as a workaround for beta.2:
$transitions.onFinish({}, function() {})

Thanks! That was it.

Nice to read this!
Thanks a lot!

For anyone who's still having problems with this:
I was using async calls within $transition hooks on my app.run.
Based on this answer, i created a TransitionService to manage application transactions and keep track of what transactions are running on application in order to guarantee that only one transaction happens at a time. I achieved this by saving the current transaction on TransitionService and then aborting any previously saved transaction on every new transaction.


qt-3: Make configureFlags a list

Motivation for this change
This is cleaner, and makes it easier to limit rebuilds while editing the flags.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Qt 3.3 is from February 2004. I think it's time we drop it from our repository. I see 2 applications using it, lprof, which should be able to use a newer version, and an old version of taskjuggler.

Regarding lprof. Seems Qt4 support was merged in CVS, but there has not been any release with it.

I think I'll merge this now to help with my proposed configure flags deprecation, but yes I approve of just deleting Qt 3 too.


Change targets from list to map

Resolves #53

I'll merge this just before the next release, so people don't get confused if they installed the old version and are looking for documentation


ci: remove debian buster from pipelines

NR-259631
Debian Buster is going EOL in June, and currently the pipelines where this OS version is used are failing because an archived package repository needs to be used. So we are disabling Buster from the pipelines as it will be unsupported soon. The deb package is generated anyway.

could you add some context to the PR description, I'm not sure why is this change happening

You're right. Done!


unfocus specs

Small PR to close #108.
Focused specs (with fdescribe) were preventing other tests from running.
I don't use Jasmine nor Gulp often, so feel free to ignore if useless.

@smhg thanks for the PR, this actually uncovers a couple failing tests

Thank you!


[C++][Parquet] Decoding byte stream split encoded columns fails when it has null values

Reading from a parquet file fails with the following error
Data size too small for number of values (corrupted file?).
This happens for the case when there is a BYTE_STREAM_SPLIT-encoded column which has less values stored than number of rows, which is the case when the column has null values (definition levels are present).
The problematic part is the condition checked in ByteStreamSplitDecoder<DType>::SetData, which raises the error if the number of values does not match the size of the data array.
I'm unsure whether I have enough experience with the internals of the encoding/decoding part of this implementation to fix this issue, but my suggestion would be to initialize num_values_in_buffer_ with len/static_cast<int64_t>(sizeof(T)).
Reporter: Roman Karlstetter / @romankarlstetter
Note: This issue was originally created as ARROW-13024. Please see the migration documentation for further details.

This problem is now also discussed in more detail here: #15173

I think this can be closed since #34140 was merged.
Could you take a look, @wjones127


Socket event filters should not force returning data

Feathers hooks allow you to return nothing in a hook and just modify data. Event filters should behave the same way. Currently, you must return the data you want to send down the event filter chain.
However, we should still retain the ability to return false to prevent the filter chain from continuing and therefore the event from being dispatched.
This is most likely solved by just adding data === false to these lines:
https://github.com/feathersjs/feathers-socket-commons/blob/master/src/events.js#L57
https://github.com/feathersjs/feathers-socket-commons/blob/master/src/events.js#L84

I'm going to close this since I don't think we'll implement it before the updated event filtering proposal (https://github.com/feathersjs/feathers/issues/388#issuecomment-239564856).

Ya that's cool. If we end up doing what we have planned and make dispatching events the last hook in the hook chain then it pretty much solves this issue anyway.


[BUG] When you delete a host and there's less than three hosts the VMs are lost

Describe the bug

If you delete a host with VMs on it and there's less than three in the cluster it will fail to migrate them to a new host
To Reproduce
Steps to reproduce the behavior:

Create a cluster
Expected behavior

You should either be prompted to move the VMs, or the migration should complete.
Support bundle

harvester-supportbundle_0b1adc6b-9518-4cb6-8044-4353071f75d7_2021-07-16T21-20-36Z.zip
Environment:

Harvester ISO version: master-6ae8d8ee-head
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal with DL160

Additional context
Add any other context about the problem here.

Verified in master-9f917060-head

Created 3 node cluster.
Create a VM which is scheduled to node-2
Delete node-2

Result:
The VM is recreated and running on another node after a period of time


Resolve CVE-2018-1000620 Vulnerability

Update request package to version that no longer requires hawk package (and by extension the vulnerable cryptiles package).
See: https://nvd.nist.gov/vuln/detail/CVE-2018-1000620

Thanks!


prettify conflict bot message

Yes, I think it's a good idea to link to the Wiki Page, :octocat:

sorry i didn't see that wiki page i will do it shortly thaanks @Akshay2996


Ascon News Plugin

Ascon News plugin serves demonstrational purpose and yet it needs further upgrades:

display general news;
store news locally and check their freshness;
display personal news.

Ascon News plugin is ready in its most basic form. This issue can be closed, and the news ones hsould be opened if there's any need for further improvement.
Also, the idea of making http requests in Blazor WASM project doesn't seem very good. It's better to have a separate web service for that case.


DSND-2337: Convert snake case to camel in transform_rules file

Describe the changes

Used regex expressions which I'll pop on the ticket to modify the yml file from snake_case to camelCase.

Related Jira tickets
DSND-2337
Developer check list
General

[y] Is the PR as small as it can be?
[y] Has the Jira ticket been updated with any relevant comments?
[ ] Is the README up to date?
[ ] Has the POM been updated for the latest versions of dependencies?
[ ] Has the code been double-checked against main?
[ ] Does the code adhere standards in this repository, including SonarQube checks?

Testing

[ ] Do the code changes have unit and integration tests with code coverage > 80%?
[ ] Has the code been tested locally and/or passed the API Karate tests on Tilt?
[ ] Have mandatory manual test cases been run?
[ ] Are extra Karate tests required?
[ ] Are all the test data resources up to date?

Release preparation
Where possible, add links to the respective Jira tickets when an item is checked

[ ] Have these changes been included in a release ticket?
[ ] Are changes required to the docker-chs-development deployment or test data?
[ ] Are any changes required to the environment added to chs-configs?

Notes to the tester
Add any testing hints or instructions here.

CI: No security warnings found

CI: No security warnings found


Team update - Mar 01, 2023

This is a @Quansight-Labs/czi-a11y-grant team sync 🎉🎉🎉! This is a way for the Team Members to provide status reports on what they've been up to this week and request help and attention for things they are working on. This issue will be closed at the end of the day.
Copy and paste the template below, and answer questions as you wish!

Response Template
**Thanks I'd like to give 🙌**
- So-and-so helped me out a lot with foo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...

**My availability for next week**
- I'll be off on foo day...

**Important items for discussion 💬**
- I have a question about goal <link-to-goal>
- Can @foo give a comment on issue #NN ?
- I opened #NN for discussion, please chime in
- I need to discuss foo

:mag: Needs Triage
The Needs Triage issues require an initial assessment and labeling.
No issues need triage! 🎉
:dart: Project boards
Please make sure the boards reflect the current status of the project.
Jupyter a11y grant project

Updates from last week :heavy_check_mark:

I'm working on the GSoD proposal - I hope to have a draft ready to share by tomorrow.
I started reviewing the themes extension

Challenges I faced and things I'd like assistance with 🙏

I'm ok!

My availability for next week

I'll be here

Important items for discussion 💬

I don't have anything for today

Thanks I'd like to give 🙌

Thank you to @steff456 for submitting the conference proposal!
Thanks to @gabalafou for user testing script review!

Updates from last week :heavy_check_mark:

#184 I've been updating the draft script based on feedback and made the requested interest form.
Notebook authoring tips draft is not a public PR. I also have been turning this into slides and a review checklist for the upcoming STScI hackathon.

Challenges I faced and things I'd like assistance with 🙏

I don't think I have anything now.

My availability for next week

I'll be here all week.

Important items for discussion 💬

I don't think I have anything now.

Thanks I'd like to give 🙌

@isabela-pf for creating Google doc to put down our goals through the end of the grant.

Updates from last week :heavy_check_mark:

I worked towards deliverable: https://github.com/Quansight-Labs/jupyter-a11y-mgmt/issues/168. I know I said I would have the PR up before now, but I kept running into little issues and playing whack-a-mole. I promise this is going up today as PR against the JupyterLab repo.

Challenges I faced and things I'd like assistance with 🙏

This PR isn't getting attention and has a merge conflict with master yet again: https://github.com/jupyterlab/jupyterlab/pull/13577

My availability for next week

I'll be here!

Important items for discussion 💬

Nothing from me today.

@steff456
- Submitted SciPy proposal
- Working on Google Season of Docs proposal - missing metrics and will share for review
- Deadline is the 24th of March -> need to share this with JLab folks at the next team meeting (8th of March)
- Move onto the theming extension right after the 1st draft of the season of docs submission

@isabela-pf
- Run through the testing scripts w/Gabriel and Stephannie and made changes/adjustments
- Working on notebook authoring guidelines and checklist -> next, finish synthesising learnings from user testing
- Wrap up tasks for user testing: scripts, email with w/our details, and consent form

@gabalafou
- 🎉 🎉 Getting his tab-trap up in JupyterLab 🎉 🎉
- Lab - there is a feature freeze already
- @trallard to ping Dharhas and Mike to review the nightmare PR on focusable elements
- demo on the focus visible around the notebooks cells


check for variants of baseline parameter in config

There are config files that have the parameter string Baseline instead of BaseLine.
See http://calib.stereolabs.com/?SN=4353 for an example.
I included a fix that checks which variant of the baseline parameter is present and loads accordingly.
Furthermore, I marked the zed_cpu_ros_node as required in the launch file such that roslaunch kills all other nodes if an error occurs in this node.

Can you rebase all your commit into one for simplicity?
Thanks.
ref: https://www.atlassian.com/git/tutorials/rewriting-history

Hey,
I did the changes. Please check :)

Great! Thanks


make all configs setable through environment variables

Right now the TLS configs take paths rather than the contents of the certificates themselves. I don't know if anything else is missing right now and I didn't see a list of the names of the environment variables in the docs.

Ah sorry, it's mentioned in https://github.com/docker/notary/blob/master/docs/running_a_service.md#overriding-configuration-file-parameters-using-environment-variables, but not linked from the actual config references themselves.  We should probably duplicate that.
And apologies, could you also clarify what this issue is requesting?  I wasn't sure how to interpret the description:

Accept the contents of TLS certs in environment variables?  (as was discussed IRL?)
Accept the whole configuration via 1 environment variable?  (if so, should individual fields still be listable?)
Document which environment variables can override the config?

Ah, yes, sorry, I didn't know if all configs are editable through environment variables. That's what I was referring to. There's no need to take the entire config as one environment variable if each individual field is configurable already through the environment. Feel free to open a separate issue for the documentation issue.


improve coreg report plot

looks now like this:

Looks like a missing back somewhere:
WARNING: py:class reference target not found: mne.Report`can plot coregistration results. This is
very useful to check the quality of the :term:`trans

Nice!! @agramfort care to add a tiny changelog entry?

Thanks @agramfort!


resolve.alias works with Vite dev/build, but not Vitest

Describe the bug
Using resolve.alias from Vite, I am able to use MUI with styled-components.  However, I am unable to run Vitest tests with it.  (Tried using test.alias as well, but had the same results.)
I might be misunderstanding something, but my expectation is that Vitest resolves to the alias provided in the Vite config.
MUI docs for using styled-components https://mui.com/material-ui/guides/styled-engine/ for some additional info on how it is done with a few other tools.
Reproduction
https://stackblitz.com/edit/vitejs-vite-3kqcme?terminal=dev

Open the link.
Run build or dev and see that it works and renders an element with the text 'Box'.
Run test and see that it throws an error.

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (4) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.10 - /bin/yarn
    npm: 7.17.0 - /bin/npm
  npmPackages:
    @vitejs/plugin-react: ^2.0.0 => 2.0.0
    vite: ^3.0.1 => 3.0.2
    vitest: ^0.19.0 => 0.19.0

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Found https://github.com/vitest-dev/vitest/issues/1562 which is the same issue.


[C/inference] Use allowed_elements instead of restricted-elements

The name 'restricted-elements' of nnstreamer configuration is not
matched as its real operation. Because of this reason, its name is
renamed to 'allowed_elements'. This patch updates the related code.
Signed-off-by: Sangjung Woo<EMAIL_ADDRESS>Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Required PR

https://github.com/nnstreamer/nnstreamer/pull/3635

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #128. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @again4you, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/128-202201061935190.89205598831177-1633228c1306a3496db8290610961e569c1d4a2d/.


feature roadmaps are all using the earliest sprint and showing it as the current sprint

We noticed this on the last day of the sprint, not sure if it is a bug or how the last day of the sprint is presented
Browser
Choose a browser
[ ] IE11
[x ] Chrome
[ ] FireFox
[ ] Safari
Version
[ ] Azure DevOps/VSTS
[x ] TFS 2017 Update 2/3
[ ] TFS 2018
Screenshots
If applicable, add screenshots to help explain your problem.

Currently seeing this problem. Was it ever resolved?

Sorry, but this code in this repo is not currently being maintained. We recommend you use the Delivery Plans feature that is core to Azure DevOps.


gdnative-bindings is not rebuilding when changes are made to api.json

build.rs should be updated to depend on api.json
println!("cargo:rerun-if-changed=api.json");

Probably introduced by #471?


404 On Your Headline

I'm getting a 404 from the link mentioned here

Thanks for the report, fixed on master.


Fix image export in ImageViewer

Fix image export in ImageViewer:

Expand export function: (current image | all images)
Check .IsCreationSupported flag

Edit menu:

Current image export (both single image format and container format):

All images export (only container format):

Fix #246

Saving as IMGD appears to swap color channels. Other formats work well.

Oh this B⇔R channel swapping problem is serious. I'll check this.

As of the latest commit, the B⇔R swap appears to be fixed, however .bmp extraction creates a broken image that crashes the viewer. The image will open with traditional image viewers, but it displays incorrectly.

For now I'll go ahead and merge this, as every format except bmp works as expected. This is unimportant right now and can be fixed at a later time down the line.


Moved all notebooks to docs/notebooks.

Now all notebooks are in the same place, thus all are subject
to auto-doc generation at readthedocs.io and to automated testing
with travis.
Some notebooks are too slow, exclude them at docs/conf.py:exclude_patterns.
Cleanup a bit the section headings in notebooks so that they show
up well in readtehdocs.io.

It looks like the notebooks touched in this PR are deleted from notebooks/ but not added to docs/notebooks/?

It looks like the notebooks touched in this PR are deleted from notebooks/ but not added to docs/notebooks/?

Good catch, added now


💬 [Question] Should We Send A Notification Mail To Remind To Contribute?

💬 Question

Should We Send A Notification Mail To Remind To Contribute?

The sending can be switched off for sure.
This is to help the users to develop a habit.

Yes!


Add more / make changes to the topics for the .topic command

Description

I think it would make sense to review the current questions we have in the py_topics.yaml file and make appropriate additions/corrections.
Reasoning

I think that the .topic command is really cool and engages members more in the topical channels as well as py-gen. I don't check those channels often, but from what I've seen, .topic is used quite frequently so I think it makes sense to keep it that way.
Proposed Implementation

I think I said everything in the description.
Would you like to implement this yourself?

[x] I'd like to implement this feature myself
[ ] Anyone can implement this feature

(If you have any ideas for making changes to the topics, please post a comment on this issue and I will consider them!)

You're welcome to make suggestions for new topics. Let's keep them on the issue and discuss, and once semi-finalized a PR can be raised?

Yep, that sounds like a good idea. 👍

Let's start with the ones that don't already have topics.
For #algos-and-data-structs:

What is a good algorithm that you know in Python? (might need to be reworded, that sounds a bit weird)
What are some advantages of NumPy arrays over Python lists?
What do you know and/or understand about inheritance in Python?
What are some benefits of modules in Python?

For #c-extenstions:

What is a good C extension you would recommend?
How would you go about coding your own C extension in Python?

For #software-design:

What is a cool software design you know and/or created yourself that you would recommend?

For #type-hinting:

What are the pros and cons of type hinting in Python?
How can you tell when you need to type hint in your own code?

For #unit-testing:

How often do you run unit tests on your projects? Do you think they are necessary? Why or why not?
How do you write a unit test in Python?
What are the best Python unit testing frameworks?
What are some best practices for Python unit testing?
What is the difference between Pytest and Unittest?

That's all I have for now. The other channel that doesn't have any topics currently is #data-science-and-ai. If anyone comes up with any topic ideas for that channel, please post them on this issue!

@minalike Would it be ok with you if I started a PR with the above changes? This issue has been around for quite a bit now and nobody else has suggested anything.

I am of the impression that the .topic command best serves its purpose in python-general and the off-topic channels. I think for the topical questions adding more questions wouldn't be of much use. But that's going but my gut, I haven't actually searched for invocations of the command.

After gathering some internal feedback, we feel the usage of the topic command outside of python-general, off-topic, and occasionally discord-bots is not high enough to require additional topics. While there is no harm in adding more, the current suggestions aren't compelling enough to add to the current list.
We do have interest however, in boosting the current topic questions for our more traffic-heavy channels where the command is invoked frequently making the existing topics very repetitive. Users can make suggestions here: https://forms.gle/oMDNk98oZ8GJoF6XA


Livereload Reloading All the Paths

Recently migrated a project from middleman 3 to 4. Livereload is working, however, it is reloading all of my haml files and not just the changed file.
I change careers.html.haml and in terminal I see it reloading paths from work/*, explore, contact etc...
Before the migration I would just see the careers page being reloaded in terminal.
config.rb
activate :livereload
Is there a config option I'm missing or is this the correct functionality?
Thanks!

The same for me

Proof:

You can reproduce it easily, using this project: https://gitlab.com/gitlab-com/www-gitlab-com

Unfortunately, we don't have a means of knowing which files of a same-type influence which other files. Our template renderer (Padrino) does not provide a dependency graph. The simplest (and slowest) solution is to reload all files of a type if one changes.

As an aside, there is no full-time maintainer for this extension. I just try keep it from being broken, but never use Livereload when using Middleman for work.
If anyone has time, desire and attention, I'd happily allow them to work on improving Livereload support.

@tdreyno Is there a way to turn off the reload everything behaviour?
Also, somewhat related, where are the files that the reload extension operate on defined?
https://github.com/middleman/middleman-livereload/blob/master/lib/middleman-livereload/extension_3_1.rb#L52
also, I've found a small bug in the ignore option, with a fix here: https://github.com/middleman/middleman-livereload/pull/95


turn process CPU 100%

Soundly the turn server received some bytes not conforming the standards, then the process always running CPU in 100%.
The server log is:
listening <IP_ADDRESS>:20011...
Waiting for Ctrl-C...
[2021-04-08T23:13:45Z DEBUG webrtc_turn::server::request] received 407 bytes of udp from <IP_ADDRESS>:5088 on <IP_ADDRESS>:20011
[2021-04-08T23:13:45Z DEBUG webrtc_turn::server::request] handle_turn_packet
[2021-04-08T23:13:45Z ERROR webrtc_turn::server] error when handling datagram: 4f4e5320 is invalid magic cookie (should be 2112a442)

Version: webrtc-turn v0.1.2

Thanks for reporting this issue. Will take a look soon.

Looks likely the problem exists always, when started the example server, it appears.
   Compiling webrtc-turn v0.1.3 (/Users/clia/github.com/webrtc-rs/turn)
    Finished dev [unoptimized + debuginfo] target(s) in 43.97s
     Running `target/debug/examples/turn_server_udp --public-ip <IP_ADDRESS> --users user=pass`
[2021-04-09T03:04:21Z TRACE mio::poll] registering event source with poller: token=Token(1), interests=READABLE | WRITABLE
listening <IP_ADDRESS>:3478...
Waiting for Ctrl-C...

@clia, looks like it is due to the following code piece. I need to figure out a better way to handle Ctrl-C signal.
let running = Arc::new(AtomicBool::new(true));
    let r = running.clone();

    ctrlc::set_handler(move || {
        r.store(false, Ordering::SeqCst);
    })
    .expect("Error setting Ctrl-C handler");

    println!("Waiting for Ctrl-C...");
    while running.load(Ordering::SeqCst) {}
    println!("\nClosing connection now...");

fixed this issue in commit: e14fbebac58f0f03fe7a08cc2c6f96425317c285

👍


Nexus 7 emulator flagged as rooted

Hi, using a fresh copy of the standard nexus 7 emulator in avd and your sample app it gets flagged as rooted:

I've tested it with android 7.0, 7.11, 8.0 with the same result.
Android 12 also claims to be rooted but with a different result:

even though the su file is there in system/xbin/:

Log for 7-8:
2022-05-11 11:45:43.447 4596-4596/com.scottyab.rootbeer.sample V/RootBeer: RootBeer: checkForBinary() [193] - /system/xbin/su binary detected!
2022-05-11 11:45:43.484 4596-4596/com.scottyab.rootbeer.sample V/RootBeer: RootBeer: checkForDangerousProps() [283] - ro.debuggable = [1] detected!
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/bin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/xbin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /sbin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /su/bin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/.ext/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/failsafe/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/sd/xbin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/usr/we-need-root/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/xbin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /cache/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /dev/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/sbin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /vendor/bin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /vendor/xbin/su Absent :(
2022-05-11 11:45:43.495 4596-4596/com.scottyab.rootbeer.sample I/zygote: Deoptimizing boolean kotlin.jvm.internal.Intrinsics.areEqual(java.lang.Object, java.lang.Object) due to JIT inline cache
2022-05-11 11:45:43.484 4596-4596/com.scottyab.rootbeer.sample V/RootBeer: RootBeer: checkForDangerousProps() [283] - ro.debuggable = [1] detected!
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/bin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/xbin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /sbin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /su/bin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/.ext/su Absent :(
2022-05-11 11:45:43.485 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/failsafe/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/sd/xbin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/usr/we-need-root/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/xbin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /cache/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /dev/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/sbin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /vendor/bin/su Absent :(
2022-05-11 11:45:43.486 4596-4596/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /vendor/xbin/su Absent :(
2022-05-11 11:45:43.495 4596-4596/com.scottyab.rootbeer.sample I/zygote: Deoptimizing boolean kotlin.jvm.internal.Intrinsics.areEqual(java.lang.Object, java.lang.Object) due to JIT inline cache
2022-05-11 11:45:48.418 4596-4601/com.scottyab.rootbeer.sample I/zygote: Do full code cache collection, code=251KB, data=162KB
2022-05-11 11:45:48.419 4596-4601/com.scottyab.rootbeer.sample I/zygote: After code cache collection, code=251KB, data=139KB
2022-05-11 11:45:50.010 4596-4638/com.scottyab.rootbeer.sample I/zygote: Deoptimizing kotlin.coroutines.CoroutineContext kotlinx.coroutines.internal.DispatchedContinuation.getContext() due to JIT inline cache
2022-05-11 11:45:50.011 4596-4596/com.scottyab.rootbeer.sample I/zygote: Deoptimizing void kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(java.lang.Object) due to JIT inline cache

Logs for 12:
2022-05-11 11:47:49.512 6676-6704/com.scottyab.rootbeer.sample D/EGL_emulation: app_time_stats: avg=16.66ms min=9.55ms max=29.46ms count=49
2022-05-11 11:47:50.516 6676-6704/com.scottyab.rootbeer.sample D/EGL_emulation: app_time_stats: avg=14.50ms min=9.14ms max=24.90ms count=53
2022-05-11 11:47:51.061 6676-6676/com.scottyab.rootbeer.sample V/RootBeer: RootBeer: checkForDangerousProps() [283] - ro.debuggable = [1] detected!
2022-05-11 11:47:51.063 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/su Absent :(
2022-05-11 11:47:51.065 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/bin/su Absent :(
2022-05-11 11:47:51.065 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/local/xbin/su Absent :(
2022-05-11 11:47:51.067 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /sbin/su Absent :(
2022-05-11 11:47:51.068 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /su/bin/su Absent :(
2022-05-11 11:47:51.070 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/su Absent :(
2022-05-11 11:47:51.073 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/.ext/su Absent :(
2022-05-11 11:47:51.076 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/bin/failsafe/su Absent :(
2022-05-11 11:47:51.077 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/sd/xbin/su Absent :(
2022-05-11 11:47:51.080 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/usr/we-need-root/su Absent :(
2022-05-11 11:47:51.081 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system/xbin/su Absent :(
2022-05-11 11:47:51.082 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /cache/su Absent :(
2022-05-11 11:47:51.083 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /data/su Absent :(
2022-05-11 11:47:51.085 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /dev/su Absent :(
2022-05-11 11:47:51.085 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /product/bin/su Absent :(
2022-05-11 11:47:51.086 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /apex/com.android.runtime/bin/su Absent :(
2022-05-11 11:47:51.087 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /apex/com.android.art/bin/su Absent :(
2022-05-11 11:47:51.088 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /system_ext/bin/su Absent :(
2022-05-11 11:47:51.090 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /odm/bin/su Absent :(
2022-05-11 11:47:51.092 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /vendor/bin/su Absent :(
2022-05-11 11:47:51.093 6676-6676/com.scottyab.rootbeer.sample I/RootBeer: LOOKING FOR BINARY: /vendor/xbin/su Absent :(
2022-05-11 11:47:51.518 6676-6704/com.scottyab.rootbeer.sample D/EGL_emulation: app_time_stats: avg=14.07ms min=5.88ms max=48.83ms count=46

@scottyab Hi there, faced the same issue, all standard android studio emulators detect as rooted. Is this an expected behavior?

Emulators are usually rooted so I think this is probably expected behaviour.

Sorry for the slow reply. This is working as expected but we should include a FAQ note about emlators to confirm this.

Emulators are usually rooted so I think this is probably expected behaviour.

I'm not sure it's correct to say emulators are usually rooted. However they are debuggable and this system property 'ro.debuggable' is classed as a dangerous property so it's flagged as an indication of root. dangerous maybe a little OTT but it's certainly not something expected on a genuine device.


[build] Roll boringssl to latest commit

Boringssl now has built-in bazel support, so we no longer have to use a commit from main-with-bazel instead of the primary branch. A few code changes are needed based on the RSA struct now being opaque, which is why we deferred updating this so far.

This is failing //src/workerd/api/node:tests/crypto_dh-test because of https://boringssl-review.googlesource.com/c/boringssl/+/62226 or https://boringssl-review.googlesource.com/c/boringssl/+/62228, which reject some input parameters. We could still update to c08ccc9ed166a82b92edd70ab215ae1f2501e838, but that's a much smaller update. Moving this back to draft stage.


Boundary flux calculation is incorrect for non-absorb BCs

Currently the boundary flux calculation is done by performing a surface update on the skin cell, a zeroed ghost cell, and blank dummy cell. This gives the surface term at the skin/ghost interface, and a zero flux at the ghost/dummy interface.
For the absorbing wall BC this is correct as the only contribution to the surface term is made by the skin cell distribution. For other BCs, there is a distribution in the ghost cell which should contribute to the skin/ghost surface update as well.
However, doing an update with the ghost cell distribution supplied by the BC causes there to be an additional unwanted surface contribution from the ghost/dummy interface.
Some means of separating the left and right surface term updates is therefore required.

Issue fixed with PR: 2523a14


Command to find config file location.

Alternatively to set values :-) By reflex I've set author to Matthias Bussonnier<EMAIL_ADDRESS>and stugled (a bit) to fix it.

Any time you use it, if you give it a value different from the default, that should become the new default. It's intended to be more like memory than config.


TWTRCompose doesn't store session after signing in - endless loop of signing in / granting permissions instead

After logging in / granting permissions via TWTRCompose, no session is stored / available
Expected behavior
Logging in / granting permissions via TWTRCompose will create a session, so when I try to show the window, I'll be able to send a tweet.
Actual behavior
Trying to open the TWTRCompose only opens Twitter and asks me to grant permissions, over and over again.
Steps to reproduce the behavior
Show a TWTRCompose. Log in / accept permissions.
Try to press the tweet button again to actually send the tweet, and instead go right back to the permissions page

I'll note - the ONLY Twitter functionality I'm looking for in my app is a referral share via Tweet. I'm not trying to use Twitter as authentication or anything. Considering that this TWTRCompose can detect no signed in user and take me to the app to authenticate it, why is it not able to do anything with that action? It seems to me once that login / accepting permissions is completed, it should return me to my app and show the TWTRCompose I was trying to open in the first place.
What are the proper steps to do this, if not signing in / accepting permissions, then opening the compose again?

Facing the exact same issue. Would appreciate some help here :)

@JacobJT Thanks for the quick reply. That did not change the behaviour though :/. Clicking on the button opens the Twitter app where Twitter asks me to authorise my iOS app to read tweets etc. Then when I select "Connect", I am redirected back to my app. Pressing the button again just repeats the same thing (i.e Twitter app launches and I am asked for authorising my iOS app again)

@sushinoya Which block is executing? I imagine the first if?
I'm not sure what else to try. My displayTweet function just does what I put above, except it sets the text and url.  I had the behavior you're experiencing until wrapping that in the if block to check for hasLoggedInUsers and to sign in if there aren't any.

@JacobJT do you mind if I see your code for displayTweet?

        let composer = TWTRComposer()
        composer.setText(<My Text>)
        composer.setURL(<My URL>)
        composer.show(from: self) { result in
            if( result == .done) { print("Successfully composed Tweet") }
            else { print("Must have cancelled...") }
        }

After a bit of debugging (a commented out everything inside the displayTweet method), I realised that it is this line Twitter.sharedInstance().logIn that is causing the loop.
After that neither the if( session != nil ) condition nor the else condition are executed

Try reverting to the previous version, I've seen a lot of comments about it being less buggy. I only had that experience when I was opening the TWTRComposer without checking if I had a logged in user first.  Once I added the line you mentioned, it worked fine.
Only difference I see between what we're doing is that I'm using TWTRTwitter instead of Twitter, so that's my last suggestion.

I already am using an older version
pod 'TwitterCore', '~> 3.0.3'
pod 'TwitterKit', '~> 3.2.2'

I don't have a bridging header though. I thought the pod should do that for the user

I don't use Cocoapods, i use Carthage. Perhaps CocoaPods handles that and it was only an instruction when not using pods?

Like you I'm using the Twitter Kit just for simple tweets and I had this exact issue also, until I implemented the openURL callback in the app delegate:
- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url             options:(NSDictionary *) options {     [[Twitter sharedInstance] application:application openURL:url options:options];     return YES; }
Also note from this article that it's necessary to have a placeholder URL in the configuration of the twitter app in the app.twitter.com dashboard, otherwise the redirect back to your app doesn't happen correctly. Implementing both these points fixed the issue for me.

@nick-sturrock This fixed it for me. Thanks!

@nick-sturrock Does this placeholder need to be a valid deeplink to your app? Or any URL? Is it acceptable to just put my website link there or it meant to be like a backend server call letting me know the action took place?

Just any valid URL will do - they recommended http://placeholder.com in their example, which works for me.

Thanks the

(BOOL)application:(UIApplication *)application openURL:(NSURL *)url options:(NSDictionary *) options { [[Twitter sharedInstance] application:application openURL:url options:options]; return YES; }

worked for me. Although the fist time through it comes back as a blank tweet composer.

The above method accepts url which will work.
Better fix is to update callback URL on apps.twitter.com to add something like:
twitterkit-<consumerKey>://
And instead of returning YES on openURL, you can do normal:
[[Twitter sharedInstance] application:application openURL:url options:options]
This was announced Early May.
https://twittercommunity.com/t/action-required-sign-in-with-twitter-users-must-whitelist-callback-urls/105342

Yup, the only things needed is do folow Twitter documentation and add the function below, a simple copy paste:
func application(_ app: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey : Any] = [:]) -> Bool {
     return TWTRTwitter.sharedInstance().application(app, open: url, options: options)
}


[Misc]: RuntimeError: CUDA error: invalid configuration argument

Anything you want to discuss about vllm.
I am not sure if this should be a bug report, this is why I am starting by submitting this as a discussion.
We are running vllm on 4 gpus via Kubernetes. Information about the enviroment:

The output of `python collect_env.py`
Collecting environment information...
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.31

Python version: 3.12.6 (main, Sep 10 2024, 00:05:17) [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-119-generic-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA TITAN RTX
GPU 1: NVIDIA TITAN RTX
GPU 2: NVIDIA TITAN RTX
GPU 3: NVIDIA TITAN RTX

Nvidia driver version: 550.107.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Byte Order:                           Little Endian
Address sizes:                        46 bits physical, 48 bits virtual
CPU(s):                               20
On-line CPU(s) list:                  0-19
Thread(s) per core:                   2
Core(s) per socket:                   10
Socket(s):                            1
NUMA node(s):                         1
Vendor ID:                            GenuineIntel
CPU family:                           6
Model:                                85
Model name:                           Intel(R) Xeon(R) W-2155 CPU @ 3.30GHz
Stepping:                             4
CPU MHz:                              3300.000
CPU max MHz:                          4500.0000
CPU min MHz:                          1200.0000
BogoMIPS:                             6599.98
Virtualization:                       VT-x
L1d cache:                            320 KiB
L1i cache:                            320 KiB
L2 cache:                             10 MiB
L3 cache:                             13.8 MiB
NUMA node0 CPU(s):                    0-19
Vulnerability Gather data sampling:   Mitigation; Microcode
Vulnerability Itlb multihit:          KVM: Mitigation: VMX disabled
Vulnerability L1tf:                   Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
Vulnerability Mds:                    Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:               Mitigation; PTI
Vulnerability Mmio stale data:        Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Mitigation; IBRS
Vulnerability Spec rstack overflow:   Not affected
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; IBRS; IBPB conditional; STIBP conditional; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Mitigation; Clear CPU buffers; SMT vulnerable
Flags:                                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req md_clear flush_l1d arch_capabilities

Versions of relevant libraries:
[pip3] flashinfer==0.1.6+cu121torch2.4
[pip3] numpy==1.26.4
[pip3] nvidia-cublas-cu12==<IP_ADDRESS>
[pip3] nvidia-cuda-cupti-cu12==12.1.105
[pip3] nvidia-cuda-nvrtc-cu12==12.1.105
[pip3] nvidia-cuda-runtime-cu12==12.1.105
[pip3] nvidia-cudnn-cu12==<IP_ADDRESS>
[pip3] nvidia-cufft-cu12==<IP_ADDRESS>
[pip3] nvidia-curand-cu12==<IP_ADDRESS>
[pip3] nvidia-cusolver-cu12==<IP_ADDRESS>
[pip3] nvidia-cusparse-cu12==<IP_ADDRESS>
[pip3] nvidia-ml-py==12.560.30
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] nvidia-nvjitlink-cu12==12.6.68
[pip3] nvidia-nvtx-cu12==12.1.105
[pip3] pyzmq==26.2.0
[pip3] torch==2.4.0
[pip3] torchvision==0.19.0
[pip3] transformers==4.44.2
[pip3] triton==3.0.0
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.6.1.post2@
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    GPU2    GPU3    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NV2     SYS     SYS     0-19    0               N/A
GPU1    NV2      X      SYS     SYS     0-19    0               N/A
GPU2    SYS     SYS      X      NV2     0-19    0               N/A
GPU3    SYS     SYS     NV2      X      0-19    0               N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

The loaded model is "Hermes-3-Llama-3.1-70B.Q5_K_M.gguf" with tools enabled. The tools functionality is what we are looking into. Using "models--NousResearch--Hermes-3-Llama-3.1-8B" works fine but does not work as great as the openai models so we wanted to try a larger model. But the larger model randomly crashes but I have no idea what the logs are trying to say:
vllm error.log
I searched the available issues for similar errors, but the once I found were showing stacktraces at different places and also marked as solved. I could not get the input dump since I deleted the container while rolling back to the 8B model.
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

NVIDIA TITAN RTX

can you try to run it on more recent gpus?

Unfortunately for now only those are available to me


Brainstorm for More DRC Checks

Right now we have the following checks:
These checks are meant to check a certain function in SpyDrNet-TMR:

drc_apply_nmr - meant to be run right after calling apply_nmr() to see if what we specified to be replicated was actually replicated.
drc_surface_pins - meant to be run right after calling surface_pins(). Checks to see if the pins specified to be surfaced were actually surfaced.
drc_uniquify_nmr_property - meant to be run right after calling uniquify_nmr_property(). Checks to see if the instances' properties were actually uniquified.
drc_insert_organs - meant to be run right after calling insert_organs(). Makes sure that voters are where we said we wanted them and that they are wired up correctly.

These are meant to be run after finishing replicating and modifying a design:

drc_connections_after_replication_and_insertion - this check is like a final check of the connections in the replicated design compared to the connections in the original design. This acts as a check for replication and organ insertion.
drc_properties_after_replication - can be run anytime after replication. Makes sure properties of instances in the replicated design match up to the corresponding instances in the original design.

The documentation has additional info about these checks. They seem to work well, but of course they can always use more testing.
Now we want to see if there are any other DRC checks that can be written and implemented.

Some Ideas:

make sure that if ports aren't replicated buffers are also not replicated


The image build locally can not work!

I followed the official markdown document, but i do not know the reason causing this problem.

Tried your process but didn't get the same result. can you provide more information

Tried your process but didn't get the same result. can you provide more information

Tried your process but didn't get the same result. can you provide more information

I followed the official markdown document, but i do not know the reason causing this problem.

Tried your process but didn't get the same result. can you provide more information

I followed the official markdown document, but i do not know the reason causing this problem.

 Tried your process but didn't get the same result. can you provide more information

Could u push this image tu dockerhub, and i pull it for testing?

I followed the official markdown document, but i do not know the reason causing this problem.

 Tried your process but didn't get the same result. can you provide more information

Could u push this image to dockerhub, and i pull it for testing?

The current situation is normal, because the manager needs to specify kubeconfig to start and the corresponding kubeconfig is not specified here

got it, but when i kubectl apply /Jobflow/deploy/jobflow.yaml, the jobflow-controller pod meets problem of "Back-off restarting failed container", and then i logs the pod, showed error of the last line in the picture.

 got it, but when i kubectl apply /Jobflow/deploy/jobflow.yaml, the jobflow-controller pod meets problem of "Back-off restarting failed container", and then i logs the pod, showed error of the last line in the picture.

Since the alpine base image is used here, the manager needs to be statically compiled. You need to set go env CGO_ENABLED="0".The above are all caused by not using static compilation.

 got it, but when i kubectl apply /Jobflow/deploy/jobflow.yaml, the jobflow-controller pod meets problem of "Back-off restarting failed container", and then i logs the pod, showed error of the last line in the picture.

I will add these in the makefile, thanks

thanks for your help, and after u update the makefile, can u let me know and i can re-pull it again! Thanks a lot

@huangyufeng0507 you can retry now, thanks for your feedback.

first, you shold make build the project and prodect  bin/manager file , then docker build it


GN-4323: Make document public

Overview

Makes DocumentContainer and EditorDocument publicly accessible to enable querying for snippet content, which is stored in EditorDocument.
Connected issues and PRs:
Insert snippet JIRA - https://binnenland.atlassian.net/browse/GN-4323
Pending PR in plugins - https://github.com/lblod/ember-rdfa-editor-lblod-plugins/pull/165
Setup

Usual launch with docker, make sure the migration runs, running the SPARQL query publicly
PREFIX dct: <http://purl.org/dc/terms/>
PREFIX pav: <http://purl.org/pav/>
PREFIX ext: <http://mu.semte.ch/vocabularies/ext/>
SELECT (COUNT(?snippetDocument) AS ?count)
WHERE {
    ?snippetList a ext:SnippetList ;
  		ext:hasSnippet/pav:hasCurrentVersion ?snippetDocument .
}

Should now give you the correct count
Challenges/uncertainties

My first time writing a SPARQL migration, please check it thoroughly 😅 it did work locally...

Unrelated to this specific pr, but i'm not gonna go hunt for the pr that introduced it
in the translatation files, the fragment-plugin.modal.alert.error-intro key references the Vlaamse Codex (Flemish Codex) which has nothing to do with this plugin.

wow I didn't realize I posted that comment in the backend PR :joy: sorry about that, but the translation is good

@dkozickis I suppose we can close this one off?


(in progress) SignomialEquality constraints and methods

This is a PR in progress for @mopg and bscohen to work on signomial programming algorithms -- with a particular focus on dealing with equality constraints.
@bqpd, I hacked together an initial prototype but this could use your eyes -- suggestions welcome on how to do this right.
The code we used this morning to test was
from gpkit import Variable, Model, SignomialsEnabled
x = Variable("x")
y = Variable("y")
ymin = Variable("y_{min}", 4)

with SignomialsEnabled():
    c = SignomialEquality(x, y + 1)

m = Model(x, [c,
              y >= ymin])

#m.localsolve(x0={"x": 1, y: 1})
sol = m.localsolve()

@bqpd, what's the best way to look at the convergence of the SP iterations? There are (surprisingly?) None Types mixed in with the gps:
[type(gp.result) for gp in sol.program.gps]
returns
[NoneType, dict, NoneType, dict, NoneType, dict, dict, dict]

test this please

test this please

Should we implement all four kinds of eq constraints, or just the linearize-both-sides one?

In a production version I would choose one (the linearize-both-sides). However, I think a little bit more testing needs to be done on how well that one performs, before deciding to use it.

Hmm, that seems like an argument for implementing all four (or at least a couple) so that the user can choose...

If the implementation in #743 of just the full linearizer looks alright, I'll close this PR (but keep the branch)


Fix CircleCI docker volumes cleanup

Associated change in st2-packages: https://github.com/StackStorm/st2-packages/pull/481
Recently we got more failed builds. After more investigation it was "No space left on device" errors which resulted that mongodb, rabbitmq, postgresql failed to start.
See: https://discuss.circleci.com/t/no-space-left-on-device-while-creating-mongo/11532/13 for more context.
Fixing "No space left on device" in CircleCI infrastructure via additional Cleanup, caused by volumes persisting between the builds.

Good catch :+1: