Cannot get recording working

I'm in Unity 2019.2.14f1 .. I did follow the steps of removing the "direct to camera" setting and adding OpenVR....everything appears to be working as far as the scene goes but hitting the trigger does not record anything, thus I tried to use recorder manually and the anim files that it creates don't see to do anything except twitch the model around without actually doing any hand or body movements. Any ideas?

@Ace71425 had similar issue myself trying this out... Honestly, bought a kinect v2 and used nimate w/ blender. The kinect works great for general body movements and excellent for facial mocap with lipsync (if you pay for brekel face app). Ultimately though could get just as much done body wise with AutoRigPro now that is a worthwhile purchase for sure!

Yeah ive been at this for years and I was recently rejuvenated by seeing this project..my thought was that if I can use an open source add on in unity like this and combine it with kinect to VR software to combine the power of the rift and the kinect and then contribute to the project and tweak the code myself i could have a pretty accurate mocap attachment to every unity project...but i cant even get this thing to record animations let alone see if it can accept Kinect sensors in steamVR and then further develop the prediction calculations

@Ace71425 Honestly, OpenMocap is cool but seems to essentially be just VR tracking hooked up with Inverse Kinematics and some associated leg movement animations.  I've nearly the exact thing accomplished for Oculus devices on youtube, I think the user 'Valem' put something out in that regard. I also recently used an opensource project with SteamVR that works very well on the Index or Vive (no additional trackers needed either) https://github.com/WireWhiz/VR-Instincts.  Going back to non-real-time, the kinect's limitation on recording mostly forward facing movement is easily overcome by using it to just record the natural jitter most people have when moving or standing, and  transferring the info to a AutoRigPro armature. I usually do that and then add on any 360 limb or body rotations ontop the end result is indistinguishable IMO. Still, sounds like you're looking for more of an in-engine real-time solution. If you ever end up going the non-real-time route and would like any tips n tricks in blender for the setup hit me up (ChunkyToads#8868 on discord).  I've kept thorough notes and have utilized it regularly on a variety of models. For now good luck.
On Mon, Aug 3, 2020 at 11:57 PM Ace71425<EMAIL_ADDRESS>wrote:
Yeah ive been at this for years and I was recently rejuvenated by seeing this project..my thought was that if I can use an open source add on in unity like this and combine it with kinect to VR software to combine the power of the rift and the kinect and then contribute to the project and tweak the code myself i could have a pretty accurate mocap attachment to every unity project...but i cant even get this thing to record animations let alone see if it can accept Kinect sensors in steamVR and then further develop the prediction calculations—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yeah I'm not married to any specific idea I just have a kinect and a rift
and would love to find a good solid solution for motion capture...a blender
solution would be great too...i sent you a discord friend request would be
interested to hear about your setup
On Tue, Aug 4, 2020, 11:47 AM ChunkyToads<EMAIL_ADDRESS>wrote:

@Ace71425 https://github.com/Ace71425 Honestly, OpenMocap is cool but
seems to essentially be just VR tracking hooked up with Inverse Kinematics
and some associated leg movement animations.  I've nearly the exact thing
accomplished for Oculus devices on youtube, I think the user 'Valem' put
something out in that regard. I also recently used an opensource project
with SteamVR that works very well on the Index or Vive (no additional
trackers needed either) https://github.com/WireWhiz/VR-Instincts.  Going
back to non-real-time, the kinect's limitation on recording mostly forward
facing movement is easily overcome by using it to just record the
natural jitter most people have when moving or standing, and
transferring the info to a AutoRigPro armature. I usually do that and then
add on any 360 limb or body rotations ontop the end result is
indistinguishable IMO. Still, sounds like you're looking for more of an
in-engine real-time solution. If you ever end up going the non-real-time
route and would like any tips n tricks in blender for the setup hit me up
(ChunkyToads#8868 on discord). I've kept thorough notes and have utilized
it regularly on a variety of models. For now good luck.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexismorin/OpenMocap/issues/3#issuecomment-668675222,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALC2RG6DMBDECH4QGVC32O3R7AUQVANCNFSM4PT5VNRQ
.


Updated from v0.9.3 to v1.0.0-pre2  and key words dont work.

Ahoy
Massive fan of the web UI, we use it daily for admin tasks!
One of the key features we use is looking up key words used in chat/commands, but this seems to not work at all in 1.0.0-pre2, is this environment based?

Hi, there certainly were a lot of updates to the program since v0.9.3. The search query was completely revamped, and that may have been causing people quite a lot of trouble searching the chats.
I will look through it the next time I can look into the program

Thanks, I backdated to the old web UI for now so we can search for things.

Bump @chuushi


please upgrade hassio-cli to latest version

Hi.
Did upgrade today and i have

core-ssh:~# hassio -v
hassio version 1.3.1

and there is 1.4 out sins 22/9
BR

seems there is a issue with ha reboot command

core-ssh:~# hassio ha info
{
"result": "ok",
"data": {
"version": "0.81.0",
"last_version": "0.81.0",
"machine": "raspberrypi3",
"image": "homeassistant/raspberrypi3-homeassistant",
"custom": false,
"boot": true,
"port": 8123,
"ssl": true,
"watchdog": true,
"wait_boot": 600
}
}
core-ssh:~# hassio ha restart
Error decoding json invalid character ':' after top-level value: 403: Forbiddencore-ssh:~#

1.4 is out a long time: https://github.com/home-assistant/hassio-addons/commit/c47b3673ded481dc04dc7ba653cb0b56f593ff66


Code not working

I got the code:
I ran the command: 'py read.py' in step 6 of the setup, and I got this. Is this code broken???
Traceback (most recent call last):
File "C:\Users\kaywa\OneDrive\Desktop\notion-crypto-integration-main\read.py", line 102, in
MyIntegration().UpdateIndefinitely()
File "C:\Users\kaywa\OneDrive\Desktop\notion-crypto-integration-main\read.py", line 20, in init
self.getDatabaseId()
File "C:\Users\kaywa\OneDrive\Desktop\notion-crypto-integration-main\read.py", line 31, in getDatabaseId
self.my_variables_map["DATABASE_ID"] = response.json()["results"][1]["id"]
IndexError: list index out of range

Hello, there here's a video tutorial I've recorded to show how to get this to work.
https://drive.google.com/file/d/1Rd5NjGDTu-BNWJjTP_Ip3rJMtLpybLwC/view?usp=sharing
Hope this clarifies it all :)

I am closing this as it has evidently been working. Feel free to reopen if necessary.


Remove maxOccurs="unbounded" for all elements inside sequence

Because it's already implicit.
Example:
	<xsd:complexType name="UIDGroupDefinitionsType">
		<xsd:complexContent>
			<xsd:extension base="complexBaseType">
				<xsd:sequence>
					<xsd:element maxOccurs="unbounded" name="UIDGroupDefinition" type="UIDGroupDefinitionType"/>
				</xsd:sequence>
				<xsd:attribute name="uID" type="xsd:string" use="optional"/>
			</xsd:extension>
		</xsd:complexContent>
	</xsd:complexType>

here maxOccurs could be removed without change in semantics.

Default for maxOccurs is 1, therefore no need to change anything.
Alternatively you can set maxOccurs on the sequence element to avoid children attributes.


Make 'helm install' quieter by default

As @jchauncey pointed out, the default helm install command prints the JSON output to STDOUT, which is sort of excessive. Especially for larger charts. We should suppress this, probably exposing it under the current debug,v flag.

Another option might be to change the output quantity via a similar route that kubectl uses. kubectl allows you to define the output type which then in turn shows ALL info or a subset (consider the output you get from json vs wide).
-o, --output="": Output format. One of: json|yaml|wide|name|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See golang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template [http://releases.k8s.io/release-1.1/docs/user-guide/jsonpath.md].

@sgoings we do something similar for helm info
Example: helm info alpine --format='{{.}}'


Can't query google drive/storage external tables

Dataform uses a service account for accessing BigQuery, trying to query a external table that lives in Google Drive results in the error:
ApiError: Access Denied: BigQuery BigQuery: No OAuth token with Google Drive scope was found.

This is now fixed, provided the user has enabled the Google Drive API in their Google Cloud project and given access for the drive sheet to the service account.


MacOS installation guidelines

Nice project, thanks!
Could you insert MacOS guidelines?
If you agree, I can make a pull request.
Hi!
Lewix

Hello lewixlabs, thank you for your interest in collaborating with the theme. I didn't add the guide for MacOS because I don't have one for testing. If you want to make a Pull Request feel free, Ok? I believe it is the same as installing on Linux.

Hi @gabrielcaussi
in MacOS path is different:
/Applications/Arduino Pro IDE.app/Contents/Resources/app/plugins/themes
In this path I added dracula.json file and I restarted Arduino Pro.
Last I pressed CMD+K and CMD+T to select dracula theme.
Thanks!
Lewix

Hi lewixlabs!
I just added the information you gave me to install on MacOS to the repository.
Could you check to see if this is it?
Link: https://github.com/dracula/arduino-pro-ide/blob/master/INSTALL.md
Thanks!

Hi lewixlabs!
I just added the information you gave me to install on MacOS to the repository.
Could you check to see if this is it?
Link: https://github.com/dracula/arduino-pro-ide/blob/master/INSTALL.md
Thanks!

Yes, thank you @gabrielcaussi !
Lewix


Add option to ignore issues with certain labels

Add the ability to ignore issues or PRs with certain labels. This is useful in case a bug or enhancement is initially targeted to a milestone but is later closed as wontfix and the milestone isn't removed. Or if you don't want certain issues to show up even if they are in the milestone like chore tasks, questions, etc.

Thanks for the pull request, but I’m not sure that this change is necessary.

Or if you don't want certain issues to show up even if they are in the milestone like chore tasks, questions, etc.

An issue will only be included if it has a label that matches one of the configured sections. With no section for chores or questions, they won’t appear in the release notes.

This is useful in case a bug or enhancement is initially targeted to a milestone but is later closed as wontfix and the milestone isn't removed

This feels like an error in the issue labels and I’m not sure that the generator should try to cope with it. If the error was made the other way so that wontfix was in place when it should not be, such filtering would cause the issue to be missing from the release notes. I think that’s worse than accidental inclusion.
Have I misunderstood the intent of the proposed changes?

@steven-sheehy we'd need some feedback on this one please.

With no section for chores or questions, they won't appear in the release notes.

That highly depends on a project's GitHub templates and workflow. My project does not have a chore issue template so the issue will always be tagged with either bug or enhancement. And in my opinion this is entirely appropriate to have a chore also labeled as an enhancement. A chore is an enhancement that's just minor enough that you don't want to include it in the release notes.
Another possibility is if a project wants to have different release notes for different sub-modules in the same repo but with a common milestone, they could use labels with the module name to filter.
Point is, not everyone manages their project the same way and has different use cases.

This feels like an error in the issue labels and I'm not sure that the generator should try to cope with it.

I disagree otherwise I wouldn't have opened this PR. I inherited a project with a lot of issues marked as won't fix, duplicate, etc. and no release notes. I used this tool to retroactively generate release notes for past milestones. Cleaning these issues by hand would've been a lot more difficult and error prone than adding a line of yaml to ignore them.

If the error was made the other way so that wontfix was in place when it should not be

That's always a possibility, but as this is an opt-in feature with no default filtering we have to assume that users who want this functionality are managing their labels appropriately so things don't get excluded accidentally.
If in the future this tool is enhanced to generate releases notes from tags or commits (like gren), then it couldn't rely on the milestone being populated correctly.

Thanks very much for the PR @steven-sheehy. This is in master with a minor tweak to the property name.


Adding DG WholeBodyController and solo12 demo

@MaximilienNaveau I've addressed your comments. Let me know if you want me to change anything else before merging.


AlertManager-route-for-interventions-prod

Why:
AlertManager route for interventions-prod#2941

Merge conflicts

paulwyborn  3:12 PM
Hi David:
Your ticket:
AlertManager-route-for-interventions-prod#1212
Should be complete now - severity “”hmpps-interventions”

https://github.com/ministryofjustice/cloud-platform-infrastructure/pull/1215
David Lantos:spiral_calendar_pad:  3:17 PM
Thanks Paul!
3:18
I’m wondering — I’d like 2 routes in the end
3:18
1 for prod alerts and non-prod alerts
3:18
should/could the severity reflect that? (edited)
paulwyborn  3:20 PM
Will it go to a different slack channel?
David Lantos:spiral_calendar_pad:  3:20 PM
yeah in the long run we’d have #interventions-alerts for prod and #interventions-dev-notifications for anything non-prod
paulwyborn  3:22 PM
Do you want me to add the dev one now?
New
David Lantos:
if it’s possible, yes please

https://github.com/ministryofjustice/cloud-platform-infrastructure/pull/1215
paulwyborn  3:46 PM
Hi David - you should have 2 severities created now for their respective slack channels:
hmpps-interventions-non-prod
hmpps-interventions-prod
Let me know if any problems?


Add a MINIMAL pragma to Ord and check existence of other MINIMAL pragmas

PlutusTx.Ord.Ord lacks a MINIMAL pragma meaning it's easy to cause an infinite loop by defining an instance of this class. We should simply take the pragma from base (where that code is stolen from):
{-# MINIMAL compare | (<=) #-}

and check existence of MINIMAL pragmas for all the other type classes where such a pragma applies.

Thank you for the suggestion!
Let me deconstruct it here to minimize context switching

Ord is a type class that defines a total ordering for types.
A pragma is a special instruction or directive that provides additional information to the compiler, allowing for optimizations or modifications in how the code is processed. Pragmas are denoted by the syntax {-# ... #-}, and they do not generally affect the semantic meaning of the program, but they can influence performance and behavior during compilation.
the MINIMAL pragma is used to specify the minimal complete definition of a type class, indicating which methods must be implemented for an instance of that class. This is particularly useful for classes that have methods with circular defaults, ensuring that instances adhere to a defined interface.
https://downloads.haskell.org/~ghc/7.8.1/docs/html/users_guide/pragmas.html
base

TODO:

[ ] find the line in PlutusTx where the changes need to be applied.
[ ] open PR.

Hello @effectfully !
This is where I can't get further without your advice!
I made fixes to Ord as you suggested. then moved on to listing Type Classes in plutus-tx/plinth, which I did using git grep -e "^class .* where" -- **/*.hs
The command returns 34 lines, which I added to the conversation in the pull request.
Please review the PR draft above and suggest the next steps!
Thank you!


Added new quotes

Not sure if new quotes needed, but thought of adding some of my favorite ones :)
Signed-off-by: shaishavgandhi05<EMAIL_ADDRESS>

Thanks @shaishavgandhi05! 👍


[FLINK-17015]Fix NPE from NullAwareMapIterator

What is the purpose of the change
HeapMapState#iterator could return a null iterator when using Heap statebackend, it should better return empty map for  NullAwareMapIterator.
Brief change log

HeapMapState#iterator return empty map when stateTable doesn't contain current namespace table.

Verifying this change
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@Myasuka According to the discussion, I have already align the behavior of HeapMapState #entries(), #keys(), #values(), and #iterator() and RocksDBMapState #entries()  to return empty iterator. Please review this again, thanks.


[HUDI-1822][WIP] Rewriting rfc-27 for data skipping index

What is the purpose of the pull request

Re-writing RFC27 in the new format (moving away from wiki) with some updates to some of the design nuances.

Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@nsivabalan
In the RFC， key format is [ColumnId] [PartitionId] [FileId]/ [ColumnId] "agg" [PartitionId]，it will using hash32/hash128 to generate unique IDS，would like to know how to guarantee the uniqueness between two different columnNames/PartitionValues/FileNames?
I.e., once two different ColumnNames have the same ID after hash32, it will lead a wrong pruning results.

@manojpec : Can you please respond to @hujincalrin 's comment above.


Updates tests

Solves for the following issues/PRs with merge conflicts into v0.8 branch resolved:
https://github.com/estarriolvetch/ERC721Psi/issues/7
https://github.com/estarriolvetch/ERC721Psi/pull/15
https://github.com/estarriolvetch/ERC721Psi/issues/24

Actually. Looks like this didn't merge properly. Let me investigate further.

Lets try this one more time in a different PR. This time I will merge the mintOptimization branch into the update_test branch.


How can I send AT Command via serial port??

SerialPort Version:latest

NodeJS Version:v8.8.1

Operating System and Hardware Platform: Quectel

Have you checked the right version of the api docs?:yes

Are you having trouble installing and you checked the Installation Special Cases docs?

Are you using Electron and have you checked the Electron Docs?:yes

Summary of Problem
I need to send some AT Command via my ttyUSB3 serial port??
Steps and Code to Reproduce the Issue

Create a buffer as below,
var at_cmd = new Buffer("AT\r"); and write,
serialport.write(at_cmd, function(err) {
if(err) {
return console.log("AT command write error " + err);
}
});


Old GCC version in docker base_env

Docker base_env image now has gcc-7 by default, it should be gcc-9

Also no lit installing in Dockerfile_base

affects to issues-47


Vcpkg regression: shaderc no longer supports shared library build

Describe the bug
As a follow up to this issue: https://github.com/microsoft/vcpkg/issues/16122, seems that shaderc shared library is no longer built?
Environment

OS: Windows
Compiler: MSVC 2019

To Reproduce
Steps to reproduce the behavior:

./vcpkg install shaderc:x64-windows
See error
-- Note: shaderc only supports static library linkage. Building static library."

Expected behavior
Shaderc vcpkg used to support both static and shared lib build, now it seems that only static lib is supported?
Failure logs
-(please attached failure logs)
Additional context
Add any other context about the problem here.
Package: shaderc:x64-windows
Vcpkg version: 2021-01-13-d67989bce1043b98092ac45996a8230a059a2d7e

Hi @jmoguillansky-gpsw
Thanks for posting this issue.
Currently shaderc only supports static build. Please see
#Note: glslang and spir tools doesn't export symbol and need to be build as static lib for cmake to work
vcpkg_check_linkage(ONLY_STATIC_LIBRARY)

https://github.com/microsoft/vcpkg/blob/master/ports/shaderc/portfile.cmake#L1-L2
Generally, vcpkg supports both static and dynamic builds. But for some ports, they only support static or dynamic build, which is related with the ports themselves.
So the current behavior is expected.

Hi, I saw that comment.  Shaderc upstream supports shared library build.  Its not a shaderc issue.  In the most recent commit vcpkg disabled shaderc shared library build.  Its a vcpkg issue

This should be revisited. Probably it never was a problem for non-MSVC, and now there is also dllexport:
https://github.com/google/shaderc/blob/aaa44b544909600381e1a180074ed7f544e48410/libshaderc/include/shaderc/visibility.h#L21-L25


Update stride-logo-readme.png

Removes transparent background so it is display correctly in Github page
PR Details
Really something minor, but still an imporovement over the look of the Github page.
Description
Just added solid color to the background of the PNG.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Can I ask you what is the reason behind adding new background ? I have a concern that on a light background it might look a bit off.
Please, take a look:

Okay... well, in my case it looks like this:

I added a bit of padding to the image, so now its not that misplaced. Also I obviously had to choose between dark on white background or white on dark background, and thought the version white on dark works for both backgrounds a bit better. Hope it also works for you guys.

I still think there is a better solution for supporting dark themes. Maybe instead of adding an unnecessary background, we could just add an outline to the logo in a similar way Godot does?
Reference (dark/light theme) :

What do you think?

Good call! I added an outer glow to the logo, that worked better than an outline IMO.

Currently this is what I see on your branch:

While I guess it could make sense to add some border to make the logo more visible in dark themed GitHub, IMO it should be minimal - (2-3px) - the glow I see looks very thick on the dark version and because it's feathered it makes the text less readable. I think a hard edge or much less intense feathering would be preferred.
But actually, I see there's a way to use different image for different theme color - https://github.com/GiorgosXou/Random-stuff/tree/main/Programming/StackOverflow/Answers/70200610_11465149
As such it would be advisable to use the correct logos. I pulled this zip of SVGs from Discord (author sebl):
stridesvgs.zip
We should use the SVGs to generate the PNGs without loss of quality. The current one is solid.svg, the white one is solid-1.svg

Okay, that seems to be a good way to go.
I have pushed the black and white versions made from sebls SVGs. What I don't know is how to link them properly, right now the path seems to be set dynamically but in the example a direct path is used. Could you link them in the Readme?

@chkworks Well, I think its a matter of choice. I would rather go with direct path because, less megs would be downloaded :v:

Alright, I have reverted the original logo to the design without the outer glow, but left the black and white versions in this PR. When they are pushed into the main branch, I can try to include them with the provided method using direct paths to the versions, depending on the theme.

When they are pushed into the main branch, I can try to include them

@chkworks Why not directly in your current PR?

Alright, I initially thought that the URL will be linked to my user name, but I think the path is now taken from the original repository... hope that works now?

Yes it does! Looks good to me.


Bump Java Version

I tried installing JDK 8, but could not find it on the web.  They redirect to JDK version 21.  So I installed that.  I hope it all works.

Security Manager is Deprecated.
Here is the error message:
[info] [launcher] getting Scala 2.10.6 (for sbt)...
java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release.
The full log is below.  And it looked like it was going so well...
bash-3.2$ cd J1Sc
bash-3.2$ sbt
[info] [launcher] getting org.scala-sbt sbt 0.13.16  (this may take some time)...
downloading https://repo1.maven.org/maven2/org/scala-lang/scala-library/2.10.6/scala-library-2.10.6.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/main/0.13.16/jars/main.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/0.13.16/jars/sbt.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/compiler-interface/0.13.16/jars/compiler-interface.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/io/0.13.16/jars/io.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/interface/0.13.16/jars/interface.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/main-settings/0.13.16/jars/main-settings.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/actions/0.13.16/jars/actions.jar ...
:: loading settings :: url = jar:file:/opt/homebrew/Cellar/sbt/1.9.6/libexec/bin/sbt-launch.jar!/org/apache/ivy/core/settings/ivysettings.xml
[SUCCESSFUL ] org.scala-lang#scala-library;2.10.6!scala-library.jar (4147ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/ivy/0.13.16/jars/ivy.jar ...
[SUCCESSFUL ] org.scala-sbt#interface;0.13.16!interface.jar (8145ms)
[SUCCESSFUL ] org.scala-sbt#sbt;0.13.16!sbt.jar (8189ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/logic/0.13.16/jars/logic.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/logging/0.13.16/jars/logging.jar ...
[SUCCESSFUL ] org.scala-sbt#compiler-interface;0.13.16!compiler-interface.jar (10195ms)
[SUCCESSFUL ] org.scala-sbt#actions;0.13.16!actions.jar (10645ms)
[SUCCESSFUL ] org.scala-sbt#io;0.13.16!io.jar (10700ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/process/0.13.16/jars/process.jar ...
[SUCCESSFUL ] org.scala-sbt#main;0.13.16!main.jar (11324ms)
downloading https://repo1.maven.org/maven2/org/scala-sbt/launcher-interface/1.0.1/launcher-interface-1.0.1.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/run/0.13.16/jars/run.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/command/0.13.16/jars/command.jar ...
[SUCCESSFUL ] org.scala-sbt#main-settings;0.13.16!main-settings.jar (11668ms)
[SUCCESSFUL ] org.scala-sbt#launcher-interface;1.0.1!launcher-interface.jar (521ms)
[SUCCESSFUL ] org.scala-sbt#ivy;0.13.16!ivy.jar (7709ms)
[SUCCESSFUL ] org.scala-sbt#logic;0.13.16!logic.jar (4155ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/classpath/0.13.16/jars/classpath.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/api/0.13.16/jars/api.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/completion/0.13.16/jars/completion.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/compiler-integration/0.13.16/jars/compiler-integration.jar ...
[SUCCESSFUL ] org.scala-sbt#logging;0.13.16!logging.jar (5152ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/compiler-ivy-integration/0.13.16/jars/compiler-ivy-integration.jar ...
[SUCCESSFUL ] org.scala-sbt#run;0.13.16!run.jar (4000ms)
[SUCCESSFUL ] org.scala-sbt#process;0.13.16!process.jar (4469ms)
[SUCCESSFUL ] org.scala-sbt#command;0.13.16!command.jar (4424ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/relation/0.13.16/jars/relation.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/task-system/0.13.16/jars/task-system.jar ...
[SUCCESSFUL ] org.scala-sbt#api;0.13.16!api.jar (3888ms)
[SUCCESSFUL ] org.scala-sbt#classpath;0.13.16!classpath.jar (4134ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/tasks/0.13.16/jars/tasks.jar ...
[SUCCESSFUL ] org.scala-sbt#completion;0.13.16!completion.jar (4343ms)
downloading https://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.10.6/scala-compiler-2.10.6.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/tracking/0.13.16/jars/tracking.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/testing/0.13.16/jars/testing.jar ...
[SUCCESSFUL ] org.scala-sbt#compiler-integration;0.13.16!compiler-integration.jar (4181ms)
downloading https://repo1.maven.org/maven2/org/scala-lang/scala-reflect/2.10.6/scala-reflect-2.10.6.jar ...
[SUCCESSFUL ] org.scala-sbt#compiler-ivy-integration;0.13.16!compiler-ivy-integration.jar (3533ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/control/0.13.16/jars/control.jar ...
[SUCCESSFUL ] org.scala-lang#scala-reflect;2.10.6!scala-reflect.jar (1197ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/collections/0.13.16/jars/collections.jar ...
[SUCCESSFUL ] org.scala-sbt#relation;0.13.16!relation.jar (3845ms)
downloading https://repo1.maven.org/maven2/jline/jline/2.14.4/jline-2.14.4.jar ...
[SUCCESSFUL ] jline#jline;2.14.4!jline.jar (326ms)
[SUCCESSFUL ] org.scala-sbt#task-system;0.13.16!task-system.jar (4199ms)
[SUCCESSFUL ] org.scala-sbt#tasks;0.13.16!tasks.jar (4010ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/classfile/0.13.16/jars/classfile.jar ...
[SUCCESSFUL ] org.scala-sbt#tracking;0.13.16!tracking.jar (3884ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/incremental-compiler/0.13.16/jars/incremental-compiler.jar ...
[SUCCESSFUL ] org.scala-sbt#testing;0.13.16!testing.jar (3890ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/compile/0.13.16/jars/compile.jar ...
[SUCCESSFUL ] org.scala-lang#scala-compiler;2.10.6!scala-compiler.jar (4063ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/persist/0.13.16/jars/persist.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbinary/sbinary_2.10/0.4.2/jars/sbinary_2.10.jar ...
[SUCCESSFUL ] org.scala-sbt#control;0.13.16!control.jar (3902ms)
downloading https://repo1.maven.org/maven2/org/scala-sbt/ivy/ivy/2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4/ivy-2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/cross/0.13.16/jars/cross.jar ...
[SUCCESSFUL ] org.scala-sbt.ivy#ivy;2.3.0-sbt-48dd0744422128446aee9ac31aa356ee203cc9f4!ivy.jar (545ms)
downloading https://repo1.maven.org/maven2/com/jcraft/jsch/0.1.50/jsch-0.1.50.jar ...
[SUCCESSFUL ] com.jcraft#jsch;0.1.50!jsch.jar (333ms)
downloading https://repo1.maven.org/maven2/org/scala-sbt/serialization_2.10/0.1.2/serialization_2.10-0.1.2.jar ...
[SUCCESSFUL ] org.scala-sbt#serialization_2.10;0.1.2!serialization_2.10.jar (341ms)
downloading https://repo1.maven.org/maven2/org/scala-lang/modules/scala-pickling_2.10/0.10.1/scala-pickling_2.10-0.10.1.jar ...
[SUCCESSFUL ] org.scala-lang.modules#scala-pickling_2.10;0.10.1!scala-pickling_2.10.jar (518ms)
downloading https://repo1.maven.org/maven2/org/json4s/json4s-core_2.10/3.2.10/json4s-core_2.10-3.2.10.jar ...
[SUCCESSFUL ] org.json4s#json4s-core_2.10;3.2.10!json4s-core_2.10.jar (386ms)
downloading https://repo1.maven.org/maven2/org/spire-math/jawn-parser_2.10/0.6.0/jawn-parser_2.10-0.6.0.jar ...
[SUCCESSFUL ] org.spire-math#jawn-parser_2.10;0.6.0!jawn-parser_2.10.jar (253ms)
downloading https://repo1.maven.org/maven2/org/spire-math/json4s-support_2.10/0.6.0/json4s-support_2.10-0.6.0.jar ...
[SUCCESSFUL ] org.scala-sbt#classfile;0.13.16!classfile.jar (4569ms)
downloading https://repo1.maven.org/maven2/org/scalamacros/quasiquotes_2.10/2.0.1/quasiquotes_2.10-2.0.1.jar ...
[SUCCESSFUL ] org.spire-math#json4s-support_2.10;0.6.0!json4s-support_2.10.jar (272ms)
downloading https://repo1.maven.org/maven2/org/json4s/json4s-ast_2.10/3.2.10/json4s-ast_2.10-3.2.10.jar ...
[SUCCESSFUL ] org.json4s#json4s-ast_2.10;3.2.10!json4s-ast_2.10.jar (367ms)
downloading https://repo1.maven.org/maven2/com/thoughtworks/paranamer/paranamer/2.6/paranamer-2.6.jar ...
[SUCCESSFUL ] org.scalamacros#quasiquotes_2.10;2.0.1!quasiquotes_2.10.jar (426ms)
[SUCCESSFUL ] org.scala-sbt#collections;0.13.16!collections.jar (6159ms)
[SUCCESSFUL ] com.thoughtworks.paranamer#paranamer;2.6!paranamer.jar (267ms)
downloading https://repo1.maven.org/maven2/org/scala-sbt/test-interface/1.0/test-interface-1.0.jar ...
[SUCCESSFUL ] org.scala-sbt#persist;0.13.16!persist.jar (4580ms)
[SUCCESSFUL ] org.scala-sbt#compile;0.13.16!compile.jar (5077ms)
downloading https://repo1.maven.org/maven2/org/scala-sbt/template-resolver/0.1/template-resolver-0.1.jar ...
[SUCCESSFUL ] org.scala-sbt#test-interface;1.0!test-interface.jar (271ms)
[SUCCESSFUL ] org.scala-sbt#cross;0.13.16!cross.jar (4122ms)
[SUCCESSFUL ] org.scala-sbt#template-resolver;0.1!template-resolver.jar (259ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/cache/0.13.16/jars/cache.jar ...
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/test-agent/0.13.16/jars/test-agent.jar ...
[SUCCESSFUL ] org.scala-tools.sbinary#sbinary_2.10;0.4.2!sbinary_2.10.jar (5170ms)
[SUCCESSFUL ] org.scala-sbt#incremental-compiler;0.13.16!incremental-compiler.jar (6040ms)
downloading https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/apply-macro/0.13.16/jars/apply-macro.jar ...
[SUCCESSFUL ] org.scala-sbt#test-agent;0.13.16!test-agent.jar (3604ms)
[SUCCESSFUL ] org.scala-sbt#apply-macro;0.13.16!apply-macro.jar (4213ms)
[SUCCESSFUL ] org.scala-sbt#cache;0.13.16!cache.jar (4619ms)
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved
[info] [launcher] getting Scala 2.10.6 (for sbt)...
java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release
at java.base/java.lang.System.setSecurityManager(System.java:429)
at sbt.TrapExit$.installManager(TrapExit.scala:52)
at sbt.StandardMain$.runManaged(Main.scala:60)
at sbt.xMain.run(Main.scala:35)
at xsbt.boot.Launch$.$anonfun$run$1(Launch.scala:149)
at xsbt.boot.Launch$.withContextLoader(Launch.scala:176)
at xsbt.boot.Launch$.run(Launch.scala:149)
at xsbt.boot.Launch$.$anonfun$apply$1(Launch.scala:44)
at xsbt.boot.Launch$.launch(Launch.scala:159)
at xsbt.boot.Launch$.apply(Launch.scala:44)
at xsbt.boot.Launch$.apply(Launch.scala:21)
at xsbt.boot.Boot$.runImpl(Boot.scala:78)
at xsbt.boot.Boot$.run(Boot.scala:73)
at xsbt.boot.Boot$.main(Boot.scala:21)
at xsbt.boot.Boot.main(Boot.scala)
[error] [launcher] error during sbt launcher: java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release

The previous posting was sent before I was done editing it.  So I have edited it with more details.

Hmm  sbt 0.13.16 is reaaaaaly old, i would say, could try 1.6.0 ?
here you can update it :
https://github.com/SteffenReith/J1Sc/blob/master/project/build.properties
About tje JVM, personnaly i'm on :
javac <IP_ADDRESS>
rawrr@rawrr-pc:~$ java --version
openjdk <IP_ADDRESS> 2023-08-24
OpenJDK Runtime Environment (build <IP_ADDRESS>+1-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build <IP_ADDRESS>+1-post-Ubuntu-0ubuntu122.04, mixed mode, sharing)

Sorry about that, it posted before I was done.
The devel branch uses
scalaVersion := "2.11.12"
val spinalVersion = "1.8.0b"
So it is not clear to me which version I should be using.   master or devel?   @SteffenReith, which do you recommend I should be using?
Best would be if you would do a merge, so that there would be no questions as to which to use.  Alternatively I could issue a pull request for the versions I am using.   Not a big change.  Two files, And I still have not tested it on hardware.
I am busy figuring out which files I need to change to port to the pico-ice board.  Work is slower, now that school has started.


Propagate and handle errors in database and static file services

Some of the static file service and database service methods have error return values, although they do not get propagated and probably need to be handled.
See:
https://github.com/paradigmxyz/reth/blob/068220bb0ad3c626e2323dda91f7423e9b375278/crates/engine/tree/src/static_files.rs#L183
So, we will need to check the failure modes which would cause these errors, and either handle or propagate them.

Done


updated mojibar (2.3.3)

There was a pull request template when you submitted. It contains the steps that must be followed.
If you were not presented with a template, you may have submitted your pull request via a CLI tool (likely hub). It that was the case, you may wish to see if the tool has a way to let you use the template (hub is working on it).
Please add and fill in the template to your original post.


fix mobile 'add more' button goes to homepage

The problem and the solution is from: https://forum.tastyigniter.com/d/2886-add-more-items-not-working

{{ restaurant_url('local/menus') }} should redirect to the menus page not homepage..

The problem is restaurant_url('local/menus') is not always the menu url of the location you are ordering. For my case, I have a location named test, and it is set to the default location. the restaurant_url('local/menus') here gives me {domain}/default/menus. (I even don't have a location called default)


Allele counts for homref not showing up in Variant Detail

This is probably an unintentional side effect caused by filtering based on 'gt_unknown'

Gene.iobio should be able to show homrefs if the trio samples are in separate files.  (In fact, I thought I fixed gene.iobio to do this a while ago!)
We won’t always have multi-sample vcfs, so we need to account for this in gene.iobio anyways.
Gene.iobio requires multi-sample vcfs for affected/unaffected sibs, so long-term, we need to figure out a way to distinguish between one multi-sample vcf and multiple single-sample vcfs.

Seems fixed


Help with hypergeometric test

I'd like to use stats.hypergeom to implement a hypergeometric test for significance. However, using the recommended way, I'm getting an odd result.
 I happen to draw all 4 red balls.
from scipy.stats import hypergeom
hypergeom.sf(4, 19275, 4, 2880)
--> 0.0
hypergeom.cdf(4, 19275, 4, 2880)
--> 1.0

This doesn't make sense, since although you've collected all 4 red balls, there's a probability you collect them by chance. Using an online hypergeometric test utility,  I arrive instead at:

Probability of drawing 4 successes or more from a sample of 2880:
P(X >= 4) = 0.0004975336447094944.
Probability of drawing exactly 4 successes from a sample of 2880:
P(X = 4) = 0.0004975336447094944.

There doesn't seem to be much documentation online about how to implement a hypergeometric test using this library, and what I've found is occasionally inconsistent, so an authoritative, conclusive answer, perhaps in the hypergeom docs, would probably be helpful.
This might also just be an issue of precision (though I doubt it). However if that's the case, might any of the functions related to hypergeom in scipy.special help with this? No clue, just a thought.
@ev-br hoping you're willing to take a look at this since you were involved in #6840

The inequality in the definition of the survival function is a strict inequality, and with only 4 red balls, P(X > 4) is 0, as expected.

hypergeom.sf(3, 19275, 4, 2880)
0.00049753364470522961
Iow, looks as expected.

Thanks!


Replaced GDrive links with Zenodo

Replacing Google Drive links with the Zenodo artifact containing the jar files.

@snadi Is it okay if I merge this in? Or would you rather I put it on a different branch?

Yes! Apologies that I missed this somehow. Thanks Henry!

I am working on trying to upload the files for the SOComments work, but Zenodo isn't taking kindly to the 25gb db file.


Fix tracking of ActiveDeviceList

About the PR

Fix tracking of active network cofigurators. Add validation of tracked configurators and devices.
Why / Balance

This was the second of the sources of Can't resolve Robust.Shared.GameObjects.MetaDataComponent
errors in the logs that I was given.
Technical details

Improper checking and clearing of ActiveDeviceList caused references DeviceLists configurator lists to become stale. This breaks the updater function into a controlled region and fixes these issues. There are two ways to desync the list I found:

Mixed UI

open a list view
open a config view (sets ActiveDeviceList)
close the list view (clears ActiveDeviceList)
close the config view (ActiveDeviceList is null, DeviceList is not updated)

Device Switching

open a config view (sets ActiveDeviceList)
open a config view for a different machine (sets ActiveDeviceList, does not update previous DeviceList)

Media

Requirements

[X ] I have read and am following the Pull Request and Changelog Guidelines.
[X ] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl: procdox

fix: server side serialization bug caused by opening multiple network configuration menus

you don't have to add your name to the CL since your preferred name is the same as your github one, just leave it blank and it'll automatically make it procdox


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.25",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9921c866dc369577c3ebb9adf2383b01b58c18de"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "9921c866dc369577c3ebb9adf2383b01b58c18de",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.25 by commit 9921c866dc369577c3ebb9adf2383b01b58c18de. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000482


Creating a prepared statement for a delete generates a fatalError

Prepared statements that do not return values appear to generate a fatalError.
database.prepare(query: "DELETE FROM my_table WHERE "MyIndex" = $1").wait()
Postgres responds with a message of type 110 (.noData) which trips the default case at https://github.com/vapor/postgres-nio/blob/7c195a48659fa20c9161b64cfe55b088c4a1d1cd/Sources/PostgresNIO/Connection/PostgresDatabase%2BPreparedQuery.swift#L82

https://github.com/vapor/postgres-nio/pull/123


subsys: fs/nvs: fix writes when write_block_size != 1

The current code computes the block-aligned len by ANDing the len with
~write_block_size instead of ~(write_block_size - 1).
In addition the compute value can be 0 (for lengths that are less than
the block size), so the first flash write might have to be skipped.
Signed-off-by: Aurelien Jarno<EMAIL_ADDRESS>

@Laczen, this is the fix I talked about in #8141.

Codecov Report

Merging #9600 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9600   +/-   ##
=======================================
  Coverage   52.15%   52.15%
=======================================
  Files         212      212
  Lines       25916    25916
  Branches     5582     5582
=======================================
  Hits        13517    13517
  Misses      10149    10149
  Partials     2250     2250

Continue to review full report at Codecov.

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

The nvs sample was broken on frdm_k64f after the rewrite. This fixes it.


http broken in latest nightly

building http in the latest nightly of rust (2018-3-27 as of this writing) fails. A selection of the errors is below:
error: use of deprecated item 'std::ascii::AsciiExt': use inherent methods instead
  --> src\uri\mod.rs:32:5
   |
32 | use std::ascii::AsciiExt;
   |     ^^^^^^^^^^^^^^^^^^^^
   |
note: lint level defined here
  --> src\lib.rs:160:9
   |
160| #![deny(warnings, missing_docs, missing_debug_implementations)]
   |         ^^^^^^^^
   = note: #[deny(deprecated)] implied by #[deny(warnings)]

error[E0034]: multiple applicable items in scope
   --> src\method.rs:325:9
    |
325 |         Method::try_from(t.as_bytes())
    |         ^^^^^^^^^^^^^^^^ multiple `try_from` found
    |
    = note: candidate #1 is defined in an impl of the trait `std::convert::TryFrom` for the type `_`
note: candidate #2 is defined in the trait `convert::HttpTryFrom`
   --> src\convert.rs:22:5
    |
22  |     fn try_from(t: T) -> Result<Self, Self::Error>;
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    = help: to disambiguate the method call, write `convert::HttpTryFrom::try_from(...)` instead

It would seem the recent stabilization of TryFrom as well as the deprecation of AsciiExt have broken http.
Side note: Is Rust allowed to cause breakage like this with new versions of the compiler? I would think that it would be problematic to do so. TryFrom seems to be an issue since it is included in the prelude.

I don't know. I filed https://github.com/rust-lang/rust/issues/49436.

We can likely fix this internally. I doubt the rust team would consider this a breaking change.

This is one of the things that's "expected breakage" but if it ends up being overly traumatic to the ecosystem we might back out.

@sfackler define "overly traumatic". My understanding was that these sorts of "expected breakage" would go through an ecosystem "crater" (or whatever it is called) and if it broke things it wouldn't be applied.
I understand the problem that one must be able to add new fns / traits, but if breaking the http crate is considered "expected breakage", that seems to fail at Rust's promise for backwards compatibility as this will cascade down do everyone that depends on http as well as production Rust users.
The "fix" seems to be to not include TryFrom in std's prelude until the next Rust edition, which is coming soon.

Yeah, we'll be looking at the crater report that runs for the first beta.

but if breaking the http crate is considered "expected breakage"

Are you arguing that the http crate is inherently special and must never be broken?

The "fix" seems to be to not include TryFrom in std's prelude until the next Rust edition, which is coming soon.

Yeah, that's probably what we'd do if we end up deciding to back the prelude part out. I don't think prelude changes were formally covered in the epoch RFC but it definitely seems like something we would be able to do.

Almost any change to the API of any existing item has the ability to break third party code. We do not think it's reasonable to never be able to touch anything after it's first been added, so we say that we're allowed to make these changes anyway. At that point, some amount of downstream code may or may not break. If that's happened, there needs to be a change either in the standard library or in those downstream libraries. Depending on how many of those there are, we make a decision of how to move forward. Crates used by "production users" have been broken before in this kind of way, and they will be broken in the future.
Production users on stable have 6 weeks before this affects them in any way - this is why we have release trains. Production users on nightly should (hopefully) be pinning to a specific nightly to avoid being randomly broken whenever something lands that affects them. Cutting an http release with #194 will fix those production users. Removing TryFrom from the prelude will also fix them.

I agree that there actually many many things that could break compiling (adding an inherent method to an item could break someone, if they implemented a trait for that item and there's now a name conflict).
In this case, we certainly can (and likely will, to at least prepare for the future) merge #194. However, the problem exists that anyone with a binary that upgrades compiler version, but doesn't want to upgrade their Cargo.lock, will suddenly see things break. A 0.1.5 release of http should be super easy to apply, but it's an unfortunate user experience.
Especially since they can't really opt-out, other than to not upgrade their compiler. That's because this trait is in the prelude.

What opting out would be possible with other library changes that broke third party crates?

However, the problem exists that anyone with a binary that upgrades compiler version, but doesn't want to upgrade their Cargo.lock, will suddenly see things break.

Could you go into more detail about why people are in that situation?

What opting out would be possible with other library changes that broke third party crates?

In that case, possibly none. However, many people likely hold the compiler and std to a higher standard, and std is special in that use std::prelude::* is magically injected into every module.

Could you go into more detail about why people are in that situation?

I cannot. I'm talking in theoreticals. The situation still exists, and while probably rare and sounds contrived, it's really not: with Rust's stability guarantees, people should feel free to upgrade their compiler whenever. If they do so, and suddenly see their app doesn't compile, they'll be less trusting of upgrading.

@sfackler It's mostly that the stable version of Rustc is not included in Cargo.lock. It has been my understanding that pinning a project to a stable version of rustc should not be needed.
The issue arises when you clone a Rust repo, run cargo build, it should work.
If I am mistaken, then it should become recommended as good practice to include a rustup toolchain file (https://github.com/rust-lang-nursery/rustup.rs/#the-toolchain-file) in projects.
For example, Conduit transitively depends on http and has all the versions locked. Releases are frozen in time and we would like them to be able to be compiled reliably even in the future.
Up until today, we have not really pinned the Rustc version in the repo, so if the TryFrom change lands, it will break our past release builds. Maybe this is a bad assumption and we can’t rely on rustc stability. It would be good to figure out best practices

with Rust's stability guarantees, people should feel free to upgrade their compiler whenever.

I don't understand what stability guarantees you're referring to. We have added 14 methods to Iterator and 2 methods to Ord, both traits in the prelude, since 1.0 and those additions have broken crates multiple times (for_each being a recent notable case). We identify these cases explicitly as minor changes in our stability guarantees. The prelude isn't mentioned in that RFC, but adding a new trait to the prelude is IMO roughly equivalent to adding new methods to existing traits in terms of the types of breakage it can produce.

@sfackler
Regarding the section you linked:

All that said, it is incumbent on library authors to ensure that such "minor" changes are in fact minor in practice: if a conflict like t.foo() is likely to arise at all often in downstream code, it would be advisable to explore a different choice of names. More guidelines for the standard library are given later on.

The main point is that the Rust team has advertised stability as a feature. To downstream users, it doesn't actually matter if a change is minor or not, it matters if their build will break. If the Rust team is not reasonably able to provide a guarantee of stability, that is fine but should be advertised and downstream users can adjust best practices by, for example, pinning the stable version of Rust.
Again if this change lands on Rust stable, it will break the existing frozen Conduit builds due to the fact that we did not pin the version of Rust but dependencies are pinned.

Seems the change was reverted for now : https://github.com/rust-lang/rust/pull/49518

Thanks


Entity too large

Allow to configure a max POST data size for the server.

Just re-wrote the PR, please feel free to have a look

All outstanding issues fixed, only one point remaining to be discussed.


image display not working in gnome-terminal

Just as the title states, trying to display and image in the neofetch output doesn't work when using gnome-terminal. pretty much using the same exact config that I use in Konsole, which works.
 I was supposed to do that, and even had a text editor open to type it out... but got caught up in something and posted the little that I did. Give me just a min and I'll have it typed up.

here is my config file:
neofetchconf.txt
I have uploaded a screenshot of the output of neofetch, after editing the conf file.

here is the verbose log:
https://paste.ubuntu.com/p/nGxCvzjg6g/

this is what it looks like when I dont try and use the w3m back end, and just change the ascii art to the lfs distro:

Also, I have installed w3m of course.

It works fine, just not in wayland.


create screen test and capture css media fingerprint

https://developer.mozilla.org/en-US/docs/Web/CSS/@media

[x] - devicePixelRatio
[x] - matchMedia
[x] - @media: https://jsfiddle.net/w8qxu1p2/1/
[x] - detect screen via getComputedStyle: https://jsfiddle.net/jrnca3wh/
[ ] @import can access media queries: https://jsfiddle.net/873kspn4/1/

matchMedia(`(min-device-height:${screen.height}px)`).matches
matchMedia(`(min-device-width:${screen.width}px)`).matches
matchMedia(`(max-device-height:${screen.height}px)`).matches
matchMedia(`(max-device-width:${screen.width}px)`).matches
matchMedia(`(device-height:${screen.height}px)`).matches
matchMedia(`(device-width:${screen.width}px)`).matches

https://abrahamjuliot.github.io/creepjs/tests/screen.html
orientation and viewport are undefined - FF nightly 86, and yes my inner is square :)

tzp has a scrollbar hence viewport is not 1000x1000

https://abrahamjuliot.github.io/creepjs/tests/screen.html
orientation and viewport are undefined - FF nightly 86, and yes my inner is square :)

tzp has a scrollbar hence viewport is not 1000x1000

https://jsfiddle.net/873kspn4/1/
FF nightly 86 RFP off = prefersColorScheme: "", prefersReducedMotion: ""
FF nightly 86 RFP on = prefersColorScheme: "", prefersReducedMotion: "no-preference"
What does import gain over just a straight css (besides the fact that JS can read it quickly)

https://jsfiddle.net/873kspn4/1/
FF nightly 86 RFP off = prefersColorScheme: "", prefersReducedMotion: ""
FF nightly 86 RFP on = prefersColorScheme: "", prefersReducedMotion: "no-preference"
What does import gain over just a straight css (besides the fact that JS can read it quickly)

viewport

I'm now discovering, FF has visualViewport behind the flag dom.visualviewport.enabled. This should now yield the unsupported label if both dimensions are undefined.

orientation

Oops, that's a bug I left in there. Fixed.

@import

@media and @import are pretty much the same. I might add this later to test if Chromium's proposed privacy budget covers both and matchMedia.

viewport

I'm now discovering, FF has visualViewport behind the flag dom.visualviewport.enabled. This should now yield the unsupported label if both dimensions are undefined.

orientation

Oops, that's a bug I left in there. Fixed.

@import

@media and @import are pretty much the same. I might add this later to test if Chromium's proposed privacy budget covers both and matchMedia.

https://bugzilla.mozilla.org/show_bug.cgi?id=1579584#c5 and subsequent comments
I've been letting android tests lapse. Anyway, if I read that right, then we can detect if dynamic toolbar is enabled? I should make a test: i.e if enabled 100vh - inner = toolbar height ... if disabled 100vh - inner = zero
wanna test that for me?

https://bugzilla.mozilla.org/show_bug.cgi?id=1579584#c5 and subsequent comments
I've been letting android tests lapse. Anyway, if I read that right, then we can detect if dynamic toolbar is enabled? I should make a test: i.e if enabled 100vh - inner = toolbar height ... if disabled 100vh - inner = zero
wanna test that for me?

I do not know what you mean by @media and by MediaQueryList. What is the difference? Which one is @matchmedia if any?
I have questions. Using Firefox Nightly on Android. RFP off on the left, RFP on on the right
screen test

Both

why the fake screen returns
why is the height different in visualViewport

note: how are you getting this. In TZP we use a binary search in matchmedia to get subpixels (decimals) for measurements (screen, inner etc) which show up when the devicePixelRatio != 1 = almost always on android = entropy galore!!

RFP on

why undefined for heights
why is aspect ratio fake? in TZP with RFP on this is all portrait (all 8 values). What are you using to calculate 16/9 or 6/13 etc
FWIW I don't think it's worthwhile returning e.g. 16/9 when that entropy is already in the width + height measurements: but maybe you're trying to catch something out here, like an extension lie? Please explain yourself young man, or you won't get any pudding.

creepy test

green boxes on RFP=on

I do not know what you mean by @media and by MediaQueryList. What is the difference? Which one is @matchmedia if any?
I have questions. Using Firefox Nightly on Android. RFP off on the left, RFP on on the right
screen test

Both

why the fake screen returns
why is the height different in visualViewport

note: how are you getting this. In TZP we use a binary search in matchmedia to get subpixels (decimals) for measurements (screen, inner etc) which show up when the devicePixelRatio != 1 = almost always on android = entropy galore!!

RFP on

why undefined for heights
why is aspect ratio fake? in TZP with RFP on this is all portrait (all 8 values). What are you using to calculate 16/9 or 6/13 etc
FWIW I don't think it's worthwhile returning e.g. 16/9 when that entropy is already in the width + height measurements: but maybe you're trying to catch something out here, like an extension lie? Please explain yourself young man, or you won't get any pudding.

creepy test

green boxes on RFP=on

100vh - inner = toolbar height ... if disabled 100vh - inner = zero

This seems the same as obtaining 100vh and inner (the difference is only unspoken). I'm not sure how 100vh were obtained to verify this, but document.documentElement.clientHeight should match window.innerHeight. I don't have a dynamic tooldbar (?) on my devices.
 const hasToolbar = !!(document.documentElement.clientHeight - window.innerHeight)

100vh - inner = toolbar height ... if disabled 100vh - inner = zero

This seems the same as obtaining 100vh and inner (the difference is only unspoken). I'm not sure how 100vh were obtained to verify this, but document.documentElement.clientHeight should match window.innerHeight. I don't have a dynamic tooldbar (?) on my devices.
 const hasToolbar = !!(document.documentElement.clientHeight - window.innerHeight)

MediaQueryList and matchMedia are the same. MediaQueryList is the object returned.

MediaQueryList and matchMedia are the same. MediaQueryList is the object returned.

I don't have a dynamic toolbar

Android > Firefox > Settings > General > Customize > Scroll to hide toolbar (default = on)

I don't have a dynamic toolbar

Android > Firefox > Settings > General > Customize > Scroll to hide toolbar (default = on)

screen test

fake screen: if a result is undefined, the screen is presumed fake. I added the output and limited the fake test to screen (the test just compares screen with matchMedia). I'm realizing this returns a false positive if the matchMedia only matches a float, but I've only noticed this in an android emulator (I presume it's the same in a virtual machine) and in those context, the screen size is technically fake. Are you getting a fake screen on an actual android device?
visualViewport: this returns a float height on FF Android. I'm now using Math.round in the template output, but the floating point might provide some entropy in a fingerprint.

const vViewport = 'visualViewport' in window ? visualViewport : { }
const { width: viewportWidth, height: viewportHeight } = vViewport
console.log(`${Math.round(viewportWidth)} x ${Math.round(viewportHeight)}`)

undefined heights/aspect ratio: since I'm searching for an integer (up to 10000px), if there is no match it's undefined.
16/9 aspect ratio: this is really not that useful since width height reveals the same (aspect-ratio is only unspoken)

// gcd is based on https://stackoverflow.com/a/1186465
const gcd = (a, b) => b == 0 ? a : gcd(b, a%b)
const { innerWidth, innerHeight } = window
const { width: screenWidth, height: screenHeight } = screen
const ratio = gcd(innerWidth, innerHeight)
const screenRatio = gcd(screenWidth, screenHeight)
const aspectRatio = `${innerWidth/ratio}/${innerHeight/ratio}`
const deviceAspectRatio = `${screenWidth/screenRatio}/${screenHeight/screenRatio}`

/*css*/
@media (aspect-ratio: ${aspectRatio}) {
	body {--viewport-aspect-ratio: ${aspectRatio};}
}
@media (device-aspect-ratio: ${deviceAspectRatio}) {
	body {--device-aspect-ratio: ${deviceAspectRatio};}
}

screen test

fake screen: if a result is undefined, the screen is presumed fake. I added the output and limited the fake test to screen (the test just compares screen with matchMedia). I'm realizing this returns a false positive if the matchMedia only matches a float, but I've only noticed this in an android emulator (I presume it's the same in a virtual machine) and in those context, the screen size is technically fake. Are you getting a fake screen on an actual android device?
visualViewport: this returns a float height on FF Android. I'm now using Math.round in the template output, but the floating point might provide some entropy in a fingerprint.

const vViewport = 'visualViewport' in window ? visualViewport : { }
const { width: viewportWidth, height: viewportHeight } = vViewport
console.log(`${Math.round(viewportWidth)} x ${Math.round(viewportHeight)}`)

undefined heights/aspect ratio: since I'm searching for an integer (up to 10000px), if there is no match it's undefined.
16/9 aspect ratio: this is really not that useful since width height reveals the same (aspect-ratio is only unspoken)

// gcd is based on https://stackoverflow.com/a/1186465
const gcd = (a, b) => b == 0 ? a : gcd(b, a%b)
const { innerWidth, innerHeight } = window
const { width: screenWidth, height: screenHeight } = screen
const ratio = gcd(innerWidth, innerHeight)
const screenRatio = gcd(screenWidth, screenHeight)
const aspectRatio = `${innerWidth/ratio}/${innerHeight/ratio}`
const deviceAspectRatio = `${screenWidth/screenRatio}/${screenHeight/screenRatio}`

/*css*/
@media (aspect-ratio: ${aspectRatio}) {
	body {--viewport-aspect-ratio: ${aspectRatio};}
}
@media (device-aspect-ratio: ${deviceAspectRatio}) {
	body {--device-aspect-ratio: ${deviceAspectRatio};}
}

dynamic toolbar

I'm not sure there is practical method to detect this since the toolbar is only hidden when/if the user scrolls.

dynamic toolbar

I'm not sure there is practical method to detect this since the toolbar is only hidden when/if the user scrolls.

creepy test

I use an iframe for the screen metrics on creep, and as far as I know RFP restricts screen metrics in iframes.

creepy test

I use an iframe for the screen metrics on creep, and as far as I know RFP restricts screen metrics in iframes.

what are you using for getting vunits?
function get_vunits() {
	let div, vh1, vw1
	div = document.createElement("vunits")
	div.style.height = "100vh"
	div.style.width = "100vw"
	div.style.maxHeight = "none"
	div.style.boxSizing = "content-box"
	document.body.appendChild(div)
	vw1 = div.clientHeight
	vh1 = div.clientHeight
	document.body.removeChild(div)
	console.log(vw1 +" x "+ vh1) // I get 0x0 .. approx 2ms

	function vh(v) {
		let h = Math.max(document.documentElement.clientHeight, window.innerHeight || 0);
		return (v * h) / 100;
	}
	function vw(v) {
		let w = Math.max(document.documentElement.clientWidth, window.innerWidth || 0);
		return (v * w) / 100;
	}
	function vmin(v) {
		return Math.min(vh(v), vw(v));
	}
	function vmax(v) {
		return Math.max(vh(v), vw(v));
	}
	console.log(vw(100), Math.max(document.documentElement.clientWidth, window.innerWidth || 0));
	console.log(vh(100), Math.max(document.documentElement.clientHeight, window.innerHeight || 0));
	console.log(vmin(100));
	console.log(vmax(100)); // approx 1 or 2 ms
}

what are you using for getting vunits?
function get_vunits() {
	let div, vh1, vw1
	div = document.createElement("vunits")
	div.style.height = "100vh"
	div.style.width = "100vw"
	div.style.maxHeight = "none"
	div.style.boxSizing = "content-box"
	document.body.appendChild(div)
	vw1 = div.clientHeight
	vh1 = div.clientHeight
	document.body.removeChild(div)
	console.log(vw1 +" x "+ vh1) // I get 0x0 .. approx 2ms

	function vh(v) {
		let h = Math.max(document.documentElement.clientHeight, window.innerHeight || 0);
		return (v * h) / 100;
	}
	function vw(v) {
		let w = Math.max(document.documentElement.clientWidth, window.innerWidth || 0);
		return (v * w) / 100;
	}
	function vmin(v) {
		return Math.min(vh(v), vw(v));
	}
	function vmax(v) {
		return Math.max(vh(v), vw(v));
	}
	console.log(vw(100), Math.max(document.documentElement.clientWidth, window.innerWidth || 0));
	console.log(vh(100), Math.max(document.documentElement.clientHeight, window.innerHeight || 0));
	console.log(vmin(100));
	console.log(vmax(100)); // approx 1 or 2 ms
}

Are you getting a fake screen on an actual android device

Yes. The screen shots are from my realsies android

Are you getting a fake screen on an actual android device

Yes. The screen shots are from my realsies android

vh units

I use document.documentElement.clientHeight. It's teh same as above. Where v is 100 and h is clientHeight, (100 * h) / 100 yields the same result as h

vh units

I use document.documentElement.clientHeight. It's teh same as above. Where v is 100 and h is clientHeight, (100 * h) / 100 yields the same result as h

TZP when devicePixelRatio is not 1

That's sounds awesome. I'll take a look and try it out.

TZP when devicePixelRatio is not 1

That's sounds awesome. I'll take a look and try it out.

^^ big edit 3 posts up :)

^^ big edit 3 posts up :)

TZP when devicePixelRatio is not 1

That's sounds awesome. I'll take a look and try it out.

the decimal places happen because of the real devicePixelRatio, not because I factor in the reported dPR
Here is my realsies android with RFP on

it hides dPR as 1, in reality it is 2.60.. something. Note my PoC that exposes an almost real value
I am not using that dPR PoC at all, but note the two matchMedia min height results have decimal places - revealing entropy and the existence of subpixels

TZP when devicePixelRatio is not 1

That's sounds awesome. I'll take a look and try it out.

the decimal places happen because of the real devicePixelRatio, not because I factor in the reported dPR
Here is my realsies android with RFP on

it hides dPR as 1, in reality it is 2.60.. something. Note my PoC that exposes an almost real value
I am not using that dPR PoC at all, but note the two matchMedia min height results have decimal places - revealing entropy and the existence of subpixels


nodejieba

The Jieba Chinese Word Segmentation Implemented By Node.js .

Looks interesting, but it's a bit too obscure of a use-case for this list, which tries to common things ;)

Because it is for chinese word segmentation.
English README


Swift3 Support

This Pull Request adds Swift3 support and the ability to set string items to step through. Both need to be reviewed additionally.

Hi @Legoless Thank you for the PR. I finally merged it 🎉 Could you update the README for the new property you added?