add telemetry test for customize metrics

add http only now

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
afa4dc3ac919b429374c879028678871e5f79dea
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
93e38471c3c0bd7e291207ce8d380021f35e1470
link
/test integ-telemetry-k8s-tests_istio

release-notes_istio
81f3226b539c4e4253f1340b882e6dfe8e5fec26
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
f0273ee02fb58b60fa4cb507aefff65e4b26e316
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
f0273ee02fb58b60fa4cb507aefff65e4b26e316
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
f0273ee02fb58b60fa4cb507aefff65e4b26e316
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
694d40379ae8befef1219ab3e4c8835222abeb46
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
c67347f7836dac4ef0f308758f8e36ffbc730000
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
c67347f7836dac4ef0f308758f8e36ffbc730000
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
c67347f7836dac4ef0f308758f8e36ffbc730000
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
52b1d578a6cb92979f1d3cd0494a3709861e8f4e
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@richardwxn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
52b1d578a6cb92979f1d3cd0494a3709861e8f4e
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
52b1d578a6cb92979f1d3cd0494a3709861e8f4e
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


xxl breakpoint size?

Hello,
First of all awesome framework, great job! I have a small suggestion, with the increased resolution of screens, it seems like 1200px as a max breakpoint is a bit too small. Bootstrap v5 introduces a new breakpoint (xxl) which is 1400px. I think this breakpoint could be a great addition as that it will be nicer on high resolution screens. I can help out with creating this.
Thanks!

Hey, thanks for bringing this up. Halfmoon auto-scales up everything when the screen size gets bigger than 1600px. You can see it in this image: Image link
Do you feel this removes the need for the xxl breakpoint you are suggesting? I would love some more opinions too if possible.

Only adding an extra extra large .container does not make sense to me. It has to be a full breakpoint if it is to be added.

yes of course not only for .container but for anything that gets a restricted widths based on breakpoints like .container.


Implement Data Size Cfgu Type

Suggestion
10kb
1mb
100gb
etc..
Motivation
No response
Context
No response

@davidmeirlevy could i work on it since i am also willing to work on a similar issue

Go for it :)

Go for it :)

could you please review it, thanks!


horizon: GitHub Releases should include ARM64 artifacts

Currently, Horizon debian/apt releases don't include ARM64 artifacts, we should at least include binaries for:

darwin-aarch64
linux-aarch64

Acceptance criteria:
the Jenkins pipelines for stellar-horizon-package-builder-new and stellar-horizon-promote-to-stable-new and soroban-package-builder build/promote the arm64 platform bin to debian/apt repo also.
The jenkins pipleline for stellar-horizon-docker-builder also builds and pushes an arm64 platform version of stellar/stellar-horizon image

Getting 403 forbidden when i go to the sites.


media_likes and invalid media id

Hello!
I get small bug in media_likes method.
My code:

response_media_likes = client.media_likes(media_id[i])

where media_id[i] =<PHONE_NUMBER>82350758_280756576,
return:

"{"meta":{"error_type":"APINotFoundError","code":400,"error_message":"invalid media id"}}"

But i get this media id in user_recent_media method. And I check this id in API Console:

https://api.instagram.com/v1/media/855639925282350758_280756576

and get:

HTTP/1.1 200 OK

Any idea?
Use rails 4.1.6, ruby 2.0
Thanks!

Ensure that the media item you are trying to get the likes doesn't belong to a private user.

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

I'm facing the same problem. Any news?


For completions of union type, get all possible properties

Fixes #6405 and #15428.
When providing completions for a union type, we will now iterate over all union members to get all possible properties, rather than just those common to the union. So for { a, b } | { b, c } we will give completions for a, b, c instead of just b.
The implementation of getAllPossiblePropertiesOfType could possibly be better, so it needs review from someone familiar with the checker.

thanks!


[21564] Update fastdds_profiles.xsd file location

Description

@Mergifyio backport 3.0.x

Contributor Checklist

[X] Commit messages follow the project guidelines.
N/A Code snippets related to the added documentation have been provided.
[X] Documentation tests pass locally.
[X] Applicable backports have been included in the description.

Reviewer Checklist

[x] The PR has a milestone assigned.
[x] The title and description correctly express the PR's purpose.
[x] Check contributor checklist is correct.
[x] CI passes without warnings or errors.

@Mergifyio backport 3.0.x


[appium-flutter-driver][java] cannot use click(), tap() or getText()

I am having issues using appium flutter driver with JAVA
tap	🆗	driver.elementClick(buttonFinder)

tap	🆗	driver.touchAction({action: 'tap', element: {elementId: buttonFinder}})

getText	🆗	driver.getElementText(counterTextFinder)

After I switchContext("FLUTTER") when I call click() or getText() on a FlutterElement element I receive <Method not implemented yet>
What would the correct syntax be for JAVA?
Thanks

May https://github.com/appium-userland/appium-flutter-driver/blob/main/example/java/src/test/java/example/appium/FlutterTest.java help?

May https://github.com/appium-userland/appium-flutter-driver/blob/main/example/java/src/test/java/example/appium/FlutterTest.java help?

Thank you very much, I will give it a try :)


HelmRelease OCIRepository

Looks like OCIRepository  as a format per HelmRelease is not recognised:
Example:
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: OCIRepository
metadata:
  name: vault-secrets-webhook
  namespace: flux-system
spec:
  interval: 5m0s
  url: oci://ghcr.io/bank-vaults/helm-charts/vault-secrets-webhook
  ref:
    semver: ">= 1.*.*"

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: vault-secrets-webhook
  namespace: vault
spec:
  interval: 10m
  chartRef:
    kind: OCIRepository
    name: vault-secrets-webhook
    namespace: flux-system
  values:
    replicaCount: 1
    debug: true
    configMapMutation: true
    secretsMutation: true
    configMapFailurePolicy: Fail
    podsFailurePolicy: Fail
    secretsFailurePolicy: Fail
  ref:
    semver: ">= 1.*.*"

I hope this is fixed with #11


Why format does work?

function isStringType(property, format) {
    console.log('isExpectedType => ', isExpectedType(property, 'string'));
    if (isExpectedType(property, 'string')) {
        if(!format) {
            return true;
        } else if(format === 'date' || format === 'date-time') {
            var date = new Date(property);
            if(date !== "Invalid Date" && !isNaN(date) && isNaN(property)) {
                return !(format === 'date' && property.length !== 10);
            }
        } else {
            // If format is specified but not special rules apply then validation is true
            return true;
        }
    }
    return false;
}

I'm wondering why code in else will be always return true, Is it should js regex test?

We are testing the rules associated with the string type.  It only has a date subset.  Any other text will pass as a string.
Effectively we are saying that if the property has a format value and it is unknown then it is a string. Any extra string formats would go in place of that else...


Update all button for all extensions, reload all updated extensions on restart

VSCode Version: 1.7.1
OS Version: Windows 7

Updating extensions becomes difficult as user needs to restart VSCode for each extension update.
Steps to Reproduce:

Click Update for all extensions with update available.
Click Reload for one of the updated extensions,  VS Code restarts.

Desired Behavior
VS code should reload all extensions which have been updated.
Actual Behavior:
Only the clicked extension is reloaded, remaining new extensions show update button.
User needs to update and reload each extension individually

Hmm, first, there is a little menu entry to update all in one step. Not sure if there is a problem with your installation, but even if you click every single one of them, when they are ready (you can tell if all show the blue reload button) you have to only restart once.
Actually, you even don't have to use that button, they all do the same, reloading the window. You can have the same effect using the command Reload Window via the command palette.

@kaiwood Thanks for providing help to @akankshagaur
@akankshagaur Please let me know if you still have issues with updating extensions. Reopen the issue with the concise problem.
Thanks


tf.gather produces zeros for invalid indices on GPU

Environment info
Operating System: Ubuntu 16.04 LTS (64 bit)
$ dpkg -l | grep cuda | grep ^ii
ii  libcuda1-361                                361.42-0ubuntu2                                             amd64        NVIDIA CUDA runtime library
ii  libcudart7.5:amd64                          7.5.18-0ubuntu1                                             amd64        NVIDIA CUDA Runtime Library
ii  libcudnn5                                   5.0.5-1+cuda7.5                                             amd64        cuDNN runtime libraries
ii  libcudnn5-dev                               5.0.5-1+cuda7.5                                             amd64        cuDNN development libraries and headers
ii  libcudnn5-doc                               5.0.5-1+cuda7.5                                             amd64        cuDNN documents and samples
ii  nvidia-cuda-dev                             7.5.18-0ubuntu1                                             amd64        NVIDIA CUDA development files
ii  nvidia-cuda-doc                             7.5.18-0ubuntu1                                             all          NVIDIA CUDA and OpenCL documentation
ii  nvidia-cuda-gdb                             7.5.18-0ubuntu1                                             amd64        NVIDIA CUDA Debugger (GDB)
ii  nvidia-cuda-toolkit                         7.5.18-0ubuntu1                                             amd64        NVIDIA CUDA development toolkit

$ find /usr/lib -name libcud\*
/usr/lib/i386-linux-gnu/libcuda.so.1
/usr/lib/i386-linux-gnu/libcuda.so.361.42
/usr/lib/i386-linux-gnu/libcuda.so
/usr/lib/x86_64-linux-gnu/libcudnn_static.a
/usr/lib/x86_64-linux-gnu/libcudnn_static_v5.a
/usr/lib/x86_64-linux-gnu/libcuda.so.1
/usr/lib/x86_64-linux-gnu/libcudart.so.7.5.18
/usr/lib/x86_64-linux-gnu/libcudnn.so
/usr/lib/x86_64-linux-gnu/libcuda.so.361.42
/usr/lib/x86_64-linux-gnu/libcudnn.so.5.0.5
/usr/lib/x86_64-linux-gnu/libcudart.so
/usr/lib/x86_64-linux-gnu/libcudart.so.7.5
/usr/lib/x86_64-linux-gnu/libcudadevrt.a
/usr/lib/x86_64-linux-gnu/libcudnn.so.5
/usr/lib/x86_64-linux-gnu/stubs/libcuda.so
/usr/lib/x86_64-linux-gnu/libcuda.so
/usr/lib/x86_64-linux-gnu/libcudart_static.a

$ python -c "import tensorflow; print(tensorflow.__version__)"
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcudnn.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally
0.10.0rc0

Steps to reproduce
In [23]: x = tf.constant([1.1,2.2,3.3])

In [24]: a = tf.constant(123,dtype=tf.int32)

In [25]: tf.gather(x,a,validate_indices=True).eval()
Gather_8: /job:localhost/replica:0/task:0/gpu:0
I tensorflow/core/common_runtime/simple_placer.cc:818] Gather_8: /job:localhost/replica:0/task:0/gpu:0
Const_8: /job:localhost/replica:0/task:0/gpu:0
I tensorflow/core/common_runtime/simple_placer.cc:818] Const_8: /job:localhost/replica:0/task:0/gpu:0
Const_7: /job:localhost/replica:0/task:0/gpu:0
I tensorflow/core/common_runtime/simple_placer.cc:818] Const_7: /job:localhost/replica:0/task:0/gpu:0
Out[25]: 0.0

In [26]:

You are correct.  The validation is always performed, since overhead was negligible.

To clarify: it works on CPU but not on GPU, right?  Unfortunately, while we always perform the checks on GPU, we never report those errors back to the user:
https://github.com/tensorflow/tensorflow/blob/c5f94b10bbb30e525fa3ca313e7ccb173040c90a/tensorflow/core/kernels/gather_op_gpu.cu.cc#L40
It would be great to fix this, but we didn't know how to do it in a performant fashion.

So what does the CPU version do? https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/gather_op.cc
I was not expecting a zero as return when I sent in a out of bounds index. NaN maybe but not zero.

@hholst80 The CPU gives you an exception independent of what you're using (True or False).  This is to avoid crashing.  NaN would be reasonable, but the real fix would be to get an actual exception to bubble back up to the CPU from the GPU.

I neither have the context for this bug, nor am I going to be able to get to this in a reasonable time frame.

I don't know enough about GPUs to solve this one.  @zheng-xq Can you triage?

This is an area that is contribution welcome. We cannot have GPU synchronize with CPU. There are a few ways:

Trigger a "trap" instruction on GPU, which triggers an interrupt on the host CPU.
Allocated a pinned memory on CPU, and write the error status from GPU in the kernel. During the launch, also schedule an asynchrous functor to check the status through "ThenExecute".

I'd love to see GPU doing the same thing as the CPU code is doing, but as I said, the flag is unnecessary since it does not do anything on neither GPU nor CPU (and this behavior is undocumented as well).
If the exception thingy from GPU is too hard to do right now just put a NaN here instead of T(0)?
https://github.com/tensorflow/tensorflow/blob/c5f94b10bbb30e525fa3ca313e7ccb173040c90a/tensorflow/core/kernels/gather_op_gpu.cu.cc#L41
Silent and undetectable failure is dangerous...

Here's an older issue that can be closed once this one is fixed: https://github.com/tensorflow/tensorflow/issues/3067

@hholst80: You can only put NaN into the output if T is a floating point type, so I'm afraid that the idea can't work for all types :(
@zheng-xq: Do you know whether it's possible to somehow signal an error in TensorFlow after OpKernel::Compute() has already finished? It seems that this might not be possible through the OpKernelContext, as it's only guaranteed to live roughly until the end of OpKernel::Compute().
From reading the Executor code at https://github.com/tensorflow/tensorflow/blob/00700f00fdf71baec1342d1afd7849e16fbd2a33/tensorflow/core/common_runtime/executor.cc#L1210 it doesn't seem like there's an opportunity to pass a Status from our asynchronous functor to the Executor, but I might be wrong here.

If someone really wants to have this kernel report errors, here are some more details:

Add non-default attribute so the kernel can optional synchronize with GPU and check errors.
A more TensorFlow way is to change the kernel AsyncOpKernel, and check the errors and call "done" through ThenExecute. That way, the current thread is released to do other work. But ops following gather still cannot issue.
Still use the sync OpKernel, schedule ThenExecute to check for the error. The down-side is the context is long gone at that point. So you can print out enough error message and crash the process with LOG(FATAL).

I will leave it up to the contributor/developer to choose from those. But it is important that by default, we don't synchronize and hold off other kernel launches unnecessarily.

Thanks!
I think the checking shouldn't be optional, otherwise users will keep running into problems, so that would rule out option 1.
Option 2 still blocks ops that depend on gather. I think we should try to avoid this if we can.
Option 3 sounds good, but a LOG(FATAL) would crash the interpreter that the user might be running TensorFlow in, which isn't very nice. (But maybe this is easy to fix?)
I've also thought of writing a CheckGather op, which performs the index checking separately from Gather. It could be launched alongside Gather from a Python wrapper.
This could either always run on the CPU, or synchronize with the GPU, possibly as an AsyncOpKernel as you've explained.
Maybe the cleanest option would be to modify Executor slightly to add support for asynchronous error reporting.
For example, we could add a Status protected by a mutex to Executor that's specifically designed for asynchronous error reporting. The op's Compute method could then pass the Status into a callback that's executed as part of the CUDA stream. The Executor would then check the Status after it synchronized the computation.
I'm not sure how useful this change would be for ops other than Gather, though.

I've talked to my colleagues about modifying executor. It is trickier than we would like.
At this point, I think option 3 with LOG(FATAL) is the path with the least potential problems. I agree that it is not clean. But there are plenty of CHECK in TensorFlow, which does essentially the same thing. So if we put debugging information in that error message, perhaps it is more useful to people than it is today.

@zheng-xq Actually we've done quite a bit of work to remove LOG(FATAL) uses that can be triggered by the user.  The policy is that they should all be unreachable.  It would be a shame if gather did this.

In that case, maybe we could explore the async error reporting as @ibab mentioned. The tricky part is that we need to hold executor to wait for all the error checks to finish at the end. Otherwise, the run could finish  successfully before the async error checking. And we need to be very careful that we don't cause a deadlock.

I ran into this issue today (on v1.0).
If no fix is on the horizon, I suggest either removing the validate_indices option or mentioning in the API docs that it works only on CPU for now, as that helps with debugging (otherwise people will think their problem lies elsewhere, trusting that the indices must be valid).

@Fenugreek Interested in contributing a doc fix?

@girving Yes. A bit busy today but will get back by early next week.

@girving I feel a little stupid but after 15+ minutes of looking I can't find where the docs for tf.gather live. They're not in python/ops/array_ops.py. Any tips?

tensorflow/core/ops/array_ops.cc

Cool, thanks for the pointer @josh11b . I am hoping to submit a pull request for the doc fix in a day or so, looking to be consistent with docs elsewhere Re: GPU vs CPU differences/limitations.

This is my proposed addition to the tf.gather doc in array_ops.cc:

validate_indices: DEPRECATED. If this operation is assigned to CPU, values in
indices are always validated to be within range. If assigned to GPU,
out-of-bound values in indices currently result in output values of 0.

Given @hholst80 's comment on Aug 5, 2016 above, and confirming by looking at the CPU and GPU .cc source, the above seems the most complete doc. We may prefer to avoid saying that current fallback value on GPU is 0, in case people start depending on it.
The above fix is in my fork at github.com/Fenugreek/tensorflow. I expect there will be comments resulting in changes, so I am holding off making a pull request.

Looks good.  Maybe change the GPU sentence to

If assigned to GPU, out-of-bound indices result in unspecified behavior (currently the result is 0, but this may become an error in future).

Ok, changed it as so and put in the associated pull request #8646 .

Related bug with the same "how to signal errors on GPU" problem: https://github.com/tensorflow/tensorflow/issues/3638.

What about unifying the GPU and CPU implementations of gather by always returning 0 for out-of-bound indices, then having a separate op which checks indices with a CPU-only implementation. That way you get consistent behavior, error propagation if desired and a clean interface.
That would also allow "conditional gather"-type operations relatively easily, where a default value is used for indices that are out of range, such as:
tf.gather(xs, indices) + (indices >= tf.shape(xs)[0]) * 2.0
At the moment conditional gather operations like this is tricky on the CPU, since error checking is always done.

My idea was that there are two ops. The gather op is changed to be forgiving, i.e.g both GPU and CPU it returns zero whenever an index is out-of-bounds. A separate op (say "check_indices") with only a CPU implementation determines whether the gather is "valid" (i.e. no out-of-bounds lookups, in the same way that the current CPU implementation does (iiuc).
For some applications, forgiving gather is exactly what you want. It is simple to turn this into something which uses a user-specified default value instead of 0, using something like the code snippet above. Afaict, forgiving gather is currently quite hard to effect in tensorflow.
tf.gather can be implemented in terms of forgiving gather and check_indices. This preserves the current CPU behavior, and extends that to the GPU case, fixing this bug.

A separate op (say "check_indices") with only a CPU implementation ...

If this op is forced to be run on CPU, it could slow down the computation due to additional data transfers between CPU and GPU. I can't assess the impact this might have, but this effect should be considered.

Yeah, I agree that's something to bear in mind. The motivation for my suggestion was just that: (a) I think it's uniformly better than the current situation where the GPU implementation is nominally "incorrect" (doesn't check indices); and (b) I think the current GPU behavior ("forgiving gather") is actually a great op to have.
The procedure to check indices could consist of an op which outputs a boolean (whether the indices were valid) and has a GPU implementation, and a CPU-only op which takes that and actually raises the error. This avoids any large GPU to CPU transfer.

I am currently using this quirk of the gather op because I want to have identically 0 tensors if the index is out of bounds. Is this bad from a performance perspective?

Hi @hholst80!
We are checking to see whether you still need help in this issue . It will raise error in CPU and render zero in GPU .Attaching Gist and Reference .Thanks!


AdapterAbstract: added buffered mode

When cache is being used together with DB, allow
the adapter to simulate consistency within the
single connection

[x] exceptions on blacklisted functions? (increment, decrement, add, etc.)
[x] buffered handling for memcached extension

:+1:

:white_check_mark:


body: opt-in logging button

Yes please & thanks. I unfortunately have a bunch of video already uploaded to comma's datacenters now until I thought to check and realized it. As a stopgap measure I have added the following into /etc/profile to at least prevent uploads.
export BLOCK="uploader"

I wish I had a way to delete them but I couldn't find a way.


[ID-823] Split up profile page

https://broadworkbench.atlassian.net/browse/ID-823
Prefactoring for further changes to the PersonalInfo section of the Profile page.
This moves Profile to the src/auth directory and breaks it up into multiple modules: one for each tab and one for the overall profile. src/pages/ProfilePage wires the Profile component into navigation.
There is one user facing change here: the "What is your area of research?" heading is changed from an h2 to an h3 since it's a subsection of the profile.
Side note: maybe "identity" would be a better name than "auth" for the feature area directory?

I do kind of like "identity" as a directory name vs "auth". Looks good overall though!


Type java.util.List of field X is not supported

Hi,
I'm getting following error. How can I solve this?
Type java.util.List<X> of field X is not supported
Note: All my classes extend RealmObject.

Lists of @Parcel annotated objects are absolutely supported.  Is X annotated with @Parcel, with the proper Realm configuration?

Thanks for your answer. I found that the problem was from another thing. Sorry for reporting this.


Mutiroot workspace: creating PRs for different workspace should not reuse description webview

Create a multi root workspace with two repositories
Make changes to both repositories and create PR
Creating the first PR opens a description webview
Creating the second PR for another repo updates the content of the preview PR

IMHO in multi root workspace, PRs for different repos should not share the same webview.

Duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/3058


Switch to DTOs in POST

Every Incoing JsonObject from a Post should be replaced with a fitting dto and instead of getInteger or similar use the DTO methods.

looks good for now


Terminal auto types random text

Issue Type: Bug
I am trying to debug a powershell script in VSCode and as soon as I enter the parameter values, I get random auto entered text (see attached photos).

I attempted to ctrl+c but that still continues to auto enter text.
Only way to stop this is by terminating the terminal session.
VS Code version: Code 1.55.0 (c185983a683d14c396952dd432459097bc7f757f, 2021-03-30T16:01:05.981Z)
OS version: Darwin x64 20.3.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
32.00GB (5.17GB free)

Process Argv
--crash-reporter-id bcf56f26-dca7-4c02-b3c2-69e2861263d0

Screen Reader
no

VM
0%

Extensions (33)

Extension
Author (truncated)
Version

terraform
4op
0.2.1

better-comments
aar
2.1.0

aws-toolkit-vscode
ama
1.22.0

vscode-bicep
Azu
0.1.37-alpha.gf88c6d95ad

armview
ben
0.4.5

bracket-select
chu
2.0.2

bracket-pair-colorizer
Coe
1.0.61

bracket-pair-colorizer-2
Coe
0.2.0

gitlens
eam
11.3.0

prettier-vscode
esb
6.3.1

terraform
has
2.9.1

azure-pipelines
ms-
1.183.0

vscode-azureappservice
ms-
0.21.2

vscode-azurefunctions
ms-
1.3.0

vscode-azureresourcegroups
ms-
0.3.0

vscode-azureterraform
ms-
0.3.2

vscode-bicep
ms-
0.3.126

vscode-docker
ms-
1.11.0

csharp
ms-
1.23.9

vscode-dotnet-runtime
ms-
1.0.0

vscode-aks-tools
ms-
0.0.8

vscode-kubernetes-tools
ms-
1.3.0

python
ms-
2021.3.680753044

jupyter
ms-
2021.5.702919634

remote-containers
ms-
0.166.0

azure-account
ms-
0.9.7

azurecli
ms-
0.5.0

powershell
ms-
2021.2.2

azurerm-vscode-tools
msa
0.15.0

vscode-yaml
red
0.17.0

markdown-preview-enhanced
shd
0.5.17

vscode-ansible
vsc
0.6.0

arm-params-generator
wil
1.0.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt678:30270856
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30276681
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
pythonvspyt639:30281910
pythontbcf:30265426
wslfolderdoccf:30282075
vspre833cf:30267465
pythonptprofiler:30281270
vshan820cf:30276953
pythondataviewer:30283453

Performed the following troubleshooting steps:

Restarted app
Restarted laptop
Deleted powershell extension and reinstalled
Deleted VSCode and Extensions from laptop and reinstalled along with Powershell.

The issue only occurs when I attempt to debug a powershell script

IM SUFFERING OF THIS 2 WEEKS HORRIBLE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Been suffering for weeks myself. Not sure if this is vscode or vscode-powershell bug tbh. I've only been able to repro in Powershell integrated terminal while using my debian-based devcontainers. PowerShell integrated terminal on Windows directly hasn't shown this yet, but I guess they work fundamentally different since pasting in devcontainer terminal is super-slow.
Resizing vscode windows can sometimes stop it.

Open a .ps1 file to start the PowerShell integrated console
Paste invoke-pester ./Samples/demoIssue1891.tests.ps1 -FullNameFilter "get-emoji" -Output Diagnostic
Add another double-quote after get-emoji so it becomes ...meFilter "get-emoji"" -Output..... Problem will hopefully occur.

oh i was about to say that I forget to say that im using INSIDER version... but also in stable you saying...
so it can be related to usign remote extension? i use it also for wsl2

I'm seeing lots of similar random string -- that look like terminal control strings -- 24;17R --- etc.
this occurs primarily when in a pwsh session or running a pwsh script.

yeah, very annoying!

It only happens when using the integrated terminal for me. Tried starting in a temporary terminal, no extensions, reinstall, nothing works.

just to be clear, I'm seeing this with PowerShell Core sessions only. I've also seen this on plain old macOS using pwsh core 7.x latest too.

im 2 weeks getting this horrible bug... in under wsl2...
tip: fast way to get the problem
start terminal
type
cls   enter
u get             ;1R

I've seen this happen in the non-integrated terminal. It was just a normal VS Code terminal running pwsh, with no PowerShell extension installed.

I know he's an assignee but paging @Tyriar if he's aware of any recent changes that may be related.

Sorry about this, I plan to look at it soon. This might workaround the problem:
"terminal.integrated.localEchoLatencyThreshold": -1

Sorry about this, I plan to look at it soon. This might workaround the problem:
"terminal.integrated.localEchoLatencyThreshold": -1

🎉🎉Thank you! That solved my reproducable scenario. I might finally be able to work again! 😄

Thanks @Tyriar!

This is again caused by writeSync which was what caused the issue a couple of weeks ago, flushing the output using it is causing a double write of the cursor report response and pwsh handles an unexpected cursor report by just echoing it.
terminalProcessManager.js:87 on before data
terminalInstance.js:851 xterm write: "\u001b[6n"
terminalProcessManager.js:399 process write: "\u001b[11;1R"
terminalProcessManager.js:399 process write: "\u001b[11;1R"

@connor4312 I needed to disable flushing of output as it's no longer possible to do this without adding async everywhere which would be a huge change to the addon. It's not clear what the problem is getting fixed in f82ff2194fc81ed0d0ca87018fc5526dfc1946e8 and b97bb4e8b95210427d615a470161b795b894991c is but I'm pretty sure those issues won't be worth than this one which basically renders pwsh unusable.

I think the no-oping you did in https://github.com/microsoft/vscode/commit/14b07fe6e752926d51ae6d6c19ddcac3c6400900 is the best we can do for now. We'd really need https://github.com/microsoft/vscode/issues/115949 in order to handle this properly without writeSync.

Sorry about this, I plan to look at it soon. This might workaround the problem:
"terminal.integrated.localEchoLatencyThreshold": -1

Thank you @Tyriar.  This did the trick for now.

YES THIS SOLVED for me
wsl2 pengwin... powershell 7... vscode insider... win insider

I'm seeing similar issue again while still using the @Tyriar's workaround in settings. It doesn't start at random in existing consoles like the original issue, but it starts after reloading window in the same devcontainer.

In devcontainer with PS integrated console open
Reload Window
VsCode starts a new PS integrated consoel, but auto-focuses on ": pwsh" terminal which is the original console from step 1. In this console, the control characters keep going for a while. Sometimes 2sec, sometimes more.

This was not happening after the workaround was provided. Changes in latest vscode?
Now running VSCode Stable 1.56.2 w/vscode-powershell 2021.2.2

@fflaten should be fixed with https://github.com/microsoft/vscode/issues/123803


Developer-guides, "Atomic units" replacement with "Piconero(j)"

After translating the deamon developer-guide and reading about the denomination, i figured out we were refering to "atomic units" which are not defined anywhere else.
So i suggest to change this and use the official denomination of piconero(j).
This PR include changes in all files for all languages, and an additional link to the moneropedia denomination page for the "heading note" about it.
I even changed it for Polski, but this will need a quick review from @zofiazinha to make sure something is not inconsistent.

In such a case, i believe i have to update moneropedia articles: create an atomic unit entry and cross-refer denomination's piconero and it as the actual equivalent?

Done. Let me know if we close this one.

Closed as we will implement #706 instead.


Add Rust scaffolding to the project

Fixes #1
Add Rust scaffolding to the repository.

Cargo.toml and src/lib.rs

Add Cargo.toml to define the Rust project and its dependencies.
Add src/lib.rs with a simple function pub fn hello() -> String { "Hello, world!".to_string() }.

CMakeLists.txt

Modify CMakeLists.txt to include Rust support by adding find_package(Cargo) and add_subdirectory(src/rust).

src/rust/CMakeLists.txt

Add src/rust/CMakeLists.txt to build the Rust library using CMake.
Add find_package(Cargo REQUIRED) and add_custom_target(rustlib ALL COMMAND cargo build --manifest-path ${CMAKE_CURRENT_SOURCE_DIR}/Cargo.toml).

conanfile.py

Modify conanfile.py to include Rust dependencies in the requires list.
Ensure Rust dependencies are installed during the build process.

README.md

Update README.md to include instructions for building, running, and testing the Rust library.

For more details, open the Copilot Workspace session.

This pull request introduces Rust support to the project by adding new dependencies, build instructions, and example code. The changes include updates to the CMakeLists.txt, Cargo.toml, README.md, conanfile.py, and the addition of a new Rust source file.
Rust Integration:

CMakeLists.txt: Added find_package(Cargo) and add_subdirectory(src/rust) to include Rust build configuration.
Cargo.toml: Created a new Cargo.toml file to define the Rust package and its dependencies.
src/rust/CMakeLists.txt: Added a new CMake configuration file for building the Rust library.
src/lib.rs: Added a simple Rust function hello() that returns a greeting string.

Documentation Updates:

README.md: Added instructions for building, running, and testing the Rust library.

Dependency Management:

conanfile.py: Added Rust as a dependency in both the requires and tool_requires sections. [1] [2]


Add option to disable RBAC and ServiceAccount

Adds rbac.enabled to control whether ClusterRole and ClusterRoleBinding are created or not
Adds rbac.namespaced to control whether Role/Rolebinding or ClusterRole/ClusterRoleBinding are created or not
Adds serviceAccount.name to control whether ServiceAccount is created or not
Adds tests for all combinations of new settings

Besides the namespaced property, these options are all the standard options that helm create provides out of the box.
The use case for disabling rbac and serviceAccount is some cloud providers don't allow RBAC related components being created. Specifically in our case, Google Cloud Marketplace does not allow any RBAC be created and will create them via another mechanism.
The use case behind the rbac.namespaced setting is that we want to deploy a different Traefik per namespace so our chart is more self-contained and secured. Also, our operations team locks down the cluster so we can't deploy cluster level components. Setting rbac.namespaced=true and setting providers.kubernetesIngress.namespaces=mynamespace in the Traefik config allows us to reduce the permission of Traefik and have it watch only our specific namespace.
To reduce duplication, I put the if/else for namespaced inside the clusterrole and clusterrolebinding. I can duplicate them to separate role/rolebinding files if you prefer that instead.

Any update @mmatur ?


⚠ Samsung has degraded performance

In 6acae09, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1962 ms

Resolved: Samsung performance has improved in b1832e5.


swagger-core support for 3.0.0-rc1

Need to enable the model reading and schema generation for the rc1 spec

implemented in #2215 #2212 and further work


Order of records in tableview;

Changing the order should request the data with the order applied to the query before the limiter.

Table sort requests will now be sent to the backend.
If you show 99 out of n records then the 99 records will be retrieved after sorting.
Ready for testing and documentation.

Added to documentation


Prevent Other Repos from Creating Discussions

I have found that anyone can spam your discussion board if they use the wrong repo ID when configuring their instance of giscus.
Is there a way to block this or have more granular control over which repo the bot is authorized to post in?
I ask because some people copy a template that I have that is public and end up using my repo ID and then all of their test comments appear in my discussion.
I think this might be related to this page and probably the reason it was set up.
https://github.com/orgs/giscus/discussions/1298

https://github.com/giscus/giscus/blob/main/ADVANCED-USAGE.md#origins

Thank you so much!  Sorry I didn't see that!


Category Balance Notifications

I had an idea while falling asleep last night.
We should add category balance notifications after transactions have been added. This would basically notify the user with "You have £X left in X category" after a transaction was added to it.
This could be extendable to work with different providers such as:

Email
SMS (Twilio)
Pushbullet
More?

Any suggestions/reservations?

💥 working nicely

Going to leave this at Pushbullet for now. We can add more as we come to them.


Points<PHONE_NUMBER> and<PHONE_NUMBER> are missing in point.json

Points<PHONE_NUMBER>(衛生福利部花蓮醫院豐濱原住民分院) and<PHONE_NUMBER>(連江縣立醫院) are in the raw data but missing in point.json

I used to add hospitals in the map. But one of them said the masks were only for internal use and requested to be removed. So I removed all hospitals.
Ref: https://m.facebook.com/story.php?story_fbid=1436822259824566&id=282921805214623

Ok, thanks.


Feature request: Authentication scheme for systems long-term credentials

I'm trying to integrate Firestore with Weaviate, similarly to how it's done with Elastic Search. However, Weaviate seems to only support authenticating with a short-term JWT token.
I couldn't find an easy programmatic way of generating JWT tokens that Weaviate would accept. In my use case I was using WCS which is using SeMI Auth OpenID provider.
A simple mechanism could be supporting a static username/password to authenticate to Weaviate or to utilize mTLS for even higher levels of security. It was unclear whether this is already supported in Weaviate and the client libraries. For Firebase functions we have to use Javascript so that's what I tried using.
The core requirement here is to have some long-term credential that can be used to authenticate to a public Weaviate instance.

Looks like the Python Client does have a mechanism for refreshing the Access Token automatically for you if you supply it with your username/password: https://github.com/semi-technologies/weaviate-python-client/blob/5f6c93903dbc242d2df03a7ba9fd4fce0ceaf25b/weaviate/connect/connection.py#L166
and https://github.com/semi-technologies/weaviate-python-client/blob/5f6c93903dbc242d2df03a7ba9fd4fce0ceaf25b/weaviate/wcs/crud_wcs.py#L78
So that might be workable for usage with Javascript client as well, however doesn't look like the Javascript client has similar logic yet. Sadly, firebase functions only support javascript or typescript.

Added the backlog label to be able to vote for this on the roadmap. A vote for this issue is not a vote for a specific solution (we'll figure out what the right solution is when the time comes). But rather a vote is a feature that satisfies this:

The core requirement here is to have some long-term credential that can be used to authenticate to a public Weaviate instance.

Would firebase work with a self-hosted Weaviate instance as well or would it have to be a Weaviate-Cloud-Service provisioned one? The latter would make this a bit more complex because then we'd also have to take the auth for the WCS into account. But if self-hosted works, then we could build the following:

Weaviate will support basic auth, user/pwd combinations can be specified using env vars
User self-hosts Weaviate with the above auth configured and exposes it on the internet
The firebase connector uses basic auth to authenticate against the instance with the credentials set in the first step.

Probably not the prettiest solution, but one that would be minimal effort to build.

Here are the requirements for Firebase integration:

Weaviate exposed on the internet so it's accessible from Firebase functions
Utilize the Javascript client so the JS client needs to be able to support the authentication mechanism

So yes self-hosted would work because this is just an example integration. That being said, the blog I wrote did use WCS but with authentication disabled, which was fine for demo/example usage.
I do see value in starting with basic auth as a simple option to expose a self-hosted Weaviate on the internet. I'm sure there are people who expose Weaviate publicly without really understanding that anyone can access their database. This option should make it very easy for self-hosted WCS users to at least prevent anonymous users to access the DB without requiring a full fledged OIDC server. I don't like dealing with OIDC unless I really have to.
Some customers hyper focused on security have very specific requirements on what kind of credentials are acceptable and what not. Maybe a guide that shows how to setup mTLS would be helpful later. Would mTLS work already? I think you could deploy a TLS proxy in front of Weaviate that does mTLS? What do you think? Each client would get it's own unique cert that could get revoked and traffic would be encrypted as well.

+1, need  "basic auth, user/pwd combinations can be specified using env vars"

Thanks for the feedback, please upvote the first post in this thread so your "+1" is counted :-)

Hi @samos123,
The JS client supports authentication with username/password with automatic refresh since the latest version. Java and go clients should follow in the next weeks.
We do not support using env variables, is that something that people would prefer?

Nice! I think supporting env vars isn't important since you could easily do that yourself while calling the client. It does seem common to support env vars though. E.g. AWS and gcloud all support providing credentials through env vars directly.
OIDC is painful to setup and requires yet another component that can break. Some users just want a simple password or username/password to protect their public weaviate instance. Especially at larger enterprises having to integrate with corporate OIDC provider can be a very tedious and painful process. I've setup Dex and used it as an OIDC provider for k8s in the past.

Totally understand, just want to highlight what we can support.
Another option that does not involve configuring an OIDC provider/server yourself would be to use our auth server with your own weaviate instance, like in this example docker-compose file. Then you can authenticate with your WCS username/pw (client credentials will hopefully be added to WCS in a bit).
Obviously that is nothing that works in a large enterprise, but for a small setup it might be an easy start.

having a user/password or a build-in key mechanism would really helpful!


Docker

Not sure if you are aware, but this not working via https://hub.docker.com/r/scireum/s3-ninja/
docker pull scireum/s3-ninja
Using default tag: latest
Error response from daemon: manifest for scireum/s3-ninja:latest not found: manifest unknown: manifest unknown

@wifilocator we have no latest image tag name, see PR
use:
 docker pull scireum/s3-ninja:7.1.1

latest tag is now available:
docker pull scireum/s3-ninja


Undefined property: stdClass::$disposition

I have an error when fetching the body of the email. How can I solved this error "Undefined property: stdClass::$disposition"

I had this issue while ago when trying to fetch the messages to, but assumed it was a character error from a specific message, cause' i tried the limit Method and the error stopped.
Try to limit your query to 10 e-mails for example, and see if the error happens again
$oFolder->messages()->all()->limit(10)->get();

ErrorException
Notice: Undefined property: stdClass::$disposition
src/IMAP/Message.php line 721
Need to check $structure->ifdisposition first

Hi i have same issue :
Undefined property: stdClass::$disposition
httpdocs/vendor/webklex/laravel-imap/src/IMAP/Query/Query.php:223
i see girvydas working with this problem , I will be following the update

Could you release package update? It's a critical bug.

I'm still experiencing this bug using the latest version. Am I the only one?

It's already merged in 1.4.4 version.

@girvydas that's what I thought, and I also saw the PR that was fixing this getting merged in. I updated again this morning because I noticed a new release and to ensure I'n on the latest.
This is from the lock file on the server, we are definitely using 1.4.4

And then in our error logs for today:

We use horizon to process mailboxes every minute. I know horizon is a long-lived process, I've stopped and started it multiple times trying to debug this, and horizon:terminate is also part of our deployment so I don't think that's the issue.
While I'm here, I've noticed us getting errors for emails that are not UTF-8. (Trying to insert the body_html in to our database) - Is this something that the package can help with in terms of enforcing the UTF-8? If not no worries I'll continue looking in to it


[imgui-sfml] Fix usage

imgui-sfml redefines the macro ImTextureID in imgui to match the correct pointer type, which leads to inconsistent ImTextureID type errors when users use imgui-sfml and imgui at the same time.
After discussing with upstream, remove the redefinition code of ImTextureID in imgui-sfml to fix this issue.
Fixes #21530.
Already tested the usage.

Makes sense! Thanks for confirming with upstream!


feat: log a warning message if a page is being prerendered with runtime environment variables

closes https://github.com/sveltejs/kit/issues/10008
Log a Warning message if a page is being prerendered with the runtime environment variables to prevent possible mistakes and leaking private data from env

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

closing in favour of #11277


Add default placeholder to the slug (#7)

Unfortunately, we can't reference the files in the /api folder since they're private and not part of the code sent to the users. We'd need to create a new endpoint just for that, it'd be too much hassle.
I've changed it to just a static string, what do you think?

Ah, very true. A static string would work best in this case. LGTM.


PCM deployment is overriding default behavior of SSM Sessions

Hi,
When deploying pcluster-manger the following substack performs an update of the SSM-SessionManagerRunShell document by overriding the default document with an hardcoded version. As documented here, SSM-SessionManagerRunShell document controls the default SSM sessions settings for the account at the region level.
I have the following concerns:

The default SSM session settings are overwritten with a static default
The updated document changes the default SSM user for all nodes where /opt/parallelcluster directory is found. Users  expect the default ssm-user to be used while they will automatically land on the cluster nodes as the default cluster user. Also if this customization is triggered on arbitrary nodes where for some reason /opt/parallelcluster dir is present, the execution will just fail.
The command in the doc relies on some internal pcluster variables that might be changed at some point with the risk to break ssm session access.
[minor] The change is even persisted when deleting pcluster-manager stack

Can you share details on why this is necessary and if this configuration can be done at a more scoped level?
Cheers,
Francesco

A few notes here:

There's no way to specify the user to connect as when you run SessionManagerRunShell - the default is ssm-user
There's also no way to specify a separate SSM document when you do the shell connect. You need to use the default.
The script will only change the user if it detects the /opt/parallelcluster/cfnconfig file. If not it'll keep the default behaviour.

I wish there was a better way to do this - maybe raising a feature request with the SSM team to get either the user as a parameter or the document but for now this is the best way to ensure the correct user is set.

Thanks Sean! What is driving the need of having to switch user before the session is started vs starting the session as the default ssm-user and then performing the switch user?

AWS has landing zone accelerators that also creates/modifies the default SSM-SessionManagerRunShell document to enable encryption, centralized logging and few others according to security best practices. Also they have SCPs to deny access to that document. If we deploy pcluster managers in those environments, the stack creation fails because the lambda that modifies the document fails to execute.
I have a couple ideas that I think might work:

I think it would be better to create a whole new session document for pcluster-manager purposes and enforce users to use that when connecting through ssm
Or the same  linuxcmd can be appended to /etc/profile so it gets executed on any shell logins. Or any other similar approach (init scripts) would work.

@joshvmaws Is there anyway to point to a specific document when connecting? The link we're using is:
https://[region].console.aws.amazon.com/systems-manager/session-manager/[instance_id]?region=[region]

When we implemented this (Nov 2021) there wasn't a way to select a specific SSM document when connecting. Maybe this has changed?

In CLI there is a parameter you can pass --document-name. There must be a corresponding parameter for the web session that I haven't found yet.
There is another way of achieving this. We can update the "linux shell profile" in session manager preferences.


Store S3 keys in temporary files

The S3 mocking system currently stores the contents of keys in memory, causing excessive memory usage and/or MemoryErrors when storing large amounts of data.
This PR stores each key in a SpooledTemporaryFile with a maximum size of 16 MiB. Thus, keys are held in memory with little to no performance penalty until they exceed 16 MiB, at which point they're flushed to a temporary file on the local disk.
N.B.: this has no real effect if a large number of files under 16 MiB are written. Perhaps a smaller maximum size is warranted?
Fixes #395 and https://github.com/localstack/localstack/issues/682

Coverage decreased (-0.2%) to 92.325% when pulling f15f006f7834ab69a5ee38ae30955fdc3863562e on dargueta:s3-spooling into ed861ecae1039a048a6350a4ff832ef094cdf2c2 on spulec:master.


Refactor loop filter types

refactor loop filter types to core
rename TracksFilter to TrackFilter

Pull in loop filter refactor from #215


Possible problem when parsing floats

Since parse(float, currency, _opts) uses * 100 hardcoded, there's unexpected behaviour when using currencies like TND, where the conversion to the smaller unit (milim or millimes) is * 1000.
I haven't looked into other ones and just stumbled upon this while reading the code, but I have the feeling that there could be more currencies with that kind of problem.

There are a few currencies that don’t follow the "standard" pattern of subdivision into 100 subunits.
I don’t have the time right now to work on those variations as I don’t work with those currencies.
Pull requests are welcome.

@optikfluffel this is fixed today @ master https://github.com/liuggio/money/pull/61

Sorry, in #60.
I think we can close the fixed issues.


demo.py error on jetson xavier

Hi, I'm trying to run demo.py on nvidia jetson xavier board.
I installed all packages and libraries well.
However, when I run demo.py, I got an error like below.
2021-06-18 17:23:23.414 (  35.171s) [        7EB21010]vtkXOpenGLRenderWindow.:650    ERR| vtkXOpenGLRenderWindow (0x17b07610): Cannot create GLX context.  Aborting.
Anyone somebody know solution about this problem?
Additionally, I have one more question.
I don't want to show the result window. So, I added mlab.close(). However, the result window shows up and closes. I want never to show up the result window.
Somebody have any ideas?
Thank you.

Just don't run mlab.show(stop=True) and the window will not show up.

I didn't run mlab.show(stop=True). Howerver, the window still show up like below image.

I don't know how to do it.

@reddittoob Hello, I have the same problem, have you found a solution? Thanks


Provide source code tarballs for future stable releases

Currently, for stable chatterino versions only pre-built binaries (exe/dmg/appimage) are provided.
If one wants to build a stable version of chatterino from source, they run into certain issues:

The source archives that get auto-generated by github don't include submodules
- Building from a specific tag/commit fails as the submodules still track the latest version, and have been updated to be incompatible since the chatterino tag. This is wrong, it seems to be an issue with how flatpak manifests update submodules

More specifically, I am trying to get chatterino packaged into flatpak and they require reproducible builds, which doesn't happen when either the repo or it's submodules are building from git master.
I have looked at how fedora does it's chatterino package, and it locks all of the submodules at a specific commit. IMO this is not a good solution, and it would get very tedious to update each submodule invidiually while checking for it's compatibility (perhaps this is also why the fedora package is currently broken, #2565 ).
A solution for all of this would be to provide a source code tarball with all of the submodules included.
Also on the topic of packaging, the appdata.xml file doesn't fully adhere to the standards:
$ appstream-util validate resources/com.chatterino.chatterino.appdata.xml

resources/com.chatterino.chatterino.appdata.xml: FAILED:
• attribute-invalid     : <screenshot> width too large [https://chatterino.com/img/screenshot-3.png] maximum is 1600px
• attribute-invalid     : <screenshot> height too large [https://chatterino.com/img/screenshot-3.png] maximum is 900px
• tag-missing           : <release> required
Validation of files failed

I'm fine with providing source code tarballs as part of the nightly build process

For the purposes of packaging this is "resolved" for me, since the 2.3 tag works properly. It looks like there was an issue specific to the 2.2.3 tag.


[Question] How to build a rule pattern to select tagged template literal

Source code example:
function footerTemplate() {
    return html`<footer>Your footer here.</footer>`;
}

Hi @ShenQingchuan, my dearest sponsor! Thanks for this issue.
I think it can be solved using yaml.
rule:
  kind: call_expression
  has:
    kind: template_string
    field: arguments

https://ast-grep.github.io/playground.html#eyJtb2RlIjoiQ29uZmlnIiwibGFuZyI6ImphdmFzY3JpcHQiLCJxdWVyeSI6IiIsImNvbmZpZyI6IiMgQ29uZmlndXJlIFJ1bGUgaW4gWUFNTFxucnVsZTpcbiAga2luZDogY2FsbF9leHByZXNzaW9uXG4gIGhhczpcbiAgICBraW5kOiB0ZW1wbGF0ZV9zdHJpbmdcbiAgICBmaWVsZDogYXJndW1lbnRzXG4iLCJzb3VyY2UiOiJmdW5jdGlvbiBmb290ZXJUZW1wbGF0ZSgpIHtcbiAgICByZXR1cm4gaHRtbGA8Zm9vdGVyPllvdXIgZm9vdGVyIGhlcmUuPC9mb290ZXI+YDtcbn1cblxuY29uc3QgYiA9IGh0bWxgPGRpdj4gaW50ZXJwb2xhdGlvbiB0ZXN0ICR7Zm9vdGVyVGVtcGxhdGV9YCJ9

Thanks!
But I saw you build this rule as kind: call_expression with field: arguments. I got confused by the following two situations:

in this example, I intended to make another call expression with a template string argument, and I saw arguments AST node in the tree view.
But I didn't found arguments in that tagged template string AST nodes
How can the rule you showed above work to distinguish a "tagged template string" and a typical "call expression" with the "arguments" field ?

I saw arguments AST node in the tree view.
But I didn't found arguments in that tagged template string AST nodes

Thanks for clarifying your confusion.
In ast-grep (as well as tree-sitter), an AST node has two attributes: a kind and an optional field.
The kind corresponds to the node's inherent type, say it is a template string then its kind is template_string.
The field is an optional attribute and is only present when the node is in a special position relative to its parent node.
In this case, arguments means the child node is inside the call expression's argument position.
That's the background knowledge of ast-grep. Now let's see your question.
field: arguments means the target node is inside its parent node's arguments position. For example,
html`<div/>`

The example above <div/> has the kind template_string with field arguments, which matches both our kind and field matcher.
The confusing part is that call(xxx)'s parenthesis part has the kind as arguments as well. However, its kind does not match our query kind: template_string. So it fails to match.

I think this is worth documenting! Thanks for the feedback!


get RuntimeError: Error(s) in loading state_dict for E2E: when doing test on model from training

here's my config for training, i use FUNSD dataset
%run 'main.py' --add-geom --add-embs --add-hist --add-visual --add-eweights --src-data 'FUNSD' --gpu 0 --edge-type 'fully' --node-granularity 'gt' --model 'e2e'  --weights *.pt
then i run the best model using this:
%run 'main.py' -addG -addT -addE -addV --gpu 0 --test --weights e2e-20230213-0530.pt
then i got the Error:
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1497, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for E2E:
Unexpected key(s) in state_dict: "projector.modalities.3.0.weight", "projector.modalities.3.0.bias", "projector.modalities.3.1.weight", "projector.modalities.3.1.bias".
size mismatch for projector.modalities.1.0.weight: copying a param with shape torch.Size([300, 4]) from checkpoint, the shape in current model is torch.Size([300, 300]).
size mismatch for projector.modalities.2.0.weight: copying a param with shape torch.Size([300, 300]) from checkpoint, the shape in current model is torch.Size([300, 1448]).
size mismatch for message_passing.linear.weight: copying a param with shape torch.Size([1200, 2400]) from checkpoint, the shape in current model is torch.Size([900, 1800]).
size mismatch for message_passing.linear.bias: copying a param with shape torch.Size([1200]) from checkpoint, the shape in current model is torch.Size([900]).
size mismatch for message_passing.lynorm.weight: copying a param with shape torch.Size([1200]) from checkpoint, the shape in current model is torch.Size([900]).
size mismatch for message_passing.lynorm.bias: copying a param with shape torch.Size([1200]) from checkpoint, the shape in current model is torch.Size([900]).
size mismatch for edge_pred.W1.weight: copying a param with shape torch.Size([300, 2414]) from checkpoint, the shape in current model is torch.Size([300, 1814]).
size mismatch for node_pred.0.weight: copying a param with shape torch.Size([4, 1200]) from checkpoint, the shape in current model is torch.Size([4, 900]).

Hi @icang1694 ,
at test time it seems like you are not using edge weights --add-eweights.
Try again and if does not work post here the two models, during training and testing time (so we can get a look at them).
A.

thankyou @andreagemelli i miss that option


Chef 16.2.44 backwards compatibility

Pull Request Checklist
Is this in reference to an existing issue? No
General

[X] Update Changelog following the conventions laid out here

[X] Update README with any necessary configuration snippets

[ ] Cookstyle (rubocop) passes

[ ] Foodcritic passes

[ ] Rspec (unit tests) passes

[ ] Inspec (integration tests) passes

New Features

[ ] Added a Testing Artifact as either an automated test or a manual artifact on the PR.

[X] Adedd documentation for it to the README.md

Purpose

Minor typo fixes, README update
Fixed resource declaration introduced in Chef 16.2.44.

Known Compatibility Issues

Cookstyle is still failing due to the ChefSpec coverage, but I'm honestly not sure what it is or if we can take it out. However, this PR currently addresses the breaking change introduced in 16.2.44.


Extracting Schema?

Hi,
Is there someway to extract the schema that json-graphql-server has created when you run json-graphql-server data.js ?

Duplicate of #22


Pass method_name to reflex class

This PR makes method_name an optional argument on build_reflex, as discussed in https://github.com/podia/stimulus_reflex_testing/issues/5.
As mentioned in that issue, this implementation requires repeating yourself to set the method name twice, ie:
reflex = build_reflex(url: "foo", method_name: "create")
reflex.run(:create)

Definitely open to better ideas here, but this has at least unblocked me for the time being. Thanks for your help!

Gosh, I'm so sorry this has sat for so long.

Gosh, I'm so sorry this has sat for so long.


Reduce GTID exposure

This should really only be visible for attendance and IAA exports

For September, let's work on finding everywhere this (and API tokens) shows up and figure out options on hiding those.

Resolved with #505 (I think?)


⚠ Bofrost.at has degraded performance

In c1e8c8e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1429 ms

Resolved: Bofrost.at performance has improved in ff0b689.


OPTIONS in vcpkg_configure_cmake can not override variables in CMakeLists.txt

The line OPTIONS -DCMAKE_CXX_STANDARD=${CXX_STANDARD} take effect only if 0005-remove-CMAKE_CXX_STANDARD.patch (i.e. remove set(CMAKE_CXX_STANDARD 14) in the original CMakeLists.txt) is applied.
Why can't it override the variables defined in CMakeLists.txt?
ports/poppler/portfile.cmake
vcpkg_from_github(
    OUT_SOURCE_PATH SOURCE_PATH
    REPO freedesktop/poppler
    REF poppler-20.12.1
    SHA512 f692682689c0b0fcc3953a1cc157b6e1d2ce3ccab185189d6dc0807f1dd3ea2d1a9773d0b805079a30b3c8a3b0cf3ee83239ed48d7b08dc7762eba29c2033674
    HEAD_REF master
    PATCHES
        0001-remove-tests.patch
        0002-remove-utils.patch
        0003-remove-glib-and-GObject-introspection.patch
        0004-remove-Qt5-and-Qt6-support.patch
        0005-remove-CMAKE_CXX_STANDARD.patch
)

if("cpp17" IN_LIST FEATURES)
    set(CXX_STANDARD 17)
else()
    set(CXX_STANDARD 14)
endif()

message(${CXX_STANDARD})

vcpkg_configure_cmake(
    SOURCE_PATH ${SOURCE_PATH}
    PREFER_NINJA # Disable this option if project cannot be built with Ninja
    OPTIONS -DCMAKE_CXX_STANDARD=${CXX_STANDARD}
    #OPTIONS -DCMAKE_CXX_STANDARD=${CXX_STANDARD}
    # OPTIONS -DUSE_THIS_IN_ALL_BUILDS=1 -DUSE_THIS_TOO=2
    # OPTIONS_RELEASE -DOPTIMIZE=1
    # OPTIONS_DEBUG -DDEBUGGABLE=1
)

vcpkg_install_cmake()

file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")

file(INSTALL ${SOURCE_PATH}/COPYING DESTINATION ${CURRENT_PACKAGES_DIR}/share/${PORT} RENAME copyright)

BTW, for the sample code at https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/vcpkg_check_features.md
# ports/mimalloc/portfile.cmake
vcpkg_check_features(OUT_FEATURE_OPTIONS FEATURE_OPTIONS
  # Keyword FEATURES is optional if INVERTED_FEATURES are not used
    asm       MI_SEE_ASM
    override  MI_OVERRIDE
    secure    MI_SECURE
)

vcpkg_configure_cmake(
  SOURCE_PATH ${SOURCE_PATH}
  PREFER_NINJA
  OPTIONS
    # Expands to "-DMI_SEE_ASM=ON; -DMI_OVERRIDE=OFF; -DMI_SECURE=ON"
    ${FEATURE_OPTIONS}
)

It seems that OPTIONS can override the variables defined in CMakeLists.txt

Hi @playgithub
The OPTIONS parameter in vcpkg_configure_cmake can override options but not variables. If a variable it's not set, it is possible to set it with OPTIONS; but if the CMakeLists.txt declares the variable, it won't be overridden.

Options are declared using option(<option_name> "description" <value>)
Variables are declared using set(<variable_name> <value>)

You can read more here: https://cmake.org/cmake/help/latest/command/option.html
In the case of CXX_STANDARD, I think the best thing to do would be to create a patch that removes the hard-coded set(CXX_STANDARD 14) and instead let users control the standard using a toolchain file or a custom triplet.

let users control the standard using a toolchain file or a custom triplet

Use a triplet to control C++ standard is nice, has it been implemented?


Source tracking does not detect local changes for relative paths

Summary
force:source:beta:status or force:source:beta:push does not detect local changes for paths in the sfdx-project.json that have been specified as a relative path i.e. ./path/to/package
#1258
Steps To Reproduce:

Create a scratch org using force:org:create
Specify packages in sfdx-project.json with relative paths i.e. path: "./path/to/package"
Run force:source:beta:push using the scratch org from step 1
Run force:source:beta:status using the scratch org from step 1

Expected result
Source tracking should detect local changes regardless of how the path is specified e.g. path/to/package or ./path/to/package
Actual result
"No results found" for force:source:beta:push
Either no results or remote changes only for force:source:beta:status
System Information

sfdx-cli 7.134.0
macOS 10.15.7

marked as bug: W-10886128


[AVM Module Issue]:

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Issue Type?
I'm not sure
(Optional) Module Version
0.1.0
(Optional) Correlation Id
No response
Description
Please add location in resource group output.tf

@ajeetchouksey  thank you for opening this. Unfortunately I am going to close this and not merge the PR as per spec documentation "Remember, you SHOULD NOT output values that are already inputs (other than name)": https://azure.github.io/Azure-Verified-Modules/specs/tf/res/#id-tffr2---category-outputs---additional-terraform-outputs


removed implementation section #Fixes #989

Fixes
Fixes #989 by @AetherUnbound
Description
I removed "Implementation" section from
.github/ISSUE_TEMPLATE/infrastructure_improvement.md
and
.github/ISSUE_TEMPLATE/code_quality.md
which was no longer of any use.

Hello there @AetherUnbound  New to contributions ...Can you tell me why all checks are not marked and how to do about it?


Unable to support Laravel 10

As far as I can tell the package supports Laravel 10.
Do you see any errors? Can you share it?

./composer.json has been updated
Running composer update coding-socks/laravel-upload-handler
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- coding-socks/laravel-upload-handler v0.1.0 requires php ^7.1 -> your php version (8.2.15) does not satisfy that requirement.
- coding-socks/laravel-upload-handler[v0.2.0, ..., v0.2.1] require php ^7.3 -> your php version (8.2.15) does not satisfy that requirement.
- coding-socks/laravel-upload-handler v0.2.2 requires illuminate/support ^6.10 || ^7.0 || ^8.0 -> found illuminate/support[v6.10.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- coding-socks/laravel-upload-handler v0.2.3 requires illuminate/support ^6.10 || ^8.0 || ^9.0 -> found illuminate/support[v6.10.0, ..., v6.20.44, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires coding-socks/laravel-upload-handler * -> satisfiable by coding-socks/laravel-upload-handler[v0.1.0, ..., v0.2.3].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require coding-socks/laravel-upload-handler:*" to figure out if any version is installable, or "composer require coding-socks/laravel-upload-handler:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Sorry, my bad. I added support but forgot to release a new version. I just did that.
Please try again and let me know if you run into any issues.

Thank you


bumped ruby version to 3 and faraday version to 2

This PR adds support for ruby v.3.2 and faraday version 2 (https://github.com/lostisland/faraday/discussions/1358) which is shipped with a bunch of optimizations and improvements out of the box

thanks @UmanShahzad


Arguments specified in launch.json not being passed to debug target

Brief Issue Summary

The "args" property in launch.json is supposed to allow passing command line arguments to the debug target executable, but it does not appear to work.
Expected:

Define command line arguments in the args array
Arguments are passed in to the debug target

Apparent Behavior:

Define command line arguments in the args array
"args": ["--loglevel", "debug", "--enable-logfile"]
Arguments are not passed to debug target (The program executes, but without the desired arguments)

CMake Tools Log

2020-09-17T01:52:12.925Z [debug] [cache] Parsing CMake cache string
2020-09-17T01:52:23.421Z [debug] [extension] [9958] cmake.launchTarget started
2020-09-17T01:52:23.563Z [info] [main] Building folder: Tilegame Tilegame
2020-09-17T01:52:23.611Z [debug] [main] Saving open files before configure/build
2020-09-17T01:52:23.709Z [info] [build] Starting build
2020-09-17T01:52:23.740Z [debug] [driver] Start build Tilegame
2020-09-17T01:52:23.741Z [debug] [driver] Runnnig pre-configure checks and steps
2020-09-17T01:52:23.742Z [info] [proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --build c:/Users/Travis/Documents/VSCodeStuff/Tilegame/build --config Debug --target Tilegame -- -j 8
2020-09-17T01:52:23.799Z [info] [build] ninja: no work to do.
2020-09-17T01:52:23.805Z [debug] [cmakefileapi-parser] Read reply folder: c:\Users\Travis\Documents\VSCodeStuff\Tilegame\build\.cmake\api\v1\reply
2020-09-17T01:52:23.805Z [debug] [cmakefileapi-parser] Found index files: ["cache-v2-6e617cfe085f0be9092b.json","codemodel-v2-147861faf833ff37efb1.json","index-2020-09-17T01-52-00-0686.json","target-Tilegame-Debug-11db8cb0ca22af5a2824.json"]
2020-09-17T01:52:23.811Z [debug] [driver] Run _refreshExpansions
2020-09-17T01:52:23.811Z [debug] [driver] Run _refreshExpansions cb
2020-09-17T01:52:23.813Z [info] [build] Build finished with exit code 0
2020-09-17T01:52:23.826Z [debug] [extension] [9958] cmake.launchTarget finished (returned {"_proxy":{},"_disposed":false,"_queuedRequests":[],"_idPromise":{},"_creationOptions":{"name":"CMake/Launch","shellPath":"C:\\Windows\\System32\\cmd.exe"},"_name":"CMake/Launch","isOpen":true,"_pidPromise":{},"_id":4,"_cols":292,"_rows":21})
2020-09-17T01:52:23.862Z [debug] [cache] Reading CMake cache file c:/Users/Travis/Documents/VSCodeStuff/Tilegame/build/CMakeCache.txt
2020-09-17T01:52:23.863Z [debug] [cache] Parsing CMake cache string
2020-09-18T02:38:35.638Z [debug] [extension] Deactivate CMakeTools

Developer Tools Log

the args array is notably empty in the developer tools console log
[Extension Host] [CMakeTools] 2020-12-13T08:14:35.192Z [debug] [main] Debug configuration from cache: {"type":"cppdbg","name":"Debug Tilegame","request":"launch","cwd":"C:\\Users\\Travis\\Documents\\VSCodeStuff\\Tilegame\\build","args":[],"MIMode":"gdb","miDebuggerPath":"C:\\msys64\\mingw64\\bin\\gdb.exe","setupCommands":[{"description":"Enable pretty-printing for gdb","text":"-enable-pretty-printing","ignoreFailures":true}],"program":"C:\\Users\\Travis\\Documents\\VSCodeStuff\\Tilegame\\build\\Tilegame.exe"}
console.ts:137 [Extension Host] [CMakeTools] 2020-12-13T08:14:35.193Z [debug] [main] Starting debugger with following configuration. {"workspace":"file:///c%3A/Users/Travis/Documents/VSCodeStuff/Tilegame","config":{"type":"cppdbg","name":"Debug Tilegame","request":"launch","cwd":"C:\\Users\\Travis\\Documents\\VSCodeStuff\\Tilegame\\build","args":[],"MIMode":"gdb","miDebuggerPath":"C:\\msys64\\mingw64\\bin\\gdb.exe","setupCommands":[{"description":"Enable pretty-printing for gdb","text":"-enable-pretty-printing","ignoreFailures":true}],"program":"C:\\Users\\Travis\\Documents\\VSCodeStuff\\Tilegame\\build\\Tilegame.exe"}}
contextKeyService.ts:420 Element already has context attribute
w @ contextKeyService.ts:379
console.ts:137 [Extension Host] [CMakeTools] 2020-12-13T08:14:38.021Z [debug] [extension] [4989] cmake.debugTarget finished (returned {"_debugServiceProxy":{},"_id":"5c05c9e5-fad3-4aad-bbd2-4a2c336b1312","_type":"cppdbg","_name":"Debug Tilegame","_workspaceFolder":{"uri":{"$mid":1,"fsPath":"c:\\Users\\Travis\\Documents\\VSCodeStuff\\Tilegame","_sep":1,"external":"file:///c%3A/Users/Travis/Documents/VSCodeStuff/Tilegame","path":"/c:/Users/Travis/Documents/VSCodeStuff/Tilegame","scheme":"file"},"name":"Tilegame","index":0},"_configuration":{"type":"cppdbg","name":"Debug Tilegame","request":"launch","cwd":"C:\\Users\\Travis\\Documents\\VSCodeStuff\\Tilegame\\build","args":[],"MIMode":"gdb","miDebuggerPath":"C:\\msys64\\mingw64\\bin\\gdb.exe","setupCommands":[{"description":"Enable pretty-printing for gdb","text":"-enable-pretty-printing","ignoreFailures":true}],"program":"C:\\Users\\Travis\\Documents\\VSCodeStuff\\Tilegame\\build\\Tilegame.exe"}})

Platform and Versions

Operating System:  Windows
CMake Version: 3.15.0
VSCode Version: 1.52.0
CMake Tools Extension Version: 1.5.3
Compiler/Toolchain: GCC 10.2.0

Other Notes/Information
Here's the actual launch.json:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build/Tilegame.exe",
            "args": ["--loglevel", "debug", "--enable-logfile"],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}/build",
            "environment": [],
            "externalConsole": true,
            "MIMode": "gdb",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                }
            ]
        }
    ]
}

How are you invoking the debugger, F5 or cmake.Debug command? Launch.json is consumed if you use F5, which triggers the debugging feature of the CppTools extension. The CMake debug feature is not reading launch.json and currently it uses an empty array as debug program arguments.
We have a PR addressing the arguments problem on the CMake Tools side but it has some challenges and we are not going to have time to finalize soon.
https://github.com/microsoft/vscode-cmake-tools/pull/1201
If you use F5 and launch.json, you can still benefit of CMake Tools knowledge for debug binary path and run folder, via these commands that you can write in launch.json:
"program": "${command:cmake.launchTargetPath}",
"cwd": "${command:cmake.launchTargetDirectory}",
This way you don't have to hardcode the two manually and let the extension deduce it every time for you.

Correction to my comment above, the CMake Tools extension is using an empty args array unless you define cmake.debugConfig.args, which I forgot to mention. That is how to can send arguments to the CMake Tools debugging feature (but not the launch in terminal feature, for which we have that PR I mentioned).

Using F5 instead of the debug button on the bottom status bar causes it to use the arguments specified in launch.json, so that is a usable workaround, as well as setting the cmake.debugConfig.args in settings.json. Thanks for the help!


Neovide starting with Height and Width of 0

Not sure why this happens, just installed yesterday, thought it didn't work until I resized the tiny black line in the middle of my screen. Here are the log files:
https://pastebin.com/PHPDPhSz

This actually seems to be tied with the Pop!_OS default desktop environment (gnome3)
Using the cinammon-desktop-environment neovide starts in a normal window

This problem may be related to this https://github.com/Kethku/neovide/issues/213

I think this has been fixed in main. Please reopen if you come back to this and the issue remains.


How to observe the mouseout event

Hello
My animation is loop state.
When I mouse levae, I want to return to the original state.
I don't  find events or methods to return.
If I add mouseout event, it's always trigger.
Is there any other way？

What do you mean by original state? There is a pause method if you want to control playback manually. Or stop if you want to reset back to the start.


Investigate how to allow token owner to configure M and N parameters

Need to check what need to work on and create the issues for each tasks. Need to consider for previous created tokens that are in the soft disable state too.

We need to test first to see if it work with current Sigma implementation.

We don't need this anymore. See #675 for more details.


Build failure

$ stack --version
Version 1.6.1 x86_64 hpack-0.20.0
$ stack build

leads to
[...]
    Configuring extensible-0.4.6...
    Building extensible-0.4.6...
    Preprocessing library extensible-0.4.6...
    [ 1 of 23] Compiling Data.Extensible.Internal.Rig ( src/Data/Extensible/Internal/Rig.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Internal/Rig.o )
    [ 2 of 23] Compiling Data.Extensible.Wrapper ( src/Data/Extensible/Wrapper.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Wrapper.o )
    [ 3 of 23] Compiling Data.Extensible.Internal ( src/Data/Extensible/Internal.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Internal.o )
    [ 4 of 23] Compiling Data.Extensible.HList ( src/Data/Extensible/HList.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/HList.o )
    [ 5 of 23] Compiling Data.Extensible.Class ( src/Data/Extensible/Class.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Class.o )
    [ 6 of 23] Compiling Data.Extensible.Struct ( src/Data/Extensible/Struct.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Struct.o )
    [ 7 of 23] Compiling Data.Extensible.Sum ( src/Data/Extensible/Sum.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Sum.o )
    [ 8 of 23] Compiling Data.Extensible.Product ( src/Data/Extensible/Product.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Product.o )
    [ 9 of 23] Compiling Data.Extensible.Dictionary ( src/Data/Extensible/Dictionary.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Data/Extensible/Dictionary.o )

    /private/var/folders/xz/z3wrll111zn03hdhkd_pxs5w0000gp/T/stack47531/extensible-0.4.6/src/Data/Extensible/Dictionary.hs:104:98: error:
        • Variable not in scope: expr :: Membership (x : xs) x1 -> m a6
        • Perhaps you meant ‘exp’ (imported from Prelude)

[...]

Because it looks that the error occurs in not our tour code but the extensible package, the error should be reported to the extensible's issue tracker.
Although I upgraded my stack and removed local caches then ran stack clean && stack build, the error did not occur.
So I'll close this issue.

It was not an extensible problem since it built on Linux. Something is wrong on Mac. I don't know whom to report this problem to, maybe Stack.


test(carousel): adds test cases for the carousel component

#49
Description
Adds test cases for the src/lib/components/Carousel/Carousel.tsx component.
Tests have shown that the component does not handle the error if slides were not provided. (Fixed)
The component logic was updated a bit according to test results.
Fixes #49
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X ] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules
[X] I have checked my code and corrected any misspellings

@rluders ready for review. thank you.


Take values from options

Let it work:
['@nuxtjs/style-resources', {
    scss: [
      './assets/vars/*.scss',
      './assets/abstracts/_mixins.scss'
    ]
}]

Thanks!


Any plans to support stylelint@15?

Thanks for your work!
Just curious, any plans to support stylelint@15?

Yes, new release coming soon :)

https://github.com/stylelint-scss/stylelint-scss/releases/tag/v4.4.0


Dictionary Issues

Creating a new dictionary doesn't create a DICT row in the DB
Copying a Dictionary doesn't create a DICT row in the DB

No errors reported in logs

I've worked out what this is..
When stepping  a pipeline with two XSLTs:
in XSLT one, a dictionary is referenced by name incorrectly
but the error appears in the pane for XSLT two (XSLT two also references a dictionary, but correctly)


Common: Introduce StopAllIteration filter status for decoding and encoding filters

Signed-off-by: Yang Song<EMAIL_ADDRESS>Description: Created a new filter return status for headers: StopAllTypesIteration. Returning this status means the filter and the filters following it stop iteration on not only headers but also data and trailers. The upstream filters will not be impacted.  The change only includes decoding path.
Risk Level: High. HCM refactor.  Should be a no-op as no filters return the new status but a lot of code is changing.
Testing: Integration test for decoding path.
Docs Changes: Comments added for the new status.
#5842

I only include the decoding path change in this PR. Because the code change is very simple, I suspect I must have missed some cases. It's better to get feedback before I am too far away from the right path, ;)
The plan is to change decoding path first, and then change the existing filters (I think all the impacted filters are decoding filters?). After that, I will modify metadata decoding path accordingly. WDYT?

cc @birenroy

@soya3129 nit: do you mind adding a more expressive PR title e.g introduce StopAllTypesIteration filter status for decoding filters it makes it easier to understand what the content of the PR is.

@soya3129 nit: do you mind adding a more expressive PR title e.g introduce StopAllTypesIteration filter status for decoding filters it makes it easier to understand what the content of the PR is.

Oops. Thanks for the reminder! Fixed.

I am still working on enabling h2 for one of the tests. But I figure I should ask for another review in case I am off the track again, :) Thanks!

Sorry about the delay!!
I think the code is ugly. But I couldn't think of other cleaner ways for now. Will keep thinking a better way.

@soya3129 can you merge master and then I can take another pass?
/wait

Added unit test, and discovered a bug!! Thanks for the suggestion!
I am still working on the encoding path. Besides the similar change to the decoding path, encoding path also needs to save metadata in HCM if iteration has stopped all. So maybe it's cleaner to put encoding path in a separate PR? WDYT?

On a second thought, I decided to include encoding path change (without metadata change) in this cl. Only unit test is included for encoding path. I am working on encoding integration test. I think I will delay the change for metadata until I update the existing filters.

Sorry about the confusion. The latest change is to reset iteration state (conn_manager_impl.cc:1632-1635)  before calling doData() and doTrailers(). In the previous version, we keep StopAll state after calling doData() and doTrailers(). The problem with the previous version is if the the filter's decodeData() returns StopSingleIteration, we will reset the state to StopSingleIteration in commonHandleAfterDataCallback(), and the filter's decodeTrailers() will start iterating with the next filter instead of the current one.
I think with the current change, I can remove check_stop_all and check_iteration_state, which is used to skip state check if the filter is already in StopAll state. Thanks for catching that!

Sorry for the multiple iterations. Please take another look. Thanks!

The good news is this is ready to land.  Hurrah!
The bad news is our release got pushed back from last week to this week, and after some discussion on #envoy-maintainers we're both close enough to cutting this release (and doing our first round of security patches) I think we'll merge this first thing after the release is cut (theoretically Friday).  Sorry about the additional delay and thanks again for all your work getting this tricky feature ready to land!

Thank you so much @soya3129 for your awesome work on this change. I know it took a lot of iterations but I'm very happy with how it turned out. We will get this merged ASAP!

Thanks for the opportunity and all the reviews! I learned a lot, :)

@soya3129 can you merge master and we can get this in? Thank you!
/wait


(Chore) App 3.0 - Get Travis to green

This PR gets Travis to green! It does this by disabling OSX in Travis for now, fixing all front end lint errors, and using make -C instead of cd. Please give it a once over for sanity!

Changes Unknown when pulling 8c73361120160cb7e598ff965204d729f3df0281 on v3-chore-ci into ** on app-3-0**.


Generate does not output placeholders for boolean properties

Bug Report
Steps to Reproduce:
Add a boolean field to a node, relationship or metadata object
e.g.
{
    "type": "object",
    "properties": {
          "propertyBoolean": {
                  "type": "boolean"
           }
      }
}

Expected Result:
{
     "propertyBoolean": "{{ PROPERTY_BOOLEAN }}"
}

Actual Result:
{}

Environment:
Latest version of CLI
Additional Context:
Placeholder values are tricky here. We can't just output false as this could be dangerous.
We should consider a warning to use enums instead of booleans.
Suggested fix for booleans is:

output a string placeholder (will fail validation)
emit a warning saying to use enums instead
add a spectral rule to also emit this warning on pattern files

I was reviewing the newly launched tour.json-schema.org (which is very cool btw, going to link it from our docs).
So it turns out we have another option here by combining boolean and null type.
If we defined the type as
{
  "type": ["boolean", "null"]
}

then we could use a null placeholder, the schema would be valid but we could warn the null placeholder.


Add Open Tech Calendar

Open Tech Calendar has been used in the Edinburgh and wider Scotland tech scene for quite a few years now. Other instances of it could be hosted, and it could probably be adapted to any goal, not necessarily tech. It has location lookups and notifications, but as far as I know, no billing. It promotes the publishing of open data APIs.

Thanks!

Beat me to it 👍


Dunfell Corretto recipe contains incorrect ARM checksums.

While building Greengrass v2 I hit a problem with the arm.md5sum and arm.sha256sum for the following Corretto recipe:
meta-aws/recipes-devtools/amazon-corretto/corretto-11-bin_<IP_ADDRESS>.1.bb
This is the file being fetched:
https://corretto.aws/downloads/resources/<IP_ADDRESS>.1/amazon-corretto-<IP_ADDRESS>.1-linux-armv7.tar.gz;name=arm
These are the current (incorrect checksums) in the above recipe:
SRC_URI[arm.md5sum]        = "67cb4d9d4a313c4f001d81717f2b7cd4"
SRC_URI[arm.sha256sum]   = "4648ea4419ddc20bdb6f2378355d289cbaadd588b41e112c03d03d06eaa075e2"
These are the correct checksums for the Amazon Corretto tar ball:
SRC_URI[arm.md5sum]        = "b7d9f46eabd604c0bf89227bc64644ed"
SRC_URI[arm.sha256sum]   = "63c05e86606d53df6a33472bb570fa9318de8125644dd928566d6205a1ecb024"

it appears the corrections were done in #250 in master branch. can that change be applied to other release branches?

The checksum should be fixed on dunfell-next I am preparing a release into dunfell. It should be merged some time tomorrow.

This should now be resolved on dunfell


Completion information

Currently, it's not possible to determine when a task completed, nor when it was scheduled. This makes it more difficult to measure how long tasks have been in the queue, which is helpful when analysing queue depth (a la #12).
2 new fields should be added:

enqueued_at: When the task was enqueued
finished_at: When the task finished running (whether it succeeded or not)

I am attending the DjangoCon sprint and working on this.


Feature/identifiers check

Overview
Added a helper to check identifiers before adding to the system.

I added a comment about being more strict with the regexps, specially because there're quite a few very open (e.g. ^U). It would be good to expand at least the easy ones (e.g. NCT), but I'm happy to handle this later.


URL Whitelist

I've had some massive issues getting outbound connectivity for a client even with the whitelist in place.
After opening up the server to all ports > all destinations outbound I can see lots of traffic to *.cloudapp.net
Should this be required in the whitelist?

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

ID: bdbd2045-3f96-0c47-00ed-b514a759a6bd
Version Independent ID: 90e715cd-08c2-09e9-292f-bfc515f0dee3
Content: Add an on-premises app - Application Proxy in Azure Active Directory
Content Source: articles/active-directory/manage-apps/application-proxy-add-on-premises-application.md
Service: active-directory
GitHub Login: @barbkess
Microsoft Alias: barbkess

@richie1080 Sorry for the delayed response. *.cloudapp.net doesn't require whitelisting and is not recommended as well. *.cloudapp.net is used primarily for Azure applications /cloud services and is generated automatically by the azure system whenever we deploy certain services like web apps / coud services etc.  You can learn more about this here. Please let us know if the information helps you . In case of any further queries, feel free to let us know.

@richie1080 We have not heard from you in a while.We will now proceed to close this thread. If you have further questions, please tag me in the comments and I will gladly continue the conversation.


UI shows 404 page when following link or refreshing page

e.g. the following path exists but the link doesn't work
https://arequipa.sia.tech/buckets/default/files

This is a dupe of https://github.com/SiaFoundation/renterd/issues/1026 and is fixed by https://github.com/SiaFoundation/web/pull/537. It is in the next release: https://github.com/SiaFoundation/web/pull/531.


Regex Capture Groups

Release: v0.2.5
I have the following log line I am trying to grok pattern match:
{"blah": "foo", "somethin": "baz", "status": 200}
My Grok Pattern (tested on https://regex101.com, and has captured value of 200):
STATUS "status":\s+([^",}]*)
My Grok Metric (Config v2):
match: '%{STATUS:status}'
labels:
    status: '{{.status}}'

I want .status to be just 200, but instead I am getting "status": 200
The grok patter in match seems to be using the whole match sequence in the pattern defintion rather than the capture group. Is this a bug or a feature?

You should not confuse capture groups and named patterns. If you write %{STATUS:status} you are saying that everything that is matched by the pattern STATUS will be stored in the variable status. This has nothing to do with the capture group used in the STATUS pattern.
To achieve what you want, you could try something like this:
match: '"status":\s+%{NUMBER:status_number}'
labels:
    status: '{{.status_number}}'

The variable status_number contains the match of the NUMBER pattern. The NUMBER pattern is defined in file patterns/grok-patterns which is included in grok_exporter.

Thanks!