Updates for 17.07.0-ce-rc1

Major Notes:

Removes old raspbian cruft now that raspbian has a repo on
download.docker.com
Adds a support matrix so that we can have an easier time updating
what architectures/distros we support
Added support for s390x and aarch64
Had to change add-apt-repository to an echo into a file, was not
functioning correctly on raspbian see moby/moby#31405
Update testing pipeline for multiarch
Removed deprecation warnings for raspbian

Signed-off-by: Eli Uriegas<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "update_for_170701rc1" git@github.com:seemethere/docker-install.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

This PR removed the mirror support, which is essential for user in China. Is there any plan to bring them back?
ping @Hyzhou and @lizzha, have we stopped support for the docker repo mirror in China?
BTW, @lizzha, the certificates on https://mirror.azure.cn/ are revoked.

@twang2218 I don't mind adding support for mirrors if we know those mirrors will be maintained

Looks like the mirrors only mirror the old (apt.dockerproject.org / yum.dockerproject.org) repositories, not yet the new download.docker.com repos e.g. https://mirrors.aliyun.com/docker-engine/apt/repo/pool/main/d/docker-engine/
I get a 403 on the azure mirror (but possibly it doesn't have a browsable index)

https://mirrors.aliyun.com/docker-engine
This mirror will be maintained by Alibaba Cloud. And it works will now. :)

@Hyzhou Alright I'm fine with that, I'll work up a PR to re-add https://mirrors.aliyun.com/docker-ce

@seemethere The mirror https://mirror.azure.cn/ is supported by Microsoft, could you please also re-add it?
@twang2218 the mirror is now only accessible from Azure China Cloud. How do you know that the certificates are revoked?

@lizzha is the mirror now mirroring download.docker.com or apt.dockerproject.org / yum.dockerproject.org ?

Hi @thaJeztah It's still mirroring apt.dockerproject.org / yum.dockerproject.org, seems like we also need to add download.docker.com. And for compatability, we need to maintain both repos. I will take this as a work item. Thanks.

@lizzha IIRC, Azure mirror was publicly accessible before, right? I remembered that I tested install using Azure mirror after PR https://github.com/moby/moby/pull/27005, and tested after Docker 1.13 release.
I didn't realize that you limited the accessibility of Azure docker mirror to Azure China Cloud only since then. I thought the mirror in the docker official install script should be publicly available.
About the site certificate revoke issue, I saw it from my Chrome during my attempt of visiting https://mirror.azure.cn today:

Is it because of https://security.googleblog.com/2016/10/distrusting-wosign-and-startcom.html ?

@lizzha it's not good that the mirror is not publicly accessible - there's no way for us to easily verify that the mirror is complete and mirrors the content correctly...

@Hyzhou not a big deal, but do you think you could make the mirror redirect http to https?

@friism if Docker will verify the mirror, is that OK that we open up some IPs for you to access the mirror?

@twang2218 Not sure why you see the certificate issue. It looks good from my side.

@lizzha certificate which signed by WoSign was revoked by chrome.

@friism I agree. I will try to do that.

@Hyzhou https://test.docker.com has been updated with the Aliyun mirror
Commit hash: cfa611a

@friism Aliyun Mirror used by a lot of service. If we make http redirect https, some service or module which does not support the 3XX redirect probably down. We will transform it gradually.

Aliyun outdated

Can you add other Chinese mirror
example USTC https://mirrors.ustc.edu.cn/docker-ce/

Docker CE has mirror independent. you can find help here.

I already add your QQ ! Can you contact me?

⋊> /e/a/sources.list.d apt-cache madison docker-ce                                                                                00:01:56
 docker-ce | 17.09.0~ce~rc1-0~debian | http://mirrors.aliyun.com/docker-ce/linux/debian stretch/test amd64 Packages
 docker-ce | 17.07.0~ce-0~debian | http://mirrors.aliyun.com/docker-ce/linux/debian stretch/test amd64 Packages
 docker-ce | 17.07.0~ce~rc4-0~debian | http://mirrors.aliyun.com/docker-ce/linux/debian stretch/test amd64 Packages
......

outdated ?

Already solved.Thank you @Hyzhou


Remove '-Zmiri-check-number-validity' and '`-Zmiri-tag-raw-pointers' from Miri

They are just enabled by default nowadays.

Fixed in fa309bd241e3fa21df9637338d4660610b777657


TBI: Enhance some UX parts for 1st release

Description (include screenshots)
This TBI will add some UX changes in preparation for the first release. Please note this is just for a bit of clean up. Future UX enhancements will be made in separate tickets with involvement and direction from UX colleagues.
Currently, the initial launch view of guided answers extensions looks like this:

Please see the tasks below to see list of minor UX enhancements
Value

Good first impressions
Presentable compared to Guided Answers web application

Architecture Elaboration
Does it requires architecture elaboration?
Notes
Tasks
Changes in Guided Answers list page/view:

[x] Add tab title as Guided Answers extension by SAP (https://github.com/SAP/guided-answers-extension/pull/50)
[x] Add SAP icon before Guided Answers header (done with https://github.com/SAP/guided-answers-extension/pull/30)
[ ] Add Interactive documentation designed to help troubleshoot issues, navigate processes and guide through tasks. after Guided Answers header
[x] Add Search title above Search text box
[ ]  Align all the controls and search results correctly in the Guided answers list page

Changes in Guided answers details view:

[x] Align and adjust the font size for the Guided Answers: <name of the branch>
 (done with https://github.com/SAP/guided-answers-extension/pull/30)

[x] Remove the buttons which was carried over from POC. This will be added later as a new feature request with instructions in the guided answers reflecting that

closing, covered with new designs


Unreachable panic starting RGB daemon

When starting version 0.2 of the RGB daemon (rgdb binary), the program panics with the following message:
thread 'main' panicked at 'internal error: entered unreachable code', src/rgbd/runtime.rs:210:9

After further investigation, I realized that this issue is taking place because the main thread is waiting on futures that were supposed to resolve only after the child processes (stashd and fungibled) terminate, but instead are being immediately resolved, and this is due to the fact that, at some point, the tokio::process module that was used to start those child processes has been replaced with the std::process module.
A proposed fix (#126) reverts that change.

After further investigation, I realized that this issue is taking place because the main thread is waiting on futures that were supposed to resolve only after the child processes (stashd and fungibled) terminate, but instead are being immediately resolved, and this is due to the fact that, at some point, the tokio::process module that was used to start those child processes has been replaced with the std::process module.
A proposed fix (#126) reverts that change.

thank you for the investigation; pls see my commend in the PR

thank you for the investigation; pls see my commend in the PR


Resolve syncing conflicts from repo_sync_working_branch to live

Pull request opened by OPS to resolve syncing conflicts from repo_sync_working_branch to live.

@CarolynRowe Hi Carolyn, can you please review, advise, and merge? Thanks!

I am unable to resolve this as it is not my working branch.  Perhaps follow up with James?


License check fails on Edge nodes

Describe the bug
If you try and run the provider against an Artifactory Edge node, you'll see an error:
│ Error: Artifactory requires Pro or Enterprise license to work with Terraform! If your usage doesn't require a license, you can set `check_license` attribute to `false` to skip this check.
│
│   with provider["registry.terraform.io/jfrog/artifactory"],
│   on provider.tf line 11, in provider "artifactory":
│   11: provider "artifactory" {

This is happening because of the check at https://github.com/jfrog/terraform-provider-artifactory/blob/ddb3907c0227f600181e98a4bd170482102223d4/pkg/artifactory/provider.go#L255-L257. Essentially it checks for this:
regexp.MatchString(`(?:Enterprise|Commercial)`, licenseType)

This is the call you get back from the API on an Edge node:
curl -u admin https://XXXartifactory/api/system/licenses
Enter host password for user 'admin':
{
  "type" : "Edge",
  "validThrough" : "Jul 22, 2022",
  "licensedTo" : "XXX"
}

If you read https://www.jfrog.com/confluence/display/JFROG/JFrog+Artifactory+Edge, an Edge node is something that you can only get on an Enterprise+ license.
Requirements for and issue

[ ] A fully functioning terraform snippet that can be copy&pasted (no outside files or ENV vars unless that's part of the issue)
[X] Your version of artifactory (you can curl it at $host/artifactory/api/system/version
[X] Your version of terraform

Terraform 1.1
Artifactory:   "version" : "7.31.10",  "revision" : "73110900",
Expected behavior
Given that most of the resources for an Artifactory instance are valid for an Edge instance, I'd expect to be able to deal with an Edge instance in the same manner.
Additional context
The check_license workaround should be fine here so this isn't an urgent thing our side.

@mikeycmccarthy While we work on the fix, you can set the check_license attribute to false to bypass the license checking. See https://registry.terraform.io/providers/jfrog/artifactory/latest/docs#argument-reference

@mikeycmccarthy While we work on the fix, you can set the check_license attribute to false to bypass the license checking. See https://registry.terraform.io/providers/jfrog/artifactory/latest/docs#argument-reference

You can now skip license check with a flag - but, we'll roll out a fix

This appears to be broken again.
curl -H "Authorization: Bearer $TOKEN"  https://xxxx.jfrog.io/artifactory/api/system/license
{
  "type" : "Edge",
  "validThrough" : "N/R",
  "licensedTo" : "Artifactory Online Dedicated"
}

Terraform v1.2.5

provider registry.terraform.io/jfrog/artifactory v6.11.2
provider registry.terraform.io/jfrog/project v1.1.3

@mcaulifn There's no code changes to the license checking code since May 11th. If this breakage occurs recently, my hunch is something else is causing this issue.


Issue #189

https://github.com/sendgrid/sendgrid-nodejs/issues/189 Fix README mistype

Thanks for the pull request @XEuRoMAN!
This is no longer an issue in the new version of this library, to be released within a few weeks: https://github.com/sendgrid/sendgrid-nodejs/tree/v3beta
Thanks for your support!
With Best Regards,
Elmer


what's in a rot?

are there any special requirements on rot files? anything that needs to be in them? i created a systemd service that runs rotera. it's written in nix. you can find it here: https://github.com/chessai/nixos-configs/blob/master/services/rotera.nix
rotera's home directory is set as /var/lib/rotera, and this is also where the user's specified .rot files are created. however, rotera always fails with "Rotera.open: magic header was invalid", which indicates to me that something is wrong with those files.

note that currently the nix services just calls touch ${r}.rot, for all r in the list of queues you want. nothing else.

The format of these files is not documented anywhere yet. The best way to create a correct one is to run the rotera application that comes with the library.  The first 4 kB are special.  They are a header block, similar in spirit to what LMDB does.  Then, there is the data section which contains the raw messages all butted up against one another. Last is the message offsets section.

Okay, i'll have it do that.

Why does it write the file to 'rotera.bin'?

Why not take a filepath? Also, shouldn't it be a .rot extension?

It uses rotera.bin because I wrote that code much earlier on. It should use a filename something with a .rot extension. And the filename should be configurable with a flag. I've gotten by in my simple testing so far by just renaming the file by hand and using it with rotera-server.

Also, I should add that I love that the name of this issue is "what's in a rot?"

i now have a working rotera systemd service configured with nix

https://github.com/chessai/nixos-configs/blob/master/services/rotera.nix

i made some changes to rotera, i'll need to pr those


 part and i thought i figured it out but it didn't work i even tried playing online but my browser crashes to.
Command Prompt/Terminal logs (if existing)
StrumNote.hx (line 139)
flixel/group/FlxGroup.hx (line 175)
flixel/group/FlxGroup.hx (line 175)
flixel/addons/ui/FlxUIState.hx (line 212)
MusicBeatState.hx (line 70)
PlayState.hx (line 3025)
flixel/FlxState.hx (line 202)
flixel/FlxGame.hx (line 747)
flixel/FlxGame.hx (line 677)
flixel/FlxGame.hx (line 551)
openfl/events/EventDispatcher.hx (line 402)
openfl/display/DisplayObject.hx (line 1399)

Uncaught Error: Null Object Reference
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

I need help.

Not a bug
#9507

ok how do i fix the problem then

never mind i figured it out.


fix error when trying to read 0 bytes at eof

Make sure you have checked all steps below.
Jira
I didn't know about Jira and have no clue what I have to do there
Tests
No tests
Commits
When reading an avro file record for record each time when reading the last record DataFileReader tries to get the next block but (of course) fails. This fixes the issue.
Documentation

Hello @Skeeve !!  My apologies -- I don't follow PRs on this repo and didn't see your fix.  If you have a bug and a contribution, you should make it on the real https://github.com/apache/avro/ repositories for visibility!  That's where releases happen.
We'll probably ask you to create a JIRA with some simple code to reproduce the problem: https://issues.apache.org/jira/projects/AVRO
I can help out there if you like.  If you use Slack there's an Apache Software Foundation workspace at http://s.apache.org/slack-invite -- let's get this fixed for the next release!

Opened https://github.com/apache/avro/pull/1313
Cannot join the Slack Channel :(

Thanks so much and sorry for not checking here earlier!  It looks like you can't self-subscribe to slack any longer but if you're interested, I can send you an invitation by email.
In the meantime, I'll create a JIRA in your place to track this and we'll get some eyes on it to review.

Thanks Ryan. I just contacted you via Linkedin so that I can give you contact details.


Fix style-guide.md endraw rendering

Properly closing raw/endraw to render following variables again
Why:
Example reusables and product names after https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#disclaimers-for-third-party-actions don't render. The culprit being missing endraw above them.
What's being changed (if available, include any code snippets, screenshots, or gifs):
before/after:

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@janbrasna Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


Problems creating a server with TLS and serve_with_incoming

Bug Report

Version

tonic v0.6.2 (originally reported against v0.6.1)
tonic-build v0.6.2 (originally reported against v0.6.0)

Platform

Reproduced on two machines:

Linux bigbox 5.10.0-8-amd64 # 1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux
Linux pbp 5.15.5-1-MANJARO-ARM # 1 SMP PREEMPT Thu Nov 25 11:20:40 UTC 2021 aarch64 GNU/Linux

Description
Hi,  I'm having a rather strange issue:  when I create a server that uses both TLS and serve_with_incoming, my clients can connect, but the clients will hang when trying to make an RPC call.
I created a self-contained repository that can reproduce this problem:  https://github.com/eminence/tonic-test-repo
The simplified version of the server code looks like this:
    let listener = std::net::TcpListener::bind("<IP_ADDRESS>:50051")?;
    let listener = tokio::net::TcpListener::from_std(listener)?;

    Server::builder()
        .tls_config(ServerTlsConfig::new().identity(id))?
        .add_service(PingServiceServer::new(MyPingService {}))
        .serve_with_incoming(TcpListenerStream::new(listener))
        .await
        .unwrap();

(The actual reproduction code in the above git repo is a little more complicated, since it allows you switch turn TLS on/off and switch between serve and serve_with_incoming at runtime).
Removing the tls_config line or replacing serve_with_incoming with serve("<IP_ADDRESS>:50051".parse().unwrap()) causes things to work.
Using the code from the above repo, run the server in terminal A:

cargo run --bin=server -- --incoming --tls

And run the client in terminal B:

cargo run --bin=client -- --tls

But changing any of these options causes the client's RPC call to work.  So we have this curious little table:

TLS
serve_with_incoming
Works?

Yes
Yes
No

Yes
No
Yes

No
Yes
Yes

No
No
Yes

When things don't work, my client's call to endpoint.connect() is successful, but the call to client.ping() hangs.
I can reliable reproduce this issue on 2 different linux machines.
Any hints about what's going wrong, or how to debug this further?
Thanks!

I also tried to reproduce this issue on a Windows machine.  The results are a little different:

TLS
serve_with_incoming
Works?

Yes
Yes
No [1]

Yes
No
Yes

No
Yes
No [2]

No
No
Yes

[1] The client hangs at connect
[2] The symptom here is the same in the original report:  The client successfully makes a connection, but hangs while doing the RPC call
I should note that I don't wait much longer than ~20 seconds when things hang.  I kill the process, so I don't know if they'll eventually become unstuck some minutes later. If you think waiting longer would be usefully diagnostically, let me know.

From discord:
Nylon — Today at 5:23 AM
I think its not bug in tonic, you need to remember to set socket to nonblocking mode if you convert std::net::TcpListener into tokio::net::TcpListener
simple change of adding
let listener = std::net::TcpListener::bind("<IP_ADDRESS>:50051")?;
listener.set_nonblocking(true)?;
let listener = tokio::net::TcpListener::from_std(listener)?;
fixes the issue completely
Image
Image
and from tokio::net::TcpListener::from_std docs
This function is intended to be used to wrap a TCP listener from the standard library in the Tokio equivalent. The conversion assumes nothing about the underlying listener; it is left up to the user to set it in non-blocking mode.
I haven't tested all the possible configurations you listed on github issues and tested only on linux but I think setting the listener to nonblocking mode should fix issue in other configurations

The above is missing setting the socket to non_blocking which should solve the hang.


question about post-training quantization and sparsity

I have three questions:

Question1: I use the .yaml file 1(hs_vgg16_quant_post_train.yaml):

quantizers:
  post_train_quantizer:
    class: PostTrainLinearQuantizer
    bits_activations: 6
    bits_parameters: 6
    bits_accum: 32
    mode: ASYMMETRIC_UNSIGNED
    model_activation_stats: ../quantization/post_train_quant/stats/hs_vgg16_quant_stats.yaml
    per_channel_wts: True
    clip_acts: AVG

and the .yaml file 2:
quantizers:
  post_train_quantizer:
    class: PostTrainLinearQuantizer
    bits_activations: 6
    bits_parameters: 6
    bits_accum: 32
    mode: ASYMMETRIC_UNSIGNED
    model_activation_stats: ../quantization/post_train_quant/stats/hs_vgg16_quant_stats.yaml
    per_channel_wts: True
    clip_acts: AVG
    overrides:
      conv1:
        bits_weights: 8
        bits_activations: 8
      .*add:
        bits_weights: 8
        bits_activations: 8
      fc:
        bits_weights: 8
        bits_activations: 8
        clip_acts: NONE

run the following command-line:
python compress_classifier.py -a vgg16_cifar -p 10 -j 22 ../../../data.cifar10 --resume-from=./logs/vgg16-sparse-1/checkpoint.pth.tar --evaluate --quantize-eval --qe-config-file ../quantization/post_train_quant/hs_vgg16_quant_post_train.yaml

I get the same log file and same output, It sames that the overrides function don't work, I don't know what's wrong with it.
Updated stats saved to logs/2019.12.19-120548/quant_stats_after_prepare_model.yaml
Parameter 'features.module.0.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.0.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.2.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.2.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.5.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.5.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.7.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.7.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.10.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.10.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.12.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.12.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.14.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.14.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.17.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.17.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.19.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.19.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.21.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.21.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.24.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.24.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.26.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.26.wrapped_module.bias' will be quantized to 32 bits
Parameter 'features.module.28.wrapped_module.weight' will be quantized to 6 bits
Parameter 'features.module.28.wrapped_module.bias' will be quantized to 32 bits
Parameter 'classifier.wrapped_module.weight' will be quantized to 6 bits
Parameter 'classifier.wrapped_module.bias' will be quantized to 32 bits

Question2: I know that

Distiller only simulates post-training quantization ......... the way post-training quantization is implemented, supported layers are wrapped with quantize/de-quantizer operations, but the layers themselves are unchanged. They still operate on FP32 tensors, but these tensors are restricted to contain only integer value

but I use the quantilization, and the checkpoint file become smaller. I don't understant why the checkpoint file can become smaller since that the value is represented by FP32?  Does it mean the weight value is stored in the checkpoint file as integer?

Question 3: The last question is not related to the quatization but about the sparsity. when I use

extensions:
  net_thinner:
      class: 'FilterRemover'
      thinning_func_str: remove_filters
      arch: 'resnet20_cifar'
      dataset: 'cifar10'

and
 - extension:
      instance_name: net_thinner
    epochs: [30]

the sparsity becomes zero at epoch  30, and increases from scratch in the following epochs, so the final sparsity is not the "total sparsity". How can I get the true "total sparsity" at the end of the pruning process?
I hope that someone could help me :)

Hi @cindybrain ,
Answer 1:
Your .yaml file doesn't match the modules in vgg16 arch. First off, vgg doesn't have skip-connections, hence '*.add' are irrelevant. In any case, vgg is actually a nn.Sequential model, it's fully connected layer is called classifier, here are the modules:
list(OrderedDict(model.named_modules()))
Out[8]:
['',
 'features',
 'features.module',
 'features.module.0',
 'features.module.1',
 'features.module.2',
 'features.module.3',
 'features.module.4',
 'features.module.5',
 'features.module.6',
 'features.module.7',
 'features.module.8',
 'features.module.9',
 'features.module.10',
 'features.module.11',
 'features.module.12',
 'features.module.13',
 'features.module.14',
 'features.module.15',
 'features.module.16',
 'features.module.17',
 'features.module.18',
 'features.module.19',
 'features.module.20',
 'features.module.21',
 'features.module.22',
 'features.module.23',
 'features.module.24',
 'features.module.25',
 'features.module.26',
 'features.module.27',
 'features.module.28',
 'features.module.29',
 'features.module.30',
 'classifier']

Answer 2: I'm not sure how you got a smaller checkpoint, maybe your original checkpoint contains the model as a whole? Our checkpoint contains only the .state_dict().
Question 3: @nzmora ?

Hi @levzlotnik ,  Really thanks for your help, I notice that I have made a mistake for question 1, and I also understand the answer 2!

Regarding question #3: sparsity is measured relative to the size of the tensors.  For example, if a weights tensor has 100 coefficients, and 20 of them are zeros, then the sparsity is 20%.  If we take the same tensor and physically remove the 20 zero coefficients, we will be left with a tensor of size 80 that has 0% sparsity.
The same thing happens in your YAML schedule: at epoch 30 you perform filter removal.  That means that all filters that have all zero-coefficients are physically removed from the weights tensors and the tensors shrink to a smaller size and suddenly go from x% sparsity to 0% sparsity.  From that point on, if you continue pruning, you will see new sparsity created (i.e. new zero coefficients), but the numbers will be relative to the smaller (thinned) tensors.
Cheers,
Neta

@nzmora
Appreciate for your detailed reply! I know how to compute by using the NNZ(sparse) and NNZ(dense)

Hi,
Closing this issue as it seems all questions were resolved. Feel free to reopen if you have further questions.


Use tini-static in Dockerfile for new alphine docker image

What changes are proposed in this pull request?
Fixes https://github.com/Alluxio/alluxio/issues/14079
change to install tini-static which includes all its dependencies
Why are the changes needed?
alphine doesn't have tini dependencies
Does this PR introduce any user facing changes?
It supports tini -- entrypoint.sh to continue working in kube scripts

Just verified this using our internal testing framework, thanks!

alluxio-bot, merge this please


feat: esm and cjs builds for node and browser

Hi @devongovett ! Hope you are doing good.
I'd like to start using foliojs packages again in react-pdf. I gradually moved away from them due to several reasons, among them because node deps in foliojs repos. This includes pdfkit and png-js.
Here's my fork. This is the same node entrypoint here but bundled with rollup to generate node and browser entrypoints. Node ones are just like the existing ones. For browser though, we remove fs dependency and ignore methods that use it, and replace zlib with browserify-zlib.
Not sure who's responsible of reviewing and publishing (I have merge rights here, but not publishing to npm) but this first step would be very helpful towards start unifying foliojs with react-pdf 😄

Thanks for the review @blikblum ! when can we expect to have this merged?

Need one more review


FIx for SOCIAL_AUTH_NEW_USER_REDIRECT_URL not working

Hi matias, a small fix to keep SOCIAL_AUTH_NEW_USER_REDIRECT_URL working, as it was broken a couple commits ago by the pipeline system.

I'll merge this if you implement the little commented change

Hi omab, could you merge this, please? I need the fix, too.


Integrate registration-only package usage with use-package

After #44 is implemented, we'll want to automatically use it when the use-package keyword :if is present.

This really isn't necessary for the 1.0 release, and should probably wait until with-feature is ready.

See https://github.com/raxod502/straight.el/issues/235#issuecomment-366342968.


possible to use user defined lpdfs?

Can stanc generate the relevant cpp to be used in this repo?

It can yes. Great idea!

nice, do you have plans to show bivariate distributions?

I do. Not sure on the exact plots to use, but yeah, definitely want to add those as well.


git checkout master before each exercise

Exercises could mention to make sure you are on the default branch before you start.  This doesn't matter if you follow these steps exactly, but are important in general when coming back to a project to do things.

I don't think this is needed / adds too much text.  maybe more important for git-intro - I wonder if I mis-filed it.


[Technical Discussions-Media Push] Context Propagation

when: bi-monthly
Day: Fridays
Time: 6:30-7am  PDT (change to EU time)
Calendar
Twitter description
Answers: Why should I join and contribute to this project?

Left a comment in the agenda: https://docs.google.com/document/d/1WWyBjtGxZAwIKHvM6wjjY8nQ_x9Cc7WnvMosGuwodG4/edit?pli=1
Tasks: https://github.com/eclipse/microprofile-marketing/issues/412#issuecomment-806167114

@aeiras I'm unsure of what is being asked for here.  I can see on the calendar that the monthly call for MP Context Propagation (previously MP Concurrency) has run out of repeats as of next month and needs to be rescheduled -- thanks for making me aware of that, even if it wasn't the intent of this issue!  I also see that you've added a comment to the meeting minutes.  Is there a new process for meetings and meeting minutes and where/how they are recorded?  Or is the request something else entirely?  I apologize if I'm just unaware of these things because I haven't been attending the wider MicroProfile meetings lately.  Do you have a link to any documentation on what needs to be done differently?

Hola Nathan, @njr-11,
Thank you for coming to this repo. I appreciate your prompt reply. :)
Actually, It was also the intent too make you notice the calendar. The calendar event was still set with old name and it went weekly. I took the liberty to delete  it once I read the minutes and I knew you were active in the project. I assigned you to the ticket specially because of it. (smily face insert)
Here is what we need from Context Propagation MicroProfilers:

[ ] move the current agenda minutes to the MP Minutes drive   the folder will be added to the MPWG page as part of documentation on how to reach MicroProfilers.
[ ] Via the MPWG, we only just secured a dedicated paid Zoom account, so every call needs at least 2 Admins from each API, it can be more if the group deems it so.  Can you get that information so we can provide you with admin access so that Admin can record to the Cloud and all the videos get added to the MP youtube?  Admins won't have to do a thing, just record and done.
[ ] can you provide a good written twitter description of the dynamics of the call?  For example:

Community Call- Twitter
Marketing call- twitter

[ ] lastly, consider submitting an MP quote, you and all those around you who make MP amazing. go to "Submit your quote" call to action

Thanks for the clarification. I've moved the meeting minutes over to the new MicroProfile drive location under the Context Propagation folder,
https://docs.google.com/document/d/1Iy_k-Yaq3AnfWaZ97z2CjOf4LLt71UnaVw8NAbyeVDs/edit?usp=sharing
That's great to hear we have a Zoom account again so we can stop using our separate company-specific web conferences.  @FroMage and @manovotn and @nmittles would you all agree to be admins as well as myself?  I'll also ask on the gitter chat if anyone else is interested, both to be admins as well as for the other items (submitting MP quote) that Ameila posted in the prior comment.

You are amazin Nathan! @njr-11
While you are an example of doing fun things to broadcast the Project with the other MicroProfilers, can you help write the tweet for the call?  Use the Calendar spacial link in that tweet: https://bit.ly/calendar-zoom-minutes
Example:
Join Today's #MicroProfileCommunityCall & let your actions show a commitment to the evolution & sustainability of #MicroProfile. #MicroProfilers' participation ensures continued growth & development of a well-governed, vendor-neutral #OpenSource ecosystem.
_https://bit.ly/calendar-zoom-minutes_
Next call is not yet scheduled yet coming up middle of April, correct?
Zoom- today we discussed the access redistribution in the community call. Conversation not completed just yet, but we have the zoom. :)
quotes
Check this out:

https://github.com/eclipse/microprofile-marketing/issues/406#issuecomment-809831513
listed and rotating every 15 seconds in the MPWG page
this page and media needs all #ossDOERs to share some light on contributing in MP, it is simply fun and inspiring.

Abrazos and thanks for pushing forward,

I'm hoping to get agreement on the Zoom admins at our next meeting, which means for April we will still be using the company-specific webex that we've used for the past several months, and then hopefully switch over to the MicroProfile Zoom for May.

Sounds wonderful, Nathan.
2 Zoom dedicated Admins is perfect.
What about the status on submitting:

the 2021 tweet for May & future calls? an example that went out today that is scheduled for steering calls 2021
quotes from every MicroProfiler, whose actions inspire collaborating in Context Propagation?

more.

Remember, any MicroProfiler can submit business tickets via this Repo to requests things that could improve the project communicating better with the world.
Let the system we have in place help the project get new contributors. Just submit new git issues with project updates worthy of attention or issues that must be tackled and need more visibility so that media can push such stuff.
Abrazos,

Received and sent!
I will close this ticket, the expectation is for both of you to gain access to zoom, latest next week.
If you don't. Please re-open the ticket or use the private email to request an update on why the delay.
Nathan,
A Context Propagation Youtube playlist will be added to the MP youtube channel to hold the recordings moving forward.  That is assuming, either you or @FroMage always record the call to the Cloud.  Any issues with it?
Your feedback is preferred. We cannot push you to record the calls, yet I personally recommend the recordings. If you cannot own it for the world to see 5years from now, then, it is truly not OSS> :)

Hey Nathan @njr-11 and Stéphane @FroMage
The very 1st media push for the technical meeting went out today. That team chose to use the already set message for the Community call MP media push.
You could choose to use the same working as well.
Did you two gain access to the Zoom account yet? This is a follow-up!
https://twitter.com/MicroProfileIO/status/1384522242080448527?s=20

This morning, John and I met with @@njr-11 to test his new zoom admin access.
Thank you Nathan the patience through the infra testing.

@rstjames, thank you in advance for helping us push this API media call!
When
2nd Thursday, 1 a month
Time:
6:30- 7:30 AM PDT- let's convert to Easter time instead of PDT
Twitter:
_Join today's #ContextPropagationCall to discuss & contribute to the API's technical direction. #MicroProfilers' participation ensures continued growth & development of a well-governed, vendor-neutral #OpenSource API.
Join: https://bit.ly/calendar-zoom-minutes
#ByCommunityForCommunity #OSS_

Suggestions for additional clarification to the Zoom Admin doc based on this morning's conversation have been added to
https://docs.google.com/document/d/1xTBnhJ2SjDmLjM6OTyRVjSnjb6r5s8_opGjSyZnD5vA/edit

Your wonderful suggestions have been accepted into the document. Thank YOU, @njr-11! 💯
As a follow-up, should MicroProfilers wish to connect next Thursday, the event has been created and is public in the calendar [John did it before returning to his PTO :) ].  Please, do not stress about the event. If there is no need for that special call, please follow up via this ticket with a "delete" request.   I will delete the call from the public calendar, OK. Just let me know early next week!
Nathan, thank you for caring enough to improve the documentation!

As a follow-up, should MicroProfilers wish to connect next Thursday, the event has been created and is public in the calendar [John did it before returning to his PTO :) ]. Please, do not stress about the event. If there is no need for that special call, please follow up via this ticket with a "delete" request. I will delete the call from the public calendar, OK. Just let me know early next week!

Yes please go ahead and delete the extra MP Context Propagation meeting entry that is on the calendar for this Thursday, May 27.  When I checked with the community, there wasn't anyone wanting to have the meeting then.  Our upcoming June meeting will be close enough.  Thanks!

Deleted. Thank you, Nathan!

@rstjames, thank you in advance for helping us push this API media call!
When
2nd Thursday, 1 a month. Starting June 2021.
Time:
6:30- 7:30 AM PDT- let's convert to Easter time instead of PDT
Twitter:
_Join today's #ContextPropagationCall to discuss & contribute to the API's technical direction. #MicroProfilers' participation ensures continued growth & development of a well-governed, vendor-neutral #OpenSource API.
Join: https://bit.ly/calendar-zoom-minutes
#ByCommunityForCommunity #OSS_

@rstjames can you help us scheduled this please?

scheduled for the year.

Thank you, beautiful Ryan!
@njr-11 🤗
the API is all set up.
thank you for helping us pilot everything about zoom, Google drive, documentation …
when you & the context propagation MicroProfilers wish to submit your quotes, just read the guidelines. Your quotes are welcomed at anytime 💛


MNT: Use noarch python {{ python_min }} variable

Use 'python {{ python_min }}' syntax for the python requirements for noarch python recipes.

c.f. https://conda-forge.org/docs/maintainer/knowledge_base/#noarch-python

Use a Jinja2 set statement for python_min to keep all the build metadata contained in the recipe/meta.yaml and override the global python_min with vector's python_min of 3.8.
Remove --no-deps --no-build-isolation 'pip install' options in recipes as the build tool (e.g. conda-build, rattler-build) will enforce all required 'pip install' options itself at build time.

c.f. https://github.com/conda/grayskull/issues/582

Bump build number.

Checklist

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

@conda-forge-admin, please rerender

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


'coroutine' object is not subscriptable

BUG REPORT
High Level Description
[Describe the problem in short]
====================================================== FAILURES ======================================================
___________________________________________________ test_notebook1 ___________________________________________________
[gw0] linux -- Python 3.7.6 /home/deeplp/anaconda3/bin/python
nb_regression = NBRegressionFixture(exec_notebook=True, exec_cwd='/tmp', exec_allow_errors=False, exec_timeout=120, coverage=False, co...place=(), diff_ignore=('/cells//outputs//traceback',), diff_use_color=True, diff_color_words=False, force_regen=True)
notebook = '/tmp/tmpgcz3x71l.ipynb'
def test_notebook1(nb_regression: nb.NBRegressionFixture, notebook):

    ## Generate from the un-run notebook
    nb_regression.force_regen = True

  nb_regression.check(notebook, False)

smarts/core/tests/test_notebook.py:105:
SMARTS version
[e.g. 0.4.12]
0.5
Previous associated issues
[Link any associated issues here]
Steps to reproduce the bug
[Description or code snippet to help reproduce the bug]
Resulting and expected behaviour
[e.g. Should print out "Hello world" but crashes with "Error: stack overflow"]
Error logs and screenshots
[Text or screenshots (preferably text)]
System information

Operating system & Environment [Please note if using Docker]:
Number of system cores available
Python version [Please note if using Jupyter]
Python packages [e.g. from pip freeze]
SUMO version
Date when bug occurred

ubuntu16.04
python3.7.6
Impact [If known]

@scalaboy Hello, thank you for the report. A package version change has caused this problem, it has no impact and will be solved in the next version.
If you need Jupyter you will need to pip install ipykernel.


New measure - fluoroquinolones item vs all oral antibiotics items

I think the spelling should be: fluoroquinolones ?

Thanks! Fixed.

Closed in favour of https://github.com/ebmdatalab/openprescribing/pull/4602


Support Matrix "Local Echo" when dealing with card fragments

The issue we were encountering in staging where we would get missing card fragment errors was due to a matrix feature called "local echo". This feature allows matrix clients to handle local messages before they have received a matrix server response. These locally echoed events are special in that their event ID's are actually not "real" event Id's rather the event ID is actually a transaction ID, and according to the matrix spec, the onus is on the client to correlate locally issued events with events received from the server (which have the real ID in them). so our client was dutifully gathering event Ids from card fragments and setting those in our boxel messages. However, the locally received events had transaction ID's masquerading as event ID's and the card fragments could not be constructed properly due to this ID mismatch. Oddly, when the matrix server is running locally, local echoes are not used (probably the matrix client is able to recognize this particular scenario and disable the feature).
The fix here is to use transaction ID's instead of event ID's for stitching together the card fragments since we can rely on those being consistent. Additionally, I added some logic to migrate the existing matrix events since this is a breaking change. We should remove this migration the next time we reset the state of the hosted matrix.

Arg--hold off on this review. it looks like our matrix tests reveal that the txn ID is sometimes not present. I need a different approach....


demarcate.js still under development

Is demarcate.js still under development?

@confile, I'm no longer actively developing demarcate but I'm happy to accept pull requests etc.


KAFKA-8398 Avoiding NPE in ByteBufferUnmapper#unmap()

https://issues.apache.org/jira/browse/KAFKA-8398
Regularly seeing this NPE when shutting down the broker in our tests. I think simply returning early in this case should suffice.
Hey @ijuma, could you take a a look at this one perhaps? Thanks!

Hey @rhauch, could you pick up and review this one perhaps? Thanks!

Thanks for the PR. This was originally submitted as #7387. I think the approach in that PR is better, so revived it via #8983 (with original authorship preserved).

Makes sense. So I'm going to close this one here, looking forward to the other fix being released soon. Thanks!


CamelCasePropertyNamesContractResolver on complex objects

Using MVC 6.0.0-rc1-final and Newtonsoft.Json 8.0.3
Got this configuration in Startup.cs
serviceCollection.AddMvc().AddJsonOptions(
                options => {
                        options.SerializerSettings.ContractResolver = new CamelCasePropertyNamesContractResolver();
                    });

And serialising this object:
public class Foo
{
   public IEnumerable<Bar> Bars {get;set;}
   public string Name {get;set;}
}

where Bar has its own various properties.
What we end up with is properties within Foo are correctly camelCased but any properties within Bar are still PascalCase. Am I doing something wrong here?

UPDATE:
Looks like I am doing something wrong. The object I am returning is coming straight from DocumentDB, meaning it is already serialised, so it doesn't go through the serialiser again.
I created a test project with the same settings and objects and its serialising everything as expected.
Sorry for the false flag.


Some fields need to be removed or renamed

DisplayPort_Product_Summary
Device_Power_Source (USB VIF has this information already)
SOP_DP_Capabilities

The following fields need to be removed

DP_Receptacle_Indication (I think this should be removed, but seems Jacob want to keep it and check the consistency of it vs the Captive_Cable USB VIF field)
Signaling_For_Transport_Of_DisplayPort_Protocol (because there is only 1 possible value: 1)
DP_Alt_Mode_Version (this is the same as the DP_Version field)
DP_Mode_Auto_Entry (no such device has ever been seen, and if there is one, we don't know how to test it)

USB2_Used needs to be renamed to USB2_Not_Used

SOPP_DisplayPort_Capabilities

All fields need to prefix with SOPP_
DPAM_Version needs to be removed

DisplayPort_Status
DP_Src_Sink_Device_Connected needs to be removed because this is a dynamic field

DP_Receptacle_Indication (I think this should be removed, but seems Jacob want to keep it and check the consistency of it vs the Captive_Cable USB VIF field)

@TimWei888 I would also vote to keep the field in the VIF tool, since in my observation the DP_Receptacle_Indication bit is older and more consistently implemented compared to the one in USB PD's ID Header VDO. I actually added the receptacle indication in ID Header VDO, and I recognize it was only present in most recent USB PD implementations.
The DP one came first, so we should use it for consistency check.
Also, the value returned for Receptacle Indication here has implications for the VIF tool description as well, now that I think about it. Basically, if the VIF is describing a product that has a receptacle, then all of the fields in the VIF regarding SOP' are irrelevant, since the product being tested doesn't inherently have a SOP'. In test, the test equipment will provide a SOP' where it makes sense.
However, if the VIF describes a captive plug, then the product contains a captive cable, and if it's DPAM 2.1, it must be e-marked, so a SOP' is expected, and should be tested for (and therefore, the test equipment does not need to emulate a SOP' when testing this product).
What do you think, Tim?

USB2_Used needs to be renamed to USB2_Not_Used

I'd prefer to reverse the values of the field and keep the name as USB2_Used. That would be incompatible with previously generated VIFs, but it would avoid having to think about a double negative while filling out the fields.

DP_Mode_Auto_Entry (no such device has ever been seen, and if there is one, we don't know how to test it)

I didn't understand quite what this means in the spec. I took it to be a source that will enter DP alt mode when it sees that it's available, without waiting for some action on the part of the tester. If that's what it means, I would think this would apply to most DP sources.

DP_Alt_Mode_Version (this is the same as the DP_Version field)

I don't think that you can support DP 2.1 with alt mode version 2.0. But I think you may not support DP 2.1 while supporting DPAM 2.1, e.g. you use the DPAM 2.1 to advertise that you only support DP 1.4. If that's valid, then I don't think these fields mean the same thing.

I was not talking about the field in the ID header, I was talking about the VIF field Captive_Cable in the USB VIF, which has been there since the very beginning. I don't have a very strong opinion here, I am fine to keep this field.

DP_Receptacle_Indication (I think this should be removed, but seems Jacob want to keep it and check the consistency of it vs the Captive_Cable USB VIF field)

@TimWei888 I would also vote to keep the field in the VIF tool, since in my observation the DP_Receptacle_Indication bit is older and more consistently implemented compared to the one in USB PD's ID Header VDO. I actually added the receptacle indication in ID Header VDO, and I recognize it was only present in most recent USB PD implementations.
The DP one came first, so we should use it for consistency check.
Also, the value returned for Receptacle Indication here has implications for the VIF tool description as well, now that I think about it. Basically, if the VIF is describing a product that has a receptacle, then all of the fields in the VIF regarding SOP' are irrelevant, since the product being tested doesn't inherently have a SOP'. In test, the test equipment will provide a SOP' where it makes sense.
However, if the VIF describes a captive plug, then the product contains a captive cable, and if it's DPAM 2.1, it must be e-marked, so a SOP' is expected, and should be tested for (and therefore, the test equipment does not need to emulate a SOP' when testing this product).
What do you think, Tim?

USB2_Used needs to be renamed to USB2_Not_Used

I'd prefer to reverse the values of the field and keep the name as USB2_Used. That would be incompatible with previously generated VIFs, but it would avoid having to think about a double negative while filling out the fields.

This is the way it is defined in the spec "USB 2.0 Signaling Not Used", I like the VIF definition to be the same as what in the base spec, so that we can use the value directly.

DP_Mode_Auto_Entry (no such device has ever been seen, and if there is one, we don't know how to test it)

I didn't understand quite what this means in the spec. I took it to be a source that will enter DP alt mode when it sees that it's available, without waiting for some action on the part of the tester. If that's what it means, I would think this would apply to most DP sources.

I don't understand what this means either, I have never seen any DPAM UUT works differently from others, maybe we should clarify this in the working group meeting.

DP_Alt_Mode_Version (this is the same as the DP_Version field)

I don't think that you can support DP 2.1 with alt mode version 2.0. But I think you may not support DP 2.1 while supporting DPAM 2.1, e.g. you use the DPAM 2.1 to advertise that you only support DP 1.4. If that's valid, then I don't think these fields mean the same thing.

You raised an interesting point here. Let's discuss it in the working group meeting. Even it's true, we should move it to the 1	DisplayPort_Product_Summary group, we should not allow an UUT to have different DPAM version on SOP and SOP Prime.

This is the way it is defined in the spec "USB 2.0 Signaling Not Used", I like the VIF definition to be the same as what in the base spec, so that we can use the value directly.

That's fair. Objection withdrawn.


Update to 9.x

Hello! Just checking in to see if there are any plans to update this module to higher versions, such as 9.x? This module is an absolute lifesaver and I would love to use it, there's just nothing else like it out there!
I have no experience in writing modules for Foundry VTT, but I'm happy to help out if it makes it easier!

#12 added compatability for 9.x!


Add class averages to course page

https://demetrios-koziris.github.io/McGillEnhanced/class-ave-crowdsourcing

Do we wanna add averages in the course model?


Prerequisite Update.

Cinder V1 produced following error:

Your OpenStack
  API
    rate limit
      is high enough... passed
    Security groups
      has ingress rule for SSH... passed
      has egress rule for HTTP... passed
      has egress rule for DNS... passed
  using the CPI
    can save a stemcell... passed
    can create a VM... passed
    has VM cid... passed
    can set VM metadata... passed
    can create a disk in same AZ as VM... failed

Failures:

  1) Your OpenStack using the CPI can create a disk in same AZ as VM
     Failure/Error: fail("#{error_message} OpenStack error: #{e.message}")

     RuntimeError:
       Disk could not be created. OpenStack error: undefined method `name' for nil:NilClass
     # ./src/specs/cpi_lifecycle_spec.rb:8:in `rescue in with_cpi'
     # ./src/specs/cpi_lifecycle_spec.rb:6:in `with_cpi'
     # ./src/specs/cpi_lifecycle_spec.rb:77:in `block (2 levels) in <top (required)>'
     # ./lib/validator/cli/cf_openstack_validator.rb:211:in `block (2 levels) in execute_specs'
     # ./lib/validator/cli/cf_openstack_validator.rb:210:in `open'
     # ./lib/validator/cli/cf_openstack_validator.rb:210:in `block in execute_specs'
     # ./lib/validator/cli/cf_openstack_validator.rb:174:in `with_environment'
     # ./lib/validator/cli/cf_openstack_validator.rb:196:in `execute_specs'
     # ./lib/validator/cli/cf_openstack_validator.rb:21:in `run'
     # ------------------
     # --- Caused by: ---
     # NoMethodError:
     #   undefined method `name' for nil:NilClass
     #   ./lib/validator/api/resource_tracker.rb:127:in `produce'

Finished in 1 minute 42.53 seconds (files took 0.09803 seconds to load)
9 examples, 1 failure

I'm sorry for late about CLA. My boss becomes too busy to be interested in my contribution to opensource right now. So, please give me more time...

Hey @kukgini thanks for the PR!
The validator should be working for cinder v1, it seems something went wrong when checking for the disk to be present. Could you please attach the testsuite.log of your run, so we can check the calls to the OpenStack CPI? Thanks!

I can't go that environment any more. But here's what i found:
There's available both version v1 and v2 on cinder only diffrent url (like /v1, /v2).
And Horizon returns v1 api end-point.
I debug into Fog Library and found lib/validator/api/fog_openstack.rb line number 28~36
always enter into 31 line.
So, When I comment out 31,32 Line like below, the problem goes away:
 28         def volume
 29           handle_socket_error do
 30             begin
 31 #              Fog::Volume::OpenStack::V2.new(convert_to_fog_params(openstack_params))
 32 #            rescue Fog::OpenStack::Errors::ServiceUnavailable
 33               Fog::Volume::OpenStack::V1.new(convert_to_fog_params(openstack_params))
 34             end
 35           end
 36         end

Maybe it will be some help.

Oh, there's another problem. Even if I force using api v1 mentioned above, validator always expect 'name' field which is previously called 'display_name' in cinder api v1. so I also changed lib/validator/api/resource_tracker.rb like this:
@@ -124,7 +128,7 @@ module Validator
               type: type,
               id: resource_id,
               provide_as: provide_as,
-              name: resource.name,
+              name: (if type == :volumes || type == :snapshots then resource.display_name else resource.name end),
               test_description: RSpec.current_example.full_description
           }
           resource_id

This indeed looks troublesome. I'm trying to get my hands on a system with only cinder v1 enabled to reproduce and fix this. Thanks!

When you fix it, please let me know. So, I can close this pull request which is no need any more. Thank you.

Thanks, I could finally reproduce. We will fix cinder v1 usage and update the validator.
Thanks for reporting this!

Here is our story to work on this: https://www.pivotaltracker.com/story/show/143495821

@voelzmo registered this bug as an issue. maybe someday it can support cinder V1 correctly.
this pull request should be closed. thanks.


Upgrading from Storybook 4.1.13 to 5.0.0 - Cannot find module<EMAIL_ADDRESS>

Describe the bug
When upgrading from Storybook 4.1.13 to 5.0.0, an attempt to run start-storybook results in the error message Error: Cannot find module<EMAIL_ADDRESS>There is no node_modules/@emotion/core folder. The only copy that gets installed is due to the dependencies within<EMAIL_ADDRESS>so it's not at the top-level node_modules folder, but instead at node_modules/@storybook/theming/node_modules/@emotion/core.
To Reproduce
Steps to reproduce the behavior:

Start with the following dependencies:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Upgrade to Storybook 5:

> yarn remove @storybook/addon-options
> yarn upgrade --latest @storybook/react @storybook/addon-actions
      @storybook/addon-knobs @storybook/@addon-storyshots
> yarn add --dev --exact @babel/core babel-loader

Attempt to start Storybook

> yarn run start-storybook -- -p 9001

Environment
Windows 10
node 10.15.0
yarn 1.13.0

Additional context
Removing yarn.lock and node_modules and reinstalling purely from the package.json file also fails.

Note that installing @storybook/theming fixes the error - is this package now mandatory?

Should not be mandatory. We're still trying to get to the bottom of this -- feels like a yarn bug, but it's all pretty opaque. @emotion/core and @storybook/theming are def in your dependency tree, but they are just not getting hoisted properly AFAIK.

Im getting the exactly same error with npm and package-lock. Error: Cannot find module<EMAIL_ADDRESS>

Resolving this as a duplicate to https://github.com/storybooks/storybook/issues/5919
We still don't know what's going on tho


srm-cuarzo: 0.5.5-1 -> 0.5.6-1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/CuarzoSoftware/SRM/releases.
meta.description for srm-cuarzo is: Simple Rendering Manager
meta.homepage for srm-cuarzo is: https://github.com/CuarzoSoftware/SRM
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5.6-1 in filename of file in /nix/store/nw4plxlf69pyiyixq35v3srngpc2q273-srm-cuarzo-0.5.6-1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
louvre
srm-cuarzo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nw4plxlf69pyiyixq35v3srngpc2q273-srm-cuarzo-0.5.6-1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A srm-cuarzo https://github.com/r-ryantm/nixpkgs/archive/ad83596e07ed8c0aedd15872f4a772a5d66f974c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ad83596e07ed8c0aedd15872f4a772a5d66f974c#srm-cuarzo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nw4plxlf69pyiyixq35v3srngpc2q273-srm-cuarzo-0.5.6-1
ls -la /nix/store/nw4plxlf69pyiyixq35v3srngpc2q273-srm-cuarzo-0.5.6-1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

louvre
louvre.dev
srm-cuarzo
srm-cuarzo.dev

Maintainer pings
cc @2xsaiko for testing.

@NixOS/nixpkgs-merge-bot merge


skale.js

SKALE.js
SKALE.js is a community run project designed to offer abstraction over the core SKALE network smart contracts.
Some of the available packages are:

@skaleproject/ima: provide content to help using IMA, the SKALE native bridge
@skaleproject/pow-ethers: SKALE proof of work mechanism written with Ethers library
@skaleproject/pow-web3: SKALE proof of work mechanism written with web3 library
@skaleproject/utils: package with utility scripts, such as, interaction with SKALE access_control predeployed contract

For more information check the project GitHub repository.

What is: Library
Language: Javascript, Typescript
Target: Web


AccessToken methods must take a context

Any method that can refresh or get a new access token may call out to another service, and must be cancellable

@dmihalcik-virtru What access token methods are you referring to?


User Testing: test app without sign-in feature to focus on app interactivity

Summary
Let's test the app without the sign-in feature to focus on the app's interactivity.
The sign in flow has some issues based on the three user interviews I performed.
It blocking the testing of the app's other features.
On the suggestion of one user, we should have an instance of the app without the sign-in.
That way we can test the maps, swiping cards, etc.
Motivation
Why are we doing this?
The current blockstack log-in is causing issues with most users I am interviewing.
We can test the sign-in feature separately to gain insights on how to improve.
In the meanwhile, we can also test the features we are building without the sign-in to
allow for faster iteration times on the other core features.
In short, we can test features in parallel.
What use cases does it support?
Improving the other features of app with feedback from real users.
What is the expected outcome?
We can gain user feedback related to the features and improve them iteratively
Describe alternatives you've considered
Fixing the blockstack sign-in first.
Using blockstack/connect was suggested. But, this will require time that may block the front end team during its implementation.
Additional context
Nope.

I don't think we need this at this point - at least, I should scope out issues for creating true QA and Staging environments, and then perhaps in one of those we'll add a way to not require tests


run on target rest api

Is it possible to run the Owasp Zap azure devops task on rest api's.
I found in the documentation of Owasp zap that this is possible through docker but I was hoping of this could work through the owasp zap azure devops task. without changing my entire build.

"Because the authentication of the rest api needs some kind of token or credentials, it may not be possible to use a vm let alone to put this inside some kind of CI/ CD pipeline."

It depends on how authentication is supposed to happen. In some cases, you can create a context for the API using the ZAP desktop app and export it to a context file. You can provide the context to a scan, so it'll know how to authenticate and using which credentials.
Alternatively, if the API depends on something like a JWS in a header, you can provide a Replacer rule that inserts the JWS header into each request.

Azure calls can be made via powershell.
For example I use it to close the instance when it finishes scanning: you have to do this in a task of PowerShell:
Invoke-WebRequest -Uri "http://localhost:$(Port)/JSON/core/action/shutdown/?apikey=$(keyOwaspZapProxy)"
then with this method you can make any type of call.


osd: try to activate when the osd if exist

closes: #406 and #326
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

@jianyunet please have a look.


No authenticated user or shop domain

Package Version: v17.1.1
Laravel Version: v8.56
PHP Version: v7.4.28
Using a toolset (Vapor):

Failure Logs

No authenticated user or shop domain

{
  "exception": {
    "class": "Osiset\ShopifyApp\Exceptions\MissingShopDomainException",
    "message": "No authenticated user or shop domain",
    "code": 0,
    "file": "/var/task/vendor/osiset/laravel-shopify/src/Traits/AuthController.php:33"
  }
}

Having the same problem with Laravel version 8, unable to get Auth::user()
use Illuminate\Support\Facades\Auth;
$shop = Auth::user();

Hi @pengbo37877 @KingFisch @yousuf-mean3
When does this error occur?

Hi @pengbo37877 ,
Having the exact same issue there. I'm actually running Vapor also (not sure if it's related).
The unfortunate timing of this error, it seems to occur after customer approves charge for installation. I myself can't seem to replicate it. Have you got any further with it?
Thanks

Hi @pengbo37877 @KingFisch @yousuf-mean3
When does this error occur?
This occurs in controller

Am getting this issue now. anyone able to find a solution ?

Hi @pengbo37877 @KingFisch @yousuf-mean3
When does this error occur?

As soon you open the project in browser. In shopify its mostly working. Any ideas?

@KingFisch fullscreen app is not currently supported with this package. It has to be in the shopify admin or you will get this error.


Cleanup minor changes for HybridGlobalization

Multiple changes: In azure-pipelines.yml, remove false hybridglobalization as it is the default and use additionalJobIdentifier instead of adding hybridglobalization to all the jobs. In maui_scenarios_ios.proj, make it so HybridGlobalization only shows up in the HG true run titles and switch to using a RunConfigString that includes all runconfigs where they are created for easy addition of configs to all scenarios. In scnearios.yml, add HybridGlobalization as a build config when true and remove it from the job name (switched to using additionalJobIdentifier).

Test run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2255505&view=results coreclr startup appears to be having problems both with and without hybrid globalization, but the saved results correctly have HybridGlobalization in the names and runconfigs.


add Spring Boot Ehcache (Java Configuration)

#121 (alternative to #431)
This is the version with Java configuration.
Quite verbose, will less flexibility than the XML configuration but a common needle for all JCache implementations.
Generator:

[x] Ehcache
[x] rename to java-configuration

Generated:

[x] EhcacheConfiguration
[x] jhipster-needle-jcache-add-entity
note 1: "jcache" needle because we can add entities at a single place for all JCache providers
note 2: explicit "entity" needle because it uses a template to have a shared ttl and max-entries
[x] integration test of the configuration (2 properties...)

This is based on a common branch: https://github.com/pblanchardie/jhipster-lite/tree/add-spring-boot-jcache

[x] Spring Boot Cache Commons (spring-boot-starter-cache + CacheConfiguration)
[x] Spring Boot JCache Commons (jcache)
[x] Spring Boot JCache Java Config (Java configuration)

will rebase

I still prefer this version, over XML one :)
But we can keep both, see my comments
As soon as the last suppressWarning is added, I can merge it, unless you want to rename some methods for keeping both solutions.

looks like action failed for a mysterious reason, re-running job could help

@pblanchardie : I'm playing a little bit with this version, to add new custom cache and it was a little bit more complex than the one from generator-jhipster
My question is:

why not using a single file for CacheConfiguration, which should look like: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java
because, with this version, I can:

add a new cache with specifc value: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java#L24
build it in constructor: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java#L29-L35
and create the cache: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java#L56

@pblanchardie : I'm playing a little bit with this version, to add new custom cache and it was a little bit more complex than the one from generator-jhipster
My question is:

why not using a single file for CacheConfiguration, which should look like: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java
because, with this version, I can:

add a new cache with specifc value: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java#L24
build it in constructor: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java#L29-L35
and create the cache: https://github.com/jhipster/jhipster-sample-app/blob/main/src/main/java/io/github/jhipster/sample/config/CacheConfiguration.java#L56

why not using a single file for CacheConfiguration

Short answer: sure we can, it would be simpler on the generated side.
Long answer: I wasn't comfortable with the single-CacheConfiguration.

code and test duplication in the generator for each cache provider
hard to test with private methods (make them package-private and it should be ok)
mixing "declarative" configuration with logic

Yes, the drawback is that the generated code has more Java classes, but you can still add a custom caches the same way than before in JCacheConfiguration (at jhipster-needle-jcache...) by using the utility methods of the injected jCacheCreator, which is provider-agnostic but accepts any Configuration, and the code of this JCacheConfiguration class is shorter.
All the provider-specific code is isolated in the relevant subpackage, as we leverage JCache abstraction.
Indeed, if you want to have multiple cache configurations, then better go with the XML file or single CacheConfiguration so everything is at the same place.
The current implementation can seem overkill unless you want to support multiple cache providers.
We can get rid of this and switch to a single CacheConfiguration, but we'll have the same boilerplate code in each cache provider feature of the generator.
If the ultimate goal is to keep the generated code stupid simple, that's probably a better choice.

why not using a single file for CacheConfiguration

Short answer: sure we can, it would be simpler on the generated side.
Long answer: I wasn't comfortable with the single-CacheConfiguration.

code and test duplication in the generator for each cache provider
hard to test with private methods (make them package-private and it should be ok)
mixing "declarative" configuration with logic

Yes, the drawback is that the generated code has more Java classes, but you can still add a custom caches the same way than before in JCacheConfiguration (at jhipster-needle-jcache...) by using the utility methods of the injected jCacheCreator, which is provider-agnostic but accepts any Configuration, and the code of this JCacheConfiguration class is shorter.
All the provider-specific code is isolated in the relevant subpackage, as we leverage JCache abstraction.
Indeed, if you want to have multiple cache configurations, then better go with the XML file or single CacheConfiguration so everything is at the same place.
The current implementation can seem overkill unless you want to support multiple cache providers.
We can get rid of this and switch to a single CacheConfiguration, but we'll have the same boilerplate code in each cache provider feature of the generator.
If the ultimate goal is to keep the generated code stupid simple, that's probably a better choice.

Not sure we'll have exactly the same thing in other cache provider. See the complex file at https://github.com/jhipster/generator-jhipster/blob/main/generators/server/templates/src/main/java/package/config/CacheConfiguration.java.ejs
Honestly, in real project, I don't see any value to have multiple cache at the same time. It would be really strange
So 2 solutions I can see here:
Keep both options and add a 3rd one:

xml
java config complete
java config single <---

I'm afraid it's too much but it's doable as JH Lite is done for that
2nd solution:

xml
replace multiple java config by a single one

Which solution do you prefer?
I can code it if you want

Not sure we'll have exactly the same thing in other cache provider. See the complex file at https://github.com/jhipster/generator-jhipster/blob/main/generators/server/templates/src/main/java/package/config/CacheConfiguration.java.ejs
Honestly, in real project, I don't see any value to have multiple cache at the same time. It would be really strange
So 2 solutions I can see here:
Keep both options and add a 3rd one:

xml
java config complete
java config single <---

I'm afraid it's too much but it's doable as JH Lite is done for that
2nd solution:

xml
replace multiple java config by a single one

Which solution do you prefer?
I can code it if you want

I kept pieces of my previous attempt with single CacheConfiguration. Will give it a try and submit a PR that you can adjust if needed.
I also think we should have only 1 java option as they have no differences in terms of functionality (the current design was mainly focused on improving the generator side).

I kept pieces of my previous attempt with single CacheConfiguration. Will give it a try and submit a PR that you can adjust if needed

So thanks a lot.
I'm working on generator-jhipster release, as:

jhipster-lite took me less than 10sec to launch the release and 3min to write the tweet
generator-jhipster will take at least 4h...


Move the project to an organization

@spacejam, @ekmartin
Thank you for putting together and open-sourcing Rust RocksDB project. We at Exonum have been using it for more than a year and are interested in its further development.
Our team is grateful to you for reviewing and integrating our patches so far, however, it seems to us the project has ceased to be your top priority recently. For this reason, I suggest moving it under a new organization “rust-rocksdb” and giving more people permission to integrate changes and publish new versions of it on crates.io. In this way the project can evolve, enlarge its community, acquire better maintenance and improve in quality.
We understand it takes efforts maintaining an open-source project and would like to offer help with that. As you may know, members of Exonum team — @DarkEld3r, @ozkriff  — have contributed various fixes and improvements to Rust RocksDB. Our team has expertise in running open-source projects in Rust, Exonum being the most prominent example.
Please consider further development of your project in a modified manner as suggested above and let us know your thoughts on the matter. You are free to contact our team members or me directly for discussion.
CC recent contributors: @kaedroho @alexreg @dgrnbrg @derekdreery

@spacejam @aleksuss Is there any progress on this?

I'd consider reaching out to the rust/crates.io team about forking the
project under an organization and changing the crates.io package.
On Fri, Sep 14, 2018 at 10:25 AM Oleksandr Anyshchenko <
<EMAIL_ADDRESS>wrote:

@Kais-DkM https://github.com/Kais-DkM Nope 😞
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spacejam/rust-rocksdb/issues/204#issuecomment-421291044,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABU-XgfJbOZpI1lSfEWfuCqsiSmsXx6tks5ua3YlgaJpZM4WNWvk
.

I'm in favor of transferring ownership of the root repo and crate to the rust-rocksdb org, which I just created. This should have been done a long time ago to avoid the fragmentation that has occurred.
This also brings up the question of whether it is possible to combine forces with some of the organizations that have forked this project and continue to invest significant resources into pushing it in the directions that they require.
@pingcap (@zhangjinpeng1987, @huachaohuang, @BusyJay, @siddontang, @hoverbear) If there is the willingness to combine efforts, now is probably the "now or never" moment to pool resources, but there are some good reasons for staying independent as well. First, as a business with code dependencies, you can't be beholden to outside control over the libraries that you rely on, but it may be advantageous to build TiKV and any other internal users on top of a "shallow fork" under pingcap control so that you can take advantage of things like windows support etc... while still having total control over the version that is depended on internally. With a proper org running rust-rocksdb, which you can be maintainers for if you are interested in collaborating, you will have way less friction to get the changes you need merged in compared to what was the case with just me running it before you stopped wanting to deal with the friction by just running your own fork, but this will be higher than the way you're running your fork independently now. So, please chip in if you think the trade-off is worthwhile at this time for pingcap to pool resources. No pressure, but I wanted to let you folks know that this is happening here and it might be an opportunity that you are interested in!
@kaedroho  @ongardie-ebay @alexreg @derekdreery you folks were previously also submitting plenty of patches before I assume you got fed up with my slow response rate :P Would you benefit from being a maintainer in this new organization?
@alexsuss Thank you for volunteering to take on maintainer responsibilities! This is going to be a great thing for the project, I think. Do you have any strong preferences for how maintainers should reach consensus, and on what consensus is required, and how contributors should be engaged?

Also @paritytech / @andresilva let me know if this is something you folks have interest in participating in!

@spacejam thanks for your response. I propose next flow for contributing:

Any change must go as a pull request.
Any PR must have at least two approvals from the team members (ideally, from people with expertise in various things).

For anything non-trivial, e.g., breaking changes, new features, I'd add:

A maintainer must leave a two working days window for other team members to be able to review the change.

Any additions are welcome. Thanks.

Just a quick response since @spacejam mentioned me: I haven't been contributing lately simply because I've been stuck over in Go-land. Of course, it'd be great to see this project actively maintained.

@spacejam
In TiKV, we have changed a lot from the origin repo, and I think it is not suitable to contribute our change now.
But we are very happy to offer help if possible.

@kaedroho @ongardie-ebay @alexreg @derekdreery you folks were previously also submitting plenty of patches before I assume you got fed up with my slow response rate :P Would you benefit from being a maintainer in this new organization?

Had no problems with your response rate :). Just haven't worked on rusticsearch in a while. I'd be happy to help out with maintaining this though!

Any PR must have at least two approvals from the team members (ideally, from people with expertise in various things).

Given that nobody is actually paid to review PRs for this project, getting just one approval will take time in most cases (see current PR list). And I think for most changes one approval is enough, but I agree that for non-trival stuff (such as major API changes and internal refactoring) should be given a chance to gather more feedback. I don't think 2 days is enough for this though, two weeks sounds more realistic to me (people go on holidays, work trips, etc).

I agree with @kaedroho that 2 days is a very short turnaround time. I think there are some times when a week would also be hard to find time for a really major review, and 2 weeks is probably more realistic given people may be on vacation or simply having a busy week. Personally, I'm an excruciatingly slow reader of code, and I can easily spend an hour re-learning the parts of the codebase that a small PR touches.
So, I propose 2 weeks as the "well, I tried to involve others, but there was no response, so I moved forward" timeout for feedback generation on a major change.
"Major change" is going to be a bit subjective. I'll trust maintainers to use their judgment to involve others early when something beyond small / routine changes happens.
Small / routine changes that can move fast, and I don't feel like I need to be involved in, but should ideally still have 2 approvals:

updating librocksdb-sys
tracking API changes without changing control flow in existing code

Historically, this repo has been a battleground for people with different refactoring ideas to more or less run wild. People have started to use the language in a more uniform way since 2014, and we can probably be more cautious about this now. My philosophy before was to just let people tidy things up in a way that will make them feel more at home, to encourage continued contribution. I think now we should be a little more cautious about refactoring for refactoring's sake, and it should probably come with some justification.
I'm going to add the contributor covenant as our code of conduct. Everything I've said is up for debate except for having one.
So, soon-to-be-maintainers (anyone who has been @-mentioned on this thread, although this will be opt-in, so if you disagree with the code of conduct you can just pretend to be afk :P), what are your opinions about:

normal changes require 2 approvals
2 week timeout on feedback for major changes, after which there is no need to get more than 2 approvals for merging
defining small changes that do not require more than 2 approvals as
a. a librocksdb-sys update
b. API tracking code in the rocksdb crate that does not change control flow
encouraging refactoring to happen for clearly functional reasons, like improving ability to reason about correctness or to ease a feature's implementation
major changes require consensus among participants. If something needs to happen, and there are disagreements about what should happen, I can act as a tiebreaker if requested but I prefer not to use this ever.

As we draw near to the 2 week mark for the above comment, I'd like to invite more feedback on the proposed process, although I think at this point it's fine to start acting on it. I've sent @aleksuss an invite to this org, and I've created a team with permission to publish to crates.io: crate-publishers
If anyone else would like to opt-into maintainership responsibilities, please either leave a message here so I can see it, or feel free to send me an email at<EMAIL_ADDRESS>

@iSynaptic yeah! I'll create a proposal PR now that formalizes this


Can't get only one item with onItemClick

Hello.
I want to add a listner for each item inside my row. The problem is that, getItemPostion returns an array of the items that are in the row, so it's impossible for me to know, what item was really selected.
How can i solve this problem ?
Thanks

Thanks! this code save some day of code!!!


37- Controller, service and router created

I created the following files for venue:
Controller: getAllVenues and getOneVenueById
Service: getAllVenues and getVenueById
Route: venueRouter
All Venues:
Image
Venue by Id:
Image

TODO find type for this function
export async function getVenueById(venueId: string) {
    return prisma.venue.findUnique({
        where:{
            id: venueId
        }})

}


Invalid file:/data/data/com.s3samples/files

hai, when i try to run your example in react-native-s3, i got an error as shown in the below image,could you please tell me that how to overcome it,
-npm install

to run in android: react-native run-android
After that in emulator when click on  New Upload i got an error like below

please tell me that how to resolve it

Because the example is not write the filename, currently you must add it yourself.
I'll providing a example file, and a guide of setting. :)

@jhen0409 Thank you for your response, I am waiting for the example file please provide as soon as possible

@jhen0409 thanks for your response, can you please provide the working example it would helpful for me

Sorry for delay, just added example file download in https://github.com/mybigday/react-native-s3/commit/8aa52d6e4537b86c55346a2706b149c6d9221f91.


Zstd release 1.5.5

Hi, @luben
we would like to release Apache Cassandra 4.0.9 but we just stumbled upon 1.5.5 release of Facebook which fixes some data corruption bugs literally few hours ago.
I want to ask: when do you plan to release 1.5.5 of this library so we can incorporate it in the project? We would love to do so!
Thanks

The plan is to release it tomorrow or during the weekend

Sure.

@smiklosovic , I am releasing it now. It should be on Maven central in an hour or so.

Done


Web (Windows): workspace.test.ts: eol, change on willSave fails

Only on Windows I see this test failing and as such have pushed a skip() for just that:
  1) workspace-namespace eol, change via onWillSave:

      AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: The expression evaluated to a falsy value:

  assert.ok(called)

      + expected - actual

      -false
      +true

      at extensions\vscode-api-tests\src\singlefolder-tests\workspace.test.ts:242:13
      at processTicksAndRejections (internal/process/task_queues.js:89:5)

Actually seeing this on Linux too, I have pushed a change to disable it when running from web.

@bpasero add you for debugging help. This test work on playwright+macOS, in electron, and also when running from within web-selfhost. I see them failing on playwright+windows but the debugging is so limited that I don't know how to drill into it

@jrieken maybe with this sloMo option you could artificially slow down the test run to get a hold of the dev tools within? But I guess simple timeouts in the test would also help already.

Turns out that this is a race between the web worker extension host and the remote one and the text exposes it.


CM autoclose tag behavior with 'whenClosing' on typing '/'

When autoclose tag is configured with 'whenClosing', if user opens an existing html file which contains some invalid tags and try to close them, cm inserts closing tags with '>' which introduces new syntax errors in the html. The screen capture below depicts the error scenario -

IMO, the logical behavior could be not to insert any close tag, as the '/' typed itself closed the open tag in the context.

Do you want to implement the behavior you describe?

@marijnh Thanks for the quick response :+1:
If you think it's a valid behavior what I have proposed, then yes, I will try to implement the new behavior and raise a PR.

Yes, it sounds valid (when the inserted content exactly matches the text after the cursor -- when not, I think it should just do the dumb thing it does now)


BytePairEncodingCore.d.ts: 'TextDecoder' refers to a value, but is being used as a type here. Did you mean 'typeof TextDecoder'?

I get an error in line 7 in the file BytePairEncodingCore.d.ts:
export declare const decoder: TextDecoder;

Should this be changed to?
export declare const decoder: typeof TextDecoder;

hi Michael, what's your stack? how are you using gpt-tokenizer? the d.ts files are autogenerated by TS during build time and are correct.


4bits微调问题

ValueError: The model you want to train is loaded in 8-bit precision.  if you want to fine-tune an 8-bit model, please make sure that you have installed bitsandbytes>=0.37.0.
我已经pip install bitsandbytes==0.41.1

上述提示不对，误导。
4bits不能微调，用7B-Chat可以。

搞了一上午，然后不能微调，服气（-_-）


verbose option for --wait

Can there be a verbose option for the new --wait option, so the user can see what is happening during longer deployments?
Perhaps a new --status_updates option that behaved like this:
helm upgrade my-test nginx-my-0.1.1.tgz --wait --status_updates

21:23:21 NAME      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
21:23:21 my-test   15        18        6            12          52d
21:23:33 my-test   15        18        6            12          52d
21:23:46 my-test   15        18        6            12          52d
21:23:59 my-test   15        18        6            12          52d
21:24:11 my-test   15        18        6            12          52d
21:24:23 my-test   15        18        12           12          52d
21:24:36 my-test   15        18        12           12          52d
21:24:49 my-test   15        18        12           12          52d
21:25:02 my-test   15        18        12           12          52d
21:25:14 my-test   15        18        12           12          52d
21:25:27 my-test   15        15        15           12          52d
21:25:40 my-test   15        15        15           12          52d
21:25:53 my-test   15        15        15           12          52d
21:26:06 my-test   15        15        15           12          52d
21:26:19 my-test   15        15        15           12          52d
21:26:31 my-test   15        15        15           15          52d

I could see this being bubbled up with --debug enabled, if this was possible.

Yes, bubbling up with the --debug option would be great!  It would certainly meet our use case.

I believe #2063 is also trying to achieve a similar goal and would probably reuse a lot of logic

closing due to inactivity.


uncomment deleteCanvasObject on Keydown

I don't know if you forgot to remove the comment or left it like that on purpose, but I need that shortcut.

Yeah, I think I forgot to remove it. Thanks for the PR! 👍


after-flaw-update tracker update

This PR introduces the after-flaw-update actions as some flaw updates might result in a necessity to update some related tracker(s). There are also some extra pieces in this PR.

On is the restructuring of the endpoint tests. The file was already too big and when I wanted to add a test cases related to this PR I had a hard time figuring out in which place there to put it. I decided to put it to no place there and instead first create a more suitable place elsewhere. To do it meaningfully it required the restructuring.
I had to fix non-atomicity test as it was only failing before. I first though that there is some kind of race condition in the package version test (and maybe was but rather in between different tests) as I already saw that error in the past and it always disappeared after rerun. This time it did not disappear so the fix was the only option.

The issue OSIDB-97 will have another part of after-affect-update tracker updates which is however independent of this one so this one is ready for a review.


Runing ls -l /usr/loca/bin/code-exploration shows that this is syminked to something like /private/var/folders/73/gbzw9z1d17nc9xp7sk5jw64h0000gn/T/AppTranslocation/8218EF9A-F559-487D-8618-E73F3D5D3B68/d/Visual Studio Code - Exploration.app/Contents/Resources/app/bin/code which no longer exists instead of the actual installation directory e.g. /Users/krupagj/Applications/Visual Studio Code - Exploration.app/Contents/Resources/app/bin/code
Presumably this is because the app isn't signed and is flagged for quarantine.

Does this issue occur when all extensions are disabled?: Yes

Can you update to latest exploration build and check if this is still an issue ? I am unable to repro on my machine.

Tested on 1.52.0-exploration Commit: 25a4ee40993f43df9229edc552bd3018c086569d
I didn't get the issue on this build

Closing for now, can reopen if there is a consistent repro. Thanks for testing!


Refactor cache store internals (day 2)

Results of the next refactoring steps, where I ended on day 2. The code is best reviewed commit-by-commit.
This PR introduces a .batch() method on the abstract Store class (a new sibling to .get(), .set(), and .subscribe()). This allows us to perform multiple successive .set() calls on the store without triggering multiple notifications to subscribers. Separating .set() calls from notifying allows us to better split and reuse individual cache mutations and enables more DRYing up of code.
More tomorrow, where I'll be focusing on moving the UmbrellaCache into @liveblocks/react (out of @liveblocks/core).
One behavioral change: Please note that the only behavioral change introduces here is in this commit (which we discussed here).

Early abstractions are not a great idea.

Exactly! I talked about this a bit with Guillaume a couple of times, and all frontend frameworks have their own strong opinions on how to do state mutations. React, Vue, Svelte, Solid, etc all take a very different stance on it. While it may be true that we would need to duplicate the optimistic update knowledge if we wanted to make a Vue package, for now, we're moving these abstractions out of core, so they don't get shipped to those that don't use/need React.
But if it turns out that later it may be beneficial to move this back into core, that's still an open road AFAIAC. It's just that if that happens, we'll make a more informed decision about it, and until then it's easier to move this code into the React package.