rdbms-connect 1.0.3 seems to be broken

If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Related command
az postgres flexible-server execute -h
Extension name (the extension in question)
rdbms-connect
Description of issue (in as much detail as possible)
When I try to run az postgres flexible-server execute -h with version 1.0.3 of the rdbms-connect extension I get this:
The command failed with an unexpected error. Here is the traceback:
dlopen(/Users/edeandre/.azure/cliextensions/rdbms-connect/psycopg2/_psycopg.cpython-310-darwin.so, 0x0002): Library not loaded: '/opt/homebrew/opt/postgresql/lib/libpq.5.dylib'
  Referenced from: '/Users/edeandre/.azure/cliextensions/rdbms-connect/psycopg2/_psycopg.cpython-310-darwin.so'
  Reason: tried: '/opt/homebrew/opt/postgresql/lib/libpq.5.dylib' (no such file), '/usr/local/lib/libpq.5.dylib' (no such file), '/usr/lib/libpq.5.dylib' (no such file)
Traceback (most recent call last):
  File "/opt/homebrew/Cellar/azure-cli/2.40.0/libexec/lib/python3.10/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/homebrew/Cellar/azure-cli/2.40.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 561, in execute
    self.commands_loader.load_arguments(command)
  File "/opt/homebrew/Cellar/azure-cli/2.40.0/libexec/lib/python3.10/site-packages/azure/cli/core/__init__.py", line 507, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
  File "/opt/homebrew/Cellar/azure-cli/2.40.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 318, in load_arguments
    super(AzCliCommand, self).load_arguments()
  File "/opt/homebrew/Cellar/azure-cli/2.40.0/libexec/lib/python3.10/site-packages/knack/commands.py", line 104, in load_arguments
    cmd_args = self.arguments_loader()
  File "/opt/homebrew/Cellar/azure-cli/2.40.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
    op = self.get_op_handler(self.op_path)
  File "/opt/homebrew/Cellar/azure-cli/2.40.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
    handler = import_module(mod_to_import)
  File<EMAIL_ADDRESS>line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/Users/edeandre/.azure/cliextensions/rdbms-connect/azext_rdbms_connect/custom.py", line 10, in <module>
    import psycopg2
  File "/Users/edeandre/.azure/cliextensions/rdbms-connect/psycopg2/__init__.py", line 51, in <module>
    from psycopg2._psycopg import (                     # noqa
ImportError: dlopen(/Users/edeandre/.azure/cliextensions/rdbms-connect/psycopg2/_psycopg.cpython-310-darwin.so, 0x0002): Library not loaded: '/opt/homebrew/opt/postgresql/lib/libpq.5.dylib'
  Referenced from: '/Users/edeandre/.azure/cliextensions/rdbms-connect/psycopg2/_psycopg.cpython-310-darwin.so'
  Reason: tried: '/opt/homebrew/opt/postgresql/lib/libpq.5.dylib' (no such file), '/usr/local/lib/libpq.5.dylib' (no such file), '/usr/lib/libpq.5.dylib' (no such file)

When I downgrade the extension to 1.0.2 it works fine.

route to CXP team

@edeandrea I am not able to reproduce this and az postgres works fine with the rdbms-connect - 1.0.3 version.

I already have the latest version of the az cli
╰─ az version
{
  "azure-cli": "2.40.0",
  "azure-cli-core": "2.40.0",
  "azure-cli-telemetry": "1.0.8",
  "extensions": {
    "containerapp": "0.3.10",
    "log-analytics": "0.2.2",
    "rdbms-connect": "1.0.2"
  }
}

Not sure if it matters but I'm running a Mac M1. macos 12.6

@edeandrea ok. got it. It looks like issue with the initial dependencies not available on macOS machine which normally gets installed during the installation or rdms-connect version.  Can you please try upgrading rdbms-connect version to 1.0.3.  I am also checking internally in the meantime if there are any known issues.

The issue is when I upgrade to 1.0.3 it no longer works. It works fine on 1.0.2.

@edeandrea Thanks for the updates.  I am checking internally on this and get back to you at the earliest. Thanks

Thank you.
@agoncal have you run into this?

I am also experiencing this bug when I install version 1.0.2 or 1.0.3. It keeps attempting to install 'clang' and failing.
Also on Mac M1. macos 12.6

@edeandrea Product team has released a new version of rdbms-connect (1.0.4) that could possibly solve this issue for macOS. Can we please check and confirm back if it works for with version 1.0.4?

Hi @SaurabhSharma-MSFT 1.0.4 seems to work fine for me! Thanks for following up!

@edeandrea  Great to hear. We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Mark plugin for Toil 7.0+

This should be ready for release, the current master branch already labeled the plugin as version 2.0.0

Seems like the gitlab runner doesn't have AWS credentials loaded in the environmental variable?
$ mkdir -p ~/.aws && cp "$GITLAB_SECRET_FILE_AWS_CREDENTIALS" ~/.aws/credentials
cp: cannot stat '': No such file or directory

I needed to expose the CI variables to unprotected branches.
I've added an upper version bound here, so we can bump the Toil version if we need to disclaim compatibility with old releases of the plugin.


Update to Cadence v0.42.5

Description
Automatically update to:

onflow/cadence v0.42.5
onflow/flow-go-sdk v0.41.16
onflow/flow-go e4011e4c93e4
onflow/flow-emulator v0.57.1

@m-Peter Do the changes to the test tests in 11bfd48 look OK?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (465f9fc) 41.19% compared to head (11bfd48) 41.19%.
Report is 5 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1264   +/-   ##
=======================================
  Coverage   41.19%   41.19%
=======================================
  Files          39       39
  Lines        2068     2068
=======================================
  Hits          852      852
  Misses       1123     1123
  Partials       93       93

Flag
Coverage Δ

unittests
41.19% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@turbolent The changes look good :100: :clap:
System contracts (RandomBeaconHistory) and utility locations (BlockchainHelpers) are expected to be excluded from coverage reports. I forgot to exclude the BlockchainHelpers in the previous release, hence the change in the code coverage percentage on the test cases.


[BUG] Incorrect logits/loss/outputs on GPT-NEOX-20B

Describe the bug
DeepSpeed(DS) optimized GPT-NEOX-20B model produces incorrect logits and loss, which hurts overall model accuracy. Numerical differences on final logits for a test phrase (see code) is as follows:

avg L2
rel L2
avg L1
max elem. diff

DS fp32 vs ACC fp32
23.070
0.00819222
3.458
36.657

DS fp16 vs ACC fp16
24.700
0.0087669
3.497
40.742

We expect a relative l2 being around 10^(-5) or smaller. The computed loss on this test phrase is 4.08 (DS FP32) vs 2.42 (HF/ACC FP32), and 4.34 (DS FP16) vs 2.43 (HF/ACC FP16). There is a huge difference in computed loss/logits which does affect overall model's quality. The bug manifests on longer text sequences, probably due to some accumulation of numerical errors. The bug affects the latest (mainline) deepspeed and version 0.7.5. (Other versions might be impacted as well, didn't test)
Note: we are comparing against HuggingFace's Accelerate output since the model does not fit a single gpu in my machine.
Here the following formulas are used:

avg l2 diff is computed as $\sum_i \frac{1}{N}(x_i-y_i)^2$
rel l2 diff as $\frac{\sum_i (x_i-y_i)^2}{\sum_i y_i^2}$
avg l1 diff is computed as $\sum_i \frac{1}{N}|x_i-y_i|$

where $x$ is output of model1 (DS or HF) and $y$ is output of model2 (ground truth).
To Reproduce
To reproduce the behavior run the following script with different options. The script simply runs deepspeed version and compares the output against the pure huggingface/accelerate version.
Script:
from transformers import AutoModelForCausalLM, AutoTokenizer
import deepspeed
import torch
import os
import transformers

TEST_INPUT = """DeepSpeed is an open source deep learning optimization library for PyTorch.[1] The library is designed to reduce computing power and memory use and to train large distributed models with better parallelism on existing computer hardware.[2][3] DeepSpeed is optimized for low latency, high throughput training. It includes the Zero Redundancy Optimizer (ZeRO) for training models with 1 trillion or more parameters.[4] Features include mixed precision training, single-GPU, multi-GPU, and multi-node training as well as custom model parallelism. The DeepSpeed source code is licensed under MIT License and available on GitHub.[5]

The team claimed to achieve up to a 6.2x throughput improvement, 2.8x faster convergence, and 4.6x less communication.[6] """

def simple_output_DS(dtype):
    model_id = 'EleutherAI/gpt-neox-20b'
    model = AutoModelForCausalLM.from_pretrained(model_id).to(device='cpu', dtype=dtype)
    tokenizer = AutoTokenizer.from_pretrained(model_id)
    world_size = int(os.getenv('WORLD_SIZE', '1'))
    local_rank = int(os.getenv('LOCAL_RANK', '0'))

    model = deepspeed.init_inference(model,
        mp_size=world_size,
        dtype=dtype,
        replace_method='auto',
        replace_with_kernel_inject=True)

    encodings = tokenizer(TEST_INPUT, return_tensors="pt")

    input_ids = encodings.input_ids.to(f'cuda:{local_rank}')
    out = model(input_ids, labels=input_ids)
    output_logits = out['logits'].cpu().to(dtype=torch.float32)
    if local_rank == 0:
        torch.save((output_logits, out['loss']), f"logits-DS-{dtype}.pt")
        print(out['loss'])

def simple_output_ACC(dtype):
    local_rank = int(os.getenv('LOCAL_RANK', '0'))
    model_id = 'EleutherAI/gpt-neox-20b'
    model = AutoModelForCausalLM.from_pretrained(model_id, device_map="auto").to(dtype=dtype)
    tokenizer = AutoTokenizer.from_pretrained(model_id)

    encodings = tokenizer(TEST_INPUT, return_tensors="pt")

    input_ids = encodings.input_ids.to(f'cuda:{local_rank}')
    out = model(input_ids, labels=input_ids.clone().to(model.get_output_embeddings().weight.device))
    output_logits = out['logits'].cpu().to(dtype=torch.float32)
    if local_rank == 0:
        torch.save((output_logits, out['loss']),  f"logits-HF-{dtype}.pt")
        print(out['loss'])

def compare_outputs(dtype):
    output_logits_m1, loss_m1 = torch.load(f"logits-DS-{dtype}.pt")
    output_logits_m2, loss_m2 = torch.load(f"logits-HF-{dtype}.pt")

    relative_avg_l2 = (output_logits_m1 - output_logits_m2).pow(2).sum()/output_logits_m2.pow(2).sum()
    avg_l2 = (output_logits_m1 - output_logits_m2).pow(2).mean()
    avg_l1 = (output_logits_m1-output_logits_m2).abs().mean()
    max_l1 = (output_logits_m1-output_logits_m2).abs().max()
    print(f"loss ds: {loss_m1.item()}")
    print(f"loss hf: {loss_m2.item()}")
    print(f"L2^2: avg_l2={avg_l2:.8f} avg_relative_l2={relative_avg_l2:.8f}; (in scientific notation: {relative_avg_l2:.5e}")
    print(f"L1: avg_l1={avg_l1:.8f} max_elementwise_l1={max_l1:.8f}")

import argparse
if __name__ == "__main__":
    parser = argparse.ArgumentParser(description='Command line tool to check LLM correctness')
    parser.add_argument('--local_rank', type=int)
    parser.add_argument('--use_ds', action='store_true')
    parser.add_argument('--use_hf', action='store_true')
    parser.add_argument('--compare', action='store_true')
    parser.add_argument('--dtype', choices=['fp16', 'fp32'], default='fp16')

    args = parser.parse_args()

    if args.dtype == 'fp32':
        dtype = torch.float32
    elif args.dtype == 'fp16':
        dtype = torch.float16

    if args.use_ds:
        simple_output_DS(dtype)
    elif args.use_hf:
        simple_output_ACC(dtype)
    elif args.compare:
        compare_outputs(dtype)

Save the code above as comparison.py and execute it as:
deepspeed comparison.py --dtype fp16 --use_ds
python comparison.py --dtype fp16 --use_hf
python comparison.py --dtype fp16 --compare

Note: you need to have HF's accelerate installed.
Expected behavior
We expect numerically close outputs, say rel l2 difference around 10**(-5) for fp32 comparison or less (0.0 ideally). We see a huge discrepancy.
ds_report output
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
async_io ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
sparse_attn ............ [NO] ....... [OKAY]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
utils .................. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/usr/local/lib/python3.8/dist-packages/torch']
torch version .................... 1.12.1+cu113
deepspeed install path ........... ['/usr/local/lib/python3.8/dist-packages/deepspeed']
deepspeed info ................... 0.8.0+fe728e3e, fe728e3e, master
torch cuda version ............... 11.3
torch hip version ................ None
nvcc version ..................... 11.3
deepspeed wheel compiled w. ...... torch 1.12, cuda 11.3

System info (please complete the following information):

OS: Ubuntu
GPU: A10G x8
Python 3.8.10

Hi @akamaster, I ran this with the latest deepspeed and observed better results for fp16:
loss ds: 2.4296875
loss hf: 2.431640625
L2^2: avg_l2=0.10383601 avg_relative_l2=0.00003690; (in scientific notation: 3.68962e-05
L1: avg_l1=0.21918750 max_elementwise_l1=2.79687500

Also, I think we do not support fp32. @RezaYazdaniAminabadi can you confirm?

fp32 is not currently supported, but we may add that soon.


Condition for HtmlParseErrorCode.CharsetMismatch

There is a special error HtmlParseErrorCode.CharsetMismatch  during parsing of document. Now its condition is:
if (_declaredencoding.WindowsCodePage != _streamencoding.WindowsCodePage).
Some encoding like Latin1 and ASCII have the same 1252 windows code page. But their are different and produce different results when parsing document. Propose to use CodePage property of encoding instead of WindowsCodePage.

Hello @aktzbn ,
Thank you for reporting,
We will try to look at this issue soon.
Best Regards,
Jonathan

Hello @aktzbn ,
A new version has been released v1.5.2-beta4,
We made the change as you recommended.
Best Regards,
Jonathan

Hello @aktzbn ,
We will close this issue, feel free to re-open if you still have it.
Best Regards,
Jonathan


Include voicemail-en-us speech model in EX

IN addition:

fix spelling error in stereo.md
remove “please don’t use dev docs” statement, since this statement is
getting copied to prod.

Can you give an example of what that would look like?
-Dnaiel

On Aug 4, 2017, at 3:34 PM, cerebrotecnologico<EMAIL_ADDRESS>wrote:
@cerebrotecnologico requested changes on this pull request.
Voicemail requires an "extension" in /v3 under "speechModel"
In docs/how-to-guides/voicemail.md https://github.com/voicebase/voicebase-docs/pull/34#discussion_r131499060:

{

"speechModel" : { "language" : "voicemail-en-US" },
In /v3 "language" must be "en-US" and you can add "extensions" and set it to "voicemail".

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/voicebase/voicebase-docs/pull/34#pullrequestreview-54491436, or mute the thread https://github.com/notifications/unsubscribe-auth/AM1gXB-hFtdMmGwh4L40kZo_CzUj_XXDks5sU5xqgaJpZM4OkiyO.

{
   "speechModel" : {
         "language" : "en-US",
          "extensions" : [ "voicemail" ]
   }
}


DXTK Collisions

I just wanted to ask if it's possible to edit the actual code and get the point of collision for example of a triangle-ray test, I've been messing with the code but I couldn't get it, I'm a bit lost to find this...

I'm not sure what it is you are doing here. For most games, the best solution for collision is to use tests with bounding volumes (spheres, bounding boxes, oriented bounding boxes) as supported by DirectXMath.
Face-by-face triangle-level tests are very expensive, so it should be avoided as much as possible or at least have first-level collision using bounding volumes.
The main feature that is missing from DirectX Tool Kit to support triangle-level collision testing is that Model only puts the geometry data into GPU IBs/VBs. To support this kind of collision, it would need to return a std::vector of indices as well as a std::vector of positions (i.e. a collision mesh per this work item).


Enforce sourcing nvm

This fixes an issue where nvm would not be loaded if a package path
is not found (such as when deploying 'simple' project directories).

LGTM :shipit:

:+1:

building new image for staging, will merge and close after testing


Navigating to "About" then back to "Home" causes the wall image to disappear

If you upload an image, then navigate to the About page and navigate back to home, Diagram 1 will be seen.
Expected behaviour
The image should still be there after page navigations
Diagram 1

Hi
https://github.com/yarkhinephyo/yolo_bouldering/pull/41
Tried to fix the issue here will test and give a final fix.
Need some time to cope up with aws and serverless, any pointers or helper docs to set up dev environment is appreciated.
Thank you.

Hi!
Thank you so much for the PR.
Just follow the setup instructions to set up the backend dev environment.
But maybe give me an hour? I will create a dev endpoint for you.
Regards,
Phyo
On Mon, Apr 26, 2021 at 6:50 PM wasiqe @.***> wrote:

Hi
#41 https://github.com/yarkhinephyo/yolo_bouldering/pull/41
Tried to fix the issue here will test and give a final fix.
Need some time to cope up with aws and serverless, any pointers or helper
docs to set up dev environment is appreciated.
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yarkhinephyo/yolo_bouldering/issues/33#issuecomment-826733233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEXSZ5FST6EXSN2V73SYPSDTKVAQDANCNFSM43QGKX4A
.

@wasiqe Can you email me so that I can send you? Thank you :)

Closed after migration to vue 3 in new code base


Update MinGW in Windows Server 2019 image for (probably) future Rust support

Tool name
MinGW64
Tool license
GNU
Add or update?

[ ] Add
[X] Update

Desired version
Any version with "rt_v8" or above
Approximate size
No response
Brief description of tool
The current version of mingw installed on Windows 2019 hosts is x86_64-8.1.0-release-posix-seh-rt_v6-rev0.7z (or the i686 equivalent). I believe rt_v6 means that it corresponds to v6.0.0 from September 2018.
There was a fix targeting v8.0.0 (https://github.com/mirror/mingw-w64/commit/68d0e7d551d2e2a5b8a15bdca3f8d15fc097ed01) released in 2020 that is necessary for the x86_64-pc-windows-gnu toolchain of rustc 1.78.0-beta.7 to work properly when installed with the default configuration. With the current version, trying to build Rust programs with that toolchain results in an ambiguous STATUS_ENTRYPOINT_NOT_FOUND error.
More details about this particular issue can be found in https://github.com/rust-lang/rust/issues/123999.
I am aware that this was discussed in https://github.com/actions/runner-images/issues/9009 for a different reason, and the decision was not yet to update. I am mainly filing this issue to help with discoverability and in case this extra use-case is enough of a reason to reconsider.
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[X] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
Based on https://github.com/actions/runner-images/issues/9009, it is probably possible, although the purpose of this request is to try avoiding potential pitfalls.

Tool installation time in runtime
No response
Are you willing to submit a PR?
I unfortunately don't have enough experience with mingw64 to confidently help here.

Hello @patowen!
We will consider upgrading the MinGW version and will let you know as soon as we make a decision.

Regarding whether to upgrade this, I don't have a strong stake in the final decision. The underlying issue I'm wanting to resolve can be resolved from several different angles, and this is just one of them:

Upgrading mingw so that the default gcc version in the PATH points to one that works well with rustc 1.78.0-beta.7 (the suggestion in this ticket)
Making rustc more robust in handling older versions of mingw (which might happen as part of https://github.com/rust-lang/rust/pull/124019)
Updating the x86_64-pc-windows-gnu Rust toolchain installation to use its own embedded version of mingw if the version installed is outdated (not sure if feasible or helpful)
Updating actions-rs/toolchain to warn or somehow handle the case of an old version of mingw
Doing nothing and suggesting a workaround for anyone encountering this issue (such as using runs-on: windows-2022 instead)
Something I hadn't thought of

I don't have a good sense of all the pros and cons of updating the mingw version or the other options, as I lack experience in GitHub actions and internal aspects of Rust, so I don't want to make any strong recommendations here.

Speaking only for Rust...

Updating the x86_64-pc-windows-gnu Rust toolchain installation to use its own embedded version of mingw if the version installed is outdated (not sure if feasible or helpful)

Using the system mingw (if available) is usually preferable so I don't think this is a desirable option.

Making rustc more robust in handling older versions of mingw (which might happen as part of https://github.com/rust-lang/rust/pull/124019)

This would workaround the issue for the nightly compiler. However, this has reached beta so it would need a backport to avoid affecting the next stable release. I don't yet know if a backport would be accepted considering this is, technically speaking, a bug outside of Rust itself. But I'll ask.
Note though that it is just a workaround for Rust's standard library. It obviously won't fix it for other use cases (e.g. a C++ application importing these functions). Then again, considering this is the first report, perhaps it's not a pressing issue otherwise.

Hello @patowen. Unfortunately due maintain concerns we not ready to upgrade mingw for windows images Because that could be make cause huge impact for other users. I am closing this tread but we will continue track similar issues for possible changing decision. If you have additional questions feel free to ask.

Thanks for the heads up, and no worries at all! Fortunately, I saw that the "beta-accepted" label has been applied to the Rust PR, so it seems like it will be backported after all. Especially given this change in the landscape, I believe I also agree with this decision to hold off on upgrading mingw.


Unable to open in chrome  (not secure) http://

hi
Unable to open in chrome  with http:// but https:// is wokring ,  when we compile android app unable to open webview apk,  Mozilla its working in both http:// and https://
Thanks

Yea its chrome matter, it need https access


bug:Anonymous avatar and username not updating properly/not showing

Other people I have talked to also had this problem, no matter how many times they update their profile, both the avatar and username of anonymous users never change to the chosen ones; even after trying to change it in multiple devices and image hosting sites. Other images in the page work fine.

Should be fixed now, thanks!
Feel free to reopen if I missed a spot where these should show.


Doctor Signup and Doctor Side Issues

[x] If the user asks to be a doctor and closes the app, the app stucks on the splash screen. It needs to start from the beginning and ask for the mobile phone number.

[x] All right, so if I'm getting this right, a doctor adds a phone number of another doctor first, then the second doctor can register as a doctor. In this case, let's add a check on the Doctor/Patient select. We don't need this check. If the phone number is given by another doctor, he can be registered as doctor, otherwise the phone can be registered as a patient automatically. Is that sound good?

[x] The new line issue is happening on your specialisation, Hospital Name text box.

[x] The home page list looks good and the search box looks great.

[ ] When a search text is entered and removed, the patient list doesn't seem to refresh.

[x] The patient list doesn't get all the patients for now. They seem to be hardcoded, since the database only has 2 patients for now.

[x] Patient profile looks great.

[x] Monitor Patient Healt screen looks great.

[x] Monitor Patient Health: None of the items seem to save the new and/or old items to the database. This screen will be completed.

[ ] Monitor Patient Health: Last Visit Date and Next visit date will show a calendar box. I don't understand the purpose of Edit button here. If the date changes, it can save the date automatically, or Save button can appear here after edit.

[ ] The issue for the (Doctor side) Notifications screen will be created.

[x] The issue for the (Doctor side) chat screen will be created.

Monitor Patient Health: Last Visit Date and Next visit date will show a calendar box. I don't understand the purpose of Edit button here. If the date changes, it can save the date automatically, or Save button can appear here after edit.

The purpose is to prevent accidentally tapping the text fields. I'll add the calendar thing on those boxes. Whenever the doctor wants to change the dates, he'll click on edit, and then text fields get activated. On pressing Save, the fields are again made inactive.

When a search text is entered and removed, the patient list doesn't seem to refresh.

This was happening due to the use of AnimatedList which had a property of initial list count. In some specific cases, the list didn't get refreshed. Replacing with ListView.builder() resolves the issue.


Remix Icons Setup

Icon Component Creation
In this pull request, a new Icon component has been introduced. The main use case of this component is to create a component that can dynamically generate icons based on the icon name.
Changes Made:

New Component:

Created a new Icon component.

Dynamic Icon Creation:

Implemented logic within the Icon component to dynamically render the icons based on the icon name.

Addition of New Library:

Added a new icon library, "Remix Icons," which complements the theme of our website and is also used in the current Figma designs.

Coming soon page:

Added a separate component to render the Coming Soon page.

Benefits:

Centralized management of icons based on their names.
Improved code organization by creating a dedicated component for handling icons.

Destructured the props object directly in the function signature to make the code cleaner and avoid repetitive props. references.


Add extensive comments to rpc_hello example

Why are these changes needed?
Add comments to the rpc_hello example for anyone new to Rust.

cc @crazyboycjr


Fix 350 truncate movement

I'm going ahead and opening this PR because things look good on my end. I hope I've done this right, and I'm concerned by how big a diff this is showing. I only changed three files: MapUnit, MovementPoints, and LowerRightInfoBox
I just pulled from godot4 for my branch and until I made these changes it said they were up to date (up to date with Prototype / godot4, not just my fork. I could use some advice on this one, let me know if I've done something wrong here.
Solving this issue: https://github.com/C7-Game/Prototype/issues/350

Hmm Ok I think I know what went wrong. I'm going to close this and open another (hopefully correct) pr


Work around GHCI Mac problem with homebrew openssl

Sorry for the weird boilerplate. Was testing PR submission from the command line for the first time!
(But this is a real PR)


Adds  component

addresses https://artsyproduct.atlassian.net/browse/PURCHASE-42 and is possibly related to https://artsyproduct.atlassian.net/browse/PURCHASE-34
The goal of this PR is to set up a foundation where all the components for the new bidding flow lives, by actually building a component. I picked up the pattern used for the Consignments directory to get started, but wanted to make sure that this is the pattern we all feel comfortable with before I move forward too deeply.
In this PR there's only <SelectMaxBid>, but I'd imagine that the Screens/ will grow as we implement more pages and add a Components/ directory to organize smaller components. One interesting thing we are going to do is that a subclass of UIViewController may have to live in the Emission as well. so we'll have to think about how we are going about this.
This PR is basically just a conversation starter. I'm not really tied to any specific pattern at this point. We don't even have to follow the existing pattern if there's something that feels more organized. Any feedback is welcome!
Directory structure:
src/lib/Components/Bidding/
├── Screens
│   └── SelectMaxBid.tsx
├── __stories__
│   └── Bidding.story.tsx
└── __tests__

The <SelectMaxBid> component:

@yuki24 The UIViewController will live in the pod (= the library that we export to Eigen).
If you look in emission/Pod/Classes/ViewControllers you will see that we already have some corresponding native view controllers, and how they work. For example, the ARArtistComponentViewController. Similarly, we would probably get a ARNewBidComponentViewController or something 😄. (edit = this is what @ashfurrow's PR does).
The AppRegistry.tsx is where components then get registered with the corresponding containers. The module name coming from the native view controller will be matched up to the right high level RN container / component.
The reason all native (objective C) view controllers start with AR by the way, is to make them unique. This is a bit of a legacy iOS thing, and so it's common practice to pick 2-3 letters that denotes your organisation or project. In our case, AR = Artsy.

Also, I'm not sure what's up with CI. It's requesting a Danger API key? @orta, soz, would you know anything about this?

It's a cross-fork PR, which we don't normally do on mobile repos ^

Ohhh of course. I didn't realise that would cause this Danger error. Thanks @orta!

ah I see. I'll close this PR and open an new, in-repo PR.


ModuleNotFoundError: No module named 'tqdm.auto

Stable diffusion runs perfectly well until you install any extension which calls for  tqdm , I've tried with multiple extensions, and its hit and miss which ones contained this error .. but it completely breaks stable diffusion which then refuses to launch once the extension has been added,
"Launching Web UI with arguments: --xformers --medvram
Traceback (most recent call last):
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\launch.py", line 41, in
main()
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\launch.py", line 37, in main
start()
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\modules\launch_utils.py", line 439, in start
import webui
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\webui.py", line 13, in
initialize.imports()
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\modules\initialize.py", line 21, in imports
import gradio  # noqa: F401
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\gradio_init_.py", line 3, in
import gradio.components as components
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\gradio\components_init_.py", line 1, in
from gradio.components.annotated_image import AnnotatedImage
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\gradio\components\annotated_image.py", line 8, in
from gradio_client.documentation import document, set_documentation_group
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\gradio_client_init_.py", line 1, in
from gradio_client.client import Client
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\gradio_client\client.py", line 24, in
from huggingface_hub import CommitOperationAdd, SpaceHardware, SpaceStage
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\huggingface_hub_init_.py", line 322, in getattr
submod = importlib.import_module(submod_path)
File "C:\Users\Aaron\AppData\Local\Programs\Python\Python310\lib\importlib_init_.py", line 126, in import_module
return _bootstrap.gcd_import(name[level:], package, level)
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\huggingface_hub\hf_api.py", line 35, in
from huggingface_hub.utils import (
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\huggingface_hub\utils_init.py", line 18, in
from . import tqdm as _tqdm  # _tqdm is the module
File "C:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\lib\site-packages\huggingface_hub\utils\tqdm.py", line 63, in
from tqdm.auto import tqdm as old_tqdm
ModuleNotFoundError: No module named 'tqdm.auto'
Press any key to continue . . .

This is what I've found to get stable diffusion running again , but it may break functionality.
pip install tqdm==4.57.0
This install a version in which the bug doesn't occur .to do so
C:>cd c:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\Scripts
c:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\Scripts>activate.bat
Venv will appear on the left before the drive number, (venv) c:
which will allow you to install the specific version of tqdm in this case the functional one being 4.57.0
(venv) c:\1ststable\stable-diffusion-webui-1.6.0-RC\venv\Scripts>pip install tqdm==4.57.0
Collecting tqdm==4.57.0
Downloading tqdm-4.57.0-py2.py3-none-any.whl (72 kB)
---------------------------------------- 73.0/73.0 kB 366.8 kB/s eta 0:00:00
Installing collected packages: tqdm
Attempting uninstall: tqdm
Found existing installation: tqdm 4.11.2
Uninstalling tqdm-4.11.2:
Successfully uninstalled tqdm-4.11.2
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
moviepy <IP_ADDRESS> requires tqdm==4.11.2, but you have tqdm 4.57.0 which is incompatible.
Successfully installed tqdm-4.57.0
and it will need to be repeated in every folder(separate installation ) you use stable diffusion in .. it doesn't appear to fix system wide for alternate setups you may have


Add frontend build as servable static file to backend

Proposed solution
React supports building exportable production build with static files, which in turn can be served from backend.
What we need:

Handler for serving the static files. Check that it works with react router, which handles url routing inside react app.
Dockerfile build process: maybe git clone from frontends master branch and build front as build-stage and copy it then to backend?

DoD (Definition of Done)
Frontend can be served directly from aiohttp backend.
Testing

probably end-to-end tests with built docker image. We can use Cypress or Selenium for this.

Fixed in #51


Cant connect to Homematic anymore

I agree to the following

[X] I have read the documentation
[X] I am aware of the latest release notes
[X] The Backend (CCU/Homegear/...) is working as expected and connected devices are controllable by its own UI.
[X] I am running the latest version of the custom_component (and Home Assistant)

The problem
HA cant connect to Homematic anymore. I do not get any good Errormessage it only says "Uknown error occured" but when I look to protocol in Homeassistant i see the following error:
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: hahomematic.client.xml_rpc
Source: custom_components/homematicip_local/control_unit.py:713
Integration: Homematic(IP) Local (documentation, issues)
First occurred: 20:57:32 (3 occurrences)
Last logged: 21:12:37
SSLError on temporary_instance-BidCos-RF: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1006)')
What version of HomematicIP (local) has the issue?
1.47
What was the last working version of HomematicIP (local)?
No response
What type of installation are you running?
Home Assistant OS
What type of installation are you running for your homematic backend?
RaspberryMatic Standalone
Which version of your homematic backend are you running?
3.47.15
What hardware are you running for your system?
Proxmox
Which config details do you use

[ ] Username and password
[ ] TLS
[ ] callback data (see)

Which interfaces do you use?

[ ] Homematic IP
[ ] Homematic (Bidcos-RF)
[ ] Groups (Heating-Group)
[ ] BidCos-Wired (HM-Wired)

Diagnostics information
config_entry-homematicip_local-f43f287e2f6ff8ba572746f6ee816cb4.json (2).txt
Anything in the logs that might be useful for us? The log (full log) is the best source to support trouble shooting!
No response
Additional information
No response

Disable the tls verify?

Mate you made my day - I did not have the option for https in ccu so I made an update-> and now I can configure as it should be!
Thank you !!!


Metrics and Kerning Inconsistencies

I have been encountering numerous metrics related issues with Roboto Slab.
First are a few inconsistencies on sidebearings like with the /H 81, 81 .versus the /I 120, 120
Neither glyph's sidebearings correspond to the original ttf which is fine since there were unpublished edits which I am assuming modified spacing a bit, but this is a large 30 unit between sidebearings that should be very similar if not identical.
Proposed Solution: Modify metrics on glyphs (via metrics keys) with extreme deviations from the metrics of identical shapes

Mark alignment is problematic across the board in the source ufos (the unpublished update). On top of this, automatic alignment of components on composite glyphs produce the wrong width and sidebearings, which in turn causes collisions, this is due to using noncombining marks as components rather than combining marks
Proposed Solution: The ideal solution in terms of structuring a good maintainable source file would be to set up glyphs with anchors and combining marks. this would mean making all noncombining marks use a component of the corresponding combining mark and then use the combining marks in the composite glyphs to enable automatic alignment. This would be fine without anchors, but I would argue that a proper anchor setup is more manageable than manually aligning and checking all components in all composites

Overall these inconsistencies mean that very little will match up on GF regressions
@davelab6 I did not want to mess with metrics and kerning so that updates will not deviate drastically from what is currently being served, but they seem necessary. What are your thoughts on how to move forward?

Modify metrics on glyphs (via metrics keys) with extreme deviations from the metrics of identical shapes

Yes, any quality improvements like this are welcome! :)

set up glyphs with anchors and combining marks

Yes, totally renovating the font data to meet modern standards is also very welcome - should reduce filesize too! :)

Overall these inconsistencies mean that very little will match up on GF regressions

That's fine; the purpose of the GFR tool is to be totally conscious about what we are changing and why. When we are improving the quality, some people may grumble that their layouts changed and they have to adjust them, but overall the quality is better for readers and for the long term.


resolves #26 js error with django-grappelli

Test failures are unrelated to your changes. Thanks for for the contribution, we must have broke this when we upgraded jquery.colorPicker to its latest version.


Preview Ajax Fallback on Windows Very Slow

On Windows (tested in Firefox) the fallback to ajax need 10-15 seconds before loading the preview.
Maybe we can find a fast way to check if Server Socket is running.
After the detection function in preview js we should do an ajax to a new controller Action. PreviewController:checkSocketRunning for example. And check over PHP if connection is possible to socket with faster timeout. So we don't need to wait for a socket.error. If the response is true use socket else use ajax.

now we only check websocket once ... this should fasten it very well (= if this is not enough websocket can be set to false in config if it is not started!


[docs] Improved development docs

Implements and closes #19

Pull Request Test Coverage Report for Build 52

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 38:
0.0%

Covered Lines:
114

Relevant Lines:
114

💛  - Coveralls


Consider porting Terraform Provider to a Crossplane provider

What is currently missing?
Currently evaluating Crossplane for in-kubernetes cluster automation, I currently use the Aiven Operator model directly but if I have Crossplane in use it makes sense for a common abstraction in platform engineering to adopt.
How could this be improved?
Maintaining a port of this provider via https://github.com/pulumi/pulumi-terraform-bridge and https://github.com/pulumi/pulumi-tf-provider-boilerplate projects and publish the resulting provider to the Crossplane/Upbound marketplace.

Hey, @danielloader! 👋
Have you checked https://github.com/pulumi/pulumi-aiven out?
Also, could you please elaborate if there are any downsides on using the Pulumi Terraform bridge instead of creating an actual Crossplane provider?

Thanks for the reply, I pasted in the wrong links in the original post, I've updated them to point to Upjet instead.
Yeah I've been doing an evaluation of Crossplane vs tf-controller vs Pulumi, and Aiven was the only provider in my POC that was missing in the Crossplane prototype.
This isn't an urgent request just figured I'd launch an issue to gather interest and ask about feasibility. On paper using Upjet to create a provider is relatively straight forward.


resolve actions warnings

resolve actions warnings

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
38

Relevant Lines:
38

💛  - Coveralls


Steam Controller works (and hidden)

Does this show up on https://steamdb.info/linux/? I don't think we need to manually filter out apps where app type ≠ Game.

Yep, we don't need to hide apps that don't show up on their own.


Look into using getRemoteTime() instead of Date.now()

Expected Behavior
Analytics dashboards always look nice.
Current Behavior
Date.now() uses the time in the users phone, so if they have the wrong time it can show weird stuff, like data in the future or distant past. See an example here: https://metabase.celo-networks-dev.org/dashboard/25 (might be fixed by the time you open the link, so see the screenshot below)

One alternative we have is to use a method called getRemoteTime which uses this library: https://github.com/artem-russkikh/react-native-clock-sync
The library makes a network request to get the real time from a server, avoiding this issues. It caches the time for 5 minutes by default and it's configurable.
The goal of this issue is to look a bit deeper into this and decide if this is a good solution to our dashboard troubles or anywhere else where we use Date.now().

I've fixed this specific dashboard issue by using the Segment provided timestamp. Still worthwhile to explore where else we could benefit from using getRemoteTime instead of Date.now


⚠ Bofrost.com has degraded performance

In a976045, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 421 ms

Resolved: Bofrost.com performance has improved in 815ee8b after 13 minutes.


Add ContextState.Stopped.

@rogeralsing  This fixed bug mentioned on gitter, that messages are still being handled after actor is stopped, if those messages are already in mailbox.

@rogeralsing  We got a bit of problem here.
If we reject any messages when LocalContext status is Stopped, we will face problems like this:
endpoint.Watcher.Tell(EndpointTerminatedEvent)
endpoint.Watcher.Stop()

Mailbox will process Stop message first since it's SystemMessage
LocalContext will become ContextState.Stopped
EndpointTerminatedEvent will no longer be processed.

Imo we go for 1.
endpoint.Watcher.Tell(EndpointTerminatedEvent)  //make the procesing of this event stop internally
endpoint.Watcher.Stop() //remove this

That would work, right?

@rogeralsing
Yep, that would work. But it might break other things as well, for example:
https://github.com/AsynkronIT/protoactor-go/blob/dev/actor/actor_example_test.go#L21
Do you think there are many real world cases that user will call Stop() right after call Tell(...)? If not I think we can just ignore it.

There is also the option to send a PoisonPill, which is a user message, but does a stop.

@rogeralsing Yep, I just got that fixed in this PR.
However I think it is still better to treat Stop as a special message, or let's just remove Stop message type,  and do that using  pid.Stop() => Mailbox.Stop() => Context.InvokeStopAsync(). In this case it can completely eliminate this Tell()/Stop() conflicts.

Problem with not being able to stopp directly is if you have an overloaded actor, mailbox is huge, and the system wants to kill it. then the stop would be stuck at the end of the queue.

@rogeralsing  In this case it might be necessary to introduce Kill() and Stop(), but this will lead to a lot of structure changes. = )
Let's merge this PR first, and I'll see if I got time to explore this direction.

@rogeralsing  I'll do the merge for now.
I just figured out that, actually if user want to have all messages processed before actor stop, for now we can just use PoisonPill.


Bump GitHub labeler to master

We are using any and all, features that only exist on the master branch of actions/labeler; see actions/labeler#73. Bump the action to master, thereby fixing this issue.
Fixes: #38

Appears to be working, LGTM!


Add dependabot config

To enable: https://dependabot.com/dotnet/
The config is generated and must be re-generated as projects are added or directories are re-named.

Well, it won't improve the "build process". It just "improves" the project files as a source asset. It's not conceptually different than running roslyn analyzers with fixs on (if that's a thing) and then having auto-generated PRs.

Yikes. I hope they improve this experience with wildcards. Having a file with three lines per .csproj doesn't look like a great plan to me -- it feels very redundant and can easily break.

I'm not familiar with this. What will the automated PRs contain? How does updating this file works?

This is how it works: https://dependabot.com/#how-it-works
Yes @terrajobst, this is the pattern: https://github.com/dependabot/feedback/issues/632#issuecomment-521448392
I want to adopt this service for the dotnet org for repos where it is valuable. This is GH's service for update PackageReferences and similar things for new packages, via automated PRs.  Once we start using it, we can give feedback. Yes, this model isn't great, but it is what it is and is workable (for now), IMO. I assume they want the config.yml to avoid a lot of compute intensive tasks.

Cool! Thanks for sharing the additional information. I think it’s good to merge.
@Rick-Anderson you might like this for aspnet/docs.

Merging on its own won't do anything (meaning, it's totally fine to merge w/o concern). The important step is turning on the service after that. Anyone can do that but I was going to wait for that step when I got back from vacation. I'm OOF next week. If someone wants to try it ahead of time, feel free. I was only volunteering to do that if there is a mess that needs to be cleaned up.
As an aside (and in response to @terrajobst), I might extend the tool so that it can be run in CI in a test mode (is my current config.yml still valid?). That would help mitigate some of that concern.

I'll let @terrajobst provide any additional concerns before merging. I'm not going to merge before taking off. Feel free to do that, however.

Thanks all.
I'll :shipit: now.

@terrajobst Yes, I agree that wildcards would be better.
We (.NET Content team) also have a long-standing work item to continue to rationalize our samples projects. There are way too many very small projects.


change order of Question 7

Switch the order of the options of question 7.  This should be done in the Typeform admin, and also in the 'formResponseHandler.js' logic, which should be updated to reflect the change

fixed by merge https://github.com/mattg95/07_campaign/pull/165


Documentation blog tutorial deprecated import from modelcluster.tags

I found a deprecated import in the tutorial part of the docs.
Release: Wagtail 1.10.1
The tutorial gets you to create a blog, then add some tags, it uses the following import which Pycharm marks as deprecated:
from modelcluster.tags import ClusterTaggableManager

It should be:
from modelcluster.contrib.taggit import ClusterTaggableManager

it's in this section in the docs: http://docs.wagtail.io/en/v1.10.1/getting_started/tutorial.html#tagging-posts

Thanks for the report @robvdl! Fixed in 6bc6480cd29a6606c86d8505a0f3d53ecd3d69df.


Documentation update: CSI Sidecars versions

Describe the solution you'd like
As some customers run Kubernetes clusters in closed environments, they need to know in advance the list & version of images they have to download before moving to the Trident installation.
It would be beneficial to add a table in the Trident requirement page that lists these images alongside their version.
Describe alternatives you've considered
manually parse the file: https://github.com/NetApp/trident/blob/master/cli/k8s_client/yaml_factory.go
Additional context
Add any other context or screenshots about the feature request here.

We have experienced this first hand with our customers. We need to know the CSI images, so far the only way is digging into the code.

The documentation for the Trident v21.01 release will include a CSI sidecar table. This is included in commit 66414c1.

The documentation for the Trident v21.01 release will include a CSI sidecar table. This is included in commit 66414c1.


Beautify the footer

Styling of the social media icon at the footer can be improved.

Hey @fineanmol . I would love to contribute by beautifying the footer including the social media icons. Kindly assign me this issue.

Hey @fineanmol  I would like to contribute to the task please assign this to me

Hey @fineanmol can you assigned me for this project

Hi @fineanmol ! I'd like to work upon the "Hacktoberfest" title in the footer as it is not properly visible. Please assign this issue to me.

I want to work on this issue. Please assign it to me

@fineanmol  Please assign it to me! I have generated the PR for it. Hope i am doing it the right way .

Hey @fineanmol I would like to contribute to this task can you please assign me this, I also have opened a pull request.


Disabled Link

I wanted to comment on #1082 but it's locked.
Using
  <Link
    onClick={(e) => !canHasLink ? e.preventDefault() : true}
    style={!canHasLink ? {pointerEvents: 'none'} : {}}
  > IDontThinkSo </Link>

still lets the user see the source code and manually enter the target location into address bar.
Not using the changed style even let's the user right-click the link and open the target in new tab.
If I really want to disable the Link, I need to replace the Link with a flat text likeso, (which can, of course, be wrapped in a component...)
{canHasLink // not so sexy
  ? <Link>YouShallPass</Link>
  : 'YouShallNopePass'}

But all those workarounds are not that elegant... Can we have proper Disabled links that mask any evidences of it being a link but still using the same component for the sake of styles (i.e. remove target url from disabled link)?

There is no support for disabled on <a>. As we're trying to match the API of an anchor as closely as possible, doing this is out-of-scope.

Right, of course, that's understandable, but what I had on mind actually is that by using disabled on a <Link/> the rendered <a> would be without a target url, ie. effectively disabled.

even though this issue is 2 and a half years old,
I believe that this is quite a common behavior that most users would like to have.
according to the way that <a> works, I do think that @ackvf 's solution is the best to fit everybody's interests (and support the intended way of disabling an <a>


Remove unused backend methods

What does this PR do?
AxesStandaloneBackend was inheriting a default implementation of get_user() from BaseBackend. Django's force_login() uses the first authentication backend that has a get_user() method for authorization (since django/django#7634), which fails because AxesStandaloneBackend will always be first but can't authorize.
The existing tests didn't notice this, because they never try to do a request after force_login().
By removing the BaseBackend parent class, AxesStandaloneBackend doesn't have a get_user() method anymore, and will be skipped by force_login(). Since AxesStandaloneBackend never authorizes a user, nothing will ever try to call the inexisting get_user().
This is the same solution django-rules uses.
Fixes #998.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[x] Did you write any new necessary tests?

Released as 6.0.4.


NoMethodError in PG adapter after upgrade

Description of the bug
When trying to upgrade opentelemetry-instrumentation-pg from 0.24.0 → 0.25.0 we start seeing an error coming from our tests. It tracks back to this line which was introduced recently in this commit
Share details about your runtime
Operating system details: Linux, Ubuntu 20.04 LTS
RUBY_ENGINE: "ruby"
RUBY_VERSION: "3.2.2"
RUBY_DESCRIPTION: "ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux]"
Share a simplified reproduction if possible
Not sure if it's a repro, but here is the code that triggers the error:
RSpec.configure do |config|
  config.around(type: ->(type) { type != :feature }) do |example|
    Timecop.scale(10) { example.run }
  end
end

And here is the stack trace:
     NoMethodError:
       undefined method `-' for nil:NilClass
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/opentelemetry-instrumentation-pg-0.25.0/lib/opentelemetry/instrumentation/pg/patches/connection.rb:111:in `obfuscate_sql'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/opentelemetry-instrumentation-pg-0.25.0/lib/opentelemetry/instrumentation/pg/patches/connection.rb:72:in `span_attrs'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/opentelemetry-instrumentation-pg-0.25.0/lib/opentelemetry/instrumentation/pg/patches/connection.rb:18:in `block (2 levels) in <module:Connection>'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/postgresql/database_statements.rb:48:in `block (2 levels) in execute'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/dependencies/interlock.rb:41:in `permit_concurrent_loads'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/postgresql/database_statements.rb:47:in `block in execute'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract_adapter.rb:769:in `block in log'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract_adapter.rb:760:in `log'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/postgresql/database_statements.rb:46:in `execute'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/postgresql/referential_integrity.rb:12:in `block in disable_referential_integrity'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract/transaction.rb:319:in `block in within_new_transaction'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activesupport-7.0.5/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract/transaction.rb:317:in `within_new_transaction'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:316:in `transaction'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/postgresql/referential_integrity.rb:11:in `disable_referential_integrity'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:407:in `block in insert_fixtures_set'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:531:in `with_multi_statements'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:406:in `insert_fixtures_set'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/fixtures.rb:630:in `block in insert'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/fixtures.rb:621:in `each'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/fixtures.rb:621:in `insert'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/fixtures.rb:607:in `read_and_insert'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/fixtures.rb:567:in `create_fixtures'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/test_fixtures.rb:275:in `load_fixtures'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/test_fixtures.rb:125:in `setup_fixtures'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-7.0.5/lib/active_record/test_fixtures.rb:10:in `before_setup'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activejob-7.0.5/lib/active_job/test_helper.rb:48:in `before_setup'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-rails-6.0.2/lib/rspec/rails/adapters.rb:74:in `block (2 levels) in <module:MinitestLifecycleAdapter>'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:457:in `instance_exec'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:457:in `instance_exec'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/hooks.rb:390:in `execute_with'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/hooks.rb:628:in `block (2 levels) in run_around_example_hooks_for'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:352:in `call'
     # ./spec/rails_helper.rb:231:in `block (3 levels) in <top (required)>'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/timecop-0.9.6/lib/timecop/timecop.rb:201:in `travel'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/timecop-0.9.6/lib/timecop/timecop.rb:131:in `send_travel'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/timecop-0.9.6/lib/timecop/timecop.rb:75:in `scale'
     # ./spec/rails_helper.rb:231:in `block (2 levels) in <top (required)>'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:457:in `instance_exec'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:457:in `instance_exec'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/hooks.rb:390:in `execute_with'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/hooks.rb:628:in `block (2 levels) in run_around_example_hooks_for'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:352:in `call'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/hooks.rb:629:in `run_around_example_hooks_for'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/hooks.rb:486:in `run'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:468:in `with_around_example_hooks'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:511:in `with_around_and_singleton_context_hooks'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example.rb:259:in `run'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example_group.rb:646:in `block in run_examples'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example_group.rb:642:in `map'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example_group.rb:642:in `run_examples'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/example_group.rb:607:in `run'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:121:in `block (3 levels) in run_specs'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:121:in `map'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:121:in `block (2 levels) in run_specs'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/configuration.rb:2070:in `with_suite_hooks'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:116:in `block in run_specs'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/reporter.rb:74:in `report'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:115:in `run_specs'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:89:in `run'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:71:in `run'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/lib/rspec/core/runner.rb:45:in `invoke'
     # /home/fletch/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/rspec-core-3.12.2/exe/rspec:4:in `<top (required)>'
     # /home/fletch/.asdf/installs/ruby/3.2.2/bin/rspec:25:in `load'
     # /home/fletch/.asdf/installs/ruby/3.2.2/bin/rspec:25:in `<main>'
     # /home/fletch/.asdf/installs/ruby/3.2.2/bin/ruby_executable_hooks:22:in `eval'
     # /home/fletch/.asdf/installs/ruby/3.2.2/bin/ruby_executable_hooks:22:in `<main>'

thanks for reporting this error.
Do you have any details with the SQL statement that it failed on?

cc: @reid-rigo

@arielvalentin based on the stack trace, it looks like it's trying to insert database fixtures.  We'll use these to write some unit tests to cover these cases.

@reid-rigo It looks like the issue is with any DDL statement. I was able to reproduce the problem with  this test:
        it 'truncates DDL statements to the config limit' do
          sql = 'ALTER TABLE "answers" DISABLE TRIGGER ALL'
          obfuscated_sql = 'ALTER TABLE "answers" DISABLE TRIGGER ALL'  # not sure what this should be
          expect do
            client.exec(sql)
          end.must_raise PG::UndefinedTable

          _(span.attributes['db.statement']).must_equal obfuscated_sql
        end

  2) Failure:
OpenTelemetry::Instrumentation::PG::Instrumentation::tracing::when db_statement is obfuscate::with obfuscation_limit#test_0002_truncates DDL statements to the config limit [/workspaces/opentelemetry-ruby-contrib/instrumentation/pg/test/opentelemetry/instrumentation/pg/instrumentation_test.rb:289]:
[PG::UndefinedTable] exception expected, not
Class: <NoMethodError>
Message: <"undefined method `-' for nil:NilClass\n\n              truncated_sql = sql[..sql.index(generated_postgres_regex) - 1]\n                                                                        ^">
---Backtrace---
/workspaces/opentelemetry-ruby-contrib/instrumentation/pg/lib/opentelemetry/instrumentation/pg/patches/connection.rb:111:in `obfuscate_sql'
/workspaces/opentelemetry-ruby-contrib/instrumentation/pg/lib/opentelemetry/instrumentation/pg/patches/connection.rb:72:in `span_attrs'
/workspaces/opentelemetry-ruby-contrib/instrumentation/pg/lib/opentelemetry/instrumentation/pg/patches/connection.rb:18:in `block (2 levels) in <module:Connection>'
/workspaces/opentelemetry-ruby-contrib/instrumentation/pg/test/opentelemetry/instrumentation/pg/instrumentation_test.rb:290:in `block (6 levels) in <top (required)>'
---------------

I did not notice this but it also looks like we do not have any error handling in the PG obfuscation block like with do with other drivers.
https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/cfec2a5389a9abb331d8db83b44031f07e974804/instrumentation/pg/lib/opentelemetry/instrumentation/pg/patches/connection.rb#L107
https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/cfec2a5389a9abb331d8db83b44031f07e974804/instrumentation/trilogy/lib/opentelemetry/instrumentation/trilogy/patches/client.rb#L97
I will take a look at reverting tomorrow if we are unable to track this down.
I suspect that the mysql2 and trilogy instrumentations also have the same problem.


TSD doesn't remove definitions removed from tsd.json

Version affected: 0.6.3
Steps to reproduce:

Create tsd.json, add some definitions
Run tsd reinstall --save
Remove one of the definitions from tsd.json
Run tsd reinstall --save

Result - removed library definitions are still in typings directory and referenced in tsd.d.ts
Expected - removed library .d.ts files are deleted and no longer referenced in tsd.d.ts
Here we also have inconsistency in behaviour - if definition is added into tsd.json, then after tsd reinstall --save it is downloaded into typings and referenced in tsd.d.ts

OK, checking...

Hi!
Now the reinstall command will remove your custom typings only if you use the --clean flag.
tsd reinstall --clean

To install the beta version:
npm install<EMAIL_ADDRESS>
Thanks for reporting this issue.
for more info https://github.com/DefinitelyTyped/tsd/issues/184

NOTE: The --save flag with reinstall command is not needed anymore.


factory reset not working (TZ-215)

hello
I am trying to implement a factory reset, for this I use the function
esp_zb_factory_reset()
but after the restart the device continues to pair with the network coordinator, I also tried to use the function
esp_zb_nvram_erase_at_start(true)
and then call
esp_zb_factory_reset()
, but in both cases it keeps connecting to the network, I assume that the nvram is not being cleared, any suggestions?

Hi @diazmanuel,
Could you please provide information about the network topology of your application? Additionally, if the end device is the only one being erased, it will try to find and join Zigbee network each time it starts up.
To verify your assumption, could you try erasing the flash for the coordinator while keeping the end device unchanged?

If that was happening, the coordinator was letting it in even though the end device wiped the memory, I'm guessing it's because it remembers the mac address of the device. Thanks for the help


updating documents to execute the knex for mysql

Just checked the tables on mysql.
everything is working perfectly.
the documents should be updated that before we executing the knex migration:latest
we need to import all environment settings from .env to the system.
to do that,
set -a
. .env
set +a
those 3 commands, will do export to the environment.

okay, the scripts was changed (not really)
they were already fine on production, and staging was fixed.


all: increase minimum supported version to go1.9

@dfawley

Can you make a new release?
So we can get this change and delete "golang.org/x/net/context" from our generated code. Thanks!


Displayed incorrect topics, producers, subscriptions, and consumers information right after a new tenant creation before namespace creation

Displayed incorrect topics, producers, subscriptions, and consumers information right after a new tenant creation before namespace creation.
Fedex20220608-1 - still have topic count of 1

Verified and it is corrected .


Win+Left Arrow should place window in Left-most column

Environment
Windows build number: Microsoft Windows [Version 10.0.17134.1069]
PowerToys version: 0.11.0
PowerToy module for which you are reporting the bug (if applicable): FancyLayout

Steps to reproduce

Enable "Override Windows Snap hotkeys"
Select a three column layout
Click on any window not currently in a layout.
Click Win+Left Arrow .
Window will jump to the right-most column.

(Same problem reversed with Win + Right Arrow)
Expected behavior
Window should be placed in the left-most layout when the Win+Left key is used, and right-most layout when Win+Right is used.

from #1623 :
@enricogior
The idea that I am proposing would involve win + left snapping a window that is not currently in any zone (just floating), to the lowest available (not occupied by another window) zone number. win + right would snap a window that is not currently in any zone (again, just floating), to the highest available zone number.
And then once a window is in a zone (not floating) win + left and win + right will move the window up and down zone numbers respectively, preferable skipping zone numbers that are already occupied by another window, like you suggested in an earlier comment.
I think this would fix the unpredictable nature of the current win + left and win + right overrides.

Another solution might be allow users to override the numbers assigned to zone in the editor... And then win+left on an unzoned window goes to <zone 1>, and win+right on an unzoned window goes to . The custom zone numbering would help users (mainly RTL language speakers) who want to think they other way around, or people with vertical layouts who want to fill from the bottom up.

#754 Also expresses frustration with the win + arrow overrides

App that is unsnapped

Left arrow snaps to 1 on that monitor
right arrow snaps to N on that monitor

@crutkas I like that idea!

@crutkas I like that idea!

@crutkas any plan to skip/cycle occupied zones when moving a snapped window left or right?

How about Win+Shift+arrow to skip occupied zones. And Win+arrow doesn't
skip?
I'd vote for no cycling personally. But, I don't run one of these crazy
crazy ultra-wide 49" monitors that the kids are using.
On Tue, Apr 28, 2020 at 2:52 PM Jarod Burchill<EMAIL_ADDRESS>wrote:

@crutkas https://github.com/crutkas any plan to skip/cycle occupied
zones when moving a snapped window left or right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/554#issuecomment-620874469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABI2EP3I223TTEPTM2OU4TLRO5FYFANCNFSM4JEYNC6A
.

--
Kind regards,
Nicholas Reid

@njreid Actually, yeah I can see how that may cause problems.
I am honestly just happy to have a win + left and win + right override that is somewhat predictable.
Also Win+Shift+arrow is already used for switching windows to different screens in windows 10.

That is a different feature, honestly, i think you start hitting some really funky edge cases like what if all zones are filled or that monitors zones are filled.

@crutkas Yeah I thought about that and came to a similar conclusion.
Thanks for taking the win + left and win + right override changes into consideration though!

Closing this in favor of https://github.com/microsoft/PowerToys/issues/162 that will support snapping in all directions (using up and down arrow as well).


Reduce CircleCI Run Time

CircleCI takes about 3 minutes, as each job takes about 1 minute (build-lint-test). We should consider improving this. Some ideas include:

Since build, lint, test all start with a docker pull that takes about 45 seconds, we could put them all together into one job. This reduces granularity, but makes things much faster.
Since build, lint, test all start with a docker pull that takes about 45 seconds, we could investigate how CircleCI (or other CI services) can cache the docker image that was pulled somehow

Looked into this. I believe we have to pay money to do this and we don't like to do that. Nice to split up build, lint, test for easier understanding still


Cannot read property 'x' of undefined

Android
Version

react-native-swiper 1.5.10
react-native 0.51.0

Error
Error in test environment

I having same issue when autoplay={true}

I having same issue when autoplay={true}

I also having same issue when autoplay={true}

In real device I am not getting this error. Only getting in simulator.

@showtan001 @ashokkumar88 @iamdurui @lishiwei @andrew 你们最后怎么解决的

I'm getting the error only when calling scrollBy()

@ashokkumar88 @iamdurui @lishiwei @andrew @Tiger-man  @HighSoftWare96  I ended up using Carousel in teast, which is much better than swiper, especially the image loading speed.

for those who met the same problem: https://github.com/leecade/react-native-swiper/issues/582
upgrade to 1.5.14 .


Tcp for NSG needs to be capital T, lowercase cp

Was correct in the end-the-end ansible file; was wrong in the NSG snippet.

@NillsF : Thanks for your contribution to the Azure documentation! The author, @iainfoulds, has been notified to review your proposed change.

Thanks, @NillsF . This looks good to merge.
#sign-off


Log message formatting

Hi, was rumaging around trying to find out where my API quota was going and noticed messages were not having values inserted as perhaps you intended.

Hi @johnno1962 - Thanks for opening this.
Were you getting an error or the wrong data using the current version? There may be something else wrong.
I see the addition of url and headers here. This makes sense and would be a good addition! Thanks for that.
However, moving to the "%" format is not needed for debug().   In fact, pylint will flag this as suboptimal (see W1201 ).  Using lazy logging lets the interpreter skip doing the text formatting until it is needed (if debug level was set). It's a small optimization but it is the reason you will see it in the code.
example test
import logging

log = logging.getLogger(__name__)
logging.basicConfig(level=logging.DEBUG)

url = "url"
headers = "headers"
code = 200
text = "text"
token = "token"

log.debug("GET URL=%s HEADERS=%s: response code=%d text=%s token=%s" % (url, headers, code, text, token))

log.debug("GET URL=%s HEADERS=%s: response code=%d text=%s token=%s", url, headers, code, text, token)

Ha, shows how much Python I know. So, the log function is performing the % expansion on demand which is as it should be. You can disregard this PR or, I've pushed another to commit to include only the URL=%s HEADERS=%s change. Thanks again for this invaluable resource. I've been able to talk to the cloud from Swift but exhausted my quota for this month :D

Thanks @johnno1962 !  It's a good addition.
Thanks to this great community, and contributors like you, the project keeps getting better. ;)


Docdiff should not apply the 'd' hotkey in textareas

Docdiff doesn't apply the d hotkey when typing in <input> fields but should apply similar checks to <textarea> fields.
https://github.com/readthedocs/addons/blob/ff8baf238d4734152dc2373afac0757a4dc7c6f5/src/hotkeys.js#L49-L69
You can see this bug in the notes field on ethicalads.io where the 'd' character cannot be typed.

We're still spotting this https://github.com/kedro-org/kedro/pull/3371#issuecomment-1833810640

@astrojuanlu thanks for commenting here pointing out to a reproducible example. I think the issue you are hitting similar to the one this issue mentions and it was solved in v0.9.0 by this PR of the addons which I released the past Tuesday but I had to revert that deploy because it broke other stuffs 😅  (see https://github.com/readthedocs/addons/issues/207)
I double checked the code and it seems it's correct: https://github.com/readthedocs/addons/blob/main/src/hotkeys.js#L58-L63
Once I fix the 0.9.0, I will do another one that once deployed it should solve the issue you are experimenting. I'm targeting this release to next Tuesday. If you want, I can disable the "hotkeys addons" in your project now as an immediate workaround. Let me know.
I'll keep you posted otherwise 👍🏼

Thanks! cc @rashidakanchwala

I just merged #208 which solves the issue with the previous release and I've deployed 0.9.1 with the fix for this. I just tested your project at https://rashida-test-kedro.readthedocs.io/en/latest/ and I was able to type the d letter without problem when performing a search 😄
I'd appreciate any other feedback you may have in the future 🙏🏼


No Audio Device Detected

OS:
Ubuntu 16.04.1
Issue Descriptions:
It is not possible to get to the initial screen of Google-Play-Music-Desktop-Player. I can open the settings dialog via the tray-icon and it seems it may lie on the fact, that no audio device is listed. The tray-icon option for audio devices remains at "loading devices".

Audio is working as expected in all other applications, including Chrome and Firefox.
Steps to Reproduce:
Opening the application on my system is enough to reproduce the error.
Let me know if there is any log-information I can provide to help with the problem hunt.

The audio device list is only fetched when the main window of GPMDP is launched.  Whatever is causing the issue it is not the audio device list.
Can you please provide your error log / debug zip file.

I found the issue. A new firewall rule was preventing the connection to the server.


Spacer shorthand enhancement

Summary
Allowed functionality to terra-spacer to be able to support shorthand property values and map them into individual directional rules.
Additional Details
Closes #1314
Thanks for contributing to Terra.
@cerner/terra

This is pretty slick 👌👌👌
At a first glance pass, I'm liking it a lot and I've been wanting the shorthand ability since the Spacer was released. I'll go through it more thoroughly later today 👍

@JakeLaCombe , @StephenEsser , @dev-cprice , @emilyrohrbough : can you finish reviewing this when you get the chance?

@JakeLaCombe @StephenEsser @dev-cprice @emilyrohrbough, bump

Do we want to add wdio tests to ensure this renders as expected? @bjankord

@emilyrohrbough I'm fine with the jest test coverage for this.


VCD of FST waveform dump

Perhaps am i wrong, but it seems that VCD or FST waveform dump doesnt't work when dynamic scheduler is used.
I got an empty VCD with only timestamps but no signal change.
main.cpp:
#include <verilated.h>
#include <Vtop.h>
#include <unistd.h>
#include "verilated_vcd_c.h"

vluint64_t main_time = 0;
double sc_time_stamp() { return main_time; }

int main(int argc, char *argv[]) {
    Verilated::traceEverOn(true);
	Verilated::commandArgs(argc, argv);
    VerilatedVcdC* tfp = new VerilatedVcdC;
	Vtop *top = new Vtop;
    top->trace(tfp, 99);
    tfp->open("dump.vcd");
	while (!Verilated::gotFinish()) {
		top->eval();
		main_time = top->timeSlotsEarliestTime();
        tfp->dump(main_time);
	}
    tfp->close();
	top->final();
	delete top;
	return 0;
}

dump.vcd:
$version Generated by VerilatedVcd $end
$date Thu Sep 16 12:28:34 2021
 $end
$timescale 1s $end

 $scope module TOP $end
  $scope module t $end
   $var wire  1 # clk $end
   $var wire 32 $ cyc [31:0] $end
  $upscope $end
 $upscope $end
$enddefinitions $end

#1
0#
b00000000000000000000000000000000 $
#2
#3
#4
#5
#6
#7
#8
#9
#10
#11
#12
#13

That is correct, thanks for reporting this bug. It's on our TODO list

This should be resolved in the new coroutine-based version. Note that it now requires GCC 10 (or Clang with coroutine TS support). Please reopen this issue if there are still any problems with waveforms.


Typo in manual (zowe 1.19)

On page 337 of the zowe 1.19.0 doc it says:
Note: When using JCEFACFKS as the keystore type, ensure that you define the class to handle the RACF keyring
using the -D options to specify the java.protocol.handler.pkgs property:
Should it not be:
Note: When using JCERACFKS as the keystore type, ensure that you define the class to handle the RACF keyring
using the -D options to specify the java.protocol.handler.pkgs property:

Can be closed, merged with #1605


cl.user_id_from_username(username) ERROR 500

Compensate with donations ($15 and more) for the time I spent to fix problems or send me your Pull Request with fixes

Tron TRX/USDT: TLprxuzHjXPkHYa7ZfTTt165p7Fphwy1Ee
Bitcoin: bc1qmp7538hktvg2gx994hrpkmsmyjc03q29awe9ra
Ethereum: 0x0E674815d513d4a00F6a7Cd4A990807aB97cC70D
Dogecoin: DSEXzMBYhBTwhNqzPGxVWFsTqVsTCeDejo

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Provide a piece of code to reproduce the problem.
Traceback
Show your full traceback so that it is clear where exactly the error occurred.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Ubuntu 21.04]
Python version [e.g. 3.8.3]
instagrapi version [e.g. 1.9.3, not "latest"]
moveipy version if used
imagemagick version if used

Additional context
Add any other context about the problem here.

Cannot reproduce
>>> cl.user_id_from_username("instagram")
'25025320'


Unable to load script from assets 'index.android.bundle'.make sure you bundle is packaged correctly.....

Environment:
OS: macOS Sierra 10.12.6
Node: 8.3.0
Yarn: 0.27.5
npm: 5.5.1
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: ^16.3.0-alpha.0 => 16.3.1
react-native: 0.55.0 => 0.55.0
Steps to Reproduce
1:react-native init Test
2:cd Test
3:react-native run-andorid
use android virtual genymotion google nexus 6p-7.1.0
Expected Behavior
run normal like ios is ok.
Actual Behavior
if release is ok .
can't load script and can't debug start chrome.
Unable to load script from assets 'index.android.bundle'.make sure you bundle is packaged correctly.....

Why is this issue closed? I am sure this issue is occurring after 0.54.** to 0.55.0 upgrade.
Android Logcat:- java.lang.RuntimeException: Unable to load script from assets 'index.android.bundle'. Make sure your bundle is packaged correctly or you're running a packager server.
after reversing the adb ports, started working in debug mode, but crashing with above error in production.

I run "sudo npm start run" and show

it's about watchman?
1:npm r -g watchman
2:brew uninstall watchman
3:brew link pcre
4:brew install --HEAD watchman
but no work still bug.

Hi guys. I have the same issue. Here's my logcat output:

For IOS:
In a terminal: cd ios
Remove the build folder with: rm -r build
Run again: react-native run-ios
Alternatively, you could open Finder, navigate to YOUR_PROJECT/ios and delete the build folder.
Then run again: react-native run-ios
For ANDROID:
In a terminal: cd android/app
Remove the build folder with: rm -r build
Run again: react-native run-android
Alternatively, you could open Finder, navigate to YOUR_PROJECT/android/app and delete the build folder.
Then run again: react-native run-android

I have tried ALL the answers here, but none work at all. Including removing build folder, clearing watchman, running as sudo, etc.

@darkmantle me neither :(

same problem

same problem here.....

same problem here...

I have resolved doing this commands:
`// create new project
react-native init awesomeproject
// use react native 0.55.4
npm remove --save react-native
npm i --save<EMAIL_ADDRESS>npm remove babel-preset-react-native
npm i --save<EMAIL_ADDRESS>// create folder assets in android\app\src\mainoid
mkdir android\app\src\main\assets
// create the "index.android.bundle" file
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android\app\src\main\assets\index.android.bundle --assets-dest android\app\src\main\res
// run the app on android device
react-native run-android`
Hope to help someone ;)

If you work on the Windows, you should run react-native bundle --platform android --dev false --entry-file index.js --bundle-output android\app\src\main\assets\index.android.bundle --assets-dest android\app\src\main\res  with cmd run as administrator(İmportant). Thus the problem was fixed :)

this trick "creating assets folder etc"  sucks , neither I can not use debugger nor hot reloading ..

thnx  ovannigenna, finally i got evaded from this thing. thnx buddy.

If you don't and to keep generating the bundle through command line all the time, you could use the Debbuger mode:
http://facebook.github.io/react-native/docs/debugging#debugging-on-a-device-with-chrome-developer-tools
This would make the Chrome to run the JS:
https://facebook.github.io/react-native/docs/javascript-environment
So a new bundle will created so the browser can run, and the app will use that bundle.

It seems that the bundle name is changed from index.bundle to index.android.bundle not sure, best you can do is

Remove the ios and android folders and react-native eject to recreate those folders.
Creating android\app\src\main\assets folder.

There is some relation between, name in package.json, app.json, application Id in build.gradle file, Activity class, and Application class package name, method getMainComponentName()
in MainApplication.java class which returns the component name. Check the names are correct or not. I am not clear how those things work together if anyone can guide me about this, but by making sure the app name in app.json and getMainComponentName() are same, solved my problem.
Not perfect solution for this issue. lots of things are unclear.
RN people need to use the latest versions of android gradle libs, and some info about if not already there, how it generates android project on react-native init, it will be helpful.

If you work on the Windows, you should run react-native bundle --platform android --dev false --entry-file index.js --bundle-output android\app\src\main\assets\index.android.bundle --assets-dest android\app\src\main\res with cmd run as administrator(İmportant). Thus the problem was fixed :)

I've tried this countless times but i keep getting this type of error:
Error: Unable to resolve module @babel/runtime/helpers/interopRequireDefaultfromC:\Users\Albert\reactnative apps\test2\index.js: Module @babel/runtime/helpers/interopRequireDefault` does not exist in the Haste module map
This might be related to https://github.com/facebook/react-native/issues/4968
To resolve try the following:

Clear watchman watches: watchman watch-del-all.
Delete the node_modules folder: rm -rf node_modules && npm install.
Reset Metro Bundler cache: rm -rf /tmp/metro-bundler-cache-* or npm start -- --reset-cache.
Remove haste cache: rm -rf /tmp/haste-map-react-native-packager-*.
at ModuleResolver.resolveDependency (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:209:1301)
at ResolutionRequest.resolveDependency (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:83:16)
at DependencyGraph.resolveDependency (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\node-haste\DependencyGraph.js:238:485)
at Object.resolve (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\lib\transformHelpers.js:180:25)
at dependencies.map.result (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:311:29)
at Array.map ()
at resolveDependencies (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:307:16)
at C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:164:33
at Generator.next ()
at step (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:266:307)`

If you work on the Windows, you should run react-native bundle --platform android --dev false --entry-file index.js --bundle-output android\app\src\main\assets\index.android.bundle --assets-dest android\app\src\main\res with cmd run as administrator(İmportant). Thus the problem was fixed :)

I've tried this countless times but i keep getting this type of error:
Error: Unable to resolve module@babel/runtime/helpers/interopRequireDefaultfromC:\Users\Albert\reactnative apps\test2\index.js: Module@babel/runtime/helpers/interopRequireDefault` does not exist in the Haste module map
This might be related to #4968
To resolve try the following:

Clear watchman watches: watchman watch-del-all.
Delete the node_modules folder: rm -rf node_modules && npm install.
Reset Metro Bundler cache: rm -rf /tmp/metro-bundler-cache-* or npm start -- --reset-cache.
Remove haste cache: rm -rf /tmp/haste-map-react-native-packager-*.
at ModuleResolver.resolveDependency (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:209:1301)
at ResolutionRequest.resolveDependency (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:83:16)
at DependencyGraph.resolveDependency (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\node-haste\DependencyGraph.js:238:485)
at Object.resolve (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\lib\transformHelpers.js:180:25)
at dependencies.map.result (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:311:29)
at Array.map ()
at resolveDependencies (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:307:16)
at C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:164:33
at Generator.next ()
at step (C:\Users\Albert\reactnative apps\test2\node_modules\metro\src\DeltaBundler\traverseDependencies.js:266:307)`

it works, try :
npm add @babel/runtime

My project runs in debug mode, but the release apk crashes. The logs have the same error -> Unable to load script from assets 'index.android.bundle'. What should I do to fix this?
The apk was generating fine, until today. I don't see how I caused it.

@km16  i fixed this.
i use android studio ,not eclipse. assets dir in android studio is android/app/assets,however,  in eclipse is android/app/src/main/assets . So move index.android.bundle index.android.bundle.meta from  android/app/src/main/assets to android/app/assets.  it works for me

I have a problem on creating a release build, since today its not building correctly anymore (I dont know why):

Task :app:bundleReleaseJsAndAssets successfully creates the index.android.bundle

PATH..../android/app/build/intermediates/assets/release/index.android.bundle
bundle: Done writing bundle output
bundle: Copying 196 asset files
bundle: Done copying assets

but when I install the .apk release file, it is unable to load the bundle file. Because its not in the apk. also the assets (images) are not in the .apk.
How can this happen?

I spent hours reading every single issue remotely related to the error to figure out how to fix this problem.  The issue was useClearText is disabled by default on Android > 9.0.
https://stackoverflow.com/a/53326616/1713216

I have spent hours trying to figure this issue out.
Accessing the development server worked locally and in the emulator's browser. The only thing that did not work was accessing the development server in the app.

Starting with Android 9.0 (API level 28), cleartext support is disabled by default.

AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest ...>
    <uses-permission android:name="android.permission.INTERNET" />
    <application
        ...
        android:usesCleartextTraffic="true"
        ...>
        ...
    </application>
</manifest>

See for more info: https://stackoverflow.com/a/50834600/1713216

Thank you!

@phips28 , @km16 did you guys get any solution?
My app works fine on physical device when debugging over USB but the release apk crashes.

@akshaysargar I updated to the latest RN 0.57 with the new metro bundler. then it worked

@akshaysargar  I faced the same problem. Signed app doesn't work on device.  I spent a whole day but  there is no success yet. I will write when find the soulution.

I caused this to myself by upgrading the gradle to com.android.tools.build:gradle:3.2.1. And that was because of trying to integrate firebase. Solved by upgrading RN to the latest version.

I also lost a lot of time trying to debug the reason. Everything worked perfectly when running with the packager server running, but the application froze on start when running the production build.
In the end I deleted and then re-generated the index.android.bundle file:
$ rm android/app/src/main/assets/index.android.bundle
$ react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res

And then did a clean Gradle build:
$ cd ./android
$ ./gradlew clean && ./gradlew assembleRelease

@mtkopone @phips28 thank you. Problem was solved after updating rn to 0.57.5
@akshaysargar have you tried to update rn?

Yes updated RN to 0.57.5 and finally it worked !!!
This issue took me few days to solve it. I was working on RN 0.55.4 initially but was cautiously updating  the RN as I had to take care of lot of dependencies. So just to inform, this issue that we are solving occurs on versions 0.56.0, 0.57.0 but finally I updated to the latest version 0.57.5 and that worked. Thanks @phips28, @mtkopone, @rgaraev

i meet same error with RN 0.57 at log cat of Android studio? i tried all way above but not solution. anyone same me?

i meet same error with RN 0.57 at log cat of Android studio? i tried all way above but not solution. anyone same me?

@phonganhhung9xtb,  What version of react native do you have exactly? I updated to 0.57.7 and the problem was solved.

I updated to v0.58.3 I also have same issue now...

Simple as that: https://medium.com/@adityasingh_32512/solved-unable-to-load-script-from-assets-index-android-bundle-bdc5e3a3d5ff
Saved my life!

Saved lots of my hours too, thanks

adb reverse tcp:8081 tcp:8081

it works for me, thanks.