detection of QA tests' failure

[x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:
The script run_test.sh does not see to be able to detect the tests failures.
See pyqa3 failure in https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=319210&view=logs&jobId=9a864fd9-6c8f-52ca-79ce-2aa6dca1a1de&j=9a864fd9-6c8f-52ca-79ce-2aa6dca1a1de&t=10fc5aa2-324e-5982-4c88-6b31fcab16b3

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

thanks, I guess replacing set -x by set -ex in the test script might fix this?
we can fix this in https://github.com/conda-forge/nwchem-feedstock/pull/7 if there's anything more to do there, otherwise we can open a separate PR

https://github.com/conda-forge/nwchem-feedstock/pull/7 is not working yet. Can we stop the  running jobs  so that I can analyze the logs?

I don't think it's easy to stop the jobs - does it prevent you from looking at the logs?
No need to worry about this from the point of view of cpu time.

I think I see what you mean - you pushed a new change and now I'm also unable to access the logs at the previous commit (-lrt does not exist on macos); unfortunately I closed the tab where I had them open.
It's possible that the the new push caused the logs to be removed - to be honest I'm not entirely sure what the rules are on this

Pushed an update

fixed in https://github.com/conda-forge/nwchem-feedstock/pull/7

I would re-open this one since the set -e change did not fix it.
We need to test it again with the following changesinbuild.sh NWCHEM_MODULES=nwdft solvation driverinrun_test.sh` I am suggesting the following header
#!/bin/bash
set -e

If this does not work, I am not sure where to look

Thanks for pointing this out.

in build.sh NWCHEM_MODULES=nwdft solvation driver (this causes the QA test pyqa3 to fail)

Just to check: this includes python or do I need to add this separately?

in run_test.sh I am suggesting the following header

#!/bin/bash
set -e

If this does not work, I am not sure where to look

Looking at https://github.com/nwchemgit/nwchem/blob/master/QA/doafewqmtests.mpi I suspect the problem is that this script will exit with a non-zero exit code if and only if the very last test fails.
Adding set -e in that script should fix the issue.

P.S. I think this behavior is not what one wants for a typical test run though, where one would like to see the results of all tests (not just up to the first test that fails).
I.e. ideally one could add a line to the end of the script that makes sure to return a nonzero exit code if one of the tests failed.

Thanks for pointing this out.

in build.sh NWCHEM_MODULES=nwdft solvation driver (this causes the QA test pyqa3 to fail)

Just to check: this includes python or do I need to add this separately?

The  NWChem build corresponding to NWCHEM_MODULES=nwdft solvation driver does not include python, however the test pyqa3 is executed and, since the NWChem executable lacks the python modules, it fails

in run_test.sh I am suggesting the following header

#!/bin/bash
set -e

If this does not work, I am not sure where to look

Looking at https://github.com/nwchemgit/nwchem/blob/master/QA/doafewqmtests.mpi I suspect the problem is that this script will exit with a non-zero exit code if and only if the very last test fails.
Adding set -e in that script should fix the issue.

Yes, I believe you are on the right track

P.S. I think the set -e behavior is not what one wants for a typical test suite though, where one would like to see the results of all tests (not just up to the first test that fails).
I.e. ideally one could add a line to the end of the script that makes sure to return a nonzero exit code unless all tests passed.

Good idea. We could have a patch for this ... could you generate it?

The NWChem build corresponding to NWCHEM_MODULES=nwdft solvation driver does not include python, however the test pyqa3 is executed and, since the NWChem executable lacks the python modules, it fails

Ah sorry, now I get it. But so is the solution to build without python support or should we try to fix the source of the problem (some missing python modules? where/how would they need to be installed?)
In any case, I'm also fine with disabling python support; it will would then reduce the number of builds down to one per platform I guess.

I.e. ideally one could add a line to the end of the script that makes sure to return a nonzero exit code unless all tests passed.

Good idea. We could have a patch for this ... could you generate it?

Hehe, I was hoping you would know the command (grepping some logs?) ;-)
The minimalist thing to do would be to just modify the run_tests.sh to something like
./doafewqmtests.mpi 2 | tee tests.log
grep -v "NWChem execution failed"

Let me know what you prefer

The NWChem build corresponding to NWCHEM_MODULES=nwdft solvation driver does not include python, however the test pyqa3 is executed and, since the NWChem executable lacks the python modules, it fails

Ah sorry, now I get it. But so is the solution to build without python support or should we try to fix the source of the problem (some missing python modules? where/how would they need to be installed?)

I guess I have not being clear enough.
The NWChem binary with python in the NWCHEM_MODULES list (e.g. NWCHEM_MODULES=nwdft solvation driver python  or NWCHEM_MODULES=all python) would get a green light on the pyqa3 test.
The whole point of

excluding python from NWCHEM_MODULES and
run the pyqa3 test

is to test if the conda recipe is able to detect test failures

Hehe, ok I think this time I finally did get it ;-) My confusion came from assuming that the test build with the failure you linked above was actually the latest build of the feedstock (and that I overlooked the test failure).
I see now that you just wanted to make sure that a green check mark actually ensures that all tests passed.
Let me make a quick PR.

Yes, the grep change you pushed in the last commit seems a good solution to me.
By the way, what does the ! character do in the last line of the script?

By the way, what does the ! character do in the last line of the script?

It should just negate the truth value of the exit code of the command


pkg_resources.get_distribution('tensorflow') isn't strict

On commit c0fa11a3a730dcf987040ea131461ccd74e7da7b setup.py changes from checking tensorflow version number by checking
tensorflow.__version__
which is 1.12.0-rc1
to checking
pkg_resources.get_distribution('tensorflow').version
which is 1.12.0rc1
which fails StrictVersion regular expression check.
Execute the following in Google's colab notebook to see this problem:
#tensorflow.__version__ works
from distutils.version import StrictVersion
import tensorflow, re
print( tensorflow.__version__ )
print( StrictVersion(re.sub(r'-rc\d+$', '', tensorflow.__version__) ) )

#pkg_resources.get_distribution('tensorflow').version blows up
import pkg_resources
tf_pkg_name = 'tensorflow'
tf_pkg = pkg_resources.get_distribution(tf_pkg_name)
print( tf_pkg.version )
print( StrictVersion(re.sub(r'-rc\d+$', '', tf_pkg.version)) )

This change makes it so I can no longer install baseline in a Google colab notebook.

Ok, I found a solution.  If the dash in the sub is followed by a question mark, then the sub can still strip off the rc# on the end even with the dash missing.

Here is a patch expressing the suggested edit.  I haven't tested it yet.  Finagling things into colab is tricky.  But making the dash optional in the rc suffix stripper doesn't look like it could cause any harm.
strictversion-fix.txt

confirmed, should be fixed now (google colab notebooks also have a problem of missing mpi, I am working on separating MPI from dependencies)


Check if Any Entry is updated or not

is there a way to check when an entry has been updated recently?  suppose we have 20 entries in the content stack and want to know any of these is updated recently so that we can only fetch the recently updated entries instead of all

Hi @aj-pilot, to determine the timing of the last entry modification, you can refer to the updated_at key in the response api is returning to you. If you require further assistance, please feel free to reach out to our customer support team.

Closing the issue as there was no further communication
cc: @abhinav-from-contentstack @shafeeqd959 @netrajpatel


Duplicate interface definition for class 'RCTBridge'

I'm getting the following error when trying to build to IOS, everything works great on Android.
Using React Native 0.41.2, PDF View ^0.3.2.
Duplicate interface definition for class 'RCTBridge'
In file included from /node_modules/react-native-pdf-view/RNPDFView/RNPDFViewManager.m:11:
In file included from /node_modules/react-native-pdf-view/RNPDFView/RNPDFViewManager.h:9:
In file included from ../react-native/React/Views/RCTViewManager.h:15: /react-native/React/Base/RCTEventDispatcher.h:12:9:
In file included from /Library/Developer/Xcode/DerivedData/App-ckzthjkwdguomaavfzoksbbpuojh/Build/Products/Debug-iphoneos/include/React/RCTEventDispatcher.h:12:
/react-native/React/Base/RCTBridge.h:65:12: Previous definition is here

There are additional errors but they all appear to stem from (or be similar to) this one, so I've only included this one. A quick look around brings up this, which might be useful?

I've tried pulling the latest codebase and everything compiles fine. A version bump (#51) would be useful!

Yep, +1 to this, had the same issue

+1


IE10,11,Edge won't pass the formdata besides "file"

Maybe this is the only case for me, but I haven't find any related issues referring to this.
I want to pass some authentication data together with file in the data block, as this:
file.upload = Upload.upload({
          url: '/api/file',
          data: {
            'file': file,
            'token': 'thetoken'
          }
        })

This works fine in Chrome and Safari, but in IE the token will not be passed in the request. I checked the request body, only file is there, the token is dropped.
I did some debugging with the upload function, and saw the parameter token was added to the formdata by formdata.append(), but in the final request it was lost. This happens in IE10, IE11 and Edge.

How do you know it is lost in the final request?
Add some screenshots or create a jsfiddle.

Sorry @danialfarid , my mistake.  I checked the body panel in IE developer tool, and there was only "form-data:file", no token and the API returned error code so I thought this is the root cause.
But when I was about to try a new way I realized the URL of the API was wrong. So I changed it to the correct one and the error gone.
Thanks for your help!


Admin homepage information screen

Complete the homepage information screen so it gives a system overview and relevant information to the developer.
A placeholder exists at the moment, complete it so it shows real information and add any other relevant information.

Some work done on this in ec84d1fa73c11bc7bd594ee021bbe8d0e01fb2cd, needs a proper design before this can be completed though.


Raw bit-preserving conversion from signed/unsigned to unsigned/signed

I'm implementing some bit manipulation algorithms on top of PrimInt and there are some situations in which I need to get an unsigned representation of the Integer type to operate on the bits directly using wrap around unsigned arithmetic.
Is there a way to:

obtain the unsigned integer type that has the same size as the current integer type
cast the current type to its associated unsigned integer type preserving the bits (i.e. transmute)?

The reciprocal operations (going from unsigned to signed) are also required.

A simple cast like value_i64 as u64 should do what you expect, preserving bits.  I'm curious though, what operations are you trying that require conversion?
There was IntSliceExt, but this was never stabilized.
I could imagine adding Signed and Unsigned associated types to PrimInt, along with as_signed and as_unsigned methods.  (That's sort of a breaking change to extend a trait, but PrimInt isn't really expected to have external impls.)

Maybe I expressed myself wrong. The use case I have is when writing a generic function that takes a PrimInt and I want to obtain a Signed/Unsigned int from it with the same size. When dealing with concrete primitive integers as you mention this is trivial.

I'm asking for the motivation.  Why does that generic function want to convert signedness?  Do you have an example where this is clearly necessary and correct?

Yes, a generic bit reverse algorithm in my PR uses them to simplify some
things.
On Friday, December 18, 2015, Josh Stone<EMAIL_ADDRESS>wrote:

I'm asking for the motivation. Why does that generic function want to
convert signedness? Do you have an example where this is clearly necessary
and correct?
—
Reply to this email directly or view it on GitHub
https://github.com/rust-num/num/issues/141#issuecomment-165860683.

Basically if you implement some of these algorithms in an impl with concrete types then yes, you don't need these.
Otherwise (implementing them in a free generic function or in the PrimInt trait) then you need something more than what the current PrimInt provides.
The generic function might want to convert signedness because, e.g., an algorithm might be easy/fast for unsigned integers due to wrap around arithmetic but hard for signed integers. Converting whatever PrimInt you have to unsigned, and then back to the original type in a lossless way is easy.
The opposite is also true, an algorithm might be fast for signed integers due to arithmetic shift (instead of logical shift).
In both cases, the algorithm works for all integers independently of their type/size as long as the proper bit representation can be used.

Note that Rust is not like C/C++, where unsigned overflow is allowed and wraps, but signed overflow is undefined behavior.  In Rust, overflow is always considered a program error, although this is usually only checked in debug builds.  When left unchecked, Rust wraps normally for both signed and unsigned integers.  See RFC560.
The point about arithmetic shifting is indeed useful, if you're taking advantage of sign extension in a signed type, or you want to avoid sign extension by using an unsigned type.
In general I'd advise against casting signedness unless you're absolutely sure it's necessary.  But these conversions are trivial to add, and should be no maintenance burden, so... OK.
Just for comparison, C++11 <type_traits> has make_signed and make_unsigned.

@cuviper actually Rust (unlike C++ but like C) define what program should do on over-/underflow. It is also considered "safe", debug asserts are only helpful warning for development purpose.
But I am also against this PR as I see no point in that. Is there any real world problem where such behaviour would be desirable?

@cuviper actually Rust (unlike C++ but like C)

C++ defines it as wrap around for unsigned integers and undefined behavior for signed integers. What does C define? (I thought C++ just deferred here to the C standard).

But I am also against this PR as I see no point in that. Is there any real world problem where such behaviour [sic] would be desirable?

The two most basic bit manipulation algorithms are logical and arithmetic shift. To perform a logical shift one needs an unsigned representation of an integer. To perform an arithmetic shift one needs a signed representation of an integer.  Any other non trivial algorithm (e.g. convert an unsigned to signed, and clamp to max/zero/whatever if the unsigned value is too large) needs a way to know for a given type, the signed/unsigned types of the same size.
From the point of view of an user that tried to extend PrimInt non-intrusively but that failed miserably, I had two options:

I could either write a new trait, and implement an algorithm 8 times (e.g. using a macro), and then constrain my functions on PrimInt + my new trait (PrimIntPlus).

Or I could write the algorithm in a generic function constrained on PrimInt + another new trait PrimIntAssociatedTypes. Either way, I needed a new trait and maybe a macro.

I found that nuts, and decided to modify PrimInt instead. Ideally, users willing to extend PrimInt with their own algorithms should just need to write them in a generic function constrained on PrimInt. I see anything else as a failure of PrimInt.
I also think that this is a prerequisite if we want to move some algorithms from the current PrimInt implementation from the macro to the trait. We don't need to do this, and arguably that can be considered masochism. Still, I think that we should at least strive to do so and try to see if the language or the rustc implementation could be improved to allow us to do so. If one cannot abstract over primitive integers easily from within a trait, how are users supposed to use Rust traits to abstract over more complicated things?  I don't think we will ever get rid of the implementation macro, but those associated types are a small step in that direction.

C and C++ are the same with unsigned overflow wrapping but undefined behavior for signed overflow.  Rust's overflow is defined and safe for both, but still considered an error -- RFC560 is clear that implementations must check this when debug_assert! is enabled, and still may at other times.
Anyway, this just means overflow doesn't matter here, but arithmetic/logical shr still has a meaningful difference.  Maybe we should just add explicit arithmetic_shr and logical_shr functions, preserving signedness in the interface but doing whatever conversion is needed in implementation.  Those would fit conceptually well next to the existing rotate_left and rotate_right.  @hauleth?
I'm not too worried that PrimInt is itself macro-implemented, but its very purpose to let others write generic code on primitives, I agree.  Since @hauleth and I seem to agree that general signedness-conversion is dubious, let's identify what particular gaps we should fill, like shr above.

:+1: for arithmetic_shr and logical_shr and shift left equivalents. This would be even better option than << as it represents the idea of the operator. So yes, big + from me for that!

I would love to have shar and shal next to shll and shlr. The operators <<
and >> are just too confusing in generic code when one doesn't know if the
type is signed or unsigned.
I think adding these is independent of whether the associated types
Signed/Unsigned make sense.
But it is worth discussing in detail how to add them since Shll/Shlr are
independent traits, so it could make sense to implement Shar/Shal in
separate traits as well, I am not sure.
Maybe we should open a different issue to discuss this more precisely?
On Wednesday, December 23, 2015, Łukasz Niemier<EMAIL_ADDRESS>wrote:

[image: :+1:] for arithmetic_shr and logical_shr and shift left
equivalents. This would be even better option than << as it represents
the idea of the operator. So yes, big + from me for that!
—
Reply to this email directly or view it on GitHub
https://github.com/rust-num/num/issues/141#issuecomment-166770450.

@hauleth, you want left equivalents just for completeness?  AFAIK those are identical.
@gnzlbg I'm not sure these need new shifting traits.  The sign-extending distinction only makes sense for fixed-width integers.  And if you still want to make the case for Signed/Unsigned associated types, please give an example of code that needs it.  The code you wrote in #142 reverse_bit_groups would be just fine signed if you had logical_shr, I think.  What other operation would require a particular signedness?

It seems you've met your own need in your bitwise crate.
https://github.com/gnzlbg/bitwise


Zulrah Helper does not allow me to use Hotkeys set.

Hello,
I've been trying to setup the plugin to my settings. I have it setup as Phase 1 F1 - Phase 2 - F2       Phase 3 - F3 with next phase set to F4, nothing overlapping but none of them would change the phases. I then switched keys to 1,2,3,4 Respectively and the same issue. I did not have any other plugins that could interfere (key remapping, etc.) to my knowledge. Had some assistance in runelite discord but we could not figure it out.
Thanks.

Hiya! HotKeys will only work once inside the Zulrah instance.
This was a change because most people will remap single letters (and in your case F1 keys) and will override it when doing normal in-game things.

Ahh ok, apologies thought it was a bug on my end or something. Thanks for the help, great plugin. Cheers!


Running Mist with base as EMR spark Cluster

I am running mist service on EMR providing following details in default.conf as
mist {
  context-defaults.spark-conf = {
    spark.master = "yarn-client"
    spark.submit.deployMode = "client"
  }

  workers.runner = "manual"
}

It is giving me error as :
"Worker ml initialization timeout: not being responsive for 2 minutes"
When I have changed to workers.runner = "local", it ran but as per my knowledge, spawning workers on the host only.
Why above error occurred and what additional configurations I have to provide to resolve it in a way that Mist uses existing cluster's worker only?

If you want to spawn workers on yarn, you can try spark.submit.deployMode=cluster.
Manual mode can be used in case when you need to spawn workers in some unusual way and it requires to specify worker.runners.cmd -  shell command how to launch worker

Would spark.master be "yarn" or "yarn-client" in case of EMR?

What would ber spark.master in case of EMR 5.6.0, "yarn-cluster" or "cluster"

According to spark docs, it should be yarn

i had following configuration :
mist {
  context-defaults.spark-conf = {
    spark.master = "yarn"
    spark.submit.deployMode = "cluster"
  }

  workers.runner = "local"
}

it is still giving error as
Worker ml initialization timeout: not being responsive for 2 minutes
Kindly help,

It ran when I supplied client.But I am still unsure as to how to check it ran on existing EMR cluster.Kindly guide regarding it.

Did you try to launch raw spark application in cluster mode? (guide)
It can help to find out where is the problem(emr configuration/env variables or mist)

@arshanvit did you find solution for that?

Hi @dos65, sorry for replying late.Yes, it feels that the application was getting deployed in existing EMR cluster as I checked in history server log of EMR cluster, the Applicationid being generated here in the job can be found in history server log of Spark.


Create governance.md

Issue from WG meeting on Feb 8 2022: document our process for decision making and next steps.

@nishakm - do you wanna take a stab at this? I don't think it needs to be super heavyweight

Will be resolved by #11.

@nishakm are we good to close this one?


regexp: Repeated capture groups only capturing final captured match.

What version of Go are you using (go version)?

$ go version
go version go1.15.2 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/danielwedul/Library/Caches/go-build"
GOENV="/Users/danielwedul/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/danielwedul/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/danielwedul/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.15.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.15.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/px/yz_xp7wj195g7n9k2h4dxp8w0000gp/T/go-build197526322=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
https://play.golang.org/p/qR9DDyTkvf0
What did you expect to see?

Regex: [^(A+B+)+$]
input: [ABAABBAAABBB].
FindStringSubmatch - Expected: [ABAABBAAABBB AB AABB AAABBB]
FindStringSubmatch -   Actual: [ABAABBAAABBB AB AABB AAABBB]
FindStringSubmatchIndex - Expected: [0 12 0 2 2 6 6 12]
FindStringSubmatchIndex -   Actual: [0 12 0 2 2 6 6 12]
FindAllStringSubmatch - Expected: [[ABAABBAAABBB AB] [ABAABBAAABBB AABB] [ABAABBAAABBB AAABBB]]
FindAllStringSubmatch -   Actual: [[ABAABBAAABBB AB] [ABAABBAAABBB AABB] [ABAABBAAABBB AAABBB]]
FindAllStringSubmatchIndex - Expected: [[0 12 0 2] [0 12 2 6] [0 12 6 12]]
FindAllStringSubmatchIndex -   Actual: [[0 12 0 2] [0 12 2 6] [0 12 6 12]]

What did you see instead?

Regex: [^(A+B+)+$]
input: [ABAABBAAABBB].
FindStringSubmatch - Expected: [ABAABBAAABBB AB AABB AAABBB]
FindStringSubmatch -   Actual: [ABAABBAAABBB AAABBB]
FindStringSubmatchIndex - Expected: [0 12 0 2 2 6 6 12]
FindStringSubmatchIndex -   Actual: [0 12 6 12]
FindAllStringSubmatch - Expected: [[ABAABBAAABBB AB] [ABAABBAAABBB AABB] [ABAABBAAABBB AAABBB]]
FindAllStringSubmatch -   Actual: [[ABAABBAAABBB AAABBB]]
FindAllStringSubmatchIndex - Expected: [[0 12 0 2] [0 12 2 6] [0 12 6 12]]
FindAllStringSubmatchIndex -   Actual: [[0 12 6 12]]

I'm not really sure what to say except that that isn't how it works.  The number of subexpressions of a regexp is fixed by the definition of the regexp.  It does not depend on the input string.

Sorry. I could have sworn that that was how it worked in some other languages. I just tested it in Perl, though, and I am mistaken.


Try out OnlyOffice

https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx

Unfortunately, looks like there are not arm64 images.


Any chance code llama can be added to the leaderboard?

https://about.fb.com/news/2023/08/code-llama-ai-for-coding/

Sorry didn't quite get what you meant, added to which leaderboard?


Static method naming

With the new static based functions. I was wondering if there were alternatives to the groupBy name. Object.groupBy and Map.groupBy sounds a little like it operates on Object or Map as opposed to building them.
Background
The majority of static Object methods operate on an object argument:

getOwnPropertyDescriptor
getOwnPropertyDescriptors
getOwnPropertyNames
getOwnPropertySymbols
hasOwn
preventExtensions
seal
assign
defineProperties
defineProperty
freeze
getPrototypeOf
setPrototypeOf
isExtensible
isFrozen
isSealed
keys
entries
values

The static Object methods that create an object, Object.create and Object.fromEntries, are in the minority but use words that strongly convey that a new value is being created.
Suggestions
Some alternatives we came up with at Bloomberg:

Object.byGrouping
Object.fromGrouping
Object.groupFrom

Thoughts?

I think having the name groupBy is important for recognizability (our own ecosystem precedent and from other languages). I don't think there's a clear pattern for naming factory methods.

The recognisability of the name does sound very valuable. So like {_,Lodash,Ramda}.groupBy, in this situation the namespace should be seen as a general collection of utilities. And having Array.groupBy doesn't scale as nicely to having various different collection types.

How about fromGroups?

@nickmccurdy This method is the opposite of that - your data is not grouped yet, and you want it to be.

I was thinking of it more from the mathematical perspective, where the callback is a functor mapping an ungrouped collection to a grouped collection. Though if the result is too arbitrary, maybe fromGrouping would be more clear.

“fromX” means it’s an X already, and as you said, it’s ungrouped.

@nickmccurdy correct me if I'm wrong, but @ljharb I think what @nickmccurdy is suggesting is that groups is referring to the function that converts from "ungrouped" to "grouped". An expansion of the name could be: getGroupsFromGroups and when you consider the "more clear" version he provided: fromGrouping, this makes even more sense: getGroupsFromGrouping.

Functions are verbs, so that function could be a "grouper" but wouldn't be "groups", a noun - and fromGrouper sounds like it's a fish :-)

I try to avoid putting get in function names as it's usually already obvious. Maybe just groups or grouped could work? Though I'm not sure if they'd have naming collisions.

TC39 reaffirmed consensus today on the existing groupBy name.


Boingy graph: implement Partial Edge Drawing (PED)

PED looks like a good technique for reducing clutter in the boingy graph.
For more information see this PED example

Before:

After:

Highlights


Sparse Tensor Core Ops

Hello,
Does triton support sparse * dense matmul with 2-of-4 sparsity, using sparse tensor cores similar to cuSparseLt and CUTLASS? I have implementations using those libraries and would like to compare to triton if possible.
Thank you,
-Collin

We currently don't

Got it, thank you for the fast response.


Add troubleshooting guide

Currently there is no troubleshotting guide. People might find it hard to follow readme to produce a hello world example.
Known issues are, but not limited to:

containerd currently only support Linux. So in order to build runwasi, either you need to have a linux machien or run it in WSL on Windows
docker buildx is a dependency
make load is broken

How is make load broken?

containerd does run on Windows, however runwasi only supports Linux at the moment because it has to wire up networking and rootfs mounts.

How is make load broken?

I think @Mossaka is referring to the fact that, when trying to run it on my machine, it didn't replace the export variable CONTAINERD_NAMESPACE with default even though this line exists:
CONTAINERD_NAMESPACE ?= default

Considering ?= only sets the value if it isn't already set, I'm guessing export CONTAINERD_NAMESPACE sets it to empty making ?= not work.

Hmmm... perhaps? I know I use this all the time.
But yeah, export should be moved... or even removed.

If we want to keep the export, we could just do:
export CONTAINERD_NAMESPACE ?= default

I've tested it and it works, @cpuguy83.


Document how to remote debug sagan app

It took me a while to figure out this command to remote debug sagan app.
./gradlew :sagan-site:run --debug-jvm
Or add "-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005" to applicationDefaultJvmArgs in build.gradle

These are the ones didn’t work. (breakpoints are skipped) :<

GRADLE_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005” ./gradlew :sagan-site:run
JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005” ./gradlew :sagan-site:run
Starting SiteMain from IDE works for dynamic(java) part, but doesn’t serve static contents

It would be nice to be documented this kind of information probably on developer section in wiki.
Thanks,

Done.
See https://github.com/spring-io/sagan/wiki, right menu.


Publish pages created by the create demo site management command

Purpose
When using the create_demo_site management commands, page created are not published by default.
Proposal
Publish all the things!

Fixed in https://github.com/openfun/richie/commit/4c0dcc3a69fdd065959676991431b3e883c11ecc#diff-3880426875654013414391c1332a9491


help me?

u can help you help me put this bot on heroku ?

Hey, we'll be posting a wiki page soon that explains how to deploy the bot to Heroku.

Furthermore, I will close this pull request because I don't see anything that contributes to the bot.
Nevertheless, thank you for pointing this out.


[Encoders] SIMD widen for ASCII to UTF-32 scenario

This is another API that would benefit from https://github.com/dotnet/coreclr/issues/6906#issuecomment-307164495

cc @GrabYourPitchforks


Vulkan: LightmapGI banding visible on baked lighting due to 8 bpc lossless compression being used by default (even with denoising enabled)

Godot version
4.0.dev (2fc31fdfc)
System information
Fedora 34, GeForce GTX 1080 (NVIDIA 470.57.02)
Issue description
A significant amount of banding is visible on direct baked lighting (even with denoising enabled). This applies to lights whose bake mode is set to Static rather than the default Dynamic, and becomes more noticeable when you disable bounces entirely. I suspect there's a precision issue somewhere in the compute shader used to bake the lightmap.
Edit: This is caused by lightmaps using Lossless compression by default instead of VRAM Compressed (or VRAM Uncompressed). Standard lossless and lossy compression does not support HDR – only VRAM compression, Basis Universal or the uncompressed storage modes do.
Enabling denoising does not improve the situation, since denoising isn't meant to combat banding anyway. Enabling the screen-space debanding filter doesn't resolve this issue either, as the banding is part of the lightmap texture itself.
GLES3 does feature bicubic lightmap sampling which can hide banding a little. Nonetheless, there's still a lot of banding in the lightmap texture that wouldn't be hidden by bicubic sampling once it's implemented in the Vulkan renderer.
Steps to reproduce
Real-time light in Vulkan (good)

Fully baked light in Vulkan (bad)

GLES3 in 3.x (good)

Minimal reproduction project

master: test_light_attenuation_lightmap_master.zip
3.x (for comparison, baked with https://github.com/godotengine/godot/pull/52918 enabled): test_light_attenuation_lightmap_3.x.zip

I think this is caused by an incorrect setting for the compress mode of the lightmap texture. For the reproduction project is the lightmap data stored in 'test.lmbake'. This data contains a texture test.exr which compress mode is set to Lossless (PNG) which is a RGB8 format. This compress mode can be seen in the Import tab of the scene, when the test.exr tecture is selected. The default setting for the compress mode is Video RAM which is a RGBE9995 format.
The first setting does not have enough precision causing the banding effect. The latter is much better and the banding is reduced.

I did find another effect which is that the color between real-time light and bake-light differs. This can also be seen in the reproduction project. Maybe we should open a separate issue for that. Any way I will investigate those color differences.

See https://github.com/godotengine/godot/issues/53388 for the different color output between baked and real-time lights.

I propose to close this issue as it is caused by an incorrect setting (see comment).
In case this explanation is not considered a solution, I like to understand what needs to be done further for this issue.

I can confirm that changing the compression mode to VRAM Compressed, VRAM Uncompressed or Basis Universal resolves the issue:

However, we should make sure that newly created lightmap textures automatically use the right compression setting (VRAM Compressed setting in this case).

Needs updated MRP, the attached one is completely black in alpha 9 and spams errors.

this was fixed by https://github.com/godotengine/godot/pull/73136

For future reference, the default will need to change from VRAM Uncompressed to VRAM compressed once we get betsy merged


Dream.static is returning incorrect headers for non-exists file

Given a static route like this one
Dream.get("/**") @@ Dream.static("public")

Try to access random route would have these behavior:

Chrome shows ERR_INVALID_RESPONSE
Safari downloads an empty file automatically
dream.log shows 404
curl -v -o - http://localhost:5000/not-exists

curl -v -o - http://localhost:5000/dasdabbbbsd
*   Trying ::1...
* TCP_NODELAY set
* Connection failed
* connect to ::1 port 5000 failed: Connection refused
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 5000 (#0)
> GET /dasdabbbbsd HTTP/1.1
> Host: localhost:5000
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Content-Type: application/octet-stream
< Set-Cookie: dream.session=0JDfhSEyb-zsmGQA1cFJae_G2; Max-Age=1209599; Path=/; HttpOnly; SameSite=Strict
< Content-Length: 0
<
* Connection #0 to host localhost left intact

@aantron said on Discord that those headers shouldn't be there.

Content-Type is probably what trigger safari to download it as file

Should be fixed by https://github.com/aantron/dream/commit/809835dcfe655bbe2fd811acae4ddecd6f1800b4. The issue was that when the response is not one of the 2xx responses that carries content, Dream.static should not set the Content-Type based on the file extension, since file data is not being sent.

@aantron I've tested 809835d and it works perfectly. On safari it shows a blank page and I'm not sure if that's a normal behavior of safari because I can't think of any website without a 404 template

Thanks!
Can you try comparing on Safari to 404 page from a Dream app without a 404 template, but outside /public? For example, compare with your own web app's general routes, or any of the examples, such as 3-router.

@aantron it shows 404 as well. But I want to test non-dream behavior

@aantron it shows blank page as well. But I want to test non-dream behavior

Understood. It was just a partial comparison you could do cheaply (since I don't have Safari) — thanks!
It's actually a bit disappointing that Safari has this behavior. Part of the reason I used blank replies by default is that Chrome's stand-in pages are localized by Chrome (at least on my system with my versions). So not using an error template actually helps with localization, while providing an English template would positively harm it.
Safari's blank page behavior undermines this pretty completely.

while providing an English template would positively harm it.

That is, if Dream tried to provide its own default cookie-cutter templates, without knowing what the localization needs of each app are (if any).

@aantron oh. I don't suggest Dream would provide default error template.
Is there a way for me to provide a catch all hook for error pages?

Is there a way for me to provide a catch all hook for error pages?

Absolutely, that's the intended way to do it, and Dream will even capture lower-level errors (so, all errors) and forward them to you hook. See the error example, also in the playground, and its API docs:

You can easily customize all error responses generated by Dream, whether from your application, or at lower levels in the HTTP stack.


IFunctionBindingsFeature is internal and pevent unit testing in middleware

Description
I'm currently writing a authentication middleware. When it identifies that the user bearer token is not valid it sets the response data to return a 401 response.
`    public async Task Invoke(FunctionContext context, FunctionExecutionDelegate next)
{
HttpRequestData? request = await context.GetHttpRequestDataAsync();
    if (request is null)
    {
        await next(context);

        return;
    }

    try
    {
        var authService = context.InstanceServices.GetRequiredService<ICustomAuthService>();

        AuthorizedContext authorizedContext = await authService.Authorize(request);

        context.Items.Add("AuthorizedContext", authorizedContext);

        await next(context);
    }
    catch (HttpRequestException exception)
    {
        LogErrorMessage(request, exception);
        context.GetInvocationResult().Value = request.CreateErrorResponse(exception);
    }
    catch (Exception exception)
    {
        LogErrorMessage(request, exception);
        context.GetInvocationResult().Value = request.CreateErrorResponse(exception);
    }

`
The function GetInvocationResult on context is a static function that calls another static function GetBindings. GetBindings executes this line of code: context.Features.GetRequired<IFunctionBindingsFeature>();. GetRequired is also a static function that calls features.Get<T>
I would need to to create unit tests but I cannot mock static functions. I'd have to go mocking features.Get<IFunctionBindingsFeature> but it is impossible because IFunctionBindingsFeature is an internal interface.
I've been wondering if it is possible to open this up to allow unit testing possible. I want to be able to add unit tests when a user cannot be authenticated and check that the middleware returns the correct error.

@kshyju  @brettsam @fabiocav
Any update on this? Seems like a simple fix to make this public.

Any updates? We've ended up with the same issue while using Middleware feature.

bump. I need it too.

While awaiting a solution, a straightforward workaround involves using a wrapper around the FunctionContext itself, which can later be mocked during unit testing. Alternatively, you could implement a factory that accepts a FunctionContext as a parameter and returns a FunctionContextWrapper object. This latter approach eliminates the need to pass the FunctionContext to each wrapper method individually.
public interface IFunctionContextWrapper
{
    object? GetInvocationResult(FunctionContext context);
    void SetInvocationResult<T>(FunctionContext context, T newValue);
    Task<HttpRequestData?> GetHttpRequestDataAsync(FunctionContext context);
    HttpResponseData? GetHttpResponseData(FunctionContext context);
    // we needed above methods, you may need other depending on your case
}

public class FunctionContextWrapper : IFunctionContextWrapper
{
    public object? GetInvocationResult(FunctionContext context)
    {
        return context.GetInvocationResult().Value;
    }

    public void SetInvocationResult<T>(FunctionContext context, T newValue)
    {
         context.GetInvocationResult().Value = newValue;
    }

    public async Task<HttpRequestData?> GetHttpRequestDataAsync(FunctionContext context)
    {
        return await context.GetHttpRequestDataAsync();
    }

    public HttpResponseData? GetHttpResponseData(FunctionContext context)
    {
        return context.GetHttpResponseData();
    }
}


fix(): skips initialization of git if directory is already under version control

avoids nested git repos, which are probably not what we wanted to have
see also: http://boxysystems.com/index.php/nested-git-repo-gotchas/

Many thanks for the feedback!
Let me do a second try...

Looks good. I'll submit it when I have time to rebase or if you want to rebase quickly I'll merge. Thanks!

Done. Squashed and rebased!


failure to build with Rust 1.16.0

$ git show
commit 70b78abf071a2849e20861df99bbd6b1e889ef71 (HEAD, tag: 0.4.8)
Merge: b0957ea 782d4f7
Author: Ashley Mannix<EMAIL_ADDRESS>Date:   Mon Jul 29 07:03:20 2019 +1000

    Merge pull request #345 from KodrAus/cargo/0.4.8

    prepare for 0.4.8 release
$ cargo +1.16.0 build
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling cfg-if v0.1.10
   Compiling log v0.4.8 (file:///Users/cardoe/work/log)
error: expected one of `,` or `=`, found `::`
   --> /Users/cardoe/.cargo/registry/src/github.com-1ecc6299db9ec823/cfg-if-0.1.10/src/lib.rs:143:19
    |
143 |     #[allow(clippy::assertions_on_constants)]
    |                   ^^

error: expected one of `=` or `]`, found `::`
   --> /Users/cardoe/.cargo/registry/src/github.com-1ecc6299db9ec823/cfg-if-0.1.10/src/lib.rs:143:19
    |
143 |     #[allow(clippy::assertions_on_constants)]
    |                   ^^

error: aborting due to previous error

error: Could not compile `cfg-if`.
Build failed, waiting for other jobs to finish...
error: build failed

A bit confused by this but when I bisect cfg-if it shows that https://github.com/alexcrichton/cfg-if/commit/3e311415b29781b886a6b6611206305cec9527a7 breaks support with 1.16.0.

However it seems more plausible that the break is caused by https://github.com/alexcrichton/cfg-if/commit/75e817fa2cdd9d3cb2c558fa91ba3dacdbfa8d73

As you've noted, the error is caused by the cfg-if crate. If you need to build against 1.16, you can downgrade that package to a working version.

@sfackler I think you closed this prematurely. https://github.com/alexcrichton/cfg-if is a dependency of this crate. I don't use Rust 1.16.0 but I am a maintainer of https://github.com/cardoe/stderrlog-rs which this crate advertises. Since this crate says it strictly supports Rust 1.16.0 and newer, I tests all commits against my crate with Rust 1.16.0. Unfortunately due to changes in https://github.com/alexcrichton/cfg-if there is no version of this crate that builds anymore which works with Rust 1.16.0.
How am I suppose to fix a dependency of log?

The console output was me attempting to build this crate (log), @sfackler and it failing.

cargo update -p cfg-if --precise 0.1.9


s3: Use rest.URLEscape rather than url.QueryEscape.

The X-Amz-Copy-Source header should be a path. url.QueryEscape escapes spaces with a plus sign (+) while rest.URLEscape (which mimics the url.PathEscape available from go 1.8) uses %20
See: https://play.golang.org/p/xWAAVXu8DKK
This works around an issue when copying objects with spaces in their key on DigitalOcean Spaces.

That looks great thank you!
I've tested that change (by running the rclone integration tests) against

digital ocean
s3
ceph
wasabi

And it all looks good.
Digital Ocean integration (short and long) are now passing which is great :-)
I did get a few of these while running the integration tests which are from the go http layer

2017/12/23 11:13:03 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n
408 Request Time-out
\nYour browser didn't send a complete request in time.\n\n"; err=<nil>
2017/12/23 11:13:03 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n
408 Request Time-out
\nYour browser didn't send a complete request in time.\n\n"; err=<nil>
2017/12/23 11:13:03 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n
408 Request Time-out
\nYour browser didn't send a complete request in time.\n\n"; err=<nil>

These will cause bug reports for rclone (eg #1583 for hubic) but I don't think that is something I can fix in rclone since it is the go http layer making the report.  There are quite a few issues about this on the go bug tracker, but the conclusion of most of them seems to be that the server is in error.  I think the server should just close the idle connection without sending anything but I don't know which RFC that would be in!
Thank you very much for your help.
BTW if you want to run the long integration tests
cd fs
go test -v -remote do:

(or whatever you called your digital ocean spaces remote).


port: app insights connection string (#3543)

fix: app insights constructor

port: connectionString or instrumentationKey for app insights

Pull Request Test Coverage Report for Build 734314929

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.003%) to 84.955%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

Totals

Change from base Build 727121721:
-0.003%

Covered Lines:
18903

Relevant Lines:
21191

💛  - Coveralls


[Bug]: Unique constraint failed on the fields: (username)

Package
@lucia-auth/sveltekit
Package version
0.3.0
Describe the bug
If I try to create a new account with an existing name, an error will be thrown below the form:
Unknown error occurred
System info
MacOS Ventura, Firefox, Node18, Vite 4.0.0
For Vite4 i had to change the invalid() function to fail()
Reproduction
Create an account, log out, try to create the same account again.
Relevant log output
PrismaClientKnownRequestError:
Invalid `prisma.user.create()` invocation:

Unique constraint failed on the fields: (`username`)
    at RequestHandler.handleRequestError (/Users/xxx/Code/SK-Auth-Variants/LuciaTest/node_modules/.pnpm/@prisma+client@4.7.1_prisma@4.7.1/node_modules/@prisma/client/runtime/index.js:34869:13)
    at RequestHandler.handleAndLogRequestError (/Users/xxx/Code/SK-Auth-Variants/LuciaTest/node_modules/.pnpm/@prisma+client@4.7.1_prisma@4.7.1/node_modules/@prisma/client/runtime/index.js:34841:12)
    at RequestHandler.request (/Users/xxx/Code/SK-Auth-Variants/LuciaTest/node_modules/.pnpm/@prisma+client@4.7.1_prisma@4.7.1/node_modules/@prisma/client/runtime/index.js:34836:12)
    at async PrismaClient._request (/Users/xxx/Code/SK-Auth-Variants/LuciaTest/node_modules/.pnpm/@prisma+client@4.7.1_prisma@4.7.1/node_modules/@prisma/client/runtime/index.js:35926:16)
    at async Object.setUser (file:///Users/xxx/Code/SK-Auth-Variants/LuciaTest/node_modules/.pnpm/@lucia-auth+adapter-prisma@0.1.4_lucia-auth@0.3.0/node_modules/@lucia-auth/adapter-prisma/index.js:94:41)
    at async Auth.createUser (/node_modules/.pnpm/lucia-auth@0.3.0/node_modules/lucia-auth/auth/index.js:132:26)
    at async default (/src/routes/signup/+page.server.ts:18:20)
    at async handle_action_json_request (file:///Users/xxx/Code/SK-Auth-Variants/LuciaTest/node_modules/.pnpm/@sveltejs+kit@1.0.0-next.583_svelte@3.54.0+vite@4.0.0/node_modules/@sveltejs/kit/src/runtime/server/page/actions.js:51:16)
    at async resolve (file:///Users/xxx/Code/SK-Auth-Variants/LuciaTest/node_modules/.pnpm/@sveltejs+kit@1.0.0-next.583_svelte@3.54.0+vite@4.0.0/node_modules/@sveltejs/kit/src/runtime/server/index.js:400:17)
    at async Object.eval [as handle] (/node_modules/.pnpm/@lucia-auth+sveltekit@0.4.0_6j2u4yas2ynq6ppmhzjdazjfje/node_modules/@lucia-auth/sveltekit/server/hooks.js:87:16) {
  code: 'P2002',
  clientVersion: '4.7.1',
  meta: { target: [ 'username' ] },
  batchRequestIdx: undefined
}

Additional information
Instead Unknown error occurred i expect this message from the +page.server.ts:
Username already in use

Was able to recreate it. It seems it's prioritizing errors from username over provider_id.

Hey @pilcrowOnPaper, can you solve it?
I tried to understand it, but i think i have to learn a lot before...

Yeah I'm trying to see if I can make Prisma prioritize errors for a column, but the easiest way to handle this is to just catch and read the Prisma error

@KoljaL
Sorry it took a while, updated the examples


feat: Add support for Azure OpenAI Endpoint in OpenAIEmbeddingProvider

Added  support Azure OpenAI Endpoints. to OpenAIEmbeddingProvider to
Updated Embedding model configuration to include Azure-specific parameters.

Closes #1515

Looks great, one small typo and the rest should be good to go!


Local image json

Using local image json to improve image load time.

Coverage decreased (-0.06%) to 94.52% when pulling 451b3b3f5e54f8ef6b44e4d3913add9cea1615f1 on local-images into cf10fe3ef77c37464687500876f336145aaa4193 on master.


[0.4.0] Main workflow page missing Workflow Run Id

In comparison in "old" ui:

it's useful to have run id on the main display as sometimes you just want to take those two and be able to copy/paste them when running tctl commands, or want to paste the workflow id and run id in your code tests.

Thanks @tsurdilo I want to break this UI out in two views, one that optimizes for local debugging and one that is tuned for cloud operations. I'm going to close this issue for the interim, we've decide to remove run ID for the immediate short-term.

Hi @canvanooo

we've decide to remove run ID for the immediate short-term

may I please know why? run id is super important info for users


[ Util ] Add how to generate cifar 10/100 bmp images

Add document explain how to generate cifar 10/100 bmp images
Self evaluation:

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

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

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

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/717-202011061204330.22326993942261-5005e7d77ddb10a47347a9a0890526a171344a1d/report/misspelling_result.txt.


How to use WOW.js with nuxt

I am having issues using a third party library. I have tried to follow the documentation but I am missing something. Using the starter template, I npm installed wow.js. I don't understand what to put in vendor js file.
my nuxt.config.js looks like:
 plugins: [     { src: '~plugins/main.js', ssr: false }   ],   build: {      vendor: ['wowjs'],
my main.js file in the plugin folder reads:
if (process.BROWSER_BUILD) {   require('WOW') }
Any pointers?

Will be trying some options later today, will post results.

@jzucadi Isthere any news?

Sorry, I haven't been able to sort this out yet.

WOW have issues when using as cjs or es6 module, you can try https://github.com/matthieua/WOW/issues/233#issuecomment-173640648

as @shrpne pointed out, the solution is including:
 require('imports?this=>window!js/wow.js');


pure pursuit

Made speed a constant at the top, but it could easily be changed to a parameter. Also, no acceleration limits which leads to pacbot overshooting the target in higher speed cases.


OSError on Apple M2 Chip

Describe the bug
When installing julacall via pip install juliacall and run import juliacall,
I got
OSError: dlopen(/Applications/Julia-1.8.app/Contents/Resources/julia/lib/libjulia.1.8.dylib, 0x000A): tried: '/Applications/Julia-
1.8.app/Contents/Resources/julia/lib/libjulia.1.8.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need
'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Applications/Julia-1.8.app/Contents/Resources/julia/lib/libjulia.1.8.dylib' (no
such file), '/Applications/Julia-1.8.app/Contents/Resources/julia/lib/libjulia.1.8.dylib' (mach-o file, but is an incompatible architecture
(have 'arm64', need 'x86_64'))

My system

OS: Mac2023  with M2 chip
julia version 1.8.5
If an issue with JuliaCall, the output of pip list or conda list and juliapkg.status():

Package
Version

juliacall
0.9.20

juliapkg
0.1.13

numpy
1.26.4

pip
24.0

scipy
1.13.1

semver
3.0.2

setuptools
69.5.1

typing_extensions
4.12.1

wheel
0.43.0

I could run this a couple of months ago, but failed this week
Thank you!

It seems like you have an x86_64 version of Julia installed in /Applications but a arm64 version of Python. Both need to be the same to work in the same process.

Thanks for the reply.
I think I somehow managed to resolve the issue.
The solution was to install rosetta an  the x86 version of Julia.


[release-1.1] fix: Add ClusterRoleBinding for instancetype:view ClusterRole

What this PR does / why we need it:
Manual backport of #11025
This adds a ClusterRolebinding which grants every authorized user read access to VirtualMachineCluster{Instancetype,Preference} CRs.
This allows unprivileged users to make use of
VirtualMachineCluster{Instancetypes,Preferences} by default.
Conflicts:
pkg/virt-operator/resource/generate/rbac/cluster.go
Note:
The conflict is due to a code refactoring in cluster.go that was not
backported.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[x] Design: A design document was considered and is present (link) or not required
[x] PR: The PR description is expressive enough and will help future contributors
[x] Code: Write code that humans can understand and Keep it simple
[x] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[x] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[x] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[x] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[x] Community: Announcement to kubevirt-dev was considered

Release note:

Allow unprivileged users read-only access to VirtualMachineCluster{Instancetypes,Preferences} by default.

/cc @acardace
/cc @fossedihelm

Wait for #11059 to go in first, this might save us the merge conflict

Closed in favor of #11077


Updating import to 1.5.4 in both insiders and stable

This PR fixes #21313

@aasimkhan30 published, please vbump the extension in main branch.


fix: dont skip block context

ref https://github.com/alloy-rs/alloy/pull/523#issuecomment-2103693743
cc @banteg

already made a pr here https://github.com/alloy-rs/alloy/pull/719

sweet, ty


support for Flat OpenDocument (fodt)

Expected Behavior
Gotenberg should support the Flat OpenDocument format with extension fodt.
Current Behavior
Extension fodt isn't supported.
Possible Solution
Since LibreOffice supports it natively, maybe add it to https://github.com/thecodingmachine/gotenberg/blob/master/internal/app/api/office.go ?
Context
The Flat OpenDocument format is nice alternative to the standard zipped OpenDocument format. You can edit it with any editor or edit it with sed and other tools. It's nothing more than a normal OpenDocument file in one flat XML file.

Thanks!


Unable to train a Vision Encoder Decoder Model

ValueError: The batch received was empty, your model won't be able to train on it. Double-check that your training dataset contains keys expected by the model: args,kwargs,label_ids,label.

Hello, please provide a minimial reproducible example


Only calling window.localStorage and window.sessionStorage after safe checks

Fix for #152

Ran tests successfully under service account

:shipit:


v1.7.5 release

Pre-release

[ ] Create a new project for the next release version
[ ] Add build targets for the new release on Docker Hub

All versions:

cilium
operator
docker-plugin

Cilium v1.8 or later:

operator-generic
operator-aws
operator-azure
hubble-relay

[ ] Check that there are no release blockers for the targeted release version
[ ] Ensure that outstanding backport PRs are merged
[ ] Consider building new cilium-runtime images and bumping the base image
versions on this branch
[ ] Move any unresolved issues/PRs from old release project into the newly
created release project
[ ] Push a PR including the changes necessary for the new release:

[ ] Update the VERSION file to represent 1.7.5
[ ] Update helm charts via make -C install/kubernetes
[ ] (If applicable) Update the cilium_version and cilium_tag in
examples/getting-started/Vagrantfile
[ ] Update AUTHORS via make update-authors
[ ] Use Cilium release-notes tool to generate CHANGELOG.md
[ ] Point .github/cilium-actions.yml to the newly created project
[ ] Commit all changes with title Prepare for release v1.7.5

[ ] Merge PR
[ ] Create and push both tags to GitHub (v1.7.5, 1.7.5)
[ ] Wait for docker builds to complete

cilium
operator
docker-plugin

[ ] Create helm charts artifacts in Cilium charts repository using
cilium helm release tool & push to repository
[ ] Run sanity check of Helm install using connectivity-check script.
Suggested approach: Follow the full GKE getting started guide.
[ ] Create a release for the new tag v1.7.5, using the release notes
from above
[ ] Announce the release in #general on Slack (only [@]channel for vX.Y.0)

Post-release

[ ] Prepare post-release changes to master branch using contrib/release/bump-readme.sh
[ ] Update the stable tags for each Cilium image on Docker Hub (if applicable)
[ ] Update external tools and guides to point to the new Cilium version:

[ ] kops
[ ] kubespray

duplicate of https://github.com/cilium/cilium/issues/11911


[Sprint 41 Review Only - Do not merge yet] XD-2358-2359-2360-2549 Kafka source using the Simple Consumer API

[Do not merge - dependency in staging]

Upgrade to Spring Integration Kafka 1.0.0.M3
Replace the Kafka Source with one based on the KafkaMessageDrivenChannelAdapter
Add support for listening to a subset of the original set of partitions ('partitions' module parameter)
Evenly split the listened partitions between module instance and coordinate via Zookeeper
Add support for starting reading from a series of initial offsets ('initialOffsets' parameter)
Pluggable strategy for storing offsets during consumption (supported: in-memory/transient and Redis)

No tests on matter.
Or do existing tests for Kafka source cover this well?

Re: testing - the core components have been tested as part of Spring Integration Kafka. There currently are is KafkaSinkSourceTest that exercises the source. Added https://jira.spring.io/browse/XD-2624 to cover the more comprehensive testing before RELEASE.

That's all.
@mbogoevici , be sure to comment in the PR in the future after adding commits.
Unfortunately GH doesn't notify us, when there is just only commit added...

Ok. Fixed.

squashed, rebased, merged as a3e40c2979a882a017c1394abcd057a73325c0b2


DS2: SotFS - ItemLotParam2_XXX is gone

When I create a new project with "Loose Params" flag enabled, ItemLotParam2_XXX is not extracted.
v1.07

When I try to select a line in an existing project with the extracted params, newParam is null.

In the previous version it still works:
v1.06

If you need more information, just let me know.

Looks like an oversight made the paramdef unfindable, and looseparams are still being shown when not having paramdefs. Likely a unique quirk of DS2's special param loading code.
Working on fixes for both as we speak.

fixed with #370


feat: Expand derive macros under cursor in Expand Macro Recursively

Expands the derive macros under the cursor if it is one a derive attribute, with this the feature should be basically feature complete I believe(except for the whitespace problem ofc)?
Actually this might interact a bit funky with items that have attributes and derives since we don't descend the cursor token into macro invocations first, for obvious reasons. So I expected trying to expand a derive in that case will either just expand the attributes on the item or fail in general.
Closes https://github.com/rust-analyzer/rust-analyzer/issues/4005

(Note that we do not expand built-ins to what rustc usually expands so we get a stub-ish expansion for Clone and the like)


GPS FIelds non editable, solves #225

Issue Reference
This PR addresses the Issue : Fixes #225
Summarize
GPS FIelds are non-editable till we implement some sort of placepicker. More details can be found on #225

When testing, also test /requests/ page and Open in Maps button.

What about limiting to numerical fields

I will add this as a temporary fix

Limiting to numerical field/regex will again cause confusion, we can't expect common people to be aware of co-ordinates. This applies to accuracy as well as there is no standard unit for measuring it.

Seems like I forgot to set them to readOnly. fixed it on #236


Emote text disappears from text box

Using BD with the discord windows app.
When selecting a BD emote from the emote window, the text is added to the text box as it should. However when clicking on the text box to continue writing, any of the emote text that was added by BD from the emote window will then disappear.
Note, it does not clear the whole text box but only BD emote text that was recently added by the emote window.

I can conclude that happens on v0.2.82:1.792


Please support ktlint 1.0.0

ktlint 1.0.0 has been released on the 5th of September and it has some breaking changes regarding conventions. Please add support for it.

I see you are already working on it. Thank you <3

@szedelenyi Yep! Feel free to download a manual zip if 1.0.0 support is critical. I'm working on ironing out the last few features and configuration options 😁

Closing as a dupe of #306 which I'll close once I submit the update to Jetbrains


in modal is not working

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

please do it

Just follow the docs
https://github.com/likashefqet/react-native-image-zoom#usage-with-modals-on-android


Use bundled deps file with function file(url+zip etc.)

Issue Ref: #1198
Description:
When enable   use-bundled-deps in k8s api config for function, kubeless will use the deps file that in bundled file such as requirement.txt(python)(dependent on runtime).
For example
apiVersion: kubeless.io/v1beta1
kind: Function
metadata:
  name: exampledeps
  label:
    function: exampledeps
spec:
  runtime: python3.7
  timeout: "60"
  handler: exampledeps.handler
  function: https://example.com/exampledeps.zip
  function-content-type: url+zip
  #deps: requirements.txt
  use-bundled-deps: "true"

TODOs:

[x] Ready to review
[x] Automated Tests
[ ] Docs

@andresmgot Hi! May you help me to find a place that I can write on?

@andresmgot Hi! May you help me to find a place that I can write on to the doc?

Since at the moment, the feature would only be available doing an "advanced deployment" I would add some docs here: https://github.com/kubeless/kubeless/blob/master/docs/advanced-function-deployment.md There, you can add that you can omit the Deps field and modify the content type to achieve what you want.

Thank @SaigyoujiYuyuko233! Let me know what you think about my suggestion.

Thanks for suggestion! I will fix that later :)

@andresmgot Ready for review! Thanks! :)


Error: unknown CSR `mclicbase'

I'm tring to use iverilog to simulate opene902 core, everything seems to be ok but the assembler return an error:
Error: unknown CSR `mclicbase'

it seems that the read/write operation of mclicbase CSR register is not allowed for this assembler.
my riscv toolchain is the official riscv64-unknown-elf-gcc, version number is 8.1.0.

I have tried use the toolchain with version 10.2.0, but it also return the similar error information.

Solved this issue by using the  Xuantie-900-gcc-elf-newlib-x86_64-V2.6.1 published by t-head.


Since 0.59.0, the "brackets" block style does not save

I prefer the [brackets] [] block style, but since 0.59.0, that choice is not remembered across plays. The block style now returns to [default ] # when I quit and restart the game.

Thanks for reporting. I think I know how to fix it.

That fixed it! Thanks!
I'm also submitting a Homebrew pull request so that I can install from the master branch rather than a release tarball: https://github.com/Homebrew/homebrew-core/pull/67600


Support the AccessKit focus and blur actions

I believe this is necessary to activate and deactivate input focus with TalkBack on Android. Assistive technologies on other platforms can also request the focus action, though none of the AccessKit backends support the blur action yet.

It certainly would be better for the framework to support this automatically for any focusable widget. I'll see if there's an easy way to do that in the current architecture.

To let the framework automatically handle the AccessKit focus and blur actions, it seems to me that we should add a flag to WidgetState to indicate whether the widget is in the focus chain, so build_access_node can check that flag. Does anyone have a different idea?

Yeah, I think that makes sense. Don't forget to reset that flag in the update_focus pass.
I know that our logic for focus has not been fully reasoned about, so a short-term change to unlock this functionality should be fine. (In particular, I don't think we know how setting a custom 'tab-index' will work)

OK, now the framework generically supports this for any widget in the focus chain.

OK, I think my last push addresses all remaining review comments.

@DJMcNab @PoignardAzur Can you please give this one more look before I merge?

Will do tomorrow.


update rust-bitcoin to 0.31

Since elements-miniscript depends on rust-simplicity and keystone depends on both rust-elements and elements-miniscript we need this to try out https://github.com/ElementsProject/rust-elements/pull/188
Not mergeable yet, since it requires rust-elements release to remove the patch section

can't figure out how to reproduce the clippy issue locally

Also, I am not sure how to solve the fuzz errors...

I can't wait to nixify CI so our errors become more reproducible.

Lol, when you find out what's involved in running clippy from Nix you'll wish you were still waiting.

Thanks @uncomputable that fixed the clippy issue.

latest force-push only updated the version of unreleased rust-elements.
fuzzing fixed thanks to secp256k1-zkp point release https://github.com/BlockstreamResearch/rust-secp256k1-zkp/pull/78
To be undrafted now needs only rust-elements release


Fixes #1900 - Add a marathon-interface project

Generally looks good: does the publishing work in TC?


:art: A new line before code block.

Seriously, before Gemfile commited it was inline code, not block code.
Ref https://github.com/slashsBin/styleguide-git-commit-message/commit/8b6f8dae0d6ec54187ec3e988714b6cbc6247715

Why the New Line?
It works without it now, doesn't it?

You can check it out here too: http://slashsbin.com/styleguide-git-commit-message/

That's odd. I had revert the commits into gh-pages branch and there's nothing wrong.
https://indrakaw.github.io/styleguide-git-commit-message/
I had to google it and found this: https://anon.to?https://github.com/jekyll/jekyll/issues/3724
You may close this PR or merge.


Expose format & ban list info from Card

Add relationships/links between cards and formats and ban lists they are in.

Both card and printing have this info exposed after #107 and #119


[Feature]: Support for compiled model graph for TPUs

🚀 The feature, motivation and pitch
A very naive question, is there any way to get or download the compiled LLM model graph for TPUs, so that we can bypass the time consuming step of graph compilation on TPU VMs.  What I am trying to find out is that can I compile the (model + Hardware) graph on the CPU and execute that on TPU cluster. Thank you so much for considering.
Alternatives
No response
Additional context
No response
Before submitting a new issue...

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

Hi @confusedgoose627 sorry i missed this question (I was using the TPU tag to filter). Hopefully this helps future readers. You'll want to write to a compilation cache on disk and have that available for the machine you're using on future runs (like on a new node that's autoscaling, or if you want to run the server a second time on the same machine).
sort of like (in a manifest):
- name: VLLM_XLA_CACHE_PATH
value: "/data"
or set directly as an env var on a local machine.
It takes significantly less time the second time you run it once you have this env var set and the compiled graph written to an accessible storage location.


More Cleanup

Add updated auto formatters
Add flake8
Update pytest config and handle warnings

After this I'll make an initial release so we can test in https://github.com/jupyter-server/jupyter_server/pull/651


[BEAM-3209] Clarify documentation on support for reading from/writing to time par…

…titioned BQ tables.
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @aaltay

LGTM

SUCCESS
--none--

SUCCESS
--none--

FAILURE
--none--

Thanks.

FAILURE
--none--


twister: handle quotes for all args

Instead of only cmake arguments, add support handling quotes for all args by escaping them properly instead of removing the quotes altogether.

what is the issue you are to fix exactly?

what is the issue you are to fix exactly?

I was trying to pass below to the sample.yaml twister test and as the quotes are removed west build fails with malformed string CONFIG_TRAFFIC_GEN_REMOTE_IPV4_ADDR=<IP_ADDRESS>.
extra_args: CONFIG_TRAFFIC_GEN_REMOTE_IPV4_ADDR="<IP_ADDRESS>"


RFP - IObit Driver Booster

I am requesting a package to be made.
Application website:
https://www.iobit.com/en/driver-booster.php

A package for this request already exists:
https://chocolatey.org/packages/driverbooster


Example of multiple textures

For example when I want to use a texture map and a normal map for a single program, how does ModernGL decide which Sampler2D corresponds to which texture.use() call? Is there an example of multiple texture use?

texture.use() is equal to texture.use(0). 0 stands for GL_TEXTURE0
Here is a small snippet to show how to assign textures to samplers easily:
texture1.use(1)
texture2.use(2)
texture3.use(3)

program.uniforms['sampler1'].value = 1
program.uniforms['sampler2'].value = 2
program.uniforms['sampler3'].value = 3

I will add an example and I will link it in the docs.
This is a small project that uses multiple textures: heightmap-multitexture-terrain

PS: I am currently unifying the examples (a single example file will work with multiple window implementations).

Thank you for the feedback!

Hello!
I refactored the examples and added an example for multi textures.
If you want to run the examples please install the following modules first:
pip install ModernGL ModernGL.ext.examples ModernGL.ext.obj

The multi texture example is: examples/multi_texture_terrain.py

Awesome, thanks! I'm currently working on something else but radiant will become a priority for me again in a month or so.

Taking the liberty of closing this issue. The multitexture example is present and some of the comments here may even refer to version 4.x.


E2E: go release main SLSA3 config-ldflags assets

Repo: https://github.com/slsa-framework/example-package/tree/v16.0.14
Run: https://github.com/slsa-framework/example-package/actions/runs/6728142763
Workflow name: go release main SLSA3 config-ldflags assets
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-assets.slsa3.yml
Trigger: release
Branch: v16.0.14
Date: Thu Nov  2 04:09:53 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v16.0.14
Run: https://github.com/slsa-framework/example-package/actions/runs/6741136624
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-assets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.release.main.config-ldflags-assets.slsa3.yml
Trigger: release
Branch: v16.0.14
Date: Fri Nov  3 04:17:13 UTC 2023
Tests are passing now. Closing this issue.


add config option to enable / disable "dev mode"

In particular, we want a way to (via config option) re-enable password authentication and user management so we can test them.  As it stands right now, neither feature is exposed.  It doesn't really matter what the default is as long as we can toggle this on or off as needed.

As of 1.0beta1, local password authentication and user management work.  Should we just close this issue?

Yes we should.  Closing.


Fix: merge is not a function

Fixed #94

@jengjeng thanks for fixing this so quickly! May I ask how your environment looks like? Do you use ES6 with Babel for example?

@jengjeng if you are using es6 then probably #96 is a better fix for this issue.

Yes. I'm using babel. I agree to merge it with #96


Add command-line parameter -slug to over-ride what's in the config file

This was implemented as -m for me to identify what my / the user's slug is


New Feature: limiting shared code

A cool feature of GWT was that I could "emulate" shared code that was written for the server in the client with a "limited" implementation. The actual way to do this in GWT via super-sourcing was maybe a little odd but I wanted to make my code work in teavm und stubled over this problem. First of all I am impressed what is already working and at which speed - so thanks for all your hard work.
When using by Bean class in TeaVM, I got this error:
Class java.util.concurrent.ConcurrentHashMap was not found
    at io.github.mmm.bean.AbstractBean.<init>(AbstractBean.java:54)
    at io.github.mmm.bean.Bean.<init>(Bean.java:31)
    at com.demo.Client$MyBean.<init>(Client.java:41)
    at com.demo.Client$MyBean.<init>(Client.java:37)
    at com.demo.Client.<init>(Client.java:14)
    at com.demo.Client.main(Client.java:19)

Code is open-source, so you can find it here:
https://github.com/m-m-m/bean/blob/master/core/src/main/java/io/github/mmm/bean/AbstractBean.java#L54
Of course, I can try to rewrite my code and change the design so that I use a protected method providing the map implementation that gets overridden for the backend. However, I am sure this is not the last time I hit some problem like this. Also the problem could occur with external code that can not be tweaked.
Is there a solution in TeaVM for this problem available or planned?
Sidenote: Also I am thinking about the approach of candies in https://dragome.com where one can provide a complete JavaScript version for a library (JAR). Allowing to implement an optimized JavaScript/WASM would also be a killer feature to emulate the beans and properties I created in my OSS project natively in the browser to even more boost performance as JavaScript already has properties with value change listeners and this does not need to be emulated via Java compiled with teavm.

You can create org.teavm.classlib.java.util.concurrent.TConcurrentHashMap in your project. See how Java class library emulated in classlib module

Aha, cool. So it seems you already have some kind of GWT super-sourcing equivalent in TeaVM.
https://github.com/konsoletyper/teavm/tree/master/classlib/src/main/java/org/teavm/classlib/java
So maybe I could provide a documentation snipplet as PR and this issue can already be closed as the feature is already there. I assume the 'T' prefix is just a kind of design decision to avoid code completion pollution and stands for TeaVM.
Also if I would actually write such TConcurrentHashMap class and make it work, I could provide this as PR so #445 could be closed.

Is the same approach also working to provide client implementations for non JDK internal code?
I assume so. In other words when I add org.teavm.classlib.«mypackage».T«MyClass» it will replace «mypackage».«MyClass» in the client code?

Is the same approach also working to provide client implementations for non JDK internal code?
I assume so. In other words when I add org.teavm.classlib.«mypackage».T«MyClass» it will replace «mypackage».«MyClass» in the client code?

No, things are little bit complex. The rules are provided here, you can add you own teavm.properties file with you own rules


can't find it on Yarn

Hello!
I am very interested in this component, looks really interesting,  but I can't find it on Yarn as the Readme file specifies... is there any other way I can import this component in my project?

I just published it on the npm registry. It was not published so far, as the README stated ;)
Give it a try.

Working like a charm in a Firebase-Angular5-Material project, trying out Spanish internationalization, enough with MatNativeDatetimeModule. Thank you so much!!!!!!


Use npe2 fetch for discovering plugin manifests

Summary
This issue captures the work described in TODO number 3 of #587. Refactor plugins/get_plugin_manifest.generate_manifest to use npe2 fetch command for discovering/generating manifests.
Rationale: Following npe2 #185 the library now provides a fetch command which takes a plugin name and version, and retrieves its manifest (building it if the plugin is npe1). Using this tool is a good separation of concerns between the napari hub and the npe2 library, and ensures we use the same mechanisms a plugin developer would to ensure their plugin's compatibility with npe2 and the napari hub. Additionally, the mechanism is more full featured than our initial implementation: avoids plugin installs for packages where the wheel can be retrieved, more options for customization and error message reporting.
Intended Outcome
Our manifest discovery & generation is identical to that used in napari and reproducible by plugin developers locally.
How will it work?
We will replace the majority of the code in plugins/get_plugin_manifest to instead just run the npe2 fetch command. We still need to decide on certain customizable options for this command:

install napari on initial failure in case plugin was missing napari dependency? (may need small npe2 change)
validate that npe1 plugins can actually be imported before generating manifest? (may need small npe2 change)
catch missing dependency errors from plugin and attempt to fix?
turn off env building for plugin install to speed things up, since we're running in a dedicated container anyway? (needs small npe2 change)

This issue can be closed following the work in #645.


clientv3: support WithRequireLeader in lease client

Fixes #7275
Also includes a test/fix for the etcdserver when using WithRequireLeader for lease streams. Without the fix, the lease stream could wait forever on a Recv() if the leader is lost instead of exiting immediately.

LGTM

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9ca7f22). Click here to learn what that means.
The diff coverage is 92.45%.

@@            Coverage Diff            @@
##             master    #7630   +/-   ##
=========================================
  Coverage          ?   73.27%
=========================================
  Files             ?      327
  Lines             ?    26638
  Branches          ?        0
=========================================
  Hits              ?    19520
  Misses            ?     5638
  Partials          ?     1480

Impacted Files
Coverage Δ

etcdserver/api/v3rpc/lease.go
92.85% <100%> (ø)

clientv3/lease.go
92.24% <90%> (ø)

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 9ca7f22...8024a0d. Read the comment docs.


Fix: region selector tests moved to blocks

Before: https://stage--dme-partners--adobecom.hlx.live/channelpartners/?georouting=off
After: https://quickfix-nala--dme-partners--adobecom.hlx.live/channelpartners/?georouting=off

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.53%. Comparing base (9f9c62f) to head (6eef161).

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #106   +/-   ##
=======================================
  Coverage   83.53%   83.53%
=======================================
  Files          10       10
  Lines        3212     3212
=======================================
  Hits         2683     2683
  Misses        529      529

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


The main example doubled the selector, one styled while the other is not styled.

I use this example.
<select class="selectpicker">
  <option>Mustard</option>
  <option>Ketchup</option>
  <option>Relish</option>
</select>

I downloaded bootstrap-select via Bower, also with all recent package of Bootstrap and JQuery also from Bower.


Use appveyor to test windows compatibility

Although I am not a specialist, the implementation of appveyor (or other) would test the Windows compatibility in the npm scripts.
What do you think about it ?

Sounds interesting. I reckon that is another CI. Keen to make a PR with base config?
PS: exactly at current moment I am sitting behind Mac and PC, pushing from Mac and running scripts on PC. That is funny. Would be cool to have this automated.

https://ci.appveyor.com/project/nkbt/react-component-template

As I said, I'm not a specialist, but I want to try. I read the doc, I make tests quickly and I try to do a PR.

First test : https://ci.appveyor.com/project/forresst/react-component-template/build/2

:yum: nice

Hi, @forresst since your build is working, you can do a PR and all extra configuration if needed I could add later. What do you reckon?

sounds really good

Oooooops ! I forgot the subject.
I made some changes to be roughly equivalent to circleCI:

only node.js 0.10.4
Install npm release 3 : npm -g install npm@3
I deleted 'npm run build'. It was launched twice!

Sorry for the delay

@forresst no worries! thanks you a lot!


Monitor how long requests are in the queue

When a client makes a request, the clio server receives it and begins processing. However, if the clio server is under heavy load, the request may have to wait before processing begins. This is all done behind the scenes by asio, but we should try to somehow find a way to log when requests are waiting, and for how long.

Done in #168, however it is currently only logged, and will be reported in counters after #151 is merged


Layer Reshape along the sample axis

Hi, I wonder is that possible to reshape a keras tensor along a sample axis? For example, something looks like
from keras.layers import Input
from keras.layers.core import Reshape

input_shape = (5,32,32,1) # the batch size is 5
tensor = Input(batch_shape=input_shape)
new_tensor = Reshape((1,)+tensor._keras_shape)(tensor)	# the new tensor should be (1,5,32,32,1)

I have a bug when trying the above code: ValueError: total size of new array must be unchanged
It seems that keras does not allow to change the size of sample axis, it this true? Is there any solution to this problem?
Thanks!

I think "TimeDistributed" is the solution.

You can use a Lambda layer that wraps keras.backend.reshape.


Fully resolve items

This change is

Current dependencies on/for this PR:

main

PR #2595   👈

This comment was auto-generated by Graphite.


Snapshot can only be used to initialize an empty database.

I'm currently trying to replay from snapshot inside a docker container with an attached volume. On fresh run everything seems to work and I sync up after 1-2 days. However, if the container rolls over at any point for any reason I get this message.
warn  2020-04-08T21:09:18.280 nodeos    chain_plugin.cpp:1093         plugin_initialize    ] 3110006 plugin_config_exception: Incorrect plugin configuration
Snapshot can only be used to initialize an empty database.
    {}
    nodeos  chain_plugin.cpp:862 plugin_initialize
error 2020-04-08T21:09:18.280 nodeos    main.cpp:125                  main                 ] 3110006 plugin_config_exception: Incorrect plugin configuration
Snapshot can only be used to initialize an empty database.
    {}
    nodeos  chain_plugin.cpp:862 plugin_initialize
rethrow
    {}
    nodeos  chain_plugin.cpp:1093 plugin_initialize

I am 100% the node is shutting down gracefully, I handle all signals. Here is my config.  If I remove --snapshot all together, after first roll over, it seems to start at 0 like it never synced before from a snapshot.
I can't find complete documentation on how to simply get a node up and running quickly and maintain all history information going forward. I want my node to be able to be shutdown/restart without having to manually manipulate files / etc on reboot.

--snapshot can only be used if there is no state directory.  You should have a startup script for your nodeos that checks if there is state and if yes, don't use the snapshot.
My startup script looks like this:
#!/bin/sh

ulimit -a
DATADIR="/var/lib/nodeos"
CONFIGDIR="/etc/nodeos"
COMMAND="/usr/bin/nodeos --config-dir $CONFIGDIR -d $DATADIR"

if [ -e /var/lib/nodeos/snapshots ]
then
        SNAPSHOT=`ls /var/lib/nodeos/snapshots/ | head -1`
else
        SNAPSHOT=""
fi

if [ ! -e /usr/bin/nodeos ]
then
        echo "No nodeos binary; aborting"
        sleep 10
        exit 1;
fi

if [ -e "$DATADIR/state/shared_memory.bin" ]
then
        echo "nodeos-wrapper: we've previously run"
        echo "if error then rm -fr $DATADIR/state/*"

elif [ ! -z "$SNAPSHOT" ] && [ -e "$DATADIR/snapshots/$SNAPSHOT" ] && [ -e "$DATADIR/blocks/blocks.log" ]
then
        echo "nodeos-wrapper: we've previously run, but state is missing; using snapshot"
        echo "if error then rm -fr $DATADIR/snapshots/*"
        COMMAND=`echo $COMMAND --snapshot $DATADIR/snapshots/$SNAPSHOT`

elif [ -e "$DATADIR/blocks/blocks.log" ]
then
        echo "nodeos-wrapper: we've previously run, but state is missing; replaying blocks"
        echo "if error then rm -fr $DATADIR/blocks/*"
        COMMAND=`echo $COMMAND --replay-blockchain --genesis-json=$CONFIGDIR/genesis.json`

elif [ ! -z "$SNAPSHOT" ] && [ -e "$DATADIR/snapshots/$SNAPSHOT" ]
then
        echo "nodeos-wrapper: we've previously run, but state and blocks are missing; using snapshot"
        echo "if error then rm -fr $DATADIR/snapshots/*"
        COMMAND=`echo $COMMAND --snapshot $DATADIR/snapshots/$SNAPSHOT`

else
        echo "nodeosd-wrapper: first time start"
        COMMAND=`echo $COMMAND --genesis-json=$CONFIGDIR/genesis.json`
fi

exec $COMMAND

@phewitt
Are you using 2.0.x release?
Tried with a nodeos version similar to 2.0.5 release (same day as it is released). See the sync will be resumed from previous graceful exit when using w/o --snapshot. However the log print is confusing, (Catching up with chain, our last req is 0, ...), may need to fix this.

Started Nodeos with --snapshot, (handshake from <IP_ADDRESS>:9876 - 64abcce, lib 116708620, head 116708952, head id db4b5fda5d9013ff.. sync 1)
info  2020-04-21T18:06:40.164 thread-0  net_plugin.cpp:816            connection           ] creating connection to peer.main.alohaeos.com:9876
info  2020-04-21T18:06:40.164 thread-1  net_plugin.cpp:2141           operator()           ] host: peer.main.alohaeos.com port: 9876
info  2020-04-21T18:06:40.315 thread-2  net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to peer.main.alohaeos.com:9876, lib 116693816, head 116693816, id 9cecee94ff9ac52c
info  2020-04-21T18:06:40.432 thread-1  net_plugin.cpp:1379           set_state            ] old state in sync becoming lib catchup
info  2020-04-21T18:06:40.432 thread-1  net_plugin.cpp:1545           start_sync           ] Catching up with chain, our last req is 0, theirs is 116708620 peer peer.main.alohaeos.com:9876
info  2020-04-21T18:06:40.432 thread-1  net_plugin.cpp:1491           operator()           ] requesting range 116693817 to 116693916, from peer.main.alohaeos.com:9876
info  2020-04-21T18:06:40.432 thread-1  net_plugin.cpp:1605           recv_handshake       ] handshake from <IP_ADDRESS>:9876 - 64abcce, lib 116708620, head 116708952, head id db4b5fda5d9013ff.. sync 1
info  2020-04-21T18:06:52.427 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116693917 to 116694016, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:07:02.086 thread-0  producer_plugin.cpp:401       on_incoming_block    ] Received block b6aad929e1e9420f... #116694000 @ 2020-04-21T16:01:34.000 signed by atticlabeosb [trxs: 17, lib: 116693816, conf: 0, latency: 7528086 ms]
info  2020-04-21T18:07:03.792 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694017 to 116694116, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:07:10.167 thread-2  net_plugin.cpp:3090           connection_monitor   ] p2p client connections: 0/25, peer connections: 1/1
info  2020-04-21T18:07:15.304 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694117 to 116694216, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:07:27.945 thread-1  net_plugin.cpp:1491           operator()           ] requesting range 116694217 to 116694316, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:07:38.686 thread-1  net_plugin.cpp:1491           operator()           ] requesting range 116694317 to 116694416, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:07:40.167 thread-1  net_plugin.cpp:3090           connection_monitor   ] p2p client connections: 0/25, peer connections: 1/1
info  2020-04-21T18:07:50.638 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694417 to 116694516, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:08:02.094 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694517 to 116694616, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:08:10.170 thread-2  net_plugin.cpp:3090           connection_monitor   ] p2p client connections: 0/25, peer connections: 1/1
info  2020-04-21T18:08:13.440 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694617 to 116694716, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:08:25.744 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694717 to 116694816, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:08:37.129 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694817 to 116694916, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:08:39.855 thread-2  net_plugin.cpp:943            _close               ] closing 'peer.main.alohaeos.com:9876', peer.main.alohaeos.com:9876
info  2020-04-21T18:08:39.995 thread-1  net_plugin.cpp:943            _close               ] closing 'peer.main.alohaeos.com:9876', peer.main.alohaeos.com:9876
info  2020-04-21T18:08:40.001 thread-0  net_plugin.cpp:3515           plugin_shutdown      ] shutdown..
info  2020-04-21T18:08:40.001 thread-0  net_plugin.cpp:3532           plugin_shutdown      ] close 1 connections
info  2020-04-21T18:08:40.001 thread-0  net_plugin.cpp:3552           plugin_shutdown      ] exit shutdown
info  2020-04-21T18:09:25.655 thread-0  main.cpp:149                  main                 ] nodeos successfully exiting

restart nodeos w/o --snapshot (handshake from <IP_ADDRESS>:9876 - 64abcce, lib 116709265, head 116709593, head id 4b3ef5e5de2c5b6a.. sync 1)

info  2020-04-21T18:12:02.137 thread-1  net_plugin.cpp:1545           start_sync           ] Catching up with chain, our last req is 0, theirs is 116709265 peer peer.main.alohaeos.com:9876
info  2020-04-21T18:12:02.137 thread-1  net_plugin.cpp:1491           operator()           ] requesting range 116694506 to 116694605, from peer.main.alohaeos.com:9876
info  2020-04-21T18:12:02.137 thread-1  net_plugin.cpp:1605           recv_handshake       ] handshake from <IP_ADDRESS>:9876 - 64abcce, lib 116709265, head 116709593, head id 4b3ef5e5de2c5b6a.. sync 1
info  2020-04-21T18:12:03.726 thread-1  net_plugin.cpp:1491           operator()           ] requesting range 116694606 to 116694705, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:12:04.738 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694706 to 116694805, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:12:05.746 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694806 to 116694905, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:12:14.638 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116694906 to 116695005, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:12:26.204 thread-0  producer_plugin.cpp:401       on_incoming_block    ] Received block b60d5e38950d72ba... #116695000 @ 2020-04-21T16:09:56.000 signed by atticlabeosb [trxs: 19, lib: 116694672, conf: 0, latency: 7350204 ms]
info  2020-04-21T18:12:26.840 thread-2  net_plugin.cpp:1491           operator()           ] requesting range 116695006 to 116695105, from <IP_ADDRESS>:9876 - 64abcce
info  2020-04-21T18:12:30.947 thread-1  net_plugin.cpp:943            _close               ] closing 'peer.main.alohaeos.com:9876', peer.main.alohaeos.com:9876
info  2020-04-21T18:12:30.947 thread-1  net_plugin.cpp:943            _close               ] closing 'peer.main.alohaeos.com:9876', peer.main.alohaeos.com:9876
info  2020-04-21T18:12:30.952 thread-0  net_plugin.cpp:3515           plugin_shutdown      ] shutdown..
info  2020-04-21T18:12:30.952 thread-0  net_plugin.cpp:3532           plugin_shutdown      ] close 1 connections
info  2020-04-21T18:12:30.952 thread-2  net_plugin.cpp:943            _close               ] closing 'peer.main.alohaeos.com:9876', peer.main.alohaeos.com:9876
info  2020-04-21T18:12:30.952 thread-0  net_plugin.cpp:3552           plugin_shutdown      ] exit shutdown


shortcut problems

From<EMAIL_ADDRESS>on 2011-01-27T05:23:44Z
What steps will reproduce the problem?
open pref and change shortcut.
I tried to change the shortcut of "comment". from 3 to quote_double (french keyboard) What is the expected output? What do you see instead? when I press ctrl+", I get a " (not a comment) What version of the product are you using? On what operating system? spyderlib 2.06. XP sp3 and Ubuntu 10.10
Please provide any additional information below
. I tried to use other shortcut for "comment". like "slash". does not work.
But if I use a simple letter, like ctrl+J, it works
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=539

From pierre.raybaut on 2011-01-31T01:15:23Z
Status: Duplicate
Mergedinto: 478


Any solution for GrapheneOS

Avoid duplicates

[ ] This enhancement request has not already been raised before
[ ] Enhancement request is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in CWA-Wishlist
[ ] If you are proposing a new feature, please do so in CWA-Wishlist

Current Implementation

Suggested Enhancement

Expected Benefits

Closed as duplicate entry #813