Allow kwargs in lambda handlers

What does this PR do?
Allows kwargs in lambda handlers.
Motivation
Our serverless project has kwargs in the lambda handlers to make testing easier. If we add the datadog lambda wrapper, the tests break.
Example of kwargs in a lambda handler:
SQS = boto3.client('sqs', region_name='us-east-1')
DYNAMO_CLIENT = boto3.resource('dynamodb', region_name='us-east-1')
LOGGER = setup_logger()

def lambda_handler(event, context, logger=LOGGER, sqs_client=SQS, dynamodb_client=DYNAMO_CLIENT):
    pass

Testing Guidelines
I ran ./scripts/run_tests.sh and all tests were OK. I also installed locally this version of the package on my project and my tests now pass.
Additional Notes
I also modified the run_tests.sh shebang to #!/bin/bash since the PYTHON_VERSIONS array was declared with bash-specific syntax and trying to run ./scripts/run_tests.sh with sh failed.

@SamuelM333 The PR is now merged and will be included in the next release. Thanks for your contribution 👍


waynergy: init at 0.0.13

Description of changes
Include waynergy package for https://github.com/r-c-f/waynergy

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 196478 run on x86_64-linux 1

1 package built:

waynergy


git-credential-libsecret error

Hi, I got the following error when I was trying to execute clone_and_checkout_branch.cpp sample. I use an ArchLinux distribution with libsecret. So, I already have the /usr/lib/git-core/git-credential-libsecret installed:
terminate called after throwing an instance of 'cppgit2::git_exception'
what():  reference 'refs/remotes/origin/usr/lib/git-core/git-credential-libsecret' not found

I was trying to pass a hex as reference


Use string copy for the SNI server name.

Since the server name is a string, we don't need to manually copy, we can just copy it into a std::string.

[approve ci]

I thought it is a workaround to ensure the string is available when ATS makes a log entry.
@ywkaras thoughts?

I thought it is a workaround to ensure the string is available when ATS makes a log entry.
@ywkaras thoughts?

The lifetime should be the same, right?

Ah, I read unique_ptr as shared_ptr... Now I don't get what it is for.

I found the related discussion about this variable. Seems like there was a lifetime issue and the type was shared_ptr on the first proposal. Maybe we don't have a reason not to use std:string now.
https://github.com/apache/trafficserver/pull/6108#pullrequestreview-310186898


Improve docs

Looks good expects for distributed joins. If we do decide to enable it by default, we need to clearly document this including the session property (should do this in any case).

@electrum where do you want to document session properties?  They are now self documenting, run show session, so I am a bit concerned about having two locations for documentation.

For something like distributed joins, we should have a section that explains the feature and trade off, and lists the config option and session option.
This should be in a new configuration chapter that comes after the deployment chapter.

Looks good


Create LICENSE

Coverage remained the same at 100.0% when pulling 65e40bcd9b0ddd3aacd093ca15766b33766af65d on add-license-1 into cef0c483211c8325f61fee6239fe4c60e68224b2 on master.


Emqttd crashed when stress test is running

Environment

OS: Ubuntu 14.04
Erlang/OTP: 20/9.0
EMQ: 2.1.2
CPU: 4-vcore
MEM: 8GB

Description
I used emqtt_benchmark to run stress test. When I simulated 8k publishers to run for minutes, the system would be out of memory and the emqttd processes would be crashed:
Configuration
OS max tcp connections limit has been raised to 64k
emq.conf is default except for:
mqtt.listener.tcp.max_clients = 65536
mqtt.listener.ssl.max_clients = 65536

acl.conf is default except for:
{allow, all, subscribe, ["$SYS/#", {eq, "#"}]}.

Test Steps
Sub:
./emqtt_bench_sub -h <emqttd-ip> -c 8 -t bench/test

Pub:
./emqtt_bench_pub -h <emqttd-ip> -c 8000 -t bench/test -q 0

Problem Description
CPU & MEM Usage(OOM can be observed)

error.log
2017-07-04 11:44:15.777 [error] <0.1139.0> Supervisor 'esockd_connection_sup - <0.1139.0>' had child connection started with mochiweb_http:start_link({emq_dashboard,handle_request,[{state,"/usr/lib/emqttd/lib/emq_dashboard-2.1.2/priv/www",#Fun<emq_d..>}]}) at <0.17389.0> exit with reason {json_encode,{bad_term,{'EXIT',{badarith,[{emqttd_vm,loads,0,[{file,"src/emqttd_vm.erl"},{line,160}]},{emq_dashboard_overview,node_info,0,[{file,"src/emq_dashboard_overview.erl"},{line,77}]},{rpc,local_call,3,[{file,"rpc.erl"},{line,311}]},{emq_dashboard_overview,'-nodes_info/0-lc$^0/1-0-',2,[{file,"src/emq_dashboard_overview.erl"},{line,73}]},{emq_dashboard_overview,nodes_info,0,[{file,"src/emq_dashboard_overview.erl"},{line,73}]},{emq_dashboard,'-dispatcher/1-fun-3-',4,[{file,"src/emq_das..."},...]},...]}}}} in context connection_crashed

crash.log
2017-07-04 11:44:15 =SUPERVISOR REPORT====
 Supervisor: 'esockd_connection_sup - <0.1139.0>'
 Context:    connection_crashed
 Reason:     {json_encode,{bad_term,{'EXIT',{badarith,[{emqttd_vm,loads,0,[{file,"src/emqttd_vm.erl"},{line,160}]},{emq_dashboard_overview,node_info,0,[{file,"src/emq_dashboard_overview.erl"},{line,77}]},{rpc,local_call,3,[{file,"rpc.erl"},{line,311}]},{emq_dashboard_overview,'-nodes_info/0-lc$^0/1-0-',2,[{file,"src/emq_dashboard_overview.erl"},{line,73}]},{emq_dashboard_overview,nodes_info,0,[{file,"src/emq_dashboard_overview.erl"},{line,73}]},{emq_dashboard,'-dispatcher/1-fun-3-',4,[{file,"src/emq_dashboard.erl"},{line,52}]},{mochiweb_http,headers,5,[{file,"src/mochiweb_http.erl"},{line,75}]}]}}}}
 Offender:   [{pid,<0.17389.0>},{name,connection},{mfargs,{mochiweb_http,start_link,[{emq_dashboard,handle_request,[{state,"/usr/lib/emqttd/lib/emq_dashboard-2.1.2/priv/www",#Fun<emq_dashboard.1.31422183>}]}]}}]

crash.dump analyzed by erl_crashdump_analyzer.sh
analyzing /var/log/emqttd/crash.dump, generated on:  Tue Jul 4 11:45:29 2017
Slogan: eheap_alloc: Cannot allocate 762886488 bytes of memory (of type "old_heap").
Memory:
===
  processes: 9123 Mb
  processes_used: 9122 Mb
  system: 534 Mb
  atom: 0 Mb
  atom_used: 0 Mb
  binary: 399 Mb
  code: 24 Mb
  ets: 20 Mb
---
total: 9657 Mb
Different message queue lengths (5 largest different):
===
      1 281442
      1 276601
      1 251671
      1 243350
      1 208328
Error logger queue length:
===
0
File descriptors open:
===
  UDP:  0
  TCP:  8023
  Files:  7
  ---
  Total:  8030
Number of processes:
===
16270
Processes Heap+Stack memory sizes (words) used in the VM (5 largest different):
===
      1 79467343
      2 66222786
      1 55185655
      1 45988046
      1 26613454
Processes OldHeap memory sizes (words) used in the VM (5 largest different):
===
      3 95360811
      3 79467343
      1 66222786
      1 196650
      1 6772
Process States when crashing (sum):
===
      3 Current Process Garbing
      3 Current Process Internal ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | ACTIVE | RUNNING | GC | TRAP_EXIT | ON_HEAP_MSGQ
      2 Garbing
      1 Internal ACT_PRIO_HIGH | USR_PRIO_HIGH | PRQ_PRIO_HIGH | ON_HEAP_MSGQ
      1 Internal ACT_PRIO_LOW | USR_PRIO_LOW | PRQ_PRIO_LOW | IN_PRQ_LOW | ACTIVE | IN_RUNQ | TRAP_EXIT | ON_HEAP_MSGQ
      2 Internal ACT_PRIO_LOW | USR_PRIO_LOW | PRQ_PRIO_LOW | TRAP_EXIT | ON_HEAP_MSGQ
      2 Internal ACT_PRIO_MAX | USR_PRIO_MAX | PRQ_PRIO_MAX | ON_HEAP_MSGQ
      2 Internal ACT_PRIO_MAX | USR_PRIO_MAX | PRQ_PRIO_MAX | TRAP_EXIT | ON_HEAP_MSGQ
      2 Internal ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | ACTIVE | RUNNING | GC | TRAP_EXIT | ON_HEAP_MSGQ
   8006 Internal ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | IN_PRQ_NORMAL | ACTIVE | IN_RUNQ | ON_HEAP_MSGQ
      9 Internal ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | IN_PRQ_NORMAL | ACTIVE | IN_RUNQ | TRAP_EXIT | ON_HEAP_MSGQ
      1 Internal ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | IN_PRQ_NORMAL | IN_RUNQ | TRAP_EXIT | ACTIVE_SYS | ON_HEAP_MSGQ
     94 Internal ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | ON_HEAP_MSGQ
   8150 Internal ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | TRAP_EXIT | ON_HEAP_MSGQ
   8017 Scheduled
   8251 Waiting

I don't think emqttd couldn't handle 8k cocurrent publishers with such resources(4-vcore/8GB), can anynoe know why the crash occured?
Thank you in advance.

@sincethen The fanout is 8K(pub) * 8 (sub) = 64K/s for you use only one topic in this test case. Messages will be accumulated in the queue of subscribers, and finally memory overloaded.
Benchmark report of EMQ 2.0: http://emq-xmeter-benchmark-en.readthedocs.io/en/latest/

@emqplus Thanks for your reply so much. I'll publish 8k different topics and use 8k subsribers to subscribe each topic later.

@sincethen The benchmark scripts for 8K/s PubSub:
./emqtt_bench_sub -h <emqttd-ip> -c 8000 -t bench/%i -q 0

./emqtt_bench_pub -h <emqttd-ip> -c 8000 -t bench/%i -q 0

@emqplus Then, how many messages could the emq be able to process per second for only one topic? It seems that it depends on memory and the amount of subscribers. I'd also like to have the quantization result. For example, for one topic, how many memories would be used by 1k messages per second and how many subsribers should subscribe them? Maybe, we should also consider the amount of publisher?

@sincethen The benchmark report of EMQ 2.0: https://readthedocs.org/projects/emq-xmeter-benchmark-en/

@emqplus Thank you. But I couldn't find the one topic scenario in the performance report above. Could you tell me how to calculate/transform the result from the report for the one topic scenario?


Adjust Catalog logs

The Catalog client is little too verbose when it errors. There are expected NotFound errors that we can downgrade to debug. Also the caller of the client logs errors so we don't need to explicitly do it in these cases.

👀 @wild-endeavor


[React-native 0.56] [Toggle Inspector] renderer.getInspectorDataForViewTag is not a function

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
    System:
      OS: macOS Sierra 10.12.6
      CPU: x64 Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz
      Memory: 613.02 MB / 32.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 9.1.0 - ~/.nvm/versions/node/v9.1.0/bin/node
      npm: 5.5.1 - ~/.nvm/versions/node/v9.1.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.2, macOS 10.13, tvOS 11.2, watchOS 4.2
      Android SDK:
        Build Tools: 23.0.1, 23.0.2, 23.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.2, 27.0.3
        API Levels: 23, 25, 26, 27
    IDEs:
      Android Studio: 3.1 AI-173.4697961
      Xcode: 9.2/9C40b - /usr/bin/xcodebuild
    npmPackages:
      react: ^16.4.1 => 16.4.2
      react-native: ^0.56.0 => 0.56.0
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-git-upgrade: 0.2.7

Description
After upgrate RN to 0.56, I'm try Toggle Inspector but that below error occur when I click anywhere in screen

Can confirm that upgrading to 0.57.0 of just the react-native package.json dependency did not fix the issue.

Found out the solution to this problem for us. We had a library, react-metrics, from which we imported a single named export. Turns out the lib goes ahead and enables screen tracking (taps, gestures) metrics for you even if you don't import those other functions. So we did a deep import e.g. import blah from react-metrics/some/sub/folder and this resolved the issue.


Save device address

Isn't it possible to implement bookmarks (IP:port of a device) for future connections? Or at least remeber previous address.
I want to be able to turn on ADB-over-Network feature on CyanogenMod 13, and press connect button in Android Studio. Now i have to specify IP address every time i start Android Studio.

I would add this feature in next version,thanks


fix: invalid date after subuh call a new date after prayer time

Refactor function getToday to fix invalid date after subuh by call a new date after prayer time based on issue #14

Hi mas, Thanks for Fixing please resolve the conflict firs

done @adityaputra11


Public repository is not found in repositories section

jcenter was added to list repositories

Build is fixed, no need to add jcenter to build script.


Warning ALWAYS_SEARCH_USER_PATHS when upgrade RN version 0.40.0

I have been issue blow:

Who can help me?

I can confirm having the same issue after upgrading from RN 0.39.2 to RN 0.41.2.

hi @bd-arc  :) . I upgrade from RN 0.39 to RN 0.40.0? I known't fix it where? I worry won't build product in IOS :(

I updated RN 0.42.0 and setting like blow?

Same issue here.

If you go to your project's Build Settings (in Xcode) and search for ALWAYS_SEARCH_USER_PATHS, you can see the setting for your own app there. Mine is set to No, but I'm still getting these warnings, so they're most likely coming from native dependencies you've linked.
You'll need to submit PRs to those dependencies to make the warnings go away. In the meantime, it's probably not anything to worry about!

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


Google oauth

Are you going to implement this?

I'll have a look at implementing this next weekend (won't have time before that).

This has been implemented now by https://github.com/nabeelamjad/poke-api/pull/4 thanks to @xssc, I'll add documentation later today and push a new release.


Issue uninstalling vproxy

local % brew uninstall vproxy
Warning: Calling plist_options is deprecated! Use service.require_root instead.
Please report this issue to the jittering/kegs tap (not Homebrew/brew or Homebrew/homebrew-core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/jittering/homebrew-kegs/Formula/vproxy.rb:162
Uninstalling /usr/local/Cellar/vproxy/0.7.1... (6 files, 8.3MB)
Warning: The following may be vproxy configuration files and have not been removed!
If desired, remove them manually with rm -rf:
/usr/local/etc/vproxy.conf
/usr/local/etc/vproxy.conf.sample

@dpanse not sure which issue you are reporting here but the first warning is a deprecation which I do need to fix.
The second warning is not an issue, just a note from homebrew that config files will not be deleted automatically. You have to clean those up yourself.


S3FileLoader and S3DirectoryLoader does not work on AWS Lambda

Both the loaders fail with the error below-
[Errno 30] Read-only file system: '/home/sbx_user1051'

This is because of this line. The only writable directory in AWS Lambda is /tmp, so there should be a way to set the directory.

Why was this issue closed? @wasa-ism how did you fix it?


Clicking on annotation link in lookout should open a new tab

It would be better if the links opened in a new tab, rather than replacing lookout.
Originally posted by @robertdavidsmith in https://github.com/G-Research/armada/issues/701#issuecomment-1171469338
When a user clicks on a link in annotations, the browser should open a new tab rather than overwriting the existing tab.

Hey team! Please add your planning poker estimate with ZenHub @dejanzele @jayofdoom @kannon92 @richscott

We can close with https://github.com/G-Research/armada/pull/1421


Added multiple resources

Can you remove the node js resource & add it in https://github.com/DhanushNehru/Ultimate-NodeJs-Resources
And format your commit as well

Okay sure , will be opening a new PR . Thanks for the update @DhanushNehru , sorry about the delay.


feat(momento-proxy): add delete support

Adds support for delete/del commands for memcahce and redis protocols.

@danielamiao Built momento-proxy locally tested w/ redis cli and telnet for memcache and looking good delete seems to be working well.
REDIS

MEMCACHE


Show an error when we cannot load a particular widget

For #9523
When loading 3rd party controls, their source may not be on unpkg.com. When this happens show an error to the user. If they're not connected to the internet, tell them this is likely why.
I tested this by removing our require define for azureml (as it's not on unpkg.com)

Codecov Report

Merging #10907 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #10907      +/-   ##
==========================================
- Coverage   60.67%   60.65%   -0.02%
==========================================
  Files         580      580
  Lines       31530    31531       +1
  Branches     4480     4480
==========================================
- Hits        19131    19126       -5
- Misses      11429    11433       +4
- Partials      970      972       +2

Impacted Files
Coverage Δ

...ience/interactive-common/interactiveWindowTypes.ts
100.00% <ø> (ø)

src/client/datascience/jupyter/jupyterNotebook.ts
4.27% <ø> (ø)

src/client/datascience/jupyter/jupyterSession.ts
56.80% <ø> (ø)

src/client/datascience/types.ts
100.00% <ø> (ø)

src/client/common/utils/localize.ts
95.20% <100.00%> (+0.01%)
:arrow_up:

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c523d6b...a95a8af. Read the comment docs.

@rchiodo
Thanks for cleaning up the imports by using import type, better to be explicit


Warn an admin before they remove their own admin access

As a test I just changed my own permissions and removed my administrative access. The action was successful but I was then shown a "Sorry, you do not have permission to access this area." message and I have no way of changing it back.
If an admin removes their own admin access it would be good if they at least gave a warning that the action can't be reversed and permissions will be greatly restricted to avoid people locking themselves out.

It's generally a good idea to prohibit users from modifying their own access permissions at all, both because of this, and because it hypothetically could also be a way for a user to escalate their own privileges (assuming there is some other flaw/bug allowing this).
And it's much easier to safely verify that userToModify != currentUser than checking whether there still would be some other admin left in the system if current user demotes theirself etc.

Resolved in #3502 - users can no longer unset their own is_superuser (or is_active) flag.


TNBPay - Feature update

Link to the milestone and objectives table.
#288
Detailed log of all completed objectives including valid proof of work.
The github repo has been updated. Doc also has been updated. https://github.com/akandejaphet/TNBPay
It can be tested live here > https://tnbcgames.com/enroll/
Project Wallet
86ee75d4cea77ca8339cc97f5e7426a3434d9f91465cd441c0c7593bd852e955

@olowudaniel1 , some points:

"Your enrollment was successful, the bracket would be updated soon." Should be "Your enrollment was successful, the bracket will be updated soon."

The countries are not in order. Do we need countries? Some people may not want to reveal this.

I hit "Payment made, next" after not sending the payment and it still said it was successful.

Fixed

Approved.

Approved for 10000 TNBC.


Measure code coverage by test

What would you like to be added:
Measure code coverage by test.
Why is this needed:
Code coverage is not perfect, but it's a reasonably good metric for quality.

Most of the code is covered by integration test, can we collect those?

Most of the code is covered by integration test, can we collect those?

IMHO, it makes more sense to measure the coverage of unit tests, which usually verify more fine grained behaviors in modules not exposed in the user facing layer.

IMHO, it makes more sense to measure the coverage of unit tests, which usually verify more fine grained behaviors in modules not exposed in the user facing layer.

We need to integrate coverage into GitHub Workflow.

We need to integrate coverage into GitHub Workflow.


feat:Allow Chinese punctuation as leading chars in long text mode

Fixes #40
This PR enhances the input validation to:

Support Chinese punctuation marks (like "【") as leading characters in long text mode
Modify the prompt message

Before:
kd -t "【安防卫士"  // print "✘  请输入有效查询字符或参数"
After:
kd -t "【安防卫士"  // print "
【安防卫士
Security guard
"
kd "【安防卫士"      // print "✘  请以字母、数字或汉字开头"

Thanks :)

Glad to help! :)
------------------ 原始邮件 ------------------
发件人:                                                                                "Karmenzind/kd"                                                                                @.>;
发送时间: 2024年12月11日(星期三) 中午12:55
@.>;
<EMAIL_ADDRESS>主题: Re: [Karmenzind/kd] feat:Allow Chinese punctuation as leading chars in long text mode (PR #43)
Thanks :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


.click is throwing error in windows 10 but working fine in linux(Ubuntu)

I tried to click a button to load more content in a webpage, for that I used the following code,
                                b = Watir::Browser.new
                                b.goto "https://www.example.com/"
                                b.button(:class => "ga_Finder_Load_More").click

This code is running fine in linux(ubuntu) and I can load the data in the webpage by clicking the button. But when I run the same code in window 10 I am getting the following error,
       C:/Ruby200/lib/ruby/gems/2.0.0/gems/watir-webdriver-0.9.1/lib/watir-            webdriver/elements/element.rb:508:in `assert_exists' from C:/Ruby200/lib/ruby/gems/2.0.0/gems/watir-webdriver-0.9.1/lib/watir-webdriver/elements/element.rb:114:in `click' from leafly_v1.3.rb:70:in `block (2 levels) in <main>' from leafly_v1.3.rb:67:in `each' from leafly_v1.3.rb:67:in `block in <main>' from C:/Ruby200/lib/ruby/gems/2.0.0/gems/nokogiri-<IP_ADDRESS>-x86-mingw32/lib/nokogiri/xml/node_set.rb:187:in `block in each' from

Ruby version - 2.0.0
watir-webdriver - 0.9.1
Can anyone please help me to fix this or can any one suggest me alternate method to click a button.
Thanks.

This looks like a question rather than an issue. Please send questions to the watir user group.
We reserve these GitHub issues for concrete issues with the Watir software.  If you've found one, please provide a concise reproducible test case and describe what results you are seeing and what results you expect.


IPv6 networking support

Benefit/Result/Outcome
A customer has a request for IPv6 Support with MLZ deployments at each tier
Description
Update bicep templates for networking deployment to support, configure and deploy IPv6 for vNets/Subnets/Networking
Acceptance Criteria

IPv6 is supported in MLZ deployments using dual-stacked networks
Azure Bicep is updated so that it is flexible to deploy IPv4 or IPv6 or IPv6 dual-stacked or IPv6 only networks (https://docs.microsoft.com/en-us/azure/virtual-network/ip-services/ipv6-overview)
Update documentation on how to add IPv6 support to existing IPv4 only deployments (https://docs.microsoft.com/en-us/azure/load-balancer/ipv6-add-to-existing-vnet-powershell)
Array types are added for address prefixes (instead of current string types)
Array types are added for subnets

Additional information from the customers who are using MLZ for their program:
At a high level, I think we need to be able to include IPv6 networking info in the deployment scripts (especially for Tier-3), but ultimately we want to be able to include IPv6 info any time we are specifying IPv4 info.
Our engineer identified where it might be best to make changes (see below), but there were additional considerations he wanted to explore (especially re: firewalls and ExpressRoute). I asked him to provide as much detail as possible.
From the vNet / vNet peering component it looks very easy.
Updating the virtualNetwork module to support multiple address prefixes should allow IPv6 ranges to be set for the vNet and subnets.
Azure calls them dual stack vNets. Same thing should apply for subnets as well.
Standard caveat that I haven’t tested these changes, but this is what I’d look at first.

Azure Firewall doesn’t support IPv6 rules yet. I’m not sure the roadmap / timeline on that. I’m not sure exactly how we’ll be routing our traffic, but this could be a blocker.
ExpressRoute does support IPv6. If we route traffic down the ExpressRoute to the NIH Firewall then out to the internet IPv6 would work fine. We’d just need to update the MLZ to configure the route tables to do this.

accidentally clicked close sorry!

I think this can be potentially implemented if we "add" ipv6 to the subnets or create new.
According to this article
We can potentially add an ipv6 subnet to the peered vnet to accomplish this: https://docs.microsoft.com/en-us/azure/virtual-network/ip-services/ipv6-overview

Lisa, thanks for adding the comments. Please make sure you sync with Mike D. He is adding the "acceptance criteria" to the issue to ensure that the production dependency our customer has on IPV6 will be satisfied with the planned work in our backlog.
Regards,
Denise Pirnia, PMP(r), PMI-ACP(r), CSM
Program Manager, Mission Solutions and Customer Expansion
Microsoft Corporation, Mission Engineering
301-771-8375 |<EMAIL_ADDRESS>[Microsoft Logo]
@.*** [CHANGE  PRACTITIONER  Prosci]  @.*** http://aka.ms/CFSI @.***  @.***
Confidentiality statement
This E-mail and any of its attachments may contain Microsoft proprietary information, which is privileged, confidential, or subject to copyright belonging to Microsoft Corporation. This E-mail is intended solely for the internal use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
From: lisamurphy-msft @.>
Sent: Wednesday, April 6, 2022 10:37 AM
To: Azure/missionlz @.>
Cc: Denise Pirnia @.>; State change @.>
Subject: Re: [Azure/missionlz] IPv6 networking support (Issue #693)
I think this can be potentially implemented if we "add" ipv6 to the subnets or create new.
According to this articlehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fexpressroute%2Fexpressroute-howto-add-ipv6-portal%23%3A~%3Atext%3D1%2520Add%2520IPv6%2520support%2520for%2520private%2520peering%2520using%2Cexisting%2520virtual%2520network.%2520Follow%2520the%2520steps...%25205%2520Limitations.&data=05|01|depirn%40microsoft.com|1d45c6153b5f4632a03108da17daf42d|72f988bf86f141af91ab2d7cd011db47|1|0|637848526422637248|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Rg1C8faaPGW8ofSjeVA0Et2pBn5OHXIbEl5II0g1Bpw%3D&reserved=0
We can potentially add an ipv6 subnet to the peered vnet to accomplish this: https://docs.microsoft.com/en-us/azure/virtual-network/ip-services/ipv6-overviewhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-network%2Fip-services%2Fipv6-overview&data=05|01|depirn%40microsoft.com|1d45c6153b5f4632a03108da17daf42d|72f988bf86f141af91ab2d7cd011db47|1|0|637848526422637248|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=g0s6bP%2FDZqNiyiHLvSyhAdp5VHYwGZBCejxSQVRXW48%3D&reserved=0

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fmissionlz%2Fissues%2F693%23issuecomment-1090347529&data=05|01|depirn%40microsoft.com|1d45c6153b5f4632a03108da17daf42d|72f988bf86f141af91ab2d7cd011db47|1|0|637848526422637248|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=UocMphRNRiGQB23lMq68r6nUSotax9ELKApbpeGgYQ4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASR4ZI3SQG4MJUCPEJNAYTDVDWOR5ANCNFSM5QGT2GGQ&data=05|01|depirn%40microsoft.com|1d45c6153b5f4632a03108da17daf42d|72f988bf86f141af91ab2d7cd011db47|1|0|637848526422637248|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2B4LloRHG21RiVyKkCDnlAd8BxKHFIDmfp%2BMks1v%2FM2M%3D&reserved=0.
You are receiving this because you modified the open/close state.Message ID<EMAIL_ADDRESS>

New acceptance criteria added, thank you @mikedzikowski !
This configurable pattern of offering three different "flavors" of networking configuration is worth considering.
Will need to consider the possibility of incorporating this with Azure Firewall, as previously stated by @DPirnia
Another thought on this might be Azure Front Door as a CDN, but I'm not certain on the availability of this option in disparate clouds: https://docs.microsoft.com/en-us/azure/frontdoor/front-door-overview

Maybe consider array type to allow multiple subnets.

Created a backlog item to start this work that involves changing the data type to an array for subnets and address prefixes.
This is only a pre-cursor to this ask though but I will link it here: #710

Not supported for AVD


remove step Install Chrome cause it seems already pre-installed in ub…

…untu-latest in GitHubActions

Codecov Report

Merging #291 (f70e128) into master (a8262bd) will decrease coverage by 14.86%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #291       +/-   ##
===========================================
- Coverage   60.76%   45.89%   -14.87%
===========================================
  Files          35       35
  Lines        1937     1937
  Branches      118      118
===========================================
- Hits         1177      889      -288
- Misses        729     1014      +285
- Partials       31       34        +3

Flag
Coverage Δ

unittests
45.89% <ø> (-14.87%)
:arrow_down:

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

Impacted Files
Coverage Δ

selene/core/wait.py
53.70% <0.00%> (-33.34%)
:arrow_down:

selene/core/exceptions.py
66.66% <0.00%> (-33.34%)
:arrow_down:

selene/common/fp.py
71.42% <0.00%> (-28.58%)
:arrow_down:

selene/core/condition.py
55.69% <0.00%> (-27.85%)
:arrow_down:

selene/support/webdriver.py
45.83% <0.00%> (-25.01%)
:arrow_down:

selene/support/by.py
48.27% <0.00%> (-24.14%)
:arrow_down:

selene/core/entity.py
37.29% <0.00%> (-22.64%)
:arrow_down:

selene/support/shared/config.py
65.98% <0.00%> (-18.45%)
:arrow_down:

selene/core/match.py
41.60% <0.00%> (-17.52%)
:arrow_down:

selene/support/conditions/have.py
50.68% <0.00%> (-16.44%)
:arrow_down:

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a8262bd...f70e128. Read the comment docs.


Failed Parentage rosolution and workflows not progressing from closed-out to announced.

Impact of the bug
Reqmgr
Describe the bug
This issue is a follow up on https://its.cern.ch/jira/browse/CMSCOMPPR-27653
This issue is closely related to https://github.com/dmwm/WMCore/issues/11252
All our workflows are moved from closed-out status to announced  by Unified. One of the flags in the workflow description that is checked during this transition is ParentageResolved = Trrue. This flag is set either by default in case no resolution is needed or later by ReqMgr2. The CherryPy thread which  is doing the resolution is StepChainParentageFixTask, running on the reqmgr-task pod at K8.
Looking into one such workflow: cmsunified_task_HIG-RunIISummer20UL17wmLHEGEN-03833__v1_T_220608_152814_5551  we find the following related datasets from two different steps:
    "Step5": {
      "ParentDset": null,
      "ChildDsets": [
        "/GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17RECO-106X_mc2017_realistic_v6-v3/AODSIM"
      ]
    },
    "Step6": {
      "ParentDset": "/GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17RECO-106X_mc2017_realistic_v6-v3/AODSIM",
      "ChildDsets": [
        "/GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17MiniAODv2-106X_mc2017_realistic_v9-v3/MINIAODSIM"
      ]
    }

Looking into the logs we see that parentage resolution is tried for the parent but not for the child dataset:
022-08-19T16:32:17.900Z [INFO] StepChainParentageFixTask.py:72 Resolving parentage for dataset: /GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17RECO-106X_mc2017_realistic_v6-v3/AODSIM
2022-08-19T16:32:17.907Z [INFO] DBS3Reader.py:938 Parent datasets for /GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17RECO-106X_mc2017_realistic_v6-v3/AODSIM are: []
2022-08-19T16:32:17.908Z [WARNING] DBS3Reader.py:943 No parent dataset found for child dataset /GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17RECO-106X_mc2017_realistic_v6-v3/AODSIM
2022-08-19T16:32:17.908Z [INFO] StepChainParentageFixTask.py:87 Parentage for '/GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17RECO-106X_mc2017_realistic_v6-v3/AODSIM' successfully updated. Proc
essed 437 out of 1567 datasets.
2022-08-19T16:32:17.908Z [INFO] StepChainParentageFixTask.py:90     spent 0.0078012943267822266 secs on this dataset: /GluGluToRadionToHHTo2G2WTo2G4Q_M-1200_TuneCP5_PSWeights_narrow_13TeV-madgraph-pythia8/RunIISummer20UL17RECO-106X_mc2017_realistic_v6-v3/AODSIM

This leads to a big increase of workflows in status closed-out. The trend starts simultaneously with the one from issue https://github.com/dmwm/WMCore/issues/11252. See the attached image bellow:

Upon further investigation we've noticed the the thread actually never managed to complete during a single pooling cycle and also  logs that  we used to have separate have been merged into the general log.
before:
parentageFixTask-reqmgr2-tasks-749465758c-x45np-20220812.log
statusChangeTasks-reqmgr2-tasks-749465758c-x45np-20220812.log

after
-rw-r--r--. 1 1000 1000 302193121 Aug 19 01:59 reqmgr2-20220818-reqmgr2-tasks-749465758c-x45np.log
-rw-r--r--. 1 1000 1000 469074023 Aug 20 01:59 reqmgr2-20220819-reqmgr2-tasks-749465758c-x45np.log
-rw-r--r--. 1 1000 1000 572314327 Aug 21 01:59 reqmgr2-20220820-reqmgr2-tasks-749465758c-x45np.log
-rw-r--r--. 1 1000 1000 619256094 Aug 22 01:59 reqmgr2-20220821-reqmgr2-tasks-749465758c-x45np.log
-rw-r--r--. 1 1000 1000 455811482 Aug 22 15:50 reqmgr2-20220822-reqmgr2-tasks-749465758c-x45np.log

How to reproduce it
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context and error message
Add any other context about the problem here, like error message and/or traceback. You might want to use triple back ticks to properly format it.

I feel like we have a major problem with the ReqMgr2 CherryPy threads service (called reqmgr2-tasks in k8s). We have problems affecting many of those threads:

this one, concerning StepChain parentage fix
the heartbeat monitoring and AMQ, see https://github.com/dmwm/WMCore/issues/11252
and Hasan also reported two workflows completed with no output stats, apparently the workflows were completed while jobs were still running

Besides having messed up logs for those services (since ~Aug 13th), I had the impression that a new cherrypy thread gets started every few minutes, still unclear if it's the same cherrypy thread or a new one getting spawned.

@amaltaro , I already pointed @todor-ivanov to plots of reqmgr2 RAM usage, see at plot. It shows both Reqmgr2 and ReqMgr2-tasks pods (which you can select by clicking on the pod name). Both show spikes up to 3GB of RAM which is resource limit in k8s and can cause pod's restart, Bottom line, the reqmgr2 had always such behavior, see from a plot but reqmgr2-tasks start getting it from around Aug 14th. I still doubt it is an issue with infrastructure. If we had issue with cherryypy thread then we will not have spikes in reqmgr2 before Aug 14th which is the case of reqmgr2-tasks. Have a look at plot to select your pods and dates.

I get a 500 Internal Server Error whenever I try to access the dashboard you shared. Is it "ReqMgr2" or the "CMSWEB timber k8s" dashboard?
If it was about resources, then I would expect the POD/replica to actually get killed and a new one started. This is not the behavior we see from the logs, the same POD (log) keeps reporting that it started a cherrypy thread.

plot is working fine for me, you can access it by visiting CMS monitoring dashboard, https://monit-grafana.cern.ch/d/000000530/cms-monitoring-project?orgId=11, then search for ReqMgr2 and view Memory usage by (node, pod) from kube-eagle plot.

from one of the log what is the following exit code means:
WATCHDOG: server exited with exit code signal 9..

Which explains why I see cherrypy threads getting restarted all the time.
Imran joined a discussion over MM "Web Serv & Security" channel.

It is interesting to see now that after we traced down and changed RAM threshold that reqmgr2-tasks spike up to 4GB and requires 5mins to stay at 3-4GB level to process the data, then it release it. I'm attaching RAM plots before and after adjustment:

before the pod limit adjustment (which cause pod restarts due to oom kill):

after adjustment

Thanks Valentin. We might evaluate to actually separate those cherrypy threads in their own k8s service in the future.
Things are moving forward and I confirm that the StepChain parentage CP thread is back operational, here is a summary of its last cycle:
2022-08-26T20:23:08.721Z [INFO] StepChainParentageFixTask.py:102 A total of 1788 requests have been processed, where 10 will have to be retried in the next cycle.

which started triggering workflow status transition from closed-out to announced.

I have created an extra issue to follow up on the WMCore resources requirements (to be worked on in the coming days):
https://github.com/dmwm/WMCore/issues/11259
and bumped up this issue related to k8s livenessprobe:
https://github.com/dmwm/WMCore/issues/10223
I think we can now close this issue out. Thanks to everyone that helped to investigate it.
Feel free to reopen it if I missed anything important still to be followed up in here.


The keyword color wrong after update to 1.86.0

Type: Bug
I use portable mode that place a sub dir named "data" at VSCode dir where code.exe resides.
I do the update action by extracting new version zip file to a new directory and then move the sub dir "data" from old version to new version VSCode dir.
After update to 1.86.0 from 1.85.2, the keyword color of python file was wrong.
I'm using the "Tomorrow Night Blue" theme.
The keywords lost their color which was set to #EBBBFF in TNB theme and presented with pure white (#FFFFFF).

When I move the "data" dir back to old v1.85.2 VSCode dir and launch v1.85.2 of code.exe, the color comes back.
I also tried a clean launch with an empty "data" folder, then change theme and load a python source code file, the problem is still there no matter install python language extension or not.

I found this issue maybe referring the same problem #204197

Another issue referencing this same problem, unfortunately marked as *as-designed
#203998

Same for me on TNB theme.  You get so used to a theme over years, that changes like these are very jarring.

Based on the thread above, I modified my settings like so to apply #EBBBFF to several text rules.
Depending on your language you might have different scopes.    These were for Typescript.
But you can use CMD+SHIFT+P Developer: Inspect Editor Tokens and Scopes to hover over the syntax and find the scope keys to use.
{
  "editor.tokenColorCustomizations": {
    "textMateRules": [
      {
        "scope": [
          "keyword.control.import.ts",
          "keyword.control.from.ts",
          "keyword.control.export.ts",
          "storage.type.ts",
          "meta.function.ts"
        ],
        "settings": {
          "foreground": "#EBBBFF",
          "fontStyle": ""
        }
      }
    ]
  }
}

I agree. I was just having a lot of trouble getting to work yesterday and this morning until I found a solution.  Like ain't nobody got time to be tweaking theme colors right now.   But it was just too distracting otherwise.

Downgrading to v1.85 is also a temporary fix for this (i'm in the same boat, don't have bandwidth right now for the distraction)

It looks like the grammar parsing rule has been at least partially changed, but I didn't find any information in 1.86 ReleaseNotes. For python the variables lost their color and presented using #FFFFFF confused that whether there were errors in the code file, which really is a disturb in working.
Also downgraded to v1.85.2 for now, looking forward next update to see if the problem will be settled down or at least an explanation about the rule change, or TNB theme update for 1.86+.

Asking theme maintainers to update (many of which are archived and unmaintained) without any warning or guidance seems like a regression.

This was caused by https://github.com/microsoft/vscode/pull/200043/files#diff-feb7ff0a1e168824a90fd0d2f324602089bf3f6d84013c66880673952b5d306f
Fix is on the way...

Add the following to your settings.json to fix it while we wait for a release:
// Temporary workaround for https://github.com/microsoft/vscode/issues/204223
"editor.tokenColorCustomizations": {
  "textMateRules": [
    {
      "scope": "keyword, storage, storage.type, entity.name.tag.css, entity.name.tag.less",
      "settings": {
        "foreground": "#EBBBFF"
      }
    }
  ]
}


rocsparse_spmm dense matrices have to have same order

I was having trouble using the rocsparse_spmm function, the solve stage (only the solve stage) kept returning an error rocsparse_status_invalid_value. After a while of searching, I found this if in the source code, only allowing dense matrices B and C with the same storage order (row major or column major). Okay, this might make sense, since it's another case to implement (although cuSPARSE has no problem with that). But I could not find any info about this restriction in the documentation.
Please add a note about this to the docs (and please take a look at other functions if the same problem isn't there too).

Also, as a sidenote, please improve the error reporting (across all ROCm libraries). As far as I remember, CUDA libraries print an actually helpful error message before returning the status/error code.

@jakub-homola Thanks for bringing this to our attention.I am currently investigating allowing different rocsparse_order for both B and C matrices. Ill report back once I have a working PR.
I agree on your side note about improving the error reporting. Ill bring this up at our next group meeting.

@jakub-homola I have merged the fix (https://github.com/ROCmSoftwarePlatform/rocSPARSE/commit/b13e637195f65d8e02ac554f0ee532d2aea11829) that allows using mixed rocsparse_order for the dense 'B' and 'C' matrices in SpMM to the develop branch. We are targeting this for rocm-6.0 release. I can also report that we are currently working on improving the logging also targetted for the rocm-6.0 release.

Awesome, thanks :)


Sprigressbar is based on the game Progressbar95. The goal is to fill your progress bar with blue or orange segments while avoiding red segments and closing the annoying mascots with your cursor.

How do you play your game?
Move your progress bar using WASD and your cursor using IJKL.
Catch the blue and orange segments in the empty space of your bar. Once the bar is filled you move to the next level. Orange segments don't give points at the end of the level. Red segments must not be touched at all cost, pink segments take away your progress, gray segments do nothing.
Close the mascots by moving your cursor into them. Some mascots can cause a game over and some rare ones can give you bonus points.

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[x] The image is in the /games/img directory.
[x] The name of the image matches the name of your file.

Thanks for your PR!

I might update the game, will I need to make another pull request?

No, that's why I want to update it later.

It's done, I decided to add easier levels at the beginning of the game.

nice updates! now did you make it to the end?

Yes, I just needed to try more

ok, out of curiosity, where did you heard about sprig?

My friend told me about it, but he doesn't have access to a computer so he can't make a game yet.


update README

Out of sync w/ current updates, possibly update after wizard is release ready.

Yep made this into issue #54 and #55.

from @fractastical: first screenshoot is confusing in readme, maybe doesn’t start w/ right command?

updated cc @fractastical


use string replace instead of regex in cjson for speed-up

Using strings.ReplaceAll instead of re.ReplaceAllString in below function show yield the same result while being faster.
https://github.com/secure-systems-lab/go-securesystemslib/blob/20c79cb5588a34d84d379f4d2ef6ceaa61f5b989/cjson/canonicaljson.go#L20-L23
This issue was initially raised by @jku in https://github.com/secure-systems-lab/securesystemslib/issues/372 and fixed by @PradyumnaKrishna in https://github.com/secure-systems-lab/securesystemslib/pull/410.

Closed by #25


Dismiss notification when clicked

Since clicking the notification opens the app, the notification should be dismissed.

I was just about to open an issue about this, and saw the pull req. Thanks :smile:


Group By Produces Inconsistent Counts

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
When retrieving record counts directly the results are different than expected. If I run the query through the query explorer in azure storage or in the browser vs running the same query via the sdk in .net core I get two different record counts.
To Reproduce

Create database
Create container
populate container with ~2k items with 2 different partition keys
Run following sql query to get count in c#
SELECT VALUE COUNT(1) FROM (SELECT root.id FROM root WHERE (root["dateField"] <= "2020-08-28T15:50:12.9709035+00:00") and root.partitionKey = 'key0' GROUP BY root.id) as c

The count will be different than when run in storage explorer.
Expected behavior
Same counts returned in both.
Actual behavior
Different counts are observed.
Environment summary
SDK Version: 3.12.0
OS Version (e.g. Windows, Linux, MacOSX)
Windows & Linux
Additional context
Add any other context about the problem here (for example, complete stack traces or logs).

Queries with an aggregate system function and a subquery with GROUP BY are not supported in Cosmos DB. Learn more here: https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-group-by

@tsharp the workaround here is the use the following variant
SELECT VALUE COUNT(1)
FROM root
WHERE (root["dateField"] <= "2020-08-28T15:50:12.9709035+00:00" and root.partitionKey = 'key0'
GROUP BY root.id


MRG: Fix CTF helmet

Found a bug with the CTF helmet generation, and also a tiny one with plot_evoked_field. This fixes them.
It also fixes some warnings in decoding_rsa.py, and makes the SPM faces example run. We'll see if CircleCI can handle it now. I think it should be able to.
Should go into 0.17.

Takes 3 min to generate, which will make it the longest example. I guess it's worth adding?
https://10255-1301584-gh.circle-artifacts.com/0/html/auto_examples/datasets/plot_spm_faces_dataset.html

Argh CircleCI died, so maybe the memory requirements are still too high. I'll remove the plot_ so we can move on with the release.

yes!


windows powertoys text extractor issue

Microsoft PowerToys version
0.74.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
TextExtractor
Steps to reproduce
whenever the text extractor is launched, it only shows a blank or black screen for nothing to seen to be extracted.

PowerToysReport_2023-10-05-15-32-55.zip
✔ Expected Behavior
when launched through shortcut keys or via system tray icon, it should work properly.
❌ Actual Behavior
it shows a completely blank screen.
Other Software
everything

This is frequently caused by the app Mica For Everyone. Please see #28217 for more details on how to resolve this incompatibility. Does this help? /needinfo

It solves the problem, thank you so much


[bug] slsa-framework/slsa-github-generator deadlocks if builder outputs a lot of data over stdio

Describe the bug
The slsa-framework/slsa-github-generator deadlocks if builder outputs a lot of data over both stdout and stderr. The reason is that the current implementation reads from stdout and stderr sequentially, which is a known cause of deadlocks: https://github.com/golang/go/issues/16787.
Because of #3569, it also does not print any logs in the process, the action just times out.
To Reproduce
Steps to reproduce the behavior:

Run the action in https://github.com/project-oak/oak/pull/5018, which happens to produce a lot of output over stdio.

I'll create a simpler reproduction upon request. But the bug should be fairly obvious when looking at internal/builders/docker/pkg/builder.go and https://github.com/golang/go/issues/16787.
Expected behavior
No deadlock.
cc @tiziano88 @jblebrun

Pre release now available, ref: https://github.com/slsa-framework/slsa-github-generator/pull/3570#issuecomment-2064815105


Jiechengdong/typescript integration

Overview
Typescript Integration - further backend work

[] Bug
[ ] Feature
[ ] Tech Debt

Description
Further backend typescript integration work
Additional context
Still need to retrieve some of the structures for tastyAPI queries but other than that mostly done with backend integration
Co-authored with @sc1272

Looks good!


The URL path is not valid - '/v1/apps/' is not a valid URL

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Basically there is an error when you have enabled waiting for build processing in appstore connect.

Command executed

Complete output when running fastlane, including the stack trace and command used

 Spaceship::UnexpectedResponse: [!] The URL path is not valid - '/v1/apps/' is not a valid URL
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/spaceship/lib/spaceship/connect_api/api_client.rb:222:in `handle_response'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/spaceship/lib/spaceship/connect_api/api_client.rb:113:in `get'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:27:in `get_app'
16:31:08     /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in `get_app'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/spaceship/lib/spaceship/connect_api/models/app.rb:101:in `get'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/pilot/lib/pilot/manager.rb:45:in `app'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/pilot/lib/pilot/build_manager.rb:123:in `wait_for_build_processing_to_be_complete'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/pilot/lib/pilot/build_manager.rb:78:in `upload'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:34:in `run'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
16:31:08     Fastfile:146:in `block (2 levels) in parsing_binding'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/lane.rb:33:in `call'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/commands_generator.rb:110:in `block (2 levels) in run'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/commands_generator.rb:354:in `run'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/commands_generator.rb:43:in `start'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in `take_off'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/gems/fastlane-2.216.0/bin/fastlane:23:in `'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/bin/fastlane:23:in `load'
16:31:08     /Users/mobiledev/Downloads/teamcity_agent/work/.gems/ruby/2.6.0/bin/fastlane:23:in `'
16:31:08   Process exited with code 1

Environment

 [REPLACE THIS WITH YOUR INFORMATION]

I have the same issue
The URL path is not valid - '/v1/apps/' is not a valid URL


Order of operations issue with nullish coalescing operator

The nullish coalescing operator is ignoring parenthesis and reordering operations in very strange ways.
IonScript Source:
  return this.binomialName + ":" + (this.variety ?? "")

Resulting JS:
    var _ref;
    return (_ref = this.binomialName + ':' + this.variety) !== null && _ref !== void 0 ? _ref : '';

Expected JS:
    var _ref;
    return this.binomialName + ':' + ( (_ref = this.variety) !== null && _ref !== void 0 ? _ref : '' )

This is still causing subtle issues here and there. I think this is a pretty dangerous bug. Is there some way you could work around the escodegen bug for now?


Failed to get status of deployment

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: Error
Error Message: Failed to get status of deployment.
Version: 0.18.0
OS: win32
OS Release: 10.0.18362
Product: Visual Studio Code
Product Version: 1.48.2
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:164:515775
rejected extension.bundle.js:164:515202
processTicksAndRejections task_queues.js:85:5

Please provide repro steps.

Dupe of https://github.com/microsoft/vscode-azureappservice/issues/1425


Crash when using carpenter‘s hammer with offhand

https://pastebin.com/pBJxtW2C

I can't reproduce. Can you check if it still happens with https://github.com/GTNewHorizons/Backhand/releases/tag/1.5.7-pre?

I also happens with 1.5.7.

Which block are you using it on and can you send a new log?

ohhh i was using hammer right click on carpenters bed to switch colors

cant reproduce in 1.5.8-pre

https://github.com/user-attachments/assets/b060e372-826c-4115-80e9-454b437c1093
Crash with Carpenter's garage door.
https://pastebin.com/QLuAZK1K

That is hopefully be fixed in https://github.com/GTNewHorizons/Backhand/releases/tag/1.5.10-pre

crash-2024-08-05_13.28.44-client.txt
1.5.10-pre

Third times the charm https://github.com/GTNewHorizons/Backhand/releases/tag/1.5.11-pre this time it should definitely be fixed.
You'll need to install https://github.com/GTNewHorizons/GTNHLib/releases if you don't already have it.


build-fhs-userenv-bubblewrap: use -m not -f for readlink

Description of changes
This change will let certain invalid paths to be passed, avoiding extremely weird and hard to debug behavior.
I have yet to test it more globally but I have no reason to suspect it would function any different, except for this additional change.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval

I've run into the same problem.  What will it take to get this integrated, @jonringer @jagajaga ?

Since the option can fail successfully, I think is more correct than what we have currently.


At sporadic times of the week, libraries refuse to show available in Petio.

Describe the bug
Some libraries, specifically TV shows refuse to show available. It appears that it doesn't even scan them when doing TMDB Show scans.
Some top level TV Show libraries show to be available.
To Reproduce
No known way to reproduce. Does this on a brand new install as well through Atlas DB, and local DB.
Expected behavior
Last week the libraries were showing available for sure, but then suddenly, TV shows showed no longer available, but showed requestable.
Screenshots
N/A
Desktop (please complete the following information):

OS: Windows 10 x64
Browser Chrome
Version: 96.0.4664.110

Smartphone (please complete the following information):
Same issue
Additional context
While bypassing all proxies and web hosts, etc. This issue is also present when browsing directly to localhost:7777

This sounds like perhaps an intermittent Plex connection issue. If Petio can't find certain media items when it scans then it will remove them from being "available". As this isn't a wider issue with Petio I'm going to close the issue and recommend you talk with our support team on Discord to better diagnose and hopefully resolve the issue.


BWN Network

Thank You for your great sourc code!
Yolo2_light also avaliable on BWN network?
Thank you

Yes, but yolov2_light only for detection: https://github.com/AlexeyAB/yolo2_light

How to use BIT1-XNOR-inference - only for custom models (you should train it by yourself):
You should base your cfg-file on yolov3-spp_xnor_obj.cfg and train it by using this repository as usual https://github.com/AlexeyAB/darknet by using pre-trained file darknet53_448_xnor.conv.74
Then use it for Detection-test or for getting Accuracy (mAP):
./darknet detector test data/obj.names yolov3-spp_xnor_obj.cfg data/yolov3-spp_xnor_obj_5000.weights -thresh 0.15 dog.jpg
./darknet detector map data/obj.data yolov3-spp_xnor_obj.cfg data/yolov3-spp_xnor_obj_5000.weights -thresh 0.15


[Enhancement] Copy/Paste filters

Mod: Blueprints Tweaks
Allow the filter of sorters and chests to be changed during the copy/paste process

This is very necessary!!! good


Display tags of the particular image searched via docker search command

Would be great for users to see the available tags of the particular image searched via docker search command.
Somewhat may be like docker search tags ubuntu should display all the tags of the ubuntu image present in docker hub.

Thanks for suggesting. This is a duplicate of https://github.com/docker/docker/issues/17238, so let me close this one. Please subscribe to that issue to keep informed on updates 👍


Avoid highlighting the new matrix multiplication operator.

The symbol for matrix multiplication (introduced in Python 3.5) is the
same as the symbol for the start of the decorator. This change should
correctly highlight only the decorators, but avoid highlighting the
multiplication operator. It also avoids highlighting syntactically
incorrect use of a function definition on the same line with a
decorator (or any other code).

I'll include it.


Badge / version sort order broken?

Hi!
Both the badge at https://github.com/marco-schmidt/am and the first link at https://javadoc.io/doc/com.github.marco-schmidt/am show version 0.0.3 although there were versions 0.0.4 to 0.0.6 and most recent 0.1.0, which I would expect in both contexts to be displayed. All versions are available in the version drop-down, but 0.0.3 is first and likely therefore the default for both badge and drop-down menu. Any idea how I could have the most recent version shown? This worked up to and including 0.0.6, if I remember correctly.
Greetings and thanks for hosting javadoc.io,
Marco

Thanks for reporting. It's a bug when onboarding Bintray.

Hi!
Both the badge at https://github.com/marco-schmidt/am and the first link at https://javadoc.io/doc/com.github.marco-schmidt/am show version 0.0.3 although there were versions 0.0.4 to 0.0.6 and most recent 0.1.0, which I would expect in both contexts to be displayed. All versions are available in the version drop-down, but 0.0.3 is first and likely therefore the default for both badge and drop-down menu. Any idea how I could have the most recent version shown? This worked up to and including 0.0.6, if I remember correctly.
Greetings and thanks for hosting javadoc.io,
Marco

Hi guys please do not upload anything that contained bugs and etc I hope that you are well understood that this is not supposed to be done. I reiterated again please do not upload anything that has bugs or so on. I hope u understand my deeper meaning. If you are not happy write back here. I am very happy to give you assistant.

fixed


Implement simd256 ml-kem

[x] #250
[x] #255
[x] #252
[ ] #268
[ ] #269

avx2 C is ongoing and the primary target for this week


Fix the duplicate of listing HTTF LP CFD model

Bug Description

A minor bug is noticed for the duplicated listing of HTTF LP CFD model under the HTGR and RELAP-7 HTTF model pages.
Steps to Reproduce

Impact

Closed by #343


Add array button text to all property arrays

Follow-up to https://github.com/godotengine/godot/pull/63266.

Adds the ability to specify options for property arrays with the ADD_ARRAY and ADD_ARRAY_COUNT macros.
See https://github.com/godotengine/godot/pull/63266 for the options.
Adds custom add button text for all property arrays.

Opening as draft because this is currently untested due to https://github.com/godotengine/godot/issues/63895.

Rebased and added text to more arrays that were originally missed.


Add type definitions for less-middleware

less-middleware/less-middleware.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/less-middleware
http://bower.io/search/?q=less-middleware
others?

[X] has a test file? (less-middleware/less-middleware-tests.ts or others)
[ ] pass the Travic-CI test?

@federicobond thanks mate!


svn: E170013: Unable to connect to a repository at URL 'https://llvm.org/svn/llvm-project/llvm/trunk'

Hello!
Can anybody help me with this issue?
I tried to follow instruction of building from source and have error when run ./install_clif.sh.
Destination <path to pykaldi folder>/tools/clif already exists.
Already up to date.
<my venv path>/bin/ninja
Using ninja for the clif backend build.
svn: E170013: Unable to connect to a repository at URL 'https://llvm.org/svn/llvm-project/llvm/trunk'
svn: E175009: The XML response contains invalid XML
svn: E130003: Malformed XML: no element found

All dependencies before was installed correctly. Also, If I open link https://llvm.org/svn/llvm-project/llvm/trunk I got 404 Not Found. Does link changed?

I guess the problem exists because the llvm link is down. Does anyone know the exact github version of trunk@307315?

I guess the problem exists because the llvm link is down. Does anyone know the exact github version of trunk@307315?

You can clone from https://github.com/bobzsj87/llvm-307315

You can clone from https://github.com/bobzsj87/llvm-307315

Thank you, @XavierGithub, I have also edited the install_clif.sh
Instead of,
#svn co https://llvm.org/svn/llvm-project/llvm/trunk@307315 llvm #cd llvm/tools #svn co https://llvm.org/svn/llvm-project/cfe/trunk@307315 clang
just past this:
wget https://github.com/llvm/llvm-project/archive/llvmorg-5.0.0-rc1.tar.gz
tar -xvf llvmorg-5.0.0-rc1.tar.gz
cp -r llvm-project-llvmorg-5.0.0-rc1/llvm/ .
cp -r llvm-project-llvmorg-5.0.0-rc1/clang llvm/tools/
cd llvm/tools

I couldn't find the version 307315 but I found 309*** from the official github repo: https://github.com/llvm/llvm-project/releases/tag/llvmorg-5.0.0-rc1

Thank you, @XavierGithub, I have also edited the install_clif.sh
Instead of,
#svn co https://llvm.org/svn/llvm-project/llvm/trunk@307315 llvm #cd llvm/tools #svn co https://llvm.org/svn/llvm-project/cfe/trunk@307315 clang
just past this:
wget https://github.com/llvm/llvm-project/archive/llvmorg-5.0.0-rc1.tar.gz
tar -xvf llvmorg-5.0.0-rc1.tar.gz
cp -r llvm-project-llvmorg-5.0.0-rc1/llvm/ .
cp -r llvm-project-llvmorg-5.0.0-rc1/clang llvm/tools/
cd llvm/tools

I couldn't find the version 307315 but I found 309*** from the official github repo: https://github.com/llvm/llvm-project/releases/tag/llvmorg-5.0.0-rc1

@quents,  it worked!
After replacing part of the code which you described everything installed correctly.
Thank you for help!

@quents,  it worked!
After replacing part of the code which you described everything installed correctly.
Thank you for help!


Add a helper to remove identical classes for class clashes

Thanks!

Sorry, but I ended up rewriting quite a bit of this. It feels cleaner to me like this.
But it still needs some performance checking. It's slower than it should be.

Darn. My mistake. This can't work like that. This needs some more work.

Thank you for your work. I am looking forward to the new release


Remove Autocomplete within UI Patient Capture

Autocomplete may crash browser and break application functionality if values not found
Steps to reproduce (tested on Firefox on Staging)
Enter ZIP code 12345 and press tab
If you type slow it might not allow you to even type more than 2 digits.
Browser stalls and increases memory to several GB within short time of script is not stopped.
If script is stopped application will not work (no drop-down lists and no save)

PR ist offen. Es fehlte nur ein if :)


Document 1.1.x Finder and Reader API extensions

The documentation needs to be updated to help plugin authors take advantage of the new capabilities in the 1.1.x Finder & Reader API.

#2093
#2103

Anything left to do there ?

I think it's all set.


View requires explicit height to render inside a ListView if empty on 0.12.0

I've implemented a simple renderRow function that uses an empty view that has a background colour applied on one side and the other side has row data. You can see the example working in 0.11.4 here https://rnplay.org/apps/kyAXMA.
This behaviour is inconsistent with the 0.12.0 version. The only way to get the empty coloured view to render is to specify a height. I would expect alignItems: 'stretch' on the parent view to be sufficient to make this behave as I'd expect.
Has something been changed between versions? Is there a more appropriate way to be doing this?
Thanks

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/view-requires-explicit-height-to-render-inside-a-listview-if-empty-on-0120
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix. We rely on the community to provide
bugfixes as the core team is focused on performance.


Slippage value in Savers from Thorchain seems wrong

It seems that the slippage value on Savers of Thorchain isn't calculated right.
Screenshot from Shapeshift (wrong value), one from Thorswap (right value).

Thanks for reporting this @HostFat ! It looks like THOR deprecated a few types and we're still using them instead of their new variant. Fixed in https://github.com/shapeshift/web/pull/5556 :)


The unit test case of the current libnetwork code cannot pass the test

[root@localhost libnetwork]# pwd
/root/src/github.com/docker/libnetwork
[root@localhost libnetwork]# export GOPATH=/root
[root@localhost libnetwork]# go test -v  github.com/docker/libnetwork
=== RUN   TestErrorInterfaces
--- PASS: TestErrorInterfaces (0.00s)
=== RUN   TestNetworkMarshalling
--- PASS: TestNetworkMarshalling (0.00s)
=== RUN   TestEndpointMarshalling
--- PASS: TestEndpointMarshalling (0.00s)
=== RUN   TestAuxAddresses
--- PASS: TestAuxAddresses (0.02s)
=== RUN   TestSRVServiceQuery
time="2019-08-01T19:34:51+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge/2593a7914aa4caf8581d86f931a8298b4d2398d4c448093ce01806930515eb04/ is not added to the store"
time="2019-08-01T19:34:51+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/cc6eadd86b5777ac5f70a92d430d2f2f5041baafd2c1a5b19c4e960291d03d8c/ is not added to the store"
time="2019-08-01T19:34:52+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/cc6eadd86b5777ac5f70a92d430d2f2f5041baafd2c1a5b19c4e960291d03d8c/ is not added to the store"
time="2019-08-01T19:34:52+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/cc6eadd86b5777ac5f70a92d430d2f2f5041baafd2c1a5b19c4e960291d03d8c/ is not added to the store"
--- PASS: TestSRVServiceQuery (2.37s)
=== RUN   TestServiceVIPReuse
time="2019-08-01T19:34:53+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge/6a962c5eb2fb1cc201c7faee4ca287d7ed7a3565944c9cfc8d0e4952d7ebf74f/ is not added to the store"
time="2019-08-01T19:34:54+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/4168ee8a025cae49296b5bea3a4a4311c1bd29c89d5d29204b4eabe42d61af3d/ is not added to the store"
time="2019-08-01T19:34:55+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/4168ee8a025cae49296b5bea3a4a4311c1bd29c89d5d29204b4eabe42d61af3d/ is not added to the store"
time="2019-08-01T19:34:55+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/4168ee8a025cae49296b5bea3a4a4311c1bd29c89d5d29204b4eabe42d61af3d/ is not added to the store"
--- PASS: TestServiceVIPReuse (2.19s)
=== RUN   TestIpamReleaseOnNetDriverFailures
time="2019-08-01T19:34:55+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge/7aaedf8113cdb9d75e617cdf54e39320c33b0f0a50e4551659fea6e5c2ae4047/ is not added to the store"
time="2019-08-01T19:34:56+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge/554f6507f80de0d5d06e4422fdd80fb174dcd5d41dbbc4af144bb184d1b763f0/ is not added to the store"
time="2019-08-01T19:34:56+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/f910d38df917fe1750bb540b9a30112db393098da28bf95379681923b2978900/ is not added to the store"
--- PASS: TestIpamReleaseOnNetDriverFailures (1.36s)
=== RUN   TestDNSIPQuery
time="2019-08-01T19:34:57+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge/57f479d32911818cf0f70c6c67268e6fc4de6c2ede39e13db9202aa018d66d31/ is not added to the store"
time="2019-08-01T19:34:57+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/8060b9c3bf81cc632d0d9854d7dd8e423fc491358efa171c79088aec34837640/ is not added to the store"
time="2019-08-01T19:34:57+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/8060b9c3bf81cc632d0d9854d7dd8e423fc491358efa171c79088aec34837640/ is not added to the store"
time="2019-08-01T19:34:57+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge-endpoint/8060b9c3bf81cc632d0d9854d7dd8e423fc491358efa171c79088aec34837640/ is not added to the store"
--- PASS: TestDNSIPQuery (1.20s)
resolver_test.go:137: Response:  ;; opcode: QUERY, status: NOERROR, id: 30768
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
    ;; QUESTION SECTION:
    ;name1	IN	 A

    ;; ANSWER SECTION:
    name1	600	IN	A	<IP_ADDRESS>

resolver_test.go:137: Response:  ;; opcode: QUERY, status: NOERROR, id: 63462
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;NaMe1	IN	 A

    ;; ANSWER SECTION:
    NaMe1	600	IN	A	<IP_ADDRESS>

resolver_test.go:157: Response:  ;; opcode: QUERY, status: NOERROR, id: 8167
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;name1	IN	 MX

resolver_test.go:169: Response:  ;; opcode: QUERY, status: SERVFAIL, id: 26570
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;nonexistent	IN	 MX

=== RUN   TestDNSProxyServFail
--- FAIL: TestDNSProxyServFail (0.00s)
resolver_test.go:225: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/br-4e578b5de7d3/route_localnet: no such file or directory
=== RUN   TestSandboxAddEmpty
--- PASS: TestSandboxAddEmpty (0.27s)
=== RUN   TestSandboxAddMultiPrio
--- PASS: TestSandboxAddMultiPrio (3.99s)
=== RUN   TestSandboxAddSamePrio
--- PASS: TestSandboxAddSamePrio (3.80s)
=== RUN   TestCleanupServiceDiscovery
time="2019-08-01T19:35:06+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge/8521daf3aaed24341a87bcd8db7de6b49d4877fc189b297e2b8e61d52a4297a1/ is not added to the store"
time="2019-08-01T19:35:06+08:00" level=warning msg="bridge store not initialized. kv object docker/network/v1.0/bridge/8668f10b0cbf7098ab98400b205a09cde2e11e104108375a27bbdaeac71ad443/ is not added to the store"
--- PASS: TestCleanupServiceDiscovery (0.67s)
=== RUN   TestDNSOptions
--- PASS: TestDNSOptions (0.61s)
=== RUN   TestBoltdbBackend
time="2019-08-01T19:35:07+08:00" level=warning msg="Cannot restore overlay endpoints because local datastore is missing"
time="2019-08-01T19:35:08+08:00" level=warning msg="Cannot restore overlay endpoints because local datastore is missing"
time="2019-08-01T19:35:08+08:00" level=info msg="Removing stale endpoint newendpoint (a4e9bf252977fea60c0a4adb5e88558a4017592385994ce639127e7c4560f792)"
time="2019-08-01T19:35:08+08:00" level=info msg="Fixing inconsistent endpoint_cnt for network host. Expected=0, Actual=1"
time="2019-08-01T19:35:08+08:00" level=info msg="Removing stale endpoint newendpoint (e62ca697d440e560b6ecf3ecac9d084f5a7839f132dd12775a1d12193a505fda)"
time="2019-08-01T19:35:08+08:00" level=info msg="Fixing inconsistent endpoint_cnt for network host. Expected=0, Actual=1"
--- PASS: TestBoltdbBackend (0.93s)
=== RUN   TestNoPersist
--- PASS: TestNoPersist (0.02s)
=== RUN   TestMultipleControllersWithSameStore
--- PASS: TestMultipleControllersWithSameStore (0.02s)
=== RUN   TestHost
time="2019-08-01T19:35:08+08:00" level=info msg=" does not exist, we create an empty resolv.conf for container"
time="2019-08-01T19:35:08+08:00" level=info msg=" does not exist, we create an empty resolv.conf for container"
time="2019-08-01T19:35:10+08:00" level=info msg=" does not exist, we create an empty resolv.conf for container"
--- PASS: TestHost (2.07s)
=== RUN   TestBridgeIpv6FromMac
--- PASS: TestBridgeIpv6FromMac (0.94s)
=== RUN   TestEndpointJoin
--- FAIL: TestEndpointJoin (0.02s)
libnetwork_linux_test.go:228: Cannot read IPv6 setup for bridge testnetwork1: open /proc/sys/net/ipv6/conf/testnetwork1/disable_ipv6: no such file or directory
=== RUN   TestExternalKey
--- FAIL: TestExternalKey (0.02s)
libnetwork_linux_test.go:395: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestEnableIPv6
--- FAIL: TestEnableIPv6 (0.01s)
libnetwork_linux_test.go:575: Cannot read IPv6 setup for bridge testnetwork: open /proc/sys/net/ipv6/conf/testnetwork/disable_ipv6: no such file or directory
=== RUN   TestResolvConfHost
--- PASS: TestResolvConfHost (0.53s)
=== RUN   TestResolvConf
--- FAIL: TestResolvConf (0.01s)
libnetwork_linux_test.go:733: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestParallel1
=== PAUSE TestParallel1
=== RUN   TestParallel2
=== PAUSE TestParallel2
=== RUN   TestParallel3
=== PAUSE TestParallel3
=== RUN   TestNullIpam
--- PASS: TestNullIpam (0.00s)
=== RUN   TestNull
--- PASS: TestNull (2.32s)
=== RUN   TestBridge
--- FAIL: TestBridge (0.01s)
libnetwork_test.go:158: Cannot read IPv6 setup for bridge testnetwork: open /proc/sys/net/ipv6/conf/testnetwork/disable_ipv6: no such file or directory
=== RUN   TestUnknownDriver
time="2019-08-01T19:35:14+08:00" level=warning msg="Unable to locate plugin: unknowndriver, retrying in 1s"
time="2019-08-01T19:35:15+08:00" level=warning msg="Unable to locate plugin: unknowndriver, retrying in 2s"
time="2019-08-01T19:35:17+08:00" level=warning msg="Unable to locate plugin: unknowndriver, retrying in 4s"
time="2019-08-01T19:35:21+08:00" level=warning msg="Unable to locate plugin: unknowndriver, retrying in 8s"
--- PASS: TestUnknownDriver (15.05s)
=== RUN   TestNilRemoteDriver
time="2019-08-01T19:35:29+08:00" level=warning msg="Unable to locate plugin: framerelay, retrying in 1s"
time="2019-08-01T19:35:30+08:00" level=warning msg="Unable to locate plugin: framerelay, retrying in 2s"
time="2019-08-01T19:35:32+08:00" level=warning msg="Unable to locate plugin: framerelay, retrying in 4s"
time="2019-08-01T19:35:36+08:00" level=warning msg="Unable to locate plugin: framerelay, retrying in 8s"
--- PASS: TestNilRemoteDriver (15.00s)
=== RUN   TestNetworkName
--- FAIL: TestNetworkName (0.02s)
libnetwork_test.go:253: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestNetworkType
--- FAIL: TestNetworkType (0.02s)
libnetwork_test.go:279: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestNetworkID
--- FAIL: TestNetworkID (0.01s)
libnetwork_test.go:305: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestDeleteNetworkWithActiveEndpoints
--- FAIL: TestDeleteNetworkWithActiveEndpoints (0.01s)
libnetwork_test.go:332: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestNetworkConfig
--- FAIL: TestNetworkConfig (0.05s)
libnetwork_test.go:437: Cannot read IPv6 setup for bridge br-4339021e0a92: open /proc/sys/net/ipv6/conf/br-4339021e0a92/disable_ipv6: no such file or directory
=== RUN   TestUnknownNetwork
--- FAIL: TestUnknownNetwork (0.03s)
libnetwork_test.go:476: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestUnknownEndpoint
--- FAIL: TestUnknownEndpoint (0.02s)
libnetwork_test.go:509: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestNetworkEndpointsWalkers
--- FAIL: TestNetworkEndpointsWalkers (0.02s)
libnetwork_test.go:550: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/network1/route_localnet: no such file or directory
=== RUN   TestDuplicateEndpoint
--- FAIL: TestDuplicateEndpoint (0.02s)
libnetwork_test.go:678: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestControllerQuery
--- FAIL: TestControllerQuery (0.02s)
libnetwork_test.go:728: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/network1/route_localnet: no such file or directory
=== RUN   TestNetworkQuery
--- FAIL: TestNetworkQuery (0.02s)
libnetwork_test.go:830: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/network1/route_localnet: no such file or directory
=== RUN   TestEndpointDeleteWithActiveContainer
--- FAIL: TestEndpointDeleteWithActiveContainer (0.04s)
libnetwork_test.go:977: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestEndpointMultipleJoins
--- FAIL: TestEndpointMultipleJoins (0.02s)
libnetwork_test.go:1052: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testmultiple/route_localnet: no such file or directory
=== RUN   TestLeaveAll
--- FAIL: TestLeaveAll (0.02s)
libnetwork_test.go:1120: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestContainerInvalidLeave
--- FAIL: TestContainerInvalidLeave (0.01s)
libnetwork_test.go:1185: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestEndpointUpdateParent
--- FAIL: TestEndpointUpdateParent (0.01s)
libnetwork_test.go:1251: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/testnetwork/route_localnet: no such file or directory
=== RUN   TestInvalidRemoteDriver
--- SKIP: TestInvalidRemoteDriver (0.00s)
libnetwork_test.go:1309: Skipping test when not running inside a Container
=== RUN   TestValidRemoteDriver
--- SKIP: TestValidRemoteDriver (0.00s)
libnetwork_test.go:1360: Skipping test when not running inside a Container
=== CONT  TestParallel1
=== CONT  TestParallel3
=== CONT  TestParallel2
--- FAIL: TestParallel1 (0.01s)
libnetwork_test.go:1468: Cannot read IPv4 local routing setup: open /proc/sys/net/ipv4/conf/network/route_localnet: no such file or directory
--- FAIL: TestParallel3 (0.02s)
libnetwork_linux_test.go:937: network network2 not found
--- FAIL: TestParallel2 (0.02s)
libnetwork_linux_test.go:937: network network2 not found
FAIL
FAIL	github.com/docker/libnetwork	53.979s
[root@localhost libnetwork]#

I want to know if there is a problem with my test method or something else that causes the test case to fail.
Please give me some feedback.

On master , we don't see any issues.  Can try running individual test and check if it runs?

I think that you can reproduce this problem on master.
When I execute these test cases separately, they are really able to pass the test. But I think we need to be sure that these test cases will pass the test when testing the entire directory.
Do you agree with me?
[root@localhost libnetwork]# go test -count=1  -v -run="TestEndpointJoin" github.com/docker/libnetwork
=== RUN   TestEndpointJoin
--- PASS: TestEndpointJoin (2.64s)
PASS
ok  	github.com/docker/libnetwork	2.710s
[root@localhost libnetwork]# go test -count=1  -v -run="TestExternalKey" github.com/docker/libnetwork
=== RUN   TestExternalKey
--- PASS: TestExternalKey (2.87s)
PASS
ok  	github.com/docker/libnetwork	2.923s
[root@localhost libnetwork]# go test -count=1  -v -run="TestEnableIPv6" github.com/docker/libnetwork
=== RUN   TestEnableIPv6
--- PASS: TestEnableIPv6 (1.49s)
PASS
ok  	github.com/docker/libnetwork	1.552s
[root@localhost libnetwork]# go test -count=1  -v -run="TestResolvConfHost" github.com/docker/libnetwork
=== RUN   TestResolvConfHost
--- FAIL: TestResolvConfHost (0.00s)
libnetwork_linux_test.go:645: network testhost not found
FAIL
FAIL	github.com/docker/libnetwork	0.067s
[root@localhost libnetwork]# go test -count=1  -v -run="^TestResolvConf$" github.com/docker/libnetwork
=== RUN   TestResolvConf
--- PASS: TestResolvConf (2.59s)
PASS
ok  	github.com/docker/libnetwork	2.648s
[root@localhost libnetwork]#

@ selansen  Could you give me some feedback?

@ selansen Could you explain the code below for me?
Why can running the test cases in the container ignore the error that is returned by the function checkBridgeNetFiltering?
func setupBridgeNetFiltering(config *networkConfiguration, i *bridgeInterface) error {
err := checkBridgeNetFiltering(config, i)
if err != nil {
if ptherr, ok := err.(*os.PathError); ok {
if errno, ok := ptherr.Err.(syscall.Errno); ok && errno syscall.ENOENT {
if isRunningInContainer() {
logrus.Warnf("running inside docker container, ignoring missing kernel params: %v", err)
err = nil
} else {
err = errors.New("please ensure that br_netfilter kernel module is loaded")
}
}
}
if err != nil {
return fmt.Errorf("cannot restrict inter-container communication: %v", err)
}
}
return nil
}


Use existing go version in go mod tidy an verify

This change ensures that running make mod-tidy doesn't update the go version specified in the mod files.

Actually, I think I missed something here. There reason my go version was being updated was that I had inadvertently created a go.mod file in api/producer with go 1.23.2 (running go mod init). This is then propagated to modules that pull this in.
I'm going to close this PR as unneeded since setting go 1.20 in that module addresses the issue.
Sorry for the back and forth.


Question: how to visit IP address?

For the project I'm working on, is there a way 'visit' to an IP address with colly?

Simply use the IP address instead of domain. (E.g. c.Visit("http://<IP_ADDRESS>/"))


Fix incompatibility function

Declaration of OptimistDigital\MenuBuilder\Classes\MenuItemText::getDisplayValue($value = NULL): string should be compatible with OptimistDigital\MenuBuilder\Classes\MenuItemBase::getDisplayValue(string $value): string

Thanks! Weird this issue didn't happen before.

Hey! Sorry about that, I made another update to these functions in release 1.3.3. My project crashed due to (string $value) enforcements when $value was null. I decided to remove the string type enforcements altogether and replace them all with $value = null.

Thank you, the most important is that classes are compatible.


2.2.0

Update to 2.2.0

:tada: This PR is included in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: