Add charset option

When I fetch some data that contains accents of all sorts (hey, don't judge me, I speak french), the returned result messes up all the accents.
I have this piece of code client-side that fixes some problems, but it can't fix data coming back from the server:
$.ajaxSetup({     scriptCharset: "utf-8",     contentType: "application/json; charset=utf-8" });
That would be a very nice addon to your awesome proxy.

Max

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38117789-add-charset-option?utm_campaign=plugin&utm_content=tracker%2F12536595&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F12536595&utm_medium=issues&utm_source=github).

Thanks for the suggestion! I've put it on the planning board for v2 of the service. :)


Improve ClinGen support - Mondo subset (EPIC)

We do not have a definitive solution yet for ClinGen, but we will pursue the following paths:

Add a release product (subset) to Mondo which contains only the information relevant to ClinGen (genes, diseases), with a special feature which is that the canonical "Mondo" labels are swapped with the corresponding clingen preferred labels (aka ClinGen subset)

Deploy the subset on Monarch OLS so that it is easily browsable by ClinGen curators
Export a table which contains three columns: Mondo ID, canonical label, ClinGen preferred labels, for all terms in the ClinGen subset (as an easy way to access the ClinGen subset).

Make it easier to retrieve synonym types from the Monarch API
ClinGen will curate the ClinGen subset autonomously (the list of diseases and genes to be included in the clingen subset)

Related issues to keep track off:

[ ] https://github.com/monarch-initiative/mondo/issues/7027
[ ] https://github.com/monarch-initiative/monarch-app/issues/500 (an issue to request adding synonymtype retrieval to Monarch API)

This issue will continue to evolve.
Questions for ClinGen
@courtneythaxton

Currently the terms (labels) of diseases that are used (preferred) by ClinGen are tagged with CLINGEN_PREFERRED. Would you like to keep that tag, or rename it?
Currently, the CLINGEN_PREFERRED tag and the clingen subset are deleted from Mondo before a release. I don't remember the context of this decision, but there must have been some encouragement from someone in your organisation to drop this distinction. Can we reinstate these after our discussion on Monday?

@matentzn Thank you for starting this ticket. I am checking back within ClinGen about your questions of changing the clingen_preferred label, and whether we can reinstate this. I will get back to you as soon as I can.

@matentzn I was able to talk with Jonathan Berg and Bradford Powell (@bpow) .
If we could please update the CLINGEN_PREFERRED to a title of CLINGEN_LABEL, we would appreciate it. Also, with this update, we approve the reinstatement of the CLINGEN_LABEL release. Ideally, we can work on updating the current CLINGEN_LABEL with the proposed list (#3 above).
I plan to talk with the ClinGen Data Platform WG (DPWG) leads more on this topic, but as I understand, this autonomously maintained list by ClinGen would still be hosted by Mondo, correct? I want to make sure that if the question of provenance arises, that I am prepared with discussing all options :). I will also plan to loop you all in for later discussions and clarifications with the DPWG.
Please let me know if you need anything else.

@courtneythaxton excellent, thank you. In this PR #7112 we rename the CLINGEN_PREFERRED to CLINGEN_LABEL and reinstate it into the pipeline!


make array entities non-nullable

For example change childs: [Court!] and other similar cases to childs: [Court!]!  to get rid of unnecessary null checks (it changes the type from Array<string> | null to Array<string>)

childs was already fixe in #13
But there are other arrays that need this change


Show all meetings in a specified year

We can do this a couple ways:
(1) Revert to the original dropdown, but with an option to select a single year.
(2) Give the calendar a range...see this commit: https://github.com/datamade/la-metro-councilmatic/commit/295fb9140ac9c8abe9e3d53d0d1e1bccd0a66012

We will use the later (show the calendar range).

Calendar range added!


💅 Logo early preview and feedback

I'm working on the tsx logo and I'm looking for some early feedback
I opened a PR in the sponsors-only development repo: https://github.com/pvtnbr/tsx/pull/1
If you're a tsx fan, I'd love for you to chime in 🙌 ❤
If you're not a sponsor yet, my sponsorship program is only $2/month.
Please join—your support will go a long way! 🚀

Logo has been released!


Can't copy text of relation member names

Here the text I want to copy, 天輪-翁子線,  is sitting in front of me,

but there is no easy way to copy it with the mouse.
Sure, I could get it from elsewhere, but still...
Poking around in the "v" menus doesn't find it either.

@jidanni What browser are you using? I'm able to select and copy the text in Firefox and Safari on macOS.

Closing this in favor of #8136, but more info would still be useful if you have it @jidanni.

Even in Firefox,

Browse https://www.openstreetmap.org/edit?relation=5668778
Try to copy any text out of any of the Members
You end up grabbing the whole member and reordering it

That is because instead of just giving a "reordering handle to grab on"
on the edge of each member, somebody has made the whole member its own handle.

Looks like this is a "feature" of Power Route relations. I can reorder the relation members in this way with other power routes as well - and accordingly cannot copy the relation member names.
Definitely NOT the same issue as #8136, and this probably deserves to be reopened.
BUT... I really like the ability to reorder relation members here. Would be great if this state were toggle-able for all "route" relations. Flip a bit and you wouldn't be able to reorder the relation members, but you could now copy their names.

I defend the right of anybody to reorder relations.
They just need little handles added to them, for users to grab on and pull them around.
The 'lazy' way is to forget the handles, and make the whole item one big handle.
With the concurrent loss of Accessibility as the price.

Here on my Zenfone, grabbing the hamburger icon does the trick_

@jidanni Oh okay, I think I was looking at the Relations section by mistake, not the Members section.


Rename "opengpg-interop" to "openpgp-interop"

i think this directory name was just a typo

thanks


Assert child count in mangleDependentGenericConformanceRequirement

From LLDB, we've seen crash instances where mangleDependentGenericConformanceRequirement segfaults when reading node->getChild(1).
This change introduces a DEMANGLER_ASSERT that verifies the input node has two children, which the surrounding code implicitly assumes.
rdar://78025198

@swift-ci test

@swift-ci test Windows Platform


Can you release  pre-training code of CodeT5?

Hi!
I would like to know how methods like MIP(Masked Identifier Prediction), IT(Identifier Tagging), BDG(Bimodal Dual Generation) etc are implemented. I'd appreciate it if you release pre-training code of CodeT5.

你好，你的邮件我已收到，我会尽快查看~~~

Hi, we do not have a plan to release the pretraining code so far.


torch_dreams incompatible with single channel input

For now, torch_dreams only supports RGB images. Need to add an optional argument to support single input channel models.

There were some errors when someone directly tried to do gradient ascent on the the single channel tensor, this was because I lazily wrote used squeeze() which converted a 4d tensor of size [1,1,20,20] to [20,20]. While the expected size was [1,20,20].


TestHelper "createProxy" does not create unique proxies.

This is a quirky issue, and maybe I am overlooking something here:
Expected Behavior
When I create multiple proxies in a test using the testhelper's 'createProxy()' function, I expect that each proxy created is unique (deployed at a different address).
Current Behavior
When creating multiple proxies of the same contract inside a it() block (or even creating one inside a beforeEach and one inside an it() block) the resulting proxies are identical.
When following the documentation here: https://docs.zeppelinos.org/docs/testing.html
If I attempt to create two proxies in a single it() block, the second proxy has the same address as the first- they are identical.
Example:
  it("should create two proxies", async function() {
    const proxy1 = await this.project.createProxy(Sample);
    const proxy2 = await this.project.createProxy(Sample);

    const add1 = proxy1.address;
    const add2 = proxy2.address;
    console.log(add1, " ", add2);
    add1.should.eq(add2);
  });

In this case, this test will pass, and the addresses from the console.log will be identical.
My complete test code is:
Note the commented out Sample2 variable.  However, I am not clear of what the behavior is in this case. I would expect createProxy(Sample) to generate me a unique proxy each time.
const { TestHelper } = require("zos");
const { Contracts, ZWeb3 } = require("zos-lib");

ZWeb3.initialize(web3.currentProvider);

const Sample = Contracts.getFromLocal("Sample");
// const Sample2 = Contracts.getFromLocal("Sample");
const ERC20 = Contracts.getFromNodeModules("openzeppelin-eth", "ERC20");

require("chai").should();

contract("Sample", function() {
  beforeEach(async function() {
    this.project = await TestHelper();
  });

  it("should create two proxies", async function() {
    const proxy1 = await this.project.createProxy(Sample);
    const proxy2 = await this.project.createProxy(Sample);

    const add1 = proxy1.address;
    const add2 = proxy2.address;
    //console.log(proxy1);
    console.log(add1, " ", add2);
    proxy1.should.eq(proxy2);
  });
});

Fixed by #810


Cannot attach Cosmos DB and hit:"Error: If you see this message please contact SupportHub"

After installing the Azure Databases extension in VS Code, tried to attach the Cosmos DB account but with hitting below error message.
"cannot attach Cosmos DB and hit:"Error: If you see this message please contact SupportHub"

Attach other Azure resources worked fine. May I know is there any idea for this issue? May I know how to mitigate it.

This message is not generated through the extension. This might be generated due to a corporate proxy.

@Shawngbk are we good to close this issue?


[BUG] Predict residuals error with hierarchical forecaster

Describe the bug

The predict_residuals function doesn't work for me when the forecaster is hierarchical/panel type
To Reproduce

from sktime.forecasting.base import ForecastingHorizon
from sktime.forecasting.exp_smoothing import ExponentialSmoothing
from sktime.utils._testing.hierarchical import _bottom_hier_datagen

# generate a 3 node hierarchy ts
y = _bottom_hier_datagen(
    no_bottom_nodes=3,
    no_levels=1,
    random_seed=111,
)
fh = ForecastingHorizon([1, 2], is_relative=True)

# forecast all levels
forecaster = ExponentialSmoothing(trend="add", seasonal="additive", sp=12)
forecaster.fit(y)
# error to do with fh
print(forecaster.predict_residuals(y))

Expected behavior

Same behavior as for a single level, except returns a multi-index object
# forecast one level works fine
y_single = y.loc[("l1_node01")]
forecaster = ExponentialSmoothing(trend="add", seasonal="additive", sp=12)
forecaster.fit(y_single)
# works fine
print(forecaster.predict_residuals(y_single))

Additional context

Workaround for now

fh_resid = ForecastingHorizon(
    y.index.get_level_values(-1).unique(), is_relative=False
)
resid = y - forecaster.predict(fh=fh_resid)
print(resid)

Versions

System:
python: 3.8.12 (default, Oct 12 2021, 03:01:40) [MSC v.1916 64 bit (AMD64)]
executable: C:\Users\ciaran-g\Anaconda3\envs\sktime-dev\python.exe
machine: Windows-10-10.0.19042-SP0
Python dependencies:
pip: 21.2.2
setuptools: 58.0.4
sklearn: 1.0.2
sktime: 0.11.4
statsmodels: 0.13.1
numpy: 1.21.5
scipy: 1.7.3
pandas: 1.3.5
matplotlib: 3.5.0
joblib: 1.1.0
numba: 0.55.1
pmdarima: 1.8.4
tsfresh: 0.19.0

do you understand the nature of the bug, given that your workaround works?
Maybe the fix is really easy?

confirmed with python 3.9


Cannot return a value from models.llamacpp

Describe the issue as clearly as possible:
Consider the following code:
from outlines import models

# No error
models.llamacpp(
      repo_id="M4-ai/TinyMistral-248M-v2-Instruct-GGUF",
      filename="TinyMistral-248M-v2-Instruct.Q4_K_M.gguf",
)

# No error. Output: <outlines.models.llamacpp.LlamaCpp object at 0x1052ebc10>
print("==>", models.llamacpp(
      repo_id="M4-ai/TinyMistral-248M-v2-Instruct-GGUF",
      filename="TinyMistral-248M-v2-Instruct.Q4_K_M.gguf",
))

# Error 'NoneType' object is not callable
model = models.llamacpp(
      repo_id="M4-ai/TinyMistral-248M-v2-Instruct-GGUF",
      filename="TinyMistral-248M-v2-Instruct.Q4_K_M.gguf",
)

An error is produced when assigning the return value of models.llamacpp to the variable model (third case above). The error does not occur when the return value is not assigned or when it is printed. Is this expected behavior? If it is, this behavior is not documented. Furthermore, the test suite (test_integration_llamacpp.py) does not appear to test for this case. How do I proceed?
Suggestion: in the documented examples, could you state the version of Outlines that example is meant to work with? Breaking changes occur on a regular basis, which might prevent examples from being duplicated easily. Thanks.
Steps/code to reproduce the bug:
from outlines import models

# Error 'NoneType' object is not callable
model = models.llamacpp(
      repo_id="M4-ai/TinyMistral-248M-v2-Instruct-GGUF",
      filename="TinyMistral-248M-v2-Instruct.Q4_K_M.gguf",
)

Expected result:
The code should output normally with no output.

Error message:
Traceback (most recent call last):
  File "/Users/erlebach/src/2024/my_llama_cpp-python/.venv/lib/python3.10/site-packages/llama_cpp/llama.py", line 2201, in __del__
  File "/Users/erlebach/src/2024/my_llama_cpp-python/.venv/lib/python3.10/site-packages/llama_cpp/llama.py", line 2198, in close
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 584, in close
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 576, in __exit__
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 561, in __exit__
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 340, in __exit__
  File "/Users/erlebach/src/2024/my_llama_cpp-python/.venv/lib/python3.10/site-packages/llama_cpp/_internals.py", line 69, in close
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 584, in close
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 576, in __exit__
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 561, in __exit__
  File "/Users/erlebach/opt/miniconda3/lib/python3.10/contextlib.py", line 449, in _exit_wrapper
  File "/Users/erlebach/src/2024/my_llama_cpp-python/.venv/lib/python3.10/site-packages/llama_cpp/_internals.py", line 63, in free_model
TypeError: 'NoneType' object is not callable

Outlines/Python version information:
Version information

```
0.1.5
Python 3.10.10 (main, Mar 21 2023, 13:41:05) [Clang 14.0.6 ]
```

Context for the issue:
I cannot duplicate the documented examples, or some of the testing modules.

Here is a solution to the problem in the form of a PR, which is undocumented. I found this with the help of Sonnet 3.5 . Could somebody please reply to this and explain why the provided examples in Outlines work for you? Thanks.
Title: Fix llama.cpp cleanup and generator usage pattern
Description
This PR addresses two issues:

The cleanup error with llama.cpp models when assigning to variables
The proper way to use generators with parameters in Outlines

Changes
Changed from problematic pattern in ex5.py:
# DON'T DO THIS - Will cause cleanup issues
m = models.llamacpp(
    repo_id="M4-ai/TinyMistral-248M-v2-Instruct-GGUF",
    filename="TinyMistral-248M-v2-Instruct.Q4_K_M.gguf",
)

To proper cleanup pattern in ex6.py:
import os
from outlines import models, generate
from dotenv import load_dotenv
import torch

load_dotenv()
hf_token = os.getenv("HF_API_TOKEN")
if not hf_token:
    raise ValueError("Hugging Face API token not found. Please set HF_API_TOKEN in .env file.")

def create_model_and_generate(prompt: str):
    # Create model directly
    model = models.llamacpp(
        repo_id="M4-ai/TinyMistral-248M-v2-Instruct-GGUF",
        filename="TinyMistral-248M-v2-Instruct.Q4_K_M.gguf",
    )

    try:
        # Create generator without parameters
        generator = generate.text(model)

        # Generate response with parameters at call time
        response = generator(
            prompt,
            max_tokens=100,
            temperature=0.7
        )
        return response

    finally:
        # Ensure model cleanup
        del model

# Use the function
prompt = "Write a short story about a cat."
result = create_model_and_generate(prompt)
print(result)

Key Improvements

Proper resource management using try/finally
Explicit cleanup with del model
Generator parameters moved to call time instead of creation time
Single function to handle model lifecycle

Testing
The code has been tested and no longer produces the NoneType error during cleanup.
Documentation Updates
This pattern follows the Outlines documentation for structured generation(1) which shows that parameters should be passed during generation, not during generator creation.
Fixes #[issue_number]

My goal is to use the Outlines library on my local machine WITHOUT accessing the internet. So far, that is proving quite difficult. Could you please provide a model with Llama.cpp using regex for example, that works? Or with generate.text? I can use Option 1 below, but Option 2 does not work and should.
        response = model.create_completion(
            prompt,
            max_tokens=100,
            temperature=0.7,
            stream=False
        )
        return response['choices'][0]['text']
        """

        # Option 2: If you want to use Outlines generator (alternative)
        generator = generate.text(model)
        response = generator(prompt)
        return response

Here is the full code:
""
This script demonstrates how to use the Hugging Face API with a LLaMA model to generate text.

It loads the Hugging Face API token from a .env file, sets a random seed for reproducibility,
and defines a function to create a model and generate text based on a given prompt.

Usage:
  1. Ensure you have a .env file with your Hugging Face API token set as HF_API_TOKEN.
  2. Run the script to generate a text response based on the provided prompt.

Example:
  prompt = "Write a short story about a cat."
  result = create_model_and_generate(prompt)
  print(result)
"""

import os
from llama_cpp import Llama # E: Unable to import 'llama_cpp'
from outlines import models, generate
from dotenv import load_dotenv
import torch

# HF token is not required
load_dotenv()
hf_token = os.getenv("HF_API_TOKEN")
if not hf_token:
  raise ValueError("Hugging Face API token not found. Please set HF_API_TOKEN in your .env file.")

# Set random seed for reproducibility
torch.manual_seed(42)

def create_model_and_generate(prompt: str):
  # Create the llama model directly first
  llm = Llama(
      model_path="/Users/erlebach/data/llm_models/Meta-Llama-3.1-8B-Instruct-Q4_K_M.gguf",
      n_gpu_layers=-1
  )

  # Then create the Outlines model wrapper
  # model = models.LlamaCppModel(llm)

  # Create an Outlines model wrapper
  model = models.llamacpp(
      model=llm,  # Pass the existing model instance
      repo_id="local",  # Required but not used for local models
  )

  try:
      # Option 1: Use llama-cpp directly (recommended for local models)
      """
      response = model.create_completion(
          prompt,
          max_tokens=100,
          temperature=0.7,
          stream=False
      )
      return response['choices'][0]['text']
      """

      # Option 2: If you want to use Outlines generator (alternative)
      generator = generate.text(model)
      response = generator(prompt)
      return response

  finally:
      pass

# Use the function
prompt = "Write a short story about a cat."
result = create_model_and_generate(prompt)
print(result)


Greek Translations

Adding Greek Translations (Part 1)

There was some version of index.yml that contained keys:
noCameraAccess:
noCameraFound:
safariSupportOnly:

...but could not find them now, are they removed @marvinsxtr ? Thanks

@mackonsti I forgot that they are on the dev branch. Please also add the translations for them

Added, thanks.  I cannot find some exact translation.
What is TMG in the imprint text? An acronym of..?
Do we keep key creditsTranslation especially the part of the URL (free version)? I have kept it anyway.
What do you mean with "Note that selecting a file directly from camera is not supported." in selectCertificateDescription (index.yml) ? Select a file from the camera, the actual camera? How on earth can this be done 🤣 I guess you're trying to make it simple for people who think they can upload files via the camera feature?
Danke!

For imprint, you can use "legal note" as a synonym.
TMG is "Telemediengesetz" in German I believe.
Keep the creditsTranslation part with the link to deepl, I translated some parts of the Finnish translation with it and use it for single missing keys.
Yeah, I tried to explain that it is not possible to select a file and the choose to take a picture.

Hi @marvinsxtr I have updated the last and hardest translation part for GDPR as well as some fixes based on your comments. I have triple-checked everything and we are good to go. When you have time, let me know if-when you push these to production. Thank you again very much for your help and patience, happy to have helped.

@mackonsti The changes are now live, see #56.


Strengthen animation listener iteration patterns

This patch aligns the iteration patterns used by animations and
ChangeNotifier. They now both respect re-entrant removal of listeners
and coalesce duplication registrations. (Also, ChangeNotifier
notification is no longer N^2).
This patch introduces ObserverList to avoid the performance regression that the
previous version of this patch caused.
Fixes #7533

@Hixie
Attempt 2

Please file a bug (or comment on an existing bug) or add a TODO about adding documentation about the fact that you'll get called a surprising number of times if you remove yourself while iterating but you added yourself to multiple listenables that all ended up deferring to the same change notifier.

I filed https://github.com/flutter/flutter/issues/7570 so we don't lose track of it.


Implement java.io.Closeable in PowerShell class

Suggestion:
Implement java.io.Closeable in the PowerShell class to allow Java 7+ users to automatically close the powershell session with a try-with-resources statement.

Ups!, I forgot to add this to 2.0 version, sorry.
I will include it in 2.1

@profesorfalken  Thanks for your share , the autoCloseable was enabled in 2.1 , one more question , Can we close PowerShell session manually?

Hi @LonnccGitHub ,
Yes of course. You can call manually the method close()
Best regards


the requested package drewn/mailchimp-api could not be found in any version

i tried to install drewn/mailchimp-api with this strings
{
"require": {
"drewm/mailchimp-api": "*"
}
}
and i get this error;   Problem 1
- The requested package drewm/mailchimp-api could not be found in any versio
n, there may be a typo in the package name.
Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your min
imum-stability setting
see https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion f
or more details.

Read http://getcomposer.org/doc/articles/troubleshooting.md for further common
problems.

Thanks @JamesLaugesen this solved my issue.


Log git username in data load script slack msg

To increase visibility of who is changing data.

Tested the script change a couple of times. Working well, so I'm going to merge.


Don't skip Python 3.5

The only thing that worries me is that I could not get geos to compile on Windows and Python 3.5 using features. See https://github.com/conda-forge/geos-feedstock/pull/5#issuecomment-201940475

The only thing that worries me is that I could not get geos to compile on Windows and Python 3.5 using features

I'd say that if there is a problem downstream, the feedstock should be able to deal with that automatically - there should be no annotation in this recipe about which dependencies exist IMO.

I could not get conda smithy rerender to add the CONDA_PY: 35lines. Should I just add them manually or do you want to investigate?

I'd say that if there is a problem downstream, the feedstock should be able to deal with that automatically - there should be no annotation in this recipe about which dependencies exist IMO.

I could not get conda smithy rerender to add the CONDA_PY: 35lines. Should I just add them manually or do you want to investigate?

Hehe. That is precisely what is going on here. We can't build cartopy against py35 because it doesn't have all of its dependencies available - so there was no matrix item in the CI. The recipe shouldn't reflect that, but the feedstock certainly could (and does).

Let's merge and see how we get on. :+1:

Ah OK. I though that the removal of skip alone would update the CI config.
BTW which dependency is missing? We do have a "generic" geos that is working. The failure I comment above is in a PR that tries to use features to compile geos.

The failure I comment above is in a PR that tries to use features to compile geos.

I see. In which case, I'm uncertain. I'm not too worried, but I can dig further if you want. Searching with conda search -c conda-forge --platform win-64 <dep name> is one option. Ideally we'd have a tool to diagnose these.

I think I found the problem: https://github.com/conda-forge/cartopy-feedstock/blob/master/recipe/meta.yaml#L19

So what's the status on building for Python 3.5? I think the packages on anaconda.org cause Python 3.5rc4 to be installed.

OS X and Linux packages for Python 3.5 are already in the channel. Windows will be soon. (See #5.)

Right, but if I ask to install CartoPy in Python 3.5.1 I get:
Fetching package metadata: ..........
Solving package specifications: ....
Error: The following specifications were found to be in conflict:
  - cartopy -> numpy 1.8*
  - cartopy -> python 2.7*|3.4*|>=2.7,<3.5
  - python 3.5.1*
Use "conda info <package>" to see the dependencies for each package.

Asking for info on the package:
cartopy 0.14.0 np110py35_0
--------------------------
file name   : cartopy-0.14.0-np110py35_0.tar.bz2
name        : cartopy
version     : 0.14.0
build number: 0
build string: np110py35_0
channel     : conda-forge
size        : 1.6 MB
arch        : x86_64
binstar     : {'owner_id': '5528f42ce1dad12974506e8d', 'channel': 'main', 'package_id': '56f0128969180359233aa1e4'}
license     : GNU LGPL
machine     : x86_64
md5         : cd174eff02418251034aed6d1933e3c8
operatingsystem: darwin
platform    : osx
subdir      : osx-64
target-triplet: x86_64-any-darwin
installed environments:
dependencies:
    matplotlib
    mock
    nose
    numpy 1.10*
    owslib
    pillow
    proj.4
    pyepsg
    pyshp
    python 3.5*
    python >=2.7,<3.5
    scipy
    shapely >=1.5.6
    six

So the 3.5 package depends on python 3.5* and python <3.5, which results in requiring python 3.5.0rc4; that's not good.

Ah. That should be fixed in #5 too. I did not notice that the binaries were affected by that.

Somehow I missed #5, thanks!


touchQueue and touchStates

Is "touchqueue" a drag queue?  Is "touchstates" a click event

No.
touchQueue (in Unity, currently not implemented in the UE4 example) is an event queue which collects all UI touch events received over the network from the framework.  This gives you a chance to process the touches during the game loop as appropriate - typically you would run through the full queue and handle each touch event during an update.
A UI touch event mostly follows the Apple definition, so an event is created when you begin a touch on the screen, when you move the touch, when you release and a cancel event (i.e. interrupt from a phone call).
Touchstates shows the current state of the first 10 multi touches.
To further understand the difference:

you touch the screen and hold
A single touch event will included in the next packet and will be added to the queue,.  There will be no further updates to the queue until the user does something else.  In your game code you would probably remove the touch from the queue and do something (i.e. write 'click' on the screen).
Touchstates will show the position of the touch at index 0, every packet.

you then move your finger quickly.
multiple touch events may be sent with the next packet, one for each position along the path of your finger, and all will be added to the queue.  The touchstate will show only the latest position.

you release
A single touch event expressing release will sent in the next packet and added to the queue.  Touchstates will show released for the state of that touch.

Final note: as of today Dec 18th, touchstates and multitouch are features we have just added to our framework and is currently only available in private testing.  We will add this to our public beta app (Pose Camera) soon as well, but if you are using the latter please stay with the previous version of our Unity demo until we make this widely available.


feat: extend function between Ioo to be homeomorphism between Icc

Both homeomorphism and strictly monotone function between open intervals can be extended to be
an homeomorphism between the closed intervals.

[ ] depends on: #7018
[ ] depends on: #7351
[x] depends on: #7449

Here is another version of #7564 and #7565. You could check the statements and proofs of StrictMonoOn.Ioo_continuous_extend_Icc and Homeomorph.Ioo_extend_Icc to see what we could benefit from Function.toval.

I've changed my mind. I agree we should close these PRs.


Add ZeroConst and OneConst traits

As described in issue #54.
Works much the same way as i128 support: probes the compiler in the build script, and can be made a requirement by enabling the associated_consts crate feature.
There are several other traits in the crate which have similar "pseudo-consts", such as Bounded and Float, which should also eventually make use of associated constants through additional traits. However, Float in particular is not so straightforward; it already has its own FloatConst subtrait, which would require either a breaking change or a different naming convention to be extended, among other things.
A NumConst trait also seems like a natural fit; most types will implement either all or none of these const-y traits. However, it could be worth holding off on this, in case const fn ends up offering support for trait methods. Something like NumOps with compile-time evaluation would be a very powerful feature for generic code.
My suggestion is that #54 be closed and a new issue opened to discuss a broader implementation of associated constants in the crate. It's also likely that the discussion would affect the contents of this pull, so I think it's probably worth withholding these changes until then.
Very interested to hear others' thoughts on this!

Works much the same way as i128 support: probes the compiler in the build script, and can be made a requirement by enabling the associated_consts crate feature.

I'm not sure I want an explicit feature for this.  That was kind of an accident for i128, as I started with just a feature, and then I quickly got user feedback that auto-detection would be more useful to dependent crates.  In this new case, I think we can just leave it to the build script alone.
I recently started an autocfg crate which I want to start using throughout num crates, but it only has path/type/trait probing right now.  I should probably add support for arbitrary expressions for cases like you've written here.

There are several other traits in the crate which have similar "pseudo-consts", such as Bounded and Float, which should also eventually make use of associated constants through additional traits. However, Float in particular is not so straightforward; it already has its own FloatConst subtrait, which would require either a breaking change or a different naming convention to be extended, among other things.

Maybe ConstFoo would be a better naming convention?  It seems to read a little more directly to have ConstZero provide const ZERO, for instance.  Then we kind of dodge the Float issue by having the existing FloatConst and a new ConstFloat -- that will be a little confusing, but acceptable IMO.

A NumConst trait also seems like a natural fit; most types will implement either all or none of these const-y traits.

A direct parallel to Num would only include ZERO and ONE.  I'm not sure what others would fit "most" types.  Integers won't have the floating point constants, of course. BigInt and BigUint can't have bounded constants, since they're unbounded, but then they can't really implement ZERO or ONE either until there's a way to have a constant backing Vec.

I'm still interested, if you care to discuss my earlier reply. Otherwise, I may reimplement this separately.

Hi! Sorry for never getting back to this...
All the changes you suggested sound good and I'd be happy to implement them.
One of my concerns was forward-compatibility for the eventual implementation of compile-time math expressions. My intuition was that we would need another trait with const fn method implementations, ConstNumOps, which would fit in with ConstNum (which I was unclear about in my previous post).
But it looks like the current RFC proposal will make these library-defined const-y traits unnecessary. It adds a const Trait syntax that makes all the trait methods in a specific implementation const; exactly what we are doing here.
But that's probably far enough away for these traits (and maybe a few others?) to be useful as a stop-gap until then. Of course the RFC could change so I think it's worth only making other const-t traits when there is a concrete use-case with the current features in Rust. I think Zero, One, and Bounded are good candidates for that.
PS: Should I rebase this branch so it's up to date? Or is it cleaner to do it in the merge commit? Thanks!

I went ahead and rebased this onto rust-num:master (and tidied up some of the commits) so this shouldn't have any problems being merged. I also added an implementation for a ConstBounded trait, I figure it's not hard to revert if it you don't think it's a good fit.

Just wondering, what is the benefit of associated constants over for example, the soon-coming impl const Zero? I would argue that the latter is better and has the same functionality without needing a separate trait. Plus it requires no changes: people can use new versions of rust with those capabilities while the crate can still support old versions (I could be wrong about that)

@gluyas

But it looks like the current RFC proposal will make these library-defined const-y traits unnecessary. It adds a const Trait syntax that makes all the trait methods in a specific implementation const; exactly what we are doing here.

@Coder-256

Just wondering, what is the benefit of associated constants over for example, the soon-coming impl const Zero? I would argue that the latter is better and has the same functionality without needing a separate trait.

I wasn't aware of that proposal -- somehow I missed when @gluyas first linked it.
So yes, that looks great! The only disadvantage will be waiting for this support to reach a stable release of rustc, but long term this does look like a better way to approach these constants. Since that RFC is now in fcp-merge status, I'm inclined to leave it to that, rather than expanding num-traits with something that will be inferior. It seems better to suggest that folks can use their own local traits for ConstZero/etc. as a stop-gap, rather than being stuck in our API. OK?

Plus it requires no changes: people can use new versions of rust with those capabilities while the crate can still support old versions

We'll probably want impl const on a bunch of the local trait implementations for primitives, but the traits themselves shouldn't need any change.

Seems good. Closing this favour of waiting for language support.
Should also resolve #54.


CI: check that the verifier builds in no_std

This uses a fork on the cargo no-std-check utility that does not require the use of a nightly compiler.

We briefly talked about this needing a nightly compiler but I'm still getting the tool to run and get good results by using a stable compiler. My guess is that nightly is only required for building the stdlib parts of sysroot and this utility kicks out stdlib from the sysroot. If you prefer forking into the risc0 repo itself, feel free to fork https://github.com/SchmErik/cargo-no-std-check and I can update the url in the main.yml! For now, I forked it on my account


Typing issue: 戻り値 is missing even though less commoner similar word 返り値 has been registered

Category of the typing issue
Choose one of them (delete rest of them)

Out-of-vocabulary

Issues
Write issues to the following table. (It's in the markdown format)

input [e.g.ゆうひ]
expected [e.g. 夕日]
actual [e.g. ユウヒ]

もどりち
戻り値
戻り 地

かえりち
返り値
返り値

Version or commit-id
[e.g. Mozc-2.28.4960.100+24.11.oss or d50a8b9ae28c4fba265f734b38bc5ae392fe4d25]
You can get the version string by converting "Version" or "ばーじょん".
Google Japanese Input Dev (GoogleJapaneseInput-2.29.5374.100+24.11.9), but I have confirmed that “返り値” has been registered even in a build artifact of the plain Mozc using Windows Sandbox
Additional context
Add any other context about the problem here.
“戻り値” has been registered in the MS IME.

“返り値” has been registered at line 84154 in https://github.com/google/mozc/blob/master/src/data/dictionary_oss/dictionary08.txt.
The reason why “戻り値” is commoner:
https://qiita.com/paul_soundprj/items/ffb34b28cceec7f1577b (Japanese)

Thank you for your report.
3c10b49fcf43db32f578acb49a45cfb4fe5e1cff has added the word.
FYI. aux_dictionary.tsv is the file for manually adding words.

aux_dictionary.tsv

I see. Now I can send a PR.


GO:0005671 | Ada2/Gcn5/Ada3 transcription activator complex

GO:0005671 | Ada2/Gcn5/Ada3 transcription activator complex
A multiprotein complex that possesses histone acetyltransferase and is involved in regulation of transcription. Contains either GCN5 or PCAF in a mutually exclusive manner. The budding yeast complex includes Gcn5p, two proteins of the Ada family, and two TBP-associate proteins (TAFs); analogous complexes in other species have analogous compositions, and usually contain homologs of the yeast proteins. Both ATAC- or SAGA (see GO:0000124, SAGA complex) are involved in the acetylation of histone H3K9 and K14 residues. PMID:10637607
From, Dom Helmlinger:
This GO annotation relates to the ATAC complex, which does not contain “two TBP-associate proteins (TAFs)”.
To answer your question, no, yeasts do not have an ATAC complex (see for example this: Helmlinger D and Tora L, Trends in Biochemical Sciences, 2017, PMID: 28964624). ATAC and SAGA share many subunits, including those forming the HAT module (Gcn5, Ada2, Ada3, and Sgf29). However, metazoans such as flies and mammals have duplicated the ada2 gene, giving rise to two paralogs, Ada2a and Ada2b. Each is specific to either the ATAC complex, which contains Ada2a, or the SAGA complex, which specifically has Ada2b.
Both S. cerevisiae and S. pombe have only one ada2 gene and no orthologs of the subunits that are specific to ATAC (eg ZZZ3, ATAC2, HCF1, WDR5,YEATS2, NC2-beta, and MBIP in humans).
Val: It seems  this term has been used to describe the  submodule in S. cerevisiae (which should be only SAGA?), and the ATAC complex in human
Suggest, redefining clearly as ATAC, and adding a taxon restriction for yeast

@bmeldal
Essentially there is an
ADA module in yeast, which contains just Gcn5, Ada2, and Ada3 of SAGA, as well as two specific components Ahc1 and Ahc2.
However, there does not seem to be any evidence of an ADA sub-complex
The ATAC is a SAG-like complex and is not present in yeast.

I had a look back at our curation as well as the above mentioned papers etc and according to
PMID:28964624 (review of all SAGA-related HAT complexes)
PMID:21734642 (evidence for scADA complex) (also very old PMID:10490601)
PMID:19936620 (evidence for hATAC/SAGA)
PMID:22426530 (review for hATAC/SAGA)
I think there are 3 distinct complexes:
ADA: only in Saccharomyces cerevisiae
ATAC: only higher eukaryotes, incl drome, mouse, human
SAGA: pretty much everywhere from yeast to human
I think GO:0005671 Ada2/Gcn5/Ada3 transcription activator complex therefore needs to be split again into ADA and ATAC. If you look into the history, it was first added for yeast ADA, and then changed to include ATAC.
If you agree, I can suggest new defs.
Will require re-annotation...
NB: We also need to highlight that ATAC and SAGA can have GCN5 or PCAF as their mutually exclusive HAT. (We only have SAGA with GCN5 at the moment as the review came out after we curate this, I'll put those updates on my to do list)

GO:NEW1 ADA complex
Synonyms:
Ada2/Gcn5/Ada3 transcription activator complex [EXACT]
ADA histone acetyltransferase complex [EXACT]
ADA HAT complex [EXACT]
scADA [NARROW]
Def:
A chromatin remodelling complex that regulates transcription via acetylation primarily of nucleosomal histones H3 and H2B. In budding yeast shares the histone acetylation (HAT) module of ADA2-GCN5-NGG1-SGF29 with the related SAGA complex (GO:0000124).
NB: I have the feeling, ADA is restricted to budding yeast.
Refs:
PMID:21734642
PMID:28966424
Relationship:
is_a GO:0070461 SAGA-type complex
GOCID:bhm

GO:NEW2 ATAC complex
Synonyms:
ADA2A-containing complex
KAT2A-containing ATAC complex
KAT2B-containing ATAC complex
G-ATAC complex [EXACT]
Ada two A containing complex [EXACT]
Ada-Two-A-containing complex [EXACT]
Ada Two-A containing complex [EXACT]
Def:
A chromatin remodelling complex that regulates transcription via acetylation primarily of nucleosomal histones H3 and possibly H4. Shares the histone acetylation (HAT) module of GCN5/PCAF-ADA2-ADA3-SGF29 (or orthologs) with the related SAGA complex (GO:0000124). Contains HAT subunits GCN5 or PCAF in a mutually exclusive manner. In addition to the HAT module contains DR1/NC2B, KAT14, MBIP, WDR5, YEATS2 and ZZZ3 or orthologs. Also regulates the activity of non-histone targets and orchestrates mitotic progression by regulating Cyclin A degradation through acetylation.
NB: I have the feeling, ATAC is not present in fission nor budding yeast.
Refs:
PMID:19936620
PMID:20562830
PMID:28966424
Relationship:
is_a GO:0070461 SAGA-type complex
GOCID:bhm

SAGA also needs restructuring, working on it with Sandra right now. Will open a separate ticket when we have it all detangled.

@bmeldal : and pombe would have neither?

+id: GO:0140671
+name: ADA complex
+namespace: cellular_component
+def: "A chromatin remodelling complex that regulates transcription via acetylation primarily of nucleosomal histones H3 and H2B. In budding yeast shares the histone acetylation (HAT) module of ADA2-GCN5-NGG1-SGF29 with the related SAGA complex." [GOC:bhm, PMID:21734642, PMID:28966424]
+synonym: "ADA HAT complex" EXACT []
+synonym: "ADA histone acetyltransferase complex" EXACT []
+synonym: "Ada2/Gcn5/Ada3 transcription activator complex" EXACT []
+synonym: "scADA" NARROW []
+is_a: GO:0070461 ! SAGA-type complex
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21335 xsd:anyURI
+created_by: pg
+creation_date: 2021-06-25T11:02:49Z
+
+[Term]
+id: GO:0140672
+name: ATAC complex
+namespace: cellular_component
+def: "A chromatin remodelling complex that regulates transcription via acetylation primarily of nucleosomal histones H3 and possibly H4. Shares the histone acetylation (HAT) module of GCN5/PCAF-ADA2-ADA3-SGF29 (or orthologs) with the related SAGA complex (GO:0000124). Contains HAT subunits GCN5 or PCAF in a mutually exclusive manner. In addition to the HAT module contains DR1/NC2B, KAT14, MBIP, WDR5, YEATS2 and ZZZ3 or orthologs. Also regulates the activity of non-histone targets and orchestrates mitotic progression by regulating Cyclin A degradation through acetylation." [GOC:bhm, PMID:19936620, PMID:20562830, PMID:28966424]
+synonym: "Ada two A containing complex" EXACT []
+synonym: "Ada Two-A containing complex" EXACT []
+synonym: "Ada-Two-A-containing complex" EXACT []
+synonym: "ADA2A-containing complex" EXACT []
+synonym: "G-ATAC complex" EXACT []
+synonym: "KAT2A-containing ATAC complex" EXACT []
+synonym: "KAT2B-containing ATAC complex" EXACT []
+is_a: GO:0070461 ! SAGA-type complex
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21335 xsd:anyURI
+created_by: pg
+creation_date: 2021-06-25T11:05:14Z

To do:

[ ] add taxon restrictions on new terms
[ ] obsolete  GO:0005671 | Ada2/Gcn5/Ada3 transcription activator complex (next week when new terms are available)

As far as I know ADA is a submodule in (both) yeast, and is not functional independently so we would not represent that in GO. We would only need SAGA for annotation.

As far as I know ADA is a submodule in (both) yeast, and is not functional independently so we would not represent that in GO. We would only need SAGA for annotation.

ADA in budding yeast has 2 components that are not found in SAGA: AHC1 & AHC2

From Dom:
ADA: no evidence that it exists in fission yeast, although no one has specifically looked at this. ADA exists in budding yeast, in which 1-2 additional subunits (Ahc1 and Ahc2) specifically define the ADA complex, together with Gcn5/Ada2/Ada3. Ahc1 and Ahc2 have no orthologs in fission yeast. Nevertheless, a recent paper shows that ADA exists in Drosophila, in which there is also no Ahc1/2 orthologs. In that case, ADA was defined using biochemical fractionation and acetylation assays. The same type of experiments would need to be done in S. pombe to conclude about its existence.
ATAC is absent from both yeast species (and I think from fungi).

So for now  I think we should block ADA for Schizosccharoyces  species, and ATAC for all yeast.
v

Dear all,
The proposal has been made to obsolete GO:0005671 | Ada2/Gcn5/Ada3 transcription activator complex. The reason for obsoletion is that it was split into 2 more precise terms:
GO:0140671 ADA complex
"A chromatin remodelling complex that regulates transcription via acetylation primarily of nucleosomal histones H3 and H2B. In budding yeast shares the histone acetylation (HAT) module of ADA2-GCN5-NGG1-SGF29 with the related SAGA complex."
and
GO:0140672 ATAC complex
"A chromatin remodelling complex that regulates transcription via acetylation primarily of nucleosomal histones H3 and possibly H4. Shares the histone acetylation (HAT) module of GCN5/PCAF-ADA2-ADA3-SGF29 (or orthologs) with the related SAGA complex (GO:0000124). Contains HAT subunits GCN5 or PCAF in a mutually exclusive manner. In addition to the HAT module contains DR1/NC2B, KAT14, MBIP, WDR5, YEATS2 and ZZZ3 or orthologs. Also regulates the activity of non-histone targets and orchestrates mitotic progression by regulating Cyclin A degradation through acetylation."
There are 73 EXP annotations,

BHF-UCL|12
FlyBase | 27
MGI | 16
SGD | 18
https://github.com/geneontology/go-annotation/issues/3847

There is one InterPro mapping  to IPR037807
This term is not present in any subsets.
We are opening a comment period for this proposed obsoletion. We’d like to proceed and obsolete this term on July 26, to leave time for groups to make corrections. Unless objections are received by July 26, 2021, we will assume that you agree to this change.
You may comment on the ticket: geneontology/go-ontology#21335
Thanks, Pascale

I've reviewed FBs - all are updated to ATAC complex.
Interestly, just found a paper on ADA complex in insects (which the authors call a metazoan ADA complex) https://academic.oup.com/nar/article/47/7/3383/5304717
Tagging @phanivg on this - I've also found an insect-specific HAT complex - CHAT - we might want a new term for this - I'll hand that over to you, Phani ;-) https://pubmed.ncbi.nlm.nih.gov/32735945/

I've reviewed FBs - all are updated to ATAC complex.
Interestly, just found a paper on ADA complex in insects (which the authors call a metazoan ADA complex) https://academic.oup.com/nar/article/47/7/3383/5304717
Tagging @phanivg on this - I've also found an insect-specific HAT complex - CHAT - we might want a new term for this - I'll hand that over to you, Phani ;-) https://pubmed.ncbi.nlm.nih.gov/32735945/

The plot thickens... that's why I didn't suggest any taxon restraints (apart from ATAC not in yeast and ADA not in pombe). I don't have time to check all cases and the papers I reviewed were only yeast and mammalian based, with references to SAGA in "everything".


investigate generic grammar for rich text formatting

useful for word/teams/slack/github messages/etc etc. activate via tag as appropriate.

fwiw I have a plan for something like where we can use the existing generic editor commands that normally don't work outside of an editor (so like anything that's not just movement or deletion using the ctrl  key), but I've only just started to play around with it recently. but the idea is to have a vim backend process that talon can interact with over RPC, then can copy/pasting the input field  text from the given not so powerful text input field (in tracking cursor position) and behind the scenes do all of the automated editing/processing and cursor updates. there is obviously some problems with something like this if the input is super large. I have really basic proof of concept support for doing character finding (as in moving the cursor to the specified character) inside of the url bar in my browser, in it seems like it should be fairly easy to extend a more powerful commands.
obvious the biggest caveat is that would rely on people having neovim installed, but it seems easier to leverage in existing editors functionality rather than have to implement it all ourselves?
I'm not really sure that this is along the lines of what you are thinking but it came to mind when I just read this so I thought I'd mention it anyway

Huh, very interesting. That’s much more elaborate that what I had in mind for this, hehe. Sounds compelling.
something like this
tag: rtf
-
go boldly: user.rtf_bold()
go italics: user.rtf_italics()
...


left/right stereo pan of the file

Hi, I was wondering if there was an easy way to do the stereo pan of a file in your library.

That feature is not available but you are welcome to open a pull request.


start-dev and dev are not working

I wanted to use this project as a base for a new one, but it's really frustrating to constantly run npm run build (which takes forever) and then npm start again.
I saw there are 2 run scripts start-dev and dev in the package.json, but when I run the start-dev script, it just never updates and always provides the old files. The dev script is even worse, I mean it appears as if it would do something, but on localhost:3000 there is nothing and I didn't see a reference to another port anywhere.

You run npm run dev in one console. This sets webpack to run forever in that console, watching for file changes
then you open a 2nd console, and run npm run start-dev which will trigger nodemon to watch the entire project for file changes, and restart the server
to make nodemon not trigger for every change,but only on the "rebuilt" changes:
change the dev-start script to: nodemon --watch dist --watch dist-server dist-server/main.js
This tells nodemon to only restart the server when the packaged files change
BONUS: Add the following to the webpack.config to force webpack to wait for 2.5 seconds before rebuilding files (cuts down on builds triggering while you are making changes if you use something like autosave)


Improve sorting classes

The following class is not sorted incorrectly (the result is m-2 rounded mt-1.5),

Since mt-1.5 is not explicitly listed on the package.json
A quick fix is just to add mt-1.5, but I think this plugin could be more awesome if we use another package such as tailwind-classes-sorter (but I couldn't make it work :disappointed:) or we create a new one that accepts a configuration more compact:
"tailwindCSS.headwind.defaultSortOrder": {
          "type": "array",
          "default": [
            "m-{value}",
            "mt-{value}",
            ...,
        ]
}

Thanks for the issue report.
Are you using prettier? If it is coc.nvim, you can use it by installing coc-prettier.
There is an official prettier plugin provided by tailwindcss.

https://github.com/tailwindlabs/prettier-plugin-tailwindcss

If you install this in your project, you will get the sorting you expect when prettier is run, so give it a try.


[Ludown] Add ability to specify LUIS and QnA application information in .lu file

Fixes #1229
Proposed Changes

added ability to include application description information in .lu file for both LUIS and QnA
updated parser
updated refresh command

Testing

verified existing tests pass
added new tests

@feich-ms FYI

@vishwacsena , could you please merge this PR into master first so that I can merge these changes from master and then changed it to antlr?

Yes. I have one more PR that's related. I'll let you know once all those are in. @feich-ms


Quotation Marks & Apostrophe's rendering incorrectly after kepubify conversion

For my workflow, I've been using Epubor to decrypt my kindle books, then convert to KEPUB using KEPUBIFY on MacOS.  I've been noticing for sometime now that on my converted books that apostrophe and quotation marks render as multiple extended characters.  For example, an apostrophe shows as : â€™
As a test, I used Calibre to convert the same book to kepub format, and it shows correctly.  This seems to be caused by kepubify.  Any thoughts on why this might be happening?  Not sure if this is a bug, or something specific to my workflow with kepubify.

The Rules_ The Way of the Cycling Disciple.kepub.zip
Here is a sample file along with a jpeg I've marked with samples I see when reading on my Kobo

Nevermind, updating to current build, 4.0.4, appears to resolve the issue


Added features such as explaining bugs to selected code

The selected part can be acted upon separately by the selected code combined with the context

Hi @shuaiBi903 ,
Thanks for filing the issue!
I don't quite understand the request. Could you explain more?


ci: deflake macOS cache updates

The last few failures for #3645 the build timed out because uploading or downloading the cache made no progress in 3600s.  With this change the upload and/or download of the cache may timeout, but that would not break the build because they run with a || true at the end.
Whether the overall build will still timeout for other reason, or the 20 minutes consumed by the cache upload/download timeout proves too much, that remains to be seen. In any case, I believe this would help, if nothing else, it would give us more information as something else would fail.
Part of the work for #3645

This change is

What's the effect of this change?

Updated the description, will include that in the commit message too.


[MM-18385] Force screen reader to read whole aria-live section on multiselect option change

Summary
Firefox was not correctly reading the aria-live region of the multiselect component, instead it was reading bits and pieces as the text field was updated. This PR adds the aria-atomic label, which ensures the entire option is read correctly.
NOTE: Microsoft Edge continues to have issues with JAWS and NVDA. See: https://github.com/FreedomScientific/VFO-standards-support/issues/266
Hopefully this will be fixed soon.
Tested on Firefox 69.0 and JAWS 2019.1907.42
Ticket Link
https://mattermost.atlassian.net/browse/MM-18385

Hi @devinbinnie
Will this also fix the other issue reported in the ticket, i.e.
Reader does not reads 'no results found' in the Direct messages Modal
Can you please check and confirm. If not, can you please fix this issue too.

@hmhealey aria-atomic forces the screen reader to read the label as a whole rather than individual text updates. My guess as to what was happening here was that the label was being read before the entire text string was interested, and it was reading each bit as it was inserted.
It seems really odd for it to be doing that, as I would assume the entire string would be inserted as a whole, but it appears to be the case as aria-atomic forced the reader to stop doing that. A11y standards are not consistently implemented across browsers as we can see.

Creating a new SpinWick test server using Mattermost Cloud.

Please wait while a new kubernetes cluster is created for your SpinWick

@hmhealey @srkgupta Well, it seems like my fix might not have done anything, as I can't get it to read properly with JAWS anymore. NVDA seems to work fine, but JAWS refuses to read aria-live tags. I'm sensing there's a bug in either the browser or JAWS, I don't think this an issue with our software anymore.

Kubernetes cluster created. Now will deploy Mattermost... Hang on!

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3679.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

@asaadmahmood Do you recall adding any aria-hidden or any sort of tags that would hinder this from being read? That's the only thing I can think of having an issue with our software.

@devinbinnie Don't think so.

Okay after further investigation I've identified this issue as an issue between JAWS and Firefox. See the JIRA ticket for more information.
We can still merge this as a fix for the Direct Messages modal reading individual pieces of the names, as the reading still works with Firefox using NVDA.

@amyblais can this go into v5.16? I think it should as we should be supporting NVDA as much as possible.

Sounds good,

Test server destroyed


Added watcher for changes to dataset

Requires a   $( '#yoursearchbox' ).typeahead( 'destroy', 'NoCached' ); where you're reinitializing bloodhound as well.

See #53


baseline.txt not working for large files

I have an extremely complex legacy project that I'm trying to implement flakeheaven on - along with the wemake style templates and want the checks to run through pre-commit
.pre-commit-config.yaml
default_stages: [commit, manual]
repos:
  - repo: https://github.com/flakeheaven/flakeheaven
    rev: 3.0.0
    hooks:
      - id: flakeheaven
        entry: flakeheaven lint
        additional_dependencies: [
          wemake-python-styleguide
        ]

pyproject.toml
[tool.flakeheaven]
baseline = "baseline.txt"

[tool.flakeheaven.plugins]
# These plugins get installed by `wekmake-python-styleguide` as defined in pre-commit-config.
"flake8-*" = ["+*", "-Q000"]
"py*" = ["+*"]
pep8-naming = ["+*"]
mccabe = ["+*"]
wemake-python-styleguide = ["+*"]

I have generated a baseline file by doing the following:

manually installing flakeheaven by doing pip install flakeheaven==3.0.0
running flakeheaven baseline > baseline.txt (this file is about 5000 lines long!)
poetry install --sync (as I want pre-commit to manage the flakeheaven version so don't want it in my env)

The problem
When I try and make changes to any of the legacy files, flakeheaven reports errors on many lines - not just the ones that I changed. I assumed that this was happening because I was (for example) adding a new method in the middle of the file and flakeheaven was picking up the new line numbers of the second half of the file as a change. But I've tried adding a new function right at the bottom of the file and flakeheaven still reports errors elsewhere in the file that were previously ignored due to the baseline.

I've proven the baseline works if I undo any changes then run flakeheaven lint <path/to/file.py>.
I've tried this exact same flow on a dummy project with only a 20 line "legacy" file that has issues and flakeheaven correctly reports errors only where I have changed code - correctly ignoring any functions that have issues that I haven't changed.

Does anyone have any suggestions of how I can get this working? My only guess is that the size/complexity is the problem here.

From BaselineFormatter and make_baseline, the hash is computed from (1) the path to the source code, (2) the line number*, and (3) the code itself.
I'm thinking maybe the line numbers might have changed as well? For example this would happen if something like black or another formatter is also running between the baseline and the pre-commit hook.

Closing this question as I don't think there is any easy way to fix this.


@/UI Docker multi platform

Description
As part of migrating our PROD env to new instances, we're investigating deploying to arm64 instances. Dokku already supports arm64 but our build pipeline only supports amd64.

[X] VPN Manager

[X] DEV
[ ] PROD

Type of change

[X] Chore

Screenshots
N/A
Checklist:

[x] My code follows the style guidelines 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
[ ] I have made corresponding changes to the documentation

Success 🚀 ... we can successfully run our apps in arm64. We'll create a PR to update the docker build job to include arm64 for all apps but first, we should probably switch to callable workflows to reduce copy and paste.


Why not rename the repo?

Hi :)
Why not rename the repo like your page http://svgporn.com/ ?
And the old url github.com/gilbarbara/logos will redirect to the new one.

hey!
The svgporn domain was a little inside joke and I'll probably change it soon. I've already purchased http://svgmania.com/
So I think it's best to keep the repo name simple and constant.
[s]

Ok ok as you want :+1:
I just thought maybe you didn't know about the GitHub's redirection.

:grimacing: :+1:

@gilbarbara I think svgmania.com is a much better name.
It will also avoid the domain from being blocked at work 😆


Update to use tags in 1.2.4 input manifests

Signed-off-by: Peter Zhu<EMAIL_ADDRESS>Description
Update to use tags in 1.2.4 input manifests
Issues Resolved
#1417
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1503 (210e370) into main (cbeffeb) will decrease coverage by 0.15%.
The diff coverage is n/a.

:exclamation: Current head 210e370 differs from pull request most recent head 14e737c. Consider uploading reports for the commit 14e737c to get more accurate results

@@             Coverage Diff              @@
##               main    #1503      +/-   ##
============================================
- Coverage     94.32%   94.16%   -0.16%
  Complexity       12       12
============================================
  Files           146      146
  Lines          3134     3134
  Branches          8        8
============================================
- Hits           2956     2951       -5
- Misses          171      176       +5
  Partials          7        7

Impacted Files
Coverage Δ

src/system/temporary_directory.py
83.87% <0.00%> (-12.91%)
:arrow_down:

src/system/os.py
92.30% <0.00%> (-7.70%)
:arrow_down:

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 cbeffeb...14e737c. Read the comment docs.


Add dev version of lightning as dependency to dev branch

Adds the development branch of PL lightning as a dependency to the QML repo.
PL-lightning will be a dependency of the 0.18 version of PL, so we mirror the dependency here to confirm that no issues are caused in the QML repo demos.
See also https://github.com/PennyLaneAI/qml/pull/337 for the master branch version.

Closing since none of the demos currently depend on development features of lightning.


Skip object identifiers when checking for unused symbols

UserVoice request: http://vfpt.uservoice.com/forums/247560-general/suggestions/8793808-do-not-mark-orange-in-the-right-bar-unused-self-re
Graying out object identifiers could be annoying. Since it has little practical value, we skip it while checking for unused references.

I'm afraid I disagree. What's more, that User Voice has only 4 votes. I like how it works now. Maybe we should ask people?

Sure, please ask around on Twitter and Slack.

@cloudroutine wrote on Slack:

I'd prefer another toggle like "Gray out unused member identifiers" and a toggle for whether unused items show up in the scroll bar

I agree, we should add two options:

Syntax coloring
Gray out unused opens
Gray out unused declarations

Gray out unused self identifiers

Show unused symbols on scroll bar

BTW, what do you think about using "Highlight" instead of "Gray out"?

Highlight is more accurate since this is in the context of syntax highlighting and because the color for unused items doesn't have to be grey.

Gray out unused self identifiers: the option is too fine-grained to support a very specific use case. I wouldn't want to go that way.
Show unused symbols on scroll bar: It might be useful, but it doesn't solve the problem here.

What do you think about using "Highlight" instead of "Gray out"?

Yes, it's better with 'Highlight' as @cloudRoutine said.

If you don't like the idea to add a setting for "Gray out unused self identifiers" and not all people like removing the feature (including me), I suggest to drop this PR.

Please do make it optional. I consider the "this" identifier to be used as soon as a member is declared using the member this.membername syntax. I don't like being told that it isn't being used when it is required by the syntax (it feels like returning a false positive).

this is completely redundant. It's just a variable, and if you don't need it, you should claim about it explicitly, like _self or __. I think putting this everywhere is just old C# habit.

This tweet convinced me https://twitter.com/CarstenK_Dev/status/631013723700903936.
Happy to close this and forget it forever.


Make the nav menu scrollable

When the <nav> menu has many items (is long) or on short-height windows or screens, the <nav> simply overflows the window with the overflown items cut-off and inaccessible. This quick-fix proposal constraints the <nav> at the bottom and enables scrolling for overflow behaviour.
Although, browsers’ – at least Chrome – scrollbars look thicc and out of place.
I discovered this oversight while trying to fix #48/#62. This can be an initiating step, as the next would be making the bottom retract to make room for the <footer> (which has non-constant height, and I am not aware of how to respond to that).

@ParadoxV5 thanks for this! It works for me and I really needed it :clap:


RANCHER with net bridge : link didn't work

Rancher Versions:
Server:  rancher/server:v1.3.0-rc6
healthcheck: rancher/healthcheck:v0.2.0
ipsec:
network-services: network-manager:v0.4.0
scheduler:
**Docker Version:
Client:
Version:      1.12.4
API version:  1.24
Go version:   go1.6.4
Git commit:   1564f02
Built:        Mon Dec 12 23:41:49 2016
OS/Arch:      linux/amd64
Server:
Version:      1.12.4
API version:  1.24
Go version:   go1.6.4
Git commit:   1564f02
Built:        Mon Dec 12 23:41:49 2016
OS/Arch:      linux/amd64
**
OS and where are the hosts located? (cloud, bare metal, etc):
Redhat , and all is in the same server
**Environment Type: Cattle
I have traefik on front of  rancher server
Steps to Reproduce:
I specified the network_mode: bridge for all my services in docker-compose
I deploy by catalog :
Results:
my services are visibles for traefik (ip exemple : <IP_ADDRESS>)  ---> GOOD
Rancher with the UI show me links between stack services and when I click on link I see the container -->Good
But in fact, the linked containers didn't see another
for example my web container dont 'see the database container and then my webserver crach, and when I ping inside the container (webserver)for the container linked (database) : no answer
Expected:
It works for traefik , for rancher, and in container themselves !!

I drop traefik, now i'm using loadbalancer, it's work fine


AGP 3.0a7 and Gradle 4.1 M1.

Worth replacing compile with implementation?
Also, I think https://github.com/JakeWharton/u2020/blob/0733f955ced7c160e088b74015ff34e7cbec10e0/build.gradle#L120 was fixed.

The configuration switch can come later. And I'm pretty sure that bug isn't fixed it's just marked as impossible fix fully.


Default Token Configuration is ignored when dragging an actor to the sidebar rather than to the scene

Possibly related to https://github.com/foundryvtt/pf2e/issues/2001
To reproduce, set the Core settings of "Default Token Configuration" to a certain value that differs from the value for creatures in the compendium, and then compare dragging to the scene with dragging to the sidebar.
The default token configuration fails to apply to the new actor's prototype token, unless it was dragged onto the scene.

Oh, I see it got fixed in core foundry V13 now :)
https://github.com/foundryvtt/foundryvtt/issues/11639


feat: Surface using logfmt for dev-time logs

What this PR does / why we need it
Adding both tee to the log file (so the logs show up in Datadog) and logfmt for easier to parse dev-time logs (there's a lot of details a dev doesn't need in the default log format).
For more info on the logfmt go here https://outreach-io.atlassian.net/wiki/spaces/EN/pages/706347415/Logging#Formatting-option

Jira ID
DTSS-1937

Notes for your reviewers

Eh, just realized, this is calling logfmt which is in eng which is closed source. We might want to pull that out and OSS it otherwise devspace won't work for peepz


Make ClaimTrie Sync Fast

Right now we are iterating through all claim names and then all claims. Due to bottleneck on lbrycrd this is not feasible.
We need to instead grab all claims that have been created/updated since the last sync. We also need to grab all supported claims since the last sync. The unique names from those sets is what should query lbrycrd for. This should make the claimtrie sync lightning fast as there are probably very few name updates in 15 minutes. Also grabbing a set of claims from the database (just the required fields) in one go that might potentially have had status changes is faster than one by one.

this has been addressed via 0b8ae9337508b53e91ef3ce2bc293ee45cdd6a96
The sync is now lightning fast by only syncing the created or updated claims ( considerations are made for supports for the claim ).


package sets application@label value

i get the error
Attribute application@label value=... from AndroidManifest.xml:17:9-36
        is also present at [com.polidea.rxandroidble:rxandroidble:1.4.3] AndroidManifest.xml:16:18-50 value=(@string/app_name).

when compiling when using the package. without the package everything compiles fine.

Thanks for reporting this issue! We’re working on it, library is still in progress.
Regards
Konrad Krakowiak

I have the same problem too.

@emdete @alishir It has been a long time since we stopped maintaining the library but now we come with great news! We are currently working with Frontside on a new BLE Flutter library and BLE simulator. Beta version has been released already and we are going to release 2.0.0 in the first half of November

Still seeing this issue, can we reopen it, please ?

@Drkstr could you provide the logs, please?

Sure.
Here is the error log when I run a flutter project with the flutter_ble_lib package(version 2.0.1) without adding "tools:replace="android:label" to the manifest file.
/Users/rakshak/personal_projects/ble_test_flutter/android/app/src/debug/AndroidManifest.xml:16:9-41 Error:
Attribute application@label value=(ble_test_flutter) from AndroidManifest.xml:16:9-41
is also present at [com.polidea.rxandroidble:rxandroidble:1.7.0] AndroidManifest.xml:16:18-50 value=(@string/app_name).
Suggestion: add 'tools:replace="android:label"' to  element at AndroidManifest.xml:14:5-35:19 to override.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugManifest'.

Manifest merger failed : Attribute application@label value=(ble_test_flutter) from AndroidManifest.xml:16:9-41
is also present at [com.polidea.rxandroidble:rxandroidble:1.7.0] AndroidManifest.xml:16:18-50 value=(@string/app_name).
Suggestion: add 'tools:replace="android:label"' to  element at AndroidManifest.xml:14:5-35:19 to override.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 5s
Finished with error: Gradle task assembleDebug failed with exit code 1
flutter doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.14.5 18F132, locale en-AU)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
[✓] Android Studio (version 3.5)
[!] IntelliJ IDEA Ultimate Edition (version 2018.1.8)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[!] Connected device
! No devices available
! Doctor found issues in 2 categories.

@Drkstr should be fixed in 2.2.0

Awesome thanks :D


Clarify Documentation of THR_MDL_FAC

The documentation of the thrust model parameter THR_MDL_FAC did not mention both thrust and "PWM" being relative values. Also the use of the term PWM could be misleading, since the model is applicable to CAN ESCs as well.
PWM was replaced with motor control signal, and the description text for the parameter list (or QGC parameter description) was changed to make the model more clear.
Could close PX4/Firmware#13105

Fixes #13105 .
@bresch Can you please check


Display active games

by accident closed it -> will reopen it

New tests that you added (not modified) should follow the new test naming convention that was decided together.


plutus-chain-index swagger documentation isn't complete and/or rendering correctly

Summary
Swagger/OpenAPI documenation is supposed to be interactive and offer the user a way into an API. Currently, a number of endpoints in the plutus-chain-index docs are incomplete and it is difficult/impossible for a new user to access these and find the right way into  the endpoints.
Take for example this naive use of the tx endpoint:

Steps to reproduce the behavior
On the command line the result looks as follows:
curl -X 'POST' 'http://xxx.xxx.xxx.xxx:9084/tx'  \
 -H 'accept: application/json;charset=utf-8'   \
 -H 'Content-Type: application/json;charset=utf-8'   \
 -d '"27b46f95470d82b88e7a91429ed3b7c3c14c151223289f5510e72598678a5b0b"'

Actual Result
Error in $: parsing Plutus.V1.Ledger.Tx.TxId(TxId) failed, expected Object, but encountered String

Expected Result
A valid request can be built for any endpoint on the chain-index API and it will return something sensible.
Thanks to this Cardano stack exchange post, we have a way forward for this endpoint: https://cardano.stackexchange.com/questions/7714/how-to-query-the-chain-index-tx-endpoint
e.g.
curl -X 'POST' \
  'http://xxx.xxx.xxx.xxx:9084/tx' \
  -H 'accept: application/json;charset=utf-8' \
  -H 'Content-Type: application/json;charset=utf-8' \
  -d '{"getTxId" : "27b46f95470d82b88e7a91429ed3b7c3c14c151223289f5510e72598678a5b0b"}'

This successfully returns transaction information on preprod.
Connected to: https://github.com/input-output-hk/plutus-apps/pull/130
Connected to https://github.com/input-output-hk/plutus-apps/issues/652
Connected to https://github.com/input-output-hk/plutus-apps/issues/651
Connected to https://github.com/input-output-hk/plutus-apps/issues/4
Describe the approach you would take to fix this
Add the documentation to the endpoints where there is none. The example value/schema portion of the endpoint needs to be complete and accurate. Not just "string" as this can't be reverse engineered by anyone.

An annotated error response from plutus may also be amended to describe the expected schema, i.e. when is seeks an object, what does the object look like.
Error in $: parsing Plutus.V1.Ledger.Tx.TxId(TxId) failed, expected Object, but encountered String

Could be:
Error in $: parsing Plutus.V1.Ledger.Tx.TxId(TxId) failed, expected Object of type {"getTxId": "acdc1234"}, but encountered String

NB. Not a plutus developer, so this latter part may be out of anyone's control.
System info
Unsure as to which plutus-chain-index is being used as I am not sure version is available from the command line options.

NB. between the POST verb here, and the JSON (getTxId) there's some confusion in verbage. I don't know what scope there is to fix that kind of thing, but if that's worthy of another ticket, we can make that. It will be easier to analyse the different schema once it's more visible.
curl -X 'POST' \
  'http://xxx.xxx.xxx.xxx:9084/tx' \
  -H 'accept: application/json;charset=utf-8' \
  -H 'Content-Type: application/json;charset=utf-8' \
  -d '{"getTxId" : "27b46f95470d82b88e7a91429ed3b7c3c14c151223289f5510e72598678a5b0b"}'


ISPN-13737 Fallback to default provider when obtaining KeyManagerFactory

https://issues.redhat.com/browse/ISPN-13737

Thanks @tristantarrant


Light Client TLA+ Specification

A TLA+ spec for the light client verification, in accordance with the English spec.

@ancazamfir, thank you for the deep review! Josef and I went over your comments and implemented some of them (and commented on the ones we skipped).


go_template_engine

I will drop in more details soon about how to use this feature.

closing the PR due change in direction on how to resolve the flavors/addons in kubefirst


Getting resolved import from compiler API

It looks like currently it's not possible to get the path/name of the module that an import statement has been resolved to.
I was able to get the import specifier like "./module" from AST (using https://github.com/dsherret/ts-simple-ast), and from there it would have been easy to retrieve the imported file using SourceFile.resolvedModules, but resolvedModules is marked as @internal.
Specifically, there's these two lines in types.ts:
https://github.com/Microsoft/TypeScript/blob/b74ec1c58b1c01e9331422315a7451d8eaee1ac1/src/compiler/types.ts#L2321-L2322
The comment in the first line references getResolvedModuleFileName/setResolvedModuleFileName but those functions don't seem to exist anywhere in the repo.

It looks like currently it's not possible to get the path/name of the module that an import statement has been resolved to.

Why do you need it for, because it seems like it would be entirely misleading.  TypeScript has a very sort of loose concept of module resolution that doesn't necessarily reflect runtime behaviour of module, nor a specific file.  For example, this in a .d.ts file would be a resolution of any number of modules imports:
declare module 'text!*' {
    const text: string;
    export = text;
}

So the type location might be useful for quick linking and looking up stuff, but it is a type location, not a resolved file name, nor does it reflect what would actually be done by a module loader at runtime or build time.

Sure, here's my use-case: I'm working on a build tool that offloads modules ending with .ww.ts to a web worker, with a restriction that imports from those .ww.ts files to regular files can only be named imports, and those named imports should be of certain types, to be exact, (...args: any[]): void, Promise<any>, (...args: any[]): Promise<any>, Observable<any>, or (...args: any[]): Observable<any>. So if you have two modules like this:
// moduleA.ww.ts
export const f = () => console.log('f');

// moduleB.ts
import { f } from './moduleA.ww';
f();

it will generate a main script where moduleA.ww is stubbed out with a file like
export const f = rpc(...)

and it will also generate a web worker script that imports f from moduleA.ww (that's where I need the actual filename of moduleA.ww) and makes it available to be called through an RPC.
I don't know how clear above explanation is, but hopefully it gives an idea of what I'm trying to do. I'm nearly there, but I had to use a hack where I cast the compiler's SourceFile object to a custom type in order to get at the internal property resolvedModules, and then resolvedModules.get('./moduleA') gives me the filename of moduleA.ww.

@rbuckton may better know how to guide you.

It looks like currently it's not possible to get the path/name of the module that an import statement has been resolved to.
Why do you need it for

Side note, this linter that detects circular imports also needs this information:
https://github.com/bcherny/tslint-no-circular-imports/blob/master/noCircularImportsRule.ts#L34

@mhegazy @DanielRosenwasser
I also found myself needing access to resolvedModules.
I've got my own TypeScript integrations for node and webpack, each automating some configurations:
https://github.com/AviVahl/ts-tools
My webpack loader needs to know resolved modules per source file, in order to direct webpack to watch them in its graph.
I'd also like to get baseUrl and paths working natively in node/webpack by applying a custom transformer which remaps the imports to the actual target (ignoring relative requests and resolved .d.ts).
I've noticed that if I tell TypeScript to transpile to module: 'commonjs', I have the resolvedModules field readily available on the SourceFile filled with the resolution results.
Transpilation to module: 'esnext' is another story. The resolvedModules field is there, but the resolutions point to undefined, so that's not very useful.
I realize this is an internal API, but the work (resolution) has already been done for type checking, so I just need to results exposed. Any chance to get an official API exposing this information? It would cover my use case and simplify many others, like tslint's and other TypeScript integrations.


Support npm config params

In our scripts we are using $npm_config_xxx params.
for example:
"scripts": {
    "zip": "cd $npm_config_outdir && zip -rT $npm_config_outzip .",
    "crx": "crx pack $npm_config_outdir",
    "zip-crx": "npm run zip && npm run crx",
}

We can run such scripts via:
npm run zip-crx --outdir=dist --outzip=archive.zip

it would be great if npm-run-all support such npm params and not confuse it with own params or command own params.
Currently I get error:
ERROR: Invalid Option: --outdir=dist

Thank you for this issue.
I have not been aware of that feature of npm. (though npm-run-all supports $npm_package_config_xxx variables since #13).
I will do.

Thanks a lot for quick reply and actions!
When you plan to release?

Just now, I released v3.1.0 :smile:
Please tell me if there are problems.
Thank you!

This needs to be reverted. it was poorly planned and thought out.


Missing methods

Add i2cConfig(), i2cWrite(), i2cRead() and i2cReadOnce methods because Johnny-Five expects those now.

I've got this in my fork. Coming soon.

'bout time
;)

Ya, I completely forgot it wasn't finished. My personal plate (as opposed to my business plate) is pretty clean so I'm going to focus on this. I forgot how complicated this was. Going to try and improve the comments as I "re-learn" it.

Noticed the J5 website claims support for I2C: http://johnny-five.io/platform-support/#electric-imp-april

I submitted a PR to update the website. I've got I2C working but it's not ready for release.

Yeah, that was a little overly optimistic of me.


[idea for task] language models for solving the halting problem

The Halting Problem is well-known to be uncomputable (c.f. here or here.) In fact, some relatively short programs are known to have haltingness independent of ZFC (which essentially formalizes modern mathematics).* Nevertheless, many programs (including, I think, the vast majority of programs that real, working programmers write) are known for certain to either halt or run forever. However, determining whether a program halts or runs forever requires a deep understanding of how code works.
In this task, I propose to use performance on the halting problem as a benchmark for language modeling. To evaluate performance on this task, one would collect a number of programs for which haltingness is known (ideally, documented with a formal proof), then test the language model's performance on predicting the manually-collected labels.
(This task idea was originally proposed by @RomanPlusPlus here.)
*In fact, Martin Ugarte constructed a 748-state Turing machine with this property sometime around last year, beating the original bound of 7918 states by Aaronson & Yedidia 2016 by about an order of magnitude. I think that the bound could be optimized by another order of magnitude, but this is just a digression at this point.

Thank you for posting it!
In the simplest case, we could use a code like this, and just replace bound and delta with random numbers:
a = 0
while a < bound:
    a += delta

In this case, the model must guess if the code will halt for the given bound and delta


pythonPackages.flask-swagger: init at 0.2.14

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pythonPackages.flask-swagger python3Packages.flask-swagger

Thanks @vanschelven!


Minor updates to links

Fix dead link to disclaimer in footer and clean up links to avoid redirects
Use HTTPS links where possible

Thanks @anand-bhat appreciate the help!


Fix incorrect information about matrix strategy for entire workflows

This pull request addresses an error in the documentation that incorrectly suggested that the matrix strategy can parallelize entire workflows.
The matrix strategy is used to run multiple jobs within a single workflow based on a combination of variables, but it does not apply to parallelizing across workflows. This correction ensures that users have the right information when configuring their GitHub Actions workflows.
PR Type

[ ] Adding new question(s)

Warning: We do not support the inclusion of questions directly copied from official GitHub certification exams. Please only submit original questions and content that you have created.

[x] Other content changes (updating questions, answers, explanations or study resources)
[ ] Code changes (non-content)
[ ] Documentation changes
[ ] Other

What's new?
Updated documentation to reflect that the matrix strategy only applies to jobs within a workflow, not across multiple workflows.
Related issue(s)

Screenshots

I just finished the practice exam and thought there was an issue with the answer.
I think the answer should stay as "Yes." While matrix strategies work within a single workflow, they can still parallelize reusable workflows by running them as part of matrix-defined jobs.

The matrix strategy is used to run multiple jobs within a single workflow based on a combination of variables
It does run multiple jobs within a single workflow, but the question asks if you can run a whole workflow using a matrix strategy, which in this case is a reusable workflow.

I just finished the practice exam and thought there was an issue with the answer.
I think the answer should stay as "Yes". While matrix strategies work within a single workflow, they can still parallelize reusable workflows by running them as part of matrix-defined jobs.

The matrix strategy is used to run multiple jobs within a single workflow based on a combination of variables

It does run multiple jobs within a single workflow, but the question asks if you can run an entire (emphasizes the scope) workflow using a matrix strategy, which in this case is a reusable workflow.

@tfsjohan can you take a look? I think he has a point and this shouldn't have been merged. Also some guy also raised an issue about this right now too


Change index.ts to not conflict with standard prism.js

The following line conflicts with some functions in index.ts and is commented out:
https://github.com/smartcontractkit/documentation/blob/78d54631d0706393fd12ccf6d94ff79bcf6f9bf8/_src/prism.js#L17
Identify the and resolve conflict in index.ts.

Fixed in #474


AIX - condvar_1 and condvar_2 tests failing

failure in newly added tests runs for AIX
https://ci.nodejs.org/job/libuv+any-pr+multi/nodes=aix61-ppc64/250/console

`condvar_1` failed: timeout
Output from process `condvar_1`: (no output)
=============================================================

I have similar failure at condvar_1 and condvar_5 on a ppc32 Linux box as follows:
=============================================================
[%   5|+  14|-   0|T   0|S   0]: condvar_1
`condvar_1` failed: timeout
Output from process `condvar_1`: (no output)
=============================================================
[%   6|+  17|-   1|T   0|S   0]: condvar_5
`condvar_5` failed: timeout
Output from process `condvar_5`: (no output)
=============================================================

It seems to be caused by deadlock because the worker thread is run before the remaining parent thread is executed.
The following patch fixes this problem. However, it means that uv_cond_wait and uv_cond_signal are not tested.
--- a/test/test-condvar.c
+++ b/test/test-condvar.c
@@ -63,7 +63,9 @@ TEST_IMPL(condvar_1) {

   uv_mutex_lock(&wc.mutex);
   uv_sleep(100);
-  uv_cond_wait(&wc.cond, &wc.mutex);
+  while (wc.posted == 0) {
+    uv_cond_wait(&wc.cond, &wc.mutex);
+  }
   ASSERT(wc.posted == 1);
   uv_mutex_unlock(&wc.mutex);

@@ -87,7 +89,9 @@ TEST_IMPL(condvar_2) {
   ASSERT(0 == uv_thread_create(&thread, worker, &wc));

   uv_mutex_lock(&wc.mutex);
-  uv_cond_wait(&wc.cond, &wc.mutex);
+  while (wc.posted == 0) {
+    uv_cond_wait(&wc.cond, &wc.mutex);
+  }
   uv_mutex_unlock(&wc.mutex);

   ASSERT(0 == uv_thread_join(&thread));
@@ -161,7 +165,9 @@ TEST_IMPL(condvar_5) {

   uv_mutex_lock(&wc.mutex);
   uv_sleep(100);
-  uv_cond_wait(&wc.cond, &wc.mutex);
+  while (wc.posted == 0) {
+    uv_cond_wait(&wc.cond, &wc.mutex);
+  }
   ASSERT(wc.posted == 1);
   uv_mutex_unlock(&wc.mutex);

@hrektts mind sending that as a Pull Request? Thanks!

Does it have anything to do with the sleep times ?
uv_sleep(100);
ie would it pass if the sleeps were longer ?

I guess so, but generally we should wait for the condition to be set in a loop, to avoid spurious wakeups.

Agreed was just trying to understand if there was a better option than just disabling

I was in the same situation as @mhdawson . Hope the PR resolve this problem. Please feel free to correcting any mistakes!

Can this issue be closed?
https://ci.nodejs.org/job/libuv+any-pr+multi/nodes=aix61-ppc64/274/console
Doesnt fail in latest CI against v1.x

Sure it can!


Ability to modify number of cards in combo/separating cards in deck from overall cards

Title explains most of it. Some combos need a somewhat specific card (like a mana dork) and should arguably be called 2 card combos. There aren't any real needs to lower cards in combo though.  As an expansion of this idea though, could allow us to track cards on hand, graveyard, library, etc. There's certainly lots of possibilities for a feature like this.

The backend allows this


[ENH] updated dba to support custom parameters

Reference Issues/PRs

What does this implement/fix? Explain your changes.
When the distance module was updated support for custom kwargs for the averaging method in kmeans was disabled. This PR updates kmeans to support custom averaging kwargs with the new distance module.

Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Did you add any tests for the change?

Any other comments?

PR checklist

For all contributions

[x] I've added myself to the list of contributors.
[x] Optionally, I've updated aeon's CODEOWNERS to receive notifications about future changes to these files.
[x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG] indicating whether the PR topic is related to enhancement, maintenance, documentation, or bug.
[x] For new estimators, I've added the estimator to the online documentation.

should the file still be called bda? Cant we use if for mba etc?


Issues Guidance

Formatting tips:
lists

simply write '1. ' next to the first item, '2. ' etc.

bullets

this time with '- ' to start a line (make sure to include space after dash)

headers
(put a '# ' next to a line for largest heading, '## ' for smaller sub-heading, '### ' even smaller etc.)
links and more
Links are picked up automatically. For more options see: https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf


Expanded Picard/GA4GH documentation

@iliat Really nice work here!  Just a few minor comments, but otherswise this LGTM.

@deflaux Thanks ! Addressed comments (deletion, links in conf.py). PTAL.

Sorry @iliat  I noticed a few more minor things I did not notice the first time around.

Thanks @deflaux ! Addressed the latest round of comments.

This LGTM @iliat and fixes https://github.com/googlegenomics/readthedocs/issues/53 - thanks!


Concurrency bug in testing

When you run tests first time, some tests fail. Then if you rerun unpassed tests, they will pass. Seems like a bug in concurrency

I had a static lock in the tests to fix that.  Each TestInitialize would lock and TestCleanup would unlock.
Supposedly, you can get MSTest to not run concurrently as well but I was too lazy to look into it.