ValueError: setting an array element with a sequence.

💡 Your Question
Hey everyone. I am running into the kind of error that makes me wonder if I should stop coding and apply to McDonald's. I am unable to run a simple object detection using Yolo Nas or pose estimation using Yolo Nas Pose on a simple Image.
What I find extremely bizzare is that I have successfully used YoloNas Pose with a video from which this image was obtained, and I have also been able to use it on this same image in the past without errors! As far as I am concerned, my environment has not changed.
My code, corresponding image, and terminal output are below:
import cv2
import sys
import numpy as np
import torch
import os
import pathlib
import re

from super_gradients.training import models
from super_gradients.common.object_names import Models

img_input_file = "../Swings/Back/Pro/Rory/RoryScreenshot.png"

yolo_nas = models.get("yolo_nas_s", pretrained_weights="coco").to("cpu")

yolo_nas.predict(img_input_file, conf=0.25).show()

The terminal output is as follows:
(python3.9-env) deisi@MacBook-Air-3 Scripts % python3.9 ImgYOLONAS.py
The console stream is logged into /Users/deisi/sg_logs/console.log
[2023-12-12 19:51:24] INFO - crash_tips_setup.py - Crash tips is enabled. You can set your environment variable to CRASH_HANDLER=FALSE to disable it
[2023-12-12 19:51:24] WARNING - init.py - Failed to import pytorch_quantization
[2023-12-12 19:51:24,356] torch.distributed.elastic.multiprocessing.redirects: [WARNING] NOTE: Redirects are currently not supported in Windows or MacOs.
[2023-12-12 19:51:25] WARNING - calibrator.py - Failed to import pytorch_quantization
[2023-12-12 19:51:25] WARNING - export.py - Failed to import pytorch_quantization
[2023-12-12 19:51:25] WARNING - selective_quantization_utils.py - Failed to import pytorch_quantization
[2023-12-12 19:51:25] WARNING - env_sanity_check.py - Failed to verify operating system: Deci officially supports only Linux kernels. Some features may not work as expected.
[2023-12-12 19:51:26] INFO - checkpoint_utils.py - License Notification: YOLO-NAS-POSE pre-trained weights are subjected to the specific license terms and conditions detailed in
https://github.com/Deci-AI/super-gradients/blob/master/LICENSE.YOLONAS-POSE.md
By downloading the pre-trained weight files you agree to comply with these terms.
[2023-12-12 19:51:26] INFO - checkpoint_utils.py - Successfully loaded pretrained weights for architecture yolo_nas_pose_l
Traceback (most recent call last):
File "/Users/deisi/Documents/Condor/Scripts/ImgYOLONAS.py", line 33, in
prediction = yolo_nas_pose.predict(img, conf=0.75)
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/models/pose_estimation_models/yolo_nas_pose/yolo_nas_pose_variants.py", line 168, in predict
return pipeline(images, batch_size=batch_size)  # type: ignore
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/pipelines/pipelines.py", line 111, in call
return self.predict_images(inputs, batch_size)
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/pipelines/pipelines.py", line 127, in predict_images
return self._combine_image_prediction_to_images(result_generator, n_images=len(images))
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/pipelines/pipelines.py", line 386, in _combine_image_prediction_to_images
images_predictions = [next(iter(images_predictions))]
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/pipelines/pipelines.py", line 165, in _generate_prediction_result
yield from self._generate_prediction_result_single_batch(batch_images)
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/pipelines/pipelines.py", line 187, in _generate_prediction_result_single_batch
preprocessed_image, processing_metadata = self.image_processor.preprocess_image(image=image.copy())
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/processing/processing.py", line 99, in preprocess_image
processed_image, metadata = processing.preprocess_image(image=processed_image)
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/processing/processing.py", line 296, in preprocess_image
processed_image = _pad_image(image=image, padding_coordinates=padding_coordinates, pad_value=self.pad_value)
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/super_gradients/training/transforms/utils.py", line 151, in _pad_image
return np.pad(image, pad_width=padding_values, mode="constant", constant_values=constant_values)
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/numpy/lib/arraypad.py", line 805, in pad
values = _as_pairs(values, padded.ndim)
File "/Users/deisi/anaconda3/envs/python3.9-env/lib/python3.9/site-packages/numpy/lib/arraypad.py", line 491, in _as_pairs
x = np.array(x)
ValueError: setting an array element with a sequence. The requested array has an inhomogeneous shape after 2 dimensions. The detected shape was (3, 2) + inhomogeneous part.
Any guidance would be much appreciated!
Versions
No response

Maybe not all that bad after all and applying to Macas is a bit too harsh move ;)

What SG are you using?
Can you load a checkpoint you have (checkpoint = torch.load(...)) and print the entire content of checkpoint["processing_params"] ?

Something seems to be off with the paddings values in image preprocessing

Maybe it's not that bad after all and applying to Macas is a bit too harsh move ;)

What SG are you using?
Can you load a checkpoint you have (checkpoint = torch.load(...)) and print the entire content of checkpoint["processing_params"] ?

Something seems to be off with the paddings values in image preprocessing

Hey, I appreciate the fast response.
It turns out that it was an issue with the Numpy version. For some reason, when running pip list, and numpy.version the shown version was 1.23. However, for some reason version 1.26 was conflicting.
after uninstalling Numpy and installing it again, the problem was fixed.

So what numpy version was causing issues originally! 1.26?

Yes. Version 1.26 was getting involved for some reason that I don't understand. Bizarre, as when running pip list, and numpy.version the shown version was 1.23. My guess is that it got installed while installing another package that had a numpy dependency, or some other installation issue.


Fair Playoff Codeforces Solution

Description
Added solution to Codeforces question 'Fair Playoff'.
Fixes #2072 (
Type of change
Added solution to problem "Fair Playoff" in Codeforces Folder in C++ language.
Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

@ravikr126 Kindly review my PR under LGM SOC '21.


Whether carla can run in python 32 environment

Recently I built some .so files in 32-bit architecture, so change my python environment to python 32.
Then carla report this error: "/home/user/.cache/Python-Eggs/carla-0.9.11-py3.7-linux-x86_64.egg-tmp/carla/libcarla.cpython-37m-x86_64-linux-gnu.so: wrong ELF class: ELFCLASS64"
Whether carla can run in python 32 environment?

You're clearly building it for x86_64. That's not 32 bit. I don't know if CARLA can run on 32-bit architecture, but for sure we aren't really prepared to run on 32-bit. You'll probably need to change quite a few things, starting from generating an .egg compatible with 32-bit architecture.


Benchmark submission: Samsung SSD 980 PRO 1TB

This issue had missing benchmark json result file so this issue is invalid.  Please create fresh submission of benchmarks


Request: One-time donation option

There has been a request for an option to make a one-time donation to Free Code Camp via https://www.freecodecamp.com/donate/ rather than a recurring payment.  If it's not too logistically difficult, I also think this is a good idea.

Issue moved to freeCodeCamp/shop #2 via ZenHub


Add support for Cloudfront user principal

It seems is not possible to parse a valid Resource Policy on a S3 bucket, such as
{
    "Version": "2012-10-17",
    "Id": "PolicyForCloudFront",
    "Statement": [
        {
            "Sid": "1",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::cloudfront:user/some-cloud-front-user"
            },
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::bucket/*"
        }
    ]
}

using PolicyDocument.fromJson, because an 'Unsupported AWS principal value "arn:aws:iam::cloudfront:user/some-cloud-front-user"' Error is thrown

Alright, this is interesting. Thank you for reporting that!
I'll have a look at this.

I've created this PR for it
https://github.com/thinkinglabs/aws-iam-policy/pull/25


Error: Cannot find module './lib/parse-js'

On a fresh install on my raspberry pi, I pulled the latest master, ran npm install -l in the steward/steward directory, waited for it to complete, rebooted the pi, noted that the steward did not automatically start, so I went back to the steward/steward directory and attempted to start it manually:
$ sudo ./run.sh
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
info: running on Linux Debian 7.2 ( 3.10.25+ armv6l)
info: using node v0.10.22
info: [devices] loading climate driver
debug: [climate] begin
info: [devices] loading gateway driver
info: [devices] loading indicator driver
info: [devices] loading lighting driver
info: [devices] loading media driver
debug: [media] begin
info: [devices] loading motive driver
debug: [motive] begin
info: [devices] loading presence driver
info: [devices] loading sensor driver
info: [devices] loading switch driver
info: [devices] loading wearable driver
debug: [wearable] begin
info: [climate] loading cubesensors-meteo driver
info: [climate] loading ecobee-control driver
info: [climate] loading flower-power-sensor driver
info: [climate] loading insteon-control driver
info: [climate] loading koubachi-sensor driver
info: [climate] loading nest-control driver
info: [climate] loading netatmo-sensor driver
info: [climate] loading oregon-scientific-sensor driver
info: [climate] loading plantlink-sensor driver
info: [climate] loading samsung-control driver
info: [discovery] listening network_interface=eth0, ipaddr=<IP_ADDRESS>, portno=1900
info: [climate] loading teldus-meteo driver
info: [climate] loading wink-control driver
info: [climate] loading yoctopuce-meteo driver
info: [discovery] SSDP listening on http://<IP_ADDRESS>:1900
info: [discovery] multicasting network_interface=eth0, ipaddr=<IP_ADDRESS>, portno=1900
info: [gateway] loading automatic-cloud gateway
info: [gateway] loading cubesensors-cloud gateway
info: [gateway] loading ecobee-cloud gateway
info: [devices] failing ecobee-cloud gateway (continuing) diagnostic=Cannot find module 'ecobee-api'
info: [gateway] loading flower-power-cloud gateway
info: [gateway] loading insteon-automategreen gateway
info: [gateway] loading koubachi-cloud gateway
info: [gateway] loading lockitron-cloud gateway
info: [gateway] loading myq-cloud gateway
info: [gateway] loading nest-cloud gateway
info: [gateway] loading netatmo-cloud gateway
info: [gateway] loading openzwave-usb gateway
info: [gateway] loading plantlink-cloud gateway
info: [gateway] loading reelyactive-reel gateway
info: [gateway] loading rfxcom-usb gateway
info: [gateway] loading telldus-live-cloud gateway
info: [gateway] loading tesla-cloud gateway
info: [gateway] loading wink-cloud gateway
info: [gateway] loading yoctopuce-hub gateway
info: [gateway] loading zigbee-xstick gateway
info: [indicator] loading cassandra-sensor driver
info: [indicator] loading dweetio-sensor driver
alert: [steward] exception diagnostic=Cannot find module './lib/parse-js'
alert: [steward] exception stack=[{"fileName":"module.js","lineNumber":338,"functionName":"Function.Module._resolveFilename","typeName":"Function","methodName":"Module._resolveFilename","columnNumber":15,"native":false},{"fileName":"module.js","lineNumber":280,"functionName":"Function.Module._load","typeName":"Function","methodName":"Module._load","columnNumber":25,"native":false},{"fileName":"module.js","lineNumber":364,"functionName":"Module.require","typeName":"Module","methodName":"require","columnNumber":17,"native":false},{"fileName":"module.js","lineNumber":380,"functionName":"require","typeName":"Object","methodName":null,"columnNumber":17,"native":false},{"fileName":"/home/pi/steward/steward/node_modules/node-dweetio/node_modules/socket.io-client/node_modules/uglify-js/uglify-js.js","lineNumber":14,"functionName":"","typeName":"Object","methodName":null,"columnNumber":17,"native":false},{"fileName":"module.js","lineNumber":456,"functionName":"Module._compile","typeName":"Module","methodName":"_compile","columnNumber":26,"native":false},{"fileName":"module.js","lineNumber":474,"functionName":"Object.Module._extensions..js","typeName":"Object","methodName":"Module._extensions..js","columnNumber":10,"native":false},{"fileName":"module.js","lineNumber":356,"functionName":"Module.load","typeName":"Module","methodName":"load","columnNumber":32,"native":false},{"fileName":"module.js","lineNumber":312,"functionName":"Function.Module._load","typeName":"Function","methodName":"Module._load","columnNumber":12,"native":false},{"fileName":"module.js","lineNumber":364,"functionName":"Module.require","typeName":"Module","methodName":"require","columnNumber":17,"native":false}]
uncaught exception: Error: Cannot find module './lib/parse-js'
Press ^C to exit or wait 10 seconds to restart

@mrmakeit any thoughts about the missing module?

Can you try deleting the node_modules folder inside steward/steward and rerun npm install -l

Thanks, that fixed it.


Simplified "Why this question matters" for all questions

Description
Simplified "Why this question matters" for all questions.
Motivation and Context

Changed after discussion on simplifying the phrasing.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Rendered locally and everything seems to work ok, with no changes to line breaks or structure.
Advice for reviewer

Only made changes to the phrasing in quality_questions.qmd and any other changes to files are due to quarto rendering.

Merged following conflict resolution


INTERNAL ERROR: Black produced different code on the second pass of the formatter.

Hi there!
Looks like black is having trouble with this bit of code.
See details linked below:
Operating system: Reproducible on Windows and Ubuntu
Python version: 3.6.8
Black version: black==19.3b0
Does it also happen on master: Yes
Output:
$ black -l 100 ./ error: cannot format C:\Users\knakad\workspace\SageMakerPythonSDK\src\sagemakerpythonsdk\src\sagemaker\rl\estimator.py : INTERNAL ERROR: Black produced different code on the second pass of the formatter.  Please report a bug on https://github.com/ambv/black/issues.  This diff might be helpful: C:\Users\knakad\AppData\Local\Temp\blk_epnkfdbs.log All done! � � � 223 files left unchanged, 1 file failed to reformat.
blk_epnkfdbs.log

FYI, no rush on this issue. I fixed the underlying problem.
I wanted to report it in case others run into it and are unable to resolve the underlying problem.

Are you sure this is still broken on master? #872 is supposed to fix this kind of issue

I can't repro on master. If you still can, feel free to reopen with an example that fails.


Menu view helper: Can't set class on li and a elements

when working with bootsrap4 it is not enough to set class on ul element. Maybe add methods like setULClass for li and a?

You can add the classes to the li element instead of the a element or you can use a partial script. The last option should help you.
At the moment we will not add more methods to the view helper, because we will rework and simplify the whole rendering of the helpers.

@francisdaigle yes I could but look https://getbootstrap.com/docs/4.0/components/navbar/#supported-content

        Home

all ul, li and a has to have a custom class and if I change from a to li this still not help.
And yes I can use a partial script(that's what I do now), but that's annoying because I have to manage active page acl and everything myself I haven't tested yet other helpers but they may have problems as well

@froschdesign when this could happen I guess not any time soon?

@svycka
I know the Bootstrap "Navbar" and all the classes.

…I haven't tested yet other helpers but they may have problems as well

Please keep in mind zend-navigation was developed and released before Bootstrap or Foundation had a first release.

…but that's annoying because I have to manage active page acl…

It's very simple.

when this could happen I guess not any time soon?

Why are you so pessimistic? We are already working on it! (zend-expressive support first, then the rework of the view helpers)
In the meantime, I would extend the view helper, then you do not need a partial script.

I am not pessimistic just know that zend-* has a lot of projects and only a few people to work on them.

This repository has been closed and moved to laminas/laminas-navigation; a new issue has been opened at https://github.com/laminas/laminas-navigation/issues/1.


cursorline not working on Windows and via SSH

Description of the problem or steps to reproduce
cursor line not highlighted  on Windows and via SSH
I tried the default but also 16 color schemes like solarized. Only simple and cmc-16 partially "work". The line is not highlighted but the column with the line number is shown in a different color.
Specifications
1.4.2-dev.77
Commit hash: 3a8898d
Compiled on July 27, 2019
OS:  Windows 10
Terminal: ConEmu
Terminal: PuTTY (SSH to Linux)

try https://www.fosshub.com/KiTTY.html


720p and 1080p after file name

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.12.14. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.12.14

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[ x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2017.12.14
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
So, i am downloading some files from the web and i download 720p and 1080p, so i wanted to know, how can i automatically write 720p after the file name? Like "TEST VIDEO-C0DPdy98e4c" should be "TEST VIDEO-C0DPdy98e4c720"

https://github.com/rg3/youtube-dl#output-template


Remove port_forwarders from pach config if port-forward process is dead

This PR fixes a corner-case with pachctl port-forward. Basically, if the port-forward process is killed by anything other than sigint, it never gets the opportunity to remove the port_forwarders section of the pach config. As long as port_forwarders is present, pachctl will attempt to connect to localhost:<port-forward port> instead of initiating internal port forwarding, so if pachct port-forward is killed by e.g. sighup (because the shell it was running in was closed, e.g. because the CircleCI step it was running in completed) then pachctl becomes unable to connect to pachd—it tries to connect to localhost:<port-forward port> in perpetuity, even though no process is running to receive its requests. This bug, in turn, makes e.g. kube_debug.sh not work if pachctl port-forward is run in any prior CircleCI step, unless the pach config is explicitly cleared.
With this change, the pid of pachctl port-forward is stored in the pach config, and pachctl checks, on startup, that that process is alive and corresponds to a pachctl process. This means that if pachctl port-forward is killed, the next invocation of pachctl (or, actually, the next invocation of NewOnUserMachine()) will remove the obsolete port_forwarders block from the config. Downstream bugs with CircleCI and kube_debug.sh are fixed as well.

Just wanted to update this PR to say thatbI haven't forgotten about it, it's stuck on a nil dereference bug in CI. I probably won't be able to bathe it for another week and a half or so due to the 2.1.x code freeze, but my plan is to merge it once that's over


Check URL Error Message

I'm using timidity with a Python program to compose MIDI data (Abjad). The timidity playback is fine, except that I get this error message in the terminal every time a file is compiled:
Check URL type=7 Check URL type=2 Check URL type=1 open url (type=1, name=/usr/local/Cellar/timidity/2.15.0/share/timidity/timidity.cfg) url_file_open(/usr/local/Cellar/timidity/2.15.0/share/timidity/timidity.cfg) mmap - success. size=4625
Would you happen to have any suggestions on how to make the error message go away? Do I need to configure the .cfg file? Speaking of which, how to access the .cfg file on a Mac?
Thank you!

This repo is for a JavaScript version of timidity. I think you'll want to find the right repo to file this issue:
$ brew info timidity
timidity: stable 2.15.0 (bottled)
Software synthesizer
https://timidity.sourceforge.io/
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/timidity.rb


Fix design for buttons which do bad things

cf45f367202a2e3bcaa99dcf86feef3863e30478 added a button-danger, but the style could be improved. @lilliputten please make this look a bit nicer.

Fixed in PR #97.
See buttons and icons samples in demo:

In real pages (actual state):


File download ignoring "url" property (if present) on file entries?

In ContextMenu.vue:
download: {
    title: () =>  t('Download'),
    action: () => {
      const url = apiUrl.value + '?' + buildURLQuery({q:'download', adapter: props.current.adapter, path: selectedItems.value[0].path});
      emitter.emit('vf-download', url);
    },
  },

But some file entries might have a "url" property and it seems to me that this property should be used as the url to pass to vf-download.  An adapter on the server side like S3 might be returning pre-signed S3 urls for files, right?  Your vuefinder-php backend is:
$config = [
    'publicLinks' => [
        'local://public' => 'http://example.test',
    ],
];

and for files in the public folder, the url property is set to http://example.test/...  but the vuefinder component is not downloading from this location, its calling APIURL?q=download instead.
Is this an oversite, or am I doing something wrong?  In my use case, my backend is a lot like S3 and will return "url" properties for files, and I need the client to download from those urls.

You are right. That's something we missed. Downloading must be from those links.

solved


Violin plots fail when called with empty array

The following code fails using commit bc98686677dde12dd6ba6987b8d753fdb7692c5c (a few commits upstream of when plot-violin was merged into develop):
>>> FlowCal.plot.violin(data=[])

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\sexto\.conda\envs\py3_anaconda2020.07_fc_JS3xton_bc98686\lib\site-packages\flowcal-1.2.2-py3.8.egg\FlowCal\plot.py", line 1690, in violin
StopIteration

The error occurs when next() is called on an empty iterator when trying to understand data:
    # understand `data`
    if channel is None:
        # assume 1D sequence or sequence of 1D sequences
        try:
            first_element = next(iter(data))  # <-- fails here
        except TypeError:
            msg  = "`data` should be 1D array or list of 1D arrays."
            msg += " Specify `channel` to use ND array or list of ND"
            msg += " arrays."
            raise TypeError(msg)

        # promote singleton if necessary
        try:
            iter(first_element)  # success => sequence of 1D sequences
            data_length = len(data)
        except TypeError:
            data = [data]
            data_length = 1

Fixed in FlowCal v1.3.0.

Fixed in FlowCal v1.3.0.

FlowCal.plot.violin(data=[]) still fails in v1.3.0 with the following error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/jsexton/Downloads/FlowCal-master/FlowCal/plot.py", line 1810, in violin
    t = _LogicleTransform(data=data, channel=channel)
  File "/home/jsexton/Downloads/FlowCal-master/FlowCal/plot.py", line 315, in __init__
    raise ValueError("T should be positive")
ValueError: T should be positive


Remove uml (until an update)

Proposed Changes:
Removing UML, hopefully temporarily, for RC-1, as no one is able to update it in short order. @hgs-msmith - if you can update the UML and put a PR that would be great. We'll likely do RC1 in the next day or two, but then will have a couple weeks to get this in for 0.8.0
PR Checklist:

[x] This PR has no breaking changes.
[x] I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.
[ ] API only: I have run npm run generate-all to update the generated OpenAPI files.

Chris,
I will find some time to update the diagram this week.
Michael Smith
Advanced Program Engineer
space and AIRBORNE systems / L3HARRIS TECHNOLOGIES
Office: +1-303-402-4667
L3Harris.com / Michael.M.Smith<EMAIL_ADDRESS>385 Interlocken Crescent, Suite 300 / Broomfield, Colorado 80021 / USA
<EMAIL_ADDRESS>From: Chris Holmes<EMAIL_ADDRESS>Sent: Tuesday, August 20, 2019 9:19 AM
To: radiantearth/stac-spec<EMAIL_ADDRESS>Cc: Smith, Michael (asmith65) (US<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [Marketing] [radiantearth/stac-spec] Remove uml (#565)
Proposed Changes:
Removing UML, hopefully temporarily, for RC-1, as no one is able to update it in short order. @hgs-msmithhttps://github.com/hgs-msmith - if you can update the UML and put a PR that would be great. We'll likely do RC1 in the next day or two, but then will have a couple weeks to get this in for 0.8.0
PR Checklist:

[X] This PR has no breaking changes.
[X] I have added my changes to the CHANGELOGhttps://github.com/radiantearth/stac-spec/blob/dev/CHANGELOG.md or a CHANGELOG entry is not required.
[ ] API only: I have run npm run generate-all to update the generated OpenAPI fileshttps://github.com/radiantearth/stac-spec/blob/dev/api-spec/README.md#openapi-definitions.

You can view, comment on, or merge this pull request online at:
https://github.com/radiantearth/stac-spec/pull/565
Commit Summary

add foreign members description, add ItemCollection description
fix merge error
Merge pull request #481 from philvarner/extension/training_data_sprint_4
add itemcollection description
reference ItemCollection documention-to-be
add API Spec description of POST implementation
readd Item after accidental removal
fixed typo; added explicit requirement for intersects to support all geometry types
Merge branch 'dev' into example-fix
Merge pull request #476 from joshfix/example-fix
removed single-item extension to resolve conflict
Merge branch 'dev' into json-schema-fixes-for-validator
Merge pull request #478 from radiantearth/json-schema-fixes-for-validator
Merge branch 'dev' into extension-search
Merge branch 'dev' into pv/itemcollection
Merge branch 'dev' into api-stac-search-post
re-add example
change top-level ItemCollection search:meta field to Properties fields prefixed with search
add Properties to ItemCollection
minor corrections
remove identical statement
Revert "change top-level ItemCollection search:meta field to Properties fields prefixed with search"
make it clear that this is a root attribute of ItemCollection
fix WFS 3 Collections link
Updated schemas in README
Added example and schema link to be consistent with other extensions
Removed properties
There's no single item extension any longer.
Update schema.json
Clarifications
limit: number => integer
global vs local NPM package install; fixing typos
update limit description
Update schema.json
update doc with number->integer
fixed fields api extension example
Changed key name from id to name to match eo extension
Merge branch 'dev' into fix-eo-bands-examples
Merge pull request #494 from kbgg/fix-eo-bands-examples
Merge branch 'dev' into extension/training_data
fix API Query Extension OpenAPI spec examples, remove time predicate
Merge branch 'dev' into api-document
Merge branch 'dev' into extension-search
Merge branch 'dev' into pv/itemcollection
Merge pull request #467 from fredliporace/api-document
integrate itemcollection spec into item spec
Merge branch 'dev' into fields-example-fix
remove ItemCollection properties
Merge branch 'dev' into pv/itemcollection
Merge branch 'dev' into api-stac-search-post
Merge pull request #493 from joshfix/fields-example-fix
Merge branch 'dev' into extension-search
move search extension into api extensions
Merge branch 'extension-search' of github.com:philvarner/stac-spec into extension-search
Merge branch 'dev' into extension/training_data
cleaning up examples and removing label:version
Merge pull request #502 from nrweir/extension/label_nw
Changes for consistency with other extension specs.
Fixed examples and applied formatting.
fix links to ItemCollection
prevent POST JSON for WFS 3 endpoints, clarify transaction API behavior
Merge branch 'dev' into api-stac-search-post
fix ItemCollection link
add Item and ItemCollection sections
re add warning
Merge pull request #489 from philvarner/api-stac-search-post
Merge branch 'dev' into extension/training_data
changing class_name and stat_name to name
Applied changes again that got reverted by the previous commit.
update api spec STAC.yaml via generate-all
Transaction Extension Status Codes are more REST conventional
add 'in' operator over strings to query extension
Merge pull request #362 from radiantearth/extension/training_data
Update API Fields Extension with more precise semantics and behavior
Merge branch 'dev' into pv/itemcollection
fix description of flat vs. nested properties
Merge branch 'dev' into extension-search
split itemcollection into separate spec
revert changes to item spec
Merge branch 'dev' into query-extension-in-operator
Merge branch 'dev' into transaction-status-codes
Merge branch 'dev' into update-api-spec-STACyaml
Merge pull request #505 from philvarner/update-api-spec-STACyaml
Merge pull request #507 from philvarner/query-extension-in-operator
Merge branch 'dev' into extension-search
Merge pull request #482 from philvarner/extension-search
fix error response 503->500, add Location header upon POST (create)
use 5XX for error
Merge branch 'dev' into transaction-status-codes
Merge branch 'dev' into pv/itemcollection
Merge pull request #487 from philvarner/pv/itemcollection
Merge branch 'dev' into transaction-status-codes
Merge pull request #506 from philvarner/transaction-status-codes
fix cut-and-paste typo with GET/POST descriptions
Merge branch 'dev' into api-fields-extension-semantics
Merge pull request #508 from philvarner/api-fields-extension-semantics
Merge branch 'dev' into pv/fix-api-query-ext-time-and-examples
add WFS 3 /api endpoint to docs, and reformat some tables (#509)
Merge branch 'dev' into pv/fix-api-query-ext-time-and-examples
clarify meaning of GSD (#510)
Merge branch 'dev' into pv/fix-api-query-ext-time-and-examples
Merge pull request #495 from philvarner/pv/fix-api-query-ext-time-and-examples
make clear api should only have one of bbox or intersects
remove /api endpoint from WFS 3 description, as it is no longer required
Merge pull request #511 from philvarner/intersects-and-bbox
Clarify EO items platform, constellation, and instrument
Merge branch 'dev' into remove-api-endpoint
Merge pull request #514 from philvarner/remove-api-endpoint
Merge branch 'dev' into eo-clarifications
rename search extension found to matched per WFS3 terms (#515)
fix mismerge with query 'in' operator and 'time' operator
update eo:bands example to clarify index array over name
Merge pull request #518 from philvarner/fix-mismerge-with-query-in-operator-pr
Merge branch 'dev' into eo-example-clarification
Merge pull request #520 from philvarner/eo-example-clarification
Merge branch 'dev' into eo-clarifications
adding etag support to transactions
adding ETag header to patch and put responses
Updated WFS API specification to draft 2.
Updated API spec documentation.
Added reference to ISO8601 for periods. RFC3339 doesn't specify period strings.
Clarifications for/Fixes the API examples.
Updated Collection specification and fixed all collection examples.
Fixed WFS3 spec issue, aligned and cleaned up STAC API.
Updated to recent changes in the WFS repo.
There was a duplicate of the field schema in the PC extension.
Removed fields from Single Item extension (will be removed).
First draft of the summaries for catalogs.
Absolute links changed to relative in JSON schemas (#528) and clean-up.
Updated changelog.
Updated CHANGELOG
Fixed links and outdated information on APIs on the front-page of the repo.
Extension supported, first draft.
Fixed Label extension examples.
Re-generated STAC API files, which seem to be outdated.
Collections: Inherit JSON Schema from Catalog (partial fix for #533).
copy changes to SAR extension
Removed time parameter, focus on datetime parameter.
Fixed API link example as discussed with @philvarner.
Merge pull request #532 from radiantearth/misc-fixes
Merge branch 'dev' into feature/eTag
Merge branch 'dev' into wfs3-draft2
Added transaction extension to extension YAML and fixed rendering.
Regenerated YAML files to reflect latest changes.
Merge remote-tracking branch 'origin/add-transaction-to-extensions' into feature/eTag
Added YAML fragment for API search extension.
Added transaction extension to extension YAML and fixed rendering.
Merge branch 'dev' into eo-clarifications
update sar examples
Merge branch 'dev' into fix-api-links
Merge pull request #530 from radiantearth/fix-api-links
Merge branch 'dev' into eo-clarifications
add API reserved parameter language, clarification on the form of GET vs. POST JSON parameters
Merge branch 'dev' into yaml-for-search-extension
Merge branch 'dev' into feature/eTag
Merge pull request #538 from radiantearth/yaml-for-search-extension
Merge branch 'dev' into feature/eTag
Updated changelog
Merge branch 'dev' into eo-clarifications
Merge pull request #534 from radiantearth/feature/eTag
fix example with _LV1B
Merge branch 'dev' into eo-clarifications
Merge branch 'dev' into json-schema-paths-cleanup
Merge branch 'dev' into stac-extensions-field
Merge branch 'dev' into summaries
Merge remote-tracking branch 'origin/dev' into wfs3-draft2
Merge branch 'dev' into fix-pc-extension-schema
Merge pull request #526 from radiantearth/fix-pc-extension-schema
Merge branch 'dev' into reserved-parameter-language
Merge branch 'dev' into json-schema-paths-cleanup
Merge pull request #529 from radiantearth/json-schema-paths-cleanup
Merge branch 'dev' into wfs3-draft2
Merge branch 'dev' into eo-clarifications
Merge branch 'dev' into summaries
Merge branch 'dev' into stac-extensions-field
Merge branch 'dev' into reserved-parameter-language
Replaced /time with /datetime
changelog, or -> |
Merge pull request #525 from radiantearth/wfs3-draft2
Merge branch 'dev' into reserved-parameter-language
update value constraint recommendations
Merge branch 'dev' into eo-clarifications
Merge pull request #540 from philvarner/reserved-parameter-language
Merge branch 'dev' into eo-clarifications
update changelog
Merge branch 'eo-clarifications' of github.com:philvarner/stac-spec into eo-clarifications
Updated JSON Schema to have relative link.
Merge remote-tracking branch 'origin/dev' into stac-extensions-field
Merge remote-tracking branch 'origin/dev' into summaries
Moved range further down, fixed tables/typos, removed relative self links.
Explained summaries a bit more.
Added stac_version and stac_extensions to Items, changes definitions of stac_extensions in Catalogs and Collections, minor fixes in examples.
remove naming recommendations
Merge pull request #516 from philvarner/eo-clarifications
Merge branch 'dev' into stac-extensions-field
Merge branch 'dev' into summaries
Merge pull request #527 from radiantearth/summaries
Merge remote-tracking branch 'origin/dev' into stac-extensions-field
Merge pull request #531 from radiantearth/stac-extensions-field
moved best practices to root, so it can capture all best practices, not just catalog
edits to make this general for STAC, not catalog specific
Updated version numbers (#543)
added info on ids and fields
Merge branch 'dev' into stac-best-practices
Make license and providers consistent between Collection and Item (#544)
Fixed invalid example
Added links to chapters to improve navigation / UI (#541).
Merge pull request #549 from radiantearth/license-provider-issues
Merge branch 'dev' into version-numbers
Merge pull request #547 from radiantearth/version-numbers
Merge branch 'dev' into better-navigation
Merge branch 'dev' into better-navigation
Merge pull request #550 from radiantearth/better-navigation
Allow summaries to specify Stats (#542)
update common bands table
update changelog with new common band names
add single file STAC extension
update CHANGELOG with older commits
Merge branch 'dev' into common_band_names
common_band_names: small fixes
Merge branch 'common_band_names' of github.com:radiantearth/stac-spec into common_band_names
Merge branch 'dev' into stac-best-practices
Merge pull request #554 from radiantearth/common_band_names
Merge branch 'dev' into update_changelog
Merge pull request #559 from radiantearth/update_changelog
Fixed typo.
Merge branch 'dev' into stats-object
Merge pull request #551 from radiantearth/stats-object
Allow scientific extension in collections and other improvements.
Updated Changelog.
Fixed media type table (didn't render correctly) and added some wording around the evolving media type for GeoTiffs/COGs (#535).
Merge branch 'dev' into stac-best-practices
Merge pull request #562 from radiantearth/scientific-collections
Merge branch 'dev' into media-type-table
Merge pull request #563 from radiantearth/media-type-table
Issue #352: add z-axis to item spec for bbox and geometry
Add info about mixed version catalogs to best practices (#546)
Merge branch 'dev' into stac-best-practices
Fixed typo.
Merge pull request #548 from radiantearth/stac-best-practices
resolve merge
updated api and collection spec for consitency
Merge branch 'dev' into dev
single file stac - updated readmes
single-file-stac ext: update readme
single-file-stac: update changelog
Merge pull request #564 from joshfix/dev
Merge branch 'dev' into single_file_stac
Merge pull request #558 from radiantearth/single_file_stac
removing UMLs for 0.8.0-RC1 Release, as it is better to not have it there then an outdated one. Hopefully it will be updated for 0.8.0

File Changes

M .gitignorehttps://github.com/radiantearth/stac-spec/pull/565/files#diff-0 (2)
M CHANGELOG.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-1 (32)
M README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-2 (11)
D STAC-UML.drawiohttps://github.com/radiantearth/stac-spec/pull/565/files#diff-3 (1)
D STAC-UML.pdfhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-4 (0)
M api-spec/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-5 (18)
M api-spec/STAC-extensions.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-6 (1595)
M api-spec/STAC.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-7 (1387)
M api-spec/api-spec.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-8 (115)
M api-spec/examples.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-9 (102)
M api-spec/extensions/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-10 (7)
A api-spec/extensions/STAC-extensions.fragment.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-11 (3)
M api-spec/extensions/STAC-extensions.merge.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-12 (2)
M api-spec/extensions/fields/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-13 (97)
M api-spec/extensions/query/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-14 (18)
M api-spec/extensions/query/query.fragment.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-15 (18)
A api-spec/extensions/search/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-16 (45)
A api-spec/extensions/search/examples/example.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-17 (10)
A api-spec/extensions/search/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-18 (46)
A api-spec/extensions/search/search.fragment.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-19 (24)
M api-spec/extensions/transaction/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-20 (14)
M api-spec/extensions/transaction/transaction.fragment.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-21 (432)
M api-spec/openapi/STAC.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-22 (225)
M api-spec/openapi/WFS3.yamlhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-23 (1040)
R best-practices.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-24 (31)
M catalog-spec/catalog-spec.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-25 (96)
A catalog-spec/examples/basic.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-26 (11)
D catalog-spec/examples/catalog.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-27 (20)
A catalog-spec/examples/summaries-s2.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-28 (176)
M catalog-spec/json-schema/catalog.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-29 (123)
M collection-spec/collection-spec.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-30 (120)
M collection-spec/examples/landsat-collection.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-31 (250)
M collection-spec/examples/landsat-item.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-32 (5)
M collection-spec/examples/sentinel2.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-33 (127)
M collection-spec/json-schema/collection.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-34 (241)
M extensions/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-35 (27)
M extensions/checksum/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-36 (6)
R extensions/checksum/examples/example-sentinel1.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-37 (0)
R extensions/checksum/json-schema/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-38 (12)
M extensions/datacube/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-39 (4)
R extensions/datacube/examples/example.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-40 (5)
R extensions/datacube/json-schema/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-41 (17)
M extensions/datetime-range/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-42 (4)
R extensions/datetime-range/examples/example-video.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-43 (4)
A extensions/datetime-range/json-schema/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-44 (43)
D extensions/datetime-range/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-45 (27)
M extensions/eo/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-46 (106)
R extensions/eo/examples/example-landsat8.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-47 (9)
A extensions/eo/json-schema/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-48 (120)
D extensions/eo/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-49 (127)
A extensions/label/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-50 (163)
A extensions/label/examples/multidataset/catalog.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-51 (28)
A extensions/label/examples/multidataset/spacenet-buildings/AOI_2_Vegas_img2636.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-52 (1158)
A extensions/label/examples/multidataset/spacenet-buildings/AOI_3_Paris_img1648.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-53 (1562)
A extensions/label/examples/multidataset/spacenet-buildings/AOI_4_Shanghai_img3344.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-54 (742)
A extensions/label/examples/multidataset/spacenet-buildings/catalog.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-55 (72)
A extensions/label/examples/multidataset/zanzibar/catalog.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-56 (93)
A extensions/label/examples/multidataset/zanzibar/znz001.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-57 (167719)
A extensions/label/examples/multidataset/zanzibar/znz029.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-58 (48979)
A extensions/label/examples/spacenet-roads/roads_collection.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-59 (59)
A extensions/label/examples/spacenet-roads/roads_item.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-60 (146)
A extensions/label/examples/spacenet-roads/roads_source.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-61 (43)
A extensions/label/examples/spacenet-roads/spacenetroads_AOI_3_Paris_img101.geojsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-62 (25)
A extensions/label/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-63 (120)
M extensions/pointcloud/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-64 (21)
R extensions/pointcloud/examples/example-autzen.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-65 (6)
M extensions/sar/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-66 (38)
M extensions/sar/examples/envisat.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-67 (11)
M extensions/sar/examples/sentinel1.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-68 (12)
A extensions/sar/json-schema/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-69 (218)
D extensions/sar/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-70 (204)
M extensions/scientific/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-71 (13)
D extensions/scientific/example-merraclim.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-72 (39)
A extensions/scientific/examples/collection.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-73 (47)
A extensions/scientific/examples/item.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-74 (67)
R extensions/scientific/json-schema/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-75 (40)
A extensions/single-file-stac/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-76 (32)
A extensions/single-file-stac/examples/example-search.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-77 (616)
A extensions/single-file-stac/json-schema/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-78 (38)
D extensions/single-item/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-79 (45)
D extensions/single-item/example.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-80 (68)
D extensions/single-item/schema.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-81 (50)
M item-spec/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-82 (17)
M item-spec/examples/CBERS_4_MUX_20181029_177_106_L4.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-83 (5)
M item-spec/examples/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-84 (10)
M item-spec/examples/digitalglobe-sample.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-85 (15)
A item-spec/examples/itemcollection-sample-full.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-86 (87)
A item-spec/examples/itemcollection-sample-minimal.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-87 (4)
M item-spec/examples/landsat8-sample.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-88 (12)
M item-spec/examples/planet-sample.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-89 (7)
M item-spec/examples/sample-full.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-90 (21)
M item-spec/examples/sample.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-91 (6)
M item-spec/examples/sentinel2-sample.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-92 (5)
M item-spec/item-spec.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-93 (96)
A item-spec/itemcollection-spec.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-94 (41)
D item-spec/json-schema/geojson.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-95 (353)
M item-spec/json-schema/item.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-96 (81)
A item-spec/json-schema/itemcollection.jsonhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-97 (56)
M process.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-98 (2)
M validation/README.mdhttps://github.com/radiantearth/stac-spec/pull/565/files#diff-99 (2)

Patch Links:

https://github.com/radiantearth/stac-spec/pull/565.patch
https://github.com/radiantearth/stac-spec/pull/565.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/radiantearth/stac-spec/pull/565?email_source=notifications&email_token=AGLFGUFK44ODV35KAE3FMR3QFQDPFA5CNFSM4INYQW62YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HGI33DA, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGLFGUA2Y7LQWU6P6WME27LQFQDPFANCNFSM4INYQW6Q.
CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

Closed in favor of #568


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 2542 ms

Resolved: Samsung performance has improved in 763c503.


Reflection::get_descriptor_sets doesn't list samplers

example fragment shader:
#version 450
layout(binding = 0) uniform sampler2D texSampler;

layout(location = 0) in vec4 fragColor;
layout(location = 1) in vec2 fragTexCoord;

layout(location = 0) out vec4 outColor;

void main() {
    outColor = texture(texSampler, fragTexCoord) * fragColor;
}

the output of get_descriptor_sets is empty

Thank you for reporting this! The issue may have already been fixed by #27 (but was reported to cause a panic rather than an empty list in #26), but that hasn't made it to a release yet. Can you try the latest master branch and confirm that it works for you?
#5 introduces a bunch of GLSL-specific tests, one of which has a layout(set = 5, binding = 0) uniform sampler2D g_samplerimage2d; similar to your example (but in a compute shader) which results in the following binding output:
    5: {
        0: DescriptorInfo {
            ty: COMBINED_IMAGE_SAMPLER,
            binding_count: One,
            name: "g_samplerimage2d",
        },
    },

And there's similar output with your shader on that test branch. Let me know how testing goes, I'll likely just merge #5 and push out a new release if this resolves it for you!


Add v4l2_codec2 and ffmpeg_codec2

v4l2_codec2 provides hardware accelerated  h264 encoding
ffmpeg_codec2 provides hardware accelerated encoding for h264 and h265. Various other formats via software decoding
TODO: switch to mainline ffmpeg via aospext with patches from Jernej, fork ffmpeg_codec2 from raspberry-vanilla

@mikegapinski ,
Thank you for this PR
Could you share your experience on how to test codecs? Making a Wiki page someday would be nice.

From my experience CTS and VTS commands are:
atest CtsVideoTestCases
atest VtsHalMediaC2V1_0TargetVideoEncTest VtsHalMediaC2V1_0TargetVideoDecTest VtsHalMediaC2V1_0TargetComponentTest

But some methodology for measuring codecs performance would be nice to have.

@mikegapinski ,
Thank you for this PR
Could you share your experience on how to test codecs? Making a Wiki page someday would be nice.

I usually just do a BigBuckBunny in a few formats and observe the CPU usage - measuring codecs on Tesla Android is not a good idea because I run the virtual display all the time and results vary. At least they used to on my current public build without mjpeg acceleration

@rsglobal if we are doing ffmpeg with aospext should I refactor this PR to only include the v4l2_codec2 for h264 encoding(scrcpy etc)?
Or you can ping me when ffmpeg is ready on your branch and I'll rebase on top it with my changes

@rsglobal if we are doing ffmpeg with aospext should I refactor this PR to only include the v4l2_codec2 for h264 encoding(scrcpy etc)?
Or you can ping me when ffmpeg is ready on your branch and I'll rebase on top it with my changes

My plan is to enable ffmpeg-codec2 for software codecs for now and apply it to all GloDroid devices.
This requires modification of ffmpeg-codec2 to support meson.build and use aospext for building it (otherwise using ffmpeg-installed headers is not possible), So it will take some time. After that, we will add patches for h265 on top.
As for v4l2_codec2 I have no plans for it, so if you can split it from this repo, we can land it ASAP. It would be nice to put it as a part of gd_rpi4 device tree instead of glodroid configuration patches if possible. E.g. into .../gd_rpi4/codecs/ directory.

@rsglobal if we are doing ffmpeg with aospext should I refactor this PR to only include the v4l2_codec2 for h264 encoding(scrcpy etc)?
Or you can ping me when ffmpeg is ready on your branch and I'll rebase on top it with my changes

My plan is to enable ffmpeg-codec2 for software codecs for now and apply it to all GloDroid devices. This requires modification of ffmpeg-codec2 to support meson.build and use aospext for building it (otherwise using ffmpeg-installed headers is not possible), So it will take some time. After that, we will add patches for h265 on top.
As for v4l2_codec2 I have no plans for it, so if you can split it from this repo, we can land it ASAP. It would be nice to put it as a part of gd_rpi4 device tree instead of glodroid configuration patches if possible. E.g. into .../gd_rpi4/codecs/ directory.

OK. Understood. What I recommend at this state is leaving this PR unmerged as it is now. Anyone can just merge the branch locally and have hardware accelerated codecs in the best/only available form. I'll be using it in the Tesla Android builds until a better alternative emerges.
I will create another PR that adds v4l2 to rpi4 device that could be merged right now. This would give the GloDroid rpi4 builds with h264 encode/decode on top of your ffmpeg implementation with software decoders. The changes hwaccel in ffmpeg won't be happening on device level so no changes would be required here, once the patches show up it'll simply start working


how to get the unicodes insted of shortcodes in textarea?

When user selects an emoji from the picker then In textarea insted of  shortcode I want show unicode in textarea.

I also need this, event setting allowNative to true still outputs shortcodes


You can bring your bike on the bus if you want.

OTP routing supports transit+bikes, so now we expose a UI for that.
transit without bike

transit with bike

So, after playing with this a bit, I became suspicious that only bike+train routes were being recommended, never bike+bus.
With some debugging help from the nice folks working on OTP, I realized that most of my input GTFS feeds lacked the bikes_enabled column in trips.txt and routes.txt and that OTP assumes "unknown" == "not allowed".
In my transit experience, the opposite is more common: most transit agencies have some kind of rack or otherwise allow bikes on transit. So I added some pre-processing to assume bikes are allowed on transit unless they are explicitly forbidden.
I'm sure this is not universally true, and if it becomes an issue we can figure out a better solution or some kind of configurable option, but AFAIK I'm the only one using the transit features in Headway anyway. 😅
If I'm wrong and this negatively affects you, let me know and we can figure something out.
Here's some example queries of bike+transit:
Without biking (transit+walking):

Same trip with (transit+bike) can be quite a bit faster:

It'll also be enabled for the other transit zones we support (once it's deployed):

For completeness, I should add: I reached out to my local transit agency (King County Metro) about getting them to add bicycle amenities to their GTFS feed last week but haven't heard back.


Improve custom unit conversions

The non-linear unit conversion mechanism has to be further improved... https://github.com/vrtulka23/scinumtools/blob/main/src/scinumtools/units/UnitConverters.py

The conversion class structure was simplified in the newest version


Support for human-centric tasks

Hi,
Does conductor support the notion of human-centric tasks? Like a user activity where a manager needs to manually approve something before we go the next task? If yes, we are also looking to see if there is support for additional features like task escalation, delegation, inbox that shows user's tasks, etc? I did not see any explicit support for these features based on the documentation I have seen but I could have definitely missed something.
If conductor does not support human-centric tasks, any idea if there are any open source alternatives that provide the human-centric workflows which can be easily plugged into Conductor? Thanks in advance for any help you can provide.
Thanks!

I think this can be implemented using Wait(System Task) and Event Handlers.

This is something I am exploring. Can anyone send me a sample on how Wait and Event handlers can be used?

Meanwhile i learned there is a specification defining an interface between a workflow engine and the human interface.
it would allow to have reusable human interfaces, independent on the workflow engine. It could resolve this issue, if only we had an implementation that can be attached.


Error message is unclear on listing key from an unavailable rule name in servicebus namespace

This is autogenerated. Please review and update as needed.
When run az command to list keys on  an unavailable rule name in namespace, return error message "TypeError: string indices must be integers" is unclear, hard to understand the root cause. That would be good to reflect the actual error when accessing an unavailable rule name.
Describe the bug
Error message is unclear to get unavailable rule name in namespace
Command Name
az servicebus namespace authorization-rule keys list --subscription ***  --name <rule name not existing> --namespace-name ** --resource-group ** --output json
Errors:
TypeError: string indices must be integers
To Reproduce:
az servicebus namespace authorization-rule keys list --subscription ***  --name <rule name not existing> --namespace-name ** --resource-group ** --output json
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/knack/cli.py", line 215, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 654, in execute
raise ex
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 718, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 711, in _run_job
six.reraise(*sys.exc_info())
File "/usr/local/lib/python3.8/site-packages/six.py", line 703, in reraise
raise value
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 688, in _run_job
result = cmd_copy(params)
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 325, in call
return self.handler(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/init.py", line 545, in default_command_handler
return op(**command_args)
File "/usr/local/lib/python3.8/site-packages/azure/mgmt/servicebus/operations/namespaces_operations.py", line 870, in list_keys
raise models.ErrorResponseException(self._deserialize, response)
azure.mgmt.servicebus.models.error_response_py3.ErrorResponseException: Operation returned an invalid status code 'Not Found'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.8/site-packages/azure/cli/main.py", line 41, in
exit_code = cli_main(az_cli, sys.argv[1:])
File "/usr/local/lib/python3.8/site-packages/azure/cli/main.py", line 30, in cli_main
return cli.invoke(args)
File "/usr/local/lib/python3.8/site-packages/knack/cli.py", line 226, in invoke
exit_code = self.exception_handler(ex)
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/init.py", line 106, in exception_handler
return handle_exception(ex)
File "/usr/local/lib/python3.8/site-packages/azure/cli/core/util.py", line 96, in handle_exception
error = response_dict['error']
TypeError: string indices must be integers
root@dcbb744c871f:/msftkube# az servicebus namespace authorization-rule keys list --subscription bb85ce66-75b5-49d6-a82a-28988b37^C76 --name ListenSendSharedAccessKey --namespace-name hyperdrive-fail-usnatwest --resource-group vienna-usn
atwest --output json

Put any pre-requisite steps here...
``

Expected Behavior
Environment Summary
Linux-4.19.128-microsoft-standard-x86_64-with-glibc2.29
Python 3.8.2
Installer: PIP

azure-cli 2.9.0 *

Additional Context

add @houk-ms , typeError

@evanlwj Thanks for the feedbacks!
This issue should be resolved in the latest version, can you upgade CLI to 2.14.0 and try it again?

The issue is resolved, please upgrade Azure CLI  2.22.1.
hence closing the issue.


fix golangci-lint err

should replace this if statement with an unconditional strings.TrimSuffix

Codecov Report

Merging #1031 (5e9a4d3) into main (6b7448a) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main    #1031      +/-   ##
============================================
- Coverage     42.48%   42.46%   -0.03%
  Complexity      149      149
============================================
  Files           146      146
  Lines         23727    23726       -1
  Branches        422      422
============================================
- Hits          10081    10075       -6
- Misses        12332    12335       +3
- Partials       1314     1316       +2

Impacted Files
Coverage Δ

pkg/object/hdfs.go
1.00% <0.00%> (+<0.01%)
:arrow_up:

pkg/vfs/writer.go
75.25% <0.00%> (-1.02%)
:arrow_down:

pkg/meta/redis.go
69.12% <0.00%> (-0.38%)
:arrow_down:

pkg/meta/sql.go
66.42% <0.00%> (+0.09%)
:arrow_up:

pkg/vfs/reader.go
68.24% <0.00%> (+0.54%)
:arrow_up:

pkg/vfs/handle.go
86.55% <0.00%> (+0.84%)
: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 6b7448a...5e9a4d3. Read the comment docs.


Slow Login on notebook in long running app after sleeping

If an application with django-salesforce v1.0 is running long time on a notebook that has been sleeping in a low power state for some time or without a network connection, then a long timeout is possible at login or reauthenticate() of an expired token.
That is a result of commit 921560b3e9 "Fix a hidden warning about unclosed SSL connections". That commit improved a speed a little, but has this side effect.
A typical situation is if some analytics is performed interactively in JupyterLab and continued next day. It is not not a problem if Django is running continuously connected e.g. as a webserver and not before version 1.0.
The cause is a lost closing packet from Salesforce while the application was sleeping or disconnected

Closed by 02b0c99 and 249698a


Create a community collection of configuration and identifiers

I think it is a good idea to have a community-driven collection of Identifiers and Configurations for Karta. When such a collection get bigger, it will increase the chances that the configuration you are looking for was already created by a community member.
I think that such a solution can be achieved in several ways:

Encourage users to push their configs and identifier scripts to Karta/configs and Karta/src/libs
Create a new repository to store configs and libs, and use it as a submodule from inside Karta
Create an external repository (similar to FLIRTDB) to store the configs and identifiers.

Sounds like a good idea. I was hoping that calling researchers to collaborate on this, both in conferences and in twitter, will be enough. But thus far we received 0 commits / pull requests with added configurations / identifiers.
The point in presenting this plugin in conferences was exactly this, to get community collaboration to build a massive collection of identifiers / configurations. Sadly, I already tried the first option, and options 2 and 3 would only make sense once people start submitting new things, otherwise the ROI would be negative.

For (1) this can be a step in the doc. Just after compiling the config and identifier. Something like "Please consider to submit the config you created to the community collection of configurations and fingerprints."
Having a repository that aims to collect all the configurations feels more welcoming to me than pushing new configuration to the main repository

For some reason readthedocs fails when I try to build the new documentation. Hopefully it will get fixed in the next few days so the new docs will include this new update.

Fixed the docs in #40, now readthedocs is updated to reflect the call to share with us the added support / configs.

On the one hand, thank you very much for such a great plugin. What this plugin does - I've been doing it by hand for the last 15 years.
And on the other hand, you "revealed" one of my professional secrets. Now, the art of reverse engineering - will no longer be so respected, because the threshold of entry - will be significantly reduced.
Perhaps some things are better never to be made public at all.


The profile picture is not displayed when trying to login with google

If not fixed here is a stackoverflow issue that should help:
https://stackoverflow.com/questions/25606322/retrieving-a-users-public-google-gmail-picture

[!NOTE]
I am technically the assigned person for this issue for further reference

I have found the google API associated with getting photos from a google account
https://people.googleapis.com/v1/people/me?personFields=photos (the exact link to get the data)
In an example you could easily do something such as:
async function getProfilePicture() {
  try {
    // Replace these with your actual credentials (and use something that isn't basically stored in plain-text)
    const accessToken = 'YOUR_ACCESS_TOKEN';

    const apiUrl = 'https://people.googleapis.com/v1/people/me?personFields=photos';

    const response = await fetch(apiUrl, {
      method: 'GET',
      headers: {
        Authorization: `Bearer ${accessToken}`,
      },
    });

    if (response.ok) {
      const data = await response.json();
      const profilePictureUrl = data.photos?.[0]?.url;
      if (profilePictureUrl) {
        console.log(`Profile Picture URL: ${profilePictureUrl}`);
      } else {
        console.log('No profile picture found.');
      }
    } else {
      console.error('Error:', response.status, response.statusText);
    }
  } catch (error) {
    console.error('Error:', error);
  }
}

That is the basic code you could use without any outside dependencies which could cause vulnerabilities (I ofc do not guarantee this code works)

Since you asked for guidance relating relevant files - Here is the relevant file

Make sure you've read through the contributions guidelines or what we have of them so I don't have to request a lot of changes or any at all to your code contribution :sweat_smile:

Awe yep, my bad! 😅, I will get it done ASAP


C_CPP: Introduction to C

Description 📜
As a newbie in the field of tech, the first-ever programming language I learnt was C; hence I wish to contribute to this domain.
C as a language has evolved immensely over time. It was developed at Bell Labs by Dennis Ritchie between 1972 and 1973.
Ever since it has only been evolving with the times.
It is still used in today's world to a great extent, because of its many irreplaceable features! Thus with this contribution, I've given an overview of C and its programming components, structure, and keywords. I hope it gives you a kickstart in your coding journey.
Happy coding! :)
Fixes #850

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[ ] Doc#umentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[x] C/CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@Suvraneel It's good to go. You can have a look.

Updated PR with requested changes.

@prettylittleminds  LGTM ❤


create an automated csv of backers (chsf)

We need to create an automatically updated exportable csv of backers, that core contributors can export themselves.
Bear in mind that CRMs have name/surname separate and we have them together.

@xdamman we did this, right?


Naming collision on generated fakes

Hi there,
I'm using a library that contains a couple of classes like this:
data class Foo(...) {
   data class Data(...)
}

data class Bar(...) {
   data class Data(...)
}

When trying to write tests, I'd like to generate fakes based on those Data classes, and so I added
@UsesFakes(Foo.Data::class)

and
@UsesFakes(Bar.Data::class)

to their respective cases.
Unfortunately I get a kotlin.io.FileAlreadyExistsException where fakeData already exists. Is there a way to give a custom name to the fake? something like
@UsesFakes(Foo.Data::class as FooData)

Cheers!

Fix released in v1.14.0.


The editor could not be opened due to an unexpected error: Cannot read properties of undefined

Type: Bug
I'm working remotely and very often loose connection to the jupyter server. The workflow if that happens need to improve a bit, there are too many popup alerts... Right now this happened to my notebook after I got disconnected and connected again.

Extension version: 2022.9.1002511105
VS Code version: Code 1.71.2 (74b1f979648cc44d385a2286793c226e611f59e7, 2022-09-14T21:07:15.900Z)
OS version: Darwin arm64 20.6.0
Modes:
Sandboxed: No
Remote OS version: Linux x64 4.18.0-348.12.2.el8_5.x86_64

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 2, 2

Memory (System)
16.00GB (0.30GB free)

Process Argv
--crash-reporter-id 4cf64333-f132-4c56-a15d-29c771efde05

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: ber

OS
Linux x64 4.18.0-348.12.2.el8_5.x86_64

CPUs
AMD EPYC 7502 32-Core Processor (128 x 2977)

Memory (System)
503.46GB (340.95GB free)

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30557515
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012:30540252
azure-dev_surveyone:30548225
2144e591:30553903
fc301958:30573243

Similar issue here. I'm working locally, and the error message is slightly different. Closing the file and re-opening resolves the problem.

Jupyter Extension version: v2022.8.1002431955
VS code version: Version: 1.71.2 74b1f979648cc44d385a2286793c226e611f59e7
Date: 2022-09-14T21:05:37.721Z
OS: MacOS Catalina 10.15.7

It happens again..  I try to close the notebook and click on "Don't save" but the window simply doesn't close. I have to restart VScode in order to open again..

It happens again.. I try to close the notebook and click on "Don't save" but the window simply doesn't close. I have to restart VScode in order to open again..

I have the same issue. It happens fairly regularly after working in VS code for 1-2 hours. I haven't been able to identify any particular trigger

Being troubled by this problem as well.

Same here, I have seen this couple of times now, and it is interrupting my development cycle.

Same here. Working on Windows, hosting an Ubuntu server VM, using Samba.

I am having the same / a similar issue. Working on a SSH remote.

It mostly consistently triggers when I run intensive code, that also generates a lot of output (tqdm progress bars). I'm having no trouble opening the same notebook through jupyter notebook (also remote). A checkpoint of the same notebook created through jupyter, re-enables me to open the file.
The python language server crashed at the same time, so this might be related to pylance (?) or the language server. I found the onDidChangeContent property on the vscode documentation, though I do not feel capable of debuging this further. It might also be related to issue #165176. Hope this helps

Also having this problem

Has anyone solved this problem?

Same issue in Feb'23 version of VSCode. I just can't use it for longer than 10-15 minutes. Need to reload window to continue working.

Also have this issue. I use the copilot plugin.

We need to notify the copilot team. Opened a discussion here

I have the same issue here; to definitely copilot that trigger it for me wrote a message in the other thread.

Same problem here, I get this error every hour or so. Also have copilot, but no idea if this is related.

same problem, when i deactivate copilot and it stopped

Same problem here

Rolling back Jupyter and Copilot extensions resolve the issue. I've raised a ticket with GitHub regarding it and they are investigating.

I dont have copilot,  and i also have this issue.

I have this issue too; remote server, appears where my Jupyter notebooks should be. I use copilot.

I had this issue with the error message the editor could not be opened due to an unexpected error: Cannot read properties of undefined (reading 'onDidChangeContent'). Using vscode locally on MacOS. I don't use copilot. Reloading the window via F1 > Developer: Reload Window resolved the issue.

Thank you all for your feedback and patience. This issue is now mitigated in latest VS Code Insiders and will be available in next Stable.
What happens is Copilot (or any other extension) crashes the extension host and then the serializer for ipynb notebook is no longer available. Even if the extension host is restarted, we fail to re-associate the serializer extension with the notebook document in the workbench/ui. This should now be improved, work happened in https://github.com/microsoft/vscode/issues/179224


[CS2103-W16-1] UniBook

UniBook provides University students with an all-in-one platform to communicate with professors and other students taking the same modules as them.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8d5b66e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   72.15%
  Complexity        ?      399
=========================================
  Files             ?       70
  Lines             ?     1232
  Branches          ?      125
=========================================
  Hits              ?      889
  Misses            ?      311
  Partials          ?       32

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 8d5b66e...4167a55. Read the comment docs.


Adding Urdu For Pakistan in Sliding Text

What changed? Why?
Adding Urdu to our "Base is for everyone" slider.
Notes to reviewers
How has it been tested?
Runed  yarn workspace @app/web dev
Navigated to http://localhost:3000 in my browser
Maked sure that slider is working as expected

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/2

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
1

Sum
2

@razashozab44
Hi there! Thanks for contributing to Base! Could you please resolve the merge conflict?

@razashozab44
Hello, could you please rebase to fix the merge conflict?


Adding Linode to the list of CloudProviders supported by Pulumi

Related: #1879

Also added the provider configuration to the provider README https://github.com/pulumi/pulumi-linode/pull/31


Support latest server - versioning changes

new server supports versioning and there were changes in serialization amongst other things. implement support for this new server
Anatoliy Osetsymskyi
Hi guys=) We did Versinoning release of blockchain(It is next release for Dragon. We don't plan to integrate Elephant and next NEM releases at the moment, but maybe we will change it in future).
It contains breaking changes, so now sdk doesn't work with it. But you can easy fix it.
We increased the version(it is field in transaction) of each transaction from 2 bytes(uint16) to 4 bytes(uint32).
Also we added CatapultConfigTransaction and CatapultUpgradeTransaction.
You can find updated flatbuffers here:
https://github.com/proximax-storage/go-xpx-chain-sdk/tree/development/transactions/schemas
Also we added "config/{height}" and "upgrade/{height}" routes. First route returns config of network at height X, second return required version of blockchain
You can find more information in swagger:
https://github.com/proximax-storage/js-xpx-chain-rest/blob/master/swagger.yaml
If you have questions, you can check GO SDK first(For example how to create a new version of tranasction, or how to parse blockchain's config):
https://github.com/proximax-storage/go-xpx-chain-sdk/pull/46/files
Also we removed hardcoded currency MosaicId=) Now it is namespaceId "prx.xpx", because each network will have own MosaicId:
https://github.com/proximax-storage/go-xpx-chain-sdk/blob/development/sdk/consts.go#L15
For testing you can use local version of blockchain or devnet. On the next week we will push it to staging network:
Local(currency mosaic is prx.xpx): https://github.com/proximax-storage/dfms-dev-net/releases/tag/versioning-0.1
Devnet(currency mosaic is prx.xpx): http://bcdev1.xpxsirius.io:3000/config/1
Shin Neng Wong
latest update for testnet:
COW version:
bctestnet1.xpxsirius.io
bctestnet2.xpxsirius.io
*DRAGON version :
bctestnet1-dragon.xpxsirius.io
bctestnet2-dragon.xpxsirius.io
bctestnet3-dragon.xpxsirius.io
bctestnet4-dragon.xpxsirius.io
bctestnet5-dragon.xpxsirius.io
bctestnet6-dragon.xpxsirius.io

chain will be reset once new Dragon version is ready

missing stuff

rename TransactionType and TransactionVersion to entityType and EntityVersion respectively
implement

func (ref *NetworkService) GetNetworkConfigAtHeight(ctx context.Context, height Height) (*NetworkConfig, error) {
func (ref *NetworkService) GetNetworkConfig(ctx context.Context) (*NetworkConfig, error) {
func (ref *NetworkService) GetNetworkVersionAtHeight(ctx context.Context, height Height) (*NetworkVersion, error) {
func (ref *NetworkService) GetNetworkVersion(ctx context.Context) (*NetworkVersion, error) {

absence of contract duration is causing issues...
java.lang.NullPointerException: null
	at io.proximax.sdk.infrastructure.ModifyContractTransactionMapping.apply(TransactionMapping.java:564)

namespace tests have issues because names endpoint now returns full name, not just part

current status:

need to implement network config and version endpoints and transactions
issue #111 was raised for renaming the transaction type and version enums

e2e tests often timeout... likely the property to set block time does not work anymore...

timeouts can be addressed by regenerating the nemesis block. issue #111 and issue #112 were raised to track followup changes. this issue will focus on version serialization changes and related changes
The only pending task is to collect transaction data to verify mappings via jUnit tests

pull request #113 raised for this task


[feature-suggestion] [kubectl] Ability to filter "kubectl get "  output to show only select columns

kubectl get <resource_name> prints all the resource info as a table by default. Sometimes there is just too much data and one row of the table is not able to fit in one line. It takes time to comprehend that entire output. It may be particularly useful to restrict columns by name. So for example in context of resource pod, something like..
kubectl get pods --filter names
that would only pod names instead of an entire table containing all columns like POD, HOST, STATUS, CREATED, etc. would be particularly useful.
Exact interface for this might need to be discussed and planned on a wiki. (I'll try to update this issue with a more detailed suggest if I can think of something)

For now I realized I can do something like kubectl get pods |  awk '{print $1}' to get the column name I want (i.e. just the name of the pods in this case)

This is actually in progress.  #7843
On Thu, Jun 4, 2015 at 12:21 AM, Pranjal Mittal<EMAIL_ADDRESS>wrote:

kubectl get <resource_name> prints all the resource info as a table by
default. Sometimes there is just too much data and one row of the table is
not able to fit in one line. It takes time to comprehend that entire
output. It may be particularly useful to restrict columns by name. So for
example in context of resource pod, something like..
kubectl get pods --filter names
that would only pod names instead of an entire table containing all
columns like POD, HOST, STATUS, CREATED, etc. would be particularly useful.
Exact interface for this might need to be discussed and planned on a wiki.
(I'll try to update this issue with a more detailed suggest if I can think
of something)
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/9247.

Are you aware of -o template?

See also discussion in #7843

@bgrant0607: Yeah I know the -o template. (I have just used the -o json format till now)
Looks like #7843 is exactly what I reported (as @thockin pointed out) , so this is duplicate then, closing issue.


Add semantic-release

:tada: This issue has been resolved in version 3.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Properly cast complex types in scipy.io.loadmat() when mat_dtype is True

Reference issue
closes gh-17641
What does this implement/fix?
Fixes scipy.io.loadmat() to properly cast complex numbers when mat_dtype is True.
Additional information

The workflow failures don't appear related to the changes in the PR.  What can I do to resolve this?

That specific failure has now been fixed in main I believe

Great! How do I get those two workflows re-run?

@Seairth you can rebase the changes on main to your branch, by following the steps in the Development workflow guide. If you need help with that, let me know!

There's not enough information in the failed muslinux_amd64_test check for me to know why it failed.  Suggestions?

@Seairth, that job occasional fails with a seg fault.  It is almost certainly not related to your changes.

Will it stop the MR from going forward?

No, I think we've learned to ignore that particular failure.
For what its worth, I just tried to restart that job (twice, in fact).  The web interface tells me that I have successfully requested that the job be re-run, but I don't see it actually restarting.  Maybe there is a longer lag than I expected.  If a reviewer is happy with these changes, there is no need to wait for that job to be re-run. (Sorry, I haven't looked at the actual changes myself.)

Sorry to be slow.  Would you mind putting in a test that will fail without these changes?


Space offset X'00000000' or X'FFFFFFFFFFFFFFFD' is outside current limit

Sometimes calling certain procedures via this custom method executeStatement as such CALL PROCEDURE_NAME('val1'); will result in a segfault for node. It fails specifically at await statement.exec(sqlStatement);.
The job log shows the following error:
Space offset X'00000000' or X'FFFFFFFFFFFFFFFD' is outside current limit
   for object QP0ZSPWP  QSECOFR   200203.
 PASE for i ended for signal 11, error code 1.
 Value for call stack counter parameter not valid.
 Application error.  CPFB9C6 unmonitored by QP0ZPCPN at statement
<PHONE_NUMBER>, instruction X'0000'.

Environment details:

Node 10.15.3
idb-pconnector 1.0.7
idb-connector 1.2.1
IBM i version is V7R3M0 or 7.3

 executeStatement: async function(sqlStatement) {
    const conn = this.pool.attach();

    var statement, results;

    statement = new Statement(conn.connection);
    await statement.exec(`SET PATH = ` + libraryList.join(', '));
    await statement.close();

    statement = new Statement(conn.connection);
    results = await statement.exec(sqlStatement);

...

What's the SQL statement you are executing at the time? Or at least, can you give a description of the query (# of columns, column types and sizes, etc...)?

Here's some additional information. This happens when calling procedures with exec after a certain amount of rows (around 750 in our case). Here's the description of the columns.

We switched over to using execute() and fetch() the segfault doesn't happen anymore.

@dmabupt can you investigate this failure?

Since this is occurring in native code, the problem must be in idb-connector, so I'm moving the issue to that repo.

Did anyone ever investigate this issue any further?  I seem to having the same issue here when I call executeSync  I'm calling a stored proc and the results are inconsistent. Sometimes it works, sometimes I get the segmentation fault. I can call the below code 3 or 4 times and it's fine, but then other times I get the segmentation error. I'm not sure what the problem is?
My code:

 let sql = "";

                if (env == "DEV") {
                    sql = 'CALL PGX320CD.PGDR589B(?,?,?,?,?,?,?,?,?,?,?,?)';
                } else if (env == "QA") {
                    sql = 'CALL PGX320CQ.PGDR589B(?,?,?,?,?,?,?,?,?,?,?,?)';
                } else if (env == "PROD") {
                    sql = 'CALL PGX320CP.PGDR589B(?,?,?,?,?,?,?,?,?,?,?,?)';
                };

                // Set the Input Parms

                let product = "";
                let quantity1 = 0;
                let cost1 = 0;
                let quantity2 =  0;
                let cost2 =  0;
                let quantity3 =  0;
                let cost3 =  0;
                let quantity4 =  0;
                let cost4 =  0;
                let quantity5 =  0;
                let cost5 =  0;
                let messageOut = "";

                product = jsonObj.product;
                quantity1 = jsonObj.quantity.qty1;
                cost1 = jsonObj.cost.cost1;
                quantity2 = jsonObj.quantity.qty2;
                cost2 = jsonObj.cost.cost2;
                quantity3 = jsonObj.quantity.qty3;
                cost3 = jsonObj.cost.cost3;
                quantity4 = jsonObj.quantity.qty4;
                cost4 = jsonObj.cost.cost4;
                quantity5 = jsonObj.quantity.qty5;
                cost5 = jsonObj.cost.cost5;
                messageOut = "";

                let params = [
                    product,
                    quantity1,
                    cost1,
                    quantity2,
                    cost2,
                    quantity3,
                    cost3,
                    quantity4,
                    cost4,
                    quantity5,
                    cost5,
                    messageOut
                ];

                console.log(params);

                statement.prepareSync(sql,(err)=>{
                    if (err) {
                    console.log(err);
                    };
                });

                statement.bindParametersSync(params, (err)=>{
                    if (err) {
                    console.log(err);
                    };
                });

                statement.executeSync((outputParams, err)=>{
                    if (err) {
                    console.log('PGDR589: ' + err);
                    } else {
                    console.log('Params = ' + outputParams);
                    statement.close();
                    connection.disconn();
                    connection.close();
                    callback(outputParams);
                    };
                });`

My Stored Proc:
CREATE OR REPLACE PROCEDURE &LIB/PGDR589B (
 IN     PRODUCT         VARCHAR(33),
 IN     QTY1            NUMERIC(15,3),
 IN     COST1           NUMERIC(17,4),
 IN     QTY2            NUMERIC(15,3),
 IN     COST2           NUMERIC(17,4),
 IN     QTY3            NUMERIC(15,3),
 IN     COST3           NUMERIC(17,4),
 IN     QTY4            NUMERIC(15,3),
 IN     COST4           NUMERIC(17,4),
 IN     QTY5            NUMERIC(15,3),
 IN     COST5           NUMERIC(17,4),
 OUT    MESSAGE         VARCHAR(500)
 )
 LANGUAGE RPGLE
 SPECIFIC &LIB/PGDR589B
 NOT DETERMINISTIC
 CALLED ON NULL INPUT
 EXTERNAL NAME PGDR589B
 PARAMETER STYLE GENERAL ;

COMMENT ON SPECIFIC PROCEDURE &LIB/PGDR589B
 IS 'Purchase Price API' ;

the message:
Message . . . . :   Space offset X'00000000' or X'69636520656E748A' is outs
current limit for object QP0ZSPWP  MATTOJ    215693.
Cause . . . . . :   A program tried to set a space pointer, tried to use
storage outside a space, or tried to use an unallocated page in teraspace
The space class is X'08'. The space class designates the type of space:
When I add the debugger, I can see that this happens after the execute function:
SQLExecute(0):
SQLNumResultsCols(0) Has Results
/nodejs/webapi/app.sh[21]: 19066 Segmentation fault(coredump)


🦺[Tech Debt] Remove cruft: BitID

Goal
Describe the work to be done
Remove any references to the original fork (Breadwallet) where BitID was used.  This was a service to be used by the BRD team and was never implemented in Litewallet (or Loafwallet).
It causes confusion and problems maintaining the codebase.  It must be removed safely
Definition of Done

[x] Open a working branch and let @kcw-grunt know
[ ] Identify S,M,L refactors
[ ] Branch off the working branch and write issues for the refactors.
[ ] Test with older and newer iOS devices and simulators

@JasperHeist I added #58 as a dependency to make sure  it was done first.

@JasperHeist I added #58 as a dependency to make sure it was done first.

Do you want this or #58 done first? Right now it's showing this one has to be done first, is that what you wanted? @kcw-grunt

opened branch techdebt/Remove-cruft-BitID-57.  Can you confirm I interpreted the "blocking" thing right? or do you want the BCash stuff done first?

@JasperHeist I added #58 as a dependency to make sure it was done first.

Do you want this or #58 done first? Right now it's showing this one has to be done first, is that what you wanted? @kcw-grunt

Yes @JasperHeist you have interpreted this correctly The reason is BitID has less code and was never implemented by BRD/Breadwallet (from my quick assessment)


(feature)  element

Describe the feature request
Support the <progress> element. This element is not currently supported on native.

Describe the feature request
Support the <progress> element. This element is not currently supported on native.
Can you explain the problem in detail actually i'm not getting it.

Describe the feature request
Support the <progress> element. This element is not currently supported on native.

https://www.npmjs.com/package/react-native-progress


ProxiedCommandSender via /execute callee/caller incorrect

Finally had a need to try out the new ProxiedCommandSender change.
Tested against v1.5, compiled from source (at the v1.5 tag)
After noting the behavior wasn't quite right, I added some prints to see what was going on.
Here is my test command
/execute as @p run mycustomcommand

I observe the following behavior when I look at what sender actually contains:
When run as a player:
Sender is a org.bukkit.craftbukkit.v1_13_R2.entity.CraftPlayer (bad - should be ProxiedCommandSender)
When run as a command block:
Sender is a org.bukkit.craftbukkit.v1_13_R2.command.ProxiedNativeCommandSender (good)
Sender.callee is a org.bukkit.craftbukkit.v1_13_R2.command.CraftBlockCommandSender (bad - should be Player)
sender.caller is a org.bukkit.craftbukkit.v1_13_R2.command.CraftBlockCommandSender (good)
When run as the console:
Sender is a org.bukkit.craftbukkit.v1_13_R2.command.ColouredConsoleSender (bad - should be ProxiedCommandSender)

When run as a player:
Sender is a org.bukkit.craftbukkit.v1_13_R2.entity.CraftPlayer (bad - should be ProxiedCommandSender)

Logically

If you run this command as a player, which targets yourself, I think it's reasonable for it to be a regular Player as opposed to a ProxiedCommandSender.  For example, say I'm playing as Skepter ingame:
/execute as @p[name=Skepter] run mycommand and /mycommand both produce the exact same response ingame (either both are ProxiedCommandSenders or both are players).
In other news, everything else should be fixable.

Fixed the main issue in this commit - my cache implementation for NMS was broken.
As stated above, when you're executing the command as yourself, it'll not return a ProxiedCommandSender, whereas everything else should work lovely.
Thanks for pointing this out - I've been pulling my hair out about this issue.

Awesome! Thanks for your hard work.