Leverage semver for devDependencies

As I was working on #879, I was wondering if we should consider switching our devDependencies to leverage semver rather than pegging explicit version numbers for everything. Taking a look at David DM shows almost all our dependencies are out of date, we could mitigate this by using either ^ or ~ for our dependency versions.

Most of jQuery repos went in the opposite direction. Semver is an idea but reality is that from time to time a package breaks and then we have a problem. IMO it's better to just pin versions and update from time to time. Note that using non-latest version of a dependency isn't a bad thing; maybe they introduced a new feature we don't use, maybe a bug fix that doesn't affect us that much. It's good to not lock down to something ancient but it doesn't mean constantly living on the bleeding edge is an adequate answer either.

Okay, if that's the direction the larger jQuery org has gone then I'm fine with it. I'm definitely familiar with the issues you describe, but on the flip side I also enjoy staying up-to-date to gain passive benefits (e.g., performance and bug fixes) and when things do break it gives you an opportunity to contribute back to your dependencies. Just thought I'd bring it up for discussion.

The current devDependencies work for what we need and locking their respective versions help us to reproduce the same results anywhere. This approach avoid regressions or releases that won't follow semver.
In another perspective, this project needs more updates on the npm packages, avoiding a lock down on ancient modules.

Marking this as closed, but glad we now have some public documentation for our approach here.


Is there documentation for this thing???

Context

Expected Behavior

Actual Behavior

Possible Fix

Steps to Reproduce

Your Environment

Zappa version used:
Operating System and Python version:
The output of pip freeze:
Link to your project (optional):
Your zappa_settings.py:

@sleepychild The README is reasonably comprehensive... is there anything specific which is lacking from README.md?

@dpretty , how should I know. That's why I asked.


Spurious failures in cudacopy! with "invalid argument" error

This is probably related to #17 and how finalizers work.
The following function:
function test1()
  devices(dev->true, nmax=1) do devlist
    dev = devlist[1]
    device(dev)

    sz = (801, 802)
    x = CudaPitchedArray[]
    for i=1:10
      push!(x, CudaPitchedArray(Float32, sz))
    end
    for i=1:10
      @time for j=1:length(x)
        to_host(x[j])
      end
      println("Finished iteration $i.")
    end
  end
end

produces the following error on the second time it is run. If I run gc() in between the two runs, there is no error.
julia> versioninfo()
Julia Version 0.4.0-dev+2876
Commit f164ac1 (2015-01-22 22:58 UTC)
Platform Info:
  System: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Sandybridge)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.3

julia> Test.test1()
elapsed time: 0.014716371 seconds (25716080 bytes allocated)
Finished iteration 1.
elapsed time: 0.071074413 seconds (25716080 bytes allocated, 74.17% gc time)
Finished iteration 2.
elapsed time: 0.010117429 seconds (25716080 bytes allocated)
Finished iteration 3.
elapsed time: 0.063922907 seconds (25716080 bytes allocated, 81.96% gc time)
Finished iteration 4.
elapsed time: 0.010150908 seconds (25716080 bytes allocated)
Finished iteration 5.
elapsed time: 0.06263613 seconds (25716080 bytes allocated, 83.62% gc time)
Finished iteration 6.
elapsed time: 0.010153057 seconds (25716080 bytes allocated)
Finished iteration 7.
elapsed time: 0.062723099 seconds (25716080 bytes allocated, 83.70% gc time)
Finished iteration 8.
elapsed time: 0.06263111 seconds (25716080 bytes allocated, 83.61% gc time)
Finished iteration 9.
elapsed time: 0.01013381 seconds (25716080 bytes allocated)
Finished iteration 10.

julia> Test.test1()
WARNING: CUDA error triggered from:

 in checkerror at /***/.julia/v0.4/CUDArt/src/libcudart-6.5.jl:15
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:313
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:288
 in copy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:282
 in to_host at /***/.julia/v0.4/CUDArt/src/arrays.jl:87
 in anonymous at /***/test.jl:17
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:57
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:49
 in test1 at /***/test.jl:6ERROR: "invalid argument"
 in checkerror at /***/.julia/v0.4/CUDArt/src/libcudart-6.5.jl:16
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:313
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:288
 in copy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:282
 in to_host at /***/.julia/v0.4/CUDArt/src/arrays.jl:87
 in anonymous at /***/test.jl:17
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:57
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:49
 in test1 at /***/test.jl:6

This is with the git head version of CUDArt, and probably has something to do with a garbage collection pass trying to collect a Cuda pointer that came from a previous device context (before device_reset called cudaDeviceReset), so that the pointer is invalid in the new device context.
This is very irritating when testing Cuda code in the repl when the same function is run over and over again, sometimes not even correctly, so resetting everything correctly is a must.

I can't replicate this: I ran test1() 120 times in a row without a single error. It also doesn't seem to really make sense, because all the finalizers should run at the end of test1---when the devices context closes, it runs a device_reset (https://github.com/JuliaGPU/CUDArt.jl/blob/35e9e4922eba7ed4bd3154b520e6716f345195c1/src/device.jl#L90-L97). So that should be the equivalent of running gc().
julia> versioninfo()
Julia Version 0.4.0-dev+2954
Commit 8e1e310* (2015-01-28 14:07 UTC)
Platform Info:
  System: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Sandybridge)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.3

Things to try:

examine the contents of CUDArt.cuda_ptrs between runs
set debugMemory = true (it's been long enough that I don't exactly remember what this does, but I remember it being useful) https://github.com/JuliaGPU/CUDArt.jl/blob/35e9e4922eba7ed4bd3154b520e6716f345195c1/src/arrays.jl#L15

Before the failure it looks like this (I printed cuda_ptrs and the copy parameters in cudacopy!)
Finished iteration 2.
CUDArt.cuda_ptrs = Dict{Any,Int64}(Ptr{Void} @0x0000004200100000=>0,Ptr{Void} @0x0000004200c00000=>0,Ptr{Void} @0x0000004200940000=>0,Ptr{Void} @0x00000042003c0000=>0,Ptr{Void} @0x0000004201180000=>0,Ptr{Void} @0x0000004201440000=>0,Ptr{Void} @0x0000004201700000=>0,Ptr{Void} @0x00000042019c0000=>0,Ptr{Void} @0x0000004200680000=>0,Ptr{Void} @0x0000004200ec0000=>0)
params = [rt.cudaMemcpy3DParms(C_NULL,srcpos,pitchedptr(src),C_NULL,dstpos,pitchedptr(dst),ext,cudamemcpykind(dst,src))] = [CUDArt.CUDArt_gen.cudaMemcpy3DParms(Ptr{Void} @0x0000000000000000,CUDArt.CUDArt_gen.cudaPos(0x0000000000000000,0x0000000000000000,0x0000000000000000),CUDArt.CUDArt_gen.cudaPitchedPtr(Ptr{Void} @0x0000004200100000,0x0000000000000e00,0x0000000000000321,0x0000000000000322),Ptr{Void} @0x0000000000000000,CUDArt.CUDArt_gen.cudaPos(0x0000000000000000,0x0000000000000000,0x0000000000000000),CUDArt.CUDArt_gen.cudaPitchedPtr(Ptr{Void} @0x000000000d4a8ff0,0x0000000000000c84,0x0000000000000321,0x0000000000000322),CUDArt.CUDArt_gen.cudaExtent(0x0000000000000c84,0x0000000000000322,0x0000000000000001),0x00000002)]
WARNING: CUDA error triggered from:

 in checkerror at /***/.julia/v0.4/CUDArt/src/libcudart-6.5.jl:15
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:100
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:288
 in copy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:282
 in to_host at /***/.julia/v0.4/CUDArt/src/arrays.jl:87
 in anonymous at /***/test.jl:53
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:67
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:59
 in test1 at /***/test.jl:7ERROR: "invalid argument"
 in checkerror at /***/.julia/v0.4/CUDArt/src/libcudart-6.5.jl:16
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:100
 in cudacopy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:288
 in copy! at /***/.julia/v0.4/CUDArt/src/arrays.jl:282
 in to_host at /***/.julia/v0.4/CUDArt/src/arrays.jl:87
 in anonymous at /***/test.jl:53
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:67
 in devices at /***/.julia/v0.4/CUDArt/src/device.jl:59
 in test1 at /***/test.jl:7

If I surround to_host in gc_disable, gc_enable, there is also no crash, so this probably isn't to do with finalizers.

Very strange. I get this:
julia> CUDArt.cuda_ptrs
Dict{Any,Int64} with 0 entries

because this code should remove all the entries from the dict. Why isn't that happening in your case?

The message gets printed before the error in to_host, so that's cuda_ptrs just before the crash.

Ah, I misunderstood when you were running it. That's informative too (but also worth checking: you should have an empty dict right after you successfully complete test1()).
I can't see anything that looks wrong with that output. I'm pretty baffled overall. Does Pkg.test("CUDArt") pass for you? What does nvcc --version say for you? How about the deviceQuery test?

julia> Pkg.test("CUDArt")
INFO: Testing CUDArt
juliarc = "/***/.juliarc.jl"
INFO: CUDArt tests passed
INFO: No packages to install, update or remove

~ $ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2013 NVIDIA Corporation
Built on Thu_Mar_13_11:58:58_PDT_2014
Cuda compilation tools, release 6.0, V6.0.1

~ $ ./deviceQuery

Detected 4 CUDA Capable device(s)

Device 0: "Tesla M2090"
  CUDA Driver Version / Runtime Version          6.0 / 6.0
  CUDA Capability Major/Minor version number:    2.0
<snip...>

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 6.0, CUDA Runtime Version = 6.0, NumDevs = 4, Device0 = Tesla M2090, Device1 = Tesla M2090, Device2 = Tesla M2090, Device3 = Tesla M2090
Result = PASS

I should point out that I don't have direct control over the machine here, it's more like a departmental server that I can use.
I notice the runtime version is 6.0, while the wrappers were generated for 6.5. I think this is probably not the reason because the actual API is probably just the same.
At first I thought maybe it's some pointer alignment issue (the host pointer is not divisible by 128 = 0x80), but the other host pointers are also not aligned and do not cause errors.

In that example, the device is still initialized (i.e. cudaDeviceReset was not called, which is a real problem):
function isInitialized(dev)
  device(dev)
  try
    CUDArt.rt.cudaSetDeviceFlags(0)
    return false
  catch ex
    @show ex
    return true
  end
end

julia> Test.isInitialized(0)
WARNING: CUDA error triggered from:

 in checkerror at /***/.julia/v0.4/CUDArt/src/libcudart-6.5.jl:15
 in isInitialized at /***/test.jl:8ex = "cannot set while device is active in this process"
true


Could not find gem 'middleman-core (~> 3.3) ruby'

When installing on a current Middleman 3.2.2 project, Bundler reports that contentful_middleman depends on Middleman 3.3, and running bundle update reports that middleman-core (~> 3.3) ruby can’t be found on rubygems.org.

This seems to be resolved.


Process JWS-signed badges #50.

Adds tasks for detection of JWS string input, signature verification, and key ownership checks. Resolves #50.

This PR also closes #69


Theme 2 - drop cap missing indentation

everything else works, just not that part...
Expected behavior: drop caps test should be left aligned with the indented body copy below it. All of the content should go past the main container.

Looks like this has been fixed @spacedino can you please check again


Feature Request: support 360 video and images

very handy tools, thank you very much.
if the tool can support more camera types, it would be great.

Thank you for your reply.
Actually, maybe  only one more step needed to process 360 video or image in your pipeline.
After ffmpeg  360 video into equirectangular images, split these images into undistorted images.
if the tool supports fisheye and equirectangular cameras, Nothing is better than good.
https://github.com/alicevision/Meshroom/blob/develop/meshroom/nodes/aliceVision/Split360Images.py

IMHO，360 video will be the infrastructure for NERF and 3DGS in the near future.

I might look into adding a separate workflow for equirects/360 videos some time (probably as a new 01_filter_360_video.py file or something), but I can't promise anything, unfortunately I'm quite busy with other things atm, and it's not a workflow I personally use or can easily test.
I simply don't have the time to invest in adding that workflow currently.
I'll be happy to look at any PRs though.
For now I've added support for more file extensions for the from-images flow, by default jpg,jpeg,png, but with an --exts flag that lets you specify anything else. Anything supported by OpenCV should work.

IMHO，360 video will be the infrastructure for NERF and 3DGS in the near future.

I agree they will probably play a big role on the professional side, however personally I'm more interested in the ability to turn any videos shot from anyone with any smartphone or camera into a good NeRF/3DGS. That not only puts NeRFs/3DGS in the hands of everyone with a camera without any special training, it would also allow for any old footage to be turned into NeRFs.
I also think this will be more interesting for companies once the technology further matures. Want to try out a new kitchen? Simply have your customer shoot a quick video of their current kitchen, do some software magic, and you can generate a NeRF/3DGS with a completely new kitchen in-situ, with an AR viewer so they can walk around right in their would-be-new kitchen in their own house.
But to get to that point, getting good NeRFs from bad videos needs to become much easier, and that's what I was hoping to help achieve  with this script.

Thank you for the idea of universal benefit.
looking forward  to any progress.


Saleae.Logic version 2.3.47

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Blocked by https://github.com/microsoft/winget-cli/issues/684.

Blocked by microsoft/winget-cli#684.

I think that issue is something else entirely, since the drivers are packaged as part of the application here, they just need the permission to install. This is more of an Interactive-Only-Installer thing. I forget the issue number, but I think if @denelon tags this issue, wingetbot might know


Update resource health for microsoft.cdn/profile

Removed the sentence that does not have impact on resource health

Hi Resource health team,
I’ve created a pull request on github for the resource health doc for Azure CDN. As @Bernardo Alfredo<EMAIL_ADDRESS>has left your team, could someone from your team please help?
Regards
Risong
From: PRMerger14<EMAIL_ADDRESS>Sent: Friday, July 13, 2018 11:32 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Risong Na<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update resource health for microsoft.cdn/profile (#11707)
@microsoft-rinhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft-rin&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305068862&sdata=No7jH53vqC6IglU9ch3wB9qNqpJb8xw3WFbCWKVGueU%3D&reserved=0 : Thanks for your contribution! The author, @BernardoAMunozhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBernardoAMunoz&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305078870&sdata=0jikCkQx1gg48qOtRr4h7QG56D1SwNAY8wrx33%2FzLwk%3D&reserved=0, has been notified to review your proposed change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F11707%23issuecomment-404916673&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305088875&sdata=NQmL1Z%2FI9G%2FvcfyYVkX89n39DIjAq8JAOxM6Wkls9W4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASf9o5VMxjf53I0sueXADAZrXVUhsxrzks5uGOeogaJpZM4VPU_l&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305088875&sdata=JsxocxW27OE4%2BZ7lrtuifqKsDsmEfIqXyMO8bSTRYvg%3D&reserved=0.

I will try to sign off.
From: Risong Na
Sent: Friday, July 13, 2018 11:37 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Dushyant Gill<EMAIL_ADDRESS>Shawn Tabrizi<EMAIL_ADDRESS>Scott Hitch<EMAIL_ADDRESS>Prasanna Padmanabhan (AZURE PIE<EMAIL_ADDRESS>Bernardo Alfredo Munoz<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Rajesh Hegde<EMAIL_ADDRESS>Manling Zhang<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] Update resource health for microsoft.cdn/profile (#11707)
Hi Resource health team,
I’ve created a pull request on github for the resource health doc for Azure CDN. As @Bernardo Alfredo<EMAIL_ADDRESS>has left your team, could someone from your team please help?
Regards
Risong
From: PRMerger14 <notifications<EMAIL_ADDRESS>Sent: Friday, July 13, 2018 11:32 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Risong Na <rin<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update resource health for microsoft.cdn/profile (#11707)
@microsoft-rinhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft-rin&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305068862&sdata=No7jH53vqC6IglU9ch3wB9qNqpJb8xw3WFbCWKVGueU%3D&reserved=0 : Thanks for your contribution! The author, @BernardoAMunozhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBernardoAMunoz&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305078870&sdata=0jikCkQx1gg48qOtRr4h7QG56D1SwNAY8wrx33%2FzLwk%3D&reserved=0, has been notified to review your proposed change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F11707%23issuecomment-404916673&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305088875&sdata=NQmL1Z%2FI9G%2FvcfyYVkX89n39DIjAq8JAOxM6Wkls9W4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASf9o5VMxjf53I0sueXADAZrXVUhsxrzks5uGOeogaJpZM4VPU_l&data=02|01|rin%40microsoft.com|aae193f360b443bb4ff608d5e8eef129|72f988bf86f141af91ab2d7cd011db47|1|0|636671035305088875&sdata=JsxocxW27OE4%2BZ7lrtuifqKsDsmEfIqXyMO8bSTRYvg%3D&reserved=0.

#sign-off

@shawntabrizi: I'm sorry - only the author of this article, @BernardoAMunoz, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


ISPN-9281 Handle ClassNotFoundException for io.netty.channel.epoll.Epoll

https://issues.jboss.org/browse/ISPN-9281

LGTM

There are several failures in integration tests, are they related?

No, they seem to be something related to a failed server that is not relinquishing ports. @ryanemerson could these be related to the store avail stuff ?

@tristantarrant Why would you omit the jar from the classpath? I get that on some platforms you can't use the native part, but the classes should still be there.

EAP wants all native bits packaged in separate RPMs

Eh, okay ... so to satisfy their needs EAP could use the artifact without native bits in the base deployment and add the bits from :linux-x86_64 in this separate RPM. In the worst case the classes would be on the classpath twice but as long as noone forgots to update the version it should do the trick.
I am not turning down your solution, but the reason for the handling in code is non-obvious and ^ seems more elegant.

Unfortunately, creating such a build takes more time than making the epoll
dependency optional...
On Mon, 11 Jun 2018, 10:09 Radim Vansa<EMAIL_ADDRESS>wrote:

EAP wants all native bits packaged in separate RPMs
Eh, okay ... so to satisfy their needs EAP could use the artifact without
native bits in the base deployment and add the bits from :linux-x86_64 in
this separate RPM. In the worst case the classes would be on the classpath
twice but as long as noone forgots to update the version it should do the
trick.
I am not turning down your solution, but the reason for the handling in
code is non-obvious and ^ seems more elegant.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinispan/infinispan/pull/6049#issuecomment-396158614,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAX9Hj_3nC9pymD1Wtz2DSqUOQfRxBVTks5t7iXKgaJpZM4UgGdN
.


Implement possession signed endpoints with using token based authentication.

Recently, we have successfully implemented and tested a token based authentication in our mobile client application, so we should remove that old possesion-signed endpoints and replace them with token based authentication.

/api/auth/token/app/push/register -> currently has token impl. at /api/auth/token/app/token/push/register
/api/auth/token/app/operation/list -> currently has token impl. at /api/auth/token/app/token/operation/list

As you can see, there are too much "token" in the URL, so we should just use the old URLs with this new token base method for authentication.

I agree - I kept the original endpoint so that we can maintain the compatibility for the short period of time when some parts are not yet migrated. Since mToken already  implements token based authentication, the backward compatibility is no longer relevant.


Allow opening ds-metadata-uri-values links in a new window

Is your feature request related to a problem? Please describe.
It would be nice if we could indicate that metadata using the <ds-metadata-uri-values> selector on the simple item page could be opened in a new window (ie target=_blank in HTML). The rationale is that, if the user clicks a link that leads away from our site, we want it to open in a new window.
Describe the solution you'd like
We should add a new optional @Input to the <ds-metadata-uri-values> selector to allow specifying the link target. This could be passed to the component by other components, for example the <ds-item-page-uri-field> selector.

Resolved for dspace-7_x in #2866.
Not necessary for main because similar functionality was added as part of the DSpace 8.0 COAR Notify support, see: d46248e99be7383fe3308d37d1d77be56b81f427


Error handling improvement for asserter package

Signed-off-by: Jingfu Wang<EMAIL_ADDRESS>Error handling improvement for asserter package
Motivation

Solution

Open questions

@GeekArthur this is a huge change! Great work!


非常棒的综述

请问会提供中文版的综述吗

Thanks for your attention. We have listed this requirement as to be determined. Subsequent team members will conduct the writing work succeeding when they have time. Please look forward to it.


Allow users to disable automatic numbering in book title

Presently, a numerical identifier in the form of [n] is appended to the book title during command generation to facilitate differentiation among generated books. Nevertheless, users may desire the option to exclude automatic numbering from their book titles, and this capability should be made available to them.

Solved by a80a29017e48f2c86d3864be6f53b6384c514600 and  dd20994e0911f3037d64e3f3abfaf0bb820e5d63.


Updates to eliminate warnings on RTD doc generation

Signed-off-by: Stephen Curran<EMAIL_ADDRESS>I added a mock for aries_cloudagent.vc, which eliminated all of the errors. Of course I suspect that it also removes the doc generation for that module, but am not certain.  But I feel better that all the warnings are gone...

My other PR should fix most of the warnings I think, if you want to test docs generation there.

Pretty sure I did, but I can try again.

I'm guessing you are talking about #1366?  I ran the generation on top that and got many of the same errors.  Once I mocked the one ACA-Py module (vc) on top of that PR, all but one warning (below) went away.   That said, I need to update this PR after the PR is merged, as the RST generator needs to run on the latest code.  It would be nice to have that run on every build and added (if needed) to each PR.  Not sure how to do that...
The remaining error is this.  Is this a code error?
WARNING: error while formatting arguments for aries_cloudagent.protocols.issue_credential.v1_0.models.credential_exchange.V10CredentialExchange: unhashable type: 'list'

I need more context to figure out what's causing that error, and I'm not set up to test it right now. If the errors are just warnings then I'm not sure we need to disable documentation for that module.

Codecov Report

Merging #1371 (cd1294b) into main (a304568) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1371   +/-   ##
=======================================
  Coverage   95.40%   95.40%
=======================================
  Files         476      476
  Lines       28969    28969
=======================================
  Hits        27637    27637
  Misses       1332     1332

I've updated this branch with your merged PR and all is good now.
We're still generating the docs for that module (vc) AFAIK -- we're just not allowing it to be referenced from where it is called.  Not sure why we have to do that. FYI -- there had been two other modules for which we used to do that, but I just tested them and that is no longer needed.
The one error is left, but I can't figure out why it is happening.  I checked various things to do with Sphinx, but can't trace it.  I'm a bit worried it's a code issue, but that's beyond me.
This is now ready to merge.

@ianco -- is this integration error anything to do with my changes (seems very unlikely...) or an intermittent error?
Do I fake a commit to retrigger?

@ianco -- is this integration error anything to do with my changes (seems very unlikely...) or an intermittent error?

This is an intermittent error.  You can re-run the rests from the workflow page (click on the details link and then there should be a button to rerun the workflow)


elementExplorer cuts of the first letter of my statement

When I start elementExplorer regardless of the input I get an error telling me that there is a reference error
> element(by.id(''));
ReferenceError: evalmachine.<anonymous>:1
lement(by.id(''))
lement is not defined

Dupe of https://github.com/angular/protractor/pull/1898 - @hankduan can we fix the text parsing issue separately from the timing issue?

Yes, feel free to review the PR. It will fix the node 0.12.0 compatibility issue. (preferable if you can review https://github.com/angular/protractor/pull/1954 before https://github.com/angular/protractor/pull/1898 though so tests are in place)

:+1: elementExplorer is broken on node v0.12.2.

Will this work if I downgrade node? I'm facing the same issue and I have node 0.12.0

It works for me on node v0.10.30.

+1

@juliemr can you review that PR when you get a chance next week?

+1 Is the workaround to downgrade node versions?

Is the workaround to downgrade node versions?

Yes, to 0.10.30.

This is fixed now in 2.1.


Add option to group changes by module in changelog generation

It'd be cool to be able to group changes by module in the changelogs we generate, especially for massive changelogs like in CWP releases.
cc @chillu @scopeynz

+1. How far would you go with granularity here? There's been mention of spitting by recipe as opposed to splitting by individual module which could strike a good balance if this is coupled with #184

Here are some examples of splitting by module/library:

Option A (plain): https://gist.github.com/dnsl48/946e812827c06ce2c14548c63c1023ce
Option B (tables): https://gist.github.com/dnsl48/f69d1c007566729a65f2ab174403bfae

I didn't prototype splitting by recipe yet, but I guess should be easy enough to do.


NOISSUE - Change docs on the source code retrieval procedure from git clone to go get

This PR updates the documentation on how to retrieve the mainflux source code.
Signed-off-by: Sava Radoš<EMAIL_ADDRESS>

Codecov Report

Merging #366 into master will decrease coverage by 3.25%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #366      +/-   ##
==========================================
- Coverage   92.42%   89.17%   -3.26%
==========================================
  Files          43       43
  Lines        2192     1469     -723
==========================================
- Hits         2026     1310     -716
+ Misses        113      110       -3
+ Partials       53       49       -4

Impacted Files
Coverage Δ

readers/mongodb/messages.go
73.33% <0%> (-13.04%)
:arrow_down:

writers/cassandra/init.go
60% <0%> (-10.59%)
:arrow_down:

things/postgres/things.go
75.43% <0%> (-9.93%)
:arrow_down:

readers/cassandra/messages.go
81.81% <0%> (-9.1%)
:arrow_down:

things/postgres/channels.go
69.38% <0%> (-8.63%)
:arrow_down:

users/api/grpc/endpoint.go
77.77% <0%> (-7.94%)
:arrow_down:

users/postgres/users.go
88.88% <0%> (-7.41%)
:arrow_down:

http/api/transport.go
87.14% <0%> (-5.72%)
:arrow_down:

users/postgres/init.go
83.33% <0%> (-5.24%)
:arrow_down:

ws/api/transport.go
87.05% <0%> (-4.68%)
:arrow_down:

... and 33 more

Continue to review full report at Codecov.

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


ci: add build lib support

Why

Because I need to test if the idea will work

DoD

I need to be able to publish to GitHub Registry 2 packages, one for web and another one for native

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Use micropayment-core for private signing/generation/import/export and isolate bridge module.

Coverage increased (+0.8%) to 54.525% when pulling 17d8a9b9d98c250480fc4e017051918e1cef821b on F483:master into d9a856cdab30fc14d73f1b72887acd371ed92924 on Storj:master.

Coverage increased (+0.8%) to 54.525% when pulling 5ee389490035fa0215d3e98d24fa47f831d19780 on F483:master into d9a856cdab30fc14d73f1b72887acd371ed92924 on Storj:master.

Coverage decreased (-1.5%) to 52.318% when pulling d3be793d1892ea4c0502214bac3b757966cf115a on F483:master into d9a856cdab30fc14d73f1b72887acd371ed92924 on Storj:master.

Coverage decreased (-2.1%) to 51.627% when pulling 24026029d2ad5d96a418f9bea9fd1fc5c08fad68 on F483:master into d9a856cdab30fc14d73f1b72887acd371ed92924 on Storj:master.

Coverage increased (+1.6%) to 55.388% when pulling 337f217addbabf4152983ad53190379abc5061ba on F483:master into d9a856cdab30fc14d73f1b72887acd371ed92924 on Storj:master.

Merged in this commit.

@Miskerest it seems you merged code that had merge conflicts.

ok you got it :)


Bug 2069612: Special Resource Operator (SRO) - Crash when nodeSelector does not match any nodes

/lgtm


Adding the libs sizes to the docs

Is your feature request related to a problem? Please describe.
since now the packages are split people would like to know how the size of the app will be affected using each of the packages
Describe the solution you'd like
adding a table in the docs showing the size of the lib for each platform
Describe alternatives you've considered
maybe making a workflow with app without the lib and comparing its size after adding the lib?
Additional context

@abdelaziz-mahdy Making sense.
For now the only difference between opencv_core and opencv_dart is the videoio module (I am going to remove highgui from the two packages, since highgui is meaningless for Flutter), so the increased app size includes videoio module and ffmpeg, we can just build and compare the size and add a table in README (maybe in the section Status of after that).
I am kind of busy these days, so could you please work on this when you are free?

Will try to make an example workflow but due to the local build stuff It may take time to make sure it's correctly configured
I think a workaround of using the release builds if the local build configuration is not set will be great, will try and let you know

I think a workaround of using the release builds if the local build configuration is not set will be great, will try and let you know

Do you mean that downloading prebuilt libs from the releases as before? It's applicable but I am just tired to maintain them, if it is supported, we will need to build
$$2(core, dart)\times \langle 3(win,linux,mac)\times 2(x64,arm64) + 3(android) + 2(ios)\rangle=22$$
libraries, and if it is necessary to split objdetect (an increase of 6M in size on windows) and dnn (~5.4M) in the future, more libs will be needed, it's kind of crazy...
And especially for ios, it is now depends on DartCvIOS published to Cocoapods, meaning it has to be built locally.

Understandable then, let's leave the local build and see if people have any problems with it


please upgrade with 2019 videos ...

Hi team,
I moved this from here https://github.com/MicrosoftDocs/azure-docs.fr-fr/issues/663
@ehsf973 commented yesterday — with docs.microsoft.com
This is a link to a video on Channel 9 from the 2015 MS Ignite conference.

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

ID: 732eb4b2-7efe-02a0-b905-fe03f9c94e84
Version Independent ID: 64b0f82c-2d46-92c5-37f7-5e06596171b9
Content: Azure Storage security guide
Content Source: articles/storage/common/storage-security-guide.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@CeciAc Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.


Image.toByteData() becames super SLOW after Flutter 3

before flutter 3 it was working super fast
ByteData b =
        await image.toByteData(format: ui.ImageByteFormat.png) as ByteData;

What platform are you on? It's completely broken on web: https://github.com/flutter/flutter/issues/104197

Ios
Before flutter 3 it fast blazing fast.
On Sat, 21 May 2022 at 22:47 Bryson Thill @.***> wrote:

What platform are you on? It's completely broken on web: #104197
https://github.com/flutter/flutter/issues/104197
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/104300#issuecomment-1133750763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVLNPAEBCLNZ3WVTZE3WTTVLEVTFANCNFSM5WQ3ZXIA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi @fullflash,
Please try to provide all or some of the information indicated in the Performance Issue Template to investigate this issue further.
Thank you.

i will try to provide more details but this is just one flutter internal sdk toByteData method.
just generate png data from bytes with flutter sdk 3 and previous version and you will see the difference with just simple stopwatch.

Hi, please try to provide all or some of the information indicated in the Performance Issue Template so that we'll have enough details to conclude on the issue.
By the way, there is an issue #104197 with the Image.toByteData on Flutter 3.0, and it is being processed on #103803.

By the way, there is an issue #104197 with the Image.toByteData on Flutter 3.0, and it is being processed on #103803.

That's for web though, this isssue is for ios?

before flutter 3 it was working super fast
ByteData b =
        await image.toByteData(format: ui.ImageByteFormat.png) as ByteData;

VERY SLOW :( I also have same issue on iOS with flutter 3 (3.0.2).

this mush be an issues, I also have same issue on iOS with flutter 3 (3.0.2).


Sound Laws in Cascades

We should allow for several instances of sound laws, all in their individual instances, that could then be used to select individual instances to be pulled out for sound change, while at the same time allowing us to chain several changes together.

Output could stay chiefly the same for now, but the table would list several "histories" of a word, from source via instances to target.

First possibility for handling has now been added, the new website is also online.


feat: attempt to monkey patch safeStorage to provide an access alert

What does this PR do?

Motivation

Additional Notes

Describe how to test/QA your changes

Addresses part of the concerns in #7

Closing in favor of #9 because monkey patching wasn't cooperating.
There still needs to be a better solution for this.


Use ctru-sys from rust3ds

This ensures that both ctru-rs and this library are depending on the same instance of ctru-sys. Otherwise the compiler complains about trying to link in multiple copies of libctru in the same build.

Oh right, thanks for the PR 😅


[1495] Fixing warnings and add more linter rules to help with code formatting

Resolving all warning issues.
Adding more linter rules to help detect issues with code formatting and consistency.

@phongcao Thanks for the cleanup work and adding the updated rules. In the places you added the disable no-explicit-any can those be properly fixed in future or are they missing type definitions?

Those places are actually for @polatengin and team to address in the future. I don't have much information about the context so it's not safe for me to try replacing them. From now on, we discourage adding any new any type in our code.


Allow users to download the entire water rights database through a scheduled mass-download file

Similar to the JSON-LD file that is generated overnight or once a week, we need a utility that prepares a mass-data download to be accessed by users needing more than 100 K records.
https://github.com/WSWCWaterDataExchange/WestDAAT/tree/develop/src/API/WesternStatesWater.WestDaat.tools.JSONLDGenerator
Since this data is generated once and stored in blob storage, we can allow users with an account to download it. We need to track each user's data download and the 100 K download.

Example JSON-LD mass download
https://westdaat.westernstateswater.org/jsonld.json
We need to add the user token as part of this URL. So we track who is downloading the Json-ld

For water right data only, files created and saved on google drive for public download: https://drive.google.com/drive/folders/1jyKLqVvbK2Hwk89tfs44DL5rIGp5bRG3

A comment and concern with this approach, if we allow a mass download option like this, are we able to track who is downloading and using the data?  Are we concerned with some individuals taking that public data and selling it off as if they had gathered it themselves?

@rwjam That's a great point. How about we close this Google Drive link to only folks we "collaborate" with, per their request? Meaning that we need their email to share it with them. I can add a sentence asking interested users to email us.


Simplify base type and meta overrides

Q
A

Bug fix?
no

New feature?
no

API breaks?
yes

Deprecations?
no

License
Apache 2.0

What's in this PR?
Replaces multiple override fields with a single Deployment / StatefulSet override using the latest operator-tools base types.
To Do

[ ] Requires stable tag from operator-tools

a slightly different approach will be taken, closing this

a slightly different approach will be taken, closing this


Add support to call i2c_set_timeout() and i2c_get_timeout() from esp-idf for I2C Master<...>

I'm using a device that does stretch line SCL of i2c bus.
I found that in the default configuration, my device is stretching SCL for too long time, so when I'm trying to read from my device. The results is ESP_ERR_TIMEOUT.

I made a temporary workaround to the problem as follows:
extern "C" {
    fn i2c_set_timeout(
        i2c_num: esp_idf_sys::i2c_port_t,
        timeout: esp_idf_sys::c_types::c_int,
    ) -> esp_idf_sys::esp_err_t;
    fn i2c_get_timeout(
        i2c_num: esp_idf_sys::i2c_port_t,
        timeout: *mut esp_idf_sys::c_types::c_int,
    ) -> esp_idf_sys::esp_err_t;
}

let config = <i2c::config::MasterConfig as Default>::default()
    .baudrate(100.kHz().into());
let mut i2c = i2c::Master::new(
    dp.i2c0,
    i2c::MasterPins {
        sda: dp.pins.gpio26,
        scl: dp.pins.gpio25,
    },
    config,
).expect("Failed to init i2c");

unsafe {
    let mut ct: esp_idf_sys::c_types::c_int  = 0;
    i2c_get_timeout(0, &mut ct);
    println!("Current i2c stretching timout: {}", ct);
    i2c_set_timeout(0, 32000);  // <- 32000 is ok for me
}

Result:

I think this is addressed already in master, in that it has pub methods on I2cMasterDriver that allow you to read/write with a timeout.


Move mail delivery agent configuration to protected function

Right now part of  _send.. awkward to overwrite in subclasses
Better: separate function

@njam please review

_send: Docu: Only include excepections that will be thrown directly from here (CM_Exception_Invalid)

@njam please review

_send: I don't think it can throw phpmailerException - we catch those and rethrow?

@njam sorry, my bad

lgtm


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24829

Triggering TagBot for merged registry pull request

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26039

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


SENS_EN_SF1XX missing

Hi
I've tried all 1.4.x firmwares and i can't find SENS_EN_SF1XX parameter as said here. It doesn't appear even after full parameters reset.

Am i doing something wrong or it's just a problem with firmware itself? How can i enable my SF11/c LIDAR?
QGC is 3.0.1

Are you building for fmu-v4? It looks like that's the only config which
includes the sf1xx driver.
On Fri, Sep 30, 2016 at 8:10 AM Shpiler<EMAIL_ADDRESS>wrote:

Hi
I've tried all 1.4.x firmwares and i can't find SENS_EN_SF1XX parameter as
said here http://dev.px4.io/sf1xx_lidar_setup.html. It doesn't appear
even after full parameters reset.
[image: noparam]
https://cloud.githubusercontent.com/assets/5054881/18994418/ceaca21c-8738-11e6-9467-3addd1766b2b.png
Am i doing something wrong or it's just a problem with firmware itself?
How can i enable my SF11/c LIDAR?
QGC is 3.0.1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/5573, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACMZPWi8InPh374KJHHfZZH6ZqD4Nahsks5qvRhngaJpZM4KLIML
.

Are you building for fmu-v4?
I'm using pixhawk, so i have to use fmu-v2... or not?

The sf1xx driver isn't listed here:
https://github.com/PX4/Firmware/blob/master/cmake/configs/nuttx_px4fmu-v2_default.cmake
which probably explains why you can't find the parameter. You could try adding it here, but I don't know whether that will be sufficient, or whether it will fit in Pixhawk's flash.

Thx, sound like I have to try unless we have another dev's word here.

I added this driver to cmake file. The parameter has appeared, but lidar readings are still unavailable. The lidar itself works well via usb.

That's progress. Is the driver being started? There should be something in the boot log and perhaps "ps" will show it.

I had to remove some other drivers to get it into flash on px4fmu-v2. Enabling the sensor via parameter should then work out of the box. Btw. I connected my SF10a via I2C.

Fixed on master in terms of startup and available on px4fmu-v3_default.


Voice chat doesn't work

I installed everything as it should be and nothing worked. I also used tutorials on YouTube and it didn't work either, I don't know what's going on. What could be the reason? I also wanted to add that when I press m, in the lower right corner it says that it's working and no one can hear me.

You're likely using other resources that interact with voice natives, vMenu is a common culprit, if you're using it to setup perms for it to not use voice channels at all.


Revise UDP read thread implementation

Utilize WSAPoll on Windows and avoid memcpy between receiveBuffer and receiveBufferTmp
Remove receiveBufferTmp from MDDUDPSocket_s on Windows
Fix lock on nReceivedBytes on Linux
Add missing break statement in switch on Linux

close #240

Not sure what has been changed for the bullet "Fix lock on nReceivedBytes on Linux". Can't relate that bullet to any changes that I see in the diff.

Thanks. Will update ITI_MDD.dll later (after MQTT merge), since there was no change in the exported functions.

Just did a quick test with OpenModelica on Windows. Unfortunately, the changes don't work with OM. I get errors similar to below.
In file included from Modelica_DeviceDrivers.Blocks.Examples.TestSerialPackager_UDP_includes.h:5:0,
                 from Modelica_DeviceDrivers.Blocks.Examples.TestSerialPackager_UDP_functions.c:6:
D:/ModelicaLibs/Modelica_DeviceDrivers/Modelica_DeviceDrivers/Resources/Include/MDDUDPSocket.h: In function 'MDD_udpReceivingThread':
D:/ModelicaLibs/Modelica_DeviceDrivers/Modelica_DeviceDrivers/Resources/Include/MDDUDPSocket.h:50:5: error: unknown type name 'WSAPOLLFD'
     WSAPOLLFD sock_poll = {0};

Maybe it is something simple like a missing header...

@tbeu While trying tho fix the issue for OM, I realized that it is also not working with Dymola (using MSVC 2010). Seems that my test before did not use the MDD with the applied changes. I now get the following error: WSAPoll failed with error: 10022

According to MSDN WSAPOLLFD is defined in Winsock2.h, which is included for MSVC or MinGW: https://github.com/modelica/Modelica_DeviceDrivers/blob/2f88ba77353590b8f1e3d820fa05f8cac3ce52d4/Modelica_DeviceDrivers/Resources/Include/MDDUDPSocket.h#L28-L30

Yes, but there seem to be issues with the header files that come with MinGW (at least for older versions)
https://virtuallyfun.com/wordpress/2017/02/11/wsapoll-mingw/

Can you test the mentioned workaround?

Yes, I did some definitions and it builds. However, I get the same error when executing as I now get with Dymola (WSAPoll failed with error: 10022)

Hm, WSA error 10022 means WSAEINVAL = Invalid argument.

OK, can reproduce.

Instead of
sock_poll.events = POLLIN | POLLHUP;
One needs to do
    sock_poll.events = POLLIN;
    sock_poll.revents = POLLHUP;

I can get things to simulate for OM if I put in following definitions
#if defined(__MINGW32__)
/* This is an (ugly) fix if MinGW headers miss definitions for WSAPoll */
#ifndef POLLIN
typedef struct pollfd {
    SOCKET fd;
    SHORT events;
    SHORT revents;
} WSAPOLLFD, *PWSAPOLLFD, FAR *LPWSAPOLLFD;
WINSOCK_API_LINKAGE int WSAAPI WSAPoll(LPWSAPOLLFD fdArray, ULONG fds, INT timeout);
#define POLLIN 768
#define POLLHUP 2
#endif /* POLLIN */
#endif /* defined(__MINGW32__) */

Does it work if you set struct pollfd instead of WSAPOLLFD?

Instead of
sock_poll.events = POLLIN | POLLHUP;

One needs to do

    sock_poll.events = POLLIN;
    sock_poll.revents = POLLHUP;

Confirmed.

I suppose the sock_poll.revents = POLLHUP; should also be changed in the Linux part. I can't test Linux at the moment, but I will test it in the evening and just push a commit which fixes the issues

After having a closer look the documentation(s) for pollfd, the only thing that I understand should be set in both Linux and Windows is
sock_poll.events = POLLIN;

The revents is the  output parameter, filled by the kernel. Seems like Linux simply ignores if POLLHUP is or'd into events while Windows throws an error.

Thanks for the fix and tests.


pipenv will fail to install package in docker container

Im using ubuntu base image and installing some package on it make our required docker image.
I faced issue that packages are installing which was working fine some days back so I tried whole day to check where is the problem and finally identify that Pipenv not installing package in docker container if we are using version>2021.11.23.
Dockerfile
FROM ubuntu:20.04

ENV DEBIAN_FRONTEND=nonintercative

RUN apt-get update && apt-get install --no-install-recommends -y git python3.9 python3-pip python3.9-dev curl python3-dev gcc libcurl4-openssl-dev libssl-dev jq && apt-get clean && rm -rf /var/lib/apt/lists/*

RUN cp /usr/share/zoneinfo/Asia/Kolkata /etc/localtime && echo "Asia/Kolkata" > /etc/timezone && mkdir -p /var/run/celery && mkdir -p /var/log/celery/  && mkdir -p /var/www/oms && ln -s /usr/bin/python3 /usr/bin/python

RUN pip install pipenv && pip install -U setuptools && pip install --upgrade awscli

WORKDIR /var/www/oms/

COPY . .

RUN pipenv install --system --deploy

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

[packages]
celery="==5.2.3"

[dev-packages]

[requires]
python_version = "3.9"

Interesting, I did some triaging and it turns out that the sysconfig patch I added to get past a setuptools issue is causing this behavior:  https://github.com/pypa/pipenv/pull/5275/files#diff-e154923a3c93acd48d40dd714127c4b90cac776ebd71930770919d539d137f77R44
The good news is that based on a conversation with setuptools I got some new ideas to try and prevent importing setuptools in pipenv, and making those changes in this PR allows me to revert that patch, solve the setuptools problem, and it also solves your example problem where those packages get installed to a seemingly different site packages. https://github.com/pypa/pipenv/pull/5289
I cannot estimate an exact release date yet, because to make that change for real I need to make the corresponding change to requirementslib, release that and vendor in the new version into the above PR.

Thanks for your answer ! I got the same issu

This is the target PR -- ran into some merge conflicts on the other one:  https://github.com/pypa/pipenv/pull/5228

pipenv==2022.8.24 has been released 🎉


is there a way to empty all settings?

Like setting()->empty()->save();

Ive checked the source code, get the forgetAll() method, works for me, hope the document will become better, itll make the user more convenient.


Add link to Release Notes in Busola

Description
It'd be useful to have a link to the OS Release Notes in OS Dashboard and the SKR Release Notes in the managed Dashboard.
The link can be added somewhere in the Cluster Details view.

Reasons
Users can have an access to the RNs straight from Busola.

Suggestions from Mariya:
The What’s New interaction should be consistent with the BTP Cockpit interaction:

As soon as an update occurs, a dialog containing short description/list of the updates should be automatically displayed to a user’s attention. Within Busola that could look like below:

If a user checks the option “do not show this again” – the dialog shall not be displayed automatically anymore, until the user checks this option again.
Instead, all the updates shall be accessible via notification icon (sap-icon://message-information), the amount of the updates should be visible via a badge counter attached to the notification icon:

Once a user clicks the notification icon, the overlay containing all the updates, which were not previewed by a user should be displayed:

Once a user clicks the overlay away, the badge-counter shall be reset and cleared from the notification icon:

The What’s New Content Updates within Busola UI should refer to the Busola specific updates.
General Kyma updates could be referred to via a link.

Links are still not available in Busola, reopening the issue.


Error in migration when updating enum

Hi Prisma Team! Prisma Migrate just crashed.
Command
migrate dev
Versions

Name
Version

Platform
windows

Node
v16.15.0

Prisma CLI
4.2.1

Engine
2920a97877e12e055c1333079b8d19cee7f33826

Error
Error: Error in migration engine.
Reason: [migration-engine\connectors\sql-migration-connector\src\sql_renderer\postgres_renderer.rs:908:22] We should only be setting a changed default if there was one on the previous schema and in the next with the same enum.

Please create an issue with your `schema.prisma` at
https://github.com/prisma/prisma/issues/new

Hey @PauloPraf,
Please could you share with us your Prisma schema?

I had this exact same error with the following schema change.
Before:
model User {
  id            String    @id @default(cuid())
  name          String?
  email         String?   @unique
  emailVerified DateTime?
  image         String?
  accounts      Account[]
  sessions      Session[]
  roles         Role[]    @default([STUDENT])
}

enum Role {
  STUDENT
  STAFF
  MONITORINGMANAGER
  ADMIN
}

Changed only the enum:
enum Role {
  STUDENT
  STAFF
  STUDENTAFFAIRS
  ADMIN
}

I got the following warning beforehand:
⚠  Warnings for the current datasource:

  • The values [MONITORINGMANAGER] on the enum `Role` will be removed. If these variants are still used in the database, this will fail.

✔ Are you sure you want create and apply this migration? … yes

However there are no records in my database with the value MONITORINGMANAGER.

After removing the @default([STUDENT]) the migration was successfully applied.

Was this also about changing an enum for you @PauloPrafß

Was this also about changing an enum for you @PauloPraf?

Yes, it was the same situation as described above.

Another report: https://prisma-errors.netlify.app/report/14266

Hi @PauloPraf 👋🏼
It looks like this was fixed in 4.7.0, could you try upgrading to that version or a more recent one?
PR: https://github.com/prisma/prisma-engines/pull/3379

@PauloPraf I'll close this as it should be fixed already, let us know if it's indeed the case or if we should reopen this.


Don't try to handle health-check messages in fallback chain

This is intended to handle the worst part of #90 (continuously sending requests to cloudflare DNS when blocked) by making the DNS spam no longer be continuous, and only happen in shorter bursts when the local servers return NXDomain. See the commit message text below (after the horizontal rule).
I'm not actually sure what the best way to test this change out locally is. There seems to be an absence of documentation around testing changes to supervisor plugins.

If the fallback chain takes more than 2 seconds to resolve a query the fallback plugin's internal forward plugin will think it has failed and begin sending health checks every 0.5 seconds.
By immediately returning any reply for the health-check message (even an error), it will be deemed a healthy upstream server, and health-checks will stop.
If Cloudflare is inaccessible then it is very easy for it to take more than 2 seconds to process a request, and piling on a bunch of health-check messages makes things much much worse.
Refusing this specific request should have no ill effect, as there is not normally any need to make an IN NS . request, especially of an stub or recursive resolver, and in any event, normally the main chain would handle this.

if you block it, just disable it then...

I strongly disagree that advising users to manually turn off the fallback if they are blocking known external DNS resolvers is an appropriate fix, at least not if fallback is enabled by default, and when blocked results in flooding the network with packets as quickly as possible, which is exactly what happens right now.
Honestly, I feel that any failure mode that acts like denial of service attempt on the local network is not really acceptable under any circumstances, but it is especially bad behavior for a default configuration. And it is not exactly like blocking external dns resolvers is an especially exotic scenario to be running in. There exist routers that offer it as a checkbox feature (at least for port 53, but I’d be unsurprised if some have not added well known DoH resolvers to that checkbox too).
It would be one thing if the fallback were opt-in, or if it were only enabled if, on first boot, supervisor detected that the dhcp offered resolver does not handle AAAA records correctly.


Per block transition and attestation

Apologize for the fat PR. 🙈
What was wrong?
#1381 - StateMachine - per block transition and attestation
How was it fixed?
Follow the beacon chain spec - Per-block processing section except:

No update_ancestor_hashes  design in this PR
No RANDAO reveal design in this PR
No versioning design in this PR

Modifications:

helpers.py

Bugfix get_hashes_to_sign - shouldn’t re-hash the latest hash
Remove multiple slots per committee option: https://github.com/ethereum/eth2.0-specs/pull/62
Rename get_proposer_position to get_block_committees_info, it will return BlockCommitteesInfo as a simple structure of the committee information context.

eth.beacon.state_machines.base.py

Import block APIs

Import the given block into state machine
Call process APIs; if valid, update the states in memory

Process block APIs (all are classmethods)

Pure functions for processing a block
compute_per_block_transtion: compute for every block, will return the updated active_state.

Validate the validate_parent_block_proposer and attestations
Return the new active_state

(TODO in other PRs) compute_cycle_transitions: compute the cycle transitions. (CYCLE_LENGTH = 64 slots), will return the updated crystallized_state and active_state.

Proposer APIs

Proposer story, please see test_propose_block_and_validate_attestation tests:

The block proposer of slot 1:

Creates a block and process the block B1.

Note: no shard block validation currently, so I just set shard_block_hash=ZERO_HASH32.

Attests the block and create an AttestationRecord of B1
Broadcasts B1 and the attestation record of  B1.

The other attesters validate B1.

If it's valid, sign the same message.

The next block proposer or other nodes collect  the votes

Aggregate the signatures and build attestation record.
Broadcast the attestation record.

The block proposer of slot 2:

Create a block B2 with the aggregated attestation records
Attests the block and create an AttestationRecord
Broadcasts B2 and the attestation record of  B2.
(Continue)

Validation APIs (all are classmethods)

proposer validation
attestation validation

TODO

Add tests for validation APIs
Add tests for aggregate signature
Add test for multiple attestations and multiple blocks.
Add assertions in the current tests.
Too many arguments passing!

Yep I see > 6 is a bad signal. I’d prefer to keep using pure function in processing the block, so need to refactor it.
FYI: The only reason why Proposer APIs are not classmethods is because it calls self.get_attestation_record_class(), any other way to avoid it?

@djrtwo: the proposer logic is partially from old mock_make_attestations and partially something new, could you verify the description above? Thanks!
Cute Animal Picture
Cat-sper!

@pipermerriam I'm going to review this PR from a spec validity perspective

Changelog

Fix a lot PR feedback! Thanks @pipermerriam ✨
Reorg some state machine fixtures.
Move most of validation functions into eth.beacon.state_machines.validation. Only keep staticmethod validate_attestation for overviewing in StateMachine. (Or I should move all?)
Move create_signing_message and aggregate_attestation_record to helper.py.
aggregate_attestation_record -> two steps (i)  aggregate_attestation_record and  (ii) aggregate_votes.
Add test for aggregate_votes. Also found the paring is too slow to add more hypothesis case… :|
Add assertions to the tests.

Changelog

Fix test_aggregate_votes test and add verify_votes function
Add BlockProposal NamedTuple for having less arguments
Move validate_attestation to eth/beacon/state_machines/validation.py
Fix validate_attestation (should use updated recent_block_hashes) and add tests for every edge cases
Propose one more block (block_2) in test_propose_block - many lines are repeated, will consider have evm.tools.builder.chain tool in other PRs! (maybe after we have cycle transitions?)

@djrtwo @ChihChengLiang thanks for the feedback! ✨
I'm going to merge this PR and make other issues for following up attestation aggregation.


Chapter 01 - Done [PT] #51

Issue #51
Finally done!

Thanks a lot for wrapping up Chapter 1 @victorescosta and thank you @johnnv1 for the review 🔥 !!
Do you need any help fixing up the links in the quizzes?

Thanks a lot for wrapping up Chapter 1 @victorescosta and thank you @johnnv1 for the review 🔥 !!
Do you need any help fixing up the links in the quizzes?

I think I don't. My last week was kind of hectic but I'll do all these fixs right now!

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

edit: Actually, I think I need. I thought that I solved these issues, could you help me, @lewtun ? Could you explain me why "Quality Check" is failing?

Sure! You usually just need to install the requirements.txt dependencies and then run make style. I've run it for you this time, so will merge once the CI is green


Custom Event from parent to child

In the docs example, the trigger only work if it is activated from a child component. How to did it in reverse when the trigger is running in the method of parent component and sending it down to the childs (direct descendants). Do we necessarily need to create our own global event system for something like this?
My use case is I want to refresh a list of article, when the toggle has been switched.
def setFilter index
  # notify ArticleList to refresh the articles
def render
  <self>
    <div.feed-toggle>
        <ul>
          for tab, index in data:tabs
            <li.nav-item>
              <a :tap.setFilter(index)>
    <ArticleList>

Not sure if you need this anymore - sorry for the delayed response. Not completely sure what you are asking.


Component: Datepicker

Figma
https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=16545%3A53350&mode=design&t=UhNqX9sEMKDoYiIW-1
POP
https://www.figma.com/file/Uwug646a2z3s5Qwa2CZ4vV/POP-Design-System?type=design&node-id=2%3A1145&mode=design&t=7PM2KakWhMGDZ1iO-1
Code
https://design-system.post.ch/#/ng-bootstrap-samples/datepicker
Doc
https://www.experience-hub.ch/document/2803#/atoms-basis-elemente/form-inputs/datepicker-timepicker

@kaloyanso handing this over to you since you are in contact with Ayline

Closing as done


[ISSUE] Cycle in model variables

a = ModelVariable(model_point_set=main)
b = ModelVariable(model_point_set=main)

@assign(a)
def a_f(t):
    return b(t-1)

@assign(b)
def b_f(t):
    if t == 0:
        return 1
    else:
        return a(t)

output is
[...]
TypeError: 'NoneType' object is not subscriptable

During handling of the above exception, another exception occurred:
[...]
cashflower.cashflow.CashflowModelError: Unable to evaluate 'a'.

def get_cycle(src, rest):
    """Find a cycle in the components"""
    q = deque([src])
    marked = {}
    node_from = {}

    # Breadth-first search
    first = True
    e = q.popleft()
    while first or e.name != src.name:
        first = False
        for ch in e.children:
            if ch not in marked and ch in rest:
                marked[ch] = True
                node_from[ch] = e
                q.append(ch)
        e = q.popleft()

    # Recreate list of items
    cycle = [src]
    e = node_from[src]
    while e.name != src.name:
        cycle.insert(0, e)
        e = node_from[e]
    return cycle

feature/simple_cycle ---> only warning
feature/cycle ---> full solution

feature/new_cycle


Incorrect syntax in Ansible code when using Script Builder

What You Are Seeing?
The full playbook code available when using script builder has incorrect syntax when referencing variables
What is Expected?
How Did You Get This To Happen? (Steps to Reproduce)

Use Script Builder to generate Ansible playbook code
Create a playbook in VSCode and apply copied code from Script builder
Commit code to Git repository associated with a Project
Create a template that uses a correct inventory and references your Project
Execute task against your template
Observe syntax errors coming from ansible output

System Details

OS Build (In PowerShell run [System.Environment]::OSVersion.version.tostring()): Windows Server 2019
Windows PowerShell version (Run: $PSVersionTable): 5.1
Chocolatey version (Run choco --version): 1.2.0

Output Log
No logs to provide

Here is the offending code:
- name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

Ansible is reporting incorrect syntax near the variable flower brackets. Correct syntax is:
- name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: ""{{ nuget_repository_url }}""
      # source_username: ""{{ nuget_repository_username }}""
      # source_password: ""{{ nuget_repository_password }}""
      priority: 1


Benchmarks - Add LLaMA-2 Models

Added llama benchmark - training and inference in accordance with the existing pytorch models implementation like gpt2, lstm etc.

Dropped python 3.6 and added 3.10 for cpu unit tests
Updated base image 20.12 -> 24.03 (cuda 12.4) for cuda unit tests
added llama fp8 unit test for better code coverage, to reduce memory required
updated transformers version >= 4.28.0 for LLamaConfig
added llama2 to tensorrt
llama2 tests not added to test_tensorrt_inference_performance.py due to large memory requirement for worker gpu. tests validated separately on gh200

@abuccts can I get access to the unit test logs.

pytorch-llama validation on gh200.

tokenizers cargo issue: https://github.com/huggingface/tokenizers/issues/1691


image: prom/prometheus:v2.3.1 Cannot use -- storage --storage.tsdb.retention.time

Hello, I'm using docker compose to deploy Prometheus. I want to use --storage.tsdb.retention.time=7d, but a problem was encountered:
unknown long flag '--storage.tsdb.retention.time'
My docker-compose.yaml content is as follows:
version: '3'
services:
  prometheus:
    image: prom/prometheus:v2.3.1
    container_name: prometheus
    restart: always
    user: "0"
    command:
      - '--config.file=/etc/prometheus/prometheus.yml'
      - '--storage.tsdb.path=/prometheus'
      - '--web.console.libraries=/usr/share/prometheus/console_libraries'
      - '--web.console.templates=/usr/share/prometheus/consoles'
      - '--storage.tsdb.retention.time=7d'
    volumes:
      - /data/apps/prometheus/config/prometheus.yml:/etc/prometheus/prometheus.yml
      - /data/apps/prometheus/data:/prometheus
    ports:
      - "<IP_ADDRESS>:9090:9090"
    network_mode: "mynet"

You can't start using the above template, but I modified the image to prom/prometheus:latest There is no such problem

Prometheus 2.3.1 did not have that feature, it is a too old version. Did you mean 2.31.1?


Refactoring, middleware fixes, in-browser traceback

Fixes #85, fixes #87
Proposed changes

Implement an "HTTP app" interface: (req: Request, res, Response) -> Response
Refactor error handling with an HTTPErrorMiddleware and ServerErrorMiddleware similar to Starlette
Refactor routing to clearly define what is a route, what is a router, and have an HTTP and WebSocket version of those.
Other changes are defined in the changelog.

TODO:

[ ] Update middleware docs
[x] Regenerate API reference
[ ] Find a way to propagate exceptions that occur within a WebSocket context (currently, they trigger a WebSocketDisconnect — maybe we could re-raise it with a "cause"?)

Codecov Report

Merging #88 into master will decrease coverage by 0.96%.
The diff coverage is 95.93%.

@@            Coverage Diff             @@
##           master      #88      +/-   ##
==========================================
- Coverage   99.45%   98.49%   -0.97%
==========================================
  Files          21       20       -1
  Lines         738      732       -6
  Branches       65       65
==========================================
- Hits          734      721      -13
- Misses          2        6       +4
- Partials        2        5       +3

Impacted Files
Coverage Δ

bocadillo/error_handlers.py
100% <100%> (ø)
:arrow_up:

bocadillo/websockets.py
100% <100%> (ø)
:arrow_up:

bocadillo/app_types.py
100% <100%> (ø)
:arrow_up:

bocadillo/compat.py
100% <100%> (ø)
:arrow_up:

bocadillo/hooks.py
98% <100%> (ø)
:arrow_up:

bocadillo/routing.py
100% <100%> (ø)
:arrow_up:

bocadillo/staticfiles.py
100% <100%> (ø)
:arrow_up:

bocadillo/request.py
100% <100%> (ø)
:arrow_up:

bocadillo/media.py
97.14% <100%> (+0.47%)
:arrow_up:

bocadillo/middleware.py
81.81% <77.77%> (-18.19%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


Add Nature Center Trails

Moving forward on this:
https://github.com/fpdcc/webmap_data_updates/issues/119
Then we will tweak naming to first check for an actual name. If they don't have a name, would fall back to:

trail_type + trail_color + segment_type (direction)

@shua123 Thoughts?

on staging

Behavior looks good. Some issues @glw needs to address on https://github.com/fpdcc/webmap_data_updates/issues/164


How to add it to a server?

Hey!
First thank you for those amazing hacks. I especially love the emoji one and wondered how to add it to an existing jitsi server so everyone can use them. Can you help me there?
Thanks!

Replace all occurrences of jitsi.example.com with your Jitsi host name.

Create the directory /usr/share/jitsi-hacks/emoji-reaction
Download the following files and save them to the newly created directory:

https://jitsi-hacks.cketti.eu/emoji-reaction.js
https://jitsi-hacks.cketti.eu/thumbs_up.png
https://jitsi-hacks.cketti.eu/thumbs_down.png
https://jitsi-hacks.cketti.eu/zipper_mouth_face.png
https://jitsi-hacks.cketti.eu/raising_hands.png
https://jitsi-hacks.cketti.eu/hourglass.png
https://jitsi-hacks.cketti.eu/framed_picture.png
https://jitsi-hacks.cketti.eu/clapping_hands.png
https://jitsi-hacks.cketti.eu/waving_hand.png

Edit /usr/share/jitsi-hacks/emoji-reaction/emoji-reaction.js and replaceconst emojiBaseUrl = 'https://jitsi-hacks.cketti.eu/';

withconst emojiBaseUrl = 'https://jitsi.example.com/jitsi-hacks/emoji-reaction/';

Edit your web server configuration and point the web path /jitsi-hacks/ to the directory /usr/share/jitsi-hacks/.
E.g. for Apache add the following to /etc/apache2/sites-available/jitsi.example.com.conf:Alias "/jitsi-hacks/" "/usr/share/jitsi-hacks/"
<Location /jitsi-hacks/>
  Require all granted
</Location>

Reload your webserver and make sure the JavaScript file and the images are available under e.g. https://jitsi.example.com/jitsi-hacks/emoji-reaction/emoji-reaction.js
To load the script in Jitsi Meet edit /etc/jitsi/meet/jitsi.example.com-config.js and add the following lines at the top (or bottom; shouldn't really matter):function addScript(src) {
    const script = document.createElement('script');
    script.setAttribute('src', src);
    document.body.appendChild(script);
}

window.addEventListener('DOMContentLoaded', function() {
    addScript('/jitsi-hacks/emoji-reaction/emoji-reaction.js');
});

Note: This config file is loaded by clients other than the Jitsi Meet web app. I don't know if they can deal with the modification. Maybe you'll have to find another way to inject the script.
Reload Jitsi Meet in your browser. You should now be good to go.

Thank you so much!

From: cketti<EMAIL_ADDRESS>Sent: Saturday, December 5, 2020 7:35:48 PM
To: cketti/jitsi-hacks<EMAIL_ADDRESS>Cc: timololipop<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [cketti/jitsi-hacks] How to add it to a server? (#3)
Replace all occurrences of jitsi.example.com with your Jitsi host name.

Create the directory /usr/share/jitsi-hacks/emoji-reaction
Download the following files and save them to the newly created directory:
*   https://jitsi-hacks.cketti.eu/emoji-reaction.js
*   https://jitsi-hacks.cketti.eu/thumbs_up.png
*   https://jitsi-hacks.cketti.eu/thumbs_down.png
*   https://jitsi-hacks.cketti.eu/zipper_mouth_face.png
*   https://jitsi-hacks.cketti.eu/raising_hands.png
*   https://jitsi-hacks.cketti.eu/hourglass.png
*   https://jitsi-hacks.cketti.eu/framed_picture.png
*   https://jitsi-hacks.cketti.eu/clapping_hands.png
*   https://jitsi-hacks.cketti.eu/waving_hand.png
Edit /usr/share/jitsi-hacks/emoji-reaction/emoji-reaction.js and replace

const emojiBaseUrl = 'https://jitsi-hacks.cketti.eu/';
with
const emojiBaseUrl = 'https://jitsi.example.com/jitsi-hacks/emoji-reaction/';

Edit your web server configuration and point the web path /jitsi-hacks/ to the directory /usr/share/jitsi-hacks/.
E.g. for Apache add the following to /etc/apache2/sites-available/jitsi.example.com.conf:

Alias "/jitsi-hacks/" "/usr/share/jitsi-hacks/"
<Location /jitsi-hacks/>
Require all granted

Reload your webserver and make sure the JavaScript file and the images are available under e.g. https://jitsi.example.com/jitsi-hacks/emoji-reaction/emoji-reaction.js
To load the script in Jitsi Meet edit /etc/jitsi/meet/jitsi.example.com-config.js and add the following lines at the top (or bottom; shouldn't really matter):

function addScript(src) {
const script = document.createElement('script');
script.setAttribute('src', src);
document.body.appendChild(script);
}
window.addEventListener('DOMContentLoaded', function() {
addScript('/jitsi-hacks/emoji-reaction/emoji-reaction.js');
});
Note: This config file is loaded by clients other than the Jitsi Meet web app. I don't know if they can deal with the modification. Maybe you'll have to find another way to inject the script.
7.  Reload Jitsi Meet in your browser. You should now be good to go.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/cketti/jitsi-hacks/issues/3#issuecomment-739332293, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGA5FLYCNLQRNLSFX47KI3TSTJ4QJANCNFSM4UOPMUNQ.

This doesn't work anymore :(

"This doesn't work anymore" is not a very useful error description. If it's because the Jitsi Meet web user interface has changed, see https://jitsi-hacks.cketti.eu/2021/04/26/updates-to-support-new-jitsi-ui/


Angular 5 support?

Since now Angular 5 is latest, it seems that ngx-adal does not work with Angular 5 nice.
Can you check and fix?

Is there any new on this issue?

I found these for Angular 5:
https://github.com/jcmontx/angular5-adal-example
https://github.com/grumar/adal-angular5

This is now several years old, also you should use MSAL instead of ADAL library and Angular 5 is definitely old now beeing Angular 12 latest :P
So I am closing this and does not need attention anymore.


[IOS] 5.4" inch screen support

Looks like Apple will be launching a 5.4" inch iPhone this year.
In iOS 14 (don't know if it's in iOS 13 too, could someone check?). In Display & Brightness there is a Display Zoom menu where you can chose a zoomed in mode. Which scales up the screen (see attached images). It looks like flutter assumes its running on a iPhone 8 or lower.

App running Flutter <IP_ADDRESS>.2-Pre:

Native Apple App:

Hi @EliasDeuss
I can see that zoom option in iOS 13.6 too, not sure it's worth  creating this issue before device is even is announced/released
Do you have any issues when flutter in zoomed mode or is this just feature request for 5.4in support?
if you've an issue with zoom, Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Hi @EliasDeuss
I can see that zoom option in iOS 13.6 too, not sure it's worth  creating this issue before device is even is announced/released
Do you have any issues when flutter in zoomed mode or is this just feature request for 5.4in support?
if you've an issue with zoom, Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

@TahaTesser Well it’s just the flutter app doesn’t recognize that it’s zoomed in so it doesn’t use the top or bottom of the screen. So you have empty space (compared to apples default apps).

Hi @EliasDeuss
I can there is difference when using zoom mode in Flutter
Left (normal) & right (zoomed)

Do you see different behaviour?
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

@TahaTesser I did more research and it looks like it was added in iOS 14 Beta 3. So if you have your phone on zoomed mode in that beta or above it will behave like that.

@jmagman You might want to add this to #61047 . This looks like to be a iOS 14 Beta 3 addition, also here is an article talking about it. Article Link

@jmagman I also just updated the screenshots to show light mode. You can see the issue a lot better with the black bars.

I tried the zoom on the gallery app on an iPad Pro and it looks pretty good.  Flutter handles all kinds of screen sizes responsively (particularly on Android), so I wouldn't expect a 5.4" screen to cause any issues.
Standard:

(I don't know why the screenshot is cropped, but it looks good on the device.)
Zoomed:

Could you give us a sample app that reproduces this?

@jmagman Here is the flutter gallery app.
[✓] Flutter (Channel stable, 1.20.2, on macOS 11.0 20A5354i, locale en-US)
    • Flutter version 1.20.2 at /Users/elias/flutter
    • Framework revision bbfbf1770c (12 days ago), 2020-08-13 08:33:09 -0700
    • Engine revision 9d5b21729f
    • Dart version 2.9.1

@EliasDeuss That looks pretty good to me.  We can hold this open until someone can test with a real 5.4" device when it ships.  I suspect it will scale fine based on all the other phone screen sizes Flutter supports.

5.4" iPhone 12 mini simulator gallery looks good.

Closing.  If you see bugs related to the new size, please file new issues and completely fill out the template.

Is there a way to disable this? One of our clients wants this zoomed behaviour disabled for their app.

@vanlooverenkoen Please file a new issue and completely fill out the template so the frameworks team can take a look.


Documentation

There is a lack of documentation or started application that shows how to properly use this package.

It should indeed by handy if there was some more information about if you need to add some javascript to your page or not. For me the test payment is done directly, but I was expecting to see some stripe screen to enter some test card data. No? Or does this come magically when you will use the live key?


Update glibc to 2.26

glibc 2.26 https://github.com/bminor/glibc/releases/tag/glibc-2.26
On most architectures, GCC 4.9 or later is required to build the GNU C Library.
Linux kernel 3.2 or later is required at runtime, on all architectures
supported by that kernel.  (This is a change from version 2.25 only for
x86-32 and x86-64.)
glibc 2.25 https://github.com/bminor/glibc/releases/tag/glibc-2.25
glibc 2.24 https://github.com/bminor/glibc/releases/tag/glibc-2.24
The minimum Linux kernel version that this version of the GNU C Library
can be used with is 3.2, except on i[4567]86 and x86_64, where Linux
kernel version 2.6.32 or later suffices (on architectures that already
required kernel versions more recent than 3.2, those requirements remain
unchanged).  Linux 3.2 or later kernel headers are required on all
architectures.
glibc 2.23 glibc 2.24 https://github.com/bminor/glibc/releases/tag/glibc-2.23
The minimum GCC version that can be used to build this version of the GNU
C Library is GCC 4.7.  Older GCC versions, and non-GNU compilers, can
still be used to compile programs using the GNU C Library.

I agree there is probably little advantage to upgrading glibc. There may be an advantage to upgrading gcc to GCC 7. The easiest way to do that is to update our bottling Docker image from Ubuntu 16.04 to Ubuntu 18.04. That upgrades GCC 5 to 7, but also upgrades glibc from 2.23 to 2.26.
Debian 9 provides glibc 2.24 and GCC 6.3.0. If we found a need to upgrade from GCC 5 to GCC 6, that could be an option that doesn't require a newer Linux kernel version.
I suggest that we postpone upgrading the bottling architecture until we find a real and pressing need to update the compiler from GCC 5 to GCC 6 or 7.

Homebrew’s goal is to always have the latest packages. They also support only the last 3 Mac OS versions (officially).
Linuxbrew’s goal should be sort of the same.
It is just a coincidence that Linuxbrew was mostly maintained by science people, which have OS upgrade cycles of more than 10 years. So Linuxbrew tries hard to support old linuxses (which sort of works).
I would like to see the effort of maintaining old kernels and linuxeses in a separate fork. A little bit like Tigerbrew worked for that old version of Mac OS. Of course this splits a little bit the effort on a second team.
One of the reasons is that I would like to have the Gcc formula point to the latest gcc version, like on Mac.
The Linux ecosystem is really cluttered. Most of the support questions I get here are for CentOS. I would like an official list of Linux versions we do support.
Personally I would like to move to Ubuntu 18.04 as soon as possible. We can have a grace period of 2-3 month, until Ubuntu 18.04 has stabilized.
But I could live with Ubuntu 16.04 until it is EOL. Maybe we could move to gcc 6 as a first step, which allows to see if everything compiled correctly (and I bet a lot of stuff will be broken).

It is just a coincidence that Linuxbrew was mostly maintained by science people, which have OS upgrade cycles of more than 10 years.

FWIW, that is one of the main reasons to use Linuxbrew. Personally, I would use system package manager (apt-get, yum, dnf, etc) on Linux machines I have total control. But for science community, it is usual that users do not have the root access in High Performance Computing system or clusters from the university. We also have little control over OS upgrading schedule. In such case, Linuxbrew becomes one of very few choices.

Homebrew’s goal is to always have the latest packages. They also support only the last 3 Mac OS versions (officially).

On the one hand, I would argue that Apple and Linux in general have quite different philosophies on supporting and maintaining the old systems. You could say Apple effectively only supports the latest OS. So we should not apply Homebrew's policy on OS version directly on Linuxbrew. On the other hand, I don't think supporting old OS kernel somehow invalids the goal of offering the latest packages in general. For example, we do offer gcc@7 for the users who need it.

I agree with @xu-cheng. I see Linuxbrew users as those who can't use apt-get, yum, etc. Ideally, Linuxbrew would support several major OSes. What is missing is workforce (contributors). I could be in part because Linuxbrew is following the path of Homebrew in trying to support only "the latest and the greatest". I don't think "analytics" can tell us something useful in this case because if users are having trouble installing Linuxbrew on their OSes, we won't see them in analytics.
Having said that, I don't see Linuxbrew as a solution for HPC systems at the moment because they represent a very special case of Linux system with their additional complications. So, I think at this very moment it is totally reasonable to try and follow the path of Homebrew without dropping the support for old systems completely.

Increasing the minimum kernel version requirement of Linuxbrew is a big deal, because it's the one component of the system that absolutely cannot be updated by the user without admin privileges. Everything else (glibc, gcc, et c) we have control over.
Although the glibc and gcc version are somewhat coupled, but not inextricably so. We could update the gcc version used to bottle without also updating glibc. It's just easier to do both at once by updating the version of Ubuntu on which we bottle.
Bumping the default gcc version would arguably create more trouble than it would solve. We start getting build failures on formulae that fail to build with GCC 7, and there are few formula that fail to build with GCC 5 but do build with GCC 7. For those formulae we have the option of using the new gcc@7 formulae. (Thanks, @xu-cheng!)
Currently gcc@7 is the default compiler on systems that have it installed. See PR https://github.com/Linuxbrew/brew/pull/676. I'm curious to see whether gcc@7 as the default compiler on a user's system can interoperate relatively trouble-free with bottles built by GCC 5.
I suggest we revisit this issue once Ubuntu 18.04 has overtaken Ubuntu 16.04 on the Analytics.

I'm curious to see whether gcc@7 as the default compiler on a user's system can interoperate relatively trouble-free with bottles built by GCC 5.

No, it would not work. Because I deliberately make gcc and gcc@* use different libraries path/rpath to allow them coexist in the same system. Therefore, a bottle built by gcc 5 cannot be run in a system with only gcc@7 installed.
But it we choose to bump the main gcc formula to gcc 7, I think all old bottles built by gcc 5 can indeed be run by the new system, since it is designed to keep backward compatiblity.

Therefore, a bottle built by gcc 5 cannot be run in a system with only gcc@7 installed.

Can it run on a system with both gcc and gcc@7 installed?

But it we choose to bump the main gcc formula to gcc 7, I think all old bottles built by gcc 5 can indeed be run by the new system, since it is designed to keep backward compatibility.

That's what I'm hoping.

My needs are different. Our mini-cluster uses RHEL 7 (aka Centos 7) and a shared /home filesystem over NFS.  Linuxbrew has enabled us to have a common software stack across all nodes, which is cutting edge on everything, as research environment needs that.   We use singularity for the "production stuff".
I fear a big change if it is not necessary yet.  We're only partway through brew-sci and it takes a lot of time, so I don't want to add to that burden.

I am fine to wait a little bit with the update. There is no need for the moment. We can wait until the EOL of CentOS or Ubuntu 16.04. Of course that decision can be reverted if we feel that a faster change is needed.
Maybe we should have a mini roadmap + table of glibc/gcc/kernel, and write down th decision we have taken here. We should be as transparent as possible regarding that matter for our users (and more importantly for the maintainers).

Once we've decided to upgrade glibc and/or gcc we can announce it through our usual channels (Linuxbrew Updates and Twitter).  It sounds like for the time being the decision that there is no imminent update of glibc or gcc planned.

Agree with xu-cheng.  The primary reason our group is considering using linuxbrew is to be able to use newer tools on old systems, where we have no control over the kernel or system tools/libraries.  If we had control over our systems, we would ditch linuxbrew and just use yum.

Just closing here. Ubuntu 18.04 is out now. I think the wish it to wait a little bit before migrating to gcc7 and a newer glibc. Not sure we will wait until the EOL of Centos 6 or Ubuntu 16.04, but who knows :)


[DO NOT MERGE] Adding usage id property to support usages by VM family, Workspace & Comput

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@sarangan12 , can you help add "WaitForARMFeedback" label and add those folks as reviewer?
Gaurav Bhatnagar<EMAIL_ADDRESS>Sanjai Ganesh Jeenagiri sanjaiga@microsoft.com;Kristopher Bash<EMAIL_ADDRESS>Thanks a lot!

Is PR https://github.com/Azure/azure-rest-api-specs/pull/5910  still needed?

Is PR #5910 still needed?

yes, I will ask Kalpana abandon https://github.com/Azure/azure-rest-api-specs/pull/5910

Closed this PR, moved the changes to https://github.com/Azure/azure-rest-api-specs/pull/6220


Use esri/kernel instead of dojo/kernel

We should be able to replace the following with esri/kernel and not have any dojo used.
import kernel = require("dojo/_base/kernel");

I am in the process of updating the examples repo to the latest version of the jsapi so I can do this at the same time.

We'll have to wait for 4.12 for this but we should be able to do it easily. We just need to get the locale from esri/kernel instead of dojo/kernel. But we have to add it to esri/kernel first :)

Ah I see. I just assumed it was already there. Ok I'll mark it for that milestone


Update docs for configuring Apache airflow

Proposed changes -

For installing apache airflow on kubernetes the following parameters needed to be updated in the sample helm airflow values.yaml file -
i. flower.enabled: false
ii. redis.enabled: false

Added notes which will help first time users install airflow successfully.

What changes were proposed in this pull request?

How was this pull request tested?

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@akchinSTC FYI

@akchinSTC does this also fix #1978 ?


Unable to Resolve Dependency on Installation

I downloaded the deb package on code.visualstudio.com.
Then I use debtap to translate it to arch package sudo debtap code_1.73.0-1667318785_amd64.deb.
It produced code-1.73.0-1-x86_64.pkg.tar.zst.
Then I use yay -U ./code-1.73.0-1-x86_64.pkg.tar.zst to install it.
and it gave a error as follows:
警告：无法解决 "libasound2>=1.0.16"，"code" 的一个依赖关系
警告：无法解决 "libatk1.0-0>=2.2.0"，"code" 的一个依赖关系
警告：无法解决 "libcurl3-gnutls"，"code" 的一个依赖关系

I'm using Manjaro KDE.
How can I resolve it?

In addition, the previous versions has no problem like this.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Enable PortA power supply in I2C_Tester

CoreS3 portA (RED, external I2C) 5V pin has no power, so I enabled it.
See also
https://twitter.com/knaveen/status/1702901189460021430

Could you please accept this request?

The new version of the library has some differences from the previous API, and PR cannot be accepted.


how to config for  Inner zoom  / lens zoom

Hi, plz give me more Example.
how to custom for Inner zoom  / lens zoom
thank you

Hi,
custom style for zoom lens is not supported yet.
Change in dependency package (js-image-zoom) is required.
I will implement something like zoomLensStyle string property with css string with next release of js-image-zoom and update documentation here as well.
Regarding examples. Check also this demo link http://malaman.github.io/js-image-zoom/example


get-npm-wrangler-binary endpoint throwing occasional exceptions

🐛 Bug Report
Environment

operating system: Ubuntu 20.04

Steps to reproduce
Repeatedly call curl -I -XGET https://workers.cloudflare.com/get-npm-wrangler-binary/1.10.3/x86_64-apple-darwin in your terminal.
What did you expect to see?
200 OK with Wrangler binary every time I call it.
owner@facility:/tmp$ curl -I -XGET https://workers.cloudflare.com/get-npm-wrangler-binary/1.10.3/x86_64-apple-darwin
HTTP/2 200
date: Thu, 08 Oct 2020 07:34:28 GMT
content-type: application/octet-stream
content-length: 4670200
set-cookie: __cfduid=d1643c72ca730037a27c1a694c9c9b4dd1602142468; expires=Sat, 07-Nov-20 07:34:28 GMT; path=/; domain=.workers.cloudflare.com; HttpOnly; SameSite=Lax; Secure
cf-ray: 5dee2dfbeac805bb-FRA
accept-ranges: bytes
cache-control: public, max-age=14400
content-disposition: attachment; filename=wrangler-v1.10.3-x86_64-apple-darwin.tar.gz
etag: "3ea34547825a42a611e6ee458b32a97d"
expires: Wed, 19 Aug 2020 16:55:20 GMT
last-modified: Fri, 26 Jun 2020 19:29:05 GMT
cf-cache-status: MISS
cf-request-id: 05a8bb1173000005bb3a200200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
x-amz-id-2: RRE9FxBELFqzKQKAkj7MC+uFg+5VmOOkR+1BlMITZuiesBTRPRhoo7ab8Qscs28PGHebs9H5Vq8=
x-amz-request-id: B7795F5AC64E29D5
server: cloudflare

What did you see instead?
Occasional 500s with a generic Cloudflare response saying the Worker has thrown an exception.
owner@facility:/tmp$ curl -I -XGET https://workers.cloudflare.com/get-npm-wrangler-binary/1.10.3/x86_64-apple-darwin
HTTP/2 500
date: Thu, 08 Oct 2020 07:34:29 GMT
content-type: text/html; charset=UTF-8
x-frame-options: SAMEORIGIN
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
cf-ray: 5dee2e010b6f2484-FRA
server: cloudflare
cf-request-id: 05a8bb14a70000248441a56200000001

Downloading release https://workers.cloudflare.com/get-npm-wrangler-binary/1.11.0/x86_64-apple-darwin
Error fetching release Request failed with status code 500
(node:56492) UnhandledPromiseRejectionWarning: Error: Request failed with status code 500
    at createError (/usr/local/lib/node_modules/@cloudflare/wrangler/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/usr/local/lib/node_modules/@cloudflare/wrangler/node_modules/axios/lib/core/settle.js:17:12)
    at RedirectableRequest.handleResponse (/usr/local/lib/node_modules/@cloudflare/wrangler/node_modules/axios/lib/adapters/http.js:210:9)
    at RedirectableRequest.emit (events.js:315:20)
    at RedirectableRequest._processResponse (/usr/local/lib/node_modules/@cloudflare/wrangler/node_modules/follow-redirects/index.js:269:10)
    at ClientRequest.RedirectableRequest._onNativeResponse (/usr/local/lib/node_modules/@cloudflare/wrangler/node_modules/follow-redirects/index.js:50:10)
    at Object.onceWrapper (events.js:422:26)
    at ClientRequest.emit (events.js:315:20)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:596:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:119:17)

I don't know if it's helpful to mention that I am also experiencing this error; feel free to delete this comment if it's just noisy/duplicative. But I wanted to say that it might make sense to add a temporary note to the installation guide explaining that the npm method isn't working on macOS until the problem is resolved; I was confused & it took me a bit of searching to find this issue.

This should be resolved as of a few minutes ago, when we deployed a (putative) fix. @robinsloan can you try again? If you're still seeing errors, please re-open this issue and share the error message you see!

Success! I feel honored to know I might have been the last person in the universe to experience this error. Thanks!

When I try to preview my project using wrangler preview --watch or wrangler preview, I keep getting this message:
"Error: Your JavaScript project is missing a package.json file; is /home/swatilekha/hello the wrong directory?"
Could someone kindly help me out on that? Thanks.

@Swatilekha-Roy can you open a new issue about your problem? The new issue template asks a number of clarifying questions that will help ensure you. get an answer.