CAS not work?

from pymemcache.client.base import Client
client = Client(('localhost', 11211))
result, cas = client.gets('key')
client.cas('key', 'value1', cas)

Traceback (most recent call last):
File "", line 1, in
File "/root/.pyenv/versions/3.6.5/lib/python3.6/site-packages/pymemcache/client/base.py", line 437, in cas
return self._store_cmd(b'cas', {key: value}, expire, noreply, cas)[key]
File "/my/.pyenv/versions/3.6.5/lib/python3.6/site-packages/pymemcache/client/base.py", line 842, in _store_cmd
self._raise_errors(line, name)
File "/my/.pyenv/versions/3.6.5/lib/python3.6/site-packages/pymemcache/client/base.py", line 732, in _raise_errors
raise MemcacheUnknownCommandError(name)
pymemcache.exceptions.MemcacheUnknownCommandError: b'cas'

@UniqLife hello. What was solution of this issue?


Make WEOperationResult a generic with regard to result type

Make WEOperationResult a generic with regard to result type, should make it easier to use with specific types of results. Modify operation to be generic too.
Added a few simple tests covering operation result, and modified operation tests to leverage generics.

👍


How to change widths between swiping animation

I would like to be able to transition between widths of the slides when swiping.
====================================================================
http://jsfiddle.net/fmo50w7n/1465/
====================================================================
Steps to reproduce the problem

Set a default width for each slide
Change the slick-active slide to have a greater width

====================================================================
What is the expected behaviour?
That the slider would be able to handle the changing of the width.
====================================================================
What is observed behaviour?
The the slider recalculates the width after the swipe is finished.
====================================================================

so what you are wanting is the animated width change in the example jsfiddle?


Align max_tokens behavior with openai

As OpenAI's API doc says, max_tokens is an optional int param which defaults to inf. And since there is no official int inf in Python, we have two ways to trigger this param's default behavior:

Simply not pass this param when requests, and pydantic will set it to 16 for us.
https://github.com/vllm-project/vllm/blob/75c0ca9d432199d336e0bc6ae854aa1d35ba35ce/vllm/entrypoints/openai/protocol.py#L55-L61
Explicitly pass a None. This indicates we want to use the default value, as langchain does. And the official OpenAI APIs support passing max_tokens=None to openai.ChatCompletion.create.

However, vLLM's OpenAI-compatible server will complain when passing max_tokens=None.
This pr try to align this behavior with openai. If max_tokens=None is passed, we can set it to model's max_length and skip the length check.

cc @zhuohan123

I think with the kind help of @mspronesti, this pr is ready for review again @zhuohan123.

@chin-jey I think this pr is ready for review. I have requested a review from @zhuohan123.


Pushing View programmatically

Hi,
When I use     [self.navigationController pushViewController:vc animated:YES]; it pretty much doesn't work, not sure why? I'm not using storyboards.
Any help will be appreciated.

Hi @danglade
Can you provide more details? what is self and vc? and does self.navigationController exist ?


Merge pull request #25 from AOrthVector/master

I think this will update my personal fork to be in sync with upstream

did it work? let's go see


Implement DNS checks for api. from host

At the moment we have seen some recurring issues regarding the api endpoint not being reachable. This is likely an issue with the DNS, but unsure what causes this. A simple check to verify this from the host might aid in pinpointing this ahead of time.

Duplicate of #854

Can we modify the title of #854 to better reflect changes that need to happen? I'll close this issue, but we need a clrar overview of needed tests in that issue.


STORM-3175 - Allow usage of custom Callback.

STORM-3175

@srdo Ready to merge!

Hey, thanks for this update. Without this update, one would end up (re)writing a bolt like KafkaBolt with similar functionality but different  OnCompletion function, like I am doing currently for extracting the timestamp (message's ingest time) from RecordMetadata and passing it to the next bolt with current Tuple fields.
However, even with this update, I am afraid if I will be able to do the similar OnCompletion thing I am currently doing by rewriting the bolt.
The implemented OnCompletion  function looks  like ↓
@Override
public void onCompletion(RecordMetadata metadata, Exception e) {
  boolean hasNextBolt = appConf.getBooleanOrDefault(, true);
  synchronized (collector) {
    if (e != null) {
      collector.reportError(e);
    } else {
        if (hasNextBolt) {
          Long field1 = metadata.timestamp();
          Long field2 = input.getLongByField(...);
          String field3 = input.getStringByField(...);
          collector.emit( input, new Values(field1, field2, field3));
       }
        collector.ack(input);
    }
  }
}

Since, there is no reference to theTuple object in the  PreparableCallback interface, how can something like above be achieved?
If not achievable, is it a good idea to give reference to Tuple in the said interface allowing further new emits (in OnCompletion()) of tuples composed of new fields field1and fields from current tuple field2, field3?

@uddhavarote I wasn't sure if anyone needed the ability to emit new tuples after writing to Kafka, because you can still do further processing by adding another topology (or a new spout to your current topology) that reads from your target topic. There are some minor drawbacks to doing more processing after writing to Kafka the way your snippet does it. Either you emit the new tuple unanchored and you won't get at-least-once processing for the part of the topology after the KafkaBolt, or you anchor it to the input tuple like you do in your snippet, and risk adding the same tuples to Kafka multiple times. If the bolt after the KafkaBolt fails the tuple, the entire topology is repeated, including the KafkaBolt.
I'm not opposed to adding the collector to prepare as well as giving you access to the input tuple in the callback, but I think you should be aware of the drawbacks of laying out your topology like this.
Just for illustration, what I'm proposing is this
Data Source -> Your topology here -> KafkaBolt -> Topic A -> KafkaSpout -> Bolt handling metadata timestamp

rather than
Data Source -> Your topology here -> KafkaBolt -> Topic A
                                               -> Bolt handling metadata timestamp

@srdo Thanks for the details. Yeah, I am aware of the drawbacks. But I think emitting this next tuple into a different stream, not default stream,  should not replay the tuples in case of failure. That way, we create disjoint streams after the Kafka bolt.
The proposed topology looks good, however, say access to Topic A is not available due to the authorization or only RecordMetadata is required, there is no point in reading the whole topic.  I think one would be better off emitting the next tuple in the same topology rather than writing a new topology to read the data from RecordMetadata.
I would like to suggest that the access to the Tuple be provided. along with a note about the consequences in such a case.


nsc: init at 2.7.6

Description of changes
nsc is a tool for creating NATS account and user access configurations.
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)
[x] 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/)
23.05 Release Notes (or backporting 22.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

[x] Fits CONTRIBUTING.md.

Tested with nix run .#nsc -- --help

Result of nixpkgs-review pr 217235 run on x86_64-linux 1

1 package built:

nsc


Can't assign 0 to next_month()

I tried to do what described in the subject and get the following results.
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/DateRanger/init.py", line 134, in prev_month
end = end + timedelta(days=1)
UnboundLocalError: local variable 'end' referenced before assignment

Thank you. I will fix it. :)

fixed :)


[NDTensors] [BUG] Many basic tensor operations fail with CUDA extension due to LoadError: Scalar indexing is disallowed.

Description of bug
I am attempting to use the CUDA extension for NDTensors. I am finding that tensor contraction sometimes fails, along with other functions like permute, as well as the NDTensors.generic_randn call used in the example of the NDTensors CUDA extension (NDTensors/ext/examples/NDTensorCUDA.jl).
They all fail with ERROR: LoadError: Scalar indexing is disallowed. (or emit a similar warning in the REPL where scalar indexing is allowed).
Minimal code demonstrating the bug or unexpected behavior
Minimal runnable code
import CUDA
import ITensors
import NDTensors

i, j, k = ITensors.Index(3), ITensors.Index(5), ITensors.Index(2)
A, B = ITensors.randomITensor(i, j), ITensors.randomITensor(j, k)

# works when running script directly, but warns of scalar indexing in REPL
cuA, cuB = NDTensors.cu(A), NDTensors.cu(B)

contracted = cuA * cuB

@show NDTensors.cpu(contracted) ≈ A * B

# without @CUDA.allowscalar, fails with `ERROR: LoadError: Scalar indexing is disallowed.`
permuted = ITensors.permute(cuA, (j, i))

Expected output or behavior
NDTensors.cu() should work without warning in REPL on ITensors.ITensor, and ITensors.permute should work without the scalar indexing error.
Actual output or behavior
Output of minimal runnable code
NDTensors.cpu(contracted) ≈ A * B = true
ERROR: LoadError: Scalar indexing is disallowed.
Invocation of getindex resulted in scalar indexing of a GPU array.
This is typically caused by calling an iterating implementation of a method.
Such implementations *do not* execute on the GPU, but very slowly on the CPU,
and therefore are only permitted from the REPL for prototyping purposes.
If you did intend to index this array, annotate the caller with @allowscalar.
Stacktrace:
  [1] error(s::String)
    @ Base ./error.jl:35
  [2] assertscalar(op::String)
    @ GPUArraysCore ~/.julia/packages/GPUArraysCore/uOYfN/src/GPUArraysCore.jl:103
  [3] getindex
    @ ~/.julia/packages/GPUArrays/5XhED/src/host/indexing.jl:9 [inlined]
  [4] getindex
    @ ~/.julia/packages/StridedViews/MjjHH/src/stridedview.jl:97 [inlined]
  [5] macro expansion
    @ ~/.julia/packages/Strided/O8zfl/src/mapreduce.jl:330 [inlined]
  [6] macro expansion
    @ ./simdloop.jl:77 [inlined]
  [7] macro expansion
    @ ~/.julia/packages/Strided/O8zfl/src/mapreduce.jl:329 [inlined]
  [8] _mapreduce_kernel!(f::Strided.CaptureArgs{NDTensors.var"#69#70", Tuple{Strided.Arg, Strided.Arg}}, op::Nothing, initop::Nothing, dims::Tuple{Int64, Int64}, blocks::Tuple{Int64, Int64}, arrays::Tuple{StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}, StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}, StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}}, strides::Tuple{Tuple{Int64, Int64}, Tuple{Int64, Int64}, Tuple{Int64, Int64}}, offsets::Tuple{Int64, Int64, Int64})
    @ Strided ~/.julia/packages/Strided/O8zfl/src/mapreduce.jl:229
  [9] _mapreduce_block!(f::Any, op::Any, initop::Any, dims::Tuple{Int64, Int64}, strides::Tuple{Tuple{Int64, Int64}, Tuple{Int64, Int64}, Tuple{Int64, Int64}}, offsets::Tuple{Int64, Int64, Int64}, costs::Tuple{Int64, Int64}, arrays::Tuple{StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}, StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}, StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}})
    @ Strided ~/.julia/packages/Strided/O8zfl/src/mapreduce.jl:152
 [10] _mapreduce_order!(f::Any, op::Any, initop::Any, dims::Tuple{Int64, Int64}, strides::Tuple{Tuple{Int64, Int64}, Tuple{Int64, Int64}, Tuple{Int64, Int64}}, arrays::Tuple{StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}, StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}, StridedViews.StridedView{Float64, 2, CUDA.CuArray{Float64, 2, CUDA.Mem.DeviceBuffer}, typeof(identity)}})
    @ Strided ~/.julia/packages/Strided/O8zfl/src/mapreduce.jl:138
 [11] _mapreduce_fuse!
    @ ~/.julia/packages/Strided/O8zfl/src/mapreduce.jl:116 [inlined]
 [12] copyto!
    @ ~/.julia/packages/Strided/O8zfl/src/broadcast.jl:35 [inlined]
 [13] materialize!
    @ ./broadcast.jl:884 [inlined]
 [14] materialize!
    @ ./broadcast.jl:881 [inlined]
 [15] permutedims!(R::NDTensors.DenseTensor{Float64, 2, Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}}, NDTensors.Dense{Float64, CUDA.CuArray{Float64, 1, CUDA.Mem.DeviceBuffer}}}, T::NDTensors.DenseTensor{Float64, 2, Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}}, NDTensors.Dense{Float64, CUDA.CuArray{Float64, 1, CUDA.Mem.DeviceBuffer}}}, perm::Tuple{Int64, Int64}, f::NDTensors.var"#69#70")
    @ NDTensors ~/.julia/packages/NDTensors/olKso/src/dense/densetensor.jl:246
 [16] permutedims!!(R::NDTensors.DenseTensor{Float64, 2, Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}}, NDTensors.Dense{Float64, CUDA.CuArray{Float64, 1, CUDA.Mem.DeviceBuffer}}}, T::NDTensors.DenseTensor{Float64, 2, Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}}, NDTensors.Dense{Float64, CUDA.CuArray{Float64, 1, CUDA.Mem.DeviceBuffer}}}, perm::Tuple{Int64, Int64}, f::Function)
    @ NDTensors ~/.julia/packages/NDTensors/olKso/src/dense/densetensor.jl:188
 [17] permutedims!!
    @ ~/.julia/packages/NDTensors/olKso/src/dense/densetensor.jl:186 [inlined]
 [18] permutedims
    @ ~/.julia/packages/NDTensors/olKso/src/tensoralgebra/generic_tensor_operations.jl:5 [inlined]
 [19] permutedims
    @ ~/.julia/packages/ITensors/Qe99p/src/tensor_operations/permutations.jl:64 [inlined]
 [20] _permute(as::NDTensors.NeverAlias, T::NDTensors.DenseTensor{Float64, 2, Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}}, NDTensors.Dense{Float64, CUDA.CuArray{Float64, 1, CUDA.Mem.DeviceBuffer}}}, new_inds::Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}})
    @ ITensors ~/.julia/packages/ITensors/Qe99p/src/tensor_operations/permutations.jl:69
 [21] permute(as::NDTensors.NeverAlias, T::ITensors.ITensor, new_inds::Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}})
    @ ITensors ~/.julia/packages/ITensors/Qe99p/src/tensor_operations/permutations.jl:73
 [22] #permute#271
    @ ~/.julia/packages/ITensors/Qe99p/src/tensor_operations/permutations.jl:54 [inlined]
 [23] permute(T::ITensors.ITensor, new_inds::Tuple{ITensors.Index{Int64}, ITensors.Index{Int64}})
    @ ITensors ~/.julia/packages/ITensors/Qe99p/src/tensor_operations/permutations.jl:38
 [24] top-level scope
    @ ~/it_test2/test.jl:17
in expression starting at /home/william/it_test2/test.jl:17

Output of `cuA, cuB = NDTensors.cu(A), NDTensors.cu(B)` in REPL
┌ Warning: Performing scalar indexing on task Task (runnable) @0x00007f5e6b5fc970.
│ Invocation of getindex resulted in scalar indexing of a GPU array.
│ This is typically caused by calling an iterating implementation of a method.
│ Such implementations *do not* execute on the GPU, but very slowly on the CPU,
│ and therefore are only permitted from the REPL for prototyping purposes.
│ If you did intend to index this array, annotate the caller with @allowscalar.
└ @ GPUArraysCore ~/.julia/packages/GPUArraysCore/uOYfN/src/GPUArraysCore.jl:

Also, running `NDTensors/ext/examples/NDTensorCUDA.jl` results in a similar error

ERROR: LoadError: Scalar indexing is disallowed.
Invocation of setindex! resulted in scalar indexing of a GPU array.
This is typically caused by calling an iterating implementation of a method.
Such implementations *do not* execute on the GPU, but very slowly on the CPU,
and therefore are only permitted from the REPL for prototyping purposes.
If you did intend to index this array, annotate the caller with @allowscalar.
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:35
 [2] assertscalar(op::String)
   @ GPUArraysCore ~/.julia/packages/GPUArraysCore/uOYfN/src/GPUArraysCore.jl:103
 [3] setindex!
   @ ~/.julia/packages/GPUArrays/5XhED/src/host/indexing.jl:17 [inlined]
 [4] generic_randn(arraytype::Type{CuArray{T, 1} where T}, dim::Int64)
   @ NDTensors ~/.julia/packages/NDTensors/olKso/src/abstractarray/fill.jl:8
 [5] main()
   @ Main ~/ITensors.jl/NDTensors/ext/examples/NDTensorCUDA.jl:21
 [6] top-level scope
   @ ~/ITensors.jl/NDTensors/ext/examples/NDTensorCUDA.jl:116
in expression starting at /home/william/ITensors.jl/NDTensors/ext/examples/NDTensorCUDA.jl:116

Version information

Output from versioninfo():

julia> versioninfo()
Julia Version 1.9.2
Commit e4ee485e909 (2023-07-05 09:39 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 12 × Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-14.0.6 (ORCJIT, skylake)
  Threads: 1 on 12 virtual cores

Other relevant version info

(it_test2) pkg> status ITensors
Status `~/it_test2/Project.toml`
  [9136182c] ITensors v0.3.42

(it_test2) pkg> status NDTensors
Status `~/it_test2/Project.toml`
  [23ae76d9] NDTensors v0.2.10

(it_test2) pkg> status CUDA
Status `~/it_test2/Project.toml`
  [052768ef] CUDA v4.4.1

julia> CUDA.versioninfo()
CUDA runtime 12.1, artifact installation
CUDA driver 12.2
NVIDIA driver 535.104.5

CUDA libraries:
- CUBLAS: 12.1.3
- CURAND: 10.3.2
- CUFFT: 11.0.2
- CUSOLVER: 11.4.5
- CUSPARSE: 12.1.0
- CUPTI: 18.0.0
- NVML: 12.0.0+535.104.5

Julia packages:
- CUDA: 4.4.1
- CUDA_Driver_jll: 0.5.0+1
- CUDA_Runtime_jll: 0.6.0+0

Toolchain:
- Julia: 1.9.2
- LLVM: 14.0.6
- PTX ISA support: 3.2, 4.0, 4.1, 4.2, 4.3, 5.0, 6.0, 6.1, 6.3, 6.4, 6.5, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5
- Device capability support: sm_37, sm_50, sm_52, sm_53, sm_60, sm_61, sm_62, sm_70, sm_72, sm_75, sm_80, sm_86

1 device:
  0: NVIDIA GeForce RTX 3090 (sm_86, 22.728 GiB / 24.000 GiB available)

I am very new to Julia (and ITensors.jl), sorry if there is something obvious I'm missing!

Thanks for the report. @kmp5VT could you take a look?

Hello!
I am testing out the updated NDTensor CUDA extension. I am using ITensors.jl v0.3.46, CUDA.jl v5.0.0, and CUDA v11.8. I am still getting the error described in the OP for the following operation. Also I get it anytime I try to use contract with either naive or zipup.
MWE - Trying to truncate after a direct sum of two MPS
using CUDA, ITensors

function main()

    gpu = cu

    d = 2
    N = 5
    n = d^N
    x = LinRange(1, 2, n)
    f = x .^ 2
    g = sin.(x)
    s = siteinds(d, N)
    fmps = gpu(MPS(f, s))
    gmps = gpu(MPS(g, s))
    hmps = gpu(MPS(zeros(n), s))
    hmps .= add(fmps, gmps; alg="directsum")
    truncate!(hmps; cutoff=1E-8)
end

main()

@mtfishman I think there still might be an issue here, specifically in the truncate! call. I am looking into this now

@NuclearPowerNerd could you double check to make sure you are using the latest version? The error you quoted in the first post should have been fixed by #1194.

Yes. I double checked and I have ITensors v0.3.46 in the Project.toml and I also looked in the Manifest and it lists NDTensors v0.2.14 under dependencies of ITensors.

Thanks for confirming. Some of my confusion was that this appears to be specific to the CUDA.jl backend, I was running the code you shared using our Metal.jl backend and wasn't seeing any issues. We are investigating this, it looks like it is an easy fix though we might make some more involved changes to make it easier for us to fix issues that are particular to certain GPU backends in the future so will take a bit of time.

This will be fixed by #1220.

I can create a new issue if needed - please just let me know. I am still getting this error any time I try to use the zipup algorithm.

Could you start a new issue reporting a particular problem with a minimal code example as well as the full error message/stack trace? Also be sure to test against the latest versions of NDTensors and ITensors, we have been making a number of improvements and bug fixes very recently.


requiring user interaction before running tests, per chrome autoplay policy

This resolves some issues I was having running the tests in Chrome

@aceslowman would you like to merge this one!!
Go ahead

@endurance21 Great! I don't think I have permissions to merge though, or at least I'm not seeing the 'Merge Pull Request' button.

Oh yes, so let me do this work🤫


API 'variant.getMergeResources()' is obsolete and has been replaced with 'variant.getMergeResourcesProvider()

Good afternoon.
Thank you very much for your work.
But I have a problem with the latest plugin version (1.5.0) - Android Studio "says", that "API 'variant.getMergeResources()' is obsolete and has been replaced with 'variant.getMergeResourcesProvider()'. It will be removed at the end of 2019.".
And seems the problem is in your plugin. It is the stacktrace:

To determine what is calling variant.getMergeResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace. at com.android.builder.errors.EvalIssueReporter$DefaultImpls.reportIssue(EvalIssueReporter.kt:94) at com.android.build.gradle.internal.errors.SyncIssueHandler$DefaultImpls.reportIssue(SyncIssueHandler.kt) at com.android.build.gradle.internal.errors.SyncIssueHandlerImpl.reportIssue(SyncIssueHandlerImpl.kt:31) at com.android.builder.errors.EvalIssueReporter$DefaultImpls.reportIssue(EvalIssueReporter.kt:117) at com.android.build.gradle.internal.errors.SyncIssueHandler$DefaultImpls.reportIssue(SyncIssueHandler.kt) at com.android.build.gradle.internal.errors.SyncIssueHandlerImpl.reportIssue(SyncIssueHandlerImpl.kt:31) at com.android.build.gradle.internal.errors.DeprecationReporterImpl.reportDeprecatedApi(DeprecationReporterImpl.kt:77) at com.android.build.gradle.internal.api.BaseVariantImpl.getMergeResources(BaseVariantImpl.java:333) at com.android.build.gradle.internal.api.ApplicationVariantImpl_Decorated.getMergeResources(Unknown Source) at com.google.ar.sceneform.plugin.SceneformAssets$1.execute(SceneformAssets.java:54) at com.google.ar.sceneform.plugin.SceneformAssets$1.execute(SceneformAssets.java:47) at org.gradle.configuration.internal.DefaultListenerBuildOperationDecorator$BuildOperationEmittingAction$1$1.run(DefaultListenerBuildOperationDecorator.java:155) at org.gradle.configuration.internal.DefaultUserCodeApplicationContext.reapply(DefaultUserCodeApplicationContext.java:58) at org.gradle.configuration.internal.DefaultListenerBuildOperationDecorator$BuildOperationEmittingAction$1.run(DefaultListenerBuildOperationDecorator.java:152) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) at org.gradle.configuration.internal.DefaultListenerBuildOperationDecorator$BuildOperationEmittingAction.execute(DefaultListenerBuildOperationDecorator.java:149) at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:91) at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:80) at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:42) at org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:230) at org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:149) at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:58) at org.gradle.internal.event.BroadcastDispatch$CompositeDispatch.dispatch(BroadcastDispatch.java:324) at org.gradle.internal.event.BroadcastDispatch$CompositeDispatch.dispatch(BroadcastDispatch.java:234) at org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:140) at org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy33.afterEvaluate(Unknown Source) at org.gradle.configuration.project.LifecycleProjectEvaluator$NotifyAfterEvaluate$1.execute(LifecycleProjectEvaluator.java:187) at org.gradle.configuration.project.LifecycleProjectEvaluator$NotifyAfterEvaluate$1.execute(LifecycleProjectEvaluator.java:184) at org.gradle.api.internal.project.DefaultProject.stepEvaluationListener(DefaultProject.java:1418) at org.gradle.configuration.project.LifecycleProjectEvaluator$NotifyAfterEvaluate.run(LifecycleProjectEvaluator.java:193) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) at org.gradle.configuration.project.LifecycleProjectEvaluator$EvaluateProject.run(LifecycleProjectEvaluator.java:110) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:68) at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:687) at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:140) at org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35) at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:62) at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:41) at org.gradle.initialization.DefaultGradleLauncher$ConfigureBuild.run(DefaultGradleLauncher.java:274) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) at org.gradle.initialization.DefaultGradleLauncher.configureBuild(DefaultGradleLauncher.java:182) at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:141) at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:124) at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:77) at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:74) at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:154) at org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks(StopShieldingWorkerLeaseService.java:38) at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:96) at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:74) at org.gradle.tooling.internal.provider.runner.BuildModelActionRunner.run(BuildModelActionRunner.java:55) at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32) at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.run(RunAsBuildOperationBuildActionRunner.java:50) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:45) at org.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run(SubscribableBuildActionRunner.java:51) at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:47) at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:44) at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:79) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:44) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30) at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:39) at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:25) at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:80) at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:53) at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:62) at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:34) at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36) at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25) at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43) at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29) at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:59) at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31) at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:59) at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:44) at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:46) at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:30) at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67) at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74) at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72) at org.gradle.util.Swapper.swap(Swapper.java:38) at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62) at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:81) at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50) at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.lang.Thread.run(Thread.java:745)

And it is the reason, why I can't connect to Firebase and configure the notifications in my app.
Please, fix the problem in the future release.
Thank you in advance.
Regards.

Bro do you solve this problem??I also face this

implementation 'com.google.ar.sceneform.ux:sceneform-ux:1.7.0'
Gradle version : gradle-4.10.1-all.zip
Android studio version : 3.3.1
I got this log when build the project

WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.

the details log is same with @somoreingold at the top

Bro do you solve this problem??I also face this

The problem is still here.
But you can switch off this plugin, sync and try to connect to Firebase again - must be success now.
After successful connection to Firebase you can return your plugin and resync. Warning will appear again, but it is not important, because Firebase has configured already.

implementation 'com.google.ar.sceneform.ux:sceneform-ux:1.7.0'
Gradle version : gradle-4.10.1-all.zip
Android studio version : 3.3.1
I got this log when build the project

WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.

the details log is same with @dmitry-kanunnikoff at the top

Thank you, after changed version working fine

I also face this,too.And found the version 1.5.1 working fine.
project gradle:
buildscript {

    repositories {
        google()
        ...
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.2.1'
        classpath 'com.google.ar.sceneform:plugin:1.5.1'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

app gradle:

dependencies {
    ...
    implementation "com.google.ar.sceneform.ux:sceneform-ux:1.5.1"

}

apply plugin: 'com.google.ar.sceneform.plugin'
sceneform.asset('sampledata/tiger/Mesh_BengalTiger.obj',
        'default',
        'sampledata/tiger/Mesh_BengalTiger.sfa',
        'src/main/assets/Mesh_BengalTiger')

Same here.

The plugin developers need to apply the pull request for the solution of the problem.
As you can see here: https://github.com/google/play-services-plugins/pull/62

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

Thanks bro, this worked for me.

I think it's safe to use 4.3. This is a usual warning message that you'll see when upgrading google-services. That warning usually disappears before the method is removed end of 2019.

@numankaraaslan There is an issue in Google bug tracker devoted to this.

@numankaraaslan See https://github.com/google/play-services-plugins/issues/65

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

worked..... wow..

Still now...
WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
Affected Modules: app

Chane com.google.gms:google-services:4.2.0 clastpath in project level gradle.

Failed to resolve: com.android.support.appcompat-v7:28.0.0: |
-- | --
Sync Failed | 8 s 69 ms
ERROR: Failed to resolve: com.android.support.appcompat-v7:28.0.0:
Affected Modules: app
how to resolve???

Could you please send screenshot

I had this warning after updating my classpath to 'com.google.gms:google-services:4.3.0'
So I returned it to 'com.google.gms:google-services:4.1.0' and the warning was gone.

@Gunjan9sahoo maybe you should migrate to android X framework for support libraries.
Migrate to androidx libraries

AndroidX does not change the problem. It still exists.

i solved it  thank you very much
On Thu, Jul 11, 2019 at 8:21 PM mjjabarullah<EMAIL_ADDRESS>wrote:

Could you please send screenshot
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/sceneform-android-sdk/issues/408?email_source=notifications&email_token=AKE3G3DX6PWGU3OZL4BERD3P65CHHA5CNFSM4GAHD4V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZW6PNI#issuecomment-510519221,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKE3G3AYON7GK27T7QZ2OULP65CHHANCNFSM4GAHD4VQ
.

i solved it thank you very much
On Sat, Jul 13, 2019 at 11:58 PM Mendhie Emmanuel<EMAIL_ADDRESS>wrote:

I had this warning after updating my classpath to
'com.google.gms:google-services:4.3.0'
So I returned it to 'com.google.gms:google-services:4.1.0' and the warning
was gone.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/sceneform-android-sdk/issues/408?email_source=notifications&email_token=AKE3G3GXI7FAW3OBSBMIEFDP7INEBA5CNFSM4GAHD4V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3W7VA#issuecomment-511143892,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKE3G3FR532ZR4UYSLXUAKTP7INEBANCNFSM4GAHD4VQ
.

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

worked 👍

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
Thanks man for the answer. It worked for me.

I got this when I run :
_### lorraine@chepkemoi:~/AndroidStudioProjects/MyApplication$ gradlew sync -Pandroid.debug.obsoleteApi=true
Command 'gradlew' not found, did you mean:
command 'gradle' from deb gradle
Try: sudo apt install _

I got this when I run :
_### lorraine@chepkemoi:~/AndroidStudioProjects/MyApplication$ gradlew sync -Pandroid.debug.obsoleteApi=true
Command 'gradlew' not found, did you mean:
command 'gradle' from deb gradle
Try: sudo apt install _

Run like ./gradlew ...

Chane com.google.gms:google-services:4.2.0 clastpath in project level gradle.

when i change version 4.2.0 , i got an Exception "com.google.android.gms.common.api.ApiException: 12500:" like this on google signin

Chane com.google.gms:google-services:4.2.0 clastpath in project level gradle.

when i change version 4.2.0 , i got an Exception "com.google.android.gms.common.api.ApiException: 12500:" like this on google signin

I have the same problem. I don't find how to solve it.

I had this warning after updating my classpath to 'com.google.gms:google-services:4.3.0'

Thanks, it worked

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

its working.... Thank You

Maintain project gradle with these versions
classpath 'com.android.tools.build:gradle:3.4.2'
classpath 'com.google.gms:google-services:4.2.0'

classpath 'com.google.gms:google-services:4.2.0' works!

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

Worked for me. thanks

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

This works for me.

Related issue: https://github.com/google/play-services-plugins/issues/79

In my case, it was caused from gms services 4.3.0. So i had to change it to:
com.google.gms:google-services:4.2.0
I have found this by running:
gradlew sync -Pandroid.debug.obsoleteApi=true
in terminal. Go to view -> tool windows -> Terminal in Android Studio.
Gms services will probably fix this in the future versions.

Both 4.3.0 and 4.3.1 are causing this. I'm surprised to see how Google have not corrected this in the latest version (4.3.1).

I tried to lower the version to 4.2.0, but I still get the same error

would like to make my login button have image how to I go
On Wed, Aug 28, 2019 at 12:51 PM Ali Tamoor<EMAIL_ADDRESS>wrote:

Thanks man solved it after chnaging 4.3.1 to 4.2.0 in the project level
build.gradle as
classpath 'com.google.gms:google-services:4.3.0'
to
classpath 'com.google.gms:google-services:4.2.0'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/sceneform-android-sdk/issues/408?email_source=notifications&email_token=AJ6BEOGIDTFILYQSLROJ2W3QGZDCNA5CNFSM4GAHD4V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5KRRDQ#issuecomment-525670542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ6BEOEUOTV3PSBVBAOIBOLQGZDCNANCNFSM4GAHD4VQ
.

Solved to me by,

Go to the (project-level) build.Gradle file;
Replace classpath 'com.google.gms:google-services:4.3.0' with an older version like 4.2.0 instead of 4.3.1
good luck,

With com.google.gms:google-services:4.3.2 I still have the same warning.
But reverting to 4.2.0 might be worse than having this warning, IMO.

That problem was solved for me with com.google.gms:google-services:4.3.2

That problem was solved for me with com.google.gms:google-services:4.3.2

Problem solved for me with com.google.gms:google-services:4,.3.2 as well.

Fixed on com.google.gms:google-services:4.3.3

This should be fixed on  com.google.gms:google-services:4.3.3. Reverting to com.google.gms:google-services:4.2.0 isn't a good solution


Use operator @beginWith error

When  I send a request_uri is "/index.php?act=seller_center&op=statistics&rand=24954191" and my rule is "SecRule REQUEST_URI "@beginswith /index.php?act=store"
"id:1004,phase:1,pass,nolog,
ctl:ruleRemoveById=949110" but rule id 1004  that his uri is not match the "/index.php?act=seller_center&op=statistics&rand=24954191"，and I found the request I send has match the rule that his id is 1004  why？ The operator beginwith is not a exact match？

@Hello-Linux that is an specific issue of ModSecurity version 3 for apache?

@Hello-Linux I see that you created the same issue on 3 distinct (but related) ModSecurity projects:
https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/810
https://github.com/SpiderLabs/ModSecurity/issues/1458
https://github.com/SpiderLabs/ModSecurity-apache/issues/19
As others have mentioned, please be more cautious when creating issues by paying closer attention on which kind of issue you have to decide on which project the issue or mailing list it should be.
And most importantly, please try not to create several issues for the same question. Also try testing a bit more, looking through ModSecurity's reference docs (manual/books/tutorials) and searching for similar issues on Github and the mailing lists before creating a new issue. You have opened 21 new issues in these projects on the last 30 days. You will be surprised that probably many of your questions could already be answered or being handled already in other issues and mailing list e-mails.
As you know these are community projects and everyone takes their time to work improving ModSecurity and helping out each other, so any effort you could do to make everyone's lives easier will be greatly appreciated :)
Thanks!


Defined as centerDocked but placed to bottom right

Just replacing the FAB w/ yours
    floatingActionButtonLocation: FloatingActionButtonLocation.centerDocked,
        floatingActionButton: _buildFab(context),

Supposed to look like this:

But looks like this:

In general it looks like it does not follow any placement positions. I wanted to render the button on the left, but it keeps showing on right which is entirely unusable fo my use-case.
Simplified code. I have different reasons why not use FloatingActionButtonLocation -- having there more butttons.
floatingActionButton:  Align(             alignment: Alignment.bottomLeft,             child: _buildFab(context),

In general it looks like it does not follow any placement positions. I wanted to render the button on the left, but it keeps showing on right which is entirely unusable fo my use-case.
Simplified code. I have different reasons why not use FloatingActionButtonLocation -- having there more butttons.
floatingActionButton:  Align(             alignment: Alignment.bottomLeft,             child: _buildFab(context),


Alert: Use icon-condensed for closeable alerts

The problem
In closeable alerts with just a single line of text, the current close button is large enough that it ends up dictating the height of the alert. This causes the single line of text to have slightly more space below it than above it, which ends up looking like a mistaken attempt to vertically center the content (even though we're not explicitly vertically centering the content, here).
The solution
Use the icon-condensed property on the close button to make it ever-so-slightly smaller, collapsing it enough to restore the vertically-centered appearance of single-line text.
Alternatives considered

Creating a new button variant with the icon the same size but with less padding—too much complexity.
Explicitly vertically centering the text—probably easy enough to do, but not sure it's really the invariant we're going for here.

Additional information
Current:

Desired:

Can you assign this issue to me?

After running yarn test it is failed and storybook is also not working.
Branch-Develop

@CYBWEBALI Sorry to hear that. Can you please provide more information? What isn't working? Is there a failure message? This information should let us help you more quickly!

According to Contribution Guide, to run storybook cmd is:
yarn storybook:wc:dev
Command Output is:

@CYBWEBALI Thanks for the detail. Unfortunately I can't reproduce this on the head commit of develop. One difference I see is that you're using a Windows machine, which I'm not sure any of the team here is using for development. It ultimately looks like something is parsing the files incorrectly based on the copious string escapes in your output. It's quite possible something we're doing here is not Windows-compatible; I don't quite see that it is the part you highlighted at a glance, but possible. I won't be able to look deeper immediately, but if you make any headway in the meantime I'm sure we'd appreciate making sure things are working on Windows!


Stop server after puppet, and before migrations.

Testing plan: Saw an explicit stop between puppet application and database upgrades.

This pulls in one commit from #21570.  It's arguable that https://github.com/zulip/zulip/pull/21570/commits/d1b0577d260c07c45f41fe06028fcb1da7b22a1a would also make sense to  also pull into this, as a cleanup to the output as well a minor performance optimization.

This looks great! I think it makes sense to pull in that commit to improve the output, because we have gotten plenty of "bug reports" about those "process already stopped" errors in the past.
And then I guess we'll need to add a duplicate of the deferred_work part of the zerver/migrations/0376_set_realmemoji_author_and_reupload_realmemoji.py migration to deal with servers that have already upgraded.  (I don't think there's any point in trying to avoid doing work twice, since it's a fast deferred work job).

This was backported to 5.x as fc0d5fcfd5011eefba755b51bffc427cb8df925d + 00382078addc2765748741c10bf0b7b92da0d7a9


Video not displaying

I recently got my new google coral dev board and camera and I am going through the tutorials.
/examples-camera/opencv/ detect.py is the script I am trying to get to work.  When I run it I get the following error.

I installed all requirements using the install_requirements script. I also have my HDMI connection to a monitor.

Some monitors dont work with Coral.   The one I was using was not displaying anything.  Move to another one and everything isworking.


Error when running webpack in vuetify

Hi, I have a project with Vue, Vuetify, and webpack. I initiate the project with vue add vuetify. I add webpack & webpack-cli with yarn add webpack webpack-cli -D. Vuetify automatically using sass in usage. My purpose is want to set environment variables with webpack. Here's my webpack.config.js (I'm followed from all official docs):
const path = require('path');
const VueLoaderPlugin = require('vue-loader/lib/plugin')
const VuetifyLoaderPlugin = require('vuetify-loader/lib/plugin')

module.exports = env => {
    // Use env.<YOUR VARIABLE> here:
    console.log('NODE_ENV: ', env.NODE_ENV); // 'local'
    console.log('Production: ', env.production); // true

    return {
        entry: './src/main.js',
        output: {
            filename: 'bundle.js',
            path: path.resolve(__dirname, 'dist'),
        },
        module: {
            rules: [
                { test: /\.vue$/, use: 'vue-loader' },
                {
                    test: /\.m?js$/,
                    exclude: /(node_modules|bower_components)/,
                    use: {
                        loader: 'babel-loader',
                        options: {
                            presets: ['@babel/preset-env']
                        }
                    }
                },
                {
                    test: /\.s(c|a)ss$/,
                    use: [
                        'vue-style-loader',
                        'css-loader',
                        {
                            loader: 'sass-loader',
                            // Requires<EMAIL_ADDRESS>                            options: {
                                implementation: require('sass'),
                                fiber: require('fibers')
                            },
                            // Requires<EMAIL_ADDRESS>                            options: {
                                implementation: require('sass'),
                                sassOptions: {
                                    fiber: require('fibers')
                                },
                            },
                        },
                    ],
                },
            ]
        },
        plugins: [
            // make sure to include the plugin!
            new VueLoaderPlugin(), new VuetifyLoaderPlugin()
        ]
    };
};

After that, I'm running: webpack --env.NODE_ENV=local --env.production --progress

It looks like you just deleted/ignored our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.


Fetching xrefs commit info

Fetching xrefs commit info should be a separate proces for each term. At the moment, running the script fetches the information for each xref, effectively updating references for all xrefs in a repo, erasing earlier links to a certain version of an xref.

Fetching xrefs commit info now tests if an xref is already present. If so, the xref is untouched.
Also, there is a provision to remove an xref from the JSON.


i can not select more than one image

Even when i set fusuma.allowMultipleSelection = true i can not select more than one image
Please can you help me

+1


Disable base workspace upgrade

What is being addressed
This issue prevents a normal upgrade flow for the base workspace so we need to disable it for the time being.

/test-extended

@tamirkamara @LizaShak this will break Guacamole as it relies on the upgrade step to add redirect URIs.
How hard is it to fix the Redaction issue?

It's hard and @damoodamoo is fixing it.
In the meantime, I'll bring back the step calling the script directly.

I now see you deleted the update redirect urls script in that workspace upgrade PR which I don't get (and I approved it). Anyway, I'll work on reverting it.

/test-extended

/test-env-destroy

/test-destroy-env

/test-extended


Add ability to delete current audio file

As title. Just a basic thing that would be nice.

Added in develop branch:

Launched in 3.2.4.


Missing second parameter to vcs.update

Testing case:
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[packages]
requests = {git = "https://github.com/requests/requests", ref = "master"}

[dev-packages]

It is great that passa can resolve non-editable VCS deps. Iooking forward to replacing pip-tools.

LGTM!

Does the second argument always exist? We’ll need to make sure this works with older pip versions.

@uranusjr Oh no i didn't check that, it turns out it was introduced in v18.1 😢

Yea, pip's VCS support code has been getting cleaned up and improved lately.

wait why are we still using this directly?


feat: add markdownlint-rule-github-admonition to rules docker image

GitHub Admonition markdownlint rule was released a few days ago. It allows us to detect and fix GitHub-style admonitions.
With this pull request we also include it into the rules docker image.

i am sorry, to not generate an issue, but i thought i is not worth it, as the change itself is a Yay-or-Nay kind of change, either it will be used or not :)

No worries, the intent is to include all such rules.

We should wait and then retry the failing link test. It looks like maybe npm is returning HTTP 503 all over the place right now. Unrelated to your change.

Side question, for the fun of it, I created a dockerfile, which will automatically install all dependencies based on the npmjs API. It is a security risk to trust those sources blindly, but as usual, I thought I share my approach.  :)


sound: Improve function definition

Summary of the PR
instead of consume() fn, use read_output() fn which is more appropriate and in sync with the write_input() fn.
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:

[x] All commits in this PR are signed (with git commit -s), and the commit
message has max 60 characters for the summary and max 75 characters for each
description line.
[x] All added/changed functionality has a corresponding unit/integration
test.
[x] All added/changed public-facing functionality has entries in the "Upcoming
Release" section of CHANGELOG.md (if no such section exists, please create one).
[x] Any newly added unsafe code is properly documented.

Hi @dorindabassey,
Few minor suggestions here:

Please always add a commit log, even if the change is obvious.
And I would avoid rebasing such a minor rename change against any other commit, which may delay merging of this one.

Thanks.

Hi @dorindabassey,
Few minor suggestions here:
* Please always add a commit log, even if the change is obvious.

* And I would avoid rebasing such a minor rename change against any other commit, which may delay merging of this one.

Thanks.

That's Right! Thanks.


Service doesn't install in a hardened windows 10 (1709) X64 latest update

I have a hardened system (based on DoD instructions), which is enforcing DEP, and almost all other exploit protections offered by windows defender in windows 10 (1709) X64 (latest update) (always on), almost no exceptions.
All other DNS services (like Unbound), all other programs (with the exception of Tor browser) including the previous versions of DNSCrypt 1.0 service get installed on this machine, no problems, but the new DNSCrypt doesn't get installed.
How can this be fixed without defining an exception in my exploit protection environment? I am currently using unbound over a VPN, and I don't trust other DNSCrypt implementations (like stubby), and if my VPN drops my DNS goes out as well, I really need DNSCrypt to work on my system (without defining exceptions in windows defender).
Thank you.

These mitigations are for applications written in C/C++.
dnscrypt-proxy is not written in C, and doesn't depend on any external code written in C.
DEP is not really relevant to "safe" languages that don't interact with C/C++ code. In this context, ASLR isn't either, even though the Go compiler supports it as an option, but only on Linux.

So, to recap, this need to make an exception. But this is not a "bad" thing. Applications written safe languages such as Go are safer than C/C++ applications + these mitigations.
Because by design, the problems these mitigations are designed to address don't exist in these languages.


Verbose logging

cddns -v should provide enhanced logging.
Currently we are not using the tracing crate, but it would be a massive improvement.

Fixed in #33


Bluetooth: samples: Fix call to bt_audio_codec_cfg_get_chan_allocation

The function takes three parameters now. Pass "false", which should retain the old behavior.

Duplicate of #74266


Document App - enable relative image paths

To Do
docs app isn't yet enabled to relative images paths: https://github.com/eclipse-tractusx/portal-assets/pull/220
Enable relative image paths

@evegufy  do we need this story still ?

@MaximilianHauer yes, would be nice

would make step 3 obsolete https://github.com/eclipse-tractusx/portal-assets/blob/main/docs/admin/Dev Process/How to contribute.md#adding-pictures
maintaining absolute links isn't intuitive for contributors. Also, when a PR updates a picture, the picture is currently only resolved once the PR is merge into main, that's again not intuitive.


Message without clientActivityId should show up

Background
Transcript generated by Chatdown does not have activity.channelData.clientActivityId.
Summary
In our Store.ts:337, we hide everything the user sent, but without clientActivityId. It was intended to hide postbacks.
But in fact, we shouldn't hide everything because generated transcript doesn't know about Web Chat.
Postback: activity with type === 'message', but not shown on the screen. Triggered by rich cards or Adaptive Card.
Proposals

Add channelData.postback = true

Chatdown currently don't support postback

Add channelData.clientActivityId to Chatdown

Chatdown should not know anything about Web Chat

This is going to be fixed in Chatdown #377.


function-instance lookup: retrieve function instance owner's workerId

Motivation
for administrative purpose, we need to know worker-owner of the function-instance. so, adding workerId along with function-stats to find out owner of the instance.

retest this please

retest this please


[todoist] sync todos in today journal note

I am curious to better understand the use you imagine of synchronization between todoist and logseq. Currently if I import all my todo in my agenda file this has the effect of postponing to today all of my dateless todos (someday / maybe) in todoist...
Is this the expected behavior ?

The new version adds the Logseq block position setting.


【fieryeyes】fe-service open api develop

This can be developed in other languages, such as python, node, php, rust...


Check failed: error == cudaSuccess (74 vs. 0)  misaligned address

when train on Maxwell GeForce GTX TITAN X , there was an error( [math_functions.cu:79] Check failed: error == cudaSuccess (74 vs. 0)  misaligned address) , I change cuda7.5 to cuda8.0 and cudnn to cudnn5.1 but it was not work. Then I change the convolution engine to CAFFE, it worked but the training speed was too slow. How to fix the problem, thx.

I have not met this error before, maybe there is something wrong with your caffe or cudnn?
you may try https://github.com/yonghenglh6/DepthwiseConvolution for speedup.

yeah，I also met misaligned address problem and have no idea. What's shocking me more is the GPU memory it costs,almost 11G. Even in my Titan X ,the batchsize could only be 1.


Nonce's are sometimes wrong

When converting the csv files to JSON before signing, the CLI is sometimes generating the wrong nonce, even on a wallet that has had no other transactions to it and only has one transaction in the set

I can't think of any reason this would fail for a single transaction, as I'm just using getNonce() from Stacks.js
I can see how this could be a problem if you are sending multiple transactions from the same multisig address, since the transactions (and therefore nonce lookups) are done in parallel, so you might get the same nonce for multiple transactions from that address. What I could do here is to add an intermediate function that caches the results of getNonce() for each address, and if we've already fetched the nonce from the network once, increment the last value instead of fetching again


Signing nwjs helpers with company ID

Hi,
First, thanks for the guide! Good work!
I didn't follow this guide but another one, it's possible that it is yours as well.
I had problems when trying to sign nwjs helper files with the company ID. I think I was getting "ID mismatch" at some point, either when building the pkg or when trying to upload the app to the store, I can't remember now.
Anyhow, currently I am signing helpers with their own IDs like this:
codesign -s 64MR5B73ZY -i com.intel.nw.helper --entitlements ChildEntitlements.xml --deep "activecollab-timer.app/Contents/Frameworks/node-webkit Helper.app"
codesign -s 64MR5B73ZY -i com.intel.nw.helper.EH --entitlements ChildEntitlements.xml --deep "activecollab-timer.app/Contents/Frameworks/node-webkit Helper EH.app"
codesign -s 64MR5B73ZY -i com.intel.nw.helper.NP --entitlements ChildEntitlements.xml --deep "activecollab-timer.app/Contents/Frameworks/node-webkit Helper NP.app"
codesign -s 64MR5B73ZY -i com.a51.activecollab.timer --entitlements ParentEntitlements.xml --deep "activecollab-timer.app"
Without this I couldn't complete the process before.
Did you have to change the IDs in helper's info.plists ?

Hi,
you are true, thanks for pointing that out !
I have updated the Signing the app page. The code now looks like this:
codesign --deep -s $IDENTITY -i io.nwjs.nw.helper --entitlements $CHILD_PLIST $APP_PATH"/Contents/Frameworks/nwjs Helper.app"

codesign --deep -s $IDENTITY -i io.nwjs.nw.helper.EH --entitlements $CHILD_PLIST $APP_PATH"/Contents/Frameworks/nwjs Helper EH.app"

codesign --deep -s $IDENTITY -i io.nwjs.nw.helper.NP --entitlements $CHILD_PLIST $APP_PATH"/Contents/Frameworks/nwjs Helper NP.app"

codesign --deep -s $IDENTITY -i $BUNDLE_ID --entitlements $PARENT_PLIST $APP_PATH

Feel free to reopen if needed !


Migrated BTP-Operator and upgrade operation

Description
Upgrading instance where svcat => btp-operator migration failed fails as well with
Error from process: invalid BTP Operator configuration: BTP Operator is about to be installed but is missing required configuration: missing required key manager.secret.clientid, missing required key manager.secret.clientsecret, missing required key manager.secret.url, missing required key manager.secret.tokenurl

Actual result

Steps to reproduce

Troubleshooting
This code location swallows an error:
https://github.com/kyma-project/control-plane/blob/cf176b1d7b16dcebb3d458793348aba787b700c9/components/kyma-environment-broker/internal/process/upgrade_kyma/btp_operator_overrides.go#L24-L27
Check if the CM with ClusterID from svcat is removed as part of the migration or if it exists even after. It's possible the ClusterID is necessary only for the migration and not afterwards, maybe the whole workflow can be simplified.

Check if the CM with ClusterID from svcat is removed as part of the migration or if it exists even after

only references to cluster-info ConfigMap are these RBAC related ClusterRole and ClusterRoleBinding
https://github.com/kyma-incubator/reconciler/blob/1ac41480d5166358ce72396dbdc17e447e86e090/pkg/reconciler/instances/scmigration/service_catalog.go#L164-L174
https://github.com/kyma-incubator/reconciler/blob/1ac41480d5166358ce72396dbdc17e447e86e090/pkg/reconciler/instances/scmigration/service_catalog.go#L189-L198
manually verified:
$ k get cm -nkyma-system cluster-info -o json | jq -c '.data'
{"id":"c4bc1911-8797-43c8-84b2-f235fe10c9b5"}

It's possible the ClusterID is necessary only for the migration and not afterwards, maybe the whole workflow can be simplified.

confirming it looks like the ClusterID is not used by the operator. The only place the helm chart uses ClusterID is sap-btp-operator-config ConfigMap. This is not mounted, nor injected to the Deployment, neither does the controller query this ConfigMap from the kube API.
I think it should be pretty safe to simplify KEB code then.


.wav File Format Corrupted on Import

Godot version
4.0.1
System information
Windows 10
Issue description
This was noticed on Sonniss's GDC assets that they're offering for free.
After importing a .wav file that was offered by Sonniss's GDC kit for this year, each file (attached) was corrupt (screenshot of file in dir explorer attached).
As per rights granted, the sound effect is mine to freely distribute how I see fit.  See license here.
UIMisc_User Interface Vocalisation, Robotic, Futuristic,_344 Audio_Organic User Interface_12.zip

Steps to reproduce

Download attached WAV
Extract into any directory
Copy file in to any project's directory

Minimal reproduction project
In my main project, this was an issue; as you can see with my screenshot.  However, in the minimal reproduction project (attached) it imported just fine.
Wav Issue.zip

Cannot reproduce on Ubuntu 20.04 (PulseAudio) on Godot 4.0.2 with my own wav file.
Your zip file did not look like a usable Godot project and UIMisc_User Interface Vocalisation, Robotic, Futuristic,_344 Audio_Organic User Interface_12.wav-1c3b98857a69f47850965dee5dbe927b.sample in imported/ could not be read.


"Pipelines retention has been streamlined. Please go to the project settings to configure."

Aside from the fact that the project settings page does not explain what exactly is considered "streamlined",  going to the project settings takes me to a set of values that I cant seem to edit.
I used to be able to override the default (way too short) values of 30 days. My permissions level has not changed for this team project.
Its not streamlining when you remove functionality. Streamlining is when you make an existing functionality usable with less work.

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

ID: 43a285f9-738d-9f76-4de0-a4c4ecf6f5f5
Version Independent ID: 9581a043-4873-bf0a-138f-85f6a61ae950
Content: Build and release retention policies - Azure Pipelines
Content Source: docs/pipelines/policies/retention.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

I encountered this as well. Branch-specific retention options may not be possible anymore.
However, I eventually figured out that retention settings are now editable within a release pipeline's settings, and that was good enough for me. Go to the release pipeline then click Edit then choose the 'Retention' tab.
Note that each stage of the pipeline has its own retention settings. Also I'm not sure if this works for the new multi-stage pipelines currently in preview.

I get the message when looking at individual build definitions

Clicking on the link takes me to the project settings, that are all uneditable.

despite being a project administrator

"Docs" may not ultimately be the best place to open an issue, but as a customer I cant (and frankly shouldnt have to) determine if the problem is that the program is broken or the documentation is out of date.

It looks like you've encountered an issue with the product itself, rather than an issue with the documentation. To make sure it gets in front of the right people, please submit your bug here.

It looks like you've encountered an issue with the product itself, rather than an issue with the documentation

The docs team says program issue, despite the referenced page being out of date, and the program change seems to be intentional as of sprint 150 (I think that's the #). This feels like swag and "issue closure hope".
Since the docs need an update anyway to describe how retention policy is supposed to be configured now, would you mind sharing that at some point before more of my builds disappear from history?
Transfer of issue reports between docs and products isn't a user or customer's burden. They are already burdened due to either confusion between docs and program or program defect. Adding to that doesn't do any good things for the relationship.

@WilliamAntonRohm - Despite the deflection attempt, the docs team still has some work to do on this, Reopen this issue until the documentation is updated properly and found to be matching the programs current state, and cc whomever is your manager at MSFT on this issue so this can be tracked.

The documentation is updated and will be live within the next 24 hours. Feel free to create a new issue if you have any more feedback. Thank you all for your feedback!

@chasewilson - i am not seeing any changes. The git history for this page shows the last time update was in May. Am I missing something?

I'm assuming you are talking about not being able to adjust the Release retention policies. In Azure DevOps you cannot adjust them. While I agree with you on this thread it doesn't seem to be a docs issue? have you reached out to the developer community for a feature request?

I'm assuming you are talking about not being able to adjust the Global Release retention policies. In Azure DevOps you cannot adjust them.

@chasewilson - I am talking about the screenshots depicted in https://github.com/MicrosoftDocs/vsts-docs/issues/4953#issuecomment-516648890. They are for the project, not the organization and are not editable. While they are part of retention settings, this document does not cover build specific settings very well.
There is a devcomm issue that is going nowhere and a proper support case that is also going nowhere. Due to that negligence on MSFT's part, I've lost the ability to make a hotfix for software in production because the deletion of the build histories took all our version control labels with it.

@chasewilson - please either reopen this request or point me to where the build (not test run, not release pipeline) retention settings are documented.

@StingyJack I'm running into the same problem and only the Collection Administrators have ability to change this. https://stackoverflow.com/a/58811077/124331
I'm not really a fan of this, I think it's too restrictive for a Project Administrator to lack the ability to change a project specific function.

@Stevoni - do you see this functionality covered or explained in any docs or release notes?
@chasewilson - same question for you


Intro

I am a young and energetic programmer with a strong passion for programming. I enjoy creating new things and solving complex problems. I constantly strive for continuous improvement and finding the best ways to tackle tasks. Developing high-quality and well-structured code is important to me. I am here to join a team and work on exciting projects that will enhance my skills and contribute to my professional growth.

more information should be added


_.initially() plus tests

Hiya,
In a conversation with someone on irc, they wanted to do something on a first call to a function and something else on any subsequent call to the same function. I thought it might be something useful and wondered if underscore would like it.
Whilst this is a pull request, I don't expect it to be pulled unless you want it ... nor do I expect it to be the best or final solution if you do. Please take a look and I'm happy if you do or don't like it. :)
Have fun and thanks for underscore ... I love it.
Andy

Yep -- lovely idea, but I really don't think this comes up frequently enough in real-world code to merit inclusion in the core library. Good for _.mixin() though.

Ok, no worries. I forgot about mixins so I might package it up separately (or if I think of any more I'll put them all together). :)


Explanation of README recommendation against this lib

I currently recommend using vanilla A-Frame and aframe-state-component with static templating over aframe-react.

Can you elaborate on this recommendation @ngokevin? Not suggesting it's a bad recommendation, but I'm curious on the rationale. As someone quite invested in integrating A-Frame & React, the key reason I see is that React lifecycle doesn't simply align with A-Frame's or Three's lifecycle.
Additionally, I'm happy to tidy & summarize any rationale provided and append it to the README in a PR. Seems worthwhile; we've been happily using this lib in production for over a year now.
Cheers.

I would love some insights in this as well... seems you are very experience in how to use a-frame.

lmk if you have more questions.
https://github.com/ngokevin/aframe-react#aframe-react

I recommend using vanilla A-Frame and aframe-state-component with static templating over aframe-react. React wastes a lot of cycles and incurs a lot of memory garbage. aframe-react is often abused where it is too easy to place 3D/real-time logic at the React layer, causing poor performance (e.g., doing React renders on ticks). Internally, React does tons of computation to compute what changed, and flushes it to the entire application. It is apparent React ecosystem does not care much about memory as most examples allocate functions and objects in the render method, and where immutables are popular. With only ~10ms per frame to do all computation, there is little room for React's massive system.


Logging from child processes in VectorEnv

Author @abhiskk: Currently there is no way to log from child process to main process during usage of VecEnv for training. That would be good to organize logging properly log into main process or have separate files for each child process.

Looks like logging is fine now.


Unexpected Error: column reference "_age_default_alias_0" is ambiguous

When running the following query:
MATCH ({n0:0}) MATCH ()-->() MATCH ({n1:0})--() RETURN 0 AS n2

I encountered the following error:
column reference "_age_default_alias_0" is ambiguous

I believe the query mentioned above is semantically and syntactically correct and thus no error should be thrown here.
I encountered this issue when testing queries against the apache/age:PG13_latest docker image.
Steps to reproduce
Run the following query and observe it throws an error:
MATCH ({n0:0}) MATCH ()-->() MATCH ({n1:0})--() RETURN 0 AS n2

Expected behavior
The query should run successfully
Actual behavior
The query fails with the error message column reference "_age_default_alias_0" is ambiguous.

The error message "column reference '_age_default_alias_0' is ambiguous" indicates that the column reference used in the query is not unique and could refer to more than one column.
In this particular case, it seems that the issue may be related to the use of the alias "n0" and "n1" for nodes in the MATCH clause. The alias could be conflicting with a default alias generated by the system, causing the ambiguity error.
To solve this issue, you could try using a different alias for the nodes in the MATCH clause, or using a different alias for the "0" value in the RETURN clause. For example, you could rewrite the query as follows:
MATCH (n:Node)-[]->() MATCH (n1:Node)-[]->() RETURN 0 AS result
Where "Node" is the label of the nodes you want to match. By using different aliases and specifying the label of the nodes, you can avoid conflicts with the default aliases generated by the system and resolve the ambiguity error.
If this does not solve the issue, you could try checking the database schema and ensuring that there are no naming conflicts or other issues that could cause ambiguity errors.

Thanks for looking into this @AbdulSamad4068!
But this doesn't seem to fix the error. After spinning up a brand new docker container and running just the following query:
SELECT * FROM cypher('graph', $$
    MATCH ({very_weird_name:0}) MATCH ()-->() MATCH ({another_weird_name:0})--() RETURN 0 AS the_weirdest_of_all_names
$$) AS (v agtype);

The same error occurs.


Improved UMP data fetching and error handling

What's this PR do?

Moves data fetching from the component level to the router level
Allows routes to wait for their parent route to finish fetching before they do their own fetching
Moves redirects outside components and into beforeEnter router hooks
Creates new error classes that can accept arbitrary metadata and a status code
Configures Sentry reporting to accept that additional data
Simplifies our error view
Simplifies page-view logging

Why are we doing this? How does it help us?
Right now, we have a messy in-component mixin that allows child routes to wait for their parent route before doing data fetching. This is messy and complicated as it requires passing down a parentRouteIsFetching prop and showing lots of loading wheels along the way. By moving data fetching out of components entirely, navigation won't be confirmed until data has been fetched. In other words, when a new route loads, it'll already have all the data it needs: no need for additional loading indicators. Additionally, it means the user won't see the "flash" of a route they're not supposed to be on (for example, if someone tries to visit /account/blast/ when they're not a Blast subscriber).
Improving error handling is beneficial in lots of ways. Obviously, it gives us more detail about problems users might be encountering. But by associating each error type with a status code, it means that if/when we want to do server-side rendering, we can send back proper status codes instead of 200s every time.
How should this be manually tested?
First, go to 1pass and find the note called "Sentry PR review" (I'm not sure what Sentry values are secret, so I just put them all in here). Copy those into your env-docker, replacing  with, you guessed it, your name.
Then, go to the donations project on our sentry.io site and filter by the environment specified above. Keep that tab open. Next:

make
make restart
Go to /account/ and click around a few routes, just looking for anything that's obviously broken
Assuming you haven't signed up for The Blast with your test Auth0 email address, put /account/blast/ in your address bar. Confirm that you eventually get redirected back to the account overview.
Without refreshing, open up your browser console and run console.log(window.dataLayer);. There should only be one userPortalPageview event, and it should be for "Account Overview," not "The Blast."
Open up static/js/src/entry/account/index.js and change !isVerified to isVerified on line 197 (we're going to force an error to occur). Wait for Webpack to rebuild the bundles, then hard refresh. You should get sent to an error screen. Wait a few seconds, then hard refresh that Sentry tab you've got open. There should be a new error logged in there -- something about accessing a protected route while not verified. If you click into that error and scroll down to Additional Data --> status, it should be a 403.
Undo the above change and wait for Webpack to rebuild
Lastly, log out via the top-right nav button, then put /account/ back in your browser. You should get redirected to a log-in screen.

How should this change be communicated to end users?
NA.
Are there any smells or added technical debt to note?
LESS.
What are the relevant tickets?
https://3.basecamp.com/3098728/buckets/736178/todos/2352589312
https://3.basecamp.com/3098728/buckets/736178/todos/2352588307
Have you done the following, if applicable:

[ ] Added automated tests?
[ ] Tested manually on mobile?
[ ] Checked BrowserStack?
[ ] Checked for performance implications?
[ ] Checked accessibility?
[ ] Checked for security implications?
[ ] Updated the documentation/wiki?

All those steps WFM!


Simple 3D: Can we have a built in Lighting system?

So I got a 3D game project that I intended to finish it with some interesting gameplay. But... I ran into a little big issue, It's lagging when I implement the lighting system into the game. Using the same technique as the Lighting Demos

The projects lag at only 10 of point lights... Which is pretty bad for a simple PS1 style games.
Can we have an actual lighting system for the extension? It would be great!

why tf is the sharktilities icon like that 💀

why tf is the sharktilities icon like that 💀

You are my whistleextension baby

why tf is the sharktilities icon like that 💀

Genuine answer: I added some blocks and experimenting with the extension at that time


Live Stream with TTML Captions Repeated

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
Latest
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
I am not building the project just using demo app.
Are you using the demo app or your own custom app?
Custom App
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
webOS6 and Chrome
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?

I will send through a manifest to test with license key.
What configuration are you using?  What is the output of player.getConfiguration()?

What did you do?

Played live stream with embedded TTML captions.
What did you expect to happen?
Captions to display as per older versions of Shaka Player. We do not have this issue in version: "shaka-player": "3.2.2",
What actually happened?

Captions are repeated and fill up the screen. They are not removed just appended to until the video is no Longer visible.

This issue is a duplicate of: https://github.com/shaka-project/shaka-player/issues/4301
Will close and follow this.


Refactor hash.go

Is your feature request related to a problem? Please describe.
Currently there are two issues with how hash.go is implemented.

The blake3 package does not implement a standard crypto.hash() interface. Currently we just use a special method for hashing with blake3 but this is bad and should be fixed asap.

GenericSequenceHash only hashes AnnotatedSequence objects, it should also hash Feature,  and Sequence objects.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Write a wrapper around the blake3 package we use that uses the crypto.hash() interface like all the other hash functions seen here.

Replace GenericSequenceHash with a new function called HashSequence that takes an io.writer and a crypto.hash function and returns a hashed string. AnnotatedSequence, Feature, and Sequence objects should also have a .Hash() method. .GetSequence() will come in handy here.

Describe alternatives you've considered
We could continue building features around this but it’s best to refactor and build off of much cleaner code.

This has been fixed as of PR #58. Closing.


C++ Intellisense extension doesn'twork

I had installed C++ extension and when I press CTRL + SPACE there are no suggestions for autocompleting started syntax, how could i fix that if it is possible?
I know there should be some language server
Remote OS: freebsd
Remote Architecture: x64
code-server --version: 3.41

Here is my version of code-server using linuxserver.io's build with OpenCV and clangd added. Install clangd extension from store and it works out of the box.
https://github.com/ghokun/code-cv

Here is my version of code-server using linuxserver.io's build with OpenCV and clangd added. Install clangd extension from store and it works out of the box.
https://github.com/ghokun/code-cv

my freebsd has no linux support enabled, is it compatible then, and i cannot run docker

my freebsd has no linux support enabled, is it compatible then, and i cannot run docker

Actually, I shared my configuration as an example. You can checkout Dockerfile and install corresponding packages to your environment.

As there is no feature or bug here, please file this instead at https://www.reddit.com/r/codeserver.
Although I believe @Morritz correctly answered your question.

Here is my version of code-server using linuxserver.io's build with OpenCV and clangd added. Install clangd extension from store and it works out of the box.
https://github.com/ghokun/code-cv

Do you have a prebuilt docker image? If not any chance you can publish one? TIA.

Do you have a prebuilt docker image? If not any chance you can publish one? Looking for a RPi4 to host the image. TIA.

Please take a look at this repository.
There is a dockerfile that you can use to build your own image locally. Also you can check provided docker-compose file, to see how to run (My image can be downloaded from ghcr.io/ghokun/code-cv).
I should mention that my image works for x86_64. I have not tested on a raspberrypi.