Remove another mention of matrix in README

As title

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3947   +/-   ##
=======================================
  Coverage   20.27%   20.27%
=======================================
  Files         146      146
  Lines       29316    29316
=======================================
  Hits         5945     5945
  Misses      22470    22470
  Partials      901      901

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 6be7387...c669dab. Read the comment docs.

LGTM

What was the point of this ?
What did I miss ?

@strk bridge is buggy, mises half of messages and and those who go through are with quite big delay most of the time


Add placeholder blinks setting

In issue #175 a feature request was done for stopping the blinking of the placeholder (but still have a blinking carret if it moves to a spot without a placeholder).
The proposed pull request #176 just removes the blinking of the placeholder and does not leave it as an option.
This pull request adds a setting LaTeXSetting.PlaceholderBlinks that keeps the default value true and does not break any existing unit tests.
Tests are added

to make sure that the setting for a non-blinking placeholder works
to document how it should work
to make sure that it will not be removed in a whim

@charlesroddie Please verify that the effect of changing the "PlaceholderBlinks"-setting results in the behaviour you like.

Codecov Report

Merging #177 into master will increase coverage by 0.00%.
The diff coverage is 96.29%.

@@           Coverage Diff           @@
##           master     #177   +/-   ##
=======================================
  Coverage   87.33%   87.34%
=======================================
  Files         156      156
  Lines       11312    11336   +24
=======================================
+ Hits         9879     9901   +22
- Misses       1433     1435    +2

Impacted Files
Coverage Δ

CSharpMath.Editor.Tests/CaretTests.cs
99.51% <95.23%> (-0.49%)
:arrow_down:

CSharpMath.Editor/MathKeyboard.cs
89.56% <100.00%> (+0.25%)
:arrow_up:

CSharpMath/Atom/LaTeXSettings.cs
98.75% <100.00%> (+<0.01%)
:arrow_up:

CSharpMath/Display/Displays/RadicalDisplay.cs
90.56% <0.00%> (-3.78%)
:arrow_down:

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 ed72190...396815c. Read the comment docs.

 The caret does not blink anymore if the setting is used. I will copy what charlesroddie proposed.

I don't understand the enum
  public enum MathKeyboardCaretState : byte {
    Hidden,
    TemporarilyHidden,
    ShownThroughPlaceholder,
    Shown
  }

Is anyone able to document this enum assuming that it makes sense @Happypig375 @SymboLinker @FoggyFinder ?
It seems a little strange to me that, if PlaceholderBlinks, that the path is ShownThroughPlaceholder -> TemporarilyHidden -> Shown -> Hidden -> Shown -> Hidden ... . This suggests to me that ShownThroughPlaceholder is not a valid state. But it's only a guess as I don't understand the meanings.

TemporarilyHidden -> Shown
should be
TemporarilyHidden -> ShownThroughPlaceholder
So this may be a bug.

Shown: Caret is drawn. Invalid for placeholders. Will disappear when blink timer fires.
ShownThroughPlaceholder: Caret is not drawn. Placeholder is activated. Will disappear when blink timer fires.
TemporarilyHidden: Caret is not drawn. Placeholder is deactivated. Will reappear when blink timer fires.
Hidden: Caret is not drawn. Placeholder is deactivated. Will not reappear when blink timer fires.

Trying to set to Shown when caret is a placeholder will be automatically set to ShownThroughPlaceholder instead.

Thanks. Is this better than having Hidden/TemporarilyHidden/Shown and having Shown display as a cursor or active placeholder depending on the position?

Maybe this would be more clear:
  public enum MathKeyboardCaretState : byte {
    Hidden,
    TemporarilyHidden,
    TemporarilyShown,
  }

and then as charlesroddie suggested

display as a cursor or active placeholder depending on the position?

We could also re-add a Shown enum value that means "don't ever disappear, not even if the timer elapses".

I've pushed a change to this branch https://github.com/verybadcat/CSharpMath/pull/177/commits/c89ac9e2a0d7895d70c658fabe64c7e8f45f10f4 which:

Removes ShownThroughPlaceholder as per https://github.com/verybadcat/CSharpMath/pull/177#issuecomment-715922479
Adjusts the CaretState setter to actually set it to the requested value!
Avoids calling RedrawRequested when the CaretState is set to its current value

@SymboLinker your first idea wouldn't be more clear because placeholders won't be TemporarilyShown (except in the case where you had set PlaceholderBlinks to true) and the second idea requires an extra case and enables options (non-blinking cursor) which would be better expressed as a setting.

Can't quite merge as there is a problem with the cursor showing:

Investigating

Fixed

@SymboLinker I set the default PlaceholderBlinks to false as per comment above and that's the reason for failing tests. Can you get the tests to pass please?

My latest commit undos the following:

Avoids triggering RedrawRequested when the CaretState is set to its current value

I don't know why charlesroddie is so deliberate about changing a default value of PlaceholderBlinks - the point of customizability is that you can already have what you want.
Changing that would not only include changing the unit tests, but it would also require thinking about what should be done with the example project. I assume that the example project is meant to show the possibilities of CSharpMath - it supports blinking placeholders while other math repos don't (as summed up by charlesroddie for a different reason).
To do:

set it to PlaceholderBlinks = true in the example project.
set the default of LaTeXSettings.PlaceholderBlinks to false.
adjust the unit tests.

My latest commit undos the following: Avoids triggering RedrawRequested when the CaretState is set to its current value

That's fine, thanks. This was a mistake on my part.

I don't know why charlesroddie is so deliberate about changing a default value of PlaceholderBlinks - the point of customizability is that you can already have what you want.

Good defaults are extremely important and my reasons for why non-blinking is a good default are clearly given in https://github.com/verybadcat/CSharpMath/pull/176#issue-509082608 . Other people are going to use CSharpMath beyond the people in the current discussion.

I decided not to work on charlesroddie's request to change the default value of PlaceholderBlinks

Then we go back to the state described in the other PR, of either not having an option, or having an option but not having 100% thorough tests, which @Happypig375 would have to indicate an opinion on.

Please open a new PR for changing the default setting.

I didn't see your comment before I pushed changes. I don't mind having the last commit in another PR but it shouldn't make much difference and we might as well decide the default here. Is there inadequate evidence that most users will prefer non-blinking?
I think the testing thoroughness needed is independent of whether the default is true or false as the tests in question test default behavior so (as the last commit here does) deleting them correctly tests for default unblinking behaviour, whether this is done in this PR or a subsequent one.

@charlesroddie Wow, you really dislike unit tests. In 00ba606 it seems you don't even read the names of the tests. You just delete the lines that stand in the way of your change. Some tests absolutely don't make sense anymore.

I did not change the Example project because that would make #164 harder to merge.

Thank you for adjusting the tests.
@Happypig375 Looks like @SymboLinker 's VS is also adding a nuget.config file not just mine. I guess it doesn't matter a lot whether we keep it or gitignore it or find out why it's happening? Anyone with an opinion?

Good defaults are extremely important (...) .

Thinking about defaults with such avidity has given me a thought that I will keep in mind for some time. Thanks for this possibly useful insight. This led me to read the following again:

because a large block blinks which is already easy to identify, unlike the cursor where a small line blinks which is harder to identify

Yes, nice. Those subtle things are what LaTeX is about.
Because you mentioned "what others do" first, I concluded too quickly that the argumention for a request for changing the default was weak. I should not have overlooked the second part.
And here I am, ditching the "I decided not to work on...".

(...) also adding a nuget.config file not just mine. I guess it doesn't matter a lot whether we keep it or gitignore it or find out why it's happening? Anyone with an opinion?

Sometimes a NuGet.Config should be included, for example if CSharpMath would go use NightlyPackages as a dependency. That is not the case (yet), so that seems no reason to be against ignoring it now.
However, in my case today was the first time that a NuGet.Config was generated. That may solve the question how it was generated so that that can be stopped. Could ed72190a76825656e3915972f1652c14c968f51b have done a change that causes it?

@charlesroddie If you don't add unit tests testing your desired behaviour, then there is no guarantee that it will continue to function correctly aside from manual testing. And why test it manually instead of automatically?

I suspect this can be tested by calling the Keyboard's DrawCaret method with a Mock and verify that mock.StartNewPath has not been called. I will look into that later today.

The merge conflict cannot be solved by me. If the changes of cfeb157 are OK, then the MathKeyboardCaretState enum should be deleted in the merge.

If the changes of cfeb157 are OK

They make sense to me

Thanks @SymboLinker !


Is it possible to disable the ESDF generation?

As the title suggests, I was wondering if it is possible to use voxblox for just the TSDF and mesh generation. Looking at the architecture it seems like it is possible but want to make sure.

Yes that is very possible, it's probably the default mode of operation. Our main example "cow_and_lady_dataset.launch" launches a tsdf_server (as opposed to an esdf_server) which will not compute an ESDF.


Status code: 429 error

I've seen 2 issues about 418 error code, but what about 429 code, is it about blocked ip-adress too?

418 means blocked, and 429 means you're about to be blocked.

i got blocked :sob:

Don't use any of the download functionality at this moment, wait for the next update. The block would probably get removed after we(me and the service provider) come to a resolution or you can possibly bypass it by resetting your router.


Integrate Spark operator with Jupyterhub

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Please describe your question here
How to integrate Jupyterhub with Spark Operator? Tried to integrate it by installing Jupyterhub and Spark-operator but it's not working

Jupyterhub and Spark operator are running in the same namespace. Attached spark-operator service account to jupyterhub so that it can communicate with Kubernetes APIs. Creating a SparkSession through the following code,
import os
from pyspark.sql import SparkSession

spark = (
    SparkSession.builder.appName("JupyterApp")
    .master("k8s://https://kubernetes.default.svc:443")
    .config("spark.submit.deployMode", "client")
    .config("spark.executor.instances", "1")
    .config("spark.executor.memory", "1G")
    .config("spark.driver.memory", "1G")
    .config("spark.executor.cores", "1")
    .config("spark.kubernetes.namespace", "spark-operator")
    .config(
        "spark.kubernetes.container.image", "spark:3.5.0"
    )
    .config("spark.kubernetes.authenticate.driver.serviceAccountName", "spark-operator")
    .getOrCreate()
)

The executors are being creating and killed right after they are created. Cannot see driver pod anywhere.
The error we get with the above is given below;
Py4JJavaError: An error occurred while calling None.org.apache.spark.api.java.JavaSparkContext.
: java.lang.IllegalStateException: Spark context stopped while waiting for backend
	at org.apache.spark.scheduler.TaskSchedulerImpl.waitBackendReady(TaskSchedulerImpl.scala:1224)
	at org.apache.spark.scheduler.TaskSchedulerImpl.postStartHook(TaskSchedulerImpl.scala:246)
	at org.apache.spark.SparkContext.<init>(SparkContext.scala:694)
	at org.apache.spark.api.java.JavaSparkContext.<init>(JavaSparkContext.scala:58)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
	at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:247)
	at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:374)
	at py4j.Gateway.invoke(Gateway.java:238)
	at py4j.commands.ConstructorCommand.invokeConstructor(ConstructorCommand.java:80)
	at py4j.commands.ConstructorCommand.execute(ConstructorCommand.java:69)
	at py4j.ClientServerConnection.waitForCommands(ClientServerConnection.java:182)
	at py4j.ClientServerConnection.run(ClientServerConnection.java:106)
	at java.base/java.lang.Thread.run(Thread.java:833)

Can anyone please help in this regard?
Provide a link to the example/module related to the question

Additional context

Hi,
Do the Python and Spark versions of the "Jupyterhub Serve" and  Image "spark:3.5.0" match?
Although written in Korean, I recently tested the "spark:3.5.0" image with Jupyter Notebook.
I hope this helps.
url : https://github.com/ha2hi/spark-study/tree/main/spark-on-k8s/Jupyter-Notebook


philadelphia-core: Improve 'FIXMessageParser'

Inlining parsing of BeginString(8), BodyLength(9), and CheckSum(10) tags makes message parsing 5.9% faster in the performance test when the incoming CheckSum(10) check is disabled and 6.1% faster when it is enabled.

So it's faster with running the checksum than without?

So it's faster with running the checksum than without?

No, the impact is just bigger with the incoming CheckSum(10) check. This makes sense, as one of the three tags, CheckSum(10), is only checked with the incoming CheckSum(10) check enabled. (So for that case, in total three FIXTags.get() call sites are eliminated whereas with the check enabled only two.) 🙂


Auto scroll screen preset

Please verify the following:

[x] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
Giving ability to automatically set screen scroll behaviour depending on content size. With this PR, there is an additional screen preset named 'auto' which behaves as fixed screen if content fits the screen and changes itself to scrollable if it does not.

I like this idea, @martincpt -- just have a question above.

Thank you @jamonholmgren, I've pushed updates. Please review.

Wrong and misleading variable names have been fixed. Please review, @jamonholmgren.

Hey @jamonholmgren,
I've committed your suggestion but one of the CircleCI test still fails.
I told you this on one of your stream last week and you have reset the tests for but now expo tests fails. I think this is out of my authority. Source code must be ok as it was fine through several weeks.
Can you please look into it?
I want to close this PR already, hopefully with successful merge.
Thank you!

@martincpt I think updating the branch should help with that, trying that now.

@jamonholmgren Thanks! Looks like that helped. Ready to merge?

:tada: This PR is included in version 7.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


/plans/: Follow up visual style clean up.

This is a series of fixes to styling to make the /plans/ page look better.

I merged all but the last commit.  The last commit felt hard to process to me, with the green area over a green background.  I think we might want a different-colored background for the top headings.
@rishig ideas?

@rishig?

Sorry for the delay! Agree with Tim about the last commit. I think that area looks fine as is, with just the floating white text. Otherwise looking great!
Minor comments, while I'm looking at it:

Without the green boxes, could use a bit more vertical spacing in that area.
We can fiddle with the rest of wording a bit later, but maybe "Get started with Zulip today!" ("with" instead of "using")?
Maybe a bit less box shadow on the price-box? It doesn't interact well with the lighter part of the gradient. Maybe reduce 10px to 5px or something?
I think just the $8 is visually better than $8.00 (or maybe just the vertical spacing is off for me)?

We have a hard cut from gradient to white in another place as well (referring to the cut from the "hero" area with the price boxes to the FAQ section. Not sure how to make that more graceful, though I think it's fine for now if we don't have a different idea.
I can take a pass on the text in the FAQ and more generally
The horizontal bar in Compare is maybe a bit too thick?

@rishig @brockwhittaker I don't think these changes have been merged; did this get lost?

I'm not sure of the story here. @brockwhittaker?

Nothing important here; final commit was just a design change we weren't interested in implementing.

OK, but what about @rishig's batch of comments above?

OK, I'm closing this; @rishig open a new issue for any of those follow-ups that are still open.


Recover chat_id from username if not exist in redis

close #35

As we reviewed together and after some research this should not work because if the user is not saved in Redis the user was not subscribed before.


changes deprecated M_PI to Double.pi

M_PI and M_PI_2 are deprecated now, so this uses the recommended replacement, Double.pi

hi,
this is good, can you merge it please ? 👯♂

This has been fixed as part of the Swift 4 release - in Toucan v0.7


fix typos

Signed-off-by: allencloud<EMAIL_ADDRESS>

[Current coverage][cc-pull] is 55.06%

Merging [#1200][cc-pull] into [master][cc-base-branch] will increase coverage by 0.04%

@@             master      #1200   diff @@
==========================================
  Files            77         77
  Lines         12190      12190
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           6708       6713     +5
+ Misses         4564       4561     -3
+ Partials        918        916     -2

[][cc-pull]

Powered by Codecov. Last updated by [beb9c87...0a37a5b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/beb9c87298dd212c410f7999c3247851858b9a55...0a37a5b7a124c67973534ebbf9167c9c6284a0c1?src=pr
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/1200?src=pr


server script

GOAL
Running whatsapp as a server and clients connected to server can send messages; Instead of running the wa_otm or wa_bulk every time; we can run it in the background. ^^ ( idea to explore )

currently there are so many moving parts and i am running on a raspberry pi which has limited RAM; running a browser 24/7 affect its performance, so I will not explore into this idea; Code for this will be in the archived section.


Android app does not respect Android's built in spell check

When typing a message in the app, the app does not underline in red misspelled words like other apps (tested in English and Hebrew).
Tested both on an Android phone and Chromebook using the android app.

@clubtech This is an issue with the CupertinoTextField widget for Flutter. Here is a link to the docs: https://api.flutter.dev/flutter/cupertino/CupertinoTextField-class.html
Unfortunately, I don’t think this is possible to change at this time. I WISH it was, or else I would.  I will keep this open and backlog it, so hopefully when we revisit this, Flutter will have implemented a better way for us to use the system stuff

Thanks for your reply and efforts.
Is there really no way to have spell check in the app? It doesn't have to be Android's native spellcheck, but as a texting app I think a spell checker is a must.
Thank you!

Thanks for your reply and efforts.
Is there really no way to have spell check in the app? It doesn't have to be Android's native spellcheck, but as a texting app I think a spell checker is a must.
Thank you!

What I do know is that the text field supports auto correction. What I don't know if it supports actual spell checking. I will look into it for you

Ahh, so I found this open Flutter ticket: https://github.com/flutter/flutter/issues/34688
Looks like they don't support it yet :( Once they support it, I'll be sure to update to that version and get it working

Thank you very much!

I'm not sure if this issue is related, but I had a similar experience with Flutter limitations. https://github.com/BlueBubblesApp/BlueBubbles-Android-App/issues/672

Yup, they are related

Has there been any update on this issue?
Spell check in a texting app is pretty much a must.

We basically support the same functionality as Google Messages, ie misspelled words are autocorrected but intentionally misspelled words are not underlined in red. Flutter is still working on adding support for the underlining

Just wanted to bring this issue back up to see if there are any possible solution here, maybe Flutter added better support for Android's spell check and misspelled words underlining? I noticed Google Messages started to support this recently.

There is no underlining support still, the app would automatically be upgraded to that when its available.


Package clang-4.0 found.
Package lldb-4.0 found.
Package libclang-4.0-dev found.
Package cmake found.
Package make found.
Package automake found.
Package libbz2-dev found.
Package libssl-dev found.
Package libgmp3-dev found.
Package autotools-dev found.
Package build-essential found.
Package libicu-dev found.
Package python2.7-dev found.
Package python3-dev found.
Package autoconf found.
Package libtool found.
Package curl found.
Package zlib1g-dev found.
Package doxygen found.
Package graphviz found.

No required dpkg dependencies to install.

Checking boost library installation.
Boost found at /root/opt/boost.

Checking MongoDB installation.
MongoDB configuration found at /root/opt/mongodb/mongod.conf.

Checking MongoDB C++ driver installation.
Mongo C++ driver found at /usr/local/lib/libmongocxx-static.a.

Checking secp256k1-zkp installation.
secp256k1 found @ /usr/local/lib.

Checking for LLVM with WASM support.
WASM found at /root/opt/wasm/bin.

ALL dependencies sucessfully found or installed . Installing EOSIO

CMAKE_BUILD_TYPE=Release
ENABLE_COVERAGE_TESTING=false
DOXYGEN=false

-- Found Secp256k1: /usr/local/lib/libsecp256k1.a
-- Using custom FindBoost.cmake
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   program_options
--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
--   iostreams
-- Configuring EOSIO on Linux
-- binaryen building with -std=c++11
-- binaryen building for platform x86-64
-- binaryen building with -Wall
-- binaryen building with -Werror
-- binaryen building with -Wextra
-- binaryen building with -Wno-unused-parameter
-- binaryen building with -fno-omit-frame-pointer
-- binaryen building with -fPIC
-- binaryen building with -O2
-- binaryen building with -UNDEBUG
-- Using 'SYS' as CORE symbol name
-- Using 'EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV' as public key for 'eosio' account
-- Using WASM clang => /root/opt/wasm/bin/clang
-- Using WASM llc => /root/opt/wasm/bin/llc
-- Using WASM llvm-link => /root/opt/wasm/bin/llvm-link
-- Found Secp256k1: /usr/local/lib/libsecp256k1.a
-- Configuring fc to build on Unix/Apple
-- zlib found
-- Configuring Builtins
-- Configuring SoftFloat
-- Using custom FindBoost.cmake
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   chrono
--   unit_test_framework
--   locale
-- Configuring ChainBase on Linux
-- Using custom FindBoost.cmake
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   filesystem
--   system
--   chrono
--   program_options
--   unit_test_framework
--   locale
-- Configuring AppBase on Linux
-- Found bsoncxx headers: /usr/local/include/bsoncxx/v_noabi
-- Found bsoncxx library: /usr/local/lib/libbsoncxx-static.a;/usr/local/lib/libbson-static-1.0.a;-lc;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/x86_64-linux-gnu/libm.so;-pthread
-- Found mongocxx headers: /usr/local/include/mongocxx/v_noabi;/usr/local/include/bsoncxx/v_noabi
-- Found mongocxx library: /usr/local/lib/libmongocxx-static.a;/usr/local/lib/libbsoncxx-static.a;/usr/local/lib/libbson-static-1.0.a;-lc;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/x86_64-linux-gnu/libm.so;-pthread;/usr/local/lib/libmongoc-static-1.0.a;/usr/local/lib/libbson-static-1.0.a;-lc;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/x86_64-linux-gnu/libm.so;-pthread;/usr/lib/x86_64-linux-gnu/libssl.so;/usr/lib/x86_64-linux-gnu/libcrypto.so;rt;/usr/lib/x86_64-linux-gnu/libz.so;resolv
-- Git commit revision: 4f4e5c22
-- Git commit revision: 4f4e5c22
-- Git commit revision: 4f4e5c22
-- Configuring done
-- Generating done
-- Build files have been written to: /root/eos/build
[  1%] Built target binaryen
[  1%] Built target wasm
[  1%] Built target ast
[  1%] Built target asmjs
[  2%] Built target cfg
[  5%] Built target passes
[  6%] Built target support
[  6%] Built target emscripten-optimizer
[  6%] Built target builtins
[ 29%] Built target softfloat
[ 29%] Built target chainbase
[ 29%] Built target Platform
[ 30%] Built target appbase
[ 32%] Built target libc++
[ 32%] Built target eosiolib
[ 70%] Built target libc
[ 71%] contract...
[ 71%] Built target copy_skeleton_contract
[ 71%] Built target identity_common
[ 72%] Built target identity_interface
[ 72%] Built target print_floats
[ 72%] Built target eosio-s2wasm
[ 72%] Built target chainbase_test
[ 72%] Built target Logging
[ 72%] Built target appbase_example
[ 72%] Built target IR
[ 73%] Built target Runtime
[ 75%] Built target WASM
[ 75%] Built target Emscripten
[ 75%] Built target WAST
[ 76%] Built target wavm
[ 76%] Built target Test
[ 76%] Built target Disassemble
[ 76%] Built target eosio-wast2wasm
[ 80%] Built target fc
[ 80%] Generating textual assembly eosio.bios.s
/root/opt/wasm/bin/llc: : error: unable to get target for 'wasm32', see --version and --triple.
contracts/eosio.bios/CMakeFiles/eosio.bios.dir/build.make:82: recipe for target 'contracts/eosio.bios/eosio.bios.s' failed
make[2]: *** [contracts/eosio.bios/eosio.bios.s] Error 1
CMakeFiles/Makefile2:4372: recipe for target 'contracts/eosio.bios/CMakeFiles/eosio.bios.dir/all' failed
make[1]: *** [contracts/eosio.bios/CMakeFiles/eosio.bios.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 80%] Generating textual assembly simple.token.s
/root/opt/wasm/bin/llc: : error: unable to get target for 'wasm32', see --version and --triple.
contracts/simple.token/CMakeFiles/simple.token.dir/build.make:82: recipe for target 'contracts/simple.token/simple.token.s' failed
make[2]: *** [contracts/simple.token/simple.token.s] Error 1
CMakeFiles/Makefile2:2411: recipe for target 'contracts/simple.token/CMakeFiles/simple.token.dir/all' failed
make[1]: *** [contracts/simple.token/CMakeFiles/simple.token.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2
>>>>>>>>>>>>>>>>>>>> MAKE building EOSIO has exited with the above error.

sometimes it helps to simply rerun the script. if it fails again, try to
sudo apt update
sudo apt upgrade
rm -rf build
./eosio_build.sh

If available to you, you can try additionally on ubuntu 18.04

try the latest 1.2.0 (please close this issue if it works for you).

I rebuild llvm, it's works then.


Workcomp Payroll

@gurgentil This is no longer needed. We're just going to ask what is the total payroll amount for the business.


Verify checksum for downloaded archives

Given that the sources are http only, I feel this is especially important.

Coverage remained the same at 24.141% when pulling 7b4c7363b712ac66f46cc0eeb2ff94e6a403ac76 on tribut:check-sha into 9df2a780e69e6a73c34b0f2a164e933d717016e4 on JuliaDiffEq:master.

Thanks!


Use 64-bit RHS operand for shift

since downcast (unsafe cast) is disabled
and the impl always cast the RHS to the result type, which has type of max(LHS, (u)intp).
So the result type is either machine width or bigger and would have enough bits for valid values of RHS.

Codecov Report

Merging #2396 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2396      +/-   ##
==========================================
- Coverage   86.25%   86.24%   -0.01%
==========================================
  Files         315      315
  Lines       60004    60004
  Branches     6518     6518
==========================================
- Hits        51756    51752       -4
- Misses       7199     7201       +2
- Partials     1049     1051       +2

I have manually checked on 32-bit linux.


Keyboard shortcuts

This one is an easy one :)

[HOME] key: move the playback cursor to t=0
[END] key: move the playback cursor to t=end
in modal popups like the text settings popup (with color, etc.): [ESC] key should close the popup

agreed :)
I'll try to get these done tonight


[Suggestion] split get_node_attribute into 2 methods

get_node_attribute  is essentially 2 methods in 1, the first to set an attribute  if value exists, and the second to get the attribute else it dose not.
I find it quite misleading and think it would be greatly simplified if it was split into:
def get_node_attribute(self, node_handle, attribute, default=""):
    """Get the specified attribute of the given node"""
    return self.tk.call(node_handle, "attribute", "-default", default, attribute)

and
def set_node_attribute(self, node_handle, attribute, value):
    """Set the specified attribute of the given node"""
    return self.tk.call(node_handle, "attribute", attribute, value)`

Or at least be renamed to node_attribute, since the 'get' implies it can only return a variable.

Hi! Thanks for the suggestion. I've implemented your suggestion. For backwards compatibility, get_node_attribute can still be used to set the value of the node's attribute, but there is now a set_node_attribute function as well.


Davinci QT binding not found

Running version
3.14.1
Describe the bug
OpenPype menu not working.
To Reproduce
Steps to reproduce the behavior:

Go to 'Workspace'
Click on 'Scripts'
Click on 'OpenPype menu'
See error

PySide2/__init__.py: Unable to import shiboken2 from C:\Program Files (x86)\OpenPype\3.14.1\openpype\vendor\python\python_3, C:\ProgramData\Blackmagic Design\DaVinci Resolve\Fusion\Scripts\Comp, C:\Program Files\Blackmagic Design\DaVinci Resolve, C:\Users\PC\AppData\Local\Programs\Python\Python36\Lib\site-packages, C:\Program Files\Blackmagic Design\DaVinci Resolve\{VIRTUAL_ENV}\Lib\site-packages, C:\Program Files (x86)\OpenPype\3.14.1\openpype\vendor\python\python_3, C:\Program Files (x86)\OpenPype\3.14.1\openpype\vendor\python\common, C:\Program Files (x86)\OpenPype\3.14.1\openpype\tools, C:\Program Files (x86)\OpenPype\3.14.1, C:\Program Files\Blackmagic Design\DaVinci Resolve, C:\Program Files (x86)\OpenPype\3.14.1\dependencies, C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\Developer\Scripting\Modules, C:\Users\PC\AppData\Local\Programs\Python\Python36\python36.zip, C:\Users\PC\AppData\Local\Programs\Python\Python36\DLLs, C:\Users\PC\AppData\Local\Programs\Python\Python36\lib, C:\Users\PC\AppData\Local\Programs\Python\Python36
Traceback (most recent call last):
  File "C:\ProgramData\Blackmagic Design\DaVinci Resolve\Fusion\Scripts\Comp\__OpenPype__Menu__.py", line 20, in <module>
    result = main(os.environ)
  File "C:\ProgramData\Blackmagic Design\DaVinci Resolve\Fusion\Scripts\Comp\__OpenPype__Menu__.py", line 11, in main
    import openpype.hosts.resolve.api as bmdvr
  File "C:\Program Files (x86)\OpenPype\3.14.1\openpype\hosts\resolve\api\__init__.py", line 12, in <module>
    from .pipeline import (
  File "C:\Program Files (x86)\OpenPype\3.14.1\openpype\hosts\resolve\api\pipeline.py", line 19, in <module>
    from openpype.tools.utils import host_tools
  File "C:\Program Files (x86)\OpenPype\3.14.1\openpype\tools\utils\__init__.py", line 1, in <module>
    from .widgets import (
  File "C:\Program Files (x86)\OpenPype\3.14.1\openpype\tools\utils\widgets.py", line 3, in <module>
    from Qt import QtWidgets, QtCore, QtGui
  File "C:\Program Files (x86)\OpenPype\3.14.1\dependencies\Qt.py", line 1925, in <module>
    _install()
  File "C:\Program Files (x86)\OpenPype\3.14.1\dependencies\Qt.py", line 1873, in _install
    raise ImportError("No Qt binding were found.")
ImportError: No Qt binding were found.

Expected behavior
Showing the OP menu to create and publish shots.
Desktop (please complete the following information):

OS: windows
Host: Davinci

[cuID:2wb49g6]

Thank you for reporting the issue. Could you also enclose the Resolves environments? Thank you.

PySide2/__init__.py: Unable to import shiboken2 from ...
Being unable to import shiboken2 but being able to at least trigger PySide2 stands out to me that Python can find PySide2 but fails to import shiboken2 (and thus PySide2) correctly.
Can you confirm the scripts are correctly running through Python 3 in Resolve. I believe there's a preference in the application with which you can set the default python version - can you confirm the setting is set to Python 3? :)
Another workaround to avoid the setting to be required to be set to Python 3 is to change the OpenPype menu scripts extension to .py3 instead of .py - it'll force Resolve and Fusion to load it with Python 3.

Hey @aramadan0096 what is the state of this issue. Did you managed to solve it yourself or it persists? Can we close the issue?

Thank you for reporting the issue. Could you also enclose the Resolves environments? Thank you.

PySide2/__init__.py: Unable to import shiboken2 from ...
Being unable to import shiboken2 but being able to at least trigger PySide2 stands out to me that Python can find PySide2 but fails to import shiboken2 (and thus PySide2) correctly. Which could potentially happen if Python 2 tries to import a Python 3 PySide2 package.
Can you confirm the scripts are correctly running through Python 3 in Resolve. I believe there's a preference in the Resolve with which you can set the default python version - can you confirm the setting is set to Python 3? :)
Another workaround to avoid the setting to be required to be set to Python 3 is to change the OpenPype menu scripts extension to .py3 instead of .py - it'll force Resolve and Fusion to load it with Python 3.
By the way, you can confirm this suspicion by doing the following in the Py3 tab in the Console:
from PySide2 import QtWidgets

If that does work I'm pretty sure Resolve is trying to run the OpenPype menu through a Python 2 interpreter instead.

I've renamed "OpenPype__Menu.py" to "OpenPype__Menu.py3" but nothing changed, plus QtWidgets could not be imported

Hey @aramadan0096 what is the state of this issue. Did you managed to solve it yourself or it persists? Can we close the issue?

I'm really sorry for late response, I was just unable to access github... but my issue didn't  solved yet.
thanks for your understanding

When I tried to run reslove individually without OP I got this problem


ran out of memory causing ZeroDivisionError: division by zero

| epoch 013:    100 / 1899 loss=4.386, nll_loss=4.386, ppl=20.91, wps=188, ups=2.5, wpb=74, bsz=8, num_updates=22889, lr=0.0001, gnorm=2.193, clip=100%, oom=0.0012233
| WARNING: ran out of memory, skipping batch
C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\torch\autograd\function.py:41: UserWarning: mark_shared_storage is deprecated. Tensors with shared storages are automatically tracked. Note that calls to set_() are not tracked
'mark_shared_storage is deprecated. '
C:\Users\Gangolian's PC\Desktop\WikiHow Text Summary\Step 5\Topic-ConvS2S\fairseq\trainer.py:195: UserWarning: torch.nn.utils.clip_grad_norm is now deprecated in favor of torch.nn.utils.clip_grad_norm_.
grad_norm = utils.item(torch.nn.utils.clip_grad_norm(self.model.parameters(), self.args.clip_norm))
Traceback (most recent call last):
File "Topic-ConvS2S/train.py", line 29, in
main(args)
File "Topic-ConvS2S/train.py", line 23, in main
singleprocess_main(args)
File "C:\Users\Gangolian's PC\Desktop\WikiHow Text Summary\Step 5\Topic-ConvS2S\singleprocess_train.py", line 86, in main
train(args, trainer, dataset, epoch, batch_offset)
File "C:\Users\Gangolian's PC\Desktop\WikiHow Text Summary\Step 5\Topic-ConvS2S\singleprocess_train.py", line 150, in train
log_output = trainer.train_step(sample)
File "C:\Users\Gangolian's PC\Desktop\WikiHow Text Summary\Step 5\Topic-ConvS2S\fairseq\trainer.py", line 102, in train_step
agg_logging_output = self.criterion.class.aggregate_logging_outputs(logging_outputs)
File "C:\Users\Gangolian's PC\Desktop\WikiHow Text Summary\Step 5\Topic-ConvS2S\fairseq\criterions\label_smoothed_cross_entropy.py", line 68, in aggregate_logging_outputs
'loss': sum(log.get('loss', 0) for log in logging_outputs) / sample_size / math.log(2),
ZeroDivisionError: division by zero

It looks like the sample size might be 0 because there is nothing in your batch. Can you look into why you are running out of memory? Perhaps cap the number of tokens that can be in your batch.

This problem solved by decreasing the sentence size. But doesn't yet sure why sample size becomes zero.


Does not work with flatpak-installed Ghidra

I know it's far from standard, but with --path set to user's mount of Ghidra ("~/.var/app/org.ghidra_sre.Ghidra/") script fails to see files that it needs, with errors such as
FileNotFoundError: [Errno 2] No such file or directory: '/home/marcin/.var/app/org.ghidra_sre.Ghidra/Ghidra/application.properties'
application.properties can be found at ~/.var/app/org.ghidra_sre.Ghidra/config

Hello,
In my case I have it done by this steps:
first search application properties path
`-[ In the kali linux I use: updatedb; locate application.properties|grep hidra
Next:
`-[ python install.py -u root --path=/usr/share/ghidra/
Hope it's work!

i hope you dont ever consider flatpack anymore you soggy pancake

@OTsector This doesn't seem to work for me, I get ERROR: Please open Ghidra at least once to fully install dark mode.
I have definitely opened ghidra at least once. Also running Kali.


Question: how to load other javascript libraries

I'd like to use d3 to make a choropleth using http://datamaps.github.io/. In a basic html doc I would just script src="blahblahblah". How do I do that in Beaker? I tried putting that line in an HTML block before the javascript but I still can't use functions that are in the library.

any idea how i do the same thing if i'm using a docker container ?

use bkHelper.loadList, like this: http://sharing.beakernotebook.com/gist/anonymous/44e82316e785746165a6


Implement a two-stage parser

This resolves #12.

Seems like the error messages are actually only a tiny bit better :( - will have to explore this more. Errors are hard to do well.


Tuple/Struct support

Motivation: Within the realm of blockchain development and especially within the constructs of smart contracts, the use of advanced data types like tuples/structs is inevitable. The capability to utilize such complex data structures allows developers to organize and manage data efficiently. Offering native support for tuple and struct types in OrbiterSDK will empower developers to build more sophisticated and feature-rich applications, fostering the development of advanced decentralized systems.

Objective: Integrate native support for tuple/struct types within OrbiterSDK. This should allow developers to define, manipulate, and access these data types seamlessly, promoting the creation of intricate dApps and contracts that leverage the power of these data structures.

Success Criteria: Developers should be able to:

Define tuple/struct data types within their contracts.
Access and modify the values within these types seamlessly.
Ensure compatibility and interoperability with other data types and features within OrbiterSDK.

Dependencies: No dependencies.

Risks and Mitigations:

Risk: Potential issues with memory management and storage, given that tuples can be more complex than primitive data types.
Mitigation: Implement rigorous testing and validation mechanisms to ensure optimal memory usage.
Risk: Ensuring that tuple types are compatible with existing features of OrbiterSDK without introducing vulnerabilities or inconsistencies.
Mitigation: Thoroughly review and test the integration of these types with existing OrbiterSDK functionalities.
Risk: Developer unfamiliarity or confusion about using these new data types.
Mitigation: Provide comprehensive documentation and example use-cases for integrating tuple and struct types.

Resource Allocation: This task will require collaboration between core developers familiar with the OrbiterSDK's internal mechanics and those adept at C++ data structures. Given the intricacies of implementing advanced data types, a dedicated team for development, review, and testing will be essential. Proper time allocation for debugging and documentation is crucial to ensure a smooth integration of these data types into the SDK.

Tuple/struct support was implemented, closing issue.


[Generator & CLI] - Ability to auto add mucho images to /Themes/Images.js via /Images

[x] ignite-base ava tests pass
[x] fireDrill.sh passed

Describe your PR
This generator allows for easy abstraction of the images object in Images.js from the files in Images when starting a new project. This is particularly beneficial for a project that will begin with many image assets because it eliminates the individual naming (by hand) of each image in /Themes/Images.js from each file in /Images.
This PR also adds an import command to the CLI (which is a necessity for this generator due to the generate command requiring a Name and consequential generation of a superfluous file with that name)
How's it work?
This generator will look at all images in the /Images folder and:

Take the image file names
Strip out '@1x, @2x, @3x`, extraneous, etc
Turn them into a camel cased keys
Assign the new keys the values of the file names with an appended path
Format the new k: v pairs as strings and with the correct syntax for the images object (adds the require to the value as well)
Append the new files into the images object

How do I use it?

Using the current Ignite-Base Images.js and files inside /Images

Import new images at the beginning of the images object

Looks great!  I'd like to see the ignite import imagesfile command documented in readme.

One other sneaky detail: new folders have to be listed:  https://github.com/infinitered/ignite/blob/master/ignite-generator/package.json#L5-L12

@GantMan For your approval...


How to show 5 rows in each month and each month must contain it's starting dates

When I set maxRowCount to 5, then remaining dates appear separately like-

January

Remaining date of January

Problem: The dates of Jan(1) which are not adjusting in 5 rows, are coming in separate page.

Requirement: The other row of remaining dates should not appear separately. All months should have 5 rows and each month must contain starting dates(1,2,3..) For example if January month ends with 31,1,2 as outDates, then February must  contain 1,2..
It should appear like:

This is subjective, because if you set the last month as February, then what you want means that March would be generated too.

This is subjective, because if you set the last month as February, then what you want means that March would be generated too.


Kics doesn't scan zip files if the user doesn't provide the complete path of zip file

Expected Behavior
When running a kics scan with "-p folder-name", kics should perform a scan in all files within this folder, including ".zip" files.
Actual Behavior
When running a kics scan with "-p folder-name", kics scan all files (.tf, .yaml ...) but ignores ".zip" files inside the folder. By this way, kics cannot found these files and doesn't perform a scan for them.
Steps to Reproduce the Problem

You should have a valid ZIP file (contaning a valid sample inside) to perform a successful scan.
Open terminal.
Go to kics folder.
Create a folder (example: samples-folder)
Put the zip file inside this folder (example: files.zip)
Run: "kics scan -p samples-folder"
Kics will perform a scan, but no files will be scanned.
Run: "kics scan -p samples-folder/files.zip"
Kics will perform a successful scan (scanning the files.zip content)

Specifications

Version: n/a
Platform: n/a
Subsystem: n/a

This is expected behavior.


add automatic module name to apm-agent-attach

What does this PR do?
This PR adds an Automatic-Module-Name for the apm-agent-attach. This way, we can use the programmatic attach also in JPMS projects.
Checklist

[ ] This is an enhancement of existing features, or a new feature in existing plugins

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] I have made corresponding changes to the documentation

[ ] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that would fail without this fix

[ ] This is a new plugin

[ ] I have updated CHANGELOG.asciidoc
[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have updated supported-technologies.asciidoc
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.

[x] This is something else

[x] I have updated CHANGELOG.asciidoc

run docs-build


Introduce ociRegistry access support for module-templates

Proposed change(s):

Ignore parsing access layers with type ociRegistry

/test all

/test all


Added Go 1.16 to all OSes toolsets

Description
Added Go 1.16.0 version to all OSes toolsets

Related issue: actions/virtual-environments#2728
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run

/azp run

/azp run


guile-sdl2: 0.3.1 -> 0.4.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/guile-sdl2/versions.
meta.description for guile-sdl2 is: '"Bindings to SDL2 for GNU Guile"'.
meta.homepage for guile-sdl2 is: '"https://dthompson.us/projects/guile-sdl2.html"

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.4.0 with grep in /nix/store/kwph57hx5z4vnphkkm6d0chg5yvv3l6m-guile-sdl2-0.4.0
directory tree listing: https://gist.github.com/f856cf63a73e5974fe92d2fd9e577dc5
du listing: https://gist.github.com/f8e7744ce105d89c61ba6ff55e55263e

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

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
guile-sdl2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kwph57hx5z4vnphkkm6d0chg5yvv3l6m-guile-sdl2-0.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A guile-sdl2 https://github.com/r-ryantm/nixpkgs/archive/f5fb6dd796150d1c1872914c29cf6e9f6790bc9b.tar.gz

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

cc @seppeljordan @vyp for testing.

It's a bot, how could the diff not look good?

@JohnAZoidberg ocassionaly it updates something that has additional hashes that need updating or that has some complex structure that makes the update diff wrong or incomplete.


Comment out first pending tag in test

The first test in the test file should have the pending tag commented out.

@andrewtimberlake great catch! Thanks! :tada:


Enhancement: Use SVG badge for displaying Travis build status

This PR

[x] uses an SVG badge for displaying the Travis build status, as it is more pleasing for the eye

Wow, the font on the SVG badge looks way better. :+1:


yonatang solution: a jdk8 friendly, no unsafe code, epsilon-gc friendly solution

Check List:

[X] Tests pass (./test.sh <username> shows no differences between expected and actual outputs)
[X] All formatting changes by the build are committed
[X] Your launch script is named calculate_average_yonatang.sh (make sure to match casing of your GH user name) and is executable
[X] Output matches that of calculate_average_baseline.sh
[X] For new entries, or after substantial changes: When implementing custom hash structures, please point to where you deal with hash collisions (line number) - line 61, the station string is linearly transformed to a long[13]. if there is a hash collision, it will jump to the next empty space.

Execution time: 27.16 seconds (MacBook pro 2019 i9) - about ~25% slower then one of the faster solutions, probably around 4s on the evaluation machine.
Execution time of reference implementation: Merykitty's - 22.04 seconds (the safe, openjdk version)

A few words
I took the challenge of writing a "corporate friendly" solution: something that will run reasonably fast, without using any unsafe code, that can be compiled and executed with JDK 8. Just trying to make a point that corporate code can still be fast, if you really want to.
In order to compensate these limitations, I implemented an allocation-free solution (almost everything is on the stack), that could leverage the Epsilon GC, when running with a modern JVM. Using Epsilon GC reduces processing time by ~20%, comparing to G1GC. I believe the dominant contributing factor is not directly the GC overhead reduction, but it is the elimination of the CPU context switching, which can invalidate the CPU L1/L2 caching.

Thx for participating and explaining the reasoning! Loving to see the usage of EpsilonGC. This comes in at  00:12.800, i.e. a bit slower (relatively speaking) than what you have observed. Could be due to differences in ISA, e.g. longer vector registers on the eval machine from which the top entries benefit disproportionally more.


Add option to ignore the existance of certificates.

I needed a way to offer host-by-host migration from yaml to eyaml, and this was the only thing I could think of, considering we have ONE hiera.yaml file on everything and it would be a lot more work to start distributing different ones onto different machines in different environments etc.
So instead offer the option to hiera-eyaml to ignore missing certificates by setting the option :pkcs7_enforce_certs: false which makes hiera-eyaml not fail if/when the certs are missing. Once they certificates have been copied onto the machine(s), it starts decrypting the values correctly.
It's horribly ugly, and if it can be rewritten cleaner, feel free. Although I know several languages really good, this is the very first I've looked at Ruby (and I'm not impressed! :).

Hi @FransUrbo. I know that this PR is rather old. Are you still interested in getting this merged? If so, could you please rebase?

Closing due to inactivity. Please feel free to re-open.

Closing due to inactivity. Please feel free to re-open.


Missing MTL files?

Attempted to load several models (e.g., models/Razer_Abyssus_Ambidextrous_Gaming_Mouse/model.xml) into bin/simulate, but hit this error multiple times:
MuJoCo Pro version 2.10
Error: Unknown mesh file type: model.obj
Object name = model, id = 0, line = 5, column = 5
Regenerating with obj2mjcf does not seem to help - maybe due to user error?

Oops, I missed the first closed issue!


Request for Mina Metrics info.

I would like to request the following info to appear on Mina metrics.
Next block production time: Format in seconds
Synced status: Format as string
Latest chain height: Format in integer
Maximum observed chain length: Format in integer
Client version: Format as string
Thanks

+1 to getting the block height in the metrics. Currently, we just have Coda_Transition_frontier_max_blocklength_observed and Coda_Transition_frontier_max_unvalidated_blocklength_observed but can lead to situations where the node gets stuck in this state and cannot be identified:


Extension Properties

Closes #32

Minor: the commit message is wrong feat(camunda-platform): add execution properties group

Can be merged after adressing my two super minor comments

rebased so that this is auto-merged


feat(copy-updates): align copy component impl with latest designs

This PR updates the copy clipboard components to use the latest designs and interactions specified in core.
One outstanding issue that I'm not sure how to resolve is that the tooltip text for the copy buttons updates to "Copied" for a few seconds after firing the copy action, however this value isn't updated in the DOM until you move your cursor away from the copy button and then back over the top of it again. I'm using property bound [tooltip] syntax which I thought would handle this but doesn't seem to. Any idea how to solve this?
make widths configurable
improve tests
add tooltip for copy buttons
specify tooltip container to fix tooltip flutter
use input element for copy value container
remove redundant triggers
clean up view templates
use obj for storing common values in copyBase
use readonly input instead of span so copy value is scrollable
use tooltipText input prop instead of tooltip to avoid namespace collision
specify body for container attribute to fix tooltip styling issues
avoid breaking changes by setting buttonAriaLabel to buttonLabel value when passed in
update tests to use new property name

Deploy preview for patternfly-ng ready!
Built with commit 0eded5baea8610d18133024d31a193ab9cd9ae42
https://deploy-preview-444--patternfly-ng.netlify.com

:tada: This PR is included in version 4.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please add NBT tag support

Please add nbt tag

for where? already item supports NBT tags

Enchant, Potion, Egg, Damaged item, Items from other plugins support (NBT tag is not supported)

what custom items plugin are you currently using?

i'm using item adder


Java: surface cleanup

Codecov Report

Merging #1675 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1675      +/-   ##
============================================
+ Coverage     85.52%   85.52%   +<.01%
  Complexity     4290     4290
============================================
  Files           405      405
  Lines         16863    16865       +2
  Branches       1760     1760
============================================
+ Hits          14422    14424       +2
  Misses         1854     1854
  Partials        587      587

Impacted Files
Coverage Δ
Complexity Δ

...nsformer/java/JavaGapicSurfaceTestTransformer.java
98.31% <100%> (+0.01%)
31 <0> (ø)
:arrow_down:

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 9a9cb9a...1ac48be. Read the comment docs.


s390x assembly pack: add support for z14 kma instruction

This is the next (reworked) part of the 'improve s390x support' PR:
This patch series adds support for the KMA instruction, an aes-gcm implementation.
KMA turns out to be faster also for aes-ctr (just ignore the authentication part) for >=256 bytes.

What's keeping this back? I mean I thought we agreed that you fix up standard stack frame allocation, and then it should be ready to go...

Sorry @dot-asm , was waiting because i understood you wanted to examine the gcm c glue first. However, here comes the reworked asm.
Not dependent on the c glue, aes-ctr would be ready to go. Should i put it in a seperate PR?

Changes:

Improved tls code path to use a single call to kma instruction.
Also saved some coprocessor calls during setup.
Code is independent of gmul now. This required some tricks with iv setup in case ivlen != 12.  :-)
Moved all logic outside of the asm eliminating stackframe allocation and giving caller full control.

speed benchmark's small block performance (independent of 1 and 2) increased slightly compared to original submission.
ping @dot-asm

Fixed tag computation in tls code path. Test suite didnt catch this because it was the same (wrong) tag for both server and client. Would it make sense to add pairwise consistency tests against a possibly installed openssl version to catch this kind of things?

whats up with this one ?

Thanks for reminder btw...

thanks for the review. made all changed except the in-place thing to keep it consistent with default code path.
pushed with wrong commit email, causing the need-cla label, sorry. push -f ed the rework with correct mail.

When you're done with last nits, could you state if all to-be-squashed commits should be squashed with last [or one before last?] commit? If not, then squash them to your liking and I'll have one last look. After all, there were some substantial changes...

ok, done with nits and squashing.


Remove reference to app proxy blog.

The blog is no longer available and there is no app proxy blog replacement.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Merge pull request #173 from bgoonz/preview

Skip to content

Pull requestsIssues
Marketplace
Explore

bgoonz/alternate-blog-theme3

Watch

Fork

Star 7

Code

Issues2

Pull requests1

Discussions

Actions

Projects

Wiki5

Settings

More
Edit Code
Gitpod
Merge pull request #173 from bgoonz/preview #174
Open
preview  master
+0 -0
 Conversation 0 Commits 1 Checks 1 Files changed 0
Conversation

Owner
bgoonz 12 seconds ago
|
No description provided.
|

[Merge pull request](https://github.com/bgoonz/alternate-blog-theme3/pull/174/commits/9d2d9bcab4307fb2bb28f20ef76749cd5cb0d039 "Merge pull request #173 from bgoonz/preview") [#173](https://github.com/bgoonz/alternate-blog-theme3/pull/173) [from bgoonz/preview](https://github.com/bgoonz/alternate-blog-theme3/pull/174/commits/9d2d9bcab4307fb2bb28f20ef76749cd5cb0d039 "Merge pull request #173 from bgoonz/preview")
Verified
[9d2d9bc](https://github.com/bgoonz/alternate-blog-theme3/pull/174/commits/9d2d9bcab4307fb2bb28f20ef76749cd5cb0d039)

netlify bot commented now
|
👷 Deploy Preview for bgoonz-blog-v3-0 processing.
🔨 Explore the source changes: 9d2d9bc
🔍 Inspect the deploy log: app.netlify.com/sites/bgoonz-blog-v3-0/deploys/61e4577a385d9d0008444fec
|
Merge state
Add more commits by pushing to the [master](https://github.com/bgoonz/alternate-blog-theme3) branch on bgoonz/alternate-blog-theme3.
Show environments
This branch was successfully deployed
1 active deployment
github-pages--- 9d2d9bca Deployed 2 hours ago by github-pages[bot] via deploy #3
View deployment
Hide all checks1 failing, 4 in progress, 1 pending, and 2 successful checks

Deadpendency Check Failing after 22s --- Deadpendency Check Result
Details

Header rules In progress --- This check has started...
Details

Mixed content In progress --- This check has started...
Details

Pages changed In progress --- This check has started...
Details

Redirect rules In progress --- This check has started...
Details

deploy/netlify Pending --- Deploy Preview processing.
Details

CommitCheck --- All commit messages are valid!
Details

Sourcery --- No refactorings found
This branch has no conflicts with the base branch


Update CSSProperties.json

CSS Code Hints updated with properties and attributes from my Brackets-CSSCodeHints extension.
https://github.com/coliff/Brackets-CSSCodeHints
Properties and attributes added:

background-size ("initial", "inherit")
caption-side ("right, "left")
clip-path ("auto, "inherit")
image-rendering ("auto", "crisp-edges", "inherit", "pixelated")
tab-size
touch-action ("auto", "none", "pan-x", "pan-y")
will-change

Pull request as requested by @jasonsanjose . Thanks - hope to see this in Brackets Core soon. :-)

this PR does not seem to be actualized for 3 months now. maybe it's worth closing and, if there's interest, we could re-open it.

@busykai I agree with you. @coliff Please feel free to reopen it after you have reworked on this PR.


Added changes common to both PY 2 and 3

iteritems --> items
Replaced cPickle with pickle
typecasted to list wherever necessary

Codecov Report

Merging #89 into master will decrease coverage by 0.03%.
The diff coverage is 80.3%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
- Coverage   67.35%   67.32%   -0.04%
==========================================
  Files          80       80
  Lines        5753     5753
==========================================
- Hits         3875     3873       -2
- Misses       1878     1880       +2

Impacted Files
Coverage Δ

scripts/lib/xpedite/jupyter/snippetsBuilder.py
92.68% <ø> (ø)
:arrow_up:

scripts/lib/xpedite/dependencies/config.py
69.23% <0%> (ø)
:arrow_up:

scripts/lib/xpedite/profiler/__init__.py
47.57% <0%> (ø)
:arrow_up:

scripts/lib/xpedite/txn/repo.py
67.08% <0%> (ø)
:arrow_up:

scripts/lib/xpedite/analytics/timelineFilter.py
0% <0%> (ø)
:arrow_up:

scripts/lib/xpedite/analytics/conflator.py
21% <0%> (ø)
:arrow_up:

scripts/lib/xpedite/report/__init__.py
96.29% <100%> (ø)
:arrow_up:

scripts/lib/xpedite/types/containers.py
71.42% <100%> (ø)
:arrow_up:

scripts/lib/xpedite/jupyter/xpediteData.py
94.87% <100%> (ø)
:arrow_up:

scripts/lib/xpedite/report/flot.py
100% <100%> (ø)
:arrow_up:

... and 15 more

Continue to review full report at Codecov.

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


[VS Code] [Audio] Request startOrJoinCall failed unexpectedly without providing any details.

Error:
Request startOrJoinCall failed unexpectedly without providing any details.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS-Audio

extensionVersion
0.1.91

applicationName
VSCode

applicationVersion
1.72.1

platformName
Windows

platformVersion
10.0.22621

We're unable to prioritize fixes to this area as we re-evaluate our priorities and product direction. We understand that this maybe disappointing. We appreciate your input and comments on this issue till now. We will soon be sunsetting this feature and will work towards a better use experience for communication needs for Live Share users from the editor.


how do i download this

i click clone or download i download as a zip and i open it but its just a file with all the code not an exe that i can run

https://github.com/gibbed/Gibbed.Borderlands2/releases/latest


crowsetta raises unexpected argument error

When calling the vak library, the an error is raised. The Meta class doesn't have an input argument called to_seq. crowsetta version is latest 2.0.0.
Traceback (most recent call last):
File "C:\Program Files\Python36\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "C:\Program Files\Python36\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\Users\User\venv3\Scripts\vak.exe_main.py", line 5, in
File "c:\users\user\venv3\lib\site-packages\vak_init.py", line 1, in
from . import main
File "c:\users\user\venv3\lib\site-packages\vak_main_.py", line 7, in
from .cli import cli
File "c:\users\user\venv3\lib\site-packages\vak\cli_init_.py", line 3, in
from .prep import prep
File "c:\users\user\venv3\lib\site-packages\vak\cli\prep.py", line 5, in
from .. import dataset
File "c:\users\user\venv3\lib\site-packages\vak\dataset_init_.py", line 3, in
from .classes import MetaSpect, Vocalization, VocalizationDataset
File "c:\users\user\venv3\lib\site-packages\vak\dataset\classes_init_.py", line 2, in
from .vocalization import Vocalization
File "c:\users\user\venv3\lib\site-packages\vak\dataset\classes\vocalization.py", line 4, in
from crowsetta import Sequence
File "c:\users\user\venv3\lib\site-packages\crowsetta_init_.py", line 13, in
from .transcriber import Transcriber
File "c:\users\user\venv3\lib\site-packages\crowsetta\transcriber.py", line 6, in
from . import formats
File "c:\users\user\venv3\lib\site-packages\crowsetta\formats.py", line 8, in
setattr(current_module, entry_point.name, entry_point.load())
File "c:\users\user\venv3\lib\site-packages\pkg_resources_init_.py", line 2443, in load
return self.resolve()
File "c:\users\user\venv3\lib\site-packages\pkg_resources_init_.py", line 2449, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "c:\users\user\venv3\lib\site-packages\gardner\yarden2seq.py", line 141, in
to_seq=yarden2seq
TypeError: init() got an unexpected keyword argument 'to_seq'

Hi and thanks for your interest in the library.
Sorry for the confusion: vak still uses crowsetta 1.1.1.
Installing that version should fix this error.
If you're taking the library for a test drive, I would suggest using this data set:
https://figshare.com/articles/Bengalese_Finch_song_repository/4805749
The yarden format is specific to one lab and there's not yet any publicly-available datasets with that format.
If you use that repository, the annotation format for the config.ini files would be 'notmat' and the audio format would be 'cbin'. There are some example config files in tests/test_data/configs.
The version of crowsetta vak uses will go up to 2.0.0 in version 0.3.0:
https://github.com/NickleDave/vak/projects/5
but we're trying to get a paper out that's based on the current version, so that won't be until October at least.


Postgres numeric overflowing pgql js number

Currently postgraphql "treats" numeric as javascript's number.
PG Docs mention the following storage size for numeric:
Storage size: variable (User specified precision exact)
Range: up to 131072 digits before the decimal point; up to 16383 digits after the decimal point
JS number type seems to have a more fixed length (53 bits?).
Consider having a string based solution when serializing to JSON.
Similar to #302

Yeah. This is really unfortunate given we just made a breaking change for big integers 😣
For now, it’s probably a good idea to specify which number type you specifically want 👍

v4 treats numeric as a string (specifically a BigFloat); documented here:
https://www.graphile.org/postgraphile/v3-migration/#very-large-numbers
This was a breaking change.


Should Slim 4's middleware be LIFO or FIFO?

Slim 3 currently uses a Last In, First Out (LIFO) model for middleware.
That is:
$app->add('middleware3');
$app->add('middleware2');
$app->add('middleware1');

will execute the middleware in the order:

middleware1
middleware2
middleware3

This works if you imagine middleware as layers of an onion and adding a new middleware adds a new layer to the outside of the onion.
An alternative, would be to use First In, First Out (FIFO) model.
This is, the same PHP code would execute the middleware in this order:

middleware3
middleware2
middleware1

This works if you imagine middleware as a pipleline going from top to bottom where the first one you add is the first one that's executed, then the second one added is executed, etc.
Should Slim 4 change to the FIFO model?

Definitely FIFO ("first in, first out") :-)
The code goes from top to bottom, so the middleware should also run in the same direction.
Reading the middleware settings would make it easier for the developer to read and maintain, as it corresponds to the mental and natural order of code and logic.
Showing code of a middleware stack in a training or presentation (slide) is better understood by everyone. Because everyone reads the code from above and can therefore follow the sequence better.
FIFO simplifies the writing of tests which have to consider the sequence of the stack. etc...
FIFO has become standard in the PHP community and in all other middleware based frameworks (see Zend Expressive).

With FIFO, which order would the middlewares run after $app? (It really doesn't matter much to me, I'm just curious.)

For technical reasons I would prefer LIFO. With FIFO Slim could not [1] implicitly build the recursive middleware stack when calling add (see MiddlewareAwareTrait) [2], but would need to cache the list of middlewares first, to create the stack (by reversing the cached middleware list) when the stack is executed.
While FIFO might be more convenient, I think LIFO fits better for Slim – well, because it should be slim.
[1] Switching the middleware implementation to a queue based one (where each middleware's $next points back to the Middleware Dispatcher which then calls the next middleware) would allow to keep the implicit building functionality, but requires managing a middleware index (I personally prefer the current implementation)
[2] A middleware needs have a reference to the next middleware. In FIFO the next middleware is not yet known when calling App:add.

FIFO mode is more natural and Zend expressive also using FIFO mode.

FIFO is more natural when coding but I vote for the lightest solution (see @bnf comment above), Slim should stay as simplest / lightest / fastest as possible

The current LIFO model certainly adds some cognitive overhead for me.

FIFO. More intuitive for me.

FIFO for the intuitive point, but ideally (and I know this may be outside scope), an optional priority/"before" option (ie 3rd party code may register authentication middle ware first, but API design needs CORs headers checked before authentication).

FIFO is definitely the more intuitive, less confusing.

Would prefer FIFO as more intuitive (like others have said) also easier to parse and understand when looking at it because you can change the order of $app->add(...) to change the order they're applied.

FIFO for me, too, because it feels more natural, if you don't eat onions every day. I remember that I struggled with LIFO because i didn't read the Slim3-documentation carefully enough.

I know it is LIFO so I work with it as it is and that is fine for me. Perhaps what is most important is that it is really clear in the docs what is used. Personally when I started I expected FIFO and only realized I misunderstood when my tests failed.

Either LIFO or FIFO is fine with me as long as it is clearly documented. I would be in favor of using whichever one has the simplest implementation.

I prefer the LIFO approach, but if we change to FIFO's way, we could find an easy way to add an setting for that.

+1 for @theodorejb "keep Slim as slim as possible".

I prefer FIFO.

Throwing in my €0.02, I personally think FIFO makes more sense for reading as you can take a 'top down' approach

We could solve the issue by allowing the developer to set with FIFO/LIFO
It would make the migration path easier if we decide to default it to FIFO.

FIFO by default !

I prefer FIFO myself.

FIFO
<?php
/**
 * Slim Framework (https://slimframework.com)
 *
 * @link      https://github.com/slimphp/Slim
 * @copyright Copyright (c) 2011-2017 Josh Lockhart
 * @license   https://github.com/slimphp/Slim/blob/3.x/LICENSE.md (MIT License)
 */
namespace Slim;

use RuntimeException;
use Psr\Http\Message\ServerRequestInterface;
use Psr\Http\Message\ResponseInterface;
use UnexpectedValueException;

/**
 * Middleware
 *
 * This is an internal class that enables concentric middleware layers. This
 * class is an implementation detail and is used only inside of the Slim
 * application; it is not visible to—and should not be used by—end users.
 */
trait MiddlewareAwareTrait
{
    /**
     * middleware call stack
     *
     * @var callable
     */
    protected $stack = [];

    /**
     * Middleware stack lock
     *
     * @var bool
     */
    protected $middlewareLock = false;

    /**
     * Add middleware
     *
     * This method prepends new middleware to the application middleware stack.
     *
     * @param callable $callable Any callable that accepts three arguments:
     *                           1. A Request object
     *                           2. A Response object
     *                           3. A "next" middleware callable
     * @return static
     *
     * @throws RuntimeException         If middleware is added while the stack is dequeuing
     * @throws UnexpectedValueException If the middleware doesn't return a Psr\Http\Message\ResponseInterface
     */
    protected function addMiddleware(callable $callable)
    {

        if ($this->middlewareLock) {
            throw new RuntimeException('Middleware can’t be added once the stack is dequeuing');
        }

        if (is_empty($this->stack)) {
            $this->seedMiddlewareStack();
        }

        $this->stack[] = $callable;

        return $this;
    }

    /**
     * Seed middleware stack with first callable
     *
     * @param callable $kernel The last item to run as middleware
     *
     * @throws RuntimeException if the stack is seeded more than once
     */
    protected function seedMiddlewareStack(callable $kernel = null)
    {
        if (!is_empty($this->stack)) {
            throw new RuntimeException('MiddlewareStack can only be seeded once.');
        }
        if ($kernel === null) {
            $kernel = $this;
        }
        $this->stack[] = $kernel;
    }

    protected function prepare()
    {
        $handler = array_shift($this->stack);
        if (!empty($this->stack)) {
            $this->stack = $this->container->get('settings')['middleware_order'] === 'FIFO' ? array_reverse($this->stack) : $this->stack;
            foreach ($this->stack as $callable) {
                $next = $handler;
                $handler = function (
                    ServerRequestInterface $request,
                    ResponseInterface $response
                ) use (
                    $callable,
                    $next
                ) {
                    $result = call_user_func($callable, $request, $response, $next);
                    if ($result instanceof ResponseInterface === false) {
                        throw new UnexpectedValueException(
                            'Middleware must return instance of \Psr\Http\Message\ResponseInterface'
                        );
                    }

                    return $result;
                };
            }
        }
        return $handler;
    }

    /**
     * Call middleware stack
     *
     * @param  ServerRequestInterface $request A request object
     * @param  ResponseInterface      $response A response object
     *
     * @return ResponseInterface
     */
    public function callMiddlewareStack(ServerRequestInterface $request, ResponseInterface $response)
    {
        if (is_null($this->stack)) {
            $this->seedMiddlewareStack();
        }
        /** @var callable $start */
        $start = $this->prepare();
        $this->middlewareLock = true;
        $response = $start($request, $response);
        $this->middlewareLock = false;
        return $response;
    }
}

untested

I prefer LIFO (3.x style) at default, the onion model is very spectacular and logic.

I like @sunchuo 's approach. Have a default but let the user configure this via settings.

Making it a configurable option may sound nice, but it would make the code even more complex and also make it harder to contribute to other projects that use Slim, because it wouldn't be clear whether their middleware is LIFO or FIFO without looking at their configuration settings.

I like onion-style LIFO because it seems more consistent with the $app->group()->add() construction, where ->group() becomes the innermost middleware. Also I like onions.

I like the onion style as well.
But I also think @geggleto has a point, although that could be entirely dependent on amount of work required.

FWIW I'm used to and like LIFO

@RyanNerd
@theodorejb
@ellotheth
@matthewtrask
sorry for post untested code. there are some typos.
now it works well and passed the ./tests/MiddlewareAwareTest.php
Slim\Tests\Mocks\Stackable have no container。so i add "isset($this->container)"。
sorry for have no time to do better.

I like it FIFO style. But i feel like the developer should be able to decide which way he want's to organize his code and middleware.
The default should stand on LIFO, just to have lesser migration works for older-projects. (I'm just lazy and don't want to check back on some parts of my code 😆  )

I think it should not be configurable. It would add unnecessary complexity, where clear documentation would solve the problem. If we speak about a "middleware stack", the word "stack" already tells me it is LIFO. So I suggest keeping LIFO.

I would say go with FIFO. I've just begun using Slim3 as a framework and at first I didn't realize the LIFO model and then when writing my own middleware and wondering why the second middleware wasn't getting the correct attributes, I realized the LIFO model. But by reading the code, I assume you read come from top to bottom, FIFO would make more sense.
Don't know if this is possible, but if we can set LIFO or FIFO as the default, and have an option when start the $app to change it to the other.
So if it's LIFO by default, you can change toe FIFO; vice versa.

Whichever way is chosen we must be mindful to name things properly:

LIFO = Stack
FIFO = Queue

If we decided to go the Queue route (which I and my alter ego @johnrobertporter think so) I think it would open up a great way of handling middleware that is not available to us yet.
A Queue could be altered during runtime to add or remove middleware further along the Queue.
I think this would be a powerful approach for route handling and route middleware, by simply appending them to the current middleware queue. This would mean a change in the signature for a route callback however.
I never really understood the need for passing args in a callback, and it means we could make all aspects of the application into middleware, instead of having separate signatures for separate aspects.
I am happy to discuss this idea further with anyone who's interested :)

As a user I always found middlewares being LIFO something I tend to forget about from one project to the next. It's counter intuitive IMO.

I know we want slim to be - well - slim
But a queue is different from a stack
And you have to factor migration pain into this
I'd argue the middleware iterator should be injectable and match an interface
Provide a default implementation of queue and stack (FIFO and LIFO)
pick one as a default ( I don't really care, just name it right and document the heck out of it  - I'd mildly recommend a script to help with migration that recommends the BC version perhaps? )
With that you open up

The default case works as expected out of the box with no configuration
the second most common use case works out of the box with simple configuration
Really complex cases become available by plugging in a custom implementation

My 2 cents :)

And on top of that all, async queue implementation option could be very useful, i think) ...at least in 5.x)

Should Slim 4 change to the FIFO model?

No.

Should Slim 4's middleware be LIFO or FIFO?

Neither.
I'd make it configurable defaulting to LIFO for an easier migration path.
I find @auroraeosrose 's suggestion to be the best approach.

Order remains LIFO like it was in Slim 3.x. Closing as we just merged #2555


One Time & Long Term Mentorship Status

On the Mentor Profile - the mentor should have 2 status:

[x] One Time Mentorship

[x] Long Term Mentorship

The status can be: free , busy

@tsg @ClaraPapaya @sabine-mansour @lorepirri
I know we've talked to have ‘Your Profile‘ page the same for Mentor and Mentee. But we have to have a place for:
Mentor Incognito
One Time Mentorship
Long Term Mentorship
Shall we introduce a different ‘Your Profile‘ for Mentor as in the wireframe above?
Or shall we introduce these extra fields to the page ‘Your Expertise‘

done in #44


postgresql 指定多个schema的情况下. 找不到 RM channel

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
注册 io.seata.core.rpc.netty.ChannelManager#registerRMChannel 方法中 dbKeytoSet 如果postgresql指定schema的情况下.例如 jdbc:postgresql://<IP_ADDRESS>:5432/test_dev?currentSchema=system,test 则会分割成jdbc:postgresql://<IP_ADDRESS>:5432/test_dev?currentSchema=system 导致
No channel is available for resource[jdbc:postgresql://<IP_ADDRESS>:5432/test_dev?currentSchema=system,test]
13:44:08.061 ERROR --- [      AsyncCommitting_1_1] io.seata.server.coordinator.DefaultCore  : Committing branch transaction exception: BR:128130304060690433/128130292459245568

Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version : 1.8
OS : mac
Others: seata1.4.1

duplicate  https://github.com/seata/seata/issues/3591 close.


Feature/reduce docker image

Attempt to reduce the size of the docker container image to be run in production, for the sake of security, by removing build dependencies and dev-only Python packages.

@ehmadzubair @sheralim012 would you be able to cast your eyes over this PR at your earliest convenience? this is not urgent.


When search_type="similarity_score_threshold, retriever returns negative scores

System Info

OS: Ubuntu 20.04
langhcain==0.0.297
 chromadb==0.4.12
Python 3.9.18

Who can help?
@hwchase17
@agola11
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[X] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
from langchain.document_loaders import TextLoader
from langchain.embeddings.huggingface import HuggingFaceEmbeddings
from langchain.text_splitter import CharacterTextSplitter
from langchain.vectorstores import Chroma

loader = TextLoader("state_of_the_union.txt")
documents = loader.load()
text_splitter = CharacterTextSplitter(chunk_size=1000, chunk_overlap=0)
texts = text_splitter.split_documents(documents)

embeddings = embeddings = HuggingFaceEmbeddings(model_name='all-MiniLM-L6-v2', encode_kwargs={'normalize_embeddings': True})
docsearch = Chroma.from_documents(texts, embeddings)

retriever = docsearch.as_retriever(search_type="similarity_score_threshold", search_kwargs={'score_threshold': 0.2})

print(retriever.get_relevant_documents('Ketanji'))

The above code returns negative similarity scores for all retrieved results:
lib/python3.9/site-packages/langchain/vectorstores/base.py:257: UserWarning: Relevance scores must be between 0 and 1, got

[(Document(page_content='Tonight. I call on the Senate to: Pass the Freedom to Vote Act. Pass the John Lewis Voting Rights Act. And while you’re at it, pass the Disclose Act so Americans can know who is funding our elections. \n\nTonight, I’d like to honor someone who has dedicated his life to serve this country: Justice Stephen Breyer—an Army veteran, Constitutional scholar, and retiring Justice of the United States Supreme Court. Justice Breyer, thank you for your service. \n\nOne of the most serious constitutional responsibilities a President has is nominating someone to serve on the United States Supreme Court. \n\nAnd I did that 4 days ago, when I nominated Circuit Court of Appeals Judge Ketanji Brown Jackson. One of our nation’s top legal minds, who will continue Justice Breyer’s legacy of excellence.', metadata={'source': 'state_of_the_union.txt'}), -0.18782109124725155),

(Document(page_content='Madam Speaker, Madam Vice President, our First Lady and Second Gentleman. Members of Congress and the Cabinet. Justices of the Supreme Court. My fellow Americans.  \n\nLast year COVID-19 kept us apart. This year we are finally together again. \n\nTonight, we meet as Democrats Republicans and Independents. But most importantly as Americans. \n\nWith a duty to one another to the American people to the Constitution. \n\nAnd with an unwavering resolve that freedom will always triumph over tyranny. \n\nSix days ago, Russia’s Vladimir Putin sought to shake the foundations of the free world thinking he could make it bend to his menacing ways. But he badly miscalculated. \n\nHe thought he could roll into Ukraine and the world would roll over. Instead he met a wall of strength he never imagined. \n\nHe met the Ukrainian people. \n\nFrom President Zelenskyy to every Ukrainian, their fearlessness, their courage, their determination, inspires the world.', metadata={'source': 'state_of_the_union.txt'}), -0.2858684850499025),

 (Document(page_content='We are inflicting pain on Russia and supporting the people of Ukraine. Putin is now isolated from the world more than ever. \n\nTogether with our allies –we are right now enforcing powerful economic sanctions. \n\nWe are cutting off Russia’s largest banks from the international financial system.  \n\nPreventing Russia’s central bank from defending the Russian Ruble making Putin’s $630 Billion “war fund” worthless.   \n\nWe are choking off Russia’s access to technology that will sap its economic strength and weaken its military for years to come.  \n\nTonight I say to the Russian oligarchs and corrupt leaders who have bilked billions of dollars off this violent regime no more. \n\nThe U.S. Department of Justice is assembling a dedicated task force to go after the crimes of Russian oligarchs.  \n\nWe are joining with our European allies to find and seize your yachts your luxury apartments your private jets. We are coming for your ill-begotten gains.', metadata={'source': 'state_of_the_union.txt'}), -0.3382525501830016),

 (Document(page_content='For that purpose we’ve mobilized American ground forces, air squadrons, and ship deployments to protect NATO countries including Poland, Romania, Latvia, Lithuania, and Estonia. \n\nAs I have made crystal clear the United States and our Allies will defend every inch of territory of NATO countries with the full force of our collective power.  \n\nAnd we remain clear-eyed. The Ukrainians are fighting back with pure courage. But the next few days weeks, months, will be hard on them.  \n\nPutin has unleashed violence and chaos.  But while he may make gains on the battlefield – he will pay a continuing high price over the long run. \n\nAnd a proud Ukrainian people, who have known 30 years  of independence, have repeatedly shown that they will not tolerate anyone who tries to take their country backwards.  \n\nTo all Americans, I will be honest with you, as I’ve always promised. A Russian dictator, invading a foreign country, has costs around the world.', metadata={'source': 'state_of_the_union.txt'}), -0.3629898842731978)]

Expected behavior
Score for each Document  should be between 0 and 1.

For anyone else who stumbles on this, the missing piece appears to be  collection_metadata={"hnsw:space": "cosine"}.  Without it, negative scores are returned in the current version of chromadb and langchain.  If you supply client or client_settings to Chroma.from_docments, you also may need to explicitly supply a collection_name other than langchain for some reason.
This GitHub repo is helpful.

I highly appreciate if you could let me know to set collection_metadata and in what function call for langchain with aws bedrock

You supply collection_metadata to Chroma when instantiating langchain.vectorstores.Chroma

in langchain 0.2x  its doesn't work

retriever_score_threshold = vector_db.as_retriever(
search_type="similarity_score_threshold", search_kwargs={'score_threshold': 0.1,'k':5}
)
retrieved_docs = retriever_score_threshold.invoke("xxx")
retrieved_docs  ，in langchain 0.2 it doesn't work OMG ，still get negative socre

I encountered the same issue as described. Initially, I was uncertain about the root cause, so I experimented with different configurations. Here’s a brief overview of what I tried and what eventually worked for me:
Initially, I used the text-embedding-3-small model with the following setup:
persist_directory = get_absolute_path('/app/chroma/')
persistent_client = chromadb.PersistentClient(path=persist_directory)
vector_db = Chroma(
    client=persistent_client,
    persist_directory=persist_directory,
    collection_name="collection-foobar",
    embedding_function=OpenAIEmbeddings(),
    collection_metadata={"hnsw:space": "cosine"}
)
retriever = vector_db.as_retriever(
    search_type="similarity_score_threshold",
    search_kwargs={'score_threshold': 0.6},
    k=10
)

With this configuration, I encountered issues with negative scores. After switching to the text-embedding-ada-002 model, the problem was resolved. If anyone else tries this solution, please confirm whether it works for you as well. Your feedback would be greatly appreciated!

I am facing the same issue:
vectorstore = Chroma(collection_name=collection_name, embedding_function=embeddings_model, client=chroma_client.client, collection_metadata={"hnsw:space": "cosine"})
I am using the similarity_search_with_relevance_scores
this is a part of the sample output
[(), -219.28074010897063)]
warnings.warn(UserWarning: No relevant docs were retrieved using the relevance score threshold 0.7)

I did run into the same negative similarity scores using local Ollama models.
@matardy Thanks for experimenting with models and configs. But shouldn't negative scores never occur whatever model I am using? Maybe it's worthwhile to re-open the issue?

I did run into the same negative similarity scores using local Ollama models.
@matardy Thanks for experimenting with models and configs. But shouldn't negative scores never occur whatever model is used? Maybe it's worthwhile to re-open the issue.

@matardy, literally the same issue when moving to the new 3-series embedding models from openai, even encounter this when changing to max inner product.

@josefansinger how did you resolve the issue?

I did not. Sorry. Also in the LangChain Discord no response at all.

Should we reopen this ?
Just tested with the new gpt embedding model "text-embedding-3-large" same issue

Hi, any other free opensource alternative to text-embedding-3-small. Please let me know.

I used vector_store = FAISS.from_documents(text_chunks, embedding=embeddings, normalize_L2=True) and used huggingface embedding to get similarity score between 0 to 1.
Solution : normalize_L2=True

Nope, that didn't work!
If you're looking for a free open-source alternative to the text-embedding-3-small model, mxbai-embed-large is an excellent choice!

I was now able to recreate this consistently. have a script, happy to share, the issue is from the FAISS wrapper. The openai wrapper works correctly but somewhere in FAISS there are critical inconsistencies. Will try to debug mode but this is a thing.

To make matters even worse, explicitely changing the distance metric has no effect:
ar_faiss_index: FAISS = FAISS.load_local(Path(__file__).parent / "index", embeddings=embeddings, distance_strategy=DistanceStrategy.COSINE)

I am having same issue. When I use HuggingFace embedding model Alibaba-NLP/gte-large-en-v1.5, it shows this issue with the FAISS vector db. When I try same code with Open AI text-embedding-3-large embedding model this doesn't happen. It gives score between 0 and 1.

I was now able to recreate this consistently. have a script, happy to share, the issue is from the FAISS wrapper. The openai wrapper works correctly but somewhere in FAISS there are critical inconsistencies. Will try to debug mode but this is a thing.
Furthermore, querying the same faiss index with text vs with vector yields different results which makes matter even worse. (I embed it separately to do the later)

Hi, it would help to share the script. I'm curious to take a look :)

Hey all, I tried to research the bug, using this time the latest modules and the initial script :
 langchain==0.2.7
 chromadb==0.5.3
And the initial script ending in:
print(retriever.get_relevant_documents('Ketanji'))
I didn't get any scores at all, just an empty list (with the initial score_threshold of 0.2):

The omission of scores is caused by this line:

But I still don't see any negative score, even though they are (expectedly) low:

I tried this with llama3 and mistral and get negative scores

So I found out that the issue/feature is with the search with relevance score method that vector engines inherit from base VectorStore. The relevance method applies an additional relevance function which causes the negative similarities. This is an issue if your vectorstore is already returning valid distances (most cases).
All we had to do is use the other search methods like search with scores since our vector database already provides valid distances.

@pedrojrv thanks for the hint, if that is the case how does one pass the threshold to db.similarity_search_with_score(query=query, k=3) ?

I used vector_store = FAISS.from_documents(text_chunks, embedding=embeddings, normalize_L2=True) and used huggingface embedding to get similarity score between 0 to 1. Solution : normalize_L2=True

normalize_L2=True solve my problem. Thanks.


PLAT-1995: Reset TimePicker dropdown

PLAT-1995: The time picker value's which is under the time is not changed to default after selecting 'Reset' time option
Call scrollToValue for hour and minute components

This appears to be resolved by https://github.com/enyojs/moonstone/pull/2326. Proposing that we close this out @sukharenko.


Bug in actions update due to wrong config

Fix dependabot errors due to unable to find workflow files

Looking for approval here @jorgepiloto @MaxJPRey @akaszynski


Reduce metadata storage costs, persist metadata in metadata storage, and dynamically load into memory

Is your feature request related to a problem? Please describe.
Reduce metadata storage costs, persist metadata in metadata storage, and dynamically load into memory
Not all metadata is accessed frequntly, the cost of metadata in EB data cluster is absolutely considerable
Describe the solution you'd like
compatibility , performance, statbility
take Rocksdb into consideration

Maybe we can expose this feature by adding a switch for volume, sometimes some volumes are only used for data backup, may no access traffic at all.


go-lint pre-commit only applies to staged changes

The current pre-commit hook applies linting to all of the *.go files in the repo. I think this was necessary back when we had multiple go.mod and go.sum files in the repo. Either way, it doesn't seem to be necessary anymore. Now the pre-commit config will only run the linting against files that are staged for commit. This also uses the same repo we use to run our other go pre-commit tasks.
NOTE: It will run against the entire file, not just the parts that have been updated.
This screenshot shows the pre-commit linting failing on only the file staged and not on the other linting issues we currently have:

@RothAndrew I had to re-push to fix a merge conflict, when you have a moment could you re-review? Thanks.


Fixes error: expression is not a constant expression

In GCC 7.2, the bitwise assignment operators generated for C++ flags can not be constexpr, causing the build to fail. This patch makes them inline instead. Also, the second argument is made const to silence some diagnostics in Visual Studio.

Hi, can you merge? I have the same problem:
https://travis-ci.org/ezored/dependency-logger/jobs/437848402

We can't legally merge this PR because @freitass hasn't signed the CLA.  We prefer to give authors the chance to take credit for their fixes, but given this one looks to be very simple/trivial code changes, and hasn't been followed up for many months, it might be reasonable for some other contributor to make an equivalent fix in a separate PR.

Hi @xianwen, would you consider merging this PR again? I just signed the CLA, apologies for the delay.

Thanks for the update.  Approved, and leaving this for @xianwen to merge in his next round of updates.


[DOC] add a missing step for module update

Insert the documentation link:
https://docs.luos.io/pages/prototyping_boards/electronic-use.html#update-luos-robus-and-boards-firmware
Describe the issue or the suggestion:
In this section there is no step to load a project before compiling.
How would you fix the issue / which content would you add or delete?
add a specific step describing it.

Step 1 already explains how to open a project