[GHSA-f7gc-6hcj-wc42] Malicious Package in path-to-regxep

Updates

Affected products

Comments
Package already not in npmjs.com,  this advisory should be removed.

Hey @seng1e, any reason you want this advisory removed? We tend to keep malware takedown advisories live despite the package being pulled as well.

👋 This pull request has been marked as stale because it has been open with no activity.  If you do nothing this pull request will be closed eventually by the stale bot. Please see CONTRIBUTING.md for more policy details.


Should there be type validation or is everything a string

For parameters there is currently a type option for parameter validation. This has many implication on how this should be validated, what types are supported and can this be influenced by the user? Currently there could be support for: string, integer, float, number (combination of integer and float). But then what about more specific types like "date", "url" and n-more types. The alternative could be that every parameter is a string for now. This will result in less issues and less thinking for the user.

For now the only types are: string and and array of options as strings.

The type boolean was added naturally on implementing the script interpreter.


normalize_path breaks relative python interpreters

-p/--python with relative paths is broken due to using normalize_path, which changes the path rather than just normalizing it.
$ cargo run -q -- venv -p ../cpython/python .venv3.13 -vv
 uv_interpreter::find_python::find_requested_python request=../cpython/python
      0.000439s   0ms DEBUG uv_interpreter::find_python Starting interpreter discovery for Python @ `../cpython/python`
[crates/uv-interpreter/src/find_python.rs:55:46] request = "../cpython/python"
[crates/uv-interpreter/src/find_python.rs:55:26] normalize_path(dbg!(request)) = "cpython/python"
  × failed to canonicalize path `cpython/python`
  ╰─▶ No such file or directory (os error 2)

It looks like normalize_path assumes the argument path is absolute. I'll fix and document.


Add context to code components

The code component overrides were missing the tracker context, this fixes the issue.

Hello @zsherman! After a refactoring, CodeComponent lives only in createRenderer.js. Would you mind resolving the conflicts?
I think it's also worth to add some test for this change, to make sure we don't break it in future


Fix a bug where BootstrapCloudToolsForPowershell is not found by Cloud Tools For PowerShell app

The issue is that the "Cloud Tools For PowerShell" application is looking for "BootstrapCloudToolsForPowerShell.ps1" at the wrong place. Also, the bootstrap script itself is importing the module with the wrong directory.

This change is

Thanks!


Could not build Objective-C module 'UXMPDFKit'

Created a single view application
added 'UXMPDFKit' lib using the cocoapod
imported lib in viewcontroller.swift  file using import UXMPDFKit
It gives an error like Could not build Objective-C module 'UXMPDFKit' when I try to run the app

iOS Version: iOS 12
Xcode Version: 10.1 (10B61)
Swift Version: 4.2

+
is it not supported to swift 4.2 or I am missing something here? because just after installing pod I try to run the app and it throws many errors shown in the screenshot:

Can anyone help, please?

I fixed the issue by dragging lib classes to my project, and manually creating connection between lib and project


ORC-759: StructBatchReader should always skip processing on the rootReader

What changes were proposed in this pull request?
StructBatchReader assumes rootReader has no nulls and skips rootReader processing in the following methods:

seek
skip
startStripe

This behavior will be consistent with the behavior of nextBatch which already makes this assumption.
Why are the changes needed?
Make the behavior consistent on all the methods.
How was this patch tested?
Regression test, none of the existing tests have failed.

Thanks @pavibhai ! This is now merged!

Thank you, @pavibhai and @pgaref .


Don't attempt to upload zero files

Don't attempt to upload files if there aren't any files to upload.
Fixes #106.

Ideally if uploadFiles returns a promise, then it should always return a promise. Many developers may be relying on the promise with .then.
Could we instead reject the promise immediately if there are zero files?
Another solution is to disable the button if there are no valid files, which is something you can add on your end.

Another solution is to disable the button if there are no valid files, which is something you can add on your end.

Yes, but not when using uploadImmediately.

Could we instead reject the promise immediately if there are zero files?

Hm, when using uploadImmediately, uploadFiles is triggered with a send call internally. How can user code handle the resulting promise rejection?

In the case of uploadImmediately, I think a simple check at this point on addedModels.length would be sufficient.
Agreed?

That won't work if the file is invalid.
How about checking if there are any valid files before calling uploadFiles?

:+1: https://github.com/Wildhoney/EmberDroplet/blob/master/components/Droplet.js#L639-L641
Please try with v3.0.0.

That seemed to work!
Thanks, @Wildhoney.


add vendor directory

resolve https://github.com/knocknote/vitess-sqlparser/issues/7
Already fixed dependencies in this repository.
To install by go get (-u) github.com/knocknote/vitess-sqlparser , add vendor directory generated by glide

LGTM:+1:


[BUG] Fail to run the example in/DeepSpeedExamples

I follow the example here: https://github.com/microsoft/DeepSpeedExamples/tree/master/applications/DeepSpeed-Chat#-quick-start-
But then I got error to train the 1.3B model:
python3 train.py --actor-model facebook/opt-1.3b --reward-model facebook/opt-350m --deployment-type single_node

File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 1509, in _jit_compile
    _write_ninja_file_and_build_library(
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 1624, in _write_ninja_file_and_build_library
    _run_ninja_build(
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py", line 1909, in _run_ninja_build
    raise RuntimeError(message) from e
RuntimeError: Error building extension 'fused_adam'
[2023-04-14 08:07:54,793] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 4342
[2023-04-14 08:07:56,313] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 4343
[2023-04-14 08:07:56,314] [ERROR] [launch.py:434:sigkill_handler] ['/usr/bin/python3', '-u', 'main.py', '--local_rank=1', '--data_path', 'Dahoas/rm-static', 'Dahoas/full-hh-rlhf', 'Dahoas/synthetic-instruct-gptj-pairwise', 'yitingxie/rlhf-reward-datasets', 'openai/webgpt_comparisons', 'stanfordnlp/SHP', '--data_split', '2,4,4', '--model_name_or_path', 'facebook/opt-1.3b', '--per_device_train_batch_size', '8', '--per_device_eval_batch_size', '8', '--max_seq_len', '512', '--learning_rate', '9.65e-6', '--weight_decay', '0.1', '--num_train_epochs', '2', '--gradient_accumulation_steps', '1', '--lr_scheduler_type', 'cosine', '--num_warmup_steps', '0', '--seed', '1234', '--zero_stage', '2', '--deepspeed', '--output_dir', '/root/DeepSpeedExamples/applications/DeepSpeed-Chat/output/actor-models/1.3b'] exits with return code = 1

So the error here is: RuntimeError: Error building extension 'fused_adam'
I can not resolve this.
Please help.
PS: I got two GPU with 16G Mem each. I think the resource is OK.

@wang700 could you please share the output of ds_report? Thanks

@wang700 could you please share the output of ds_report? Thanks
I have encountered the same problem on Windows WSL Ubuntu 22.04.
ds_report

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
[WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
[WARNING]  async_io: please install the libaio-dev package with apt
[WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
[WARNING]  sparse_attn requires a torch version >= 1.5 but detected 2.0
[WARNING]  using untested triton version (2.0.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
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 ............... ['/home/ubuntu/anaconda3/envs/my_gpt/lib/python3.10/site-packages/torch']
torch version .................... 2.0.0+cu117
deepspeed install path ........... ['/home/ubuntu/anaconda3/envs/my_gpt/lib/python3.10/site-packages/deepspeed']
deepspeed info ................... 0.9.0, unknown, unknown
torch cuda version ............... 11.7
torch hip version ................ None
nvcc version ..................... 11.5
deepspeed wheel compiled w. ...... torch 1.12, cuda 11.3

OK. sure.

Resolved by installing official CUDA Toolkit .  I install another version manually previously.

Hello! Thanks for the info. I am having similar issues - would you mind shedding some light?

{
 "date": "2023-06-16T19:20:02-0600",
 "dirty": false,
 "error": null,
 "full-revisionid": "db4f43
/users/lisali12/.conda/envs/XXX/lib/python3.10/site-packages/pydantic/_internal/_config.py:261: UserWarning: Valid config keys have changed in V2:
* 'allow_population_by_field_name' has been renamed to 'populate_by_name'
* 'validate_all' has been renamed to 'validate_default'
  warnings.warn(message, UserWarning)
/users/lisali12/.conda/envs/XXX/lib/python3.10/site-packages/pydantic/_internal/_fields.py:126: UserWarning: Field "model_persistence_threshold" has conflict with protected namespace "model_".

You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
  warnings.warn(
/users/lisali12/.conda/envs/XXX/lib/python3.10/site-packages/pydantic/_internal/_config.py:261: UserWarning: Valid config keys have changed in V2:
* 'validate_all' has been renamed to 'validate_default'
  warnings.warn(message, UserWarning)

{
 "date": "2023-02-14T19:25:14-0800",
 "dirty": false,
 "error": null,
 "full-revisionid": "43a780
--------------------------------------------------
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

{
 "date": "2022-11-05T08:23:29+0100",
 "dirty": false,
 "error": null,
 "full-revisionid": "c5a6e1
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
 [WARNING]  using untested triton version (2.0.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
utils .................. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/users/lisali12/.conda/envs/XXX/lib/python3.10/site-packages/torch']
torch version .................... 1.13.1+cu117
torch cuda version ............... 11.7
torch hip version ................ None
nvcc version ..................... 11.2
deepspeed install path ........... ['/users/lisali12/.conda/envs/XXX/lib/python3.10/site-packages/deepspeed']
deepspeed info ................... 0.7.4+fe5ddd3, fe5ddd3, main
deepspeed wheel compiled w. ...... torch 2.0, cuda 11.7


Is load_discussions.py redundant?

I can't figure out what's the purpose of this file

It might relate to this feature?

Yes! I implemented the discussion feature a while ago. Discussions are kept
as markers with Disqus id. The script gets a list of ids and adds the
discussion markers.
On Tue, Sep 12, 2017, 21:10 Simona Holstein<EMAIL_ADDRESS>wrote:

It might relate to this feature?
[image: image]
https://user-images.githubusercontent.com/16196934/30341455-bb25c11a-97fe-11e7-9e00-754e47cdd223.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hasadna/anyway/issues/730#issuecomment-328936503, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQEw4sZRCanFv4F-SgbkK4vRLpf9dhNks5shskMgaJpZM4PVCpA
.


Add Nx

See the details in #8, that explains all the steps followed here. There was one additional change - when I was running the application using the new Nx workspace commands nx server uct-locator-back-end (see README.md for more details), I was looking at the passport.js configuration and noticed that an import path could be simplified, so I did so.
Closes #8

This all looks good to me, works better than the old setup for sure! Did we want to merge this into develop first though?

Updated the base branch!


How create form

I want put the form but I saw that don't have the archives call form.html.twig could me help, plz?

read this: https://learn.getgrav.org/forms/forms
You just need to create a form.md page and define the form properly.  The form should render fine in Quark.


AVS to On-premises Visual in this article is mis-represented

After consulting with one of our Networking GBBs, the AVS ER circuit should be connected to the ER GW in (existing) Hub VNet, same ER GW as where the on-premises ER circuit is connected.  Non-transitive by default, until the ER Global Reach feature is enabled to allow route exchange.  With both ER circuits connected to the ER Gateway with Global Reach feature, AVS and on-premises can communicate.  Please update the Visual embedded in this article.

@gamcmaho : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#reassign: @rvandenbedem I need help to make updates to the diagram in article Peer on-premises to private cloud per comments from gamchmaho above. I don't have access to original Visio diagrams to make those types of changes myself.

@PRMerger5 this PR should not be merged. This it isn't an update to article, rather customer feedback added into the article.

@rvandenbedem are you able to help with updating the diagram per customer feedback?


SEC: Support SELinux

It'd be great to have optional support for SELinux: https://rancher.com/docs/k3s/latest/en/advanced/#experimental-selinux-support
From  https://github.com/rancher/k3s/issues/2473#issuecomment-723346270 :
k3s-ansible (an excellent reference for the necessary setup steps) could be updated here as well: https://github.com/rancher/k3s-ansible/blob/721c3487027e42d30c60eb206e0fb5abfddd094f/roles/prereq/tasks/main.yml#L2-L5
OTOH something like this:
- name: Set SELinux to disabled state
  selinux:
    state: disabled
  when:
    - not (k3s_disable_selinux is defined and not k3s_disable_selinux) or k3s_disable_selinux == False
    - ansible_distribution in ['CentOS', 'Red Hat Enterprise Linux']

With this added to https://github.com/rancher/k3s-ansible/blob/master/inventory/sample/group_vars/all.yml :
k3s_disable_selinux: False

SELinux support is now automatically handled by using the K3s install script, added in https://github.com/k3s-io/k3s-ansible/pull/228

Thanks!
On Thu, Nov 9, 2023, 3:53 PM Derek Nola @.***> wrote:

Closed #98 https://github.com/k3s-io/k3s-ansible/issues/98 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/k3s-io/k3s-ansible/issues/98#event-10917916040, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMNSZWXXN42W4HKQ5OYW3YDU7DTAVCNFSM4TNJSS2KU5DIOJSWCZC7NNSXTWQAEJEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW4OZRGA4TCNZZGE3DANBQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


EthereumChainAdapter - Tests

Tests should be added for all methods of EthereumChainAdapter, which is currently untested.

FYI @0xean this is current version of tests: https://github.com/shapeshift/lib/blob/main/packages/chain-adapters/src/ethereum/EthereumChainAdapter.test.ts. And the current run of tests for the module:
 PASS  packages/chain-adapters/src/ethereum/EthereumChainAdapter.test.ts
  EthereumChainAdapter
    getBalance
      ✓ is unimplemented (7 ms)
    getFeeData
      ✓ should return current ETH network fees (14 ms)

--------------------------|---------|----------|---------|---------|----------------------------------
File                      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------------------|---------|----------|---------|---------|----------------------------------
All files                 |   33.08 |    17.43 |   17.39 |   32.69 |
 error                    |   44.44 |        0 |       0 |   44.44 |
  ErrorHandler.ts         |   44.44 |        0 |       0 |   44.44 | 6-13
 ethereum                 |   21.32 |    12.71 |   14.81 |   20.89 |
  EthereumChainAdapter.ts |   21.32 |    12.71 |   14.81 |   20.89 | 19-23,30-177,184,190-197,255-312
 utils                    |   45.16 |    26.02 |   22.22 |   45.29 |
  bignumber.ts            |      75 |       50 |   33.33 |   81.81 | 11-12
  bip44.ts                |   24.24 |        0 |       0 |      25 | 5-12,16-23,27-34
  index.ts                |   47.72 |    34.37 |   28.57 |   46.15 | 6-7,20-26,30-36,40-44
  utxoUtils.ts            |   51.42 |    15.38 |      25 |   51.42 | 13-23,35-64,128-135
--------------------------|---------|----------|---------|---------|----------------------------------
Test Suites: 1 passed, 1 total
Tests:       2 passed, 2 total
Snapshots:   0 total
Time:        3.118 s, estimated 4 s
Ran all test suites matching /EthereumChainAdapter/i.

Note: I don't think signAndBroadcastTransaction can be tested in a reliable way, since under the hood it simply calls https://docs.metamask.io/guide/ethereum-provider.html#ethereum-request-args.

EthereumChainAdapter with tests from all branches added, including the 3 unmerged PRs:
All files / ethereum EthereumChainAdapter.ts
74.63% Statements 103/138
61.66% Branches 74/120
62.96% Functions 17/27
75% Lines 102/136

BitcoinChainAdapter tests, for reference:
All files / bitcoin BitcoinChainAdapter.ts
67.3% Statements 105/156
60 % Branches 57/95
64% Functions 16/25
68.42% Lines 104/152

Closed in the final #334 PR.


Add support for Alpine 3.19

Alpine 3.19 was released on 2023-12-07.
I believe we need the RID ASAP due to https://github.com/PowerShell/PowerShell/issues/20945 which is blocking PowerShell support in https://github.com/dotnet/dotnet-docker/pull/5065.
Similar issue for Alpine 3.18: https://github.com/dotnet/core/issues/8470

@leecow @rbhanda can you check?

We no longer provide support for OS-specific RIDs, only portable RIDs. The portable RID should provide equivalent functionality.
That said, I'm not sure the RID is the fundamental problem here. Powershell ran into a problem with a .NET 8 breaking change which they needed to adapt to in their code: https://github.com/PowerShell/PowerShell/issues/20685. This may be the same problem.


⚠ GitLab Server has degraded performance

In 113f67e, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 9404 ms

Resolved: GitLab Server performance has improved in 3de153f.


chore(master): release 1.14.20

:robot: I have created a release beep boop
1.14.20 (2023-09-04)
Bug Fixes

deps: update dependency pnpm to v8.7.3 (eed345f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/docker-node/releases/tag/v1.14.20 :sunflower:


In the case of Web mode and users greater than 1, the chart still adds data after using the quit () method

Describe the bug

When the requested data is limited, I will actively call quit () to exit after the number of requests is completed.
However, in the web mode, and when the user setting is greater than 1,  the chart still adds data after using the quit () method
class Task(TaskSet):

    @task(1)
    def check(self):
        line = self.user.queueData.get()
        if line is not None:
            with self.client.post("/Issue/", headers={"Authorization": Authorization}, catch_response=True,
                                  verify=False,
                                  name="check") as response:
                if response.status_code == 200:
                    response.success()
                else:
                    response.failure(f'Failed! {response.text}')
        else:
            logging.info("The queue data has been used up～～～")
            self.user.environment.runner.quit()

class websitUser(HttpUser):
    tasks = [Task]
    host = "http://<IP_ADDRESS>:8080/"
    wait_time = between(0, 0)
    queueData = queue.Queue()
    file_handle = open('mock_list', mode='r')
    for line in file_handle:
        queueData.put(line)
    queueData.put(None)

shown in the image above，quit () has cleared the user, but the chart is still adding data statistics. This will cause the abscissa of the chart to be inconsistent with the actual test time
Expected behavior

Stop statistics after using quit()
Actual behavior

the chart still adds data after using the quit () method
Steps to reproduce

1、In the task method, the quit () method is called when the number of requests reaches
2、Start the locust service using web mode
3、The number of users is set to be greater than 1
Environment

OS:mac 10.15.7
Python version:3.7.0
Locust version: 2.5.0
Locust command line that you ran:locust -f link_test.py --stop-timeout 10
Locust file contents (anonymized if necessary)shown in the image above

Start by updating to latest version (2.8.2)

We have tried versions 1.4.1, 2.5.0 and 2.8.2. All three versions have this problem

quit() is really ment to shut down locust (not just stop the test run). I have only really used this in —headless. Sorry, but I wont have time to dig into this.

I tested it. The reason for not stopping is that the state has always been "cleanup" and has not been normally changed to "stopped". I tried to annotate the line "self. Stop_users (self. User_classes_count)", and the state changed normally after annotation. Then I looked at the "stop_users" method. It seems to be caused by the blocking of "async_calls_to_stop. Join()",

@mboutet I think you were the last person to touch that code...


Fix some errors

While working with this lib I encounter some problems that I want to fix in this pr

Closes #32


ES2015 Modules

It would be nice if import-js could be configured to produce import syntax used by ES2015 modules.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import

:+1: I saw React-router and others are using that style of importing. Should (?) be simple I think.

Here are some style guidelines used by the very popular Airbnb JS style guide that might be somewhat useful: https://github.com/airbnb/javascript#modules

https://github.com/trotzig/import-js/commit/52d3e5851a509b3dff6102852d6cb3ac204dc8a0

Closed through above referenced commit.


Is it possible to extract broken links from the crawl?

Currently it seems like the crawler only returns working links, but I'm interested in all links on the page, especially the ones that do not work.

All links are supported, the page stores the status code of the request.

Should they show up in e.g. the get_links results here https://github.com/spider-rs/spider/blob/main/examples/example.rs?
On my test run only valid links were being returned.

Can you share a minimal example or the url please? The link should be included in the results.

The crawler stores the link before requesting the page. All links are stored. If you need all of the resources use the "full_resource" configuration.

Ah, my bad. Of course the domain in those broken links wasn't matching the origin.

Ah, my bad. Of course the domain in those broken links wasn't matching the origin.

No worries, you can use website.set_external to merge domains as one.


Force yaxis to alway draw '0' even with negative data

Description
I have faced an issue while working on my project. So there are charts that do not show '0' on yaxis.
I tried forceNiceScalse: true, also tried playing with min-max and they didn`t help.
The only thing that worked for me is tickAmount, yet in my situation I see no way to calculate it for 5000 dynamic charts, so that each chart would have its own tickAmount.
Steps to Reproduce

open this codepen https://codepen.io/A_n_d_r_i_i/pen/ZEZWjBj
Try to make the chart show '0'

Expected Behavior
Chart has to draw '0' on yaxis
Actual Behavior
Chart does not draw '0' on yaxis
Screenshots

Reproduction Link
codepen https://codepen.io/A_n_d_r_i_i/pen/ZEZWjBj

@junedchhipa I'd be happy to update the documentation if you'd like. Just let me know how and in what form.
@AndriiLutsiv you have specified both min and max for the yaxis and they are no longer advisory since 3.46.0. The range is therefore fixed at 35 (= max - min). This number can only be divided by 5 and 7, since ApexCharts always uses equal divisions for the ticks.
Some choices:

adjust your yaxis options to guarantee a zero tick, eg, min: -5, max: 30 (you can assume that a nice value like 5 will be used for the increments, or min: -4, stepSize: 4, if you want a specific increment, etc, or

don't specify at all and let ApexCharts figure out what min and max to use, that will include zero (generally/always).

Here's the result leaving out both the yaxis min and max settings.

Thanks a lot for a reply. Im sorry I had to adapt the codepen to a real case scenario. Here is an updated codepen that is from my project https://codepen.io/A_n_d_r_i_i/pen/jORrqLW. As we see somehow the '0' is missing on the yaxis also there is only 1 metric instead of several ones. Im usning the most recent version of apexcharts. I wonder if it is possible to show '0' without min and max values. For some reason forceNiceScale didn`t help

This is not a solution but I can show you what's happening.
The chart height is set to 200 pixels and in order to avoid overlapping
labels on the y axis, the ticks have been reduced. At 200 there isn't much
scope wrt the number of ticks. To see the ticks it actually computed set
the height to 300 in the template section at the top of your codepen js.
There are 11 ticks (plus the X axis at the bottom). Unfortunately 11 is a
prime number so you either get all 11 ticks or just 1 and nothing in
between, because tick increments must always be equal in ApexCharts.
I need to think about how to make this better than it is but in the
meantime all I can suggest, assuming your height of 200 can't be altered:

try, for example in this case, stepSize: 1.5

fake a zero line using a yaxis annotation. Say:

annotations: {
yaxis: {
y: 0,
label: {
text: ''
}
}
}
On Wed, 13 Mar 2024, 3:53 am Andrii, @.***> wrote:

Thanks a lot for a reply. Im sorry I had to adapt the codepen to a real
case scenario. Here is an updated codepen that is from my project
https://codepen.io/A_n_d_r_i_i/pen/jORrqLW. As we see somehow the '0' is
missing on the yaxis also there is only 1 metric instead of several ones. Im
usning the most recent version of apexcharts. I wonder if it is possible to
show '0' without min and max values. For some reason forceNiceScale didn`t
help
—
Reply to this email directly, view it on GitHub
https://github.com/apexcharts/apexcharts.js/issues/4317#issuecomment-1992122211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGBUF46CZSRIUUKQOPZD5XDYX4XIHAVCNFSM6AAAAABEQHQONOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJSGEZDEMRRGE
.
You are receiving this because you commented.Message ID:
@.***>


Add recursive options for node deletion, set LUT, and toggle bounding boxes

Closes https://github.com/scenerygraphics/sciview/issues/241
When implementing this I found that the only command where there is a clear need is DeleteNode, but SetLUT also makes sense we just don't have examples where a Volume is a child of another Volume.
However, I do see the potential for other things that can be applied to Node's recursively, like adjusting position through the inspector.

Note that I found this issue (https://github.com/scenerygraphics/sciview/issues/527) when implementing this PR.


add default timeout value to requests in v1.x

Hi,
The sdk version v1.x uses the requests library. so we need to add a default timeout value to raise a proper exception when onesignal api is down.
https://documentation.onesignal.com/docs/onesignal-api#what-is-the-response-timeout-for-api-endpoints
What is the response timeout for API endpoints?
Responses are usually generated within a couple seconds. However, in extreme cases, they can take longer.
OneSignal will wait 30 seconds for a response before automatically canceling the request. To verify no duplicate requests go through, you can add an Idempotent Key with the external_id parameter.
but in requests documentation:
https://requests.readthedocs.io/en/master/user/advanced/#timeouts
Timeouts
Most requests to external servers should have a timeout attached, in case the server is not responding in a timely manner. By default, requests do not time out unless a timeout value is set explicitly. Without a timeout, your code may hang for minutes or more.
lack of timeout param in v1.x version  👇
def basic_auth_request(method, url, token=None, payload=None, params=None):
    """
    make a request using basic authorization
    :param method: [GET, POST, PUT, DELETE ...]
    :param url:
    :param token: basic authentication token
    :param payload: post body
    :param params: Dictionary or bytes to be sent in the query string
    :return:
    """
    request_kwargs = {}
    if token is not None:
        request_kwargs["headers"] = {"Authorization": "Basic {0}".format(token)}
    if payload is not None:
        request_kwargs["json"] = payload
    if params is not None:
        request_kwargs["params"] = params
    return requests.request(method, url, **request_kwargs)

the commit will be merged???

they just closed the PR without merging it 😔 🤷♂


v5.11 TEA head marker support

Description
head markers are shown wrong on cactbot overlay with v5.11 client.

exact number
shown number

1
1

2
1

3
2

...
...

7
6

8
7

Additional information
I don't have network log file, but there's working js file now distributed on Korean community.
link
FYI - I don't do TEA.

Description
head markers are shown wrong on cactbot overlay with v5.11 client.
1 shown 1
2 shown 1
3 shown 2
...
7 shown 6
8 shown 7
Additional information
I don't have network log file, but there's working js file now distributed on Korean community.
link

This error is the same as the Chinese server is happening.

I'm extremely surprised that getHeadMarkerID() is failing that way. I'm also surprised that Square did not add in the scrambling for the head markers. Unfortunately I can't do much without a log. If you could ask around your communities for one, I can at least try to figure out what the failure is. (Since the error is occurring for both CN and KO, I can probably use a log in whichever language anyone is able to give me.)

I'm also surprised that Square did not add in the scrambling for the head markers.
@JLGarber I think you're telling, you've thought SQEX will apply some scrambling to head marker on v5.1 to CN and KO, but there's never been forth applying patches. There were no randomizing opcodes before v5.1 on Korean server even though SE's server was already applied. This scrambling head markers won't happen until v5.2 too.
So, if there's some important code change which varies by patch version, should diverge code by patch version until other servers get the same patch. If it can be solved without divergence, it's better though.

I know it has not been done before, but there has not been a good reason in previous patches. Here, there was a good reason, or at least I would have thought Square would think so. I did not expect them to simply follow the straight patch progression with no changes.
You are likely correct about having to split code by patch, but I do hope that after I get a log I can figure out a way to fix things that will not care about which patch we are on.

I understand you think that way, but there won't be something applied forward, skipping 0.x patches.
+I'm trying to get log.

log1
log2
I don't know if this log includes other fights too.

Thanks for that! Unfortunately, I cannot see what the issue might be from a brief look, and it will take longer than I have over lunch to investigate. I will take a closer look tonight.

Okay, quisquous helped me figure this out. I'll write up the full explanation for what went wrong on the pull request. Thanks for the bug report!


release a new version

https://github.com/macoscope/SwiftyStateMachine/releases/tag/0.3.0 :sparkles:


[material-ui][Rating] Fix the hover state when in a flex container

[x] I have followed (at least) the PR section of the contributing guide.

closes #40019
Cause
Rating component has display: "inline-flex" but when it's wrapped with Stack or any other component with display: "flex" then it has JustifyItems: "stretch" by default which causes the Rating component to stretch over the parent component width.
Change
I have provided the property maxWidth: "max-content" by default on RatingRoot.
Note:
This can also resolved by passing alignSelf: "flex-start" instead of maxWidth: "max-content" by default on RatingRoot but this may affect if the parent component has the display property "grid" or "flex" and wants to align items other then "start".

Does anyone test this solution?

Hey @amitabh-sahu thanks for the help! @DiegoAndai I need some engineering help to tell whether this would be a breaking change or not, what do you think?

@DiegoAndai I need some engineering help to tell whether this would be a breaking change or not, what do you think?

I think it should be fine, no breaking change 👍🏼
@amitabh-sahu may I ask you to provide before and after examples to make reviews easier? You can use

This CodeSandbox as a starting point for the before
This CodeSandbox as a starting point for the after

With that, we can test it out.

Sorry, I accidentally closed the pull request.
I have opened another PR #40131.


Syncing from upstream zalando/patroni (master)

bt_gitbot

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.858%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
12638

Relevant Lines:
12656

💛  - Coveralls


Run loop buggy behaviour

Hello,
I found a "non blocking" bug in the run loop (I guess it there). In fact, it blocked my UT... but I found a "work around" fix.
I describe it in the way I made it happen.
I build a model containing a boolean :
var MyModel= DS.Model.extend(EmberValidations.Mixin, {
  switcher: DS.attr('boolean')
)};

MyModel.reopen({
  validations : {
    switcher: {
      inclusion: {
        in: ['true', 'false']
      }
    }
  }
});

I user my value on a radio button. A radio button can't have boolean values, that's why my validation uses strings.
All this works, the type changes between boolean and string on the need and the validation works fine. And the REST part in Java gets the boolean value.
My problem is when I submit my page with no error.
If eveything is fine, I do a forward to another page (a list of MyModels). Then, after some seconds, I have an error in the consol :
TypeError: this.$(...) is undefined

Following the error, it happens in this part of generated code :
 _updateElementValue: (function () {
    Ember['default'].run.next(this, function () {
        this.$().prop("checked", this.get("htmlChecked"));
    });
}).observes("htmlChecked")

I use more than one radio button, but the only one making the error is the "true / false" one.
The "work around" fix I use is to define my property as string and not boolean. Everything works fine all the same, and I don't have the error anymore.
I reproduced the problem in another way.
This time, it's not only "true / false" radio button, but all the radio buttons that trigger the problem.
In my workflow, I create a new record from an existing one (still same pages as below).
So, here is what I do :

list page -> detail page (of one record) -> click to duplicate -> foward to creation page, filling the new model with the other's values -> fill what's left in the form -> submit the form -> go back to the list

When I do that manualy, it works, no problem.
But when I do that in my UT, as it is automated, it submits the form when "run.next" is still not performed, and I have the error.
Of course, all tests I do after "submit" are in a "andThen".
I guess it means qunit don't consider radio buttons "run.next" before to do what is in the "andThen".
I managed to find a "fix" : I have to do something like that when I save my model :
model.save().then(function () {
    Ember.run.next(...[uses a flashMessages to show success]

I wonder why radio buttons run loop is not finished when I save my model, as it has already been validated by ember-validations.
That's all, folks !

Maybe a "join" would be better than a "next" ?

I've encountered this same issue.


New "async" IndexReader strategy, with performance tests

https://hibernate.atlassian.net/browse/HSEARCH-2427
https://hibernate.atlassian.net/browse/HSEARCH-402

These are my results:

Benchmark                                                  (directorytype)  (indexSize)  (maxResults)  (readerStrategy)   Mode  Cnt     Score     Error  Units
JMHBenchmarks.concurrentReadWriteTest                                   fs      5000000            10             async  thrpt   10  2021.166 ± 203.769  ops/s
JMHBenchmarks.concurrentReadWriteTest:readWriteTestReader               fs      5000000            10             async  thrpt   10   259.620 ±  16.380  ops/s
JMHBenchmarks.concurrentReadWriteTest:readWriteTestWriter               fs      5000000            10             async  thrpt   10  1761.546 ± 206.186  ops/s
JMHBenchmarks.concurrentReadWriteTest                                   fs      5000000            10            shared  thrpt   10  1804.948 ± 132.665  ops/s
JMHBenchmarks.concurrentReadWriteTest:readWriteTestReader               fs      5000000            10            shared  thrpt   10   159.672 ±  13.547  ops/s
JMHBenchmarks.concurrentReadWriteTest:readWriteTestWriter               fs      5000000            10            shared  thrpt   10  1645.276 ± 139.887  ops/s

The benchmark runs queries and index writes concurrently; the query is very simple so that it doesn't dominate the CPU usage; the high amount of concurrent writes will stress the ReaderProvider: as you can see in this scenario the new "async" reader strategy gives a good 60% performance boost.
I actually expected more, but at least it proofs the point; I guess that with higher latency hard drives or larger indexes the benefit might get stronger.

That's right, the focus is on JMHBenchmarks.concurrentReadWriteTest:readWriteTestReader; it's good to see that the other metrics didn't change.

fixed as suggested and rebased.

@gustavonalle might be in good enough shape for you to give it a try as well?

to try it out:

https://github.com/hibernate/hibernate-search/pull/1196/files#diff-40176244800f79a0f62639216680e695R906

Thanks for the explanations! Ok to merge on my side, I'll let you see with @gustavonalle .

cool, merged it.


Refactor hacbs folder and merge into src

Fixes
Fixes HAC-2493
Description
Move HACBS code up into src directory. Remove hacbs specificity on local storage items. Remove hacbs css prefix.
A few components were left in the hacbs directory due to naming conflicts. These components need to get resolved to be the same component regardless of the feature flag (that is, the component should look the same), waiting on UX to determine the common look of these components.
Type of change

[x] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)

/cc @christianvogt

/retest

LGTM! Seems like the e2e failures happens in all the open PRs

LGTM!

/approve

/lgtm


use css variables for the colours

Would you mind a few hardcoded colours?

For example the donate button. No need to make a seperate var for it, in my opinion.

#13 has some vars for the colors :+1:


minor_modification_add_process_check

minor modification where we exclude process name contains "temp.dat"

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Clop Common Exec Parameter :white_check_mark:

diskUsage: 409600
runDuration: 51.931000000000004s
scanCount: 86562


Use next branch for next minor releases

Context
We use semantic-release for releasing our software. That helps us to follow a standard procedure for the releases, which allows us to have the release process automated by scripts.
Semantic-release deploys, by default, the following branches:

regular releases to the default distribution channel from the branch master
regular releases to a distribution channel matching the branch name from any existing branch with a name matching a maintenance release range (N.N.x or N.x.x or N.x with N being a number)
regular releases to the next distribution channel from the branch next if it exists
regular releases to the next-major distribution channel from the branch next-major if it exists
prereleases to the beta distribution channel from the branch beta if it exists
prereleases to the alpha distribution channel from the branch alpha if it exists

Source: https://semantic-release.gitbook.io/semantic-release/usage/configuration#branches

Recently, we started using next-major branches, e.g. for the work related to 3.0.0 version of the spec (see https://github.com/asyncapi/spec/tree/next-major).
However, we don't use next for the regular minor releases. We do, instead, use {YEAR_OF_RELEASE}-{MONTH_OF_RELEASE}-release (Read https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md#kick-off).
Description
I suggest we create a next branch on the repositories and use it for minor releases.
My main motivation behind that is the fact we will always have a branch created in there (next) ready to be used, a branch contributors will always target by default unless they represent a BC, where next-major branch will be targeted. Less important, IMHO, is the fact that we would then be following the defaults of semantic-release, but also something that sums up.
PROS:

Contributors will target always next, or next-major branch (unless patches, which will keep targeting master), so its easy for them to find the right branch to use as base.
The need of asking contributors to change their target branch from master to the recently created release branch dissapears.
We can configure default branch in GH to next. (Removing the 5th step in https://github.com/asyncapi/spec/pull/722/files#diff-f8db13a291483ecd3b9b3a658ef71578da20891791ddce676d767cd5174552dbR154).
No need to add release branches into .releaserc files every time we start a release (e.g. https://github.com/asyncapi/spec/pull/681/files#diff-644a8fae29c8e8b6ad5405a2e66c718a3b27f2e12581b7c5e00396d32b3e5cde).
Any other?

CONS:

next branch name is not as clear as it can be 2022-04-release.
Any other?

I would like to ask not only the Code Owners @fmvilas @derberg @dalelane but some randomly picked recent contributors as @char0n @KhudaDad414 @GeraldLoeffler @nictownsend @magicmatatjahu, even though everyone is invited to share their thoughts!

I'm sold. I'd just probably call it next-minor to avoid misunderstandings.

I have to say that be default I was against as in slack I could see only one motivator, which was consistency with semantic-releases
but, now, I see great improvement really:

always the same next branch that contributing guide can mention, so specify to contributors that they should open PRs against this branch that is actually always there 💪🏼
and yeah, no more need for manual creation of branches every few months and changing config in repos 🚀

I'm all ❤ for it
I saw @fmvilas comment on next-minor. I'm with keeping it next as we agreed in the setup of release process that we never know what type of the release is the next one, even if few last releases were minor.

I'm with keeping it next

I'm in as well with next, also because it is the default name in semantic-release.

I'm with keeping it next as we agreed in the setup of release process that we never know what type of the release is the next one, even if few last releases were minor.

Yeah, you're right. It may happen that during a release we have only patches.

During the spec 3.0 meeting today, a new problem has been surfaced: is the are the next and next-major branches on the spec-json-schemas and parser-js repos to work on the version 3 of the spec? Or are they to work on the next minor and major releases respectively? Apparently, there was a mix here. In parser-js, we want to have next-major because it's undergoing a major rewrite, therefore we want to concentrate all the PRs with breaking changes in a single branch, instead of releasing many major versions. That said, I thought next and next-major branches on those repos were to keep them in sync with the next and the next major version of the spec. Apparently, that wasn't the purpose.
So I'm here now suggesting that we use next-spec and next-major-spec in these repos. Just so they're not confused with their own release cycle.
I hope I made myself understandable 😅

So I'm here now suggesting that we use next-spec and next-major-spec in these repos. Just so they're not confused with their own release cycle.

I like this 👍

oh, good point about the naming, yeah next on parser will not be good, next-spec is ok. As for the major release, I'm not so sure. First of all we do not have anything about major releases in the current release process, as this is very individual and will be rare. So I do not think we need to agree on anything for it now + for 3.0 we already know that parser will also be bumped up with breaking changes

If i understand correctly, this is what we all agreed here so far:

next-spec => replacement for 2022-xx-xx-release branches for releasing minor versions.
next-major-spec => replacement for 2022-xx-xx-release for releasing major versions.

Shall we also keep next-major in repositories so we can work on major releases without having to wait for release branches to happen?
I would vote for a yes.
A really useful example is the work we are doing rewriting the Parser-JS to TypeScript https://github.com/asyncapi/parser-js/issues/482.
Another example could be working on the next major release for the spec way in advance (like half a year) as we did for 3.0. We could start having some code in the next-major branch so it keeps being updated automatically, released by bots (prereleases) without the need of changing any .releaserc or package.json files.
WDYT?

next-spec - I'm all in for this one to have it always in the spec, schema and parser repos
next-major-spec - I'm all in for this one to have it for 3.0 related work, which will anyway continue next few months, but then we just remove it. As 4.0 will not come very soon I believe 😆
next-major I guess we can keep it for TS rewrite, but for 3.0 related work shouldn't it be done in next-major-spec?

next-major-spec - I'm all in for this one to have it for 3.0 related work, which will anyway continue next few months, but then we just remove it. As 4.0 will not come very soon I believe 😆

I would vote not to remove it. I don't think it hurts having that branch in there IMHO.

next-major I guess we can keep it for TS rewrite, but for 3.0 related work shouldn't it be done in next-major-spec?

next-major branches would be there just for major releases related to only the repository. Nothing to do with the spec, like the TS rewrite, the split out of JSON Schema definitions @jonaslagoni did, or any other breaking change not related with the spec directly.
As a summary, those branches will be there to remove friction for contributors so they feel free to start working on anything without having to ask for branches (ask for creating them or just to what branches their PR's should target).

I would vote not to remove it. I don't think it hurts having that branch in there IMHO.

it will quickly get outdated and will be less useful than it could. Of course, I mean after 3.0 release.
We do not auto-update branches that do not have PR's opened

it will quickly get outdated and will be less useful than it could.

I agree, it will. 👍
Will it make sense to always have that branch included in package.json semantic-release section so it will be just a matter of creating the branch to just have the prereleases working automatically in case we need it? Or we should just remove branch + mention in package.json semantic-release section as well? Happy with any solution.

I guess it makes sense to have it always by default in semantic-release config 👍🏼

After receiving all the feedback, this is what we agreed so far:

To create the following branches and keep them in all repositories involved in spec releases (as per today spec, spec-json-schemas, parser-js):

next-spec => replacement for 2022-xx-xx-release branches for releasing minor versions.
next-major-spec => replacement for 2022-xx-xx-release for releasing major versions.

To include next-spec and next-major-spec branches  into .releaserc or package.json files for being considered by semantic-release in all repositories involved in spec releases (as per today spec, spec-json-schemas, parser-js).
To only create next-major branches on demand for those repositories that can have parallel developments that include major changes, that can be released independently from the spec; changes that only affect the repository itself and have nothing to do with major/minor spec releases. It can be all repositories except spec (if I'm not mistaken).
To include next-major branches into .releaserc or package.json files for being considered by semantic-release in those repositories that can have parallel developments that include major changes, that can be released independently from the spec; changes that only affect the repository itself and have nothing to do with major/minor spec releases. It can be all repositories except spec (if I'm not mistaken).

Did I summarize 👍  or 👎  ? cc @dalelane @derberg @fmvilas @jonaslagoni

To include next-spec and next-major-spec branches into .releaserc or package.json files for being considered by semantic-release in all repositories involved in spec releases (as per today spec, spec-json-schemas, parser-js).

After releasing 2.4, I will work on this so I can remove the mentions to 2022-04-release and instead add next-spec and next-major-spec.

I created a PR updating the RELEASE_PROCESS.md https://github.com/asyncapi/spec/pull/785

The following issues asking Code Owners to create those branches have been created:

spec: https://github.com/asyncapi/spec/issues/786
spec-json-schemas: https://github.com/asyncapi/spec-json-schemas/issues/214
parser-js: https://github.com/asyncapi/parser-js/issues/545

The following PR has been created updating package.json to reflect the new branch strategy:

spec-json-schemas: https://github.com/asyncapi/spec-json-schemas/pull/215
parser-js: https://github.com/asyncapi/parser-js/pull/546

For the spec repo, the same PR that contains the changes for the RELEASE_PROCESS.md contains the change, but this time in the .releaserc file: https://github.com/asyncapi/spec/pull/785


admin site - "role" field options are unclear

in the remove permissions/add permissions actions, the role field does not seem to accurately represent the possible roles. Should include, e.g. "testslack: Base User"

is this still an issue in v2?

closing because I don't think this is an issue in v2


chore: adds code scanning workflow

@cprice404 good call out. I made a follow-up issue for this on our internal tracking board. Will come back and do consistently on all SDK repos.


fix: add support for copying the boot secrets

/approve

/test kube

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test kube

/retest

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test kube

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

tls
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test tls

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test vault

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

kube
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

gsm-kapp
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm-kapp

kube
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test kube

vault
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
764c63ca95ca0f1e7c815d0cf174427c7b88636d
link
/test gsm

kube
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test kube

vault
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test vault

gsm-kapp
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test gsm-kapp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test kube

vault
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test vault

gsm-kapp
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test gsm-kapp

gsm
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test kube

vault
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test vault

gsm
7e15dbc70d2034e251d07c7f8a3a877c1f20d479
link
/test gsm

gsm-kapp
bd1a9f57c7ced22b0d898c394d107da3b8175623
link
/test gsm-kapp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ghcjs broken?

I've tried and failed to build ghcjs on Mac OS X and Linux at several points over the last few weeks. During this time, I noticed fbe153989ccd8ba4955e16bd44e2ffcc9a9710cc which marked the package broken and af21595ecaf0003496933b46beb9c841d828ca4e which claimed to fix it. There was additional work in 942f5070107213a884e2fe9cb987abd07df15aad to upgrade it. Yet I'm still seeing the same issue noted in fbe153989ccd8ba4955e16bd44e2ffcc9a9710cc when I've tried to build it:
Configuring ghcjs-0.1.0...
Setup: At least the following dependencies are missing:
aeson >=0.7 && <0.9, syb ==0.4.*, text-binary ==0.1.*
builder for ‘/nix/store/b234ajazd7v2qdl6scxzpipf5l5251c9-ghcjs-0.1.0.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/j17bjr4i4fs4661x8495ddj8kxang5g6-ghcjs-0.1.0.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/j17bjr4i4fs4661x8495ddj8kxang5g6-ghcjs-0.1.0.drv’ failed

The above is with a fresh install of Nix 1.9 and a fresh checkout of nixpkgs (HEAD was 4b836fb680116ad5fa85ea2bb43ffeff3be4ec53).

Hmm. I realized I might have not used the nixpkgs I thought I did. I'll try again just to be sure.

It probably was the old nixpkgs. I rebuilt with 6bb0436bb3b773b741d842d27f1b7a84596891e8 and failed at attoparsec:
Preprocessing test suite 'tests' for attoparsec-<IP_ADDRESS>...
[ 1 of 25] Compiling QC.Rechunked     ( tests/QC/Rechunked.hs, dist/build/tests/tests-tmp/QC/Rechunked.dyn_o )
[...]
[25 of 25] Compiling Main             ( tests/QC.hs, dist/build/tests/tests-tmp/Main.dyn_o )
Linking dist/build/tests/tests ...
running tests
Running 1 test suites...
Test suite tests: RUNNING...
bs:
  anyWord8: [OK, passed 100 tests]
[...]
  members: [OK, passed 100 tests]
  nonmembers: [Failed]
*** Failed! Exception: 'Prelude.chr: bad argument:<PHONE_NUMBER>96936' (after 11 tests and 1 shrink):
"xA\EMbR"
"J\SYN\ETBq"
(used seed -2009180548307453083)

         Properties   Total
 Passed  64           64
 Failed  1            1
 Total   65           65
Test suite tests: FAIL
Test suite logged to: dist/test/attoparsec-<IP_ADDRESS>-tests.log
0 of 1 test suites (0 of 1 test cases) passed.
builder for ‘/nix/store/v5gbfalxp6wvpj2f4hjmak3aq27p2cqp-haskell-attoparsec-<IP_ADDRESS>.drv’ failed with exit code 1

This seems to be due to upstream: bos/attoparsec#103

The attoparsec bug is nondeterministic, so I'm now continuing with the rest of the build.

@spl, please report the attoparsec bug upstream.
ghcjs builds fine on Linux: http://hydra.nixos.org/job/nixpkgs/trunk/haskell.compiler.ghcjs.x86_64-linux. On Darwin, there appears to be a problem in recent versions: http://hydra.nixos.org/job/nixpkgs/trunk/haskell.compiler.ghcjs.x86_64-darwin.

Yes, it appears to be a false alarm. ghcjs did build with the latest nixpkgs. I was unintentionally using the one that came with Nix 1.9.

@spl, please do report the attoparsec failures upstream, though!

@peti It's already been reported. I linked to the issue above.

Very cool, thank you!


Unable to Control with Alexa

I am from India.
I changed the alexa country to US and entered the address of US
But from the instructions page the last step you did to link the skill, I got till there but when I enter the ID and password of kodi connect and alexa started discovering devices and after that a blank page will open.
nothing happens from there.
And then if I ask echo to play any movie, she will respond I didn't find any linked video skill
please help

In Kodi connect addon settings you should enter your email from the kodi connect page, and secret that was generated for you


[🐛] Youtube link preview not working correctly on iOS

Issue
On iOS it only shows 'Youtube - Share your videos with friends family and the world'. It's working perfectly on Android with title, description and a preview image.
Reproduce

yarn add @flyerhq/react-native-link-preview
import { LinkPreview } from '@flyerhq/react-native-link-preview'
<LinkPreview text='This link https://www.youtube.com/watch?v=dpw9EHDh2bM can be extracted from the text' />

What I tried
Testing in both Simulator and real device (iPhone X). And I got only a youtube title, no description and no preview image.
Environment

Click to expand!
System:
    OS: macOS 11.2.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 247.37 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.13.0 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 7.6.3 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.0, 30.0.2
      System Images: android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>53283
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_242 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.4 => 0.63.4
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Thank you!
Temporary fix I found
When using the Youtube link on react-native, Youtube somehow redirects to the home page of the mobile version, effectively losing all information. Adding a user-agent header temporary fixed the issue.

headers: {
"user-agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"
},

Hi @suretarget we will consider adding user-agent to the library itself, thanks for the info!

Added user-agent in v1.2.0


Updates per oauth2-server-php changes

https://github.com/bshaffer/oauth2-server-php implements the final draft of OAuth 2.0. I'm noticing issues particularly in https://github.com/nerdfiles/stripe-market/blob/master/includes/stripe-functions.php#L96-L974 when double usage of $_GET['code'] for the purposes of crafting tokens and public keys — specifically keys.
When it comes to Stripe, I'm attempting to Connect Accounts via OAuth2.0 authorization_codes — accounts are being connected by it seems a double registration then queues up the deletion of that account. I have a feeling the culpable code exists here in the glue between oauth2-server-php and stripe-php itself.

Thanks for the feedback @nerdfiles
Lil confused, though: how can I help?

I'm doing this — it would be helpful to know if this is going in the right direction.

Given's Stripe's recent documentation, this is kind of outside of scope for my interests. But I've just been wondering. Perhaps this issue can be close if it's not really essential, and the core functionality is still available without updating to oauth2-server-php.

Gotcha. Not sure I can help really
What is the "issue" that you've opened this ticket for?

Going to close this issue. Reopen if you have any questions.


Account model support

We already have an account model design in CKB, which is used to build polyjuice. Here we plan to integrate it together with lumos, so lumos can enjoy a simple account layer model, for dapps that would need this feature.

inactive


Updates for 2022-2.1 envs

TODOs:

[x] pin the latest version of scipy
[x] add prefect
[ ] add bluesky-queueserver-api

The problem with scipy>=1.8 is that it does not exist for Python 3.7:
$ conda search 'scipy=1.8=py37*[channel=conda-forge, subdir=linux-64]'
Loading channels: done
No match found for: conda-forge/linux-64::scipy==1.8[build=py37*]. Search: conda-forge/linux-64::*scipy*==1.8[build=py37*]

PackagesNotFoundError: The following packages are not available from current channels:

  - conda-forge/linux-64::scipy==1.8[build=py37*]

Current channels:

  - https://conda.anaconda.org/conda-forge/linux-64
  - https://conda.anaconda.org/conda-forge/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

and use the search bar at the top of the page.

$ conda search 'scipy=1.8=py38*[channel=conda-forge, subdir=linux-64]'
Loading channels: done
# Name                       Version           Build  Channel
scipy                          1.8.0  py38h56a6a73_0  conda-forge
scipy                          1.8.0  py38h56a6a73_1  conda-forge

We can try switching from Python 3.7 -> 3.8 for now, as diffpy is supported on that version of Python.

Downloaded the py38 test env from https://github.com/nsls2-conda-envs/nsls2-collection-tiled/actions/runs/2190779095 and installed diffpy locally. It imports successfully, so we can switch to py38 as a minimum Python version.

@gwbischof, I think it's ready to go. I added bluesky-queueserver-api from PyPI for Python 3.9 for now as it had some conflicts if installed from conda-forge.

Published on Zenodo: https://zenodo.org/record/6499325.


Add Monokai Pro and Classic

Hello,
I've added the missing filters:

Classic (Although there already is a classic variant, this one is slightly different. It's Hazenbergs own variant I guess
Pro (I've converted the pro theme to match the other filters. The colors where not quite correct and it will benefit from the configuration I've already done)

Pro

Pro (Classic)

@hlissner  @ema2159  @ianpan870102  Please check if everything is like you wanted it in this PR and #601

Reference: #532

Sure! The one thing I don't like much is the change in the bg-alt. The contrast is too much, it's too dark. The same would go for the other filters' implementation.

Sure! The one thing I don't like much is the change in the bg-alt. The contrast is too much, it's too dark. The same would go for the other filters' implementation.

I'll review it. From the top of my head I can't tell you where I picked the color from. Might have been implemented like this in VS Code (where I took the color from) or I chose it myself because it was missing.
If the latter is the case, I'll adjust it. But this will take a couple of days as I'm super stumped with work atm.
Alternatively, your or @ianpan870102 can recommend a different color.

I think I can pick some from VS Code. I think I know which ones you picked, but there is another option to pick also in VS Code which I'd rather choose.

bump

Sorry but I don't use doom/doom-themes anymore.


Use wasmtime caching

We should investigate wasmtime native caching with LRU eviction policy. Without caching, every call to Module::new will recompile the module, even if unchanged. We can use cache_config_load or cache_config_load_default. We should be careful to check how caching works with different engines
At the moment we're compiling every wasm smart contract exactly once and store it in memory, so there really is no benefit of using caching. We should only explore caching in case that we don't want to keep all triggers in memory
In #3238 we have introduced preloading of triggers. This is good because it should reduce in-memory size of wasm triggers and speed up trigger execution. With caching enabled preloading may no longer be necessary.
Who can help
@Arjentix @mversic

I don't think, that preloading will be useless if we enable caching after #3401. Because fristly I introduced preloading for Runtime Validator as it was very slow even with caching enabled

Because at first I introduced preloading for Runtime Validator as it was very slow even with caching enabled

could it be because at that point you were still using different engines? Otherwise, we have no use of wasmtime caching

Since #3406 it has become apparent that wasmtime caching improves our integration test start-up time. Without caching it takes too long for the genesis to compile. It was my initial assumption that this happens because all tests share the same validator in the genesis.json but after some poking around I wasn't able to undeniably confirm this. Therefore, wasmtime caching remains enabled
I'm closing this issue


Loose env after cd

When I use rbfu-env the switch doesn't last, e.g.
$ rbfu-env @1.9.3-p0
$ ruby -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]

It switch environments fine, but as soon as I cd anywhere else, it reverts back to my system install.
$ cd ..
$ ruby -v
ruby 1.9.3dev (2011-07-03 trunk 32372) [x86_64-linux]

Do you have "--auto" set? This hooks into cdRVM-style and switches ruby versions depending on .rbfu-version files in current directory and home directory.

No. Which is exactly why I don't understand why it would switch back to @system every time I used cd.
I want to use rbfu-env, but I don't want to use current directory .rbfu-verison.

I'm afraid I haven't been able to reproduce this bug. Can you give me some details on the version used (0.2.0 or HEAD?), what shell you're working with etc.?

I used git clone git://github.com/hmans/rbfu.git to install so HEAD. I am on a Ubuntu Linux system using bash.
My .bashrc contains
eval "$(rbfu --init)"

To reproduce I do:
$ ruby -v
ruby 1.9.3dev (2011-07-03 trunk 32372) [x86_64-linux]
$ rbfu-env @1.9.3-p0
Activated Ruby 1.9.3-p0. (from command line)
$ ruby -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]
$ cd ..
$ ruby -v
ruby 1.9.3dev (2011-07-03 trunk 32372) [x86_64-linux]
trans@logisys:rubyworks$

The only thing I can think of that might be in conflict is that I have my own redefinition of cd that I use, which is part of the reason I don't want the --auto option. Could that have something to do with it?

Yes, it could. Care to post it?

Ok. It's a work in progress on an idea I had for "context aware" commands. I suck at bash scripting so I'm sure it could be much better, but here's what I have thus far.
  # TODO: This needs work b/c it won't catch any $PATH changes after the fact.

  export REALPATH="$PATH"

  function cd() {
     builtin cd "$@"

     if [ -d ./.bin ]; then
       build=''
       for file in ./.bin/*
       do
	       build="$file:$build"
       done
     fi

     export PATH="$build:$REALPATH"
  }

It looks like you're saving PATH into REALPATH at the time your .bashrc runs, and then re-set your PATH to that every time you cd. Which will undo the changes made to PATH by rbfu-env. So, yeah, I'm afraid it's your cd function that breaks it.
Take a look at the PATH modification functions I've added to the rbfu script, maybe they're a good starting point for what you're trying to do.
Other than that, I'm closing this issue for now.

Ah, so rb-fu overrides cd regardless of --auto. I thought that's something rbfu didn't do which is why I switched :-(

No, it doesn't. But rbfu-env, which you invoke, modifies PATH (for obvious reasons), and your own cd function keeps resetting PATH to whatever it was at when your .bashrc was invoked.

Ah, I see. And thanks to your suggestion I think I know how to fix my cd now. Thank you!


How can I solve this problem?

It looks like some Nginx error.
https://github.com/wekan/wekan/wiki/Nginx-Webserver-Config


Failed to connect to Azure storage on Hololens2 device

[Enter feedback here]
Good afternoon,
I was following the Azure storage tutorial and was able to run the app in the Unity Editor just fine, but when I deployed it to the app and attempted to set an object I was met with this error:
'Failed to connect with Azure Storage. If you are running with the default storage emulator configuration, please make sure you have started the storage emulator.'
Is there a solution or work around for this?
Thank you,
Nick

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

ID: f15853f4-20ac-bea9-89b0-4cd7da19a5be
Version Independent ID: 398529a4-fee0-21bb-6cc6-b57b47d25ea1
Content: Azure Cloud Tutorials - 2. Integrating Azure Storage - Mixed Reality
Content Source: mixed-reality-docs/mr-learning-azure-02.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @jessemcculloch
Microsoft Alias: jemccull

Hi @nra20 , we're working on finding the fix for this on another open ticket: #28. I'll update you when we have something!

Hi @nra20 , we're working on finding the fix for this on another open ticket: #28. I'll update you when we have something!

Hi @hferrone  thank you for the reply. Was anyone able to figure out why this error occurs?
Best,
Nick

Hi @nra20, check out the suggested fix here https://github.com/MicrosoftDocs/mixed-reality/issues/28


Status code 403 using using GoogleFinance as provider

Hello,
Trying to use GoogleFinance as a provider gives an error code of 403:
const swap = require('node-currency-swap');
swap.addProvider(new swap.providers.GoogleFinance());
const rate = swap.quoteSync({ currency: 'USD/EUR' });

Error:
Server responded with status code 403: Sorry... We're sorry... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.
is there an API key to be integrated or so ?

+1


[NETBEANS-648] Adding source version 10 and 11 to maven projects.

Pretty trivial fix of the issue.

Closed in favor of #495


puppet: Include the OS-enabled nginx module configurations.

This allows system-level configuration to be done by apt-get install
of nginx modules, which place their load statements in this directory.
The initial import in ed0cb0a5f89d of the stock nginx config omitted
this include -- one potential explanation was in an effort to reduce
the memory footprint of the server.
The default nginx install enables:
50-mod-http-auth-pam.conf
50-mod-http-dav-ext.conf
50-mod-http-echo.conf
50-mod-http-geoip2.conf
50-mod-http-geoip.conf
50-mod-http-image-filter.conf
50-mod-http-subs-filter.conf
50-mod-http-upstream-fair.conf
50-mod-http-xslt-filter.conf
50-mod-mail.conf
50-mod-stream.conf

While Zulip doesn't actively use any of these, they likely don't do
any harm to simply be loaded -- they are loaded into every nginx by
default.
Having the modules-enabled include allows easier extension of the
server, as neither of the existing wildcard
includes (/etc/nginx/conf.d/*.conf and
/etc/nginx/zulip-include/app.d/*.conf) are in the top context, and
thus able to load modules.

Derived somewhat from #21930.
The risk here is that one of the default modules does, just by being loaded, have a performance impact.  This seems relatively unlikely, but including them does broaden the surface area for security risk, as well as memory footprint and just bugs.
If we think the risk is unacceptable, we can install nginx-light rather than nginx-full, which only includes 50-mod-http-echo.conf.  The install path for that is a little dicey, though, as it either (a) leaves those modules installed even when nginx-light swaps with nginx-full, which would combine with this commit to include more modules, or (b) explicitly uninstall the existing module packages, which might possibly break functionality if folks are using them.
If we feel that the modules are a risk, I think I'd prefer (a).
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

This seems reasonable, merged, thanks @alexmv!

I guess to be explicit, I'm fine with backporting this one.

Cherry-picked to 5.x as 029b72c4964770886651524201a5a81928ec9c1a


It would be useful if the "Run Functional Tests" build step would report its test results in real time.

It would be useful if the "Run Functional Tests" build step would report its test results in real time.
We have some large test suites which can take > 10 hours to complete. Not having these results in real time makes it hard to gauge the stability of builds as we can't see the outcome of the tests for 10 hours!
If a number of tests are failing, then we'd know that something has gone terribly wrong and we need to cancel the build and investigate.
There's obviously a workaround of "deploy more test machines" but that's not always a suitable or applicable solution.

@matthew-horrocks: Thank you for the suggestion - I have added it to the backlog and closing this issue here. I would also recommend making this suggestion on user voice https://visualstudio.uservoice.com/forums/330519-team-services/category/145281-test, so that other users that may be interested in it can vote as well.


Adding source secret option for jenkins-s2i

Solving issue #21
Adds the option to use a secret with an ssh-key for a private repo.
To test this, it should be verified that it works with both a public (no key) and a private repo (with key).

@logandonley I messed up here. can you please move the this to a second template. leave the existing template as is, and add a new one for the secret e.g https://github.com/rht-labs/labs-ci-cd/tree/master/templates/s2i-app-build


Error: Nabu Casa Report State to Google

The problem

Every now and then the restart of my Home Assistant instance is blocked. It seems like the Cloud integration is blocking the restart when failing to report state to Google.
Environment

Home Assistant release with the issue: 105.5
Last working Home Assistant release (if known): ?
Operating environment (Hass.io/Docker/Windows/etc.): Docker on Linux
Integration causing this issue: Cloud
Link to integration documentation on our website: https://www.home-assistant.io/integrations/cloud/

Problem-relevant configuration.yaml

---
cloud:
  google_actions:
    filter:
      include_entities:
        - climate.ac_bedroom
        - climate.ac_living
        - climate.ac_office
        - ...
    entity_config: !include_dir_merge_named ../integrations/cloud

An excerpt from files located in ../integrations/cloud -- here's ../integrations/cloud/climate/ac.yaml:
---
climate.ac_bedroom:
  name: "Klimaanlage Schlafzimmer"
  room: Schlafzimmer
climate.ac_living:
  name: "Klimaanlage Wohnzimmer"
  room: Wohnzimmer
climate.ac_office:
  name: "Klimaanlage Büro"
  room: Büro

State Reporting is enabled in the Cloud settings.
Traceback/Error logs

-02-22 16:18:16 ERROR (MainThread) [hass_nabucasa.google_report_state] Unexpected error
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/iot_base.py", line 108, in connect
    await self._handle_connection()
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/iot_base.py", line 147, in _handle_connection
    await self.cloud.auth.async_check_token()
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/auth.py", line 145, in async_check_token
    await self.cloud.run_executor(self._check_token)
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 166, in run_executor
    return self.client.loop.run_in_executor(None, callback, *args)
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 751, in run_in_executor
    executor.submit(func, *args), loop=self)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 163, in submit
    raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown

Additional information
It seems https://github.com/home-assistant/home-assistant/issues/28894 faced the same issue.

https://github.com/home-assistant/home-assistant/pull/32168 should hopefully fix it.


enumerate errors

I seem to keep getting enumerate errors.
IndexError: list index out of range
And the code with problems is in this range:
    **for j, sample in enumerate(samples):**
        cur_t -= 1
        if j % 100 == 0 or cur_t == -1:
            print()
            for k, image in enumerate(sample['pred_xstart']):
                filename = f'progress_{i * batch_size + k:1}.png'
                TF.to_pil_image(image.add(1).div(2).clamp(0, 1)).save(filename)
                tqdm.write(f'Batch {i}, step {j}, output {k}:')
                display.display(display.Image(filename))

That first line is usually where the error is highlighted. I'm new to this so is there anywhere I should be looking to see whats wrong?

Can you post the entire stack trace / code that you are using to produce this issue?


Upgraded To Latest; Avatars Broken

Gitea version (or commit ref): 1.12.1 (Current download from the main site.)
Git version: 2.27.0
Operating system: Windows Server 2012 R2
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist: Not relevant.

Description
Upon upgrading to latest Gitea from 1.9.x, avatars are now broken by default. User avatars are now defaulted to:
https://<website_url>/user/avatar/<username>/<user_avatar_id>

However, these do not resolve to anything and thus show a dead image. Manually attempting to go to this link does redirect to:
http://<website_url>/img/avatar_default.png

But, there are two issues here.

The redirect is going to HTTP and not HTTPS.
The redirect is not happening when looking up the avatar to be displayed anywhere on the site.

Every user has to update their avatar now to fix the issue. This appears to be a redirect and protocol de-elevation issue.

Also noticed that this does not seem to be consistent across the site. On the main repo list page, avatars are linked to:
<img class="ui avatar image" src="/user/avatar/<USERNAME>/-1" alt="">

Which fail to load, again due to the site attempting to redirect to HTTP for the default avatar.
Next, if I go to a user profile page that has a broken avatar, that page fails to display the avatar and is linked as:
<img src="/user/avatar/<USERNAME>/290" title="<USERNAME>">

Also fails and is attempting to redirect to HTTP.
Along with this, any profile page that has a broken avatar will attempt to redirect the entire site to HTTP. If you refresh/force-refresh (CTRL+F5) on a broken avatar profile page, the site is redirected to HTTP instead. This does not happen when the profile has a valid avatar though.
This seems to happen when there is any broken resource on the page. Very odd that Gitea is trying to de-elevate to HTTP like this.

Which page did you found that broken image?

Every single page that an avatar is referenced/used.
For example:

The main dashboard.
User profile pages.
Repository root pages that show commit information.
Commit pages specifically.

I was able to fix this and found the cause. Was due to Cloudflare and some of their SSL settings.
Here is a rundown of what to adjust/fix in case others run into this issue while using Gitea via IIS behind Cloudflare.

Log into Cloudflare and select the domain that your Git server is hosted behind.
Select the 'SSL/TLS' options tab for the site.

Change the encryption mode to 'Full'.

Select the 'SSL/TLS' > 'Edge Certificates' option for the site.

Change the 'Always Use HTTPS' to 'On'.
Change the 'Automatic HTTPS Rewrites' to 'On'.
Optional: Turn 'Minimum TLS Version' up to your desired security level. (1.0 Default is fine.)
Optional: Turn 'Opportunistic Encryption' to 'On'. (Recommended to be on anyway.)
Optional: Turn 'TLS 1.3' to 'On'. (Recommended to be on anyway.)

If you need to work with custom certificates and such, you should do that now as well at this point. Settings and setups for that will vary, so you will need to do that part yourself.
After your setup is done, then you should purge your site's entire cache on Cloudflare. You can do that via:
'Caching' > 'Configuration' > 'Purge Cache' - Purge Everything


block mutation of read-only array in series

[x] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

reproduction case:
In [1]: array = np.array([1, 2, 3])

In [2]: array.flags.writeable = False

In [3]: series = pd.Series(array)

In [4]: series[0] = -1

In [5]: series
Out[5]:
0   -1
1    2
2    3
dtype: int64

In [6]: array
Out[6]: array([-1,  2,  3])

In the case I was running into I was passing a numpy.memmap which is a subclass of ndarray but was over a read only memory segment so attempting the setitem was causing a segfault. The new behavior matches the numpy behavior:
In [4]: series[0] = -1
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-5-2ad0997d5cf2> in <module>()
----> 1 series[0] = -1
   ...
ValueError: assignment destination is read-only

In [5]: array[0] = -1
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-7-f67d1d011a13> in <module>()
----> 1 array[0] = -1

ValueError: assignment destination is read-only

regarding the travis failure: do you cache the compilation accross the runs? I noticed that I needed to ensure that the .so and .c was removed because for some reason the .pyd was not treated as a dependency that required recompilation.

Here's the PR where caching was added
https://github.com/pydata/pandas/pull/13526
I don't really know how it works, but it doesn't seem to check .pxd files which would explain your issue.

Working on this in #14363

Current coverage is 85.26% (diff: 100%)

Merging #14359 into master will not change coverage

@@             master     #14359   diff @@
==========================================
  Files           140        140
  Lines         50632      50632
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits          43171      43171
  Misses         7461       7461
  Partials          0          0

Powered by Codecov. Last update ee374ee...c51bc15

Sorry about the misunderstanding around setitem vs the inner function. I will undo the micro optimizations in python and create a safe/unsafe version of the cython function. The places where we are doing things in a loop can do a check once and delegate to the unsafe version where the spot calls can use the checked version.

rebased to fix conflict in whatsnew

thanks!
maybe make an issue on pandas2 repo about this (IIRC you made a comment already), so that this is not forgotton.

Thank you! I think this is not an issue in pandas2 because series is backed with a pandas.Array instead of an ndarray.


#991 Refactor validate.ts

Monika Pull Request (PR)
What feature/issue does this PR add
containing two major functions that is very complex:

validateNotifications
validateConfig

How did you implement / how did you fix it
refactoring those 2 functions into multiple units and components
How to test

run test for monika : "npm test"
run codescene test

screenshot

dropping this PR, code is not clean, colliding with other ticket.


Please import Plinga

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
We are in middle of one important dapp project and need wagmi
please accept wagmi in poll request
Regards.
Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

It will be merged eventually soon once we get the time to check everything is okay. Please don’t open issues asking for PRs to be merged.


sabnzbd: 1.2.1 -> 2.3.2

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/.sabnzbd-wrapped -h got 0 exit code
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/.sabnzbd-wrapped --help got 0 exit code
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/.sabnzbd-wrapped -v and found version 2.3.2
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/.sabnzbd-wrapped --version and found version 2.3.2
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/sabnzbd -h got 0 exit code
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/sabnzbd --help got 0 exit code
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/sabnzbd -v and found version 2.3.2
ran /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2/bin/sabnzbd --version and found version 2.3.2
found 2.3.2 with grep in /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2
found 2.3.2 in filename of file in /nix/store/3xqw8f0fsgx591sh0b1rbdapbki6faqx-sabnzbd-2.3.2

cc "@fridh"

Failure on x86_64-linux (full log)
Partial log (click to expand)
Package ‘unrar-5.5.8’ in /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/rbvermaa-spot/pkgs/tools/archivers/unrar/default.nix:39 has an unfree license (‘unfreeRedistributable’), refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘sabnzbd-2.3.2’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/servers/sabnzbd/default.nix:30 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘unrar-5.5.8’ in /var/lib/gc-of-borg/nix-test-rs-4/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-4/pkgs/tools/archivers/unrar/default.nix:39 has an unfree license (‘unfreeRedistributable’), refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.