Failed assertion: line 2747 pos 12: '!_needsLayout'

flutter: ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞══════════════════════
flutter: The following assertion was thrown during a scheduler callback:
flutter: Updated layout information required for
flutter: RenderIndexedSemantics#9ecae NEEDS-LAYOUT to calculate semantics.
flutter: 'package:flutter/src/rendering/object.dart':
flutter: Failed assertion: line 2747 pos 12: '!_needsLayout'
flutter:
flutter: Either the assertion indicates an error in the framework itself,
flutter: or we should provide substantially more information in this error
flutter: message to help you determine and fix the underlying cause.
flutter: In either case, please report this assertion by filing a bug on
flutter: GitHub:
flutter:   https://github.com/flutter/flutter/issues/new?template=2_bug.md
flutter:
flutter: When the exception was thrown, this was the stack:
flutter: #2      RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2747:12)
flutter: #3      RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #4      Iterable.forEach (dart:core/iterable.dart:279:35)
flutter: #5      RenderSliverVariableSizeBoxAdaptor.visitChildren (package:flutter_staggered_grid_view/src/rendering/sliver_variable_size_box_adaptor.dart:296:29)
flutter: #6      RenderObject.visitChildrenForSemantics (package:flutter/src/rendering/object.dart:2836:5)
flutter: #7      RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #8      RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #9      RenderObjectWithChildMixin.visitChildren (package:flutter/src/rendering/object.dart:3128:14)
flutter: #10     RenderObject.visitChildrenForSemantics (package:flutter/src/rendering/object.dart:2836:5)
flutter: #11     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #12     RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #13     Iterable.forEach (dart:core/iterable.dart:279:35)
flutter: #14     RenderViewportBase.visitChildrenForSemantics (package:flutter/src/rendering/viewport.dart:222:10)
flutter: #15     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #16     RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #17     RenderIgnorePointer.visitChildrenForSemantics (package:flutter/src/rendering/proxy_box.dart:3309:14)
flutter: #18     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #19     RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #20     RenderObjectWithChildMixin.visitChildren (package:flutter/src/rendering/object.dart:3128:14)
flutter: #21     RenderObject.visitChildrenForSemantics (package:flutter/src/rendering/object.dart:2836:5)
flutter: #22     RenderSemanticsAnnotations.visitChildrenForSemantics (package:flutter/src/rendering/proxy_box.dart:4706:11)
flutter: #23     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #24     RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #25     RenderObjectWithChildMixin.visitChildren (package:flutter/src/rendering/object.dart:3128:14)
flutter: #26     RenderObject.visitChildrenForSemantics (package:flutter/src/rendering/object.dart:2836:5)
flutter: #27     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #28     RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #29     RenderObjectWithChildMixin.visitChildren (package:flutter/src/rendering/object.dart:3128:14)
flutter: #30     RenderObject.visitChildrenForSemantics (package:flutter/src/rendering/object.dart:2836:5)
flutter: #31     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #32     RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #33     RenderObjectWithChildMixin.visitChildren (package:flutter/src/rendering/object.dart:3128:14)
flutter: #34     RenderObject.visitChildrenForSemantics (package:flutter/src/rendering/object.dart:2836:5)
flutter: #35     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #36     RenderObject._getSemanticsForParent.<anonymous closure> (package:flutter/src/rendering/object.dart:2759:61)
flutter: #37     RenderObjectWithChildMixin.visitChildren (package:flutter/src/rendering/object.dart:3128:14)
flutter: #38     RenderObject.visitChildrenForSemantics (package:flutter/src/rendering/object.dart:2836:5)
flutter: #39     RenderObject._getSemanticsForParent (package:flutter/src/rendering/object.dart:2757:5)
flutter: #40     RenderObject._updateSemantics (package:flutter/src/rendering/object.dart:2725:41)
flutter: #41     PipelineOwner.flushSemantics (package:flutter/src/rendering/object.dart:1080:16)
flutter: #42     RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:458:21)
flutter: #43     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:883:13)
flutter: #44     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:319:5)
flutter: #45     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1145:15)
flutter: #46     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1082:9)
flutter: #47     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:996:5)
flutter: #51     _invoke (dart:ui/hooks.dart:150:10)
flutter: #52     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:270:5)
flutter: #53     _drawFrame (dart:ui/hooks.dart:114:31)
flutter: (elided 5 frames from class _AssertionError and dart:async)
flutter: ═════════════════════════════════════════════════════════════════

flutter doctor -v

[✓] Flutter (Channel beta, 2.7.0-3.1.pre, on macOS 12.0.1 21A559 darwin-x64,
    locale zh-Hans-CN)
    • Flutter version 2.7.0-3.1.pre at /Users/yangchaoguo/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fc7015e35a (3 weeks ago), 2021-10-27 15:18:41 -0700
    • Engine revision a75e3b80f9
    • Dart version 2.15.0 (build 2.15.0-178.1.beta)
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/yangchaoguo/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/yangchaoguo/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 51.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.62.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (2 available)
    • iPhone 13 (mobile) • DE52EF27-8F7E-4131-8CDB-5DCF25C10285 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • Chrome (web)       • chrome                               • web-javascript
      • Google Chrome 96.0.4664.55

Hi @ycg520520, please provide a complete minimal reproducible code sample.
Thank you


Using the notebook when there is no GPU

Hello! Thank you for sharing this work! I was wondering how I can use the demo notebook locally when there is no GPU？
When running the cell under "# Use pretrained SpanModel weights for prediction, " I got this error:
2022-07-06 12:28:07,840 - INFO - allennlp.common.plugins - Plugin allennlp_models available
Traceback (most recent call last):
File "/Users/xiaoqingwan/opt/miniconda3/envs/absa/bin/allennlp", line 8, in
sys.exit(run())
File "/Users/xiaoqingwan/opt/miniconda3/envs/absa/lib/python3.7/site-packages/allennlp/main.py", line 34, in run
main(prog="allennlp")
File "/Users/xiaoqingwan/opt/miniconda3/envs/absa/lib/python3.7/site-packages/allennlp/commands/init.py", line 118, in main
args.func(args)
File "/Users/xiaoqingwan/opt/miniconda3/envs/absa/lib/python3.7/site-packages/allennlp/commands/predict.py", line 205, in _predict
predictor = _get_predictor(args)
File "/Users/xiaoqingwan/opt/miniconda3/envs/absa/lib/python3.7/site-packages/allennlp/commands/predict.py", line 105, in _get_predictor
check_for_gpu(args.cuda_device)
File "/Users/xiaoqingwan/opt/miniconda3/envs/absa/lib/python3.7/site-packages/allennlp/common/checks.py", line 131, in check_for_gpu
" 'trainer.cuda_device=-1' in the json config file." + torch_gpu_error
allennlp.common.checks.ConfigurationError: Experiment specified a GPU but none is available; if you want to run on CPU use the override 'trainer.cuda_device=-1' in the json config file.
module 'torch.cuda' has no attribute '_check_driver'
I changed cuda_device to -1 in the jsonnet files from your folder training_config. But still no luck.

Hi, sorry the CPU inference seems not supported yet, we will try to implement and test it in the future.

I am only running it on CPU (windows).
What I've done is:

template.libsonnet: put the two mentions to cuda_device as  cuda_device :: -1,
when calling the python script avoid calling also the argument for cuda

hope it helps

@chiayewken Thanks for opening the thread. I will check and get back to you. Kindly don't close this thread for next few days.

I am only running it on CPU (windows). What I've done is:

template.libsonnet: put the two mentions to cuda_device as  cuda_device :: -1,
when calling the python script avoid calling also the argument for cuda

hope it helps

Unfortunately I am unable to get this to run on MacOS CPU, I've set the template.libsonnet cuda_deivce to -1, how do I avoid calling the argument for cuda in the python script?

Following the main file that I copied here
I don't use this parameter  --trainer__cuda_device "$DEVICE" \
_rm -rf model*
mkdir -p models
$PYTHON aste/main.py
--names 14lap,14lap,14lap,14lap,14lap,14res,14res,14res,14res,14res,15res,15res,15res,15res,15res,16res,16res,16res,16res,16res
--seeds 0,1,12,123,1234,0,1,12,123,1234,0,1,12,123,1234,0,1,12,123,1234
--trainer__cuda_device "$DEVICE"
--trainer__num_epochs 10
--trainer__checkpointer__num_serialized_models_to_keep 1
--model__span_extractor_type "endpoint"
--model__modules__relation__use_single_pool False
--model__relation_head_type "proper"
--model__use_span_width_embeds True
--model__modules__relation__use_distance_embeds True
--model__modules__relation__use_pair_feature_multiply False
--model__modules__relation__use_pair_feature_maxpool False
--model__modules__relation__use_pair_feature_cls False
--model__modules__relation__use_span_pair_aux_task False
--model__modules__relation__use_span_loss_for_pruners False
--model__loss_weights__ner 1.0
--model__modules__relation__spans_per_word 0.5
--model__modules__relation__neg_class_w_eight -1


CLDC-651 refused derived variable

Is it correct that we just set a single field if any attribute of any tenant has been refused?

@baarkerlounger according to the ticket REFUSED = 1 if any of the household characteristics question have been answered as 'refused' (now 'prefer not to say') for any of the household members


RESTful API support

So that we can build the dashboard based on AJAX.
Related: #5

@bentranter If you would like to work on this one. I recommend you to create a standalone file for api handlers(e.g. app/handler/api.go)
Also, we can take http://api.ghost.org/docs/ as a reference.


fix bug on column layout

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.61%. Comparing base (10b1723) to head (0b61de6).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #144   +/-   ##
=======================================
  Coverage   73.61%   73.61%
=======================================
  Files         123      123
  Lines       17382    17382
=======================================
  Hits        12796    12796
  Misses       4586     4586

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


Pk/local git provider impvs

PR Type:
Refactoring

PR Description:
This PR introduces several improvements to the LocalGitProvider class. It now raises an error if the repository root cannot be found, and the PR title is now derived from the head branch name instead of the target branch name.

PR Main Files Walkthrough:
-local_git_provider.py: Added a check in the constructor to raise an error if the repository root cannot be found. Changed the get_pr_title method to return the head branch name instead of the target branch name.

/describe

/improve

👍


Could add ARG name (like subtype) instead of type only?

Hi, thanks to your effort to develop this amazing tool! I have a question that if you can add ARG gene name, like subtype, instead of only ARG type?

Thank you for the advice!
Currently, the database is curated based on the types of antibiotics to which ARGs confer resistance.
We could enhance the framework to predict the ARGs themselves, but achieving high accuracy may be challenging due to the vast number of ARGs, which are unevenly distributed.
Nonetheless, we could try to curate the db first.


Add Ontario Design System

Adds the Ontario Design System, which is open-source but distributed through their website.
The design system includes:

coded components
guidance
a UI kit for designers

Hi @alexpate! Wanted to check if anything further is needed for adding a publicly-shared design system to the list. Thanks!

Apologies for the slow reply. This looks great, thanks so much for adding it!

Awesome, thanks! 🎉


Refactor Transition to become a protocol

This pull request brings substantial breaking changes to the current API of the Representor. It turns Transition into a Swift protocol. This means you have to create a concrete implementation of a transition for each transition protocol used. The representor now becomes a generic structure with it's defined Transition.
I have implemented a concrete HTTP transition in this pull request, and anyone using other protocols can build their own concrete implementation of their protocol. A transition has a transition builder implementation too (so it can introduce builder methods at the transition level, such as setting a HTTP method in the case of HTTPTransition.
For example, to create a HTTP based Representor:
Representor<HTTPTransition> { builder in
  builder.addTransition("create", "/users") { builder in
    builder.method = "POST"
    builder.contentType = "application/json"
    builder.addAttribute("username")
    builder.addAttribute("first_name")
    builder.addAttribute("last_name")
  }
}

There are also breaking changes to bring the HTTP deserialiser out of the Representor itself, since the Representor is now a generic type. It isn't possible to store static variables on generic types, therefore I had to introduce a new structure called HTTPDeserialization which exposes deserializers and preferredContentTypes to allow the user to customise and add their own deserialisers for HTTP.
In previous versions, it was possible to import just the "Core" structures when using the representor if you didn't require or want the Builder DSL that I created. Unfortunately this is no longer possible and the builder has been moved from an extension to part of the core structures. This is purely due to a bug in the Swift compiler, when mangling method symbols of generic types in structure extensions (took me a while to figure out this bug was only exposed in extensions).
@zdne please review and merge.

@fosrias @smizell I think we should introduce a section on HTTP transitions to the charter. Defining the types of HTTP specific elements. This pull-request has introduced these two elements:

method (the HTTP Method that should be used to make the request)
contentType (the suggested contentType that should be used to make the request)

@smizell The Python Siren adapter should work the same way.

The Python Siren adapter should work the same way.

@kylef I think it might be helpful to go off what Verbose has, as I've already worked through some of these differences. It has an array for request and response types. It also has arrays for several other things, even rels.

@kylef per @smizell  comment – do you want to revisit this or is it good to merge?

@zdne Added suggested content types as an array and I think this is good to merge.

@kylef  please add link to the Trello internal tracking card to every PR (where applicable)

@zdne Do we want to add internal trello cards to OSS projects?

@fosrias per our offline discussion lets not do that (internal tracking cards on OSS project) I will communicate this to @kylef and @pksunkara tomorrow


Synthesis failed for java-containeranalysis

Hello! Autosynth couldn't regenerate java-containeranalysis. :broken_heart:
Here's the output from running synth.py:
under the Apache License, Version 2.0 \(the "License"\); you may not use this file except
 \* in compliance with the License. You may obtain a copy of the License at
 \*
 \* http://www.apache.org/licenses/LICENSE-2.0
 \*
 \* Unless required by applicable law or agreed to in writing, software distributed under the License
 \* is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
 \* or implied. See the License for the specific language governing permissions and limitations under
 \* the License.
 \*/
, maybe replacement is no longer needed?
2020-08-06 03:00:09,986 synthtool [INFO] > Replaced '^package (.*);' in /tmpfs/tmp/tmp8n_q3qcv/google-cloud-devtools-containeranalysis-v1-java/grpc-google-cloud-devtools-containeranalysis-v1-java/src/main/java/com/google/containeranalysis/v1/ContainerAnalysisGrpc.java.
2020-08-06 03:00:10,005 synthtool [INFO] > Running java formatter on 31 files
2020-08-06 03:00:14,048 synthtool [INFO] > Running java formatter on 1 files
2020-08-06 03:00:16,045 synthtool [INFO] > Running java formatter on 7 files
2020-08-06 03:00:17,921 synthtool [INFO] > Replaced 'import com.google.iam.v1.TestIamPermissionsResponse;' in google-cloud-containeranalysis/src/main/java/com/google/cloud/devtools/containeranalysis/v1/ContainerAnalysisClient.java.
2020-08-06 03:00:17,925 synthtool [INFO] > Replaced '(\\s+private final ContainerAnalysisStub stub;.*)' in google-cloud-containeranalysis/src/main/java/com/google/cloud/devtools/containeranalysis/v1/ContainerAnalysisClient.java.
2020-08-06 03:00:17,926 synthtool [INFO] > Running java formatter on 31 files
2020-08-06 03:00:22,193 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
.github/CODEOWNERS
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.github/trusted-contribution.yml
.github/workflows/ci.yaml
.kokoro/build.bat
.kokoro/build.sh
.kokoro/coerce_logs.sh
.kokoro/common.cfg
.kokoro/common.sh
.kokoro/continuous/common.cfg
.kokoro/continuous/dependencies.cfg
.kokoro/continuous/integration.cfg
.kokoro/continuous/java11.cfg
.kokoro/continuous/java7.cfg
.kokoro/continuous/java8-osx.cfg
.kokoro/continuous/java8-win.cfg
.kokoro/continuous/java8.cfg
.kokoro/continuous/lint.cfg
.kokoro/continuous/propose_release.cfg
.kokoro/continuous/samples.cfg
.kokoro/dependencies.sh
.kokoro/linkage-monitor.sh
.kokoro/nightly/common.cfg
.kokoro/nightly/dependencies.cfg
.kokoro/nightly/integration.cfg
.kokoro/nightly/java11.cfg
.kokoro/nightly/java7.cfg
.kokoro/nightly/java8-osx.cfg
.kokoro/nightly/java8-win.cfg
.kokoro/nightly/java8.cfg
.kokoro/nightly/lint.cfg
.kokoro/nightly/samples.cfg
.kokoro/populate-secrets.sh
.kokoro/presubmit/clirr.cfg
.kokoro/presubmit/common.cfg
.kokoro/presubmit/dependencies.cfg
.kokoro/presubmit/integration.cfg
.kokoro/presubmit/java11.cfg
.kokoro/presubmit/java7.cfg
.kokoro/presubmit/java8-osx.cfg
.kokoro/presubmit/java8-win.cfg
.kokoro/presubmit/java8.cfg
.kokoro/presubmit/linkage-monitor.cfg
.kokoro/presubmit/lint.cfg
.kokoro/presubmit/samples.cfg
.kokoro/release/bump_snapshot.cfg
.kokoro/release/common.cfg
.kokoro/release/common.sh
.kokoro/release/drop.cfg
.kokoro/release/drop.sh
.kokoro/release/promote.cfg
.kokoro/release/promote.sh
.kokoro/release/publish_javadoc.cfg
.kokoro/release/publish_javadoc.sh
.kokoro/release/snapshot.cfg
.kokoro/release/snapshot.sh
.kokoro/release/stage.cfg
.kokoro/release/stage.sh
.kokoro/trampoline.sh
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
codecov.yaml
java.header
license-checks.xml
renovate.json
samples/install-without-bom/pom.xml
samples/pom.xml
samples/snapshot/pom.xml
samples/snippets/pom.xml
2020-08-06 03:00:22,354 synthtool [DEBUG] > existing pom file found (samples/pom.xml) - keeping the existing
2020-08-06 03:00:22,354 synthtool [DEBUG] > existing pom file found (samples/snippets/pom.xml) - keeping the existing
2020-08-06 03:00:22,355 synthtool [DEBUG] > existing pom file found (samples/install-without-bom/pom.xml) - keeping the existing
2020-08-06 03:00:22,356 synthtool [DEBUG] > existing pom file found (samples/snapshot/pom.xml) - keeping the existing
2020-08-06 03:00:25,412 synthtool [DEBUG] > Wrote metadata to synth.metadata.
2020-08-06 03:00:25,493 autosynth [INFO] > Changed files:
2020-08-06 03:00:25,494 autosynth [INFO] > M synth.metadata
2020-08-06 03:00:25,494 autosynth [DEBUG] > Running: git log 8f64979cee9b4857650fea6c41543995aab06371 -1 --no-decorate --pretty=%s
2020-08-06 03:00:25,499 autosynth [DEBUG] > Running: git log 8f64979cee9b4857650fea6c41543995aab06371 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2020-08-06 03:00:25,503 autosynth [DEBUG] > Running: git add -A
2020-08-06 03:00:25,510 autosynth [DEBUG] > Running: git status --porcelain
2020-08-06 03:00:25,518 autosynth [DEBUG] > Running: git commit -m docs: recommend installation via pip -e

Closes #691

Co-authored-by: Jeffrey Rennie<EMAIL_ADDRESS>
Source-Author: Bu Sun Kim<EMAIL_ADDRESS>Source-Date: Wed Aug 5 15:23:24 2020 -0700
Source-Repo: googleapis/synthtool
Source-Sha: 8f64979cee9b4857650fea6c41543995aab06371
Source-Link: https://github.com/googleapis/synthtool/commit/8f64979cee9b4857650fea6c41543995aab06371
[autosynth-173 9b94e5f] docs: recommend installation via pip -e
 1 file changed, 6 insertions(+), 6 deletions(-)
2020-08-06 03:00:25,528 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 9b94e5f docs: recommend installation via pip -e
2020-08-06 03:00:25,536 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-08-06 03:00:25,543 autosynth [DEBUG] > Running: git diff HEAD..autosynth-173 -- . :(exclude)synth.metadata
2020-08-06 03:00:25,547 autosynth [DEBUG] > Running: git diff HEAD..autosynth-173 -- synth.metadata
2020-08-06 03:00:25,552 autosynth [DEBUG] > Running: git diff HEAD..autosynth-174 -- . :(exclude)synth.metadata
2020-08-06 03:00:25,557 autosynth [DEBUG] > Running: git diff HEAD autosynth-174
2020-08-06 03:00:25,563 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmp34y0tubb/autosynth-174.patch
2020-08-06 03:00:25,567 autosynth [DEBUG] > Running: git add -A
2020-08-06 03:00:25,574 autosynth [DEBUG] > Running: git status --porcelain
2020-08-06 03:00:25,582 autosynth [DEBUG] > Running: git commit -m cleanup: removes unused kokoro config files

* cleanup: removes unused kokoro config files

Removes unused kokoro files from the java library template. We have
stopped running some of these due to Github quota issues.

* fix:reverts back samples.cfg files

The files presubmit/samples.cfg and nightly/samples.cfg should remain in
the java template repository.

Co-authored-by: Jeffrey Rennie<EMAIL_ADDRESS>
Source-Author: Thiago Nunes<EMAIL_ADDRESS>Source-Date: Thu Aug 6 09:48:58 2020 +1000
Source-Repo: googleapis/synthtool
Source-Sha: 4530cc6ff080ef8aca258c1ec92c4db10a1bbfb4
Source-Link: https://github.com/googleapis/synthtool/commit/4530cc6ff080ef8aca258c1ec92c4db10a1bbfb4
[autosynth af6e806] cleanup: removes unused kokoro config files
 12 files changed, 6 insertions(+), 178 deletions(-)
 delete mode 100644 .kokoro/continuous/dependencies.cfg
 delete mode 100644 .kokoro/continuous/integration.cfg
 delete mode 100644 .kokoro/continuous/java11.cfg
 delete mode 100644 .kokoro/continuous/java7.cfg
 delete mode 100644 .kokoro/continuous/java8-osx.cfg
 delete mode 100644 .kokoro/continuous/java8-win.cfg
 delete mode 100644 .kokoro/continuous/lint.cfg
 delete mode 100644 .kokoro/continuous/propose_release.cfg
 delete mode 100644 .kokoro/continuous/samples.cfg
 delete mode 100644 .kokoro/nightly/dependencies.cfg
 delete mode 100644 .kokoro/nightly/lint.cfg
2020-08-06 03:00:25,593 autosynth [DEBUG] > Running: git log -1 --no-decorate --format=%B
2020-08-06 03:00:25,598 autosynth [DEBUG] > Running: git push --force origin autosynth
remote:
remote: Create a pull request for 'autosynth' on GitHub by visiting:
remote:      https://github.com/googleapis/java-containeranalysis/pull/new/autosynth
remote:
To https://github.com/googleapis/java-containeranalysis.git
 * [new branch]      autosynth -> autosynth
2020-08-06 03:00:29,665 autosynth [DEBUG] > Running: git log -1 --pretty=%b
2020-08-06 03:00:31,830 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 690, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 539, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 670, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 400, in synthesize_loop
    synthesize_inner_loop(fork, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 444, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 273, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


It is not clear whether there is distinction between VS and MSVC compiler

Page says

The /Zo option is enabled by default in Visual Studio when you specify debugging information with /Zi or /Z7

but it is not obvious what is going to happen when MSVC compiler  is used outside of Visual Studio. The way it is phrased now has ambiguous meaning, and can be read either:

/Zo is implied when  /Zi or /Z7 is passed to cl.exe
Visual Studio also passes /Zo to cl.exe when project configuration property has /Zi or /Z7 flag specified.

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

ID: 8454271f-b5ab-1e28-3a5d-8e653f1456a5
Version Independent ID: 57c8dcfb-5089-1f2f-3895-61b6154d0ff6
Content: /Zo (Enhance Optimized Debugging)
Content Source: docs/build/reference/zo-enhance-optimized-debugging.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@redbaron
Thanks for the report. The flag behavior applies to the compiler, not just in the IDE. It would be more accurate to say that /Zo is on by default unless overridden by /Zo- or /ZI.


e2e: remove testsuite BeforeEach and AfterEach

Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

/retest ci/centos/k8s-e2e-external-storage/1.20


JsonSerializer/JsonDeserializer appends a new header (header keys are not unique, and duplicates are allowed).

This is a reference to the answer on StackOverflow.
KStream-KStream inner join throws java.lang.ClassCastException when using JsonSerializer/JsonDeserializer because the types of Kafka messages key/value are encoded in the record headers, but the headers are never cleaned up. Each time the type changes, just a new header is appended (header keys are not unique, and duplicates are allowed).

Hmmm - the type headers are now removed by the deserializer, by default, since Spring for Apache Kafka version 2.2.
You are using 2.2.6 so I don't know how this could happen.
Investigating...

Well, since you provide concrete type information to the deserializers, you don't need type information in the headers. So I disabled it but we still get the same class cast exception.
So, there's something else going on...
Producers...
props.put(JsonSerializer.ADD_TYPE_INFO_HEADERS, false);

Serdes:
public class PersonKeySerde extends Serdes.WrapperSerde<PersonKey> {

	public PersonKeySerde() {
		super(keySerializer(), new JsonDeserializer<>(PersonKey.class));
	}

	private static JsonSerializer<PersonKey> keySerializer() {
		JsonSerializer<PersonKey> ser = new JsonSerializer<>();
		ser.setAddTypeInfo(false);
		return ser;
	}

}

public class PersonSerde extends Serdes.WrapperSerde<Person> {

	public PersonSerde() {
		super(valueSerializer(), new JsonDeserializer<>(Person.class));
	}

	private static JsonSerializer<Person> valueSerializer() {
		JsonSerializer<Person> ser = new JsonSerializer<>();
		ser.setAddTypeInfo(false);
		return ser;
	}

}

public final class SchoolKeySerde extends Serdes.WrapperSerde<SchoolKey> {

	public SchoolKeySerde() {
		super(keySerializer(), new JsonDeserializer<>(SchoolKey.class));
	}

	private static JsonSerializer<SchoolKey> keySerializer() {
		JsonSerializer<SchoolKey> ser = new JsonSerializer<>();
		ser.setAddTypeInfo(false);
		return ser;
	}
}

public class SchoolSerde extends Serdes.WrapperSerde<School> {

	public SchoolSerde() {
		super(valueSerializer(), new JsonDeserializer<>(School.class));
	}

	private static JsonSerializer<School> valueSerializer() {
		JsonSerializer<School> ser = new JsonSerializer<>();
		ser.setAddTypeInfo(false);
		return ser;
	}

}

java.lang.ClassCastException: com.sample.kafkastreamjoin.model.School cannot be cast to com.sample.kafkastreamjoin.model.Person
	at org.apache.kafka.streams.kstream.internals.AbstractStream.lambda$reverseJoiner$0(AbstractStream.java:98) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.kstream.internals.KStreamKStreamJoin$KStreamKStreamJoinProcessor.process(KStreamKStreamJoin.java:94) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorNode.process(ProcessorNode.java:117) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:183) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:162) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:122) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.kstream.internals.KStreamJoinWindow$KStreamJoinWindowProcessor.process(KStreamJoinWindow.java:55) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorNode.process(ProcessorNode.java:117) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:183) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:162) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.ProcessorContextImpl.forward(ProcessorContextImpl.java:122) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.SourceNode.process(SourceNode.java:87) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.StreamTask.process(StreamTask.java:366) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.AssignedStreamsTasks.process(AssignedStreamsTasks.java:199) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.TaskManager.process(TaskManager.java:420) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.StreamThread.runOnce(StreamThread.java:889) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:804) ~[kafka-streams-2.2.1.jar:na]
	at org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:773) ~[kafka-streams-2.2.1.jar:na]

Since I also confirmed that the deserializer was removing the headers, I don't think this problem has anything to do with the headers.

Why 2.2.6? I only see 2.1.5(https://github.com/arslanakhtar61/kafkaStreamJoin/blob/master/pom.xml#L8) and 2.1.0 (https://github.com/arslanakhtar61/kafkaStreamJoin/blob/master/pom.xml#L128) in the pom?
Let me try to disable headers (as you proposed props.put(JsonSerializer.ADD_TYPE_INFO_HEADERS, false);) and investigate...

2.1.5 is the Spring Boot version; it depends on Spring-Kafka 2.2.6.
I am not very familiar with KStreams, but in the debugger, I see it trying to call his (school, person) ->  lambda with
value1 = School{address='Sector F/8'}
value2 = School{address='null'}

i.e. 2 schools.

Setting the config globally to disable the headers is not enough. The application code creates some Serdes manually:

https://github.com/arslanakhtar61/kafkaStreamJoin/blob/master/src/main/java/com/sample/kafkastreamjoin/KafkaStreamJoinApplication.java#L35
https://github.com/arslanakhtar61/kafkaStreamJoin/blob/master/src/main/java/com/sample/kafkastreamjoin/KafkaStreamJoinApplication.java#L48

Those Serdes still write the headers because they are not configured. It's the users responsibility to call configure() before the objects are passed, to disable type information in the headers.

Right - I showed in my comment above how I disabled it there too.

BTW, it's working fine for me now, I must have had some cruft left behind. I deleted all the working topics, changed the application.id, and now...
school_app2= School{address='Sector F/8'}, person_app2= Person{age=12.0}
school_app2= School{address='Sector G/8'}, person_app2= Person{age=12.0}
school_app2= School{address='Sector H/8'}, person_app2= Person{age=12.0}
school_app2= School{address='Sector J/8'}, person_app2= Person{age=12.0}
school_app2= School{address='Sector C/8'}, person_app2= Person{age=12.0}
school_app2= School{address='Sector Z/8'}, person_app2= Person{age=12.0}
school_app2= School{address='Sector S/8'}, person_app2= Person{age=12.0}

I still need to investigate why the header removal didn't help in this scenario - I definitely saw the headers being removed in the debugger.

Nevertheless, thinking about how type information is added to headers, it still seems not perfect to blindly append a new header on write without checking existing headers. An existing header (with the corresponding key) should be removed, or maybe fail with an exception if a duplicate header is detected. It's kinda error prone the way it's implemented now, because the consumer also blindly picks the first header with corresponding key (not checking for duplicates).

Agreed; what's confusing me right now is the first call to a serializer or deserializer is serialize (with an existing header). I don't see how we can get there without calling a deserializer first.
The data is a School so something deserialized it 😕

Never mind; my breakpoint was in a different version :(
Still investigating...

Seems like streams retains an old copy of the headers in some circumstances.
Moved to https://github.com/spring-projects/spring-kafka/issues/1137 .

Seems like streams retains an old copy of the headers in some circumstances.

Yes, all input record headers are preserved since Kafka 2.0 (cf. https://cwiki.apache.org/confluence/display/KAFKA/KIP-244%3A+Add+Record+Header+support+to+Kafka+Streams+Processor+API) and forwarded to all output records that are a result of processing a single input record.
It was a problem in older releases that Kafka Streams stripped all headers on write. Users often want to preserve header information, what was decided to be the new default, making for example simple stream->filter()->output application behavior straightforward. User can still modify (and/or remove) headers manually as part of their business logic.
Thanks for looking into this issue and the quick turn-around time to fix it.

@mjsax Thanks for your analysis on Stack Overflow. There were 2 problems - adding rather than replacing the header(s) and iterating forward instead of using lastHeader(). We're now doing both.


Create scorpio1

HI! Please read the rules on README.md
add files on #additional-assets or additional-materials folder. don't create pull request in main folders/directory.
i will decline this pull request. thx


Load admin boundaries

This implements the basic functionalities required to display the admin boundaries and get info on click.
Screenshot:

I am getting an error in the tests:
TypeError: Cannot read property 'addSource' of undefined
I think it is because the style doesn't have time to load: https://stackoverflow.com/questions/25448553/mapbox-gl-source-addsource-bug, any thoughts?


New backend component to replace JSP component

Add new type of component-for-angular in sample data, replace all JSP includes with this one.
basecmscomponent to extend form simplecmscomponent
1 attribute: selector (string)
Not dependent on #893

we said we can wait until week of 18th but account profile may depend on this

We will use the name "FlexCmsComponent" now.

PR is here: https://stash.hybris.com/projects/C3PO/repos/spacceleratorsamplesaddon/pull-requests/15/overview

After build and initialize, you should be able to see the FlexCmsComponent in e.g. LoginPage

We have 2 forms in the old acc: return customer login and new customer login. In SPA, we only use one. So, we will move one component to another page. But, it is not in the scope of this ticket.


Valid SDX Local Controllers

Created by Luis Marin Vera via monday.com integration. 🎉

Valid SDX Local Controllers (label: epic_registration): The SDX Controller should create authentication keys or filters to allow only registered/valid SDX Local Controllers to join the SDX domain.
Leverage RabbitMQ tools to guarantee that only valid SDX-LC can send and receive information
Encryption of RabbitMQ


Feature request: Add "include" and "exclude" option just like in @vitejs/plugin-react

Unfortunately, this package currently does not support "include" and "exclude" options just like in @vitejs/plugin-react

Hi!
What's the need/use case behind this?

@ArnaudBarre Hey, thanks for the reply. My use case is to exclude test files.
All my test files are under /src/__tests__ folder, using Vitest, and whenever I changed some test file, the dev server will refresh the page. So I want to exclude those files from triggering HMR.

This is not something that can be changed by a plugin. You can use https://vitejs.dev/config/server-options.html#server-watch to ignore test files.
Maybe we should change how files are watched by default, I will discuss this with the team.

@ArnaudBarre Hey, I've tried your suggestion but unfortunately, it won't work. It will disable the HMR for vitest as well.
Usually, we will write vitest config inside vite.config.ts so we don't need to repeat those shared configs like resolve.alias.
The only solution is to create another vitest.config.ts and copy those repeated configs, so server.watch.ignored won't apply to Vitest...
A little bit frustrating...

Technically you could share some config via a third file imported in both. But that's a bit frustrating I agree.
Are you using Tailwind? I think this could be the cause of the fact that test files triggers a refresh

Yeah exactly. I was wondering why it will trigger the refresh... Looking forward to hearing about what's happening under the hood if you have time.

The simple solution is to remove test from Tailwind content.
Here is a plugin I added to a project to solve this issue more globally for an SPA. Maybe this could be fixed in core but not sure we can have an exact list of entry points. You can thanks @liautaud for writing down this nice comment.
    {
      name: "fix-tailwind-page-reload",
      apply: "serve",
      /**
       * Fixes a bug in the interaction between Tailwind and Vite where creating
       * or editing un-imported or type-only TS files would trigger a full reload.
       *
       * In short, the issue is that Tailwind needs to listen to changes in all
       * TS files in development, which it accomplishes in a hacky way by adding
       * an edge between `index.css` and every TS file in the Vite dependency
       * graph–even if the file is otherwise un-imported or contains only types.
       *
       * This lead to a bug in Vite where TS or HTML files imported by no other
       * file were not being treated as entry-points because they were being
       * "implicitly" imported by `index.css`, which was mitigated in vite#3929
       * by treating files as entry-points if they are only being imported by
       * CSS files. Unfortunately, since the Vite dependency graph also contains
       * un-imported and type-only files, these get treated as entry-points too,
       * and so they trigger a full page reload.
       *
       * In our case, though, we know that the only entry-point is `index.tsx`,
       * so we can avoid the issue altogether by hooking into `handleHotUpdate`
       * (see https://vitejs.dev/guide/api-plugin.html#handlehotupdate) and
       * disabling full page reloads for "wrong" entry-points, i.e. files being
       * imported only by CSS files which are not `index.tsx`.
       */
      handleHotUpdate({ file, modules }) {
        if (
          modules.every((m) =>
            [...m.importers].every((i) => i.url.endsWith(".css")),
          ) &&
          !file.endsWith("src/index.tsx")
        ) {
          return [];
        }
      },


Add documentation on --storage-opt

We need to add some documentation on the --storage-opt feature.
I guess it can be heavily inspired from the README.md for now.

Quite a bit of storage-opt documentation has been added over the last months - thank you guys :)

:-)


Looped Panic in Bespin Gambit

During the Panic in the Streets mission, adding a point to the Panic Index results in an infinite loop of Panic events - the first event isn't cleared with the Continue button, meaning the mission cannot progress/be completed.  It just adds another Panic event, then another, etc etc.
It appears to be a bug in how the app registers the Panic actions, and how it's supposed to reset the Panic Index after the action is complete. Rather than reducing the Panic level by one, then continuing, it seems to be reducing the Panic level by one and triggering another action no matter what the new Panic level is.

Yes, there has been a problem with how events were handled in that mission. A fixed version is available, but not implemented in the app yet - it will be fixed in the next update. Until then, you can download it here:
https://github.com/GlowPuff/ImperialCommander2/blob/main/ImperialCommander2/Assets/Resources/SagaMissions/Bespin/BESPIN4.json


Issue 128 - Support for Nested Contexts (impls: log4net, NLog)

Extended ILog with new member for NestedThreadVariablesContext. Added implementations for latest Log4Net and NLog versions.

Thanks for reviewing, Steven.
Re: the whitespace formatting - I agree, and I will wind back the AbstractLogger.cs so that the original indentation is preserved and the diff shows only the significant change.
On a related note, the formatting is a bit of an issue with the original source as a mixture of TABs and SPACEs have been used so the indentation is wildly inconsistent and messes up the layout unless you happen to use whatever TAB setting to match the spaces used (presumably 4?). I tried to revert all occurrences where VS/R# corrected the indentation but obviously missed AbstractLogger, so apologies for that.
Re: versioning - I'm not sure it's a breaking change, per se.  It is an additional property on ILog so the interface is not mutated and (unless I'm missing something obvious!) it is safe to upgrade to without requiring changes to the codebase consuming Common.Logging, as the NoOp impls facilitate the touch-free upgrade.
Given that this is additional functionality rather than a breaking change, as per SemVer rules this would be considered a Minor upgrade so perhaps it could be slated for 3.4.0?
Thoughts welcome.

Looks as if I spoke (and acted) too soon on merging this; I've had to unwind this PR until we can resolve some side-effects of these changes.
In my attempts to add these same changes to the other solutions/projects (e.g., .2010, .2013, .2015, net-20) I've discovered that there seem to be cascading dependencies back down through the earlier logger targets (e.g., Log4Net back to 1.0.9 and NLog back to 1.0) that are apparently broken by this PR.  You should be able to repro this for yourself by opening each of the other solution files and attempting to get them to compile/build against these new changes.
In my quick hacking at the problems in a private branch of my own, I was (eventually) able to get the earlier Log4Net adapter target projects to compile, but then hit a seeming blocker with the earlier NLog implementations where the NLog impl. of the nested thread variables context class makes use of a property on NLogContext that isn't actually available until the later versions of NLog.  I'll try to take some time over the next week or so and attempt other approaches to this, but if you want to take a shot at trying to resolve these issues in the meantime, that would be much appreciated too.
In the interim I've unwound this PR/MERGE to try to return the build status of MASTER to GREEN for the time being.  Probably the most obvious of several ways to resolve this would be to have a different impl. of the NLog nested thread context variables class for the versions of NLog for which the current proposed impl. is incompatible, but there may be other approaches worth exploring as well.
I'm socked in with competing obligations for the next week or two, so if you are able to look into this in the interim that might help expedite being able to get this work integrated faster.
Ultimately, in order to fully integrate this PR (or any, really) into MASTER, the following all need to be able to validate as building/compiling/tests-passing successfully with whatever modifications are necessary to accomplish that state:

Common.Logging.2010.sln
Common.Logging.2010-net20.sln
Common.Logging.2013.sln
Common.Logging.2015.sln
the build-dev.cmd NANT-based build

Thanks again for the contribution, and sorry I had to revert it for the near-term!

Ah, I see the problem now. Apologies for not spotting that. I'd presumed that the different .slns were just for the different versions of VS - I didn't realise they had different project make-ups in each.
I've gone through and add the relevant file links to all projects across those solutions, and I've also created a version of NLogNestedThreadVariablesContext.cs for versions of NLog prior to 4.1, so all should be good now.
As the original PR is closed I've raised a new one (#131) that contains the entire contribution in a single commit, rebased on top of master, so please review when you have the time and let me know if there are any issues or changes you'd like me to make.
I would like to make a suggestion of adding a CONTRIBUTING.md to describe the code setup a bit, so that those who dive straight in (cough) can avoid the same mistakes that I made!


Add log.

Add logging.

Related to https://github.com/bdim404/HackerNews-Summarize-Telegram-Bot/pull/21


Schedule update

Saw that you also had to fix some dates and times - Did you have a chance to update the issue cards too?

Did you have a chance to update the issue cards too?

I did - thanks for checking on that.


"Level UP!" : Block "mySprite say [":)"]" doesn't take effect

Describe the bug
"Level UP!" : Block " mySprite say [":)"] " doesn't take effect
Steps to reproduce the behavior
1.Navigate to https://makecode.com/_iTFaTgbMx2gD
2.Run this program
3.Observe if the mySprite will say "+5 Level-Up Bouns!" when the score gets to 10
Actual behavior
mySprite should say "+5 Level-Up Bouns!" when the score gets to 10

Actual behavior
mySprite doesn't say "+5 Level-Up Bouns!" when the score gets to 10 . It seems that block " mySprite say [":)"] " doesn't take effect.

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.6.24
3.Microsoft MakeCode version: 7.2.25

@Sheila111 what tutorial is this?
Code seems incorrect. Instead of sprite it says mysprite?

The tutorial is "Level UP!" in https://arcade.makecode.com/--skillmap#space . And this tutorial we need the plane to say something so I use mySprite not sprite.

Dupe of #4144


Spacings

Is your feature request related to a problem? Please describe.
Implement and document spacings
Describe the solution you'd like.

[ ] Document spacings and usage in storybook
[ ] Make the spacings accessible through TypeScript and SCSS / CSS

Moved to https://github.com/Energinet-DataHub/MightyDucks/issues/153


Fix image clipping on section pages at mobile size

Fixes #707
Small style tweak fixes this on both related articles and sub sections:

I confirmed that the "completed" overlay still renders properly, which seems to be the primary function of the style I modified:

I did have one question -- There exists a sass file section.scss containing section styles, but it appears that recent changes only update the .css version, so that's what I did here. Is this correct?

Thank you! This looks good to me. @ehmadzubair Feel free to merge if you don't have any further objections.
I believe the sass files were used by the Merix team back when there were working on the project. Since then, the css files have been edited directly, so I assume the sass files are obsolete and can be deleted.


Who is maintaining this addon?

This addon is no longer being maintained by the owner. Recently ember-addopted-addons was given the ability to maintain this addon.
@MelSumner

Is this addon going to be moved to ember-adopted-addons or stay in the miragejs org?
Who in adopted addons is going to be maintaining and releasing this?
There are several PRs that need to get completed due to deprecations.
I am going to cancel all my pending PRs and start over making a few targeted ones to ease the deprecations. Is there someone that can approve these. I have no problem attempting to maintain this, just not very proficient in releasing an addon. Seeing as this is pretty visible, would not like it to be my first :)
There will be a PR that will be a breaking change. We need to remove all the re-exports to make this just responsible for the things it adds. I have not found a way to deprecate the re-exports though, any ideas? At this time I would also suggest removing the old way of creating a server and use just the new way. This new way more closely resembles the documentation in MirageJs proper.

There is a release video in issue https://github.com/miragejs/ember-cli-mirage/issues/2055 I will re-watch this and see if I cant get a release out containing just a couple PRs for my first attempt.

I was unable to do a release. While I have sufficient permissions for this repo, I lack the permissions to push to NPM.

It looks like I and @SergeAstapov are at the moment.

👏🏾  awesome to see traction being made here again @cah-briangantzler and @SergeAstapov


SQLite Blob streaming support

SQLite provides an incremental I/O interface for blobs: https://www.sqlite.org/c3ref/blob_open.html
It would be nice to be able to AsyncRead / AsyncWrite to such blobs from sqlx.

My biggest concern is with the following:

The size of a blob may not be changed by this interface. Use the UPDATE SQL command to change the size of a blob.

AsyncRead makes sense, but I feel like an AsyncWrite interface to a blob would be misleading. It would have to work similarly to impl Write for &mut [u8] which returns Ok(0) at the end of the slice and tends to confuse a lot of APIs or just cause them to emit errors. But it can't grow or shrink the blob, so a truncate mode wouldn't work either.
I think a better AsyncWrite interface would actually bind the write buffer to a statement that appends its contents to the existing blob, but SQLite doesn't have a proper operator to concatenate blobs; you can sorta force || to work but it coerces the blobs to strings before concatenating them and so probably won't work properly for contents that aren't valid Unicode (worth trying out on a modern sqlite3 version though; that forum post is 10 years old).
You could write a custom function to support this properly, but all that can really do is memcpy both halves into a new allocation and return that, so you're still just manipulating the blob's contents in memory before writing it back to disk. It's hard to say whether that would be any more efficient than just SELECTing the existing blob value, appending to it, and doing an UPDATE.

Some prior art (but non-async like the rest of rusqlite): https://docs.rs/rusqlite/0.31.0/rusqlite/blob/index.html
I think of particular interest are the "positional IO API"s Blob::read_at, Blob::write_at, etc., which represent pretty direct calls to the underlying sqlite3_blob_read and sqlite3_blob_write. The std::io::{Read,Write,Sync} impls (or Async{Read,Write,Sync} impls) can be considered an optional layer on top, offering interop with code that works with standard traits, of course with the caveats previously mentioned (cannot grow/shrink).
In general, the sqlite_blob_open API seems geared towards efficient in-place updates of small ranges within large fixed-sized blobs, which is an interesting but perhaps niche usecase.


[JUJU-1690] Update changelog for v0.4.1

What's Changed

JUJU-1686 Include charm config values when reading Juju app status. by @juanmanuel-tirado in https://github.com/juju/terraform-provider-juju/pull/88

LGTM, thanks!


Convert Rails to API only mode

Part of the HM 3.0 redesign project.
Reference: https://guides.rubyonrails.org/api_app.html#changing-an-existing-application
Public Facing:

[x] #667
[x] #668
[x] #669
[x] #670
[x] #672

Manage Section:

[x] #687
[x] #736
[x] #737
[x] #738
[ ] #739
[ ] #834
[x] #740
[x] #741
[x] #742
[x] #743
[x] #744
[x] #745

Other

[x] #747
[ ] #746
[ ] #769
[ ] #825

I added #835 since it appeared to be missing from the list


First time trying this out

Hi, it's my first time trying out an AUR package and I get the same error as your CI
swift-language/src/llvm-project/compiler-rt/lib/tsan/dd/dd_interceptors.cpp:225:20: error: redefinition of 'realpath'

Can you maybe enlighten me as to what's usually the procedure for a fix?

hey cool andre, and you probably chose one of the few which does not build :)
my guess is that if one installs glibc-dev in other linux distros it would fail the same way. in arch the packages are simpler and not split in runtime and dev. so making it work for arch should make it work for others. i reported it here as i hoped an upstream fix would be preferable: https://bugs.swift.org/browse/SR-13082. am trying varun gandhi's suggestions. now hard coded into the build-aur-action: https://github.com/soloturn/build-aur-action/commit/48ca1a38bc69dea9a2320afa183645203f1d5158 .
michael hansen before tried to patch swift, and / or the swift build:
https://aur.archlinux.org/cgit/aur.git/log/?h=swift-language

@andrevidela meanwhile i know the cause.
# By default in /etc/makepkg.conf this is "-D_FORTIFY_SOURCE=2"
# Which will break `compiler-rt`
unset CPPFLAGS

https://aur.archlinux.org/packages/swift-language-git now build and produces a package. could you try it?
i switched the build so that it should produce a package and publish it if it happens to run shorter than 6 hours and does not get cancelled:
https://github.com/soloturn/swift-aur/actions?query=workflow%3A"swift-language-git+ci"


Updated magic-8-ball.py with a magic ball

I added a magic ball that will print the response from computer after it generates a random number.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[TA] Resolve regression tests

Resolved failed live tests due to regressions.

API change check
API changes are not detected in this pull request.

/azp run java -textanalytics - tests


TypeError: Cannot read property 'lastIndexOf' of undefined .. node_modules/typescript.js

✖ TypeError: Cannot read property 'lastIndexOf' of undefined
    at Object.startsWith (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:2025:20)
    at mangleScopedPackageName (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27283:16)
    at mangleScopedPackageNameWithTrace (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27270:23)
    at loadModuleFromImmediateNodeModulesDirectory (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27195:83)
    at /Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27172:39
    at Object.forEachAncestorDirectory (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:12577:26)
    at loadModuleFromNearestNodeModulesDirectoryWorker (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27166:19)
    at loadModuleFromNearestNodeModulesDirectoryTypesScope (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27162:16)
    at tryResolve (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27348:28)
    at classicNameResolver (/Users/YOUR/APP/node_modules/typescript/lib/typescript.js:27324:24)

This issue is just to help anyone searching. It's a duplicate of https://github.com/pahen/madge/issues/211 where lots of people mentioned they have the same issue, but the real canonical issue is here: https://github.com/pahen/madge/issues/157
Basically, you can't have any dynamic import( calls.
Here's a (temporary?) work-around I have suggested:

For now, I'm fine with hand-converting the few imports that I have, stashing that change in git, generating an svg, and when I want to re-generate that svg, I can just git stash pop.
A better solution may be for madge to run a codemod of some sort before doing all of it's main work. Please discuss real solutions on the real issue thread #157 (feel free to discuss work-arounds here)

I guess people are more-likely to visit this thread if the issue is open, since, it's not solved, but I'll leave that to the maintainers to decide.


two solutions

fix for dbLoad on travis (#549)

fix for overlapped expectations (#550)

@gghai , please approve! :)

As we talked about this on the call , I would let both Charles / Daphne reach to the consensus to push this to rc1 branch or not .


My connection is established, but I can't invoke functions

My connection is established, but I can't invoke functions. Surprisingly, the function on my hub did not even trigger (found out by logging every method call on my hub).
I have already tried invoking through a web browser and it's working fine, so I doubt the problem's from my SignalR hub. Would you kindly assist me again?
I am currently using signalR v2.2.1 and SwiftR 0.13.0
How I initialise my connection:
 let connection = SignalR(serverDomain + "/signalR")
connection.useWKWebView = true
connection.signalRVersion = .v2_2_1
How I setup my hub:

I've also tried invoking with the handle response, but it does not seem to be working or returning any feedback:
try(hub.invoke("testConnection", arguments: nil) { (result, error) in
                   print('FEEDBACK! :D')
 })

Good Day
I currently have the same issue has it ever been solved?
Regards

Could you share more code? Is it structured similar to the SwiftR demo app? I'm wondering if you have the hub declared such that it's no longer in scope by the time the connect callback is executed.

Hi thanks for your reply
I have structured it almost 100% like the demo except its all in a class that is created globally as signalR is used throughout the whole application so its done like this so that it runs once when the application has finished loading other values.
What works is I can receive the events for on and signal r stays connected throughout the app i can recieve its posts but the second I Invoke I either get "Error: Object Reference not set to an instance of an object" and then have to click the button 2 or 3 times before the invoke actually goes through.
Do you know anything that could cause this. The signalR implimentation was setup by my companies previous developers with no documentation so I am unsure of what the issue could be. Like I said if I spam the send button it works now and again
Sorry for late reply our time-zones must be different
Regards
Lloyd Hendricks

Actually, Object reference not set to an instance of an object sounds like .NET runtime error, not Swift. If your transport is auto, and becomes WebSockets, remember that SwiftR doesn't support custom headers with WebSockets. It sounds possible that you're getting errors on the server side where headers are expected and not found.

Hi
Thanks for the reply i will contact my API developer and ask him to confirm what the transport type is. What do you recommend using ?
Regards

Hi.
I'm using your library for an iOS app. I have almost the same issue, but I made SignalR to use WebSockets with headers, but just the first time I established the connection with SignalR and I could use invoke to get info from the server without errors. In headers, I send an access token for my server.
After that, I restarted the app and it tried to establish a new connection. Then SignalR tried first ServerSentEvents, which didn't work with authorization.
Next, it tried LongPolling. The authorization was successful but every time I use Invoke I get the same error message: "Object reference not set to an instance of an object."
As you say that SwiftR doesn't support custom headers with WebSockets, how could it work the first time?
And after using WebSockets the first time, why is not using it the next time when I restart the app?
Could we say that LongPolling doesn't work on iOS?
Thank you in advance!

Any solution so far? My connection to Hub is established and I have connectionId as well. But I'm unable to call any server method and get following error everytime. hubConnection
message = "There was an error invoking Hub method 'chathub.updateCustomer'.";

@zahid119  did you find any solution for that. ?

Yes. I accidentally set all my hub functions private. I updated them to public and it worked perfectly.


I got a question about testing

Hi,
Is there any built-in way I can keep the test runner open and see it going?
just like other task runners to run tests such as gulp watch or watchify?
Should I have to write that portion myself to achieve that?
Thank you for the great redux repo!

Hey, check out  npm run test:dev, that should be what you're looking for.
Sent from my iPhone

On Mar 8, 2016, at 2:01 AM, Youngjae Ji<EMAIL_ADDRESS>wrote:
Hi,
Is there any way I can keep the test runner open and see it going?
just like other task runners to run tests such as gulp watch or watchify?
Thank you for the great redux repo!
—
Reply to this email directly or view it on GitHub.

Thank you!
I'll try that
Have a nice week!


gophernotes: init at 0.7.1

Motivation for this change
adding go kernel for jupyterlab/notebook
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Not sure if this is the correct directory to adding jupyterlab kernel?

Result of nixpkgs-review pr 94902 1

1 package built:
- gophernotes

@GrahamcOfBorg  build gophernotes

Result of nixpkgs-review pr 94902 1

1 package built:
- gophernotes

@GrahamcOfBorg build gophernotes

Gentle reminder this is ready to be merged

Try posting that on 'ready to merge' topic on nixos discourse.
On August 27, 2020 4:10:06 AM GMT+03:00, Christopher Ostrouchov<EMAIL_ADDRESS>wrote:

Gentle reminder this is ready to be merged
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/94902#issuecomment-681203396
—
cab

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/211


Uncaught SyntaxError: Invalid or unexpected token

In latest test CSE SDK there is a syntax error that breaks the whole functionality. Link that we use https://test.adyen.com/hpp/cse/js/<OUR CLIENT ID>.shtml, screenshot of source code:

Hi,
My apology for the delay. The issue is being fixed at the moment. Please make sure to always also send a ticket to Adyen support in case you notice this as that channel is monitored more tightly than the github issue list.
Note that the live versions of the CSE SDK was not affected by today's patch and still remains on 0.1.18 and did not suffer from this error.
I will update / close this issue once the merchant test servers are patched.

@ArnoudAdyen unfortunately there is another syntax error:
Uncaught SyntaxError: Unexpected token )

Hi.
Yes. The fix forward failed, so we are rolling back to only offer 0_1_18 on the hosted CSE so we have more time on investigating what is going on with 0_1_19.

Arnoud

Closing this issue for now as the rollback was completed on thursday


Add max completion time to taskInfo (#881)

This cherry-picks #881 onto stable, in order to provide maxCompletionTime to version 2.x
@gkleiman can you please review?

Please note that I had to remove the concurrent field, as it wasn't present on stable.
See errors
[ERROR] /home/fawkes/chronos/src/main/scala/org/apache/mesos/chronos/utils/JobSerializer.scala:130: error: value concurrent is not a member of org.apache.mesos.chronos.scheduler.jobs.BaseJob
[ERROR]     json.writeBoolean(baseJob.concurrent)

[ERROR] /home/fawkes/chronos/src/main/scala/org/apache/mesos/chronos/scheduler/jobs/Jobs.scala:127: error: value concurrent overrides nothing
[ERROR]                              @JsonProperty override val concurrent: Boolean = false,
[ERROR]                                                         ^
[ERROR] /home/fawkes/chronos/src/main/scala/org/apache/mesos/chronos/scheduler/jobs/Jobs.scala:166: error: value concurrent overrides nothing
[ERROR]                                @JsonProperty override val concurrent: Boolean = false,
[ERROR]                                                           ^

LGTM, thank you so muchj!


Add Whatsapp Icon

Description
Add a WhatsApp icon to connect with the admin on WhatsApp
Screenshots
No response
Additional information
No response

@apoorvaron Kindly assign me this issue

@Nishitbaria assigned
Now start solving issues😂

@apoorvaron I have done this one already i was just uploading video

https://github.com/apoorvaron/Shorty/assets/85815172/34d7e252-f599-4aed-a0cc-082196ee704e

@apoorvaron Since its Friday so last working day in my job and very less load so trying to create issue and finding some raw solution then full working from tomorrow

https://github.com/apoorvaron/Shorty/assets/85815172/c4a3c7ff-9f81-462d-85c5-ae6009b4aa65

@apoorvaron Thanks Man


Check for dimension in FireCraftingHandler fallback method

Description
The fallback method for when doFireTick is disabled doesn't check which dimension the tracked fire belongs to, and thus will end up ignoring fires in dimensions other than the overworld, as the blocks obviously won't be found in the wrong dimension and it simply removes the tracker entries. It also breaks with doFireTick enabled when Aether is installed, due to Aether using a wrapped gamerules object to return false for doFireTick in its dimension only.
The fix is very simple, just skip over any non-matching dimension entries when iterating. I tested locally with Aether installed and confirmed it works.
This shouldn't be a breaking change.
Closes #603

Checklist:

[x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you).
[x] I have performed a self-review of my own code.
[x] I have commented my code in areas it may be challenging to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes are ready for review from a contributor.

Yeah this makes sense, seems we missed that code path. It looks fine to merge IMO, or do we wait for 1.20.2 @Rover656 ?

Happy to merge into 20.1 :) I kinda want to squash a few of the bugs left over if I can anyway :p

Thanks a lot for this Techjar!


Log file over 64 GB ??

I just want to ask, as I was wondering that my HDD space has diminished a lot recently when using this app ? -so I ran a few searches, I encountered a really big file under /localdrive/appdata/local/tumblrthree/tumblrthee.log that was over 64 GB ?
Now is this something that gathers something specially important, or how can I stop this from happening, or can please someone explain....what is this for ?

I've never had such a big log file. There must be tons of error messages of failed post downloads inside. A log file helps in finding a problem or errors.
Anyway, you can safely delete it. If you don't like logging, you can change the level in the settings or even switch it off.

Ok thanks...it helped a lot...and switched logging off. Big Thanks !


lidar_situational_graphs: 0.0.1-2 in 'iron/distribution.yaml' [bloom]

Increasing version of package(s) in repository lidar_situational_graphs to 0.0.1-2:

upstream repository: https://github.com/snt-arg/lidar_situational_graphs.git
release repository: https://github.com/ros2-gbp/lidar_situational_graphs-release.git
distro file: iron/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.0.1-1

Holding for Iron sync


Typesafe project accessor make some taks out of date when using included builds

When using typesafe project accessors and included builds, the included build becomes out-of-date depending if called from the root build or from the included build.
You can reproduce with https://github.com/martinbonnin/test-accessors/tree/076ada8ef52bf171972a6f1da997866c3bbb2d64
# Run the included build
./gradlew -p build-logic compileKotlin
# Run the root build, build-logic:compileKotlin will be run again
./gradlew help -i
[ ... ]
Task ':build-logic:compileKotlin' is not up-to-date because:
  Class path of task ':build-logic:compileKotlin' has changed from 5d5d066a31ec578a38e4c520e519ee10 to a0332dec08439c7ee6085c0ee519aec6.

This makes working with included builds cumbersome because they keep doing the same work over and over again.
It looks like this is due to the accessors .class file slightly changing between invocations. Can we make sure that the included build always see the same accessors, even when called from the main build?

Sorry for the late reply.
The issue is in the backlog of the relevant team and is prioritized by them.

@ov7a thanks for the reply. It's been a while and I've definitely lost a lot of context on this issue. It might have been fixed already. I have personally stopped using project accessors and am not impacted by this issue. Feel free to close it and I'll reopen if it becomes too much of an issue again.

@martinbonnin, it's most likely still an issue since not much has been done in this area. Unfortunately, we don't have the capacity to work on that area, but we plan to work on it eventually.

Sounds good! Thanks for the update 🙏


Protocol for batch operations

It may be useful to have an optional protocol (BatchingStore?) that defines methods for reading and writing multiple blocks at once. These would be 'private' methods (similar to -get and -list) and wrapped by a function which checks for the protocol. If the store in question doesn't implement BatchingStore, it would fall back to operating on the blocks one-by-one and returning a collection.

get-batch retrieves blocks identified by a collection of multihash ids, returning a sequence of all the blocks identified which exist in the store.
put-batch! stores a collection of blocks, returning a sequence of stored block versions.
delete-batch! removes blocks identified by a collection of multihash ids.

Done in a0b9832a8d736ed4296bbe7da3ba42766c9e8f95.


Unknown prop warning thrown by ListItem

Problem description
https://github.com/callemall/material-ui/blob/master/src/List/ListItem.js#L710
Here the onTouchTap when passed on to EnhancedButton, which is then passed on to a span, which does not recognise it as a valid prop
Link to minimal working code that reproduces the issue

Versions

Material-UI: 0.16.4
React: 15.4.2
Browser: all

We have been porting the component on the next branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.


Add duration device class for total print time and longest print sensors

This patch adds a device class to the Longest Print and Totals Print Time history sensors, similar to the rest of the existing time-related sensors.
The current implementation casts these sensors to plain text values, which makes it very difficult to try to build any automations on top of these values.
For example, I want to make a reminder every X hours of printing to do maintenance on the printer (lubricate the guides, check belt tension, check for debris in the extruder, and so on).
This could also be useful for people with print farms to more easily keep track of printer wear and tear and to more evenly distribute print jobs.

@saintonotole this is a great patch, can you adjust tests for it

@marcolivierarsenault I've adjusted the tests to match the expected data

inactive, re-open if needed


Matchers missing compound methods

Subject of the issue
I was trying to use rspec expectations' compound feature as in expect().to have_received().and.have_received() (actually for using with .ordered), but the and method is missing from HaveReceived matcher (and i guess from the others too). Including RSpec::Matchers::Composable into the matcher solves the problem (though the error may be somewhat misleading, as for example if the argument expectations fail it still complains about calls out of order).
Your environment

Ruby version: 2.6.4
rspec-mocks version: 3.8.1

Steps to reproduce
Try to chain compound methods onto have_received matcher.
Expected behavior
Should work.
Actual behavior
It raises NoMethodError.

Good catch on have_received/receive not being composable.
Reproduction example with the difference between non-composable and composable expectations:
RSpec.describe 'have_received' do
  class A
    def foo(x)
    end
  end

  subject(:a) { A.new }

  it 'fails with a proper error message' do
    allow(a).to receive(:foo).with(1)
    allow(a).to receive(:foo).with(2)
    # action here
    expect(a).to have_received(:foo).with(1).ordered
    expect(a).to have_received(:foo).with(2).ordered
  end

  it 'fails with a proper error message when chained' do
    allow(a).to receive(:foo).with(1)
    allow(a).to receive(:foo).with(2)
    # action here
    expect(a)
      .to have_received(:foo).with(1).ordered
      .and have_received(:foo).with(2).ordered
  end
end

Depending on the order of the calls in action, e.g.:
0. pass
    a.foo(1)
    a.foo(2)

same

    a.foo(1)
    a.foo(3)
 #      #<A:0x00007fcf272bb918> received :foo with unexpected arguments
 #        expected: (2)
 #             got: (3)
 #       Please stub a default value first if message might be received with other args as well.

same

    a.foo(2)
    a.foo(1)
#        #<A:0x00007ffd7dc89da8> received :foo out of order

different output

    a.foo(1)
#      #<A:0x00007ffaa4a836e8> received :foo with unexpected arguments
#         expected: (2)
#              got: (1)
#
# vs
#
#       #<A:0x00007ffaa3a9e340> received :foo out of order

In order for composability to work,
        include RSpec::Matchers::Composable

should be added to lib/rspec/mocks/matchers/receive.rb and lib/rspec/mocks/matchers/have_received.rb (optionally for receive_messages and receive_message_chain).
One spec in the suite fails, supposedly due to an issued warning.

We'd need to check that the module is defined before including it, as rspec-mocks is standalone from rspec-expectations however we also to fix that error, its occurring because ordered is not being recognised correctly.

@eLod would you like to work on this improvement?

@pirj sure, any pointers, recommendations? i get @JonRowe saying we should check if the module is defined before including it, but not sure about the second part "ordered is not being recognised correctly".

@eLod incorrect message (received :foo with unexpected arguments) is for non-compound variant, so it's a problem that we already have.
Compound expectation does not have this problem, and the failure message is more logical (received :foo out of order).
So I'd say go ahead and add that new feature, while incorrect message should be dealt with separately. Appreciate if you could file a ticket (with an example from case #3 from https://github.com/rspec/rspec-mocks/issues/1298#issuecomment-553799720).

@pirj i started to work on it, but i'm having trouble writing specs or features, getting "only the receive, have_received and receive_messages matchers are supported with allow(...).to, but you have provided: #RSpec::Matchers::BuiltIn::Compound::And:..." (which i can't reproduce in a real project suite) originating from here. Am i supposed to change that .delegate_to and .delegate_not_to functionality or missing some setup/configuration step?

@eLod hm. Can you please push your work in progress? Let's figure it out together.

@pirj see my edit, i was trying to do allow().to receive(:foo).and(receive(:bar)) which is simply not supported, once i've realised that i was able to progress. working on the specs/features now, i will push once it's in an acceptable shape.

@pirj pushed changes, not sure about the shared examples, a bit complex on how the compound expectations is built and verified. also there are examples failing, all because of .or not working as expected (or i am missing something), e.g. not passing when only the second message is received. do you think it should be part of this feature (haven't investigated what is causing the problem)?

i am guessing it is because RSpec::Matchers::BuiltIn::Or.match simply calls matcher_1_matches? || matcher_2_matches? here, so the first receive (or have_received) gets triggered which causes the error.

Closing due to inactivity during the monorepo migration, but if someone wanted to revisit this they'd be welcome.


Loading BreezeJS Angular Bridge

As in #1537 I'm setting up a Breeze-Angular Project with webpack. But I can't get the bridge to work "Can't find breeze". I'm confused what options (noParse, imports loader) I should use for this. I tried different configurations without success.
resolve: {
    root: [path.join(__dirname, "bower_components"), __dirname],
    moduleDirectories: [
      'bower_components',
      'node_modules',
    ],
    alias: {
      'breeze-dataservice-mongo': 'breeze-client/build/adapters/breeze.dataService.mongo',
      'breeze': 'breeze-client/breeze.debug',
      'breeze.angular': 'breeze-client/build/adapters/breeze.bridge.angular',
      'angular': 'angular/angular',

breeze.bridge.angular.js script header
(function (definition) {
    if (typeof breeze === "object") {
        definition(breeze);
// require is not defined .. but exports and module are.. ?!
    } else if (typeof require === "function" && typeof exports === "object" && typeof module === "object") {
        // CommonJS or Node
        var b = require('breeze');
        definition(b);
    } else if (typeof define === "function" && define["amd"] && !window.breeze) {
        // Requirejs / AMD
        define(['breeze'], definition);
    } else {
        throw new Error("Can't find breeze");
    }
}(function (breeze) {
    'use strict';

@samunro Any chance you encountered this? Using an older version from the deprecated breezejs package seems not to change anything.

Migrating from RequireJS and Bower, I finally got it working without the Bower Webpack or any DirectoryDescriptionsFilePlugin. Still confused what those were actually doing. I had to keep the root absolute "bower_components/.." prefix and alias each module.
Also the Breeze Mongo Dataservice needed some special imports to work as expected, I'm also adding this shim as a solution.
// webpack.config.js extract
resolve: {
    root: [__dirname],
    moduleDirectories: ['bower_components', 'node_modules'],
    extensions: ['', '.ts', '.coffee', '.js', '.json', '.css', '.html'],
    alias: {
        'breeze': 'bower_components/breeze-client/breeze.debug',
        'breeze.angular': 'bower_components/breeze-client/build/adapters/breeze.bridge.angular',
        'breeze-directives': 'bower_components/breezejs/labs/breeze.directives',
        'breeze-dataservice-mongo': 'bower_components/breeze-client/build/adapters/breeze.dataService.mongo',
},
loaders: [
        {
          test: /[\/\\]breeze\.dataService\.mongo\.js$/,
          loader: 'imports?this=>window'
        },
        {
          test: /[\/\\]angular\.js$/,
          loader: 'exports?angular'
        },
//...
]


Looking forward to get involved and contribute to the community 🎉

First Name
Trishala
Last Name
Swain
Discord Username (if applicable)
Trishala Swain (She/Her)#1681
Let us understand your motive.
Want to learn, grow & contribute to the community.

Hey @trishala01 👋🏻
Thanks for requesting an invite! Welcome to SidHacks Community 🎉
Before going ahead, I would want you to complete the below To-Do list.
Your To-Do List ✔

Accept the invitation sent to you via mail.
Change the appearance of this organization to "Public" from the people list here.
Join our Discord Server here.

Accept the Rules from #📓〡rules channel.
Introduce yourself to our community in 👋〡introduction channel.

Feel free to share your excitement on socials with #SidHacksCommunity. You can also tag me @siddharth_hacks.

Close this issue once you complete all the above points.

Looking forward to interacting with you in our community! Welcome once again! 🤓


access running program

I need to run a pyautoguy with non elevated rights, and call from it and elevated program. I dont know how to do it. I tought about start the program and give it the elevation, and then run pyautoguy and get focus on that running app, instead of doing app = Application().start .... do somethiing to get focus on that program. Is there a way to do it ?
Im using Windows system.

got it.
Application().connect(title_re=".My app")


Fix speedtest

Timing of GPU kernel calls are not done properly in the current benchmark code.
I also speeded up Chainer by setting max_workspace_size appropriately.
With improvements I made in https://github.com/wkentaro/fcn/pull/90, the benchmark result on my machine (Pascal Titan X) is as follows.
± % ./speedtest.py --times 5

==> Running on GPU: 0 to evaluate 5 times
==> Testing FCN32s with Chainer
Elapsed time: 0.24 [s / 5 evals]
Hz: 20.86 [hz]
==> Testing FCN32s with PyTorch
Elapsed time: 0.29 [s / 5 evals]
Hz: 17.32 [hz]
(general)

Also, could you fix README to report the updated benchmark score?

Nice work, I didn't know so much about nvvp. Thanks!


⚠ SceneTime has degraded performance

In 564470c, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2156 ms

Resolved: SceneTime performance has improved in 1149a08.


On Freecen" search page: Soundex- could name soundex be used on either/or surname and forename- i.e. 2 soundex buttons?

Soundex- could name soundex be used on either/or surname and forename instead of both or none- i.e. 2 soundex buttons?

Soundex only used on Surname (firstname already automatically searches name variants eg Elizabeth finds Betty and Liz), so change label to say Surname search.

Soundex is currently used on both forename and surname.

So can we have 2 buttons? One for first name and one for surname?
R
Sent from my iPhone
On 29 May 2020, at 01:39, Kirk Dawson<EMAIL_ADDRESS>wrote:

CAUTION: External email. Ensure this message is from a trusted source before clicking links/attachments.
Soundex is currently used on both forename and surname.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/FreeUKGen/FreeCENMigration/issues/885#issuecomment-635690623, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO5M7OQH4XVRF6YW5MKPQXLRT372DANCNFSM4M752BNA.
The University of Aberdeen is a charity registered in Scotland, No SC013683.
Tha Oilthigh Obar Dheathain na charthannas clàraichte ann an Alba, Àir. SC013683.

Yes the search could be modified to soundex on surname only or on both surname and forename. A pure soundex search on forename is likely going to add nothing more than is provided with a pure surname search so would not recommend it.
PS Soundex was designed for 'surnames'. All it really does is strip vowels


TURN backup servers not kicking in if TURN API fails.

Today the GEANT TURN API was down for about 30 minutes. In MM when joining a room it waited before timing out and then reloaded a next room. But when I've commented out the TURN API in config.js the backup turn server configuration worked. So there should be some kind of backup mechanism, that if the TRUN API fails, then the backup TURN servers should be used automatically.

API call need to have a short time limit.
https://github.com/havfo/multiparty-meeting/blob/46a2c075f03a7e348ecfbc34ba425cc458f5f3a0/server/lib/Room.js#L501
e.g.
timeout: 3000


Config-based support for custom repository classes

As the PoC of https://github.com/phpstan/phpstan-doctrine/pull/18 seems stalled to resolve custom repository classes based on the mapping, a simpler solution could be implemented in the meantime (even though it is not as good for DX as it requires more work). Instead of configuring a single repository class used by all entities, we could configure a mapping of entity classes to their repositories (the existing option can of course still be kept for the fallback for entities not present in the map):
parameters:
        doctrine:
                customRepositories:
                        MyApp\Entity\User: MyApp\Doctrine\UserRepository
                        MyApp\Entity\Team: MyApp\Doctrine\TeamRepository
                repositoryClass: MyApp\Doctrine\BetterEntityRepository

What do you think about that solution ?

Hi, I'd rather have someone finish the work on #18 rather than investing in something like this. Can you take over the work?


Allow for Thread reuse for CompactIndex fetcher

Overview
One of the main benefits of the Net::HTTP::Persistent library is that it maintains the HTTP connections so that multiple requests to the same host don't need to re-instantiate the http tcp socket to make a request, and also allows this to be done across threads.  But when used with the CompactIndex client, the each iteration of the remaining_gems? loop throws away the Bundle::Worker and initiates new Threads with new connections.
Since the resulting work on these threads only returns to the caller the result, and can be collected cleanly, it is safe to reuse these threads by other repeated gem_name iterations and gain a bit of a performance boost in the process.
While in this code change, we do run @bundle_worker.stop, we could simple skip this now as we will never use more then one Bundle::Worker's worth of threads, keeping around the worker for further calls to .specs on the same fetcher.  That said, this has not been don at this time.
Metrics
This is the result of running the fetcher for fetching gem metadata against the Gemfile for the ManageIQ project (these are sorted collection of results from the quickest times to the slowest times from a collection of benchmarks made over time, and are not in any other order besides that):

No changes
Shared threads, 25 workers
Shared threads, 15 workers

14.780272
4.429732
4.424576

14.987697
4.664379
4.447966

16.161742
7.470335
4.596416

16.698832
8.538736
8.103314

16.973982
10.293958
10.368032

17.044186
12.548805
10.873393

17.401267
13.527048
11.734078

17.417851
13.640801
12.379456

17.611628
13.695791
14.071921

17.702503
13.930277
14.151556

17.926312
14.512490
14.247501

17.953948
14.547216
14.372980

18.116374
14.562247
14.494275

18.193501
15.054224
14.496102

18.278697
16.325938
14.496330

18.313061
16.773398
14.799070

18.561052
17.029987
15.377202

18.657163
17.321094
15.658238

18.661411
17.443478
17.018813

18.739866
17.895521
17.142276

19.008614
18.075015
17.414206

19.174890
18.159239
17.860201

19.235642
18.188842
18.460573

The following changes to the lib/bundler/source/rubygems.rb were used to capture the metrics.
diff --git a/lib/bundler/source/rubygems.rb b/lib/bundler/source/rubygems.rb
index aedad70..2cd637b 100644
--- a/lib/bundler/source/rubygems.rb
+++ b/lib/bundler/source/rubygems.rb
@@ -350,11 +350,17 @@ module Bundler
             " Downloading full index instead..." unless allow_api

           if allow_api
+            require "benchmark"
+            puts Benchmark.measure {
             api_fetchers.each do |f|
               Bundler.ui.info "Fetching gem metadata from #{f.uri}", Bundler.ui.debug?
               idx.use f.specs_with_retry(dependency_names, self)
               Bundler.ui.info "" unless Bundler.ui.debug? # new line now that the dots are over
             end
+            }
+
+            puts; puts; puts "exiting..."
+            exit

And the command used to capture the metrics using this branch:
$ for I in `seq 1 15`; do \
    BUNDLE_DISABLE_POSTIT=1 ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle update; \
  done

Some things to note about this data:

These results are the lowest of the recorded and usable results, not an average
I went with the lowest because is show the range of improvement the best, but I didn't get an even number of usable results, so this was the best way (I found) to share a somewhat unbiased distribution
Usable results were the following

Used the compact_index resolver
Didn't require a retry

Unfortunately, almost half of my results had to be thrown away because they didn't match that criteria

One thing that I also observed while running in debug node and inspecting the threads is the it seems that one or two workers tend take a majority of the requests, while the other workers seem to only process one.  This is why the metrics show a second column where I adjusted the number of workers spawned to 15 (no reflected in this code change), something to also consider.
Tests
Wasn't able to run tests locally when I using the latest version of master (not sure what broke), and unsure how I would test this functionality.  Let me know if this is something you would like to go forward with adding and I will look into adding some tests around it.

Oof. This is a great catch! Thanks for the PR.

No prob.  You and @segiddins have been on the ball with responding to my (cheeky) pull requests the past couple of days, and I appreciate the work you both are putting in.
I do want to emphasize with the metrics that they are a sorted sampling, and in no particular order aside from that.  The "super fast" ones happen, but not all the time, and are definitely dependent on the response times of the rubygems api and how well my wifi card wants to behave with my router...
Hopefully I can figure out what broke with the tests, but they were working just fine when I was running them before 😟

@indirect r?

@segiddins I accidentally pushed the worker count down to 15 after updating that last commit (after doing some testing), and also found out that my internet connection was running at an abysmal 1.8ish Mbs on my lappy for who knows how long (restart fixed it).  So I am going to re-push and add some updated metrics that are much more reasonable and consistent.

New (more reasonable) metrics using the ManangeIQ and OpenProject repos as test beds:
ManageIQ  ( https://github.com/ManageIQ/manageiq )

No changes
Shared threads, 25 workers
Shared threads, 15 workers

1.421065
1.225885
1.235604

1.422998
1.234367
1.285666

1.448543
1.240576
1.294454

1.471257
1.248634
1.308538

1.472592
1.256989
1.308846

1.475861
1.262683
1.311133

1.479348
1.264154
1.315734

1.480403
1.265855
1.318963

1.482468
1.281820
1.322024

1.484387
1.292216
1.324417

1.490546
1.310216
1.325004

1.498497
1.321688
1.328751

1.512019
1.322935
1.334134

1.543380
1.324550
1.344470

1.567356
1.338790
1.349862

1.619723
1.395702
1.362866

OpenProject  ( https://github.com/opf/openproject )

No changes
Shared threads, 25 workers
Shared threads, 15 workers

1.770085
1.331694
1.405903

1.798816
1.335906
1.413870

1.799796
1.345552
1.414583

1.802692
1.407406
1.414614

1.807121
1.408128
1.417509

1.813796
1.409145
1.418434

1.822499
1.422775
1.420102

1.831169
1.425031
1.423495

1.832604
1.434294
1.430579

1.840357
1.435858
1.433573

1.845169
1.440178
1.436723

1.889174
1.441677
1.439732

1.902441
1.444408
1.440461

1.919368
1.444862
1.440594

2.186560
1.466290
1.468714

2.338394
1.467803
1.490589

@homu r+

:pushpin: Commit b4fd57f has been approved by indirect

:hourglass: Testing commit b4fd57f with merge ccf79ff...

:sunny: Test successful - status


Miscellaneous bug fixes

Pull Request Test Coverage Report for Build 3088

19 of 24 (79.17%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 66.058%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

util/thingpedia-client.js
12
17
70.59%

Totals

Change from base Build 3087:
0.03%

Covered Lines:
6893

Relevant Lines:
9797

💛  - Coveralls


Fail on warnings when building releases

This patch removes the forced CI=false which means that the build process will fail on compiler warnings.

@lkiesow As all the warnings on the build are now fixed (thx to #430) I think we can now merge this.