Pre-built Binary for CUDA 11.1

Description
CUDA 11.1 is now available and mxnet should provide pre-built binary for it.

CUDA 11.2 is now available and mxnet should provide pre-built binary for it.
It seems that CUDA 11.2 is faster than CUDA 11.1, at least on my RTX 3090.

CUDA 11.2 is now available and mxnet should provide pre-built binary for it.
It seems that CUDA 11.2 is faster than CUDA 11.1, at least on my RTX 3090.

Pytorch said they are going to skip CUDA 11.1 because of bug and realse a CUDA 11.2 version.

Pytorch said they are going to skip CUDA 11.1 because of bug and realse a CUDA 11.2 version.

@Neutron3529 The latest cudnn cannot support CUDA 11.2, how did you do that?

@Neutron3529 The latest cudnn cannot support CUDA 11.2, how did you do that?

@Neutron3529 The latest cudnn cannot support CUDA 11.2, how did you do that?

I currently using Manjaro system, and find there are no difference between cuda 11.1+cudnn<IP_ADDRESS> and cuda 11.2+cudnn<IP_ADDRESS>(maybe 11.1)
All the trainings are fine and running at full speed.

@Neutron3529 The latest cudnn cannot support CUDA 11.2, how did you do that?

I currently using Manjaro system, and find there are no difference between cuda 11.1+cudnn<IP_ADDRESS> and cuda 11.2+cudnn<IP_ADDRESS>(maybe 11.1)
All the trainings are fine and running at full speed.

CUDA 11.2 support in #19764, currently pending new release for cudnn, details are in the PR.

CUDA 11.2 support in #19764, currently pending new release for cudnn, details are in the PR.


Secret Chat Id

So after creating a secret chat, in getChats I loop through the Id's returned by getChats and filter the secretChat using ChatTypeSecret.
Thing is the returned chat is just a normal chat with a normal ID.
The Id is good enough to send messages to the secret chat but is still not the true secret_chat_id.
How do you obtain secret_chat_id from the chat object returned from getChats.
Thanks!

ChatTypeSecret contains secret_chat_id field.

Thanks Levlam

Also i see all objects have a "Extra" string variable, can I use that to carry secret_chat_id in the chat object?

No. See https://core.telegram.org/tdlib/getting-started#tdlib-interface for description of the @extra field.

So on update of Update.UpdateSecretChat it passes the secretchat, how would i find the corresponding tdapi.chat Id to clear it in DeleteChatHistory since it will not except secretchat id

You can save correspondence chat.id <-> secret_chat_id.

ok so save it locally? otherwise there it no way of correlating the two.

Save in memory.

Or better use createSecretChat to get the chat by secret_chat_id.

thanks


When extending from centos7-s2i-nodejs the env var NPM_RUN still with the same value on centos7-s2i-webapp. This is causing an error with make test.

The test script will use the env var on this line :
https://github.com/bucharest-gold/centos7-s2i-web-app/blob/master/s2i/run#L11
And shows error command not found.
NPM_RUN: https://github.com/bucharest-gold/centos7-s2i-nodejs/blob/master/Dockerfile#L13
We need to fix this to be able to move forward with the #15

Maybe override to empty string will fix NPM_RUN= \ , I don't tested yet.

I think i originally used "NPM_RUN_COMMAND" which didn't have the issue,  but i think setting "NPM_RUN" to nothing like you suggested should take care of that

yea, but now I think "NPM_RUN_COMMAND" seems better than an empty var :smile:

landed in #19


Bumping to 0.0.22 for release

Current coverage is 66.84% (diff: 100%)

Merging #139 into master will not change coverage

@@             master       #139   diff @@
==========================================
  Files            52         52
  Lines          2051       2051
  Methods           0          0
  Messages          0          0
  Branches        288        288
==========================================
  Hits           1371       1371
  Misses          603        603
  Partials         77         77

Powered by Codecov. Last update 3f38463...836bdfa

LGTM


add a better error message when incorrectly using the default slot

Add a better error message as Dave reporting on this issue here: https://github.com/surface-ui/surface/issues/620

@herminiotorres thank you! ❤


switch-to-configuration-ng: add devshell

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-vet is wrong here:

pkgs/by-name/sw/switch-to-configuration-ng: File shell.nix at line 2 contains the path expression "../../../.." which may point outside the directory of that package.

This is not true.

Reported ci error here: https://github.com/NixOS/nixpkgs-vet/issues/113


Label node on worker creation

Hi,
I want to label all new nodes from an AWS autoscaling group.
I can achieve this manually with kubectl label node.... But I want to do this automatically when a new node is deployed.
How can I label a new node when it starts? There is some script to add in user-data?

There is a --node-labels flag on the kubelet you can use. This will set the labels on a node on first registration. For example --node-labels=foo=bar,baz=bat.
You would need to add this flag to the kubelet service file which is rendered into userdata/cloud-config-worker (template: https://github.com/coreos/coreos-kubernetes/blob/master/multi-node/aws/pkg/config/templates/cloud-config-worker#L29)

thanks @aaronlevy


Richard Gama - missing region, skills, qualifications, at least one contact option

https://lead.asknet.community/profiles/22-Richard-Gama/

[ ] Update/name Region
[ ] Update Skills & Qualifications
[ ] Provide a public contact info if possible or name another contact/expert

I've send him a message

wrote him a message maybe you can follow up @romeoplat

the profile is not up to date, I'll take it down for now
Gama
Please follow up with him and open a new profile issue for him @ASKnetCommunity/coordinators

@dutandrewkulang please be careful to mark a checklist when not reflected on the website or you personally made sure everything is up to date/verified

Ok


Added two tests and removed force-unwrapping in test cases

Added two tests that I have had students trip up on. Single nucleotide strands, and strands that contain both valid and invalid nucleotides (current validation test was only with all invalid characters).
More importantly, I modified the tests to remove force unwrapping and to use XCTUnwrap instead. We would encourage our students to not use force unwrapping in their code, and we shouldn't use it in ours.

Didn't realize that XCTUnwrap wasn't available on the system -- apparently it's Xcode only at the moment. Will rewrite with what is available.


too many open streams

Describe the bug
i got too many open streams then connection dropped
*To Reproduce
I shared my server with 50 persons
Expected behavior
after this error server to connections
Logs
SOCKS5 TCP error        {"addr": "<IP_ADDRESS>:60102", "reqAddr": "<IP_ADDRESS>:6072", "error": "too many open streams"}
Device and Operating System
Ubuntu 20
Additional context
Add any other context about the problem here.

Try increasing maxIncomingStreams:
https://hysteria.network/docs/advanced/Full-Server-Config/#quic-parameters:~:text=maxIdleTimeout%3A 30s-,maxIncomingStreams,-%3A 1024

I have the same problem. I have increased it to 1000000 still getting this error


button.js: Convert to vanilla JS (incomplete)

it seems your tests failed because phantomsJS don't know closest function and the polyfill is in my PR, before finishing this PR we should finish the Alert plugin and the Button plugin will be finish quickly after that 👍

v4-without-jquery is up to date with v4-dev so you can rebase 👍

Can you update our button visual test ?


Can't move an email

Hi,
I can't move any email, and getting the following error message:
ReferenceError FASTMAIL is not defined ReferenceError: FASTMAIL is not defined

Fixed.

@neilj
thanks for the fix, however you can move an email from the trash to somewhere is, which is a little confusing to the user, hope you can make a fix for that


Custom hitsound made me unable to enter Official Matchmaking.

The instructions were clear, "Put sound on csgo/sound/". So, I put a .wav file inside "sound" folder, I tried it on Aimbotz or any other custom maps, it worked. But, as soon as I tried to enter Official Matchmaking, it said something about me modifying the game files and prevents me from playing Competitive Mode. Help, please?

verify integrity of game files from inside steam. sounds shouldn't be protected like materials are.


Can you please guide me about how can I run this source code on windows 10?

Hey!
imresize is deprecated in SciPy 1.0.0, and will be removed in 1.3.0 can you please tell an alternative for:
if imscale!=imsize:
image_np = scipy.misc.imresize(image_np, size=(imsize, imsize), interp='bilinear')
annotation = scipy.misc.imresize(annotation, size=(imsize, imsize), interp='bilinear')
in process_record.py. Thank you!

Thank you for pointing out the issue! The code has been updated to use the PIL library for image operations. Please refer to commit 98aca05a8a4993fbba64797c8e438feeafbcba4d.
Hope this works for you


Mark labels

I've been browsing through these issues, and there's a lot of duplicates, enhancements, and outdated/invalid issues. It would really help a lot of people to apply those three labels. If anybody who can wants to help, I think a lot of people would like it.

Can somebody please mark this as a enhancement?

Some groups of issues that are duplicates are installation issues and Office-format related issues, just to give you a head start, @cdmayer @D4N14L and @wiktorn.

Thank you for reaching out and for your patience. This SDK is being officially deprecated. See #209 for more information


Startup error

I've been following this from launch week and have been able to learn little bits of coding to configure/troubleshoot this bot but now am stumped. I have googled and searched the issue thread but can't find this one.
I am trying to reinstall latest version (commit 563f898) from scratch to keep everything tidy. When I attempt to run with ./run.sh configs/config.json I get this error message. I can't see where i am going wrong.
2016-08-08 13:31:14,931 [       cli] [INFO] PokemonGO Bot v1.0
Traceback (most recent call last):
File "pokecli.py", line 503, in
main()
File "pokecli.py", line 62, in main
config = init_config()
File "pokecli.py", line 170, in init_config
load.update(json.load(data))
File "C:\Python27\lib\json_init_.py", line 291, in load
**kw)
File "C:\Python27\lib\json_init_.py", line 339, in loads
return _default_decoder.decode(s)
File "C:\Python27\lib\json\decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Python27\lib\json\decoder.py", line 380, in raw_decode
obj, end = self.scan_once(s, idx)
ValueError: Invalid \escape: line 7 column 31 (char 247)
OS: WIN10
Git Commit: 563f898f61233ff86d38d83b68d8399c1f63051b
Python Version: 2.7

What does your Config.json look like?

{
"auth_service": "google",
"username": "",
"password": "",
"location": "location",
"gmapkey": "A***************",
"libencrypt_location": "C:\Users\user\Downloads\PokemonGo-Map-develop\pogom",
"tasks": [
{
"type": "HandleSoftBan"
},
{
"type": "CollectLevelUpReward"
},
{
"type": "IncubateEggs",
"config": {
"longer_eggs_first": true
}
},
{
"type": "TransferPokemon"
},
{
"type": "EvolvePokemon",
"config": {
"evolve_all": "none",
"first_evolve_by": "cp",
"evolve_above_cp": 500,
"evolve_above_iv": 0.8,
"logic": "or",
"evolve_speed": 20,
"use_lucky_egg": false
}
},
{
"type": "RecycleItems",
"config": {
"item_filter": {
"Pokeball":       { "keep" : 40 },
"Greatball":      { "keep" : 40 },
"Ultraball":      { "keep" : 70 },
"Potion":         { "keep" : 15 },
"Super Potion":   { "keep" : 40 },
"Hyper Potion":   { "keep" : 50 },
"Revive":         { "keep" : 65 },
"Razz Berry":     { "keep" : 20 }
}
}
},
{
"type": "CatchVisiblePokemon"
},
{
"type": "CatchLuredPokemon"
},
{
"type": "SpinFort"
},
{
"type": "MoveToFort",
"config": {
"lure_attraction": true,
"lure_max_distance": 2000
}
},
{
"type": "FollowSpiral",
"config": {
"diameter": 4,
"step_size": 70
}
}
],
"map_object_cache_time": 5,
"forts": {
"avoid_circles": true,
"max_circle_size": 50
},
"websocket_server": false,
"walk": 6,
"action_wait_min": 1,
"action_wait_max": 4,
"debug": false,
"test": false,
"health_record": true,
"location_cache": true,
"distance_unit": "km",
"reconnecting_timeout": 15,
"evolve_captured": "NONE",
"catch_randomize_reticle_factor": 1.0,
"catch_randomize_spin_factor": 1.0,
"catch": {
"any": {"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or"},
"// Example of always catching Rattata:": {},
"Pikachu": { "always_catch" : true }
},
"release": {
"any": {"keep_best_cp": 3, "keep_best_iv": 3, "release_below_cp": 500, "release_below_iv": 0.9, "logic": "or"},
"// Example of always releasing Rattata:": {},
"// Rattata": {"always_release": true},
"// Example of keeping 3 stronger (based on CP) Pidgey:": {},
"// Pidgey": {"keep_best_cp": 3},
"// Example of keeping 2 stronger (based on IV) Zubat:": {},
"// Zubat": {"keep_best_iv": 2},
"// Also, it is working with any": {},
"// any": {"keep_best_iv": 3},
"// Example of keeping the 2 strongest (based on CP) and 3 best (based on IV) Zubat:": {},
"// Zubat": {"keep_best_cp": 2, "keep_best_iv": 3}
},
"vips" : {
"Any pokemon put here directly force to use Berry & Best Ball to capture, to secure the capture rate!": {},
"any": {"catch_above_cp": 1200, "catch_above_iv": 0.9, "logic": "or" },
"Lapras": {},
"Moltres": {},
"Zapdos": {},
"Articuno": {},
    "// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
    "Mewtwo": {},
    "Dragonite": {},
    "Snorlax": {},
    "// Mew evolves to Mewtwo": {},
    "Mew": {},
    "Arcanine": {},
    "Vaporeon": {},
    "Gyarados": {},
    "Exeggutor": {},
    "Muk": {},
    "Weezing": {},
    "Flareon": {}

}

}

As there have been many updates since this issue was posted, I'm assuming this issue has been resolved. If I'm wrong, please reopen.


Utility: disable Signal on Windows

Windows does not support the concept of signals and has no equivalent to it.  Simply disable the interface to ensure that we do not accidentally rely on it somewhere.

@swift-ci please test


Labeling issues with Engagement Area template

Encountered a couple of labeling issues while building Engagement Area Pro 1.0 template.

Control Measures Target Points not being labeled with Target Designator field

For Battle Position features, Unique Designation field has labeling on, but label appears near edge, not centered (the standard shows the T (Unique Designation) in the center).

Issue #66 Echelon Indicators... noted by @csmoore
Data Here: https://esri.app.box.com/files/0/f/3538111917/1/f_30056997353

Closing as a repeat/duplicate of #142 (that now target label shows up but is erroneous hardcoded "AP")


Support Anthropic Claude 3

Looking for PR to add support for Claude 3, released today by Anthropic.

This pr does not seem to work for me. Error message stating it requires the new messages api.

Ah there was an API change as well?

It seems like it, other claude models work, just not Claude 3

https://docs.anthropic.com/claude/docs/models-overview#model-comparison
All Claude 3 models only support the Messages API and I think currently only the completions API is implemented for Claude here?

Correct @Penagwin - they just introduced the new Messages API and the -3 models are the ones to only support that new API. We'll need to update the backend code.

Is this the backend code for claude: https://github.com/enricoros/big-AGI/blob/main/src/modules/llms/server/anthropic/anthropic.router.ts
Might be interested in taking a crack at this

Hey everyone! 👋
I've taken a crack at adding support for Anthropic Claude 3 models, as mentioned by @enricoros and @Penagwin. The changes primarily focus on updating the backend code in anthropic.router.ts to use the new Anthropic Messages API.
Here's a quick rundown of what I've done:
🔧 Updated the backend code to use the new Messages API, as required by Claude 3 models.
🆕 Implemented support for Claude 3 models, so users can now leverage these powerful new tools.
📝 Updated the documentation and comments to reflect the changes and provide clarity on usage.
🧪 Added tests to ensure the Claude 3 functionality works as expected and to maintain code quality.
I've submitted a pull request with all the details, and I'm excited to hear your thoughts and feedback! Let's work together to get this merged and provide our users with access to the latest and greatest from Anthropic.
Thanks for your time, and let me know if you have any questions or suggestions! 😄
/p

Thanks @slapglif - looking into it. Seems like there's no Streaming support; looking into that.

@enricoros
no problem, been using this software since the day i hit you up, least i can do - i replied to the pr:

@enricoros as to the fidelity of the fix, upon further inspection, i receive some cases with:
 ○ Compiling /api/trpc-node/[trpc] ...
 ✓ Compiled /api/trpc-node/[trpc] in 1037ms (700 modules)
Error in stream: [SyntaxError: Expected ',' or '}' after property value in JSON at position 39]

this is likley a parsing error, ill see to it shortly, as for the lack of streaming support - the current situation is that streaming is supported and streams to console, but i wanted to push a working version before attacking the streaming to next bug,
to address the formatting - sorry yeah python guy, can you define your standard for me so i can use an llm to reformat?


Bugfix in UsingBareVariablesIsDeprecatedRule for variable with default empty dictionary

Fixes https://github.com/willthames/ansible-lint/issues/190
What?
Changes BareVariablesIsDeprecatedRule to check for bare variables the same way Ansible 2 does it, by checking for  {% or {{.
Why?
BareVariablesIsDeprecatedRule raises an error when a task has with_items with a default empty dictionary:
- name: configure
  ini_file:
    option: "{{ item.key }}"
    value: "{{ item.value }}"
  with_dict: "{{ ini_options | default({}) }}"

I propose splitting this commit into two - one for the tests, one for the change. I'll merge your tests but I'll implement my fix.

v3.3.0rc4 now contains the contents of #192 which implements my proposed alternative fix.
If you're able to test, please do

Fixed in 3.3.0


CLOUD-55041 Reusable flow actions, cleanup services

@mhmxs plz check

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2337/


Fix missing peer dependencies warnings

Fixes yarn complaining, and uses the new rules.
So far this has only seemed to be a problem while ejected though.

Hi @RDIL. Thanks for the PR, but it is a dupe of #7790, which will be merged shortly.


Migrate to Kotlin Multiplatform

Migrate the library from android-only to Kotlin multiplatform in order to target Android, JVM, iOS and Web

Thanks @jeffnyauke can you provide some additional information to this issue

Thanks @jeffnyauke can you provide some additional information to this issue

Updated 🙂

Closing in favour of #1497. Please continue discussions there.


tsrc push: rude message when credentials are missing

Command you ran
$ tsrc push

Actual output
=> Running git push
Branch feat/gcp set up to track remote branch feat/gcp from origin.
Everything up-to-date
Traceback (most recent call last):
  File "/home/ctaf/.local/bin/tsrc", line 11, in <module>
    load_entry_point('tbuild', 'console_scripts', 'tsrc')()
  File "/home/ctaf/src/tanker/tbuild/tcommon/cli.py", line 17, in wrapped
    main_func(args=args)
  File "/home/ctaf/src/tanker/tbuild/tsrc/cli/main.py", line 104, in main
    return module.main(args)
  File "/home/ctaf/src/tanker/tbuild/tsrc/cli/push.py", line 138, in main
    handle_merge_request(args, repo_path, current_branch)
  File "/home/ctaf/src/tanker/tbuild/tsrc/cli/push.py", line 96, in handle_merge_request
    project_id = tcommon.gitlab.get_project_id(project_name)
  File "/home/ctaf/src/tanker/tbuild/tcommon/gitlab.py", line 75, in get_project_id
    res = make_request("GET", "/projects/%s" % encoded_project_name)
  File "/home/ctaf/src/tanker/tbuild/tcommon/gitlab.py", line 61, in make_request
    token = get_token()
  File "/home/ctaf/src/tanker/tbuild/tcommon/gitlab.py", line 25, in get_token
    netrc_parser = netrc.netrc()
  File "/usr/lib/python3.6/netrc.py", line 32, in __init__
    with open(file) as fp:
FileNotFoundError: [Errno 2] No such file or directory: '/home/ctaf/.netrc'

Expected result
A message explaining what's wrong and linking me to the documentation.

Thanks for the bug report !
I'm already working on a PR to improve error management: #18
I believe we can find a clean way to deal with missing or invalid config files too.


Complted buckets JSON converter

Fixes #7713.

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Thank you for getting here, @technige, but could you turn the pipelines on so these ad other changes can be tested before an Elastic member comes here?

@technige Any ideas, when are you will able to merge it or create alfa version? Without aggregations we could not completely migrate from Nest and use a library in e-commerce platform.

@OlegoO, the problem here as I understand that Elastic has no .NET developers at the moment and no one is maintaining that repository. So, I would suggest you making a fork with that fix and publish the resulting package on your own NuGet server or git submodule it and reference as a project.

Hi @YohDeadfall, thanks for your contribution(s)! I'm the new maintainer for this repository and I'm currently familiarizing myself with the code base and trying to catch up with the existing issues/PRs.
I can't give you an exact ETA, but I'm hoping to be able to check this PR until next week. Just wanted to let you know, that I'm actively working on it.

Awesome! Since all my contributions are serialization related that should not be hard to review them. Feel free to reach me out on any question about my contributions here or the JSON serializer in general in which creation I participated in.

Now you need to allow pipelines to run, @flobernd (:


Code Jam Channels Automatic Creation

Code Jam preparation is in full swing. To reduce the burden on our organizing team, I'd like a command that will automate almost all of the team channels and role creation. Please ping me here or in server if there are any questions about this implementation. This is fairly high priority as I would like it working by June 14th.
The Proposal
A single command !codejam create <csvfile or link to a csv file> that will create the channels and roles needed for the code jam.
The csv will be structured like so:

Team Name
Team Member Discord ID
Team Leader

Annoyed Alligators
165023948638126080
Y

Annoyed Alligators
306870406697189378
N

Oscillating Otters
95872159741644800
Y

Oscillating Otters
172395097705414656
N

Oscillating Otters
212644551926611969
N

Given this csv file the following actions should be completed:

A code jam category called Code Jam should be created. All the below channels will be in this category.
Team roles for each provided team name should be created
People associated with the team name should be assigned the correct team role
Team text channels should be created with overrides for viewing + sending messages for the associated team role
A single Code Jam Team Leader role should be created
A single Team Leader Chat should be created with a role override for viewing + sending messages for the team leader role
People who are designated as team leaders should have the team leader role applied
Code Jam Events Team role and Moderation Team role should have viewing + sending messages for all the newly created channels

Other Considerations

It would be nice if it could ping the Events Lead role with a status update as this command is running and hits certain milestones
No voice channels will be created
You can assume the csv file we pass in is correct. If someone is assigned to two teams or there are two team leaders that's not something this code should worry about.

cc: @ChrisLovering please assist where you can in terms of implementation details and the like~

Should this command be limited to mods, admins (or just you)?


Display expiration time on payment details dialog for pending payments

Depends on:

https://github.com/breez/breez-sdk-liquid/issues/415

This seems related to the UI part in misty breez.

This seems related to the UI part in misty breez.

True, this issue was opened here by mistake.
Creating it on misty-breez repository.


Generator test segfault on linux py3.11

test_gen9 or test_gen9_objmode in numba.tests.test_generators are either segfaulting or hanging and causing the multiproc testsuite to timeout. Problem only occur on Linux and py3.11. Problem has occurred on x64, ppc64le, and aarch64.
Issue first occurred with the commit 201a2f8, merge of https://github.com/numba/numba/pull/8134.
The issue is hard to reproduce. Only consistent reproduction is in the buildfarm and with the buildfarm created package.
Scripts to reproduce:
$ conda create -y -q -n testenv_f8901e13 -c numba/label/pynext_ci -c numba/label/pynext_dev -c conda-forge python=3.11 numba=0.57.0dev0=np1.23py3.11h3611171_g201a2f8d6_1571 numpy=1.24 pyyaml colorama scipy jinja2 cffi ipython flake8
$ conda activate testenv_f8901e13
$ NUMBA_ENABLE_CUDASIM python -m numba.runtests -m 4 -v numba.tests

conda-forge channel is not necessary. Problem has occurred on py3.11 + np1.23 from conda defaults.

Assuming the last line is a typo and should be:
$ NUMBA_ENABLE_CUDASIM=1 python -m numba.runtests -m 4 -v numba.tests

(the =1 was missing)

The hang has reproduced for me on the first attempt at running.

generator_dealloc() was calling 0x7f3e588fb080 which was in $rax at 0x7f3e1588f281:
│    0x7f3e1588f250 <generator_dealloc>      push   %rbx                                               │
│    0x7f3e1588f251 <generator_dealloc+1>    mov    %rdi,%rbx                                          │
│    0x7f3e1588f254 <generator_dealloc+4>    call   *0x2d9e(%rip)        # 0x7f3e15891ff8              │
│    0x7f3e1588f25a <generator_dealloc+10>   cmpq   $0x0,0x30(%rbx)                                    │
│    0x7f3e1588f25f <generator_dealloc+15>   je     0x7f3e1588f26a <generator_dealloc+26>              │
│    0x7f3e1588f261 <generator_dealloc+17>   mov    %rbx,%rdi                                          │
│    0x7f3e1588f264 <generator_dealloc+20>   call   *0x2c8e(%rip)        # 0x7f3e15891ef8              │
│    0x7f3e1588f26a <generator_dealloc+26>   call   *0x2d10(%rip)        # 0x7f3e15891f80              │
│    0x7f3e1588f270 <generator_dealloc+32>   test   %eax,%eax                                          │
│    0x7f3e1588f272 <generator_dealloc+34>   jne    0x7f3e1588f283 <generator_dealloc+51>              │
│    0x7f3e1588f274 <generator_dealloc+36>   mov    0x28(%rbx),%rax                                    │
│    0x7f3e1588f278 <generator_dealloc+40>   test   %rax,%rax                                          │
│    0x7f3e1588f27b <generator_dealloc+43>   je     0x7f3e1588f283 <generator_dealloc+51>              │
│    0x7f3e1588f27d <generator_dealloc+45>   lea    0x38(%rbx),%rdi                                    │
│    0x7f3e1588f281 <generator_dealloc+49>   call   *%rax                                              │
│  > 0x7f3e1588f283 <generator_dealloc+51>   mov    0x18(%rbx),%rdi                                    │
│    0x7f3e1588f287 <generator_dealloc+55>   test   %rdi,%rdi                                          │
│    0x7f3e1588f28a <generator_dealloc+58>   je     0x7f3e1588f292 <generator_dealloc+66>              │
│    0x7f3e1588f28c <generator_dealloc+60>   subq   $0x1,(%rdi)                                        │
│    0x7f3e1588f290 <generator_dealloc+64>   je     0x7f3e1588f2a8 <generator_dealloc+88>              │
│    0x7f3e1588f292 <generator_dealloc+66>   mov    0x8(%rbx),%rax                                     │
│    0x7f3e1588f296 <generator_dealloc+70>   mov    %rbx,%rdi                                          │
│    0x7f3e1588f299 <generator_dealloc+73>   pop    %rbx                                               │
│    0x7f3e1588f29a <generator_dealloc+74>   mov    0x140(%rax),%rax                                   │
│    0x7f3e1588f2a1 <generator_dealloc+81>   jmp    *%rax                                              │
│    0x7f3e1588f2a3 <generator_dealloc+83>   nopl   0x0(%rax,%rax,1)                                   │
│    0x7f3e1588f2a8 <generator_dealloc+88>   call   *0x2c62(%rip)        # 0x7f3e15891f10              │
│    0x7f3e1588f2ae <generator_dealloc+94>   jmp    0x7f3e1588f292 <generator_dealloc+66>              │

(gdb) p/x $rax
$5 = 0x7f3e588fb080

Comparing with the source of generator_dealloc(), the address 0x7f3e588fb080 is gen->finalizer, which is being called with the state gen->state at 0x7f3e58b54558, from $rdi.
 409 static void
  410 generator_dealloc(GeneratorObject *gen)
  411 {
  412     PyObject_GC_UnTrack((PyObject *) gen);
  413     if (gen->weakreflist != NULL)
  414         PyObject_ClearWeakRefs((PyObject *) gen);
  415     /* XXX The finalizer may be called after the LLVM module has been
  416        destroyed (typically at interpreter shutdown) */
  417     if (!_Py_IsFinalizing())
  418         if (gen->finalizer != NULL)
  419             gen->finalizer(gen->state); // GRM note for #8873: We're in this call at this point
  420     Py_XDECREF(gen->env);
  421     Py_TYPE(gen)->tp_free((PyObject *) gen);
  422 }

I'm starting to wonder if it's a python3.11 change with regard to how the finalizer is invoked.

The faulting address seems to be 0x3e800003f82:
(gdb) p $_siginfo
$8 = {si_signo = 11, si_errno = 0, si_code = -6, _sifields = {_pad = {16258, 1000,
      0 <repeats 26 times>}, _kill = {si_pid = 16258, si_uid = 1000}, _timer = {si_tid = 16258,
      si_overrun = 1000, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _rt = {si_pid = 16258,
      si_uid = 1000, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _sigchld = {si_pid = 16258,
      si_uid = 1000, si_status = 0, si_utime = 0, si_stime = 0}, _sigfault = {si_addr = 0x3e800003f82,
      _addr_lsb = 0, _addr_bnd = {_lower = 0x0, _upper = 0x0}}, _sigpoll = {si_band =<PHONE_NUMBER>258,
      si_fd = 0}, _sigsys = {_call_addr = 0x3e800003f82, _syscall = 0, _arch = 0}}}

At this point, we found out that the following makes the problem go away:

mp spawn context (https://github.com/numba/numba/issues/8872)
disabling vfork (https://github.com/numba/numba/pull/8876)

How do we tell if this is a bug in:

numba?
cpython?
llvm?

I have a smaller reproducer:
# file: trythis.py
import multiprocessing as mp
from numba.tests.test_generators import TestGenerators
from numba.tests.test_exceptions import TestRaising

def test_gen9():
    testcase = TestGenerators()
    testcase.test_gen9()

def test_gen9_objmode():
    testcase = TestGenerators()
    testcase.test_gen9_objmode()

def test_try_raise():
    testcase = TestRaising()
    testcase.test_try_raise()

def run(f):
    f()
    return f.__name__

def main():
    tests = [test_try_raise, test_gen9] * 10

    for i in range(100):
        pool = mp.Pool(4)
        for it in pool.imap_unordered(run, tests):
            print(it)

if __name__ == '__main__':
    main()

$ conda env export --from-history
name: /path/to/numba.py311.conda
channels:
  - defaults
dependencies:
  - python=3.11
  - numba/label/dev::llvmlite
  - numpy=1.23
  - gxx_linux-64
  - scipy
prefix: /path/to/numba.py311.conda

This is causing a segfault within 10seconds of running:
Current thread 0x00007f0e22e17700 (most recent call first):
  File "/path/to/numba/numba/tests/test_generators.py", line 276 in test_gen9
  File "/path/to/numba/trythis.py", line 7 in test_gen9
  File "/path/to/numba/trythis.py", line 19 in run

A even simpler reproducer is this:
# File: tryanother.py
from numba import njit
from numba.tests.test_generators import TestGenerators

@njit
def try_raise():
    a = 3
    try:
        raise ValueError(a)
    except Exception:
        pass
    return a + 1

for i in range(200):
    assert try_raise.py_func() == try_raise()

    testcase = TestGenerators()
    testcase.test_gen9()

At https://github.com/numba/numba/commit/201a2f8d65ea85731df72da556d2f292489ebcb3, running the script above will cause a segfault same as previous reproducer. I can confirm that the segfault does not occur in the previous commit on main (e520da897f1eb08cf9d3912b1ef67a1081f3a786).

The segfault goes away with git checkout e520da897f1eb08cf9d3912b1ef67a1081f3a786 numba/core/callconv.py numba/core/pythonapi.py.

I'm starting to think this might be related to the fix for #8236: https://github.com/numba/numba/pull/8134/commits/6fcb8d85bf22b61cf1c5ef5671ad0379c662cb6e#diff-2ff560db01080c0603b4aa9cc3763ed9ed8cb61c2006d3f9fcd0a58fb7faa798L110-R109
Methodology:

I've started with main from today (62fa8f0939d90fa723cddbb33e2d9ab0c72079a1) and reverted the merge of #8134 from it
I've applied commits on top of this from #8134, testing with tryanother.py at each step.
Once I applied https://github.com/numba/numba/pull/8134/commits/6fcb8d85bf22b61cf1c5ef5671ad0379c662cb6e on top, tryanother.py started segfaulting very reliably.
I added another commit on top that makes CPUContext.call_conv a cached property again: https://github.com/gmarkall/numba/commit/5416c29a86c38639890844b5eb07eba40b2c7023
Making this change causes tryanother.py to run to completion repeatedly again.

The branch I used is at: https://github.com/gmarkall/numba/tree/debug-8873

Additionally, cherry-picking 5416c29 on top of main also seems to make tryanother.py stop segfaulting.

https://github.com/numba/numba/issues/8873#issuecomment-1495226364 also reproduces under Python 3.10.

Documenting conclusion from triage meeting:
Problem most likely cause by MCJIT being released by compile_isolated() before the generator object is finalized.


New feature inspired of #12

related to #12
Before when entered a project and an asset the user was free to type any task and have that app launch, creating a new folder and this made it possible for the user to make misstakes. exampel:
first time they entered this input:
maya Modeling

maya Modeling
creating task "Modeling"

next time the misspelled and typed
Maya Modelling

Maya Modelling
creating task "Modelling"

this fix makes so that only acceptable input in the API terminal from already created bat files as it is with projects and assets
this PR also adds a creation API called new.bat
this allows the user to create projects, assets from the terminal.
example:

   Active Project: hulk
   You are in: film

  1000
  2000

  1. Type first letters of asset
  2. Press [TAB] to auto-complete

 --------------------------------------

$ new shot sh010

this will output:
new shot sh010 created

and now the artist can use:
sh010

This also works with APPS:
new maya modeling
adds the bat maya modeling.bat
and after that the artist can use either the bat or free string input to enter that task,
they cannot enter a other task though as described before, exampel:
maya modelling

maya modelling
ERROR: Unrecognised command "maya modelling"

This fixes #12 and also adds functionality to terminal API so that these limits also have a solution.

If you are happy with this, I'm happy too. Let me know and I'll merge.

I approve.
Merge away.
Make it so..


python version compatibility

The merge_dicts function is only compatible with Python 3.5+ due to the {**dict1, **dict2} syntax. It's a trivial fix to make it compatible with older versions of python 3.
Thanks @jimmoffitt for the note.

Also, the setup.py doesn't specify which versions of Python this package is compatible with. That should be setup to ensure 2.x users at least don't install this package if its not intended to be backward compatible

This is a good point, and I will make that change as well.

closed by #19 .


feat: add validator run event to allow plugins to perform custom validation

fix #2183

I don't think I want the validator to be a separate thing - it's not nearly complicated enough to deserve that... I'd rather just add the validate event to ApplicationEvents and emit it on the application, then if any validator logs or listener to that method logs an error, TypeDoc will exit with the ValidationError exit code.
If it does deserve pulling out into its own class someday - I'd still want to avoid the component and emit that event from the application I think... I'm not convinced that there's value for plugins in seeing a new class.

@Gerrit0 I've reworked this PR to address those issue :)

When working on my plugin that relies on this PR, reflection.comment.getTags("@param") always return an empty array. I'm not having this issue with any other tags. Am I missing something for this tag or is this a bug?

Thanks! Should release today.

When working on my plugin that relies on this PR, reflection.comment.getTags("@param") always return an empty array. I'm not having this issue with any other tags. Am I missing something for this tag or is this a bug?

Just realized I forgot to answer this -- @param tags are moved to the ParameterReflection instances, so you generally shouldn't have any @param tags, your plugin should probably check that signatureReflection.parameters all have comments.


Add access token scope checks to improve authorization

This PR adds the ability for SMD to check for scopes and implements two related functions: VerifyClaims and VerifyScope. It also moves dedicated OAuth functionality to a separate, dedicated file in cmd/smd/auth.go.
The VerifyClaims function is needed to make sure that the scope claim is included in the incoming access token. It can also be used later for checking for inclusion of other claims such as partition-id required for accessing specific resources.
The VerifyScope function is used to check the incoming access token for specific scopes for each endpoint. Currently, this has only been implemented for /State/Components and /Inventory/RedfishEndpoints with each requiring the smd_read scope. Submitting a valid token without the smd_read scope will return the following error:
curl http://<IP_ADDRESS>:27779/hsm/v2/Inventory/RedfishEndpoints -H "Authorization: Bearer eyJhbGciOi..."
{"type":"about:blank","title":"Unauthorized","detail":"failed to verify scope: invalid or missing scope","status":401}

However, for any other endpoint that is not checking for scopes, any valid access token is sufficient to use like before.

Once https://github.com/go-chi/jwtauth/pull/85 is merged, 06b7790 should be reverted.

Runner tests passing.


Use cache-control headers on pages requiring authentication

Issue Summary
When a Page is password protected, its publicly-viewable version displays a password form at the Page's URL. If caching is used, this means that the form itself can get cached, preventing the user from progressing to the Page itself - the cached password form can keep getting returned.
I and @vsalvino had this issue using wagtail-cache, which he provided a solution for. But he suggested that if Wagtail itself issued cache-control: private headers when the page required authentication, that would probably make more sense.
Steps to Reproduce

Install wagtail-cache (or maybe use some other caching solution)
Create a Page, set it to Live, and protect it with a Password
Visit the Page's URL and enter the correct password
Instead of getting the Page itself, the form will be returned.

Technical details

Python version: 3.6
Django version: 2.1
Wagtail version: 2.4
Browser version: macOS Safari 12

Looks like there was a similar proposal in 2015, closed due to lack of interest. @loicteixeira in Slack suggested I open this.

To further clarify, step 1 above could be replaced with an upstream cache such as cloudflare, varnish, etc.
Wagtail does not seem to have an opinion on cache-control headers, which is fine. But if anyone is using an upstream cache, depending on the nature of content some pages would be cacheable, some pages would not (based on same URL but different content). Examples include pages with password view restrictions (the same url is used to serve the form and the page content) and form pages (different content depending on GET/POST, and CSRF token). Most caches should ignore the POST requests, but it is not guaranteed.
My question is would it make sense to add cache-control headers to all responses, or only to responses where the instruction is not to cache? Or maybe not at all and let the developer decide?
In wagtail-cache 0.4 we have solved this with a mixin that sets cache-control header as appropriate, and also allows the developer to specify a custom cache-control header on each model using the cache_control attribute.

I was thinking that the Vary: Cookie header that Django automatically emits whenever request.session is accessed would solve this. But this might not be the case if the cookies are being created by this view.
What I think might be happening is follows:

When the first user without a cookie visits the page, Django creates session and returns response with Set-Cookie and Vary: Cookie headers

When the second user without a cookie visits the page, the cache returns the first user's response because they didn't have a cookie when they made the request

If that's the case, then adding Cache-control: private or just Cache-control no-cache="Set-Cookie" should solve it.

The lack of Cache-Control headers caused us not only an availability issue (CSRF errors when attempting to log in) but also significant security issues (the password-protected content was visible without logging in due to the cache, once a different browser could log in).
https://github.com/coderedcorp/wagtail-cache/issues/35 details some o


Define static headers on an App

Is your feature request related to a problem? Please describe.
Today it is not possible to inject HTTP headers on an App deployed by the AWS Amplify console.
This is a problem because the Security best practices recommend to define several of them appropriately:

Strict-Transport-Security
Content-Security-policy
X-Frame-Options
X-XSS-Protection
X-Content-Type-Options

see reference
Because of the missing headers Modzilla Observatory is giving my Amplify hosted project a F
Describe the solution you'd like
It would be nice to be able to define static headers on an App for an AWS Amplify Console app.
Additional context
On an Amplify project hosted by S3andCloudfront injecting the header is possible using Lambda@Edge

@xavierraffin if you're using Amplify Console to deploy a ci/cd app, you can set custom headers:
https://docs.aws.amazon.com/amplify/latest/userguide/custom-headers.html
If you're using the Amplify CLI, you'll need to choose Amplify Console and ci/cd app as the hosting option: https://aws.amazon.com/blogs/aws/host-your-apps-with-aws-amplify-console-from-the-aws-amplify-cli/
We'll be adding support for custom headers for manual deploy apps soon, you can track that in #777
Please let us know if this doesn't work for you or you have any questions or concerns.


Interpolation with multiple mutlidimensional arrays sharing dims fails

What happened:
When trying to interpolate a N-D array with 2 other arrays sharing a common (new) dimension and with one (at least) being multidimensional fails. Kinda a complex edge case I agree. Here's a MWE:
da = xr.DataArray([[[1, 2, 3], [2, 3, 4]], [[1, 2, 3], [2, 3, 4]]], dims=('t', 'x', 'y'), coords={'x': [1, 2], 'y': [1, 2, 3], 't': [10, 12]})
dy = xr.DataArray([1.5, 2.5], dims=('u',), coords={'u': [45, 55]})
dx = xr.DataArray([[1.5, 1.5], [1.5, 1.5]], dims=('t', 'u'), coords={'u': [45, 55], 't': [10, 12]})

So we have da a 3D array with dims (t, x, y). We have dy, containing the values of y along new dimension u. And dx containing the values of x along both u and t. We want to interpolate with:
out = da.interp(y=dy, x=dx, method='linear')

As so to have a new array over dims  t and u.
What you expected to happen:
I expected (with the dummy data I gave):
xr.DataArray([[2, 3], [2, 3]], dims=('t', 'u'), coords={'u': [45, 55], 't': [10, 12]})

But instead it fails with ValueError: axes don't match array.
Full traceback:

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-19-b968c6f3dae9> in <module>
----> 1 a.interp(y=y, x=x, method='linear')

~/Python/xarray/xarray/core/dataarray.py in interp(self, coords, method, assume_sorted, kwargs, **coords_kwargs)
   1473                 "Given {}.".format(self.dtype)
   1474             )
-> 1475         ds = self._to_temp_dataset().interp(
   1476             coords,
   1477             method=method,

~/Python/xarray/xarray/core/dataset.py in interp(self, coords, method, assume_sorted, kwargs, **coords_kwargs)
   2691                     if k in var.dims
   2692                 }
-> 2693                 variables[name] = missing.interp(var, var_indexers, method, **kwargs)
   2694             elif all(d not in indexers for d in var.dims):
   2695                 # keep unrelated object array

~/Python/xarray/xarray/core/missing.py in interp(var, indexes_coords, method, **kwargs)
    652             else:
    653                 out_dims.add(d)
--> 654         result = result.transpose(*tuple(out_dims))
    655     return result
    656

~/Python/xarray/xarray/core/variable.py in transpose(self, *dims)
   1395             return self.copy(deep=False)
   1396
-> 1397         data = as_indexable(self._data).transpose(axes)
   1398         return type(self)(dims, data, self._attrs, self._encoding, fastpath=True)
   1399

~/Python/xarray/xarray/core/indexing.py in transpose(self, order)
   1288
   1289     def transpose(self, order):
-> 1290         return self.array.transpose(order)
   1291
   1292     def __getitem__(self, key):

ValueError: axes don't match array

Anything else we need to know?:
It works if dx doesn't vary along t. I .e.: da.interp(y=dy, x=dx.isel(t=0, drop=True), method='linear') works.
Environment:
Output of xr.show_versions()
INSTALLED VERSIONS
commit: None
python: 3.8.5 | packaged by conda-forge | (default, Jul 31 2020, 02:39:48)
[GCC 7.5.0]
python-bits: 64
OS: Linux
OS-release: 3.10.0-514.2.2.el7.x86_64
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_CA.UTF-8
LOCALE: en_CA.UTF-8
libhdf5: 1.10.5
libnetcdf: 4.7.4
xarray: 0.16.2.dev9+gc0399d3
pandas: 1.0.3
numpy: 1.18.4
scipy: 1.4.1
netCDF4: 1.5.3
pydap: None
h5netcdf: None
h5py: 2.10.0
Nio: None
zarr: None
cftime: 1.1.3
nc_time_axis: 1.2.0
PseudoNetCDF: None
rasterio: 1.1.4
cfgrib: None
iris: None
bottleneck: 1.3.2
dask: 2.17.2
distributed: 2.23.0
matplotlib: 3.3.1
cartopy: 0.18.0
seaborn: None
numbagg: None
pint: 0.11
setuptools: 49.6.0.post20200814
pip: 20.2.2
conda: None
pytest: None
IPython: 7.17.0
sphinx: None

Hi @aulemahal
I think you want to interpolate along tas well as x, and y.
If so, you can do
In [8]: da.interp(t=dx['t'], y=dy, x=dx, method='linear')
Out[8]:
<xarray.DataArray (t: 2, u: 2)>
array([[2., 3.],
       [2., 3.]])
Coordinates:
  * t        (t) int64 10 12
    y        (u) float64 1.5 2.5
    x        (t, u) float64 1.5 1.5 1.5 1.5
  * u        (u) int64 45 55

If not, this fails as dx['t'] and da['t'] do not match each other.
The error message can be improved.
A contribution is welcome ;)

I think this gives the correct result?
>>> da.interp(t=da['t'], y=dy, x=dx, method='linear')
<xarray.DataArray (t: 2, u: 2)>
array([[2., 3.],
       [2., 3.]])
Coordinates:
  * t        (t) int64 10 12
    y        (u) float64 1.5 2.5
    x        (t, u) float64 1.5 1.5 1.5 1.5
  * u        (u) int64 45 55

My general thought is that if an axis (like t in this case) is omitted, then should be equivalent to indexing with the existing coordinate. That is how normal indexing in xarray worked, so interpolation should work the same.

Oh! I should have thought of this. The error message is indeed unclear...
I'll close the issue as the problem is solved, but I'll note that:
da.sel(y=dy, x=dx, method='nearest')

does work, without the need to explicitly pass the shared dimension t.  This is why I expected that interp would work the same.

The error message is indeed unclear.

reopening so that we can fix this.

I'll note that:
da.sel(y=dy, x=dx, method='nearest')

does work, without the need to explicitly pass the shared dimension t. This is why I expected that interp would work the same.

I think interp should work in this case, too!
Let's keep this issue open to track that.


Demo adding constraint to duplicated field (#1198)

#1198

Dammit, I pulled the trigger on this one a little early - seems it doesn't play nicely with the upsert functions...


Switched to renamed CHTTPParser

Closes IBM-Swift/Kitura#629
Description

Motivation and Context

How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

@ianpartridge Please review and merge.


New navigation

@EdwardIrby here's the change I mentioned before. I still need to do all the work for filtering etc., but this get's the basic structure in there. I also left the Modules page mostly empty until we get around to styling it.


rpc-support: Unnecessary host packages should be removed for old deployments

Starting with commit c6798eb778621819e13f0334778ff2d55d7ff2b1 we do not install the host packages on containers anymore but a remove task is missing to remove them from the old containers

[ ] kilo

this was kilo only, just docing that ehre

closed based on PR and asking @BjoernT in irc


terraform-ls: 0.19.0 -> 0.19.1

Motivation for this change
Bump terraform-ls to 0.19.1
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

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

2 packages built:

terraform-ls
vscode-extensions.hashicorp.terraform


"TTY::Screen#size_from_ioctl reads terminal size" test fails on big endian systems

Failures:

  1) TTY::Screen#size_from_ioctl reads terminal size
     Failure/Error: expect(screen.size_from_ioctl).to eq([51, 211])

       expected: [51, 211]
            got: [13056, 54016]

       (compared using ==)
     # ./spec/unit/screen_spec.rb:115:in `block (4 levels) in <top (required)>'
     # ./spec/unit/screen_spec.rb:108:in `replace_streams'
     # ./spec/unit/screen_spec.rb:114:in `block (3 levels) in <top (required)>'

According to our arch team testers this is an endianess error, when you take the numbers as big endian uint16 and convert them to little endian they match the expected values.
This can be reproduced by running the specs on a big-endian system such as hppa or sparc.

OS version: Gentoo Linux
Ruby version: 2.6.8
TTY::Screen version: 0.8.1

Our Gentoo downstream bug report for reference: https://bugs.gentoo.org/808174

Hi Hans,
Thanks for reporting this issue.
From my quick 'research' it seems that systems that use big-endian are in minority.  The HPPA architecture is from 1996 and SPARC from 1993. I wonder how many people are affected by this issue?
The size_from_ioctl unpacks binary string returned by ioctl call with S integer directive. This directive means "16-bit unsigned, native endian (uint16_t)". So it returns whatever endian is used by the system and packs the string using the same endian. This should be a portable solution.
To make this work, we would need to detect the endianness of the system and use the appropriate directive to decode it. For example, based on the article How to check your system endianness with Ruby, we could detect endian like so:
def big_endian?
  [1].pack("S") == [1].pack("n")
end

It seems that we could use v directive "16-bit unsigned, VAX (little-endian) byte order" to convert returned byte string to little-endian. In other words, convert this line:
rows, cols, = buffer.unpack(format)[0..1]

To something like this:
rows, cols, = buffer.unpack(big_endian? ? "vvvv" : "SSSS")

Would you mind testing if this works? I need your help as I don't have access to a system I could test this with.

I have no clue about ruby, so I struggle to get the syntax right (e.g. where to put that def). Could you please provide a patch. Also, is the last line missing the [0..1]?

@graaff @DerDakon I had realised that the size_from_ioctl method isn't at fault. It packs and unpacks binary strings in the endianness native for the system. What was 'broken' is the test itself. In particular, the stubbed ioctl call always returned a canned little-endian result which failed the conversion on big-endian system. I have provided a patch referenced in this issue that should make the failing test pass. Could you please test it and let me know if it works?

Yes, tests pass now. Thanks.

Thanks for the quick responses and the fix!


Member videos/streams

Can you add a toggle for member content? There's a way of watching member streams/videos of the channel you are subscribed to via mpv but it's quite complicated in its own way, would be nice to have it in the userscript.

Do you mean --cookies or --username & --password?
If it is --cookies.
Cannot support, because userscript cannot get HttpOnly cookies.
(So far, only Tampermonkey Beta provided the GM_cookies to read HttpOnly cookies.)
So, --cookies method to play member videos will not be supported until all userscript manager provided the GM_cookies API.
If it is --username & --password.
Save account password in cleartext, it's dangerous.

But we have another way to use --cookies method.

Save cookies to file manually.
Add a option Try pass cookies in userscript.
When enable this option, mpv-handler will try pass the cookies file to youtube-dl.

Is this method acceptable?

I have got the cookies.txt, can you help me show where I can add it to the script?

I have got the cookies.txt, can you help me show where I can add it to the script?

I will add this feature to userscript and mpv-handlers in a few days.

Already supported pass cookies to youtube-dl.
See README#pass-cookies-to-youtube-dl


Make argon support VSC Beta

Title says it all, was told to make issue here instead

Added in 1.3.1.


Enhancement: Extend m365 status with an option --validateLogin

Extend m365 status with the following extra option.

Option
Description

--validateLogin
Return true or false value to validate you Microsoft 365 login status.

When we extend the m365 status command with e.g. an option --validateLogin. This would allow the command to only return a true or false value that we then could use in all of our script samples. What are your thoughts on this suggestion @.maintainers?
Originates from:

https://github.com/pnp/cli-microsoft365/issues/3472#issuecomment-1175471457

I think it would be better to extend the return type, and use the same return json when you are signed out:
Or we could update the return type:
{ loggedIn: true, connectedAs<EMAIL_ADDRESS>}

and
{ loggedIn: false }

Like I mentioned in #3472, to me the intent of --validateLogin is unclear. I'd suggest we rephrase it to something else that more clearly communicates what it will do.
@martinlingstuyl what's the difference between comparing the value of the JSON object we'd return following your proposal and comparing the value of the Logged out string we have at the moment?

I've got a few reasons for wanting a change:

The current setup actually returns two different types of content in json output mode when signed in VS when signed out. it's both JSON, but it's a json object VS a string. I think that's unhelpful. Like we're back in JavaScript days 😂
So you could append --output text to fix that, but then again: you need to write more text.
I personally find it better to compare against a boolean, than to compare against a string. Less code, more clarity.

Understood. The question is: does it matter that we return two different types of data in the status? In what scenario would you be using them simultaneously and where the current scenario could be inconvenient?
As for the comparison of current vs. proposed:
current:
$m365Status = m365 status -o text
if ($m365Status -eq "Logged out") {
    m365 login
}

proposed:
$m365Status = m365 status | ConvertFrom-Json
if ($m365Status.loggedIn -eq $false) {
    m365 login
}

Looking at both options, I don't think that the argument of writing less stands, because CLI always outputs a string, which you need to convert to an object first before you can do anything with it, and a boolean comparison in PowerShell still requires -eq $false.

Looking at both options, I don't think that the argument of writing less stands

Hadn't thought of that, you're correct. 😂 ok, you've convinced me. Let's agree we keep it this way and close the issue


[Bug]: ValueError: operator image-decode/cv2 not found!

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Thanks for read this.
I just follow this guide,
https://codelabs.towhee.io/build-a-reverse-image-search-engine-in-minutes/index#2
And I meet the bug. ValueError: operator image-decode/cv2 not found!
How can i deal with it ?
Thank you for your help
Expected Behavior
No
Steps To Reproduce
No

Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No

Hi @wbc110460 , which version of towhee are you using? I think it required towhee>=0.7.

Hi @wbc110460 , which version of towhee are you using? I think it required towhee>=0.7.

but my towhee is (0.8.0). emm

Hi @wbc110460 , which version of towhee are you using? I think it required towhee>=0.7.

but my towhee is (0.8.0). emm

Oh. I reinstalled it once again, and it ran.

Hi @wbc110460 , which version of towhee are you using? I think it required towhee>=0.7.

but in this url:https://codelabs.towhee.io/build-a-reverse-image-search-engine-in-minutes/index#3
I can't find the func read_images :  (func=read_images)
how can i deal with it?

Hi @wbc110460 , which version of towhee are you using? I think it required towhee>=0.7.

but in this url:https://codelabs.towhee.io/build-a-reverse-image-search-engine-in-minutes/index#3 I can't find the func read_images : (func=read_images) how can i deal with it?

You can refer to the notebook, it seems that the website lacks this function, I will add it, thank you :)

您好。我看咱们towheel支持视觉问答模型。但是那些例子里没有视觉问答的。 最近你们准备上一个这样的吗？
发自我的iPhone
------------------ Original ------------------
From: shiyu22 @.>
Date: Wed,Aug 24,2022 9:52 AM
To: towhee-io/towhee @.>
Cc: 王炳超 @.>, Mention @.>
Subject: Re: [towhee-io/towhee] [Bug]: ValueError: operator image-decode/cv2 not found! (Issue #1818)
Hi @wbc110460 , which version of towhee are you using? I think it required towhee>=0.7.
but in this url:https://codelabs.towhee.io/build-a-reverse-image-search-engine-in-minutes/index#3 I can't find the func read_images : (func=read_images) how can i deal with it?
You can refer to the notebook, it seems that the website lacks this function, I will add it, thank you :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Ability to use dunner with docker images whose entrypoint is defined

For Docker images whose entrypoint is defined and are run as an executable, Dunner fails to execute commands defined in it.
Example: Goreleaser's docker file.
Dunner task file:
tasks:
  release:
    steps:
      - image: goreleaser/goreleaser
        commands:
          - ["echo", "hello"]
          - ["goreleaser", "--version"]

Running this command with dunner fails with error as:
OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown
FATA[2019-08-26 18:39:51] docker: command execution failed with exit code 126

What if the entry point is something like /app/src/python/main/analyze.py? Then someone who uses this docker needs to put this again and again in commands, right?
tasks:
  release:
    steps:
      - image: SCoRe/MLKit
        commands:
          - ["/app/src/python/main/analyze.py", "--algo","ImageNet"]

Is some cases, users really don't know what is the entry point is. I strongly suggests against users having to define the entry point in commands.
WDYT @PratikDhanave @tdevinda @charithccmc @tharindupr @rehrumesh?


Unknown source file : com.android.dex.DexException: Multiple dex files define Lcom/oney/WebRTCModule/BuildConfig;

I am wondering if someone has run into this issue.  Where the build on the android (which was working till yesterday) is now giving me an error.  I had installed the react-native-permissions library, react-native-maps(which I removed because it was causing problems in the build too. Unlinked it with the react-native unlink command).
I have cleaned the cache, removed the webrtc and re-installed it.  At a total loss.
If someone has run into this issue and has been able to resolve it, would greatly appreciate the help.
Thanks

try adding:
android {
  ...
  defaultConfig {
    ...
    multiDexEnabled true

@nickkapoor
does adding support for multiDex solves your problem?

No follow-up, closing.

I do have multidex set to true. Given up on using react native for android. Too many issues with memory being freed up for a highly image based solution.

I have the same issue.
Multiple dex files define Lcom/oney/WebRTCModule/WebRTCModulePackage

does adding support for multiDex solves your problem?
No. The error persists. I checked that the module is included only once in the code.


output: refactor error handling and fix io.Reader implementation

Removes all the command-error-waiting stuff with a simple writer.CloseWithError - this means that read operations now return our command error after the buffer is cleared from reads. This greatly simplifies most of the output code - now, we can simply bubble up errors from read operations. It also the io.Reader implementation is now correct (closes https://github.com/sourcegraph/run/issues/23)

Codecov Report

Merging #32 (0b5e3a0) into main (585cd79) will increase coverage by 3.64%.
The diff coverage is 97.14%.

@@            Coverage Diff             @@
##             main      #32      +/-   ##
==========================================
+ Coverage   69.68%   73.33%   +3.64%
==========================================
  Files           8        8
  Lines         353      300      -53
==========================================
- Hits          246      220      -26
+ Misses         86       63      -23
+ Partials       21       17       -4

Impacted Files
Coverage Δ

output.go
86.84% <97.14%> (+9.76%)
:arrow_up:

Continue to review full report at Codecov.

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


Allow explicitly setting environment requested from config file

Allows using "production" RACK_ENV/RAILS_ENV, while specifying separate env from the config file
Issue # (if available)
Discussed in #87 — basically, for Rails apps, you normally want to set the RAILS_ENV to production (see Heroku's comment on this here: https://devcenter.heroku.com/articles/deploying-to-a-custom-rails-environment). When using the same config/symmetric-encryption.yml on multiple deployments (eg on Heroku stage/acceptance/production), you need a way to specify which node on the config file you'd like to use.
This could also be handled by adding separate config files for each deploy environment and using ENV['SYMMETRIC_ENCRYPTION_CONFIG'], but this method seems more elegant.
Description of changes
Added the ability to specify, with ENV['SYMMETRIC_ENCRYPTION_CONFIG'], which node is used on the yaml config, beyond just using RACK_ENV or RAILS_ENV.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Just to be clear, this allows for a single YAML config as below, and then for eg your acceptance environment, your env variables would be:
SYMMETRIC_ENCRYPTION_CONFIG=acceptance
RAILS_ENV=production
SYMMETRIC_ENCRYPTION_ACCEPTANCE_V1=abcdef
staging:
  ciphers:
  - cipher_name: aes-256-cbc
    version: 1
    key_env_var: SYMMETRIC_ENCRYPTION_STAGING_V1
    iv: !binary |-
      abcdef
    key_encrypting_key:
      key: !binary |-
        abcdef
      iv: !binary |-
        abcdef
acceptance:
  ciphers:
  - cipher_name: aes-256-cbc
    version: 1
    key_env_var: SYMMETRIC_ENCRYPTION_ACCEPTANCE_V1
    iv: !binary |-
      abcdef
    key_encrypting_key:
      key: !binary |-
        abcdef
      iv: !binary |-
        abcdef
production:
  ciphers:
  - cipher_name: aes-256-cbc
    version: 1
    key_env_var: SYMMETRIC_ENCRYPTION_PRODUCTION_V1
    iv: !binary |-
      abcdef
    key_encrypting_key:
      key: !binary |-
        abcdef
      iv: !binary |-
        abcdef

I just found this PR to use different environment. Its correct environment variable name is SYMMETRIC_ENCRYPTION_ENV , not SYMMETRIC_ENCRYPTION_CONFIG .
Thank you.

@jagaapple thanks, I updated my comment above to show the correct ENV variable


DRILL-7093 Batch Sizing in SingleSender

This PR contains changes for implementing batch sizing in SingleSender. The sizing is done by using the RecordBatchSizer.

Code changes look good to me. I have few minor comments.


Fix broken developer link

The link to the optimism docs is broken and produces a 404.  This fix will bring the user to the developer page.

@beakerfm thanks for this! can you also update the link on line 178
it has the same problem

@emilyJLin95 I have now updated the second link as you suggested.  It should point to the relevant available documentation now.

@beakerfm thanks so much! One last ask - can you squash your commits and rebase off the latest main, and then I'll merge! 😄

Thanks for this PR @beakerfm! Same request as Emily and then we're happy to merge this in.

@fainashalts @emilyJLin95 sorry for the delay. It should now be updated as you requested.

@beakerfm woohoo!! merged!!


Encoding from AudioBuffer

Would be handy for integration with the web audio API to be able to encode an audio buffer. Something like (not functional of course):
const Lame = require("./index").Lame;
const fsp = require("fs-promise");

const AudioContext = require("web-audio-engine").StreamAudioContext;
const audioContext = new AudioContext;

const TESTFILE = "./test/example.wav";
const OUTPUTFILE = "./test/encoded.mp3";

fsp.readFile(TESTFILE)
  .then((inputBuffer) => {

    audioContext.decodeAudioData(inputBuffer, (audioBuffer) => {

      const instance = new Lame({
        "output": OUTPUTFILE,
        "bitrate": 128
      })

      let buffer = Buffer.from(audioBuffer.getChannelData(0));

      instance.setBuffer(buffer);
      instance.encode().then(() => { console.log('encoding over') });

      console.log('loaded audio buffer duration:', audioBuffer.duration + 's');

    });
  });

Feel free to integrate this package as dependency in your liberty.


The Badge "Libraries.io - Sourcerank" shows wrong data

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] badge-maker NPM package

:beetle: Description

The badge "sourcerank" from Libraries.io shows in my case a rank of 8, while on Libraries.io, the actual rank is 4.

Screenshot
Rank calculation

Libraries.io link: https://libraries.io/github/Paebbels/pyAttributes
:link: Link to the badge
Generated URL from shields.io: https://img.shields.io/librariesio/sourcerank/pypi/pyAttributes

:bulb: Possible Solution
As this discrepancy exists since days, I would exclude short time image caching.

This is related to:

#1532

The corresponding libraries.io link for that badge is https://libraries.io/pypi/pyAttributes

https://libraries.io/pypi/pyAttributes reports a sourcerank of 11
https://libraries.io/api/pypi/pyAttributes reports a sourcerank of 11
https://img.shields.io/librariesio/sourcerank/pypi/pyAttributes reports a sourcerank of 11

so the badge is behaving as expected

So libraries.io has my "package" listed twice?

the PyPI package
the GitHub repository

https://libraries.io/github/Paebbels/pyAttributes is the repository https://libraries.io/pypi/pyAttributes is the package.
Its an oddity of the platform that Libraries.io gives a different sourcerank score to a package and its corresponding source repository. This is true across the board (e.g: https://libraries.io/pypi/requests vs https://libraries.io/github/psf/requests ) but if you want to discuss that in more detail, an issue on https://github.com/librariesio/libraries.io/issues is the place to do that. We don't run libraries.io - we just consume their API.

@chris48s thanks for the support and clarifying that there are two views and also 2 ranks.


Add SourceRef as possible reference for Config values

What would you like to be added:
Why is this needed:

Great feature 👏 💯


Change Indicator Height/Width and TextSize to public getter/setters.

Simple changes for the above.

Why add setIndicatorWidth and the other setters? Normally you'd want this to be a protected value and it isn't needed for a custom indicator.


Feature: Automatic update of metric when removing algorithm of Excel table results.

Since the deviation from the best solutions of an experiment is calculated when the data is passed to excel, it appears as a numerical value in the "Raw results" sheet. Therefore, when an algorithm that has better solutions is removed, the deviation from the best solutions is not updated. To obtain that value it is necessary to: rerun the experiment without that algorithm (easy wrong answer) or recalculate that value "by hand" (oh please, no!).
How it could be solve it? The pivot tablet should automatically generate these metrics from the raw result sheet.

Implemented using a more complex formula, should work in Excel 2007+.
User can enable or disable calculation in Excel, by default only used when there is less than 2.000 rows.
@scaverod could you test it?

Sure. I will let u know as soon as possible.

Feature works, closing


used .replace function to replace white space in URL's with dashes

Added the line langs[lang]["url"] = langs[lang]["url"].replace(' ','-')to the python file. This is because when there are languages with two names ("1C Enterprise" for example) it doesn't remove the spaces when concatenating the URL  (i.e. "https://github.com/trending?l=1C Enterprise") which is invalid markdown syntax and thus messes up the README.md file resulting in this:

The .replace line replaces all of the whitespace in in the URL's with - which fixes this problem while still linking to it's intended destination.

SEE: https://github.com/trending?l=1C-Enterprise as proof that URL is still directing user to intended destination.

👍


Release upload Failed

Since yesterday afternoon I'm no longer able to upload releases. I've been uploading releases for a very long time without a problem.
I'm using the latest version of the appcenter CLI ( 2.7.3 ).
appcenter distribute release --silent --file "......" --release-notes-file "changelist.md" --app "......" --group "Collaborators" --build-number "2"
I get this error.
Release upload failed
| Aborting release upload...(node:86813) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'release_distinct_id' of undefined
    at ReleaseBinaryCommand.<anonymous> (/Users/jamesonparker/.nvm/versions/node/v10.19.0/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
    at Generator.throw (<anonymous>)
    at rejected (/Users/jamesonparker/.nvm/versions/node/v10.19.0/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:86813) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:86813) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Release upload was aborted
Error: Loading release id failed with error: failed to get release id for upload id: 245f1128-ca3f-4709-9e40-3c6e11579ffa, error: {"succeeded":false,"errorCode":3,"errorMessage":"failed to get release id with HTTP status: 504 - Gateway Time-out"
}

I also experienced the same thing and had to trigger an 'appcenter login', but after this the upload doesn't work using the same token as before.. it just hangs in 'verifying uploaded file'
I tried to use some of the tokens from the 'appcenter tokens list' but doesn't work.. fails with 'unauthorized'

Same for me: stuck with "Checking the uploaded file..."

Same for me:
Release upload failed
| Aborting release upload...(node:16622) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'release_distinct_id' of undefined
    at ReleaseBinaryCommand.<anonymous> (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
    at Generator.throw (<anonymous>)
    at rejected (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

error: {"succeeded":false,"errorCode":3,"errorMessage":"failed to get release id with HTTP status: 502 - Bad Gateway"}

Same here. Old REST API stopped working today and the recommended CLI replacement fails, so any CI automation is pretty much blocked :man_shrugging:

We seem to be getting the same issue. We just updated the appcenter-cli to the latest version and get this error.
(node:77866) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'release_distinct_id' of undefined
December 8th 2020 14:28:58Error
at ReleaseBinaryCommand. (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
December 8th 2020 14:28:58Error
at Generator.throw ()
December 8th 2020 14:28:58Error
at rejected (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
December 8th 2020 14:28:58Error
at process._tickCallback (internal/process/next_tick.js:68:7)
December 8th 2020 14:28:58Error
(node:77866) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
December 8th 2020 14:28:58Error
(node:77866) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
December 8th 2020 14:29:16Info
Response status code: 200
December 8th 2020 14:29:16Info
Body: {}
December 8th 2020 14:29:16Info
Release upload was aborted
December 8th 2020 14:29:16Info
Error: Loading release id failed with error: failed to get release id for upload id: eaac6f6b-3a58-4792-87d7-28ec94e5d37c, error: {"succeeded":false,"errorCode":3,"errorMessage":"failed to get release id with HTTP status: 504 - Gateway Time-out"}

Same for us. All CI is borked by this and we're at a standstill. We need an urgent resolution.

I have the same problem in CI but manually run is a success. I don't know what's the problem.

Same here. I'm using appcenter-cli v2.7.3.

Downgrading to v2.7.0 doesn't fix it.
We're getting 502 - Bad Gateway - errors. Is the back end down?

Now I got "Release upload failed"
| Aborting release upload.../usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360
const releaseId = response.release_distinct_id;
^
TypeError: Cannot read property 'release_distinct_id' of undefined
at ReleaseBinaryCommand. (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
at Generator.throw ()
at rejected (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:93:5)
Also using appcenter version 2.7.3

I have the same problem in CI but manually run is a success. I don't know what's the problem.

for it doesn't work even to upload manually from the webpage.. it just hangs in upload and cannot click on next

The same happens with our project
Release upload failed
/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360
                    const releaseId = response.release_distinct_id;
                                               ^

TypeError: Cannot read property 'release_distinct_id' of undefined
    at ReleaseBinaryCommand.<anonymous> (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
    at Generator.throw (<anonymous>)
    at rejected (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)

Going on to AppCenter, the build in question appears to have been uploaded, but has not been distributed. So it looks like the upload is succeeding, but a subsequent step is failing.

Yes, upload works fien for me. "Checking the uploaded file..." step fails after some time. It looks like the script is trying to fetch updated status info every second or two. And then fails.

Posting this because our error is slightly different than the OP.  We are seeing "502 - Bad Gateway" versus "504 - Gateway Time-out"
This is the full text of the failure we're seeing after running the following CLI command:
appcenter distribute release --app / --file ./***.ipa --group "Collab" --token ***************************
The upload appears to succeed, but then fails after a long wait during "Checking the uploaded file...".  Using CLI version 2.7.3.
Release upload failed
| Aborting release upload...(node:20421) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'release_distinct_id' of undefined
    at ReleaseBinaryCommand.<anonymous> (/Users/***/.nvm/versions/node/v12.14.1/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
    at Generator.throw (<anonymous>)
    at rejected (/Users/***/.nvm/versions/node/v12.14.1/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
(node:20421) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:20421) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Release upload was aborted
Error: Loading release id failed with error: failed to get release id for upload id: a5f15b7d-1fee-4fe5-8edf-***************, error: {"succeeded":false,"errorCode":3,"errorMessage":"failed to get release id with HTTP status: 502 - Bad Gateway"}

This is now reflected on the status page as a Major Outage for Distribute.
https://status.appcenter.ms

@joakimkemeny lol. Well that sure is helpful 20 hours after the fact.

I just wanted to chip in for Azure DevOps users. Here's what I am seeing in the App Center distribute task logs with system.debug enabled:
[debug]-- Getting release id.
[debug]---- url: https://api.appcenter.ms/v0.1/apps/FOO_BAR/BIZ_BUZZ/uploads/releases/SOME_ID
[debug]---- "{\"id\":\"SOME_ID\",\"upload_status\":\"uploadFinished\"}"
[debug]---- http call status code: 200

It will simply loop over these logs over and over for 15+ minutes.

Status page (https://status.appcenter.ms/) is saying it's resolved ... but even trying it out through swapper (https://openapi.appcenter.ms/#/distribute/releaseUploads_create) throws a 500 error.
🤔

I'm getting this error in DevOps now:
```
2020-12-08T21:09:31.6967223Z ##[debug]-- Mark package available.
2020-12-08T21:09:31.6967976Z ##[debug]---- url: https://api.appcenter.ms/v0.1/apps/FOO_BAR/BIZ_BUZZ/releases/121/groups
2020-12-08T21:09:31.9328216Z ##[debug]---- {"code":"dependent_service_error","message":"Error: {"error":{"code":"DatabaseError","message":"Conversion failed when converting from a character string to uniqueidentifier."}}"}
2020-12-08T21:09:31.9329359Z ##[debug]---- http call status code: 500

@Brantone You're probably running into this one: https://status.appcenter.ms/incidents/4nbhlm0lxsvt
I'm not sure when, but the incident page says that there was prior communication about the old distribute APIs being shut down, and that everyone needs to move to appcenter-cli v2.7.0 or newer. They also mention moving away from the Swagger APIs that you linked:

The appcenter distribute release command in App Center CLI versions prior to v2.7.0 has stopped functioning as per our earlier communications (related to the HockeyApp SDK shutdown communicated earlier, as the old API depends on a HockeyApp proxy). To continue using the App Center distribution capability from the CLI, please upgrade your CLI to the latest version (v2.7.0 or above). You can upgrade the Appcenter CLI by running the following command in your terminal/command prompt: npm i -g appcenter-cli.
Also, if you are using custom scripts with our swagger API, please adjust your script based off the implementation of App Center CLI.

As for the new APIs, I can't find any documentation on them. I ran mitmproxy and the upload seems more complex now (it's doing chunked uploads), so my team decided to just install Node.js on our build agents and switch to using appcenter-cli for uploads, rather than making the distribute release API calls ourselves.

Hello I think I runned into similar problem. We have Azure DevOps Server 2019 version 17.143.28621.4
I am using this task:
2020-12-08T23:08:53.5435620Z Task         : App Center Distribute
2020-12-08T23:08:53.5435680Z Description  : Distribute app builds to testers and users via App Center
2020-12-08T23:08:53.5435750Z Version      : 1.139.2
2020-12-08T23:08:53.5435810Z Author       : Microsoft Corporation
I am getting error about "This API is deprecated. Please use the latest version of the App Center CLI" But how can I update App Center CLI on Azure Devops Server. Should I install some DevOps update package? I  am writing here because I think it's similar issue. If not I will start new.
Many thanks.

@Symorp You should update the task. The latest version is 3.173.0.

@rpendleton Part of the confusion is the lack of consistency .. for example: the status mentions Swagger API, but has not been consistent today. Ex: aforementioned 500, half way through today it moved to 410, and yet it still lists as available despite others which are officially deprecated are struck-out with mention of being deprecated.

I got the error when uploading the release to app center.
Release upload failed
logFilter, request: {
"rawResponse": false,
"queryString": {},
"url": "https://api.appcenter.ms/v0.1/apps/xxxxx/xxxxxxx/release_uploads/14714ee1-4eb8-4855-89b3-1260585bda4b",
"method": "PATCH",
"headers": {
"Content-Type": "application/json; charset=utf-8",
"user-agent": "appcenterCli/2.7.3 NodeJS/v12.16.1 darwin/19.6.0",
"x-api-token": "XXXXXXXXXXXXXXX"
},
"body": "{"status":"aborted"}"
}
Response status code: 410
Body: {"code":"gone","message":"This API is deprecated. Please use the latest version of the App Center CLI: https://github.com/microsoft/appcenter-cli, or if you need a custom script please use the CLI as the basis for your implementation. (Support ID: 8c1df1d9-7531-4c55-a278-2b64e1b2a661)"}
Error: Loading release id failed: A problem occured while extracting your app. (Correlation ID: 9713b68c-28a9-40e1-9c9e-20b919c3e549)

Maybe the API documentation could be updated. You know, the first link you get when you google "appcenter rest api" :) That API was never marked as depreciated.

I get the release uploaded after I created a new api token and used it in our pipeline. Previously I got the 410 response with deprecated API.

To best assist the App Center team, I've created a mockup for them for https://openapi.appcenter.ms, which they may use freely:

We're using Octopus for our uploads/deploys, with an agent on one of our own bare metal Macs.
We've upgraded appcenter-cli to 2.7.3 on the Mac and have not changed anything else in our scripts (including the token).
Deploys are now working again for us.

@kawazoe Thanks for the hint, I updated my Azure DevOps instance. To version 17.153.29522.3, patch 6. But my AppCenter task is still low 3.154.1 and I am still getting the error, Is there a way how to update only the task?

I have same issue as @Symorp
How to update the task? I am running 3.154.1.
The task only gives these settings and cant manually replace the star with a specific version:

Something is still not right. I upgraded to 2.7.3 and if i do appcenter help distribute release it says "Command distribute release is invalid" which indicates there are more problem. Can anybody confirm that you can issue distribute in the new cli version 2.7.3 ?

it's appcenter distribute release --help

it's appcenter distribute release --help

Still doesn't work for me :
I get Command distribute release --help is invalid

jenkins@mac-mini ~ % appcenter --version
appcenter version 2.7.3
jenkins@mac-mini ~ % appcenter distribute release --help

Upload release binary and trigger distribution, at least one of --store or --group must be specified

Usage: appcenter distribute release -f|--file <arg> [--mandatory] [--silent]
         [-R|--release-notes-file <arg>] [-r|--release-notes <arg>]
         [-s|--store <arg>] [-g|--group <arg>] [-n|--build-number <arg>]
         [-b|--build-version <arg>] [-a|--app <arg>]

Options:
    -f|--file <arg>                           Path to binary file
       --mandatory                            Make the release mandatory for
                                              the testers (default is false)
       --silent                               Do not notify testers of this
                                              release
    -R|--release-notes-file <arg>             Path to release notes file
    -r|--release-notes <arg>                  Release notes text
    -s|--store <arg>                          Store name
    -g|--group <arg>                          Distribution group name
    -n|--build-number <arg>                   Build number parameter required
                                              for macOS .pkg and .dmg files
    -b|--build-version <arg>                  Build version parameter required
                                              for .zip, .msi, .pkg and .dmg
                                              files
    -a|--app <arg>                            Specify app in the
                                              <ownerName>/<appName> format

Common Options (works on all commands):
       --disable-telemetry             Disable telemetry for this command
    -v|--version                       Display appcenter version
       --quiet                         Auto-confirm any prompts without
                                       waiting for input
    -h|--help                          Display help for current command
       --env <arg>                     Environment when using API token
       --token <arg>                   API token
       --output <arg>                  Output format: json
       --debug                         Display extra output for debugging

Works fine here check your version, maybe?

@IoannisFMG weird, i do run 2.7.3 and tried on two mac mini machines and same result. if i do appcenter distribute release i get Command distribute release is invalid.

Maybe there is something missing somewhere ?

@donnib - can you post your command line here?

➜  ~ appcenter distribute release
Error: Command distribute release is invalid
➜  ~ appcenter --version
appcenter version 2.7.3
➜  ~ appcenter distribute release --help
Error: Command distribute release --help is invalid
➜  ~

hi everyone.
i tried looking through the code to figure out the new api call that replaces /v0.1/apps/{owerner}/{app_name}/release_uploads but i cannot figure it out. any ideas?
we are using a powershell script that does the upload. it does more or less the same thing as the app-center-cli, but at the moment is failing with "deprecated API" and refers to this repo.

For us who don't use the appcenter tool, what's network commands to push a distribution?
POST here-and-there
PATCH another-url-and-params
that would be awesome.
Help, @pcohensc?

@donnib What node version are you running? This issue and this one indicate you need node 10.
Not running node 10 gives a 'command xxx is invalid' error it seems.

Still running into this on Android after updating the distribute version to 4.0.0 as suggested here. https://docs.microsoft.com/en-us/appcenter/sdk/distribute/android

For us who don't use the appcenter tool, what's network commands to push a distribution?
POST here-and-there
PATCH another-url-and-params
that would be awesome.
Help, @pcohensc?

Did you look at the apis here? https://openapi.appcenter.ms/#/build/builds_distribute

@airthings-noordawod https://openapi.appcenter.ms/#/build/builds_distribute Did you look at the apis here?

@airthings-noordawod I was not able to figure out their new uploads API without just giving up and using their CLI.
It looks much more complicated than the old one: https://github.com/microsoft/appcenter-cli/blob/master/appcenter-file-upload-client-node/src/ac-fus-uploader.ts

@airthings-noordawod I was not able to figure out their new uploads API without just giving up and using their CLI.
It looks much more complicated than the old one: https://github.com/microsoft/appcenter-cli/blob/master/appcenter-file-upload-client-node/src/ac-fus-uploader.ts

Well duhh. Hence my question... Why not just have a simple 1, 2, 3 steps so others can use what they want to publish an artifact? curl anyone?

Ok, if anyone is interested to using a simple mechanism to publish an asset to appcenter, instead of deploying nodejs (duhh) to all nodes, here's a 1, 2, 3 steps to do it:
https://github.com/microsoft/appcenter/issues/2069#issuecomment-740654621
Microsoft: when you make a change that affects thousands, will you WRITE IT IN BIG LETTERS and well ahead of time, please? Thank you.

Also, here's a link to a bash script that someone concucted that implements the new API: https://gist.github.com/ouchadam/c74fa26c639a50d68bc35ee5749f868c

Looks like Microsoft is going to be re-enabling the disabled endpoints until Feb 1st, 2021 to help with the transition. They also mentioned that they'll create documentation for these new endpoints for those unable to use appcenter-cli:
https://status.appcenter.ms/incidents/7930rkfgtg1y

@jameslavery thank you that solved my problem.

Here are the updated API steps:
https://docs.microsoft.com/en-us/appcenter/distribution/uploading#upload-new-release

Here are the updated API steps:
https://docs.microsoft.com/en-us/appcenter/distribution/uploading#upload-new-release

Here are the updated API steps:
https://docs.microsoft.com/en-us/appcenter/distribution/uploading#upload-new-release

The person who made those steps never really tried to use them... better to use https://github.com/microsoft/appcenter-Xamarin.UITest-Demo/blob/main/ac-distribute.sh this as a guide

I'm experience this issue at the moment.
Release upload failed Error: Command 'distribute release -f Runner.ipa --group Testers --app <redacted>' failed with exception "undefined"
appcenter cli version 2.10.6

I'm experience this issue at the moment.
Release upload failed Error: Command 'distribute release -f Runner.ipa --group Testers --app <redacted>' failed with exception "undefined"
appcenter cli version 2.10.6

Me, too. I thougth it was my outdate version 2.8.1, but upgrading it via npm also takes a lot of time.

Not sure if this is related, but we also started getting upload error from yesterday. First upload in the morning was successful, but later that day this error appeared on the next upload:
$ appcenter --version
appcenter version 2.7.3

$ appcenter distribute release -f ./some.ipa -g some-group --app some-application -r "Some comment" --token API-TOKEN-HERE --quiet --silent

Release upload failed
  (node:99868) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'release_distinct_id' of undefined
      at ReleaseBinaryCommand.<anonymous> (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:360:48)
      at Generator.throw (<anonymous>)
      at rejected (/usr/local/lib/node_modules/appcenter-cli/dist/commands/distribute/release.js:12:65)
      at processTicksAndRejections (internal/process/task_queues.js:86:5)
  (node:99868) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  (node:99868) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  Error: Loading release id failed with error: failed to get release id for upload id: ID-HERE, error: {"succeeded":false,"errorCode":3,"errorMessage":"failed to get release id with HTTP status: 504 - Gateway Time-out"}

Seems to be a gateway timeout, according to that last error message.

Same for me

Have a look at https://status.appcenter.ms and you shall see they are experiencing problems

Have a look at https://status.appcenter.ms and you shall see they are experiencing problems

The site states that everything is operational again, but I still get that same "undefined" error.

Hello guys. I'm getting the same issue for several hours already. It happens like 1/3 of all uploads
Cannot read property 'release_distinct_id' of undefined

Sorry for the inconvenience, we will update the status page once the issue is resolved.

I am sorry to reopen the thread, but Uploading to AppCenter is not working.
I am getting
The remote server returned an error: (429) Too Many Requests.
Status page is all green

I am sorry to reopen the thread, but Uploading to AppCenter is not working. I am getting The remote server returned an error: (429) Too Many Requests. Status page is all green

Same here, many requests fail, after few retries they work, but still pretty bad experience

Hi, @narciszait and @PGHM ! Please follow our status page for any updates.

Closing this issue. Please let me know if anyone is still facing it.


feat: add docker registry

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Subsetting: Categorical variable filters with very many values - check-all button only works for visible page when another filter is on

Example UMSP -> Health Center -> District in Uganda
First set another filter on Clinic Visit -> Malaria diagnosis

Now in Health Center -> District in Uganda
Clicking on the top-left checkbox

Only selects districts A-K (actually 0 to K)
Also clicking on this again doesn't deselect anything.
When no other filter is active, "check all" box works as you would expect (districts A-Z)

Related issue #1412

Currently waiting for USMP to be reloaded so that I can QA

Hi Steph, you can QA with GEMS1 and the first variable that comes up when
you search for "reason".
On Thu, Nov 3, 2022 at 3:04 PM Steph Schulman @.***>
wrote:

Currently waiting for USMP to be reloaded so that I can QA
—
Reply to this email directly, view it on GitHub
https://github.com/VEuPathDB/web-eda/issues/1170#issuecomment-1302250034,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLLH6GTWK6KU5EHXLOI3TWGPIBFANCNFSM5XZ7EHNA
.
You are receiving this because you authored the thread.Message ID:
@.***>

In GEMS1 Case Control Study, variable: "Reason not evaluated after rehydration" if search within those variables for a term "baby" and select all. It only selects those terms that are found in the search. I do believe this confirms the correct functionality.
@bobular mind confirming that above is correct.

In GEMS1 Case Control Study, variable: "Reason not evaluated after rehydration" if search within those variables for a term "baby" and select all. It only selects those terms that are found in the search. I do believe this confirms the correct functionality.
@bobular mind confirming that above is correct.

Yes, that's correct. Thank you!


Read default version to go.mod version if present

It would nice if the default version could be discovered from the repo's go.mod version if present in the same vane as go-version-file for action/setup-go
steps:
  - uses: actions/checkout@v2
  # Installs version 1.26.0
  - uses<EMAIL_ADDRESS>    with:
      go-version-file: go.mod

Hi @stevenh , the new buf-action is intended to address many of the issues with the previous set of actions. This feature however isn't currently supported. Please see the version docs for supported configs. Closing for now.