find a differ supporting object '250' of type 'string'. NgFor only supports binding to Iterables such as Arrays

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

Expected behavior

Reproduction of the problem

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Table version: 10.2.0

Angular version: 4.3.3
find a differ supporting object '250' of type 'string'. NgFor only supports binding to Iterables such as Arrays

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript 2.4.2 | ES6/7 | ES5]

+1 Same error after update to version 10.2.1

Where is this happening? Can you provide a repro?

Sorry i can't reproduce the error at the moment.

when rows data have  fieldname  "value" and all this Field value is string number; like "value":"250"

@hevan I'm not sure I'm following. So your row data is something like this:?
const rows = [{ value: "250", }, { value: "251" }]
What are you using for your columns?
Do you have a plunker you can link to?

@wizarrc like that。but I haved to change the field name and change string to number, all ok! Thank you!!!

So it's a bug, or theres is some datatype definition to the rows. Right?

Seems like. I had the same issue when my data looks like this
[
{
"key": "Ethel Price",
"value": "Johnson"
},
{
"key": "Claudine Neal",
"value": "Sealoud"
},
{
"key": "Beryl Rice",
"value": "Velity"
}
]
But reading thru the comments here, and after changing it to
[
{
"key": "Ethel Price",
"propValue": "Johnson"
},
{
"key": "Claudine Neal",
"propValue": "Sealoud"
},
{
"key": "Beryl Rice",
"propValue": "Velity"
}
]
it worked fine. Thank you

@shriramMani you answer clarify a lot the comments
thanks!

Problem solved on release 10.3.0


use insert_one instead of insert, which was deprecated in mongo 3.0

fix #15

Hey @xialu4820723, thanks again for your pull-request. I apologize for my real late response to this but I recently integrated a change that does handle those deprecated methods in a more general scope. Therefore I'm gonna close this pull-request even though I really appreciate your help.


dm.basesize not showing in docker info

docker info output as follows:
Containers: 0
Images: 4
Storage Driver: devicemapper
 Pool Name: docker-8:4-1073741920-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 2.032 GB
 Data Space Total: 107.4 GB
 Data Space Available: 105.3 GB
 Metadata Space Used: 1.72 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.146 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.127 (2016-06-11)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.6.0-1-amd64
Operating System: Debian GNU/Linux stretch/sid (containerized)
CPUs: 6
Total Memory: 15.59 GiB
Name: debian
ID: UV2L:CG6Y:NQ4W:K7KY:6VN5:DIMN:SYED:BIQK:ZYBZ:HH4I:NE5Y:4ACN
Username: hamiltino
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support

Where is dm.basesize???

hm, should be there (was added in https://github.com/docker/docker/pull/16303), but I'll need to check. What version of Docker are you running?

Docker version 1.8.3, build f4bf5c7

That explains; it was added in Docker 1.9, so you need to upgrade docker for that.
I'm closing this because this is not a bug, but feel free to comment after I closed

followed the installation guide on the docker site and now my new version is:
Docker version 1.11.2, build b9f10c9
docker base size now shows but did i downgrade my docker?

Great!


Failed to load Dreambooth on Colab (A1111), Deforum too!!!

AssertionError: extension access disabed because of commandline flags

Use the local server to install extension sir!
https://github.com/TheLastBen/fast-stable-diffusion/issues/725

Use the local server to install extension sir!
#725

Thank You sir! but I encounter troubles while using the Local sever, I tried to install dreambooth and deforum extentions, deforum was installed, and I can see it on the panel above , however Dreambooth still can't find it , I appreciate if you could help me with that too, and thank you in advance

again found issue with Deforum: ModuleNotFoundError: No module named 'py3d_tools'

again found issue with Deforum: ModuleNotFoundError: No module named 'py3d_tools'

👇 I believe we r same person rn sir. 🤭🤭
https://github.com/TheLastBen/fast-stable-diffusion/issues/745

waiting for the legendary TheLastBen to fix our mesery lol!

I'll work on it soon

I'm still having these two problems.

When I try and install Deforum via extensions tabs, I get: AssertionError: extension access disabled because of command line flags
When I upload the extensions folder, I get this when I generate: ModuleNotFoundError: No module named 'py3d_tools'

you can't install it because you're using the gradio server

Yup, Just found it on another issue. Thanks! https://github.com/TheLastBen/fast-stable-diffusion/issues/685


Add support for custom case expressions which use arbitrary/multiple column(s)

Closes #65
A relatively advanced use case that is fairly common is for values in the comparison vectors to be derived from multiple columns.
For example, to deal with the possibility of name inversions, the user might want something like:
CASE WHEN
first_name_l = first_name_r AND surname_l = surname_r THEN 2
first_name_l = surname_r AND surname_l = first_name_r THEN 1
ELSE 0
END

It's also a bit tricky to think about how this should be dealt with in comparison_columns because up until now, we've assumed that each value in the comparison vector corresponds to a single column, and each column is identified by the col_name key in the comparison_columns part of the settings dictionary.
What I've done is allowed two possible specs for an entry in comparison_columns.
Either col_name must be completed as before:
{
"col_name": "first_name"
}

or the user must explicitly specify a custom column:
  {
        "custom_name": "custom_name",
        "custom_columns_used": ["first_name", "surname],
        "case_expression": """
CASE WHEN
first_name_l = first_name_r AND surname_l = surname_r THEN 2
first_name_l = surname_r AND surname_l = first_name_r THEN 1
ELSE 0
END
""",
        "num_levels": 2
        }

The later syntax isn't very intuitive, but this is advanced functionality and it would be expected that the user would modify example settings rather than write this from scratch

Using the test case_expression of:
case when jaro_winkler_sim(
array_join(array_sort(ARRAY [first_name_key_l, middle_name_key_l, last_name_key_l]), ''),
array_join(array_sort(ARRAY [first_name_key_r, middle_name_key_r, last_name_key_r]), '')
) > 0.94 then 1 else 0 end

has highlighted an issue with _add_null_treatment_to_case_statement(...).
While it works for your example above, it assumes a format of case when colname_l... to extract colname. If I understand correctly, this is where custom_column_names should come in so the null treatment can be added to these columns without searching the case expression?

Well spotted.  I agree, the current implementation isn't very robust and could be improved

Thinking about this, I think the simplest solution may be just to drop this functionality entirely.
The only time it makes sense is the case where the user is providing a custom case expression for a single column (i.e. they have specified a col_name not a custom_name).  Most of the time when they do this, we'd recommend they parameterise one of the pre-built statements from case_statements.py rather than write their own (these pre-built ones include the -1 null treatment so don't need any additions.
In the case where they've provided a custom_name, I don't think we'd want to try and 'guess' null treatment for the user.  Instead, the docs need to clearly state the user should define how the treatment of nulls should work i.e. their case expression should include a case for case x then -1  .

OK good, because I was coming to the opinion that it was becoming more complicated than was worthwhile in order to do it "properly" because it was just the null treatment that was a problem.
That's partly because I had issues with the null treatment even for the original simple usage. For example, it isn't triggered when "then -1" is found in the expression, ignoring potential other legitimate conditions for gamma = -1 that don't check for nulls.
Will put this to bed in the morning, sorry for the delay

One last thought (not necessary for this PR but potential as an option to put in later):
It seems like the real difficulty is in trying to detect whether the user has already dealt with nulls in the case_expression.
If we assume the user doesn't include it, adding the null treatment is easy (for col_name or for a list of custom_column_names). If we're worried about it not being all that simple for custom columns, then the simple null treatment could be an option in the settings, so the only time the onus is on the user is when they have a custom column where they have specific reason to opt out of it.


Fix columns for pods in service details panel

Service nodes' pods children have a field columns: null. This broke the JS layer which expected columns: []. Made JS layer more robust.
Fixes #1046

LGTM!


[Feature Request] Export formats - ppt & html

similar to https://github.com/msoedov/hacker-slides/issues/8
there are a bunch of cool/awesome formats that'd be cool to support, but what about the following two in addition to pdf?

ppt
browser-viewable ready html+js

I don't know how difficult these would be?

I have no idea, from a brief look to reveal it does not appear to have this feature https://github.com/hakimel/reveal.js/issues/1702
You can use a full screen preview for that or/and save it as HTML
Alternatively you can create a pr for HTML export + inlining all css / js /img into html

Thx for feature suggestion, I don't it's supported yet by reveal

it might be fairly possible..
actually.. it should be possible.. there's a js library here: https://gitbrent.github.io/PptxGenJS/#try

Interesting, great suggestion @machinshin! Do you have enthusiasm to instrument this? :)


Document list format options

Signed-off-by: anatoly techtonik<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Not necessary to run jenkins but I need to take a look at the jenkins test suite runs anyway so I'm abusing your branch. :) Thanks!

jenkins: test this please

jenkins: test this please

Doesn't seem to react. =)

Ok. I see the result now.


Close #13 | Add dataset for TyDiQA Id

Please name your PR after the issue it closes. You can use the following line: "Closes #ISSUE-NUMBER" where you replace the ISSUE-NUMBER with the one corresponding to your dataset.
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script nusantara/nusa_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _NUSANTARA_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one NusantaraConfig for the source schema and one for a nusantara schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_nusantara --path=nusantara/nusa_datasets/my_dataset/my_dataset.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

@holylovenia : thanks for the review, I will fix the script ASAP!

@holylovenia @bryanwilie : Thanks for the review, I updated the scripts accordingly and, in addition. also standardize the LICENSE for indonli.py


✨ WAL Pipelines in .yml

#530  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RTLS and the rest of your teammates on  Graphite


Lack of coverage over single-precision functions from CUDA Math API

I just realized this when working on #3159. For almost all ufuncs in CuPy (there do exist exceptions), whenever a function from CUDA Math API is called, we always choose the double precision version (without the f suffix in the function name). See, for example, https://github.com/cupy/cupy/blob/3d7706315b98121635c23b342eb9312ac237aa40/cupy/core/_routines_math.pyx#L869-L873
So, for single-precision (f) inputs, the line out0 = sqrt(in0) would first upcast the input to double, do the computation, and downcast to single.
I will try to do a benchmark for this. If a non-negligible difference does show up (I think so, because the arithmetic intensity is doubled), we'll need to discuss how to address this. Currently I have two rough ideas:

Prefer explicit over implicit: We just provide a "specialization" for single-precision inputs wherever create_ufunc or its wrappers are called. This is a bit more laborious but much better for code readability. For example, the line 871 linked above would become

     ('e->e', ('f', 'out0 = sqrtf(in0)'), 'd->d', 'F->F', 'D->D'),

Attach the f suffix for single-precision inputs in the workhorse of create_ufunc: This might be possible, and offers a certain degree of automation, but I'm not yet familiar with ufuncs and elementwise kernels, so hard for me to evaluate its difficulty...

@niboshi, since you are still working on the refactoring #2920, do you have any comment? 🙂 I have not made any serious measurement, so for now I'm just raising the issue for awareness.

I did some tests and realized that for float/double this makes no difference, because CUDA provides overloaded versions for inputs with different precisions, see:
https://docs.nvidia.com/cuda/cuda-math-api/group__CUDA__MATH.html#group__CUDA__MATH
But, I am not so sure about complex float/complex double. Looking into this now...

Looks like the same overloading for complex inputs is done in the Thrust headers! I think we are good. Closing this issue, and sorry for the noise 😅


Is it possible to use env-cmd with docker?

As of now my package.json build script looks like this.
"scripts": {         "build": "env-cmd -e production react-scripts build",     },
the problem is when I run a build through docker I get this error
code ELIFECYCLE
errno 1
env-cmd -e production react-script build
Exit status 1

failed to solve: executor failed running [/bin/sh -c npm run build]: exit code: 1

Is there anyway to use env-cmd with docker-compose?

Hi, the logs in your comment don't actually include the error message. There is likely more information before "ELIFECYCLE"
Could you please provide some more information so that we can help debug this issue?


parser error when node text has format

Error
mm2github.py -w -o /dev/stdout ~/t.mm
Saving file to: /dev/stdout
Traceback (most recent call last):
  File "/opt/homebrew/Caskroom/miniforge/base/bin/mm2github.py", line 48, in <module>
    main(args)
  File "/opt/homebrew/Caskroom/miniforge/base/bin/mm2github.py", line 38, in main
    mm.write_document(outfile)
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.9/site-packages/freeplane_tools/base.py", line 159, in write_document
    fileh.write(self.get_document())
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.9/site-packages/freeplane_tools/github.py", line 46, in get_document
    self._toc(),
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.9/site-packages/freeplane_tools/base.py", line 135, in _toc
    return "\n".join(n.toc_entry for n in self._iternodes() if n.toc_entry)
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.9/site-packages/freeplane_tools/base.py", line 135, in <genexpr>
    return "\n".join(n.toc_entry for n in self._iternodes() if n.toc_entry)
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.9/site-packages/freeplane_tools/base.py", line 107, in toc_entry
    return f"{pad}[{self.text}](#{self._toc_name})"
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.9/site-packages/freeplane_tools/github.py", line 15, in _toc_name
    return re.sub("[^a-zA-Z0-9]", "-", self.text).lower() + "-"
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.9/re.py", line 210, in sub
    return _compile(pattern, flags).sub(repl, string, count)
TypeError: expected string or bytes-like object

node content
<node ID="ID_1521234531" CREATED="1632342121801" MODIFIED="1637123461801"><richcontent TYPE="NODE">

<html>
  <head>

  </head>
  <body>
    <p>
      test text
    </p>
  </body>
</html>
</richcontent>
</node>

I'll take a look at this in the next few days. thanks for submitting a bug report.


French indicator metadata cleanup

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #929

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)

[ ] Link to issue (:issue:number) and pull request (:pull:number) has been added.

[ ] bumpversion patch has been called on this branch
[ ] The relevant author information has been added to .zenodo.json

What kind of change does this PR introduce?

removed a bunch of empty comment strings among the French translations
lots of grammar and phrasing changes to

Does this PR introduce a breaking change?
Yes. Many indicators translated to French will no longer have the same spelling/phrasing in their metadata fields.
Other information:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
18 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.1%) to 90.228%

Files with Coverage Reduction
New Missed Lines
%

xclim/core/locales.py
1
90.2%

xclim/core/units.py
1
89.8%

xclim/indices/fwi.py
1
96.11%

xclim/indices/run_length.py
1
94.61%

xclim/core/indicator.py
2
96.53%

xclim/core/utils.py
12
68.44%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
12604

Relevant Lines:
13969

💛  - Coveralls

@Ouranosinc/xclim-core I wanted to make this clear that we can take some time with this PR (not too much; I would like to get this into v0.32) and also clarify that these changes arose from another project that currently patches most of these problems, so there's no rush related to a project.
The changes here don't have to be extensive; As this is a first pass at fixing many of these inconsistencies, this PR is to get the ball rolling. Please feel free to commit directly to the branch if there are any clear issues. Your comments are appreciated!

Ça serait bien de faire une rencontre (en janvier, pas possible avant) avec vous plus Dominique Paquin pour discuter des points qui ne tiennent pas juste de la grammaire (en dessous, au-dessous) ou les fautes de frappes (dessus/dessous). Les points du genre de la Moyenne de la température moyenne.
Bon pour vous ?

La plateforme de l'ONU est pratique pour ce genre de traductions : https://unterm.un.org/unterm/portal/welcome

Thanks, @RondeauG! I'll open another issue to deal with the trickier comments before merging this.

This PR is complete. It just requires #935 to go in before merging. Thanks for all the great comments!


Update _index.md

👷 Deploy Preview for gladia processing.

Name
Link

🔨 Latest commit
a3f473527b66da1289659f88638e438f576ad441

🔍 Latest deploy log
https://app.netlify.com/sites/gladia/deploys/63e2350fb194be0008b0827f


Release 0.29.0

Targeting the release date for the weekend of June 29.

I'm swamped with work this weekend. Pushing back by 1 week.

Blessing 550477f6d07456a8a7924e4f7a0e81996f405308

Release is underway.

Homebrew PR opened:
https://github.com/Homebrew/homebrew-core/pull/41668

@stefantalpalaru @kamilchm @myfreeweb release is underway

Debian and Windows packages is now available in Bintray.

Gentoo ebuild updated.

COPR build is finished. There was an odd error for Tumbleweed, I've opened an issue for it. No Tumbleweed build for 0.29.0 will be available.

thanks @stefantalpalaru

AppImage is done.

Homebrew PR merged.

Waiting on:

Docker
Playground update
Me writing release notes

Playground updated.

Ubuntu docker images are now available. Alpine should be coming up next.

Docker is done.
Release notes are out. Thanks for playing along folks.

FreeBSD Ports patch posted.


Mismatch in the ‘Block explorer URI API template’ when trying to add a custom chain

I’m trying to run this service locally and add a custom chain. In Step 3 of the process (Add your ChainInfo at http://localhost:8000/cfg/admin/chains/chain/add/), there’s an input field for the Block explorer URI API template.
This field expects the chain’s explorer API to use query parameters like:
https://api-apothem.blocksscan.io/api?module={{module}}&action={{action}}&address={{address}}&apiKey={{apiKey}}.
However, my custom chain uses path parameters instead, such as:
https://explorerapi.wemix.com/api/ext/v1/accounts/{address_hash}/transactions.

Is this field important?
What is the easiest way to resolve this issue?”

Hi @comverser,
That field is used to allow the Safe Web client to build links to block explorers, so no specific format is enforced (the field is just a string) at the infrastructure level. The Config Service also makes the Chain metadata accessible so an arbitrary service can consume this data through its API (Safe Web, Mobile, or any other service). To answer your questions:

This is used to build links to block explorers in the UI, so the importance is relative to how much you need that feature.
I'd say you'd need to adjust the code of the client consuming this data to match the format you put in the field.


Parsing issue

Describe the issue as clearly as possible:
I wanted to run one of the examples.
Steps/code to reproduce the bug:
from enum import Enum
from pydantic import BaseModel, constr

import outlines
import torch

class Weapon(str, Enum):
    sword = "sword"
    axe = "axe"
    mace = "mace"
    spear = "spear"
    bow = "bow"
    crossbow = "crossbow"

class Armor(str, Enum):
    leather = "leather"
    chainmail = "chainmail"
    plate = "plate"

class Character(BaseModel):
    name: constr(max_length=10)
    age: int
    armor: Armor
    weapon: Weapon
    strength: int

model = outlines.models.transformers("gpt2", device="cuda")

# Construct guided sequence generator
generator = outlines.generate.json(model, Character, max_tokens=100)

# Draw a sample
rng = torch.Generator(device="cuda")
rng.manual_seed(789001)

sequence = generator("Give me a character description", rng=rng)
print(sequence)
# {
#   "name": "clerame",
#   "age": 7,
#   "armor": "plate",
#   "weapon": "mace",
#   "strength": 4171
# }

sequence = generator("Give me an interesting character description", rng=rng)
print(sequence)
# {
#   "name": "piggyback",
#   "age": 23,
#   "armor": "chainmail",
#   "weapon": "sword",
#   "strength": 0
# }

parsed = Character.model_validate_json(sequence)
print(parsed)
# name='piggyback' age=23 armor=<Armor.chainmail: 'chainmail'> weapon=<Weapon.sword: 'sword'> strength=0

Expected result:
Just the parsed info.

Error message:
name='El Jinnin' age=12 armor=<Armor.plate: 'plate'> weapon=<Weapon.sword: 'sword'> strength=14
name='Throne of ' age=2013 armor=<Armor.leather: 'leather'> weapon=<Weapon.mace: 'mace'> strength=1024004800000000019100111

Traceback (most recent call last):
  File "/home/conic/llm_experimentation/./outlines_test.py", line 64, in <module>
    parsed = Character.model_validate_json(sequence)
  File "/home/conic/.local/lib/python3.10/site-packages/pydantic/main.py", line 532, in model_validate_json
    return cls.__pydantic_validator__.validate_json(json_data, strict=strict, context=context)
pydantic_core._pydantic_core.ValidationError: 1 validation error for Character
  JSON input should be string, bytes or bytearray [type=json_type, input_value=Character(name='Throne of...24004800000000019100111), input_type=Character]
    For further information visit https://errors.pydantic.dev/2.5/v/json_type

Outlines/Python version information:
File "/home/conic/llm_experimentation/./version_info.py", line 3, in <module>
    import outlines; print("Outlines", outlines.__version__)AttributeError: module 'outlines' has no attribute '__version__'

Context for the issue:
No response

Parsing seems unnecessary, sequence is already of type Character

This is indeed an error in the README, I apologise. We recently made the code output BaseModel instances instead of dictionaries and forgot to reflect this change in the README. Thank you!

Just fixed the example, closing.


Unrecognized Spotify

Spofity not recognized until you push try again button.

Spotify version: <IP_ADDRESS>.g3b5036d6
Windows version: 10.0.14393

Can you verify that it still doesn't load if you wait longer then your 'Lyric refetch rate' setting?

Yes, If I wait longer than refresh rate it works.
Maybe a message like "Detecting Spotify..." is convenient.

thx for reporting.  Can you do a pull on master and try the last version. If it works for you please comment. Thanks.

@jsolisu I'm closing this (I've already changed the message) if you see any problem in lastest release ask for reopenning the issue.


Splat not being passed as Query String

Describe the bug:
Using splat in sending query parameters to a destination doesn't seem to be working.
To reproduce:
Add the following to your netlify.toml:
[[redirects]]
  force = true
  from = "/foo/*"
  status = 301
  to = "/.netlify/functions/bar/?url=:splat"

Create a function with the following:
exports.handler = async ({queryStringParameters}) => {
  return {
    body: JSOSN.strigify(queryStringParameters),
    statusCode: 200
  }
}

The output returns empty.
Configuration
  System:
    OS: macOS 12.2.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 1.44 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.5 - ~/.nvm/versions/node/v14.17.5/bin/node
    npm: 6.14.14 - ~/.nvm/versions/node/v14.17.5/bin/npm
  npmPackages:
    netlify-cli: ^9.4.0 => 9.4.0

Expected behavior
The query string should have some value if the requested URL was /foo/bar/.
CLI Output
N/A
Additional context
N/A

Observations so far: I'm seeing this bug on a local environment with netlify dev on v9.6.4 as well as a local clone of netlify/cli.
It however doesn't seem to be the case in production, testing using code in this repo. For example:

Navigating to https://modest-ardinghelli-177f85.netlify.app/foo redirects to https://modest-ardinghelli-177f85.netlify.app/.netlify/functions/bar/?url= with the value {"url":""}.
Navigating to https://modest-ardinghelli-177f85.netlify.app/foo /bar redirects to https://modest-ardinghelli-177f85.netlify.app/.netlify/functions/bar/?url=bar with the value {"url":"bar"}.

Currently investigating local env behavior.

@jackiewmacharia It seems like this was done intentionally to match old production behaviour.
See https://github.com/netlify/cli/issues/1605
Relevant code is here:
https://github.com/netlify/cli/blob/7b89caf121f77f2343c8057e68d97efbbe5689af/src/utils/proxy.js#L204-L216


Re-layout list editor

The aim of this PR is to improve the UX of the list editor.

The editor now has a left hand side with all items tagged to the item. On the right all lists are displayed. This hopefully improves the understanding of the relationship between the two parts.
Items from the left hand side are only "draggable". Previously it was possible to sort and drag items in this list, causing confusion. It also allows users to add a link to multiple lists, something which
could previously only be achieved by turning off javascript.
When an item is included in one or more lists it is bold
When the user is about to create the first list for a tag we show a special page explaining they're about to change the "sort mode" of the tag. This can be further improved by setting the ordering explicitly - but that's for a later PR.
The layout of the tables is updated to fit more items on the screen and make dragging easier.
Previously, when an item was dragged we calculated the exact rows of that had to be updated. For example, when the user dragged the fifth item in a list of 10 to the fourth place, we would update items 4 through 10. Finding out which items to update turned out to be a fruitful source of bugs and confusion. This behaviour has been changed to always update all items in a list on each update. In the previous example, instead of 4-10, we update 1-10. In a later PR, we should use bulk-updating to the server (which is now not very hard to implement).
Related, keeping data in sync is hard on JS. showEmptyLabels() and redrawUncategorizedList() are purposely "naive". They look at the state of the world and re-render on each update, instead
of trying to only update things that changed, which would be more performant.

Before

After

Review
In a browser. Split view on GH.
Follow ups
Suggested future improvements:

Remove the title column from list_items in the database and only use it from the API.
Save the list items in a bulk ajax call.
Add a filtering box for the tagged items
Add links to tagged items on the site and/or editor (whitehall/publisher)
Add preview of the lists on topics#show and browse_pages#show
Add independent scrolling for the left and right hand side to allow easier dropping.
Set the a-to-z or alphabetical "sort modes" explicitly, instead of letting it depend on tag.lists.any?

I think it would be good to deploy this branch to preview before merging it, and get some of the people who will be using this tool to try it out.  Code review to follow.

This is excellent.


Add support for Parallel NAND Flash

Adds support for 8-bit parallel NAND flash. Includes basic page_read, page_program and block_erase methods.
Tested with a SkyHigh S34ML08G3 SLC NAND

bors ping

bors r+

bors cancel

bors r+

bors retry


fix Edge support for Slider

Without any information on what problem is being fixed merged requests can't be assessed for validity.
Closing this out without merging since no details have been provided as to why it is needed.
Thank you.


Running ide-helper-generate in post-autoload-dump

Versions:

ide-helper Version: v3.6.6
Laravel Version: 8.x
PHP Version: 8.1

Question:
This isn't really an issue with the package but rather a composer questions. In the composer post-autoload-dump scripts we are running @php artisan ide-helper:generate and @php artisan ide-helper:meta so that these are always kept up to date. The issue is that post-autoload-dump is run when using composer install --no-dev - In this event obviously the ide helper package is not installed so it breaks the execution.
Do you know if there is a way to have a separate  post-autoload-dump when running dev and when not running dev. Here is the section for your reference. We obviously don't want to use the --no-scripts option because we need other things to execute.
"scripts": {
    "post-autoload-dump": [
      "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
      "@php artisan package:discover --ansi",
      "@php artisan ide-helper:generate",
      "@php artisan ide-helper:meta"
    ],
    "post-root-package-install": [
      "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
    ],
    "post-create-project-cmd": [
      "@php artisan key:generate --ansi"
    ],
    "test": "./vendor/bin/phpunit"
  }

Hi @TheFrankman,
i fixed this by checking for the APP_ENV environment variable. There might be a better way, but this works for me. In my case the variable will be set by a docker argument during the image creation.
"if [[ ${APP_ENV} == \"local\" ]]; then php artisan ide-helper:generate; fi",
"if [[ ${APP_ENV} == \"local\" ]]; then php artisan ide-helper:meta; fi",

My solution:
"post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi",
            "[ -f .env ] && php artisan ide-helper:generate",
            "[ -f .env ] && php artisan ide-helper:models --nowrite",
            "[ -f .env ] && php artisan ide-helper:meta"
        ]
    },


argument order in location and move different

Why is the order of the arguments different in move and  location?
This is really unintuitive and makes the code really difficult to read. Especially
since move does not even have keyword arguments.

Legacy. I designed location() and later discovered move, which is a built-in capability and so can't have its order changed. We'll correct it in 2.0.

Closing as duplicate of #58


HTTPs should be reported at startup

When we start MP Server, SE WebServer they print out the listen host, port and protocol.
The protocol section (for sure in MP) does not reflect whether the port is secured with TLS, so the address always starts with http://
We should honor TLS configuration of the WebServer, and print https:// in case it is enabled.
Also example may be changed to show https:// in case the configuration is changed to tls (check feasibility, possible API addition, such as WebServer.protocol()).

Also it's prints listening on <IP_ADDRESS>.<IP_ADDRESS>
not <IP_ADDRESS>

Channel '@default' started: [id: 0xf6841beb, L:/0:0:0:0:0:0:0:0:8080]


Figure out why META_ is sometimes prepended to DAMAGE/TARGET

See commit f9ec23d

Fixed in https://github.com/HearthSim/python-hearthstone/commit/a4ef1ec6745bf2ae7375c4f2ea47974d384b5446


Add Widget item delete and sorting functionalities

Issue #:
https://github.com/bcgov/met-public/issues/838
Description of changes:

Add sort_index column for widget items and sort ascending by it
Delete widget items in bulk
update sorting of widget items
Add widget items

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

this is for removing contacts right

Removing widget_items. When we add contacts to a widget we are actually adding widget items with a widget_data_id = contact.id. As for as UI is concerned this is to remove contacts from a widget

Codecov Report

Merging #840 (1de8942) into main (ee7387a) will increase coverage by 0.18%.
The diff coverage is 88.46%.

@@            Coverage Diff             @@
##             main     #840      +/-   ##
==========================================
+ Coverage   72.41%   72.60%   +0.18%
==========================================
  Files         172      172
  Lines        4484     4526      +42
  Branches      294      294
==========================================
+ Hits         3247     3286      +39
- Misses       1199     1202       +3
  Partials       38       38

Flag
Coverage Δ

metapi
78.43% <88.46%> (+0.24%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

met-api/src/met_api/models/widget.py
86.48% <ø> (ø)

met-api/src/met_api/models/widget_item.py
82.60% <71.42%> (-1.77%)
:arrow_down:

met-api/src/met_api/services/widget_service.py
88.33% <94.11%> (+9.54%)
:arrow_up:

met-api/src/met_api/resources/widget.py
76.19% <100.00%> (ø)

met-api/src/met_api/schemas/widget_item.py
100.00% <100.00%> (ø)


Tooltip options not working

I'm trying to set tooltip options and use callbacks, and they aren't doing anything.
As you can see in the below code, I set the caret size to 0 pixels and also add a title callback. However, on my chart, the caret size stays normal and the callback is not run - "test" is not printed to the console, despite the console.log("test")
const chart = {
            id: 'chart',
            type: 'bubble',
            options: {
                maintainAspectRatio: false,
                tooltips: {
                    caretSize: 0,
                    callbacks: {
                        title: (tooltipItem, data) => {
                            console.log("test");

                            let dataPoint = data["datasets"][tooltipItem["datasetIndex"]][tooltipItem["dataIndex"]];

                            let satelliteAName = dataPoint["satelliteA"]["OBJECT_NAME"];
                            let satelliteBName = dataPoint["satelliteB"]["OBJECT_NAME"];

                            return satelliteAName + " and " + satelliteBName;
                        },
                        label: (tooltipItem, data) => {},
                        afterLabel: (tooltipItem, data) => {},
                    },

                }
            },
            data: {
                datasets: [
                    {
                        label: 'Velocity < x',
                        data: conjunctionData,
                        backgroundColor: 'rgb(255, 99, 132)'
                    }
                ]
            }
        }

Does anyone know what might be happening?

Tooltip configs are under the options.plugins key in ChartJS 3. https://www.chartjs.org/docs/latest/configuration/tooltip.html#tooltip-configuration
Example:
options: {
        plugins: {
          tooltip: {
            enabled: true,
            callbacks: {
              title() {
                return 'WOOOOOOOOOOOOOOOO'
              }
            }
          }
        }
      }

@J-T-McC thanks for your help!


[1.3] Out-of-Range Problems in Various color control cluster

Reproduction steps
When there are constraints for transaction time (0-65534) and the OptionsMask and OptionsOverride (which are restricted to 0-1) in specification, but there is no restriction in the implementation code. Thus, values such as 65535 and 3 could work normally.

MoveToHue Command has an out-of-range problem
There is no constraint check for field 2 (Transaction Time). The normal range is 0-65534.
./chip-tool any command-by-id 0x0300 0x00 '{"0":254,"1":2,"2":65535}' 0x654324 1

MoveHue Command has an out-of-range problem
There are no constraint checks for field 2 and field 3.
./chip-tool any command-by-id 0x0300 0x01 '{"0":3,"1":3,"2":3,"3":3}' 0x654324 1

StepHue Command has an out-of-range problem
There are no constraint checks for field 3 and field 4.

MoveToSaturation Command has an out-of-range problem
There are no constraint checks for field 1, field 2, and field 3.
./chip-tool any command-by-id 0x0300 0x03 '{"0":254,"1":65535,"2":3,"3":3}' 0x654324 1

MoveSaturation Command has an out-of-range problem
There are no constraint checks for field 2 and field 3.
./chip-tool any command-by-id 0x0300 0x04 '{"0":3,"1":1,"2":3,"3":3}' 0x654324 1

StepSaturation Command has an out-of-range problem
There are no constraint checks for field 3 and field 4.

MoveToHueAndSaturation Command has an out-of-range problem
There are no constraint checks for field 1, field 3, and field 4.
./chip-tool any command-by-id 0x0300 0x06 '{"0":254,"1":254,"2":65535,"3":3,"4":3}' 0x654324 1

MoveToColor Command has an out-of-range problem
There is no constraint check for field 2.
./chip-tool any command-by-id 0x0300 0x07 '{"0":65279,"1":65279,"2":65535,"3":3,"4":3}' 0x654324 1

....
Bug prevalence
each time
GitHub hash of the SDK that was being used
561d23d0db215a99705ff0696e73853c8edf11b2
Platform
other, core
Platform Version(s)
1.3
Type
Common Cluster Logic, Spec Compliance Issue
Anything else?
No response

@jmartinez-silabs

PR to add constraint check to the required arguments on the cluster server implementation.
Note:  OptionsMask and OptionsOverride are bit fields and are not constrained in the defined fields. The undefined fields are ignored by the server per spec.
It was also discussed that it was valid for Chip-tool, as a testing tool, to send out-of-range values as it can add negative tests against server implementations.


tests: check midstream exception policy in 6 - v1

Related to
Bug #5825
Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/6035

Replaced by https://github.com/OISF/suricata-verify/pull/1294


Best way to acquire date and time?

I'm currently working on building an IoT product based on this platform and the ESP32 hardware. In my application I need to know what the current time is (actual date and time). I see that I can call gettimeofday from time.h and that returns the number of seconds since the board was powered on.  However, for that to be useful I think I need to call settimeofday with the number of seconds since unix epoch.  So I'm trying to work out the easiest way to get that value. It is my understanding that the device must already be getting the date and time (using sntp?) in order to handle the x.509 certificates.  If that is indeed the case, is there any way to leverage/access that datetime that is acquired in my application?

If your device will have a reliable connection to a time server, then you could add NTP logic. However, even if you can assume that a time server is available to your devices in deployment, there are documented spoofing threats to NTP that can be tough to mitigate, especially in the context of IoT.
The default software based implementation of TLS sockets in Amazon FreeRTOS does not perform certificate revocation checking. During TLS handshakes, it does a best-effort time validity check on server certificates based on the host image build time. Neither approach is ideal; if you can take a dependency on NTP, then I agree that it's worth considering.

Thanks for the response. When you say, "based on the host image build time", what is the host that you're referring to?

The build machine. Please take a look at https://github.com/aws/amazon-freertos/blob/master/lib/tls/aws_tls.c#L212.

Ok. Thanks for the link.
So does that mean that a firmware image build on this essentially has a shelf life? Do you know how long the certs that are generated by AWS are good for?
Feel free to close this issue after responding. Thanks.

That code checks that the server certificate hadn't already expired by the time the firmware image was built. It's a best-effort/worst-case sort of thing.
Regarding the various root certificates used by AWS IoT servers, please see https://docs.aws.amazon.com/iot/latest/developerguide/managing-device-certs.html.
Regarding "Thing"/client certificates issued by AWS IoT for device testing, those appear to be valid until 2049.


disable framerate limit for browsers

add --disable-frame-rate-limit for chromium-based browsers. (for both autostarts and app menu entries)

Unstable


Add tests for solvent writers

Description
The classes that write solvent templates need to be tested. We can start by adding a test for the new OPLSOBC. Besides, a test for the OBC2 should also be added.

Support
I attach the templates to be used as reference when validating OPLSOBC: OBC_for_OPLS_test.zip

To validate  OPLOBC template writer:
from peleffy.tests.test_solvent import TestSolvent

test = TestSolvent()
test.test_OBCOPLS_writer()


help with auth settings for Firebase app

This is absolutely amazing and speeds up my development time. However, some of my endpoints require authentication through Firebase's email-and-password auth service. I can't use a service account because I need a user to be logged in (to get their UID etc),
Anyone have an idea about how I can set this up?

If it uses OAuth 2.0 you should be able to use insomnia’s OAuth support.
Sent with GitHawk

Is there a guide somewhere? I'm just unsure where to fet all the info to fill into the Insomnia settings.

On Sep 26, 2018, at 2:10 PM, Gregory Schier<EMAIL_ADDRESS>wrote:
If it uses OAuth 2.0 you should be able to use insomnia’s OAuth support.
Sent with GitHawk
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

It really depends on the type of auth you need. I'm not familiar with Firebase auth. If you could provide some more details on this then I could offer some advice.
A while ago I did write a blog post on the OAuth 2.0 stuff but it was for the GitHub API. Might still be worth a read to understand how it works. Again, this will only be relevant if FB supports OAuth 2.0 https://insomnia.rest/blog/oauth2-github-api/

For anyone still struggling with this issue, I wrote an article on it here. Hope this helps.
https://medium.com/@josh-richards/using-firebase-auth-in-insomnia-7a43fb92a8f8


Theme for Alacritty?

I absolutely love this theme and I was wondering if you'd be willing to port it to Alacritty (terminal emulator)?

Hi ! Yeah, I'll look into it! :)

You'll find below a first draft you can paste in your .alacritty.yml, let me know if it is ok. Do not hesitate to let me know if I can improve it in any way! :)
# Colors (Night Shift)
colors:
  primary:
    background: "#1b222d"
    foreground: "#fff9ee"
  search:
    matches:
      foreground: "#1b222d"
      background: "#fff9ee"
    focused_match:
      foreground: "#1b222d"
      background: "#7eddde"
    bar:
      background: "#ffd484"
      foreground: "#1b222d"
  hints:
    start:
      foreground: "#1b222d"
      background: "#fff9ee"
    end:
      foreground: "#fff9ee"
      background: "#1b222d"
  normal:
    black: "#1b222d"
    red: "#e78482"
    green: "#8fc8bb"
    yellow: "#ffd484"
    blue: "#6db3ce"
    magenta: "#ad82cb"
    cyan: "#7eddde"
    white: "#fff9ee"
  bright:
    black: "#1b222d"
    red: "#e78482"
    green: "#8fc8bb"
    yellow: "#ffd484"
    blue: "#6db3ce"
    magenta: "#ad82cb"
    cyan: "#7eddde"
    white: "#fff9ee"

Thank you so much for getting back so fast!! it looks absolutely beautiful :)
Although, it doesn't seem to be working with auto-suggestions for zsh but I'm not sure if that's an issue with the zsh plugin or the theme

Indeed, this is a settings you need to set in your .zshrc/.bashrc:
ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE="fg=#484848"


Cleaned up code, Cleaned up ReadMe, etc.

sexy.

yo! thanks for the pr, i'll check it out in a bit

alr ty for the pr once again, merging

alr ty for the pr once again, merging

np :)


Remove default port from grpc ChannelOptions

URIs should always specify a port.  If they don't, a ValueError will be raised.
Closes #80

Draft because this is based on #79

But for subclasses, where we will probably have well defined service locations, it might make sense to have a default port and only leave a floating address

People can type the ports themselves.  We are only introducing opportunities to fail, by providing defaults.

(I can see the case for that if you want to change between staging and production for example).

This example sounds particularly dangerous to me, relying on defaults for switching between staging and production is a definite way to mess things up.
Saving a few keystrokes to type the ports is not worth the risks/complications having a default would introduce.

It's not about saving keystrokes, it's about making the usage easier.
Optimally, the end user only needs to know dispatch.frequenz.io (or whatever url we use) and the client fills in port/encryption etc automatically.
For staging, of course a different domain would be better dispatch.staging.frequenz.io for example) but I am working with what I got and that's just one server/ip/domain currently ;)

Yeah, I'm even thinking about what if we want to have different versions of an API running in different ports. A service (client) could known which port uses each version, and try to find first the latest version and only connect to older versions if unavailable. I can really see use cases for letting the client chose the port (i.e. using a default). I agree is not about saving keystrokes, is about abstraction.

This example sounds particularly dangerous to me, relying on defaults for switching between staging and production is a definite way to mess things up.

How is it dangerous? Is not relying on defaults, is using different host names, user-provided host names, is using the DNS to look for a particular instance.

There is a reason why port numbers are standarized, the whole IANA thing. Ports do have meaning, even if you could use a non-standard one.
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml

Fine, let me get out of the way then.

I still see value in part of the PR, I don't think the base client should set a default port, it should just allow clients to set one. If some concrete client think it is best not to provide a default port, they can do so, and that will actually be the default.
I don't know why the door slam :worried:

To me it is always better to be explicit, users are going to copy-paste the urls anyway, I don't see how this is useful, and but I think it could mess things up if multiple services are running on the same domain name, like for different users, etc., which we already have examples for.

I agree with all of this, but still in general URLs allow omitting the port, and this is still a general purpose library (even when it might be a bit specific to our use case). With the PR I'm proposing, the default is still to require an explicit port, but if some client thinks a default port makes sense, they can do so. So unless some downstream project explicitly defines a default port, it will be required. If a downstream project goes to the trouble of setting a default, I would trust they know what they are doing. For sure it exist cases for using default ports, they are used everywhere (most services we use on a daily basis have a default port) and they are not required by the URL/URI standard. So I think it makes sense to leave the door open in this library, but go with a safe default.

No, of course not, more like a door opening. It looks like the majority thinks it is nice to have, so I won't block you, but I'd rather not do it myself.

:+1:


Link to MrHaki's blog in TupleConstructor javadoc.

As discussed on Twitter, here's an example of linking to @mrhaki's blog from the javadocs so that people have ready access to more examples for certain classes. If this gets merged, I'll look into adding more.

Thanks for the pull request.
Cédric commented on it on the developer mailing list:

I don't think linking to external resources like this is a good idea. We
don't own the end link, it can be dead very easily, especially in the
future. I would rather improve the documentation.

http://mail-archives.apache.org/mod_mbox/groovy-dev/201602.mbox/<CADQzvmknP1LUd_VLX8ymQtEJdXq5Mm0HzfSdNGMQPzi5%2BK_GaQ%40mail.gmail.com>


Custom line ending

HI there, it would be good if you enable a custom line ending character to be passed in the array of params when creating the Converter.

Enabled since 0.4.3:
added "eol" param


chore: improve demo and build

now the try online is working
improve test
change the tabs from radio buttons to anchors so we can use inline anchors
add back some steps to the pipeline

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: deprecate inconsistent config param case

Summary
fixes #3673
Currently, exposed configuration parameters are using both camelCase and snake_case.
This fixes deprecated the camelCase parameters and introduces its snake_case equivalent, while also maintaining backward compatibility
Test plan
Updated the config.yml files inside dev-test directory to use snake_case for all parameters
A picture of a cute animal (not mandatory but encouraged)

@erezrokah Do you know where is the test cases for widget config validation? So I can write the cases for requiring either new casing or old casing

No existing test cases for specific widget schemas yet.
You can see the tests for core schema here:
https://github.com/netlify/netlify-cms/blob/4b487870c631b5e829329441d6a03b86c398affc/packages/netlify-cms-core/src/constants/__tests__/configSchema.spec.js#L6
and could add similar tests in each widget package if you'd like.

Thanks @andreascm, I added a commit with some small changes/fix https://github.com/netlify/netlify-cms/pull/4172/commits/955cc77a9dc189b8f310a31446dda040dd895bdf.
If you're happy with it I think this is ready to merge

Hi @erezrokah , yes I'm good with that. I didn't realize there are some config left over and deprecation notice that needs to be added, so thank you for the fix!


Rework documentation index page

Goals

Make sure the documentation is primarily focused on users (developers of RTD are secondary or lower)
Explain the various sections in a bit more detail and guide users better than a simple toctree
At this stage, I was not attempting to significantly restructure, rewrite, or remove any docs.

This structure was influenced heavily by the Django documentation but I definitely referred to other documentation including for Travis, CircleCI, and Heroku.
Fixes: #5675
Fixes: #2667

At this stage, I was not attempting to significantly restructure, rewrite, or remove any docs.

I think this stage will be covered by #5771 and now we can care about the first steps that you are doing here.

Before this is merged, I'm going to try to do a couple things. I should have them done today:

Move a few things (vcs, conda, etc.) under guides
Move developer documentation under contributing

I did some minor moving things around but we should probably setup a few redirects once this is deployed (not just merged but deployed to /en/stable):
Guides that moved

/canonical.html -> /guides/canonical.html
/conda.html -> /guides/conda.html
/vcs.html -> /guides/vcs.html

Development docs that moved

/design.html -> /development/design.html
/design/apiv3.html -> /development/design/apiv3.html
/design/in-doc-search-ui.html -> /development/design/in-doc-search-ui.html
/design/index.html -> /development/design/index.html
/design/pr-builder.html -> /development/design/pr-builder.html
/design/theme-context.html -> /development/design/theme-context.html
/design/yaml-file.html -> /development/design/yaml-file.html
/docs.html -> /development/docs.html
/i18n.html -> /development/i18n.html
/install.html -> /development/install.html
/issue-labels.html -> /development/issue-labels.html
/settings.html -> /development/settings.html
/symlinks.html -> /development/symlinks.html
/tests.html -> /development/tests.html

This also closes https://github.com/rtfd/readthedocs.org/issues/2667 because it removed the embed API docs which were broken.

We also should redirect /en/latest/ as well :/

We also should redirect /en/latest/ as well :/

Do you mean to redirect /en/latest to /en/stable?

No, we need to also add those redirects to the latest version.

Currently, when setting a page redirect, it applies to all versions:

Sounds good -- I'm happy to ship this once the redirects are in place. 👍


Confusing statement, please recheck

This sentence is confusing and possibly grammatically incorrect:
"Sending them to the Azure Monitor Logs store (which is searchable via Log Analytics) you to integrate them into queries which search across other logs."
You should be able to read a sentence without the section defined by the parentheses, and it should still make sense. With or Without the section in the parentheses, this sentence doesn't convey exactly what's happening.

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

ID: 0ca576e1-fafa-3a02-6d29-394f342bc737
Version Independent ID: a6a83de5-41fd-2dce-eb86-cee6c086c07d
Content: Create diagnostic settings to send platform logs and metrics to different destinations - Azure Monitor
Content Source: articles/azure-monitor/platform/diagnostic-settings.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@savas-guven Thanks for your comment! We will review and provide an update as appropriate.

@savas-guven Good catch! I have verified and updated the document as required i.e.,
from - "Sending them to the Azure Monitor Logs store (which is searchable via Log Analytics) you to integrate them into queries which search across other logs."
to - "Sending them to the Azure Monitor Logs store (which is searchable via Log Analytics) helps you to integrate them into queries which search across other logs."
The update should go live soon i.e., in less than 24 hours. If there are further questions regarding this matter or feedback on the referred Azure documentation, please do let us know and we will gladly continue the discussion.

At this point it appears that there's no edits or updates needed for the referred Azure documentation so closing this issue for now.
If there are further questions regarding this matter or feedback on the referred Azure documentation, please do let us know and we will gladly continue the discussion.


Support Windows

Windows has no nanosleep function.
There is WaitableTimer for high precision (100ns) sleep in Windows:
https://stackoverflow.com/questions/5801813/c-usleep-is-obsolete-workarounds-for-windows-mingw/17283549#17283549
http://www.windowstimestamp.com/description#C_2
Using the WinAPI calls would also require to add support for them in https://github.com/retep998/winapi-rs or reinvent the wheel here.
If you just need cross platform support a fallback to std::thread::sleep on unsupported platforms may also be an option.


Feature Request: Please publish the extension

First, thanks for this! This extension has already been helpful to me and lends legitimacy to nbdev, and using nbdev with VSCode. In fact, I created a starter-project nbdev template that installs this extension. Of course it installs this extension using wget, and I need to keep it updated as the vsix gets updated. I'd rather just mark this  as a recommended extension and let everything else take care of itself.
Would a pull request help out here?
https://code.visualstudio.com/api/working-with-extensions/publishing-extension

I can do it :)  After you confirm that the auto-complete works for you on the other issue, I feel like I have enough features to publish.  LMK!

Published https://marketplace.visualstudio.com/items?itemName=hamelhusain.nbdev
Looks like I can run the commands

vsce package to build the extension file
vsce publish to publish (this also packages things)


Add long arguments to options

I've come across a few cases where I'd like to use long arguments when calling ghp-import for better readability.
@davisp do these long names look good to you?

0.5.5 includes these and should be on pypi now.


Edit vale config to be less noisy

Turns off some of the noisier and less important rules

cc @loopDelicious


Peers screen: Improve responsive display

The problem
The current-state Peers screen looks fine at wide desktop resolutions (below, 1440px wide) ...

However, both the map and the peers table deteriorate significantly at narrower widths, regardless of height:

768px wide (table columns start to break):

425px wide (map cropped horizontally, table unusable):

Additionally, map display degrades substantially at non-16x9ish aspect ratios due to the map dimensions being pegged to percentage of total screen height:

1024x385 (map unusably small, gets lost in its surrounding white space):

320x911 (map unusably cropped):

Need in brief
Improve the responsive display of the Peers screen so both the map and the table are as functional at mobile widths and unusual aspect ratios as they are in the standard 16x9, 1440px+ display. This is likely to (but will not necessarily) include:

Mobile-friendly (e.g. pinch + scale button) zoom/pan controls for peers map
Side-scroll for peers table

Please note that react-virtualized is used not only for the table on the Peers screen, but also for tables on other screens of the app. If replacing react-virtualized is part of a proposed solution, please also solve for how to implement elsewhere in Web UI.
Acceptance criteria
Solution must ...

Not sacrifice any functionality of full-sized display
Gracefully adjust when aspect ratio and display dimensions are resized (e.g. from portrait to landscape on a phone/tablet)
Display gracefully at and between the following display widths:

320x568 (small phone portrait)
568x320 (small phone landscape)
375x667 (medium phone portrait)
667x375 (medium phone landscape)
414x736 (large phone portrait)
736x414 (large phone landscape)
768x1024 (small tablet portrait)
1024x768 (small tablet landscape)

Display as gracefully as possible at extreme desktop-browser-window aspect ratios (e.g. but not limited to 400x1200, 1200x400, etc)

@lidel and @rafaelramalho19 -- thoughts on this issue's definition and acceptance criteria for potential inclusion on the bounty board?

@jessicaschilling apologies, missed this one. I think this makes a perfect bounty, but to avoid duplicated work,  would wait until we land #1602/#1616, and then see if acceptance criteria still make sense  with the more dense table.

+1. I suspect we'll need side-scroll on this table regardless of where we come out with those issues, but good plan.