Unable to use sparse_categorical_accuracy with softmax output ndims=3

System information

Have I written custom code (as opposed to using example directory):  yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Ubuntu 16.04
TensorFlow backend (yes / no):  yes
TensorFlow version:  1.14 (built from source)
Keras version:  (built-in TF version)
Python version:  3.7.4
CUDA/cuDNN version:  10.0
GPU model and memory:  GeForce RTX 2070 8G

Describe the current behavior
Running the following minimal example
import numpy
from tensorflow import keras

x = keras.layers.Input(shape=(8,), dtype="int32")
y = keras.layers.Embedding(4, 2)(x)
y = keras.layers.Dense(4, activation="softmax")(y)

training_model = keras.Model(x, y)

training_model.compile(
    keras.optimizers.SGD(),
    loss=keras.losses.sparse_categorical_crossentropy,
    metrics=[keras.metrics.sparse_categorical_accuracy]
)

data = numpy.random.randint(4, size=(16, 8))
training_model.fit(x=data, y=data)

results in
Traceback (most recent call last):
  File "issue.py", line 18, in <module>
    training_model.fit(x=data, y=data)
  File "/python_env/lib/python3.7/site-packages/tensorflow/python/keras/engine/training.py", line 780, in fit
    steps_name='steps_per_epoch')
  File "/python_env/lib/python3.7/site-packages/tensorflow/python/keras/engine/training_arrays.py", line 363, in model_iteration
    batch_outs = f(ins_batch)
  File "/python_env/lib/python3.7/site-packages/tensorflow/python/keras/backend.py", line 3292, in __call__
    run_metadata=self.run_metadata)
  File "/python_env/lib/python3.7/site-packages/tensorflow/python/client/session.py", line 1458, in __call__
    run_metadata_ptr)
tensorflow.python.framework.errors_impl.InvalidArgumentError: 2 root error(s) found.
  (0) Invalid argument: Can not squeeze dim[1], expected a dimension of 1, got 8
	 [[{{node metrics/sparse_categorical_accuracy/Squeeze}}]]
	 [[metrics/sparse_categorical_accuracy/Identity/_65]]
  (1) Invalid argument: Can not squeeze dim[1], expected a dimension of 1, got 8
	 [[{{node metrics/sparse_categorical_accuracy/Squeeze}}]]
0 successful operations.
0 derived errors ignored.

but commenting out the metrics=[keras.metrics.sparse_categorical_accuracy] line results in success.
Describe the expected behavior
When using categorical targets it should be possible to use keras.metrics.sparse_categorical_accuracy
Code to reproduce the issue
See above.
Other info / logs
N/A

Attempting to debug this by copy-pasting the code for sparse_categorical_accuracy and adding some keras.backend.print_tensor operations suggests something very strange: the symbolic shape of y_true is (?, ?, ?) (note: 3 dimensions) but the concrete value at runtime has only 2 dimensions. The 2 dimensions are correct because it's an integer array but because the symbolic shape is incorrect, the set of operations being applied causes the "squeeze" error. How can Keras be getting the symbolic shape of the targets so wrong?

I've found a work-around: training_model.fit(x=data, y=numpy.expand_dims(data, -1))

@qtdaniel We see that you are using old version of tensorflow which is not actively supported now, please verify on 2.x and open a new issue in case you face any errors, hence moving this to closed status.Thanks!


11091 rails 6

I wrote a lot of info in the commit messages so I truly recommend going one-by-one for this one (there are a lot but they're each fairly straightforward).
Hoping to get this core work released this sprint, then I have more deprecation fixes and upgrades coming soon. SO MANY DEPRECATIONS! 🚀
[Still waiting in the Travis queue... will assign you after it's confirmed]

This is ridiculous! Re-submitting on top of the cops PR #771.


[Proposal] Customizable log filter

Proposal
We should allow people to filter logs out at the fluentd level. This can be done at the component level or for log messages that match a regular expression. Both would be useful.

Nevermind I'm just going to close this for now.


Update crates to Rust 2021 Edition

Description
Rust 2021 edition is here! Let's update the crates here to use it.
Information on migration can be found over at The Edition Guide.
Some things this effort might include:
# may need to make manual changes if errors
cargo fix --edition

Beyond that, update the edition in Cargo.toml to "2021".
Lastly, consider removing import statements(if available) for TryInto, TryFrom and FromIterator as these have been added to the prelude.

@jregistr ended up doing a bit of an impromptu updated as I needed disjoin capture, so we are on 2021 edition now!


ARROW-11052: [Rust] [DataFusion] Implement metrics for HashJoinExec

Implement metrics for HashJoinExec to help debug performance issues.
Example output:
[2020-12-28T20:46:28Z DEBUG datafusion::physical_plan::hash_join] Built build-side of hash join containing 3115341 rows in 9926 ms
[2020-12-28T20:46:36Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18750000 rows and produced 144 output batches containing 388922 rows in 7994 ms
[2020-12-28T20:46:36Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18750000 rows and produced 144 output batches containing 389294 rows in 7986 ms
[2020-12-28T20:46:37Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18750000 rows and produced 144 output batches containing 389558 rows in 8326 ms
[2020-12-28T20:46:37Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18750000 rows and produced 144 output batches containing 388841 rows in 8499 ms
[2020-12-28T20:46:37Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18750000 rows and produced 144 output batches containing 390056 rows in 8643 ms
[2020-12-28T20:46:37Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18749999 rows and produced 144 output batches containing 389143 rows in 8711 ms
[2020-12-28T20:46:37Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18750000 rows and produced 144 output batches containing 389605 rows in 8712 ms
[2020-12-28T20:46:37Z DEBUG datafusion::physical_plan::hash_join] Processed 144 probe-side input batches containing 18750000 rows and produced 144 output batches containing 389922 rows in 8877 ms

@jorgecarleitao fyi

I will rebase this and address feedback once https://github.com/apache/arrow/pull/9048 is merged

The full set of Rust CI tests did not run on this PR :(
Can you please rebase this PR against apache/master to pick up the changes in https://github.com/apache/arrow/pull/9056 so that they do?
I apologize for the inconvenience.

@Dandandan , Thanks a lot for the review. I am approving because even though I consider most of your comments relevant, I do not consider them blocking the merge.
For example, summing the number of rows of all batches is O(number_of_batches) and negligible when compared to the time it takes to execute the join, thus being too minor to block this.

@Dandandan , Thanks a lot for the review. I am approving because even though I consider most of your comments relevant, I do not consider them blocking the merge.
For example, summing the number of rows of all batches is O(number_of_batches) and negligible when compared to the time it takes to execute the join, thus being too minor to block this.

I agree, feel free to address the remaining feedback or to merge it @andygrove👍

I agree, feel free to address the remaining feedback or to merge it @andygrove👍

Codecov Report

Merging #9035 (4b5154a) into master (4b7cdcb) will decrease coverage by 0.02%.
The diff coverage is 52.63%.

@@            Coverage Diff             @@
##           master    #9035      +/-   ##
==========================================
- Coverage   82.61%   82.58%   -0.03%
==========================================
  Files         203      203
  Lines       50140    50171      +31
==========================================
+ Hits        41422    41436      +14
- Misses       8718     8735      +17

Impacted Files
Coverage Δ

rust/datafusion/src/physical_plan/hash_join.rs
85.86% <52.63%> (-3.67%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #9035 (4b5154a) into master (4b7cdcb) will decrease coverage by 0.02%.
The diff coverage is 52.63%.

@@            Coverage Diff             @@
##           master    #9035      +/-   ##
==========================================
- Coverage   82.61%   82.58%   -0.03%
==========================================
  Files         203      203
  Lines       50140    50171      +31
==========================================
+ Hits        41422    41436      +14
- Misses       8718     8735      +17

Impacted Files
Coverage Δ

rust/datafusion/src/physical_plan/hash_join.rs
85.86% <52.63%> (-3.67%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix bin PATH for sudo

Fix bin PATH for sudo crictl

Let's see if this will fix the command not found issue.


Anyterm for Config UI X

Hi,
Do you think it is possible to implement Anyterm for an "in-Browser" administration of your Homebridge Device e.g Raspberry Pi ?

When running in docker this plugin actually already provides this exact feature. I didn't enable it for other platforms as I thought it might present a security risk that users may not particularly like if I added the feature with an update.

Im not too much into programming but do you think it is possible to implement this feature if you want, so if you do not want it you have to uncheck a checkbox for example ?

Is it difficult to install AnyTerm on the PI? Or is it for a single webinterface?

@razer4908 - I have enabled this. However, it's not a simple config.json flag, since this could be toggled from inside the UI itself which would defeat the purpose of having it disabled by default.
You'll need to run the process with the environment variable HOMEBRIDGE_CONFIG_UI_TERMINAL=1.
If you're running with systemd you can add this to your /etc/default/homebridge file.
Available in 3.8.3.


isabelle: Rebuild isabelle_setup.jar

This jar contained a call to /usr/bin/env bash which was causing an
error during the build of the HOL session (which could be ignored) and
caused other errors during the development of https://github.com/NixOS/nixpkgs/pull/157515
(which could not be ignored). This commit patches the java sources to
call bash directly and rebuild the jar.
Motivation for this change
Fix the error during the build from #154272
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

cc @gebner

cc @siraben because you merged isabelle stuff in the past :)

ping @gebner
It has been almost a month :)

Feel free to take over the Isabelle package and merge at your own discretion.  You certainly know more about Isabelle than I do!


Missing license file/info

What are the terms under which zippie is released?

Take what you can, give nothing back!

Just kidding, will sort this out soon. very soon.

Solved


Fix cell line height computation

Fixed computation of line height in cells as it was using column keys to determine line height instead of values.

Thanks for the pull request. The tests fail because Object.entries is not defined in the CI Chrome (53.0.2785). Please use a different function for this.

The tests now fail in IE:
IE 11.0.0 (Windows 10.0.0) Context2D: standard tests context2d: fonts FAILED
	TypeError: Object doesn't support property or method 'getTextDimensions'
	error properties: Object({ number: -2146827850 })
	    at <Jasmine>
	   at putText (src/modules/context2d.js:9:80047)
	   at Context2D.prototype.fillText (src/modules/context2d.js:9:44096)
	   at Anonymous function (spec/context2d.spec.js:82:5)
	    at <Jasmine>

I assume the reason is the es6 code you use. Could you try and use only es5 compliant code?


devices: Add Google Coral Dev Board

Closes #1303
Change-type: minor
Connects-to: #1303
Signed-off-by: Gareth Davies<EMAIL_ADDRESS>

@balena-ci retest


Jamie/bug table sweep

:nut_and_bolt: Description: What code changed, and why?
Additional sweep on formatting that may need to be adjusted related to https://github.com/chef/automate/pull/2963
:chains: Related Resources
https://github.com/chef/automate/pull/2963
:+1: Definition of Done

table headers match alignment with table columns
Any outstanding long content is ellipsed or contained in column

:athletic_shoe: How to Build and Test the Change
build components/automate-ui && start_all_services
make serve
:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable

@msorens / @susanev - I've done an additional sweep through automate and made any adjustments I could find.  Most of this is shrinking down the table headers that match to the control menu since it was shrunk down.
I'm also going to move up the new table component swapping in priority - I started to scope creep on this and decided to back off and focus on the table swapping on its own branch.

This branch is an extension of https://github.com/chef/automate/issues/2962

since you are here on scan jobs, it would be really rad to remove that sorta informational table row, and move the button to the top of the table. the button label should adjust to Create Scan Job as well.

same with nodes added tab

Any extras here can/will be handled in the table sweep i'm doing now: https://github.com/chef/automate/issues/2064


⚠ ClamAV has degraded performance

In 189110e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 107 ms

Resolved: ClamAV performance has improved in de545ad after 14 minutes.


nuxt build fails in "previews"

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
dl4hgzkr4l6xx
Region
eu-central-1
Amplify Hosting feature
Build settings, Custom builds
Describe the bug
we have a nuxt app building correctly except for pull requests (preview apps - branch "feature"), in this case the build fails
2022-05-24T09:57:53.316Z [INFO]: ><EMAIL_ADDRESS>generate /codebuild/output/src374040070/src/bflows-frontend
                                 > nuxt generate
2022-05-24T09:57:53.320Z [WARNING]: sh: nuxt: command not found

Expected behavior
the build of "feature" branch should run  normally like in other branches, the nuxt command should be found
Reproduction steps
trigger a build for pr/review app
Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - nvm install 12.13.0
        - npm ci
    build:
      commands:
        - npm run generate
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Additional information
No response

nevermind
i've found the problem was a package-lock.json using "dev": true on all packages, removing this now the build works


Disable check "azure-resource-manager-schemas"

Check is no longer maintained, is not required, and fails somewhere between "often" and "always".
Example: https://github.com/Azure/azure-rest-api-specs/pull/27733/checks?check_run_id=24518860060

I started working on this here, but abandonded it before I finished:
https://dev.azure.com/devdiv/DevDiv/_git/openapi-alps/pullrequest/567542


rust, c: export funcs explicitly invoke static constructors

Before executing any other code, use this function (provided by wasm-ld)
to run all static constructors. When wasm-ld sees this explicit invocation
of ctors, it will not generate a wrapper aorund each exported func which
executes ctors first, and therefore we make sure that cabi_realloc doesnt
invoke ctors when called as an export func.
See https://github.com/bytecodealliance/preview2-prototyping/issues/99
for more details.

https://github.com/bytecodealliance/preview2-prototyping/pull/101 demonstrates that this is a fix that prevents running constructors which call import functions from cabi_realloc

Hm actually is this correct in the face of multiple invocations? IIRC wasi-libc has no guards against repeatedly invoking this so this may run the risk of allocating the whole environment on each export call?
Should this instead be moved to crates/guest-rust/src/lib.rs and have a static bool guarding it so it's only invoked once?

This is calling __wasm_call_ctors which is synthesized by wasm-ld, and it does not have guards against being called twice.

Right, the present situation is that the ctors get called at the start of every export func, and this PR backs them that to all export funcs except cabi_realloc. Right now the ctors that exist in wasi-libc are tolerant of that behavior.
In the Rust bindgen, we can add a once cell to the guest-rust crate and make sure ctors get invoked only once.
In the C bindgen, its much more difficult to add that logic, since there is no global singleton (like a crate static can provide) to make sure constructors only get invoked once. So, I'm actually considering dropping this patch from the C bindgen, rather than provide a fix that would be somehow incorrect, and leaving it as a problem for tool conventions and the canonical abi to fix.

Constructors run at most once, I rebased the C code generator changes out, and I added a note that this is just a temporary fix until rust 1.69.0 stabilizes, at which point wasi-libc ctors should no longer call import funcs (right?)

Oh the Windows failure reminds me, could the contents of the whole fuction added here be wrapped in #[cfg(target_arch = "wasm32")]? Technically it's only safe on single-threaded platforms like wasm anyway and shouldn't do anything anywhere else otherwise.

Yes the target arch guard got dropped, by accident, in my refactor. I added it back in as a guard around the presence of the rt::run_ctors_once function.


Shall we enable Smokey to pull from force-pushes?

Currently Smokey's pulling only uses git-pull, and as a consequence some related checks are in place, for example ensuring the target can be fast-forwarded before pulling.
This method apparently can't handle non-ff cases, like a force push.
Given that all modified files (logs, config, etc.) are ignored in .gitignore, we can probably use this method to allow pulling through force pushes:
git reset --hard origin/deploy

Is it going to be something handy to have?

Generally, there are only three reasons why a force push occurs:

There's a deploy/master mixup due to a mistake when setting up a new smokey (in which case, the host is directly on hand to fix the issue)
A developer accidentally pushes to the wrong branch (in which case, it hasn't been pulled yet)
Something really bad went wrong, in which case we probably don't want to perform git surgery via Smokey commands (manual intervention would be more appropriate)

I don't see how this command would be useful for any of those scenarios. What usecase were you considering for the command?


issue with second derivative

Hi,
I have been trying to use ImplicitDifferentiation.jl for higher order jvp but I was not lucky.

I want to use it for BifurcationKit.jl, where I need 3rd order jvp

Basic example:
using ImplicitDifferentiation
using Optim
using Random
using Zygote

Random.seed!(63)

function dumb_identity(x)
    f(y) = sum(abs2, y-x)
    y0 = zero(x)
    res = optimize(f, y0, LBFGS(); autodiff=:forward)
    y = Optim.minimizer(res)
    return y
end;

zero_gradient(x, y) = 2(y - x);
implicit = ImplicitFunction(dumb_identity, zero_gradient);
x = rand(3, 2)
h = rand(3, 2)
D(x,h) = Zygote.jacobian(t->implicit(x .+ t .* h), 0)[1]
D(x,h) # works
D2(x,h1,h2) = Zygote.jacobian(t->D(x .+ t .* h2,h1), 0)[1]
D2(x,h,h) # does not work

I also have this code with ForwardDiff. Not sure the problem is the same
using ForwardDiffChainRules, ForwardDiff
@ForwardDiff_frule (f::typeof(implicit))(x::AbstractMatrix{<:ForwardDiff.Dual})
D(x,h) = ForwardDiff.derivative(t->implicit(x .+ t .* h), 0)
D(x,h) # works
D2(x,h1,h2) = ForwardDiff.derivative(t->D(x .+ t .* h2,h1), 0)
D2(x,h,h) # does not work

for zygote:
julia> D2(x,h,h) # does not work
ERROR: Compiling Tuple{typeof(Optim.perform_linesearch!), Optim.LBFGSState{Matrix{Float64}, Vector{Matrix{Float64}}, Vector{Matrix{Float64}}, Float64, Matrix{Float64}}, LBFGS{Nothing, LineSearches.InitialStatic{Float64}, LineSearches.HagerZhang{Float64, Base.RefValue{Bool}}, Optim.var"#19#21"}, Optim.ManifoldObjective{OnceDifferentiable{Float64, Matrix{Float64}, Matrix{Float64}}}}: try/catch is not supported.
Refer to the Zygote documentation for fixes.
https://fluxml.ai/Zygote.jl/latest/limitations

for FoD:

julia> D2(x,h,h) # does not work
ERROR: MethodError: no method matching gmres(::LinearOperators.LinearOperator{ForwardDiff.Dual{ForwardDiff.Tag{var"#29#30"{Matrix{Float64}, Matrix{Float64}, Matrix{Float64}}, Int64}, Float64, 1}, Int64, ImplicitDifferentiation.var"#mul_A!#11"{ImplicitDifferentiation.var"#pushforward_A#9"{Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}}, ForwardDiffChainRules.ForwardDiffRuleConfig, Matrix{ForwardDiff.Dual{ForwardDiff.Tag{var"#29#30"{Matrix{Float64}, Matrix{Float64}, Matrix{Float64}}, Int64}, Float64, 1}}}, Matrix{ForwardDiff.Dual{ForwardDiff.Tag{var"#29#30"{Matrix{Float64}, Matrix{Float64}, Matrix{Float64}}, Int64}, Float64, 1}}}, Nothing, Nothing, Vector{ForwardDiff.Dual{ForwardDiff.Tag{var"#29#30"{Matrix{Float64}, Matrix{Float64}, Matrix{Float64}}, Int64}, Float64, 1}}}, ::Vector{ForwardDiff.Dual{ForwardDiff.Tag{var"#29#30"{Matrix{Float64}, Matrix{Float64}, Matrix{Float64}}, Int64}, Float64, 1}})

it is differentiating

Do you think it requires to implement the second differential in the implicit theorem or the algo should recursively call the first differential?

Do you think it requires to implement the second differential in the implicit theorem or the algo should recursively call the first differential?

I've been asking myself the same question for a project of mine. The problem is, ChainRulesCore only supports specification of first derivatives, so I'm not sure how to go about it in a way that's easy to use.

it seems the second differential bypasses the machinery of ImplicitDifferentiation

That's definitely worth investigating. Maybe we should define a rule on the pushforward / pullback?

I add the link to the discourse post

The problem is, ChainRulesCore only supports specification of first derivatives, so I'm not sure how to go about it in a way that's easy to use.

An example is here https://github.com/JuliaNonconvex/NonconvexUtils.jl/blob/main/src/custom.jl

Changing this line https://github.com/gdalle/ImplicitDifferentiation.jl/blob/1581d2e3b1b1ddf083f0d370c9f7b323aa98f610/src/implicit_function.jl#L64 to
y = implicit(x; kwargs...)

and using a linear solver that's compatible with ForwardDiff makes the FD case work:
linear_solver(A, x) = (Matrix(A) \ x, (solved = true,))
implicit = ImplicitFunction(dumb_identity, zero_gradient, linear_solver);

Zygote still fails but I suspect that's because Zygote.jacobian mutates and is tripping Zygote's second differentiation. I have run into this issue in the past and partially avoided it by defining a version of jacobian that's not mutating. Perhaps using AbstractDifferentiation's implementation would be better here. Anyways, I will leave the rest of it to you :)

Changing this line

Seems easy enough to fix in the source code, should we?

Seems easy enough to fix in the source code, should we?

Let's

Random thought: the fact that we need a dual-compatible linear solver means we still autodiff through the iterations of the solver. Is it possible to avoid that altogether for second-order?

In theory we could. That would require defining the linear solver as an implicit function and using ForwardDiffChainRules on that. We would need to think of a good way to make this work for direct and iterative linear solvers.

That would require defining the linear solver as an implicit function and using ForwardDiffChainRules on that.

My thought was actually to differentiate the implicit function theorem a second time, like this.

I believe what the derivations in this link are doing is going to be computationally identical to making our linear solver an implicit function and letting ImplicitDifferentiation automate the rest for us. They just defined the higher order rule manually but then it gets ugly with multiple inputs and outputs, Hessian rules for functions, etc. We have a nice abstraction which can be nested, let's take advantage of that.

what the derivations in this link are doing is going to be computationally identical to making our linear solver an implicit function

I believe you're right. Although I think the SciML solvers from https://github.com/SciML/LinearSolve.jl are already differentiable with a similar implicit machinery, it can't hurt to roll out our own simpler version

I recall you tried LinearSolve before but didn't end up using it because it was still not mature enough. Maybe we can revisit it or roll our own, shouldn't be too hard for simple solvers.

I don't think we need that many solvers so direct and GMRES should be enough.

I recall you tried LinearSolve before but didn't end up using it because it was still not mature enough

It should definitely be more mature now but my main beef is that it has a truckload of dependencies, which cannot be made conditional until Julia 1.9
I recall you tried LinearSolve before but didn't end up using it because it was still not mature enough

Now (in main), you can pass DirectLinearSolver() as the linear_solver in the implicit function to do second order differentiation. For the more general case of making the linear solver an implicit function, I think we should open another issue.

See #77

Closing in favor of #77


global is not defined

I'm getting the following error:

My source:
import {StompSessionProvider} from "react-stomp-hooks";

// ...

<StompSessionProvider
    url={"https://stream.elite12.de/api/sock"}
    debug={(str) => {
        console.log(str);
    }}>
    <Router>
        <Box sx={{display: 'flex', width: '100%', height: '100%'}}>
            <NavigationBar/>
            <Box
                component="main"
                sx={{
                    flexGrow: 1,
                    p: {md: 3},
                    // width: {sm: `calc(100% - ${drawerWidth}px)`},
                    width: '100%',
                    height: '100%',
                    backgroundColor: (theme: Theme) => theme.palette.mode === 'dark' ? theme.palette.background.paper : '#f5f5f5'
                }}>
                <Toolbar/>
                <PageContainer>
                    <Suspense fallback={
Loading...
}>
                        <MainPage/>
                    </Suspense>
                </PageContainer>
            </Box>
        </Box>
    </Router>
</StompSessionProvider>

I've tried manually adding the sockjs-client dependency, but it made no difference. Any ideas?

Hello!
Please take a look at this issue: https://github.com/sockjs/sockjs-client/issues/439
This is not an issue with react-stomp-hooks itself, and likely connected to your build setup.

Same error. I am not using sockjs; I get the same error without any config.

I have just released version 3.0.0, which includes a workaround for this issue.


[BUG]: Security vulnerability

How are you running AnythingLLM?
Docker (local)
What happened?
I've reported 2 vulnerabilities on huntr.com
Please have a look and validate the same.

https://huntr.com/bounties/f786481c-5837-40ca-b830-6f327a47d9da
https://huntr.com/bounties/8ec14991-ee35-493d-a8d3-21a1cfd57869

Are there known steps to reproduce?
No response

Please do not make a bug issue for us to just check the Huntr bug bounty. This is considered spam. We check it at least once a month and will be assessed and triaged then. The Huntr team emails us about the reports, so we do not need any other reminder or notification


Dumpstate can contain warnings

Original report by me.

The tool cannot parse a dumpstate file with a warning on a first line.

Fixed with #278


Add no violations message

Description
Adds a message at the end of the output that tells that no violation has been detected in the code.
Contributes to fix #176
Type of change
New feature (non-breaking change which adds functionality)

Can you please fix coding standard errors? To do it you can launch:
./bin/php-cs-fixer fix  -v

And commit files :)

@AlessandroMinoccheri sorry, I missed the validation fail. Fixed and pushed :)

Codecov Report

Merging #205 (24cd6a0) into main (54912c9) will decrease coverage by 0.56%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #205      +/-   ##
============================================
- Coverage     92.89%   92.32%   -0.57%
- Complexity      278      293      +15
============================================
  Files            50       51       +1
  Lines           704      756      +52
============================================
+ Hits            654      698      +44
- Misses           50       58       +8

Impacted Files
Coverage Δ

src/CLI/Check.php
84.28% <100.00%> (+0.70%)
:arrow_up:

src/Analyzer/FileVisitor.php
87.50% <0.00%> (-4.81%)
:arrow_down:

src/Analyzer/PatternString.php
100.00% <0.00%> (ø)

src/CLI/Command/Init.php
85.71% <0.00%> (ø)

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 54912c9...24cd6a0. Read the comment docs.

@mloru what do you think about adding this message only with verbose mode?
Or is it better to see this message every time?

@AlessandroMinoccheri I wanted to add it because I prefer to have a clear feeback from the tool in any case (both when no problems have been detected and when there are violations). This way, when you use it in a script with other static analyzers (or in a GitHub action) you can easily spot problems by scrolling the output, without having to read it carefully. For the same reason I've set the color of the message to green.
Of course, this is just my opinion: I'm fairly to static analysis tools (and to OSS contributions too) :)

ok, let's try to display it always now.
Thanks @mloru


feat: show user input array rather than first last in log list

You just merged another PR with same title:
https://github.com/Microsoft/ConversationLearner-UI/pull/1072
Doesn't make sense to be the same.
More like fix: consolidate dialog sampling functions

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Windows: Remove linkmode internal hack

Signed-off-by: John Howard<EMAIL_ADDRESS>@jfrazelle
@akavel has fixed rsrc to support building .syso files which are multi-architecture. Hence there's no need for the hack to force linkmode internal anymore following the upgrade to golang 1.5.x. This change now builds both architectures of the Windows resource binary using a golang build tag so that the right resource gets picked up by the linker.
Verified locally that both 32 and 64-bit cross-build binaries work as expected.

gccgo errors unrelated, but restarted.

Awesome!
On Friday, January 15, 2016, John Howard (Microsoft) <
<EMAIL_ADDRESS>wrote:

gccgo errors unrelated, but restarted.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/19340#issuecomment-172056259.

LGTM

thanks for remembering this :)
On Fri, Jan 15, 2016 at 11:27 AM, Jessie Frazelle<EMAIL_ADDRESS>wrote:

Awesome!
On Friday, January 15, 2016, John Howard (Microsoft) <
<EMAIL_ADDRESS>wrote:

gccgo errors unrelated, but restarted.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/19340#issuecomment-172056259.

LGTM


Update CSV URL links

Add Source Code link
Run make bundle that add the default channel due to MR #13.

/lgtm


Dapjs

This adds dapjs package and C++ stuff for building node extensions in Travis
Let's wait until ready

The travis changes has been merged from hf2 branch, so closing this


Sanitize intents in BrowserActivity

Task/Issue URL: https://github.com/duckduckgo/Android/issues/953
Tech Design URL:
CC:
Description:
This issue happened because every time an intent.getX (X being string, bool, etc) was called, internally it would eventually call unparcel() on BaseBundle, and if there is a class that was passed somewhere on the intent that duckduckgo can't unserialize (either by Serializable or Parcelable) it would throw an exception and close the app. One thing to note is that I tracked all current calls of where the app received intents that were not under the app control, and it seems that this point is in BrowserActivity in onNewIntent. So before any call could be made to any intent getSomething call I called sanitize, which is the preferred design that duckduckgo team mentioned on the original issue URL.
I think it seems safe but may require further tests since the app is quite big and there may be corner cases, one design issue though is that every new addition to the app that handle intents would have to be checked (say if for some reason another Activity that handles outside intents would be added, someone will need to remember to add sanitize() in there). If you guys want extra control and futureproofing then maybe creating an extension method that gets extras and uses generics. So instead of using getBoolean, getString, getShort we could create a getSafe with generics and inside the method handle each case. This seems safer but it would require to refactor the entire app, but it could be enforced on future development to only use this extension method. Idk what's the best solution, it would be interesting to hear what you guys think about it.
Steps to test this PR:

Create another application that sends a bundle with a serializable or parcelable class. On the original Issue URL there's a code snippet that shows this https://github.com/duckduckgo/Android/issues/953#issuecomment-712151654
Send it to duckduckgo.

Internal references:
Software Engineering Expectations
Technical Design Template

Thanks, I will try to take a look as soon as we have some time. Thanks for the contribution.


New optimizers fail to load CUDA installed through conda

System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04 (WSL)
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.11
Python version: 3.9
Bazel version (if compiling from source): N/A
GPU model and memory: RTX 2080 Ti
Exact command to reproduce:

Create a new environment, following the official installation instructions from here https://www.tensorflow.org/install/pip#linux:

conda install -c conda-forge cudatoolkit=11.2 cudnn=8.1.0
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CONDA_PREFIX/lib/
pip install tensorflow

Run the beginner MNIST tutorial (or any other tutorial that calls fit) from here https://keras.io/examples/vision/mnist_convnet/

Describe the problem.
An error is raised:
libdevice not found at ./libdevice.10.bc

Note that if you switch to using the legacy optimizers, by switching this line
model.compile(loss="categorical_crossentropy", optimizer="adam", metrics=["accuracy"])

to this
model.compile(loss="categorical_crossentropy", optimizer=keras.optimizers.legacy.Adam(), metrics=["accuracy"])

then the example runs successfully.
Describe the current behavior.
An error occurs when running the example.
Describe the expected behavior.
The example should run without error, as it does when using the legacy optimizers.

Do you want to contribute a PR? (yes/no): no

Standalone code to reproduce the issue.
https://keras.io/examples/vision/mnist_convnet/
Source code / logs.
Full stack trace of the error:
    File ".../tmp.py", line 47, in <module>
      model.fit(x_train, y_train, batch_size=batch_size, epochs=epochs, validation_split=0.1)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/utils/traceback_utils.py", line 65, in error_handler
      return fn(*args, **kwargs)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/engine/training.py", line 1650, in fit
      tmp_logs = self.train_function(iterator)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/engine/training.py", line 1249, in train_function
      return step_function(self, iterator)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/engine/training.py", line 1233, in step_function
      outputs = model.distribute_strategy.run(run_step, args=(data,))
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/engine/training.py", line 1222, in run_step
      outputs = model.train_step(data)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/engine/training.py", line 1027, in train_step
      self.optimizer.minimize(loss, self.trainable_variables, tape=tape)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/optimizers/optimizer_experimental/optimizer.py", line 527, in minimize
      self.apply_gradients(grads_and_vars)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/optimizers/optimizer_experimental/optimizer.py", line 1140, in apply_gradients
      return super().apply_gradients(grads_and_vars, name=name)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/optimizers/optimizer_experimental/optimizer.py", line 634, in apply_gradients
      iteration = self._internal_apply_gradients(grads_and_vars)
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/optimizers/optimizer_experimental/optimizer.py", line 1166, in _internal_apply_gradients
      return tf.__internal__.distribute.interim.maybe_merge_call(
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/optimizers/optimizer_experimental/optimizer.py", line 1216, in _distributed_apply_gradients_fn
      distribution.extended.update(
    File "/home/drasmuss/mambaforge/envs/tmp2/lib/python3.9/site-packages/keras/optimizers/optimizer_experimental/optimizer.py", line 1211, in apply_grad_to_update_var
      return self._update_step_xla(grad, var, id(self._var_key(var)))
Node: 'StatefulPartitionedCall_4'
libdevice not found at ./libdevice.10.bc
         [[{{node StatefulPartitionedCall_4}}]] [Op:__inference_train_function_1026]

Likely related to:

https://github.com/tensorflow/tensorflow/issues/56927
https://github.com/tensorflow/tensorflow/issues/59013

@gowthamkpr,
I tried to execute the mentioned code in two different ways as below, but couldn't find any issue. Kindly find the gist of it here.
model.compile(loss=tf.losses.mse, optimizer=tf.keras.optimizers.SGD())
and
model.compile(loss=tf.losses.mse, optimizer=tf.keras.optimizers.legacy.SGD())

I have been encountering the same issue as @drasmuss with the non legacy opitmisers: "adam" and "rmsprop". No errors with the SGD optimizer though. Below is the error from trying to run my script with the "rmsprop" optimiser.
Node: 'StatefulPartitionedCall_8'
libdevice not found at ./libdevice.10.bc
[[{{node StatefulPartitionedCall_8}}]] [Op:__inference_train_function_1102]

Hi,
adding me me too here - hoping it adds value and not just noise :)
I'm also seeing this issue in the following setup:

CUDA 11.7 installed on SLES from RPM packages (via the official Nvidia rep)
cuDNN 8.5.0 installed from cudnn-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz
Tensorflow 2.11 installed via pip

This was not an issue with Tensorflow 2.10. With 2.11, I now get:
libdevice not found at ./libdevice.10.bc

Just checked, and it produces the same error as before. Here are the reproduction steps (I updated the installation instructions to match the changes for TF 2.12 here https://www.tensorflow.org/install/pip#linux):
# these are the standard TF installation steps, copied here for clarity
conda install -c conda-forge cudatoolkit=11.8.0
python3 -m pip install nvidia-cudnn-cu11==<IP_ADDRESS> tensorflow==2.12.*
mkdir -p $CONDA_PREFIX/etc/conda/activate.d
echo 'CUDNN_PATH=$(dirname $(python -c "import nvidia.cudnn;print(nvidia.cudnn.__file__)"))' >> $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh
echo 'export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CONDA_PREFIX/lib/:$CUDNN_PATH/lib' >> $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh
source $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh

# calling model.fit triggers the same error as before
python -c "import tensorflow as tf; model = tf.keras.models.Sequential([tf.keras.layers.Dense(10, input_shape=(10,))]); model.compile(loss=tf.losses.mse); model.fit(tf.ones((32, 10)), tf.ones((32, 10)))"

Here is the full error log:
2023-04-26 12:33:40.887265: I tensorflow/core/util/port.cc:110] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2023-04-26 12:33:40.912502: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-04-26 12:33:41.303191: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2023-04-26 12:33:41.877110: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:41.892418: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:41.892768: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:41.894668: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:41.894937: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:41.895171: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:42.496930: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:42.497198: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:42.497225: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1722] Could not identify NUMA node of platform GPU id 0, defaulting to 0.  Your kernel may not have been built with NUMA support.
2023-04-26 12:33:42.497474: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:982] could not open file to read NUMA node: /sys/bus/pci/devices/0000:01:00.0/numa_node
Your kernel may have been built without NUMA support.
2023-04-26 12:33:42.497531: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1635] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 8859 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 2080 Ti, pci bus id: 0000:01:00.0, compute capability: 7.5
2023-04-26 12:33:43.559322: I tensorflow/compiler/xla/service/service.cc:169] XLA service 0x7fad47d31b00 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2023-04-26 12:33:43.559369: I tensorflow/compiler/xla/service/service.cc:177]   StreamExecutor device (0): NVIDIA GeForce RTX 2080 Ti, Compute Capability 7.5
2023-04-26 12:33:43.562463: I tensorflow/compiler/mlir/tensorflow/utils/dump_mlir_util.cc:269] disabling MLIR crash reproducer, set env var `MLIR_CRASH_REPRODUCER_DIRECTORY` to enable.
2023-04-26 12:33:43.668017: I tensorflow/compiler/xla/stream_executor/cuda/cuda_dnn.cc:424] Loaded cuDNN version 8600
2023-04-26 12:33:43.673970: W tensorflow/compiler/xla/service/gpu/llvm_gpu_backend/gpu_backend_lib.cc:530] Can't find libdevice directory ${CUDA_DIR}/nvvm/libdevice. This may result in compilation or runtime failures, if the program we try to run uses routines from libdevice.
Searched for CUDA in the following directories:
  ./cuda_sdk_lib
  /usr/local/cuda-11.8
  /usr/local/cuda
  .
You can choose the search directory by setting xla_gpu_cuda_data_dir in HloModule's DebugOptions.  For most apps, setting the environment variable XLA_FLAGS=--xla_gpu_cuda_data_dir=/path/to/cuda will work.
2023-04-26 12:33:43.674114: W tensorflow/compiler/xla/service/gpu/llvm_gpu_backend/gpu_backend_lib.cc:274] libdevice is required by this HLO module but was not found at ./libdevice.10.bc
2023-04-26 12:33:43.674287: W tensorflow/core/framework/op_kernel.cc:1830] OP_REQUIRES failed at xla_ops.cc:362 : INTERNAL: libdevice not found at ./libdevice.10.bc
2023-04-26 12:33:43.674323: I tensorflow/core/common_runtime/executor.cc:1197] [/job:localhost/replica:0/task:0/device:GPU:0] (DEBUG INFO) Executor start aborting (this does not indicate an error and you can ignore this message): INTERNAL: libdevice not found at ./libdevice.10.bc
         [[{{node StatefulPartitionedCall_1}}]]
2023-04-26 12:33:43.682794: W tensorflow/compiler/xla/service/gpu/llvm_gpu_backend/gpu_backend_lib.cc:274] libdevice is required by this HLO module but was not found at ./libdevice.10.bc
2023-04-26 12:33:43.682947: W tensorflow/core/framework/op_kernel.cc:1830] OP_REQUIRES failed at xla_ops.cc:362 : INTERNAL: libdevice not found at ./libdevice.10.bc
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File ".../lib/python3.9/site-packages/keras/utils/traceback_utils.py", line 70, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File ".../lib/python3.9/site-packages/tensorflow/python/eager/execute.py", line 52, in quick_execute
    tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
tensorflow.python.framework.errors_impl.InternalError: Graph execution error:

Detected at node 'StatefulPartitionedCall_1' defined at (most recent call last):
    File "<string>", line 1, in <module>
    File ".../lib/python3.9/site-packages/keras/utils/traceback_utils.py", line 65, in error_handler
      return fn(*args, **kwargs)
    File ".../lib/python3.9/site-packages/keras/engine/training.py", line 1685, in fit
      tmp_logs = self.train_function(iterator)
    File ".../lib/python3.9/site-packages/keras/engine/training.py", line 1284, in train_function
      return step_function(self, iterator)
    File ".../lib/python3.9/site-packages/keras/engine/training.py", line 1268, in step_function
      outputs = model.distribute_strategy.run(run_step, args=(data,))
    File ".../lib/python3.9/site-packages/keras/engine/training.py", line 1249, in run_step
      outputs = model.train_step(data)
    File ".../lib/python3.9/site-packages/keras/engine/training.py", line 1054, in train_step
      self.optimizer.minimize(loss, self.trainable_variables, tape=tape)
    File ".../lib/python3.9/site-packages/keras/optimizers/optimizer.py", line 543, in minimize
      self.apply_gradients(grads_and_vars)
    File ".../lib/python3.9/site-packages/keras/optimizers/optimizer.py", line 1174, in apply_gradients
      return super().apply_gradients(grads_and_vars, name=name)
    File ".../lib/python3.9/site-packages/keras/optimizers/optimizer.py", line 650, in apply_gradients
      iteration = self._internal_apply_gradients(grads_and_vars)
    File ".../lib/python3.9/site-packages/keras/optimizers/optimizer.py", line 1200, in _internal_apply_gradients
      return tf.__internal__.distribute.interim.maybe_merge_call(
    File ".../lib/python3.9/site-packages/keras/optimizers/optimizer.py", line 1250, in _distributed_apply_gradients_fn
      distribution.extended.update(
    File ".../lib/python3.9/site-packages/keras/optimizers/optimizer.py", line 1245, in apply_grad_to_update_var
      return self._update_step_xla(grad, var, id(self._var_key(var)))
Node: 'StatefulPartitionedCall_1'
libdevice not found at ./libdevice.10.bc
         [[{{node StatefulPartitionedCall_1}}]] [Op:__inference_train_function_401]

It's possible that you have CUDA installed elsewhere on your system (not through conda), and tensorflow is finding libdevice in that installation.

Hi @drasmuss ,
Could you please try the following commands and let us know whether it fixes the error.
# Install NVCC
conda install -c nvidia cuda-nvcc=11.3.58
# Configure the XLA cuda directory
mkdir -p $CONDA_PREFIX/etc/conda/activate.d
printf 'export XLA_FLAGS=--xla_gpu_cuda_data_dir=$CONDA_PREFIX/lib/\n' >> $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh
source $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh
# Copy libdevice file to the required path
mkdir -p $CONDA_PREFIX/lib/nvvm/libdevice
cp $CONDA_PREFIX/lib/libdevice.10.bc $CONDA_PREFIX/lib/nvvm/libdevice/

Thanks!

Yes, that makes the problem go away, although I would hesitate to call it a solution as that's quite a cumbersome process to repeat every time we create a new environment, and a definite downgrade in user experience compared to TF <= 2.10.

@chenmoneygithub do you know if this is a known issue?

I ran into this same issue with WSL2 and the proposed fix did not initially work for me; however, it did eventually work if I rebooted my computer after updating the $CONDA_PREFIX/etc/conda/activate.d/env_vars.sh  file.
I had similar issues with the published pip install instructions for Tensorflow (https://www.tensorflow.org/install/pip#step-by-step_instructions) and had to reboot my system between several of the steps.
Hopefully this helps anyone running into this issue on WSL2


Failed to mount component: template or render function not defined.  (found in root instance)

Hi guys, I've got a bit of a familiar problem, keeping getting the error:
[Vue warn]: Failed to mount component: template or render function not defined.  (found in root instance)
Here's my webpack config:
var config_array = [] //Provide an array of configs for webpack, for multiple output paths
var webpack_config = { //Global webpack config
	devtool: 'source-map',
	plugins: [
		new webpack.ProvidePlugin({
			$: "jquery",
			jQuery: "jquery",
			"window.jQuery": "jquery"
		})
	],
	module: {
		loaders: [{
			loader: 'babel-loader',
			test: /\.js$/,
			exclude: path.join(__dirname, "./../../node_modules"),
			query: {
				presets: ['es2015'],
				plugins: ['transform-runtime'],
			}
		}]
	},
	resolve: {
		alias: {'vue$': "./../../node_modules/vue/dist/vue.js"}
	},
	debug: true
}

I'm passing an array of configs so that each individual page 'controller' file can be transpiled with all of its depenencies, and load on their respective pages. Webpack bundles successfully every time but I can no longer seem to use el: '#app' to mount the root instance.
Truth be told also, I am not sure whether I am running the standalone build or not, since nothing changes if I remove the resolve.
For the purpose of testing, the vue instance I am working with is as simple as can be:
var vm = new Vue({
  el: '#app',
  mounted: function() {
    console.log('mounted')
  }
})

Some digging showed that I can require a html file with webpack and bind it to a template key in the instance, or use the render function. Unfortunately, this is not easily possible in my case since all the template files are .cfm files and many I am working with still require coldfusion to render some content. I understand it may be that I have to transfer all my root instances into .vue templates, but was hoping there was still a way Vue could simply bind to the existing DOM, as it does without using webpack.
Also, switching to using require('vue/dist/vue') removes this error, but as soon as I add a Vuex store, it brings some weird errors about it being undefined, despite being able to output my store object in the console, and I know others have had issues importing Vue this way.
Please let me know if there's any more code or context I need to supply, the old brain is a bit scattered after so much googling and I may have missed something obvious -__-

Eurgh, seems the excessive googling really did fry my brain. Seeing this in the morning I noticed in my webpack config:
module: {
Which should be modules: {
Babel wasn't being used at all, hence why I was still using the old require() method to fudge my way through. I'll update all my code (and I'm switching to Webpack 2 for good measure), but I'll just go ahead and close this issue too.

Sorry, I'm a little confused. Are you even using Vueify? Maybe you actually wanted to open an issue in vue-loader, because it seems you're not using browserify at all.
But it doesn't really seem like a bug at all, but some problem with your exact use case. It may be your best bet to ask on the forums or in the gitter chat.


(Willing to PR) Add snapshot testing, linters, and CI?

Hi thanks for the great library and your (i.e. @3b1b's) great math videos! Given its popularity (50k stars), it would be great to add a bit of software engineering. For example:

Linters: Catch common errors, bad practices, etc. Given that the repo has type annotations, type errors can also be caught.
Snapshot testing: In short, take a "snapshot" (say, mp4 files) for the example scenes in the first run. Then, for each commit in the future, re-generate the snapshots and compare them. If the snapshots are identical, we are pretty sure the code change does not break things. The technique is often seen in frontend development.
CI (continuous integration): Run all the things above automatically on each commit to GitHub, as well as each PR.

If you want, I can provide examples of these software engineering techniques in real repositories as well :)

Ah I see, the community fork already has these :)


openmp support

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Added openmp support

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance.

@conda-forge/core I would like to merge this but I received an error from conda-forge-linter.
How should I proceed?
Thanks
Giovanni

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

Sorry I misunderstood the message... "I tried to re-render for you, but it looks like there was nothing to do" means that there is no change. I will merge this.
Thanks @isuruf for finding the mistake in openmp.


contracts: Deprecate random interface

This PR deprecates the random API provided by pallet-contracts. This means no new codes nor contracts can be deployed using this API. The functionality was already removed from ink! and solang:
https://github.com/paritytech/ink/pull/1442
https://github.com/hyperledger/solang/pull/1041
Motivation
Randomess shouldn't be part of the core API of pallet-contracts.  Reason is that not every chain might be able to provide secure (unpredictable) random numbers. By having it in the core API would force them to either provide an insecure implementation or not use pallet-contracts at all. Instead, chains that can provide secure randomness should expose this as a chain extension or via a oracle contract.
Details
This introduces a new attribute #[deprecated] attribute for our define_env macro. It makes the annotated API in the following way:
https://github.com/paritytech/substrate/blob/9981e1fc8e4615d77143d876b149c179fa67e28a/frame/contracts/src/lib.rs#L219-L227
It is important to understand that deprecated is different from just being replaced by a new version. If there is a new API for a new version we do not deprecate an API necessarily. The old versions usually stay fully functional. Deprecated on the other hand has the implications mentioned above. We only do that if we plan to eventually drop the API in question. This is the case if the  API:

is considered unsafe (as in this case)
presents a big maintenance burden
is not used anyone anymore
is rendered nonsensical by changes to the logic of the pallet

This is why we also removed all other mentions of the word deprecated in other contexts like when a new version is available.
In addition to the random API we also deprecate functions related to the no longer present state rent (replaced by state deposit). This deprecation fulfils point 4 and probably 3.

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2299257

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2299354

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2299400

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2299402

How about marking with #[deprecated] both versions of set_rent_allowance() ?

Yes! I missed this one. Deprecated it. I also regrouped so all the deprecated storage rent functions are next to each other.

bot merge

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/substrate-developer-newsletter-february-2023-notable-updates-for-frame-devs-new-deep-dives-released-calling-builders-to-apply-to-rfps-and-bounties/2137/1


Sorting and filtering additional UI

There will need to be some updates to the search page, to refine the filters and the columns that we display, etc.  But a basic set of fields/filters are there, and all of the big pieces of code to support the functionality (front/back) are in place.
SEARCH PAGE MOCK UP.docx
Review #1252 as well to ensure they work together.

[ ] remove the current search page once the new myrecords table sort/filter/search tables are built.

@micheal-w-wells  i uploaded a search page mock up here showing my vision of the fields we will need.  Please read the note at the top of the word doc re the public search page versus the user log in search page.  Also if you have other ideas or think this is duplicating metabase at all, let's chat.

We've come so far on this broadly titled ticket - would be nice to close it and call it 'v1'.

@micheal-w-wells once i see your page in dev, i will close this one and make a v2 for what is left.


v3.0.0 is brewing

Hi peeps,
Just informing that I am currently working on the next release of this directive, thus, I won't touch v2.x.x much. Sorry for this.
Meanwhile have some fun with other directives I wrote:

http://github.com/isteven/angular-route-rage - Stop polluting your $scope/controller! Use $routeParams directly in your view using this directive.
http://github.com/isteven/angular-omni-bar - Just a standalone, multi-purpose progress bar.

Cheers :)

@mohnishsingh , please open a new issue.

@mohnishsingh , please open a new issue.


Update: README.md needs to be updated

The README needs to be updated with latest command-line usage.

This is in the works in the docs directory. I'll copy it in my next commit.

Issues are like todo list items that you leave open until the issue is addressed :)

It is done :)


contentServer.br: boolean (koa-static) behaves unexpectfully

Based on the documentation which refers that

... It supports all the options of koa-static and some extra options...

contentServer.br: true gives an error. See photo below.

koa-static internally uses koa-send to serve files. So all options mainly come from the koa-send package. If you see the options of koa-send, it has an option named brotli but in koa-static it is mistakenly stated as br. So please use brotli option instead. Anyway, thanks for reporting bugs :D


500 with cachebydevice on - NGINX fastcgi

Hi,
Clean install CentOS 7 with centminmod php7 and Opencart 2.3 and latest Journal (nothing else)
I'm getting 500 if I turn cachebydevice on. Without Journal and with cachebydevice off, everething cache is working.
In server log I see following:
2016/10/20 18:49:46 [error] 4280#4280: 164 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Cannot redeclare V2PageCache::$cachebydevice in /usr/local/nginx/html/system/library/v2pagecache.php on line 36" while reading response header from upstream, client: 31.130.147., server: mysite.com, request: "GET /admin/index.php?route=extension/module/v2pagecache&token=snnpf6cDnDOOZSIDWW70AejydEG3MCBQ HTTP/1.1", upstream: "fastcgi://<IP_ADDRESS>:9000", host: "91.107.108.*"

Note the comment in the source:
// make sure only one of the three lines below is uncommented
Likely that you've got more than one of them uncommented.
Also, the Journal theme has it's own pagecache.  I don't recommend using our pagecache with the Journal theme, as they can clash.

You are 100% correct!
I had both on:
private $cachebydevice=false;
private $cachebydevice='mobiledetect';
Once I changed to
//private $cachebydevice=false;
private $cachebydevice='mobiledetect';
Everything is working.
Thank you!


Remove SAST from the nightly CI workflow

Summary
Don't run the reusable SAST workflow in the nightly workflow. The motivation being that, with pinned Action versions and a SAST scan on all pushes to the main branch anyway, analyzing the main branch nightly does not add any value.
Additionally, the nightly run can cause interference with CodeQL because it expects an analysis coming from the nightly workflow on the Pull Request branch if the base happened to be the subject of a nightly scan. Examples:

https://github.com/ericcornelissen/eslint-plugin-top/pull/25/checks?check_run_id=8577048788
https://github.com/ericcornelissen/eslint-plugin-top/pull/27/checks?check_run_id=8588905309

Superseded by #34


Switch from CircleCI to GitHub Actions

Relates #158 (macOS will be added to this next, so we don't need to deal with so many CI providers). For obvious reasons, the CircleCI job will either not start or fail.

This change is

See https://github.com/jamiesnape/drake-external-examples/runs/488134920.

@jwnimmer-tri for review since @EricCousineau-TRI is away.


Blink the calendar view

Hello,
When I am adding a material-calendarview in the relativelayout, it is working fine but when removed from the relativelayout or setvisibility to gone. Then the calendarview blink with the selected view color.
Please tell, what I need to do? I am waiting for your response.
Thanks,
Vivek Kumar

Hey @VivekKumarApps, I'm not able to replicate this. What device(s) and version(s) of Android do you see this on? And what customization options do you have set on the calendar (decorators, etc)?


adding banners

i am not able to add or edit banners, is there any anyone who can help me ?

@zam00921 Everyone is a volunteer here. So no need to write twice your request. At most, you risk people just ignoring because they'll consider it's harassment.
https://ph7cms.com/doc/en/how-to-change-promo-texts-on-homepage
Maybe if you'd explain what doesn't work then we'll be better able to help !

@polynamaude sir actually i want to add banners but i dont know how can i add banners.

Login to your admin area and click the "Settings" menu. Than click the "Ad Banners" link.  It is self explanatory after that with examples.

i am a bit confuse about the image path that how to write a image path in banners section

i am a bit confuse about the image path that how to write a image path in banners section

I don't understand a word about what you are saying here...

i am a bit confuse about the image path that how to write a image path in banners section

@zam00921 Maybe you need to learn more about web development before going on with this project.

I haven't used this feature yet so can't confirm if it works but here is what an example html code would look like:

You could change the href to read where your image is located if you want to preview it or make it link to the actual banner ad website.

btana hai tu bta zyada shoka na ho war jani diya ani diya Thanks for your help

@zam00921 As I can see you lot of experience on Github and seem to be a really experienced user. So for sure we'll help you with every little thing you may have. Do you also need help installing Windows?


options.deps in false by default

Probably options.deps should be false by default.

The plugin follows the convention one module per file. So it is intended to create a 'config' module without dependencies.
This change would also break to much existing setups that use grunt-ng-constant.


Exception when run Spatial Understanding query

Overview
I have a bug when I run a Spatial Understanding query on HoloLens. I use object placement solver code from this site: https://docs.microsoft.com/en-us/windows/mixed-reality/case-study-expanding-the-spatial-mapping-capabilities-of-hololens and example code from HoloLens toolkit.
Actual Behavior
I get the message: Exception thrown at 0x52D58C2E (SpatialUnderstanding.dll) in Spatial Understanding.exe: 0xC0000005: Access violation reading location 0x00000000.
I use Unity 2018.2.0b8 and previous HoloLens Toolkit version.

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


app.npm undefined

var npm = require('base-npm');
var Base = require('base');

var app = new Base();

app.use(npm());

console.log(app.npm); // undefined

But;
var bower = require('base-bower');
var Base = require('base');

var app = new Base();

app.use(bower());

console.log(app.bower);

konsole output;
{ [Function: bower]
  install: [Function: install],
  latest: [Function],
  save: [Function],
  saveDev: [Function] }

what's wrong?

Take a look at the usage on base-npm-prompt. I'll update the examples in the readme here and add that same message.
Basically, this plugin will only be registered on "applications". You can specify that app is an application by creating app like this:
var app = new Base({isApp: true});

@doowb
it's ok. thanks

To add to what @doowb said, plugins can (optionally) automatically propagate down child instances. The pattern of using isApp is a pattern that we use on some plugins to allow them to be "smart" about what instances they are registered on.


feat: introduce types.ftl.go to register sumtypes, which fixes encoding in unit tests

Fixes https://github.com/TBD54566975/ftl/issues/1577
This change introduces a new generated file types.ftl.go in the user-defined package itself to make sure sumtype registrations get called when running unit tests.
Notes:

This change also includes a subpackage subpackage in the test data that is not yet unit tested. Unit tests should be added (identical to the parent package's unit tests) after https://github.com/TBD54566975/ftl/issues/1903 is resolved. Some work will also need to be done to extend the types.ftl.go generation to working on subpackages.
This works by extending the existing logic operating on mainModuleContext, which means that code now generates not only just the literal main package, but also the conceptual main package's additional artifacts. I couldn't come up with a name that would be better, so it's left as-is in this PR, but please let me know if you think of something better.

Awesome. Have you played with it? What are the ergonomics like as you're updating the code/modifying the sum types?

It's been unintrusive, so good! Though I haven't tried it out in an IDE. Hopefully it works with everyone's workflows...


SSH using macOS Terminal asks for password

I'm quite new to this and I want to forward my port to a static url using sish, but it asks for password at si.sh
I've tried using both Docker method and running on my local machine, but I don't know the password, I've tried generating my own ED25519 keypair, but in sish terminal it says x509: decryption password incorrect, so may I ask for tutorial about passwords?

Thanks.

same problem

Hey @mrmc-mc,
Unfortunately, the instance running at ssi.sh is no longer public. Due to people abusing the service I decided to shut it down.
I removed the demo info from the README in this commit. Is there another reference I need to cleanup?
Best,


Document advantage of CCXT-REST over CCXT

Hi and thanks for CCXT-REST!
I am having trouble understanding what advantage CCXT-REST has over CCXT?
I understood that CCXT already provided the unified API to interact with the exchanges.
Would you be able to explain how one might have advantage using CCXT-REST?
Thank you!

Hi,
If you are not using nodejs, python or php, then ccxt-rest will allow you to use ccxt even with a different language (i.e. Java, C#, Rust, Go, etc).
Also, we have users that’s mainly on NodeJS but are still using CCXT-REST, because it allows them to cluster the integration to the exchanges, instead of just clustering their whole app.
Cheers,
Franz

Ok excellent, this would work well because I would like to use the language I already know, newLISP!
One final request Franz, would you be able to explain a bit more in detail what you mean when you say ccxt-rest allows you to "cluster the integration to the exchanges, instead of just clustering their whole app"?
Thank you very much again for this powerful software! :0)

how to use CCXT-REST in python?

@lfzCarlosC same way you use regular REST calls in python
Check this for example:
https://www.nylas.com/blog/use-python-requests-module-rest-apis/

just touching base but Im upgrading my monolith from a massive nodejs app -> to a nest-js microservice... now-> i can use this rest-api -> to make all my calls to the other endpoint. -> instead of having to write all my own functions I can send requests to a url


TDE for Azure SQL Managed Instance databases

Questions:

Is it possible to enable TDE for new SQL Managed Instance database as default?
Are there any ways to check if SQL Managed Instance database is TDE enabled?
Thanks

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

ID: a44a0e0d-f0a8-fe91-8ae5-a901e103f89e
Version Independent ID: 834b8bc9-d661-0204-9ece-1f370067ec96
Content: Transparent data encryption for Azure SQL Database and Data Warehouse
Content Source: articles/sql-database/transparent-data-encryption-azure-sql.md
Service: sql-database
GitHub Login: @aliceku
Microsoft Alias: aliceku

Hello, we are in the process to make TDE the default for managed instance databases, but it will take a couple of weeks to make it into production.
To check if a db is encrypted with TDE, run: sys.dm_database_encryption_keys

@aliceku Thank you for the information!

Hiya,
This still isn't the default, is it still on it's way into production?

Has this been addressed? If so, does PowerShell Az include a module to Set  / Get encryption status per database? This is a critical need.

Any news on making TDE enabled by default for all databases in Azure SQL Managed Instance?
From what I can see TDE is enabled on instance level but databases are not automatically encrypted.
It seem additional TSQL steps are required to enable encryption for each DB (very similar to on-prem SQL)
https://docs.microsoft.com/en-us/azure/azure-sql/database/transparent-data-encryption-tde-overview?tabs=azure-portal
According to your documentation 'For Azure SQL Managed Instance, TDE is enabled at the instance level and newly created databases'. This does not seem to be the case.


That is your work doitsujin :)

https://www.youtube.com/watch?v=x8xfGYzEJ7U
Danke, Mann ;) !!!

Hi,
here is the solution for the memory error:
https://robertsspaceindustries.com/spectrum/community/LUG/forum/149/thread/star-citizen-crashing-with-memory-allocation-error


L2 22

please check

Can one of the admins verify this patch?

Can one of the admins verify this patch?


make ciftify_recon_all usage (for surf transform) match ciftify_subject_fmri

right now MSMSulc functions for both, but they don't have similar user arguments.

they now use the same wording and settings parse


What type of update are you requesting?
A new version of an existing package
Current Package Identifier
DuckStudio.GitHubLabelsManager
Package Version
v1.4
Please describe the changes you would like to see
There is a new release (v1.4) available.
Download Page Url: https://github.com/DuckDuckStudio/GitHub-Labels-Manager/releases/tag/v1.4

Not duplicates.


Feature flag testing bridge code

Summary
We have several methods in the bridge crates that are intended for testing only. For example in MovementClient::new() this actually genning a random address and this should be renamed to MovementClient::new_for_test
This should be feature flagged as such
#[cfg(test)]
pub fn new_for_test() {}

Requirements

Feature flag the code, rename the method and improve the semantics everywhere where we have code intended for testing purposes only inside bridge/chains/ethereum/* and /bridge/chains/movement/*
All checks should pass

Here you mentioned changing new to new_for_test but new_for_test already exists. Not sure how to handle that case

There's already a function MovementClient::new_for_test. I added it to provide a way to spin up a local Movement network, which is not needed on the Eth side because Eth has Anvil.
MovementClient::new() might not be fully fleshed out, for example there are dummy values in the current implementation. But there needs to be a production, non-test function for generating a new MovementClient, right? Isn't that the purpose of MovementClient::new?
EthClient::new is called in production (non-test) in the CLI
From what I can tell, the use for MovementClient::new hasn't been written into the CLI yet. It will need to be, and at that point we'll need MovementClient::new for production use.
It appears to me that the way @0xPrimata is addressing this issue, by annotating MovementClient::new_for_test and other test functions as shown here is correct.


Use ProtocolUtils.isGeneric judge generic type

What is the purpose of the change
Only judge true isn't accurate
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #12876 (c0fcf15) into 3.2 (45405ff) will increase coverage by 0.73%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##                3.2   #12876       +/-   ##
=============================================
+ Coverage     68.77%   69.50%    +0.73%
+ Complexity      318        2      -316
=============================================
  Files          3657     1648     -2009
  Lines        170962    68371   -102591
  Branches      28310     9989    -18321
=============================================
- Hits         117573    47520    -70053
+ Misses        43258    16274    -26984
+ Partials      10131     4577     -5554

see 2043 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Restart Service does not Restart HA 0.38 or 0.38.1

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --0.38.1):
Python release (python3 --version):
Component/platform:
homeassistant/restart
Description of problem:
Select Domain > homeassistant
Select Service > restart
Press CALL SERVICE button
Bottom message says failed to call service homeassistant/restart
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
Config file untouched, this happens with the Hassbian Toybox image

1.
2.
3.

**Traceback (if applicable):**
```bash

Additional info:

Please try upgrading to 0.38.2 which we just released a few minutes ago, as it contains fixes for this bug.

Just updated to 0.38.2, and still the same, get the same Bottom message says failed to call service homeassistant/restart.

@DaveTiff Are you sure it's not actually just throwing that error and still restarting like was reported in #5931?

I can confirm that the problem persists in 0.38.2. I'm forcing the restart with systemd after waiting for the HASS and getting "unfinished sessions" afterwards...

I'm seeing the same issue. I have cleared browser cache. HA just fails after I run this from the GUI although the service still shows active. Waiting doesn't clear it up

I'm getting this message on 0.38.2 but it does in fact reload all of the components for me.

Upgraded to 0.38.3 and still have this issue.

Also confirm, still the same 0.38.3 with virgin config files,
Bottom message says failed to call service homeassistant/restart

I was having restart issues until I took out  bluetooth tracking from the config.  Works fine for me on 0.38.3

In my case (0.38.3), HA shows the message "failed to call service homeassistant/restart" but still restarts..

I have just found the same, get the failed message but it does restart

For me it's the same, Home Assistant restart but I keep getting the failed message on every restart.

Based on what I've seen, it has to do with timing. HASS is restarting so fast that it's not sending the 'I called that service" notifier to the front-end.

Just installed 0.38.4 and the now the restart from the GUI works as expected... Can anybody confirm?

Just installed 0.38.4, still getting failed message, but like 0.38.3, it does restart.
Also get a failed message when calling "Stop" but HA does stop

I think it's related to the following log-output:

17-02-22 21:00:49 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.

So the socket the frontend waiting for feedback is closed and that is reported as error. From my site, I see that message with .38.3 and .38.4, however the restart is done for both versions.

Not able to restart HASS via either the service or the new restart option on the config pane. config passes as valid.

...still not working on 0.39.1 . Worth mentioning that my setup is inside a Docker container. Moreover I don't think that HASS does silently restart in the background. I have a second tab open where I tailf the HASS startup procedure. Now after you hit restart via services in the GUI, the frontend doesn't lose connection as in you don't get the toast and after restarting via systemd, the streaming log clearly shows:
17-02-27 16:12:48 WARNING (Thread-9) [homeassistant.components.recorder] Ended unfinished session (id=2 from 2017-02-27 14:58:17.709288)
17-02-27 16:12:48 WARNING (Thread-9) [homeassistant.components.recorder] Found unfinished sessions

The only version where this did not occur (at least in my case) was 0.38.4...

I'm on 0.39.2 now and calling restart from the Configuration tab works, but calling the homeassistant.restart service doesn't restart anymore.

Restarting from the configuration panel on .39.2 works now. One thing that is annoying is that there is no visual confirmation that it has lost connection (as used to happen before .38, or when you do it via sudo systemctl restart home-assistant@homeassistant.service), which means there is no way to tell when its actually back up again.

...and now it works again on 0.39.3. You hit restart, you get the toast in the lower left corner, the log fills and no more unfinished sessions found...

 :-(
Version 0.41.0, no toast on the GUI and unfinished sessions found in the log after a systemd restart...

Ive completely given up using the admin panel at all, nothing seems to work right on it

Me too...
version 0.41

Just started with Home Assistant 0.41.0 and I have the same problem restart the service from the Chrome web page runnning on Windows 10.    The /home/homeassistant/.homeassistant/home-assistant.log
only has ONE line in it as follows:
17-04-06 11:11:02 WARNING (MainThread) [aiohttp.websocket] websocket connection is closing.
I can still reset the service while logged in as "pi"
sudo systemctl restart<EMAIL_ADDRESS>This works but it would be handy to get the web page working.  I now have to have another bash shell open just to perform these restarts.

I am getting this as well (0.42.4) with the same websocket error; however, if I try to attempt the systemctl restart command, it fails to load. If I try to sudo reboot after that, it hangs up and I have to cylce power to the pi3.

...works for me in 0.49.0. Running inside a Docker container...

Hi just installed and checked 0.49.1. It does restart but still get the message " failed to call service homeassistant/restart" in the black box bottom left of browser.

This is still an issue on 0.51.2 running Hassbian on Pi 3. Standard install, no funny business. Literally one of the first things I tried and it failed. Not clear if it works or not, because home-assistant.log gives no indication of status.

I've had this issue since the restart button was introduced.
If my log is clear of errors, I get the error message but HA will eventually restart. If I have errors (I have them everyday due to the ChromeCast issue), then the restart doesn't work and I have to kill HA. Currently on V0.56.2

I'm having the same issues with 0.57.3
It is worth to note that I installed it using the raspberry pi walkthrough on official site and this guide makes you launch it manually. At this point restarting worked great.
Ever since I set up a service for home assistant, the restart button behaves as described in this issue.

Still a problem on .60! All this button does is call "sudo systemctl start<EMAIL_ADDRESS>

I since I stopped using the built-in restart button and instead created an input_boolean that calls a sudo systemctl restart<EMAIL_ADDRESS>command. Works a treat...


Fix comparison of line IDs. There are not numbers.

Thanks for the code.
I have cherry picked the commit
https://github.com/tupinek/Map-Tube/commit/cc12bc58497d4fe2b4e64a49b6a04b86b870883b
Best Regards,
Mohammad S Anwar


Type Checking

[x] Check assignability for mapstore
[x] "is" check
[x] "is-like" check
[x] Type Assertion
[x] Casting
[x] Numeric conversion

All the above features are completed. Hence closing this issue.


Canary pipeline should use a verified release or use the github-resource

What
The canary's pipeline should pull from a release of the canary or use the gitub resource to authenticate commits.
Why
To prevent someone with write access to this repo bypassing two-eyes process

https://github.com/alphagov/gsp/pull/747


Catalog status daemon thread dies, catalog integrity and promethues metrics will then not get updated.

The catalog-integrity status and Prometheus metrics are collected and stored in a dict using a daemon thread. It looks like this thread dies unexpectedly, and there are no logic in the code to start it again.
This implementation should be changed so that the daemon thread will be restarted if it dies.
When catalog-status daemon thread  is started we store the native_id in a dict.
Will need to implement some check, that if this thread does not exists anymore, we create it again.
 if is_alive = any([th for th in threading.enumerate() if th.ident == t_id]) then start again

Updated this with new PR. Will check if this will work properly in DEV, and if it do, we can tag the new release and merge to staging and production.

This fix works as intended. New version of catalog-rebuilder tagged with v2.0.8. This update have been merged to staging. Waiting for merging to production. Closing this issue


Firefox not work

pls update

This is an old version of the script. You can find the new version here.


Incorrect buffer length for resolution ...

Hi does anyone encounter this kind of problem? How did you all solve it after encountering this problem?
**Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/picamera/camera.py", line 1704, in capture_continuous
'Timed out waiting for capture to end')
picamera.exc.PiCameraRuntimeError: Timed out waiting for capture to end
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "Object_detection_picamera.py", line 130, in
for frame1 in camera.capture_continuous(rawCapture, format="bgr",use_video_port=True):
File "/usr/lib/python3/dist-packages/picamera/camera.py", line 1710, in capture_continuous
encoder.close()
File "/usr/lib/python3/dist-packages/picamera/encoders.py", line 431, in close
self.stop()
File "/usr/lib/python3/dist-packages/picamera/encoders.py", line 419, in stop
self._close_output()
File "/usr/lib/python3/dist-packages/picamera/encoders.py", line 349, in _close_output
mo.close_stream(output, opened)
File "/usr/lib/python3/dist-packages/picamera/mmalobj.py", line 371, in close_stream
stream.flush()
File "/usr/lib/python3/dist-packages/picamera/array.py", line 238, in flush
self.array = bytes_to_rgb(self.getvalue(), self.size or self.camera.resolution)
File "/usr/lib/python3/dist-packages/picamera/array.py", line 127, in bytes_to_rgb
'Incorrect buffer length for resolution %dx%d' % (width, height))
picamera.exc.PiCameraValueError: Incorrect buffer length for resolution 640x480**
Device: Raspberry Pi 3 B+
Thank you in advance if there is.

I am also dealing with this issue except the resolution given is 1280x720 and not 640x480. No solutions found yet.


Tackle installation error: no matches for kind "Tackle" in version "tackle.konveyor.io/v1alpha1"

I am installing the tackle in my system using docker desktop for kubernetes. I have follow the steps, when i am running the CRD script getting the following error. please help on it.

@vemularamana , you need to have OLM installed before being able to deploy tackle.


grpcio_tools: implement setuptools entrypoint for generating file

Currently grpc_tools provides a command for integrating with setuptools. However, this requires custom integration on the part of the package (example: grpc_health_checking) and explicitly calling the command when building the wheel.
Is your feature request related to a problem? Please describe.
With the introduction of PEP 517 and PEP 518, directly calling setup.py will start becoming less common. Additionally this type of integration will not work with projects that use this mechanism and solely use setup.cfg
Describe the solution you'd like
Custom commands are not the only integration point that is available. setuptools. also supports entrypoints that allows for packages to act as plugins and provide custom behavior. This is documented with examples generating files based on revision control information. However, this could also be used to generate source files based on .proto files.
Describe alternatives you've considered
A project I currently work on needs to call a custom script to generate the files before building the package with build.
Additional context
I'd be interested in working on the implementation of this functionality if it is something that would be accepted.

Hi @plannigan. This sounds like a good helper feature. To make sure I understand, what you are proposing is a Makefile-like mechanism for setup.py? If a file is missing, the setup.cfg will specify how to build it and what is required to build it.
CC @gnossen WDYT?

Sounds totally reasonable to me. I'd be more than happy to review/accept a change like this.
Thanks for the offer @plannigan !

Something like that. The project I where I use grpc does not use the custom command (didn't know it existed until I started looking specifically into this issue). The current setup is a shell script that executed first that will call python -m grpc_tools.protoc with the relevant CLI arguments (--python_out, --grpc_python_out, & --proto_path). So I was thinking about something that could read pyproject.toml for configuration parameters that would allow the setuptools plugin to execute the same code path.
Also, my project also uses mypy-protobuf. So it could be nice if there was a way to accept other CLI arguments as well. But that doesn't need to be the primary concern.

@plannigan If you have a clear idea of what this feature will look like, can you put together a short proposal for what you want to do to https://github.com/grpc/proposal ? One example proposal can be https://github.com/grpc/proposal/blob/master/L95-python-reflection-client.md.
If possible, I think gRPC should support different ProtoBuf implementations.

Proposal: grpc/proposal#290


Make most of the code compatible with CUDA backend

Fixes https://github.com/SouthEndMusic/SplineGrids.jl/issues/61.
Todo:

[ ] Make follow up issue: "Compute global sample indices with kernel"
[ ] Make follow up issue: "Least squares fitting not supported for CUDA backend?"
[ ] Make follow up issue: "Compute Enzyme gradients with CUDA backend"

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

Project coverage is 95.52%. Comparing base (b73e561) to head (8f08b7e).

Files with missing lines
Patch %
Lines

src/util_kernels.jl
82.35%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #62      +/-   ##
==========================================
- Coverage   96.58%   95.52%   -1.07%
==========================================
  Files          11       11
  Lines         585      625      +40
==========================================
+ Hits          565      597      +32
- Misses         20       28       +8

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


version 3.2.4 missing npm

Where is the 3.2.4 version in npm?? can't install

Version 3.2.4 is angular-tree-component. Lower versions were angular2-tree-component. So delete old one from package and install<EMAIL_ADDRESS>

Thank you


The localisation needs improving.

Issue Type: Bug
To reproduce the bug, execute the following

Open Visual Studio Code - Insiders.
Install any localisation package if there is not any one.
Change the display language to any language different from English.
Click the 'Manage' icon on the lower left.
Notice that 'Command Palette' and 'Keyboard Shortcuts' are still in English.

Though it does not affect users too much (the English used in VS Code is not hard to comprehend), it is still a drawback.
VS Code version: Code - Insiders 1.44.0-insider (d7d1147d6b764a48b789000c03088ee9afabcd8a, 2020-03-31T08:23:56.446Z)
OS version: Windows_NT x64 10.0.18363

Another bug concerning localisation. To reproduce it, just execute the following:

Open Visual Studio Code - Insiders.
Install any localisation package if there is not any one.
Change the display language to any language different from English.
Open 'Settings'.
Notice that 'Turn on Preferences Sync' is still in English.

Thank you for your feedback!
Checked on 1.51. Already fixed.


Support GridSearch sampler

See https://github.com/pfnet/optuna/pull/665

Make this issue effort low. I'll work on this after fixed https://github.com/optuna/optuna/pull/1027.

I close this because EnqueueTrial is enough for this purpose.
https://github.com/c-bata/goptuna/blob/8dede037ee82a8b7d32680380de9013b7f982502/_examples/enqueue_trial/main.go#L40-L47


Remove data source validation of CloudWatch groups

What

Removes the use of data "aws_cloudwatch_log_group" to assert the existence of provided CloudWatch groups

Why

It prevents callers from passing in a group name directly from aws_cloudwatch_log_group, in cases where the log group is being created
Since the name attribute is generally known via configuration (statically defined), the data source attempts to read the group at plan time, but it may not exist yet.

References

This was added in https://github.com/cloudposse/terraform-aws-datadog-lambda-forwarder/pull/21. Any "plan time validation" via data sources must rely on computed attributes that cannot be known until the resource exists, i.e. a randomly generated ID. In this case, Terraform will defer the data source read until apply time because of the unknown attribute.

/test all

@nitrocode FYI

IMO this LGTM but I don't want to reverse @nitrocode's #21 PR without having him weigh in. Going to add a needs-discussion label.

/test all

Hi, checking in on how you want to resolve this. I understand the desire for #21 but ultimately the current behavior represents a bug.

@nitrocode  the PR reverses https://github.com/cloudposse/terraform-aws-datadog-lambda-forwarder/pull/21
please chime in

/test all

Hm the tests are failing on this
Error: External Program Execution Failed
  on .terraform/modules/datadog_lambda_log_forwarder.forwarder_log_artifact/main.tf line 9, in data "external" "git":
        	            	   9:   program = ["git", "-C", var.module_path, "log", "-n", "1", "--pretty=format:{\"ref\": \"%H\"}"]
        	            	The data source received an unexpected error while attempting to execute the
        	            	program.
        	            	Program: /usr/bin/git
        	            	Error Message: fatal: unsafe repository ('/__w/actions/actions' is owned by
        	            	someone else)
        	            	To add an exception for this directory, call:
        	            		git config --global --add safe.directory /__w/actions/actions

Have to imagine some change in the Actions environment is breaking https://github.com/cloudposse/terraform-external-module-artifact 🤷🏻

Yes I agree. It does seem like the testing environment has issues.
In git 2.3.6 the safe.directory feature was added so we're probably using the latest version and need to update our tests for it.
cc: @Nuru is there a way to set the global setting for git that it's recommending ?
git config --global --add safe.directory /__w/actions/actions

or would it be better to set this specifically in cloudposse/terraform-external-module-artifact then cut a new release there and bump the module version here ?
or is there a better method to solve this ?

Thanks Ben for the contribution. Apologies for this one slipping through the cracks.


Blocking Notification from showing.

I am useing NotifeeNotificationService on iOS and send a payload that looks roughly like this:
{
  tokens: Array<string>
  notification: {
    body: string
    title: string
  }
  apns: {
    payload: {
      aps: {
        contentAvailable: true // Important, to receive `onMessage` event in the foreground when message is incoming
        mutableContent: true // Important, without this the extension won't fire
      }
      notifee_options: {
        ios: {
          foregroundPresentationOptions: {
            alert: true
            badge: true
            sound: true
          }
          categoryId: string
          threadId: string
          summaryArgument: string
          sound: 'default'
        }
      }
    }
  }
}

In some cases I am wanting to block the notification from displaying in my app when a user is on a specific screen, and I can't seem to figure out how to do that.

Hey, this logic should be handled in the onForegroundEvent listener where you can control if you should display the notification (notifee.displayNotificaiton) depending on the screen the user is on. Hope that helps.