Travis CI builds failing on 'Stage sdist' task with AWX <IP_ADDRESS>

TASK [Stage sdist.] ************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AnsibleFileNotFound: Could not find or access '/opt/awx/dist/awx-<IP_ADDRESS>.tar.gz'
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not find or access '/opt/awx/dist/awx-<IP_ADDRESS>.tar.gz'"}

Example failed build: https://travis-ci.org/geerlingguy/awx-container/builds/338157010

Building locally within a Vagrant VM now...

Can reproduce it locally:
TASK [Stage sdist.] ************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AnsibleFileNotFound: Could not find or access '/opt/awx/dist/awx-<IP_ADDRESS>.tar.gz'
fatal: [awx_container]: FAILED! => {"changed": false, "msg": "Could not find or access '/opt/awx/dist/awx-<IP_ADDRESS>.tar.gz'"}

It looks like it's a problem with using Git 1.8.x which is installed by default on CentOS 7, along with AWX's make process. It ends up creating the file dist/awx-0.0.0.tar.gz instead of a version-specific file. D'oh!
See: https://github.com/ansible/awx/issues/1120
I'll make it install git from source if we're on CentOS / Red Hat 7.

So... that's weird.
This time I got:
TASK [Stage sdist.] ************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AnsibleFileNotFound: Could not find or access '/opt/awx/dist/awx-<IP_ADDRESS>.tar.gz'
fatal: [awx_container]: FAILED! => {"changed": false, "msg": "Could not find or access '/opt/awx/dist/awx-<IP_ADDRESS>.tar.gz'"}

But then looking inside the VM I found:
$ ls /opt/awx/dist
awx-<IP_ADDRESS>.tar.gz

So what is going on with the version numbers?!


docs(api): explain when to use home_after

Overview
while using drop_tip() with home_after=False can speed up protocols, it can also severely impact the volumetric accuracy of the pipette. It's crucial that users understand this before deciding to use home_after=False in their protocols
Changelog

Review requests

I think this deserves a warning admonition, do you?
do folks know what a hard limit it? or should I explain that?

Risk assessment
none: docs only

Closed in favor of #6878


Run CI checks against PRs and block merge on failure

Anyone familiar with GitLab actions know how to do this quickly?

is this maplibre related?

This works already!


Fix generated source causing compilation errors on some platforms

On some dotnet SDKs and platforms, it's possible for an incorrect empty string to be returned by AnalyzerConfigOptions.TryGetValue() instead of a null when the attribute was not found
While it does look to be an upstream bug, a missing class name is also not an acceptable value to begin with as it fails the build. It would be reasonable for us to check for and skip entries expressing empty class names rather than nulls for anyone on dotnet SDKs with with this bug
The SDK/Platform known to be expressing this bug is 7.0.410, Linux x64 This is the current latest running on GitHub Actions for .NET 7.x
As for replicating the bug, it was encountered by adding a resource for the banned API analyzer in the solutions root's Directory.Build.props:
<ItemGroup>
  <GlobalPackageReference Include="Microsoft.CodeAnalysis.BannedApiAnalyzers" Version="3.3.4" />
  <AdditionalFiles Include="$(MSBuildThisFileDirectory)/.meta/BannedSymbols.txt" />
</ItemGroup>

@LiHRaM Hey, just wondering if you're going to do a release containing this fix?

@AshleighAdams Hey, sorry about that! I've published the latest version now, thanks for your patience!

Thank you!


Add scope parameter for RoleDefinition PUT and DELETE requests

Hi @surabhi-pandey, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;


Never print a comment in dcos config show [name]

When an environment variable overrides a config value, that command prints a comment. This causes problems if the consumer is trying to parse the output.
These comments would only get printed when no config name is passed.
Fixes #1104

run linux integration tests


Helper not available inside angular module

If I have a template like

{{_ "foo"}}

{{_ "bar"}}

What dependency do I need to add to make the helper available?

Adding the tap:i18n package should do. Reopen with more details if needed

I can confirm that {{_ "hello"}} doesn't work in any .ng.html file...

Me too, this does not work with angular.. and .ng.html files.

I'm in the same situation.
Is possible to change the helper " _ " with a filter like angular-translate? e.g. {{ "hello" | tapI18n }}
i'm using angular-meteor
Thanks


Noble integer

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Added Noble Integer in Mathematics section in C,C++ and Python.
Checklist

[ ✅] I've read the contribution guidelines.
[✅ ] I've checked the issue list before deciding what to submit.
[ ✅] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Added #2371

Do review this PR @bhav09  @HarshCasper

Could you please review the PR @ankitaggarwal23

I have made all the changes do review @ankitaggarwal23 @HarshCasper

Do approve the changes and merge @HarshCasper


The dimension of vit_clip and vit_imagenet

Hello, I want to ask the input dimension before multi head attention between vit_clip.py and vit_imagenet.py
In vit_clip.py, the input dimension before T-MSA is t (b n) d, but in vit_imagenet.py,  the input dimension before T-MSA is (b n) t d.
And I see the description of the paper, it is (N+1) x T x D.
So I want to ask which one is the correct one?
Thanks a lot.

Hi, they are the same. The difference is that the self-attention implementation is different in CLIP model codes and ViT codes. But they are both doing the self-attention on the T dimension. You may check their implementation details.

OK. Got it. Thanks a lot~


Protobuf update 1.27.0 breaks websocket updates

When I have tried to use the new released protobuf 1.27.0 that broke for me any websocket updates due to I am receiving in the console a lot of [debug] messages like: connected -> reconnected and so on endless loop of this events. Any thought about this issue?

Helo @melanu1991
Unfortunate thing, looks like SwiftProtobuf is a massive release with tons of changes, including breaking behaviour changes.
Addressing in #102, works for me locally. Please check it out – if no objections/suggestions I'll proceed with release.

Thank you so much too! Well done!


Specify scrollable element for scroll behavior

What problem does this feature solve?
The savedPosition prop of scrollBehavior gets its left/top values from the window. This is an issue for pages where the main scrollable area is on another element and not the body. In these cases it will always return (0,0) making it impossible to get the last known scroll position.
What does the proposed API look like?
It would be great to have an optional element or id selector to pass into createRouter which is used in computeScrollPosition to save the scroll position of the specified element.

Duplicate of https://github.com/vuejs/router/issues/1189#issuecomment-961157423


Multiple Buffer Recycling Strategies

Adds more ways to handle buffer recycling
Different pool implementations use different strategies on retaining recyclers for reuse. For example we have:

ThreadLocalPool which uses ThreadLocal to retain at most 1 instance per Thread.
LockFreePool is "unbounded" and retains any number of instances released: in practice, it is at most the highest number of concurrently used instances.
Hybrid does both, it will detect if running on a virtual thread and choose a strategy dynamically.

Feel free to rename stuff


[Bug] Illegal instruction (core dumped) during training on container

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (master) or latest version (3.x).

Task
I have modified the scripts/configs, or I'm working on my own tasks/models/datasets.
Branch
master branch https://github.com/open-mmlab/mmdetection
Environment
'sys.platform': 'linux',
'Python': '3.7.10 (default, Feb 26 2021, 18:47:35) [GCC 7.3.0]',
'CUDA available': True,
'GPU 0': 'NVIDIA RTXA6000-24C',
'CUDA_HOME': '/usr/local/cuda',
'NVCC': 'Cuda compilation tools, release 11.1, V11.1.105',
'GCC': 'gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0',
'PyTorch': '1.9.0',
'PyTorch compiling details': 'PyTorch built with:\n  - GCC 7.3\n  - C++ Version: 201402\n  - Intel(R) oneAPI Math Kernel Library Version 2021.2-Product Build 20210312 for Intel(R) 64 architecture applications\n  - Intel(R) MKL-DNN v2.1.2 (Git Hash 98be7e8afa711dc9b66c8ff3504129cb82013cdb)\n  - OpenMP 201511 (a.k.a. OpenMP 4.5)\n  - NNPACK is enabled\n  - CPU capability usage: NO AVX\n  - CUDA Runtime 11.1\n  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_37,code=compute_37\n  - CuDNN 8.0.5\n  - Magma 2.5.2\n  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.1, CUDNN_VERSION=8.0.5, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.9.0, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, \n',
'TorchVision': '0.10.0',
'OpenCV': '4.6.0',
'MMCV': '1.7.0',
'MMCV Compiler': 'GCC 7.3',
'MMCV CUDA Compiler': '11.1',
'MMDetection': '2.26.0+31c8495'
Reproduces the problem - code sample

Run MMDetection in Docker container (Dockerfile below)
sudo docker exec -it TAGID /bin/sh
python3 'path/to/train.py' 'path/to/faster-rcnn-cfg.py' (train.py as original, cfg as from here)
During/after dataloader-workers running, probably in the training hook

-> model, config etc. unchanged except the dataset-path, batch-size and added jsonfile_prefix in evaluation-dict of config
Reproduces the problem - command or script
python3 'path/to/train.py' 'path/to/faster-rcnn-cfg.py'
Reproduces the problem - error message

Including last line before error itself:

2022-12-05 13:09:59,298 - mmdet - INFO - Checkpoints will be saved to /mmdetection/work_dirs/cfg by HardDiskBackend.
Illegal instruction (core dumped)

Additional information

Expected Result: running training (working on Google Colab with same PyTorch, CUDA etc. version)
Dataset used: custom rgb-images (320x240 pixels) in .png-format
Possible reason: not known, newly configured hardware, OS etc.

Edit: Forgot the dockerfile:
ARG PYTORCH="1.9.0"
ARG CUDA="11.1"
ARG CUDNN="8"

FROM pytorch/pytorch:${PYTORCH}-cuda${CUDA}-cudnn${CUDNN}-devel

# Install updated nvidia GPG keys
RUN apt-key del 7fa2af80
ADD https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-keyring_1.0-1_all.deb .
RUN dpkg -i cuda-keyring_1.0-1_all.deb
RUN rm cuda-keyring_1.0-1_all.deb
RUN rm /etc/apt/sources.list.d/cuda.list
RUN rm /etc/apt/sources.list.d/nvidia-ml.list
RUN apt-get update

ENV TORCH_CUDA_ARCH_LIST="6.0 6.1 7.0+PTX"
ENV TORCH_NVCC_FLAGS="-Xfatbin -compress-all"
ENV CMAKE_PREFIX_PATH="$(dirname $(which conda))/../"

RUN apt-get update && apt-get install -y ffmpeg libsm6 libxext6 git ninja-build libglib2.0-0 libsm6 libxrender-dev libxext6 \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/*

# Install MMCV
RUN pip install --no-cache-dir --upgrade pip wheel setuptools
RUN pip install --no-cache-dir mmcv-full -f https://download.openmmlab.com/mmcv/dist/cu111/torch1.9.0/index.html

# Install MMDetection
RUN conda clean --all
RUN git clone https://github.com/open-mmlab/mmdetection.git /mmdetection
WORKDIR /mmdetection
ENV FORCE_CUDA="1"
RUN pip install --no-cache-dir -r requirements/build.txt
RUN pip install --no-cache-dir -e .

SSE4 (and possibly AVX, too) was missing and needed for PyTorch.
At Module._call_impl() the error was thrown.


Imm from city Lahore country Pakistan do you can add my country sections?

[Enter feedback here
⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking. * So that i can work with your website? I see my country Pakistan is no added to your regional section can you add??

ID: 293f9fb8-bc6a-47ee-dbbe-ec60d9c6cb75
Version Independent ID: a7b41845-3da9-4c3e-8222-d47109e9a746
Content: [Find Microsoft 365 for business support phone numbers by country or region - Microsoft 365 admin] (https://learn.microsoft.com/en-us/microsoft-365/admin/support-contact-info?view=o365-worldwide)
Content Source: [microsoft-365/admin/support-contact-info.md] (https://github.com/MicrosoftDocs/microsoft-365-docs/blob/public/microsoft-365/admin/support-contact-info.md) or can you do the business with me
Service: microsoft-365-business
GitHub Login: @cmcatee-MSFT color
Microsoft Alias: Mcatee

@Assad123ghouri Thank you for your feedback. The details for Pakistan are already added to the document. You can check here- https://learn.microsoft.com/en-us/microsoft-365/admin/support-contact-info?view=o365-worldwide#pakistan
Hope this helps!
Thanks
Sri


Increment Version

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/44190
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.8.3 -m "<description of version>" 04ec87a6f5b6ab0161c35d18b2fa94cb76afdc8b
git push origin v0.8.3


Can a TITAN X run SSN?

Hi!
I want to train your SSN with a TITAN X. But pytorch mentioned that I was out of memory.
How much memory at least for training your model?
Thanks.

See #26


Use Python 3.6+ features

Up until now we have supported Python 3.5, which prevented us from using features introduced in 3.6, such as variable type annotations and f-strings.
pandas-profiling 2.5.0 will drop 3.5 compatibility. We follow the supported versions by pandas itself (3.6-3.8 currently).

See #390


fix: redefine the trait inheritance behavior

title: Redefine and explicitly formalize the trait inheritance behavior

Related issue(s): #505
Related PR(s): #517 (will be deprecated by this PR)
Code Example: https://jsfiddle.net/FannonF/yLsonr57/latest/

The basic issue is that the current defined trait merging behavior would overwrite the target object with the traits.
This might not what you would expect from trait inheritance and potentially limits the usefulness of traits, as they can't be used for inheritance use-cases.
There are three options that are proposed:

A) Do not change the current trait behavior and just describe it and it's limitations (#517)

PRO: No breaking change to the spec. Just clarifications.
CON: The current trait behavior makes inheritance use-cases impossible. It can be used for composition, but needs to be carefully handled so nothing is accidentally overwritten without the creator realizing it.

B) Change the trait behavior of the spec by changing the order of the merging / patching

Proposal: Make the target of where the trait is applied to the "most specific" and not the "least specific", so it is never overwritten.
PRO: Now we support inheritance like use-cases. We still can do composition.
CON: We break the use-case where we explicitly wan't to overwrite the target object.
If we implement this, I see two ways how to go about it

B1) Based on JSON merge patch (as we do already)

Pro: Make use of an existing standard, including existing libraries
Con: The goal and semantics of a merge patch are different than what we want to do with trait inheritance. We are re-using a standard for a different purposes than originally intended.

B2) Based on a generic object deep merge algorithm that we clearly define.

Behaves similar to JSON merge patch, but likely without the null behavior
I'd highly recommend to not merge arrays. Just overwriting is is the simplest solution and keeps the spec simple. While for some use-cases this might be a bit inconvenient, it gives the user full control.
Pro: No "dependency" to another standards or libraries. We can describe the algorithm rather shortly (like RAML) and provide a reference implementation (see my code examples).

Con: This needs to be custom implemented and there might be no existing implementation for your ecosystem.

C) Consider not supporting such traits / inheritance in a future AsyncAPI version (drop feature)

If the goal is to keep the spec itself simple and also the consumer side, we might event want to drop more complicated features
As an alternative, we move such functionality to a pre-processor stage, which the AsyncAPI providers are responsible for themselves. There they can use template languages, traits, inheritance as they like if they implement it on their own to their own expectations. In the simplest case, you can write the spec in YAML, use features like anchors and merge keys, parse and serialize it to a "simple", denormalized YAML / JSON file and be done with it.

In case we go for an option in the "B range", we have to decide:

Change the current behavior of the trait inheritance ?

This would either be a breaking change to the bug or if we stretch it a "bugfix" if we consider the current behavior as unintended (which I think we don't do after discussions with @fmvilas )

Keep the current trait implementation and add a new feature besides of it (as a new property?)

This would further increase the complexity but also the flexibility of the spec
This is a breaking change for consumers and tools, because they now need to support the new inheritance feature or else they would interpret the AsyncAPI docs wrong / incompletely. For AsyncAPI providers, it's a compatible change (the documents do not need to be migrated)

For a detailed description and discussion of the problem, see #505 and its comments.
Related Material / Inspiration

RAML Traits:

Specification: https://github.com/raml-org/raml-spec/blob/master/versions/raml-10/raml-10.md/#algorithm-of-merging-traits-and-methods
They have defined and described their custom trait (merge) algorithm as part of the spec
It looks like a RAML trait does not overwrite the target, though

Open Questions / Problems

Do we consider changing the trait merge behavior or do we want to keep it as it is?
Do we consider changing the merge behavior as a breaking change? How do we go about introducing it to the spec?
Should we stick with the JSON Merge Patch merge behavior?

The semantics and the use-case of JSON Merge Patch is quite different from the trait merge use-case. This may lead to confusions (and it already has)
JSON Merge Patch has a special behavior on merging null values, which may not be useful / expected for trait inheritance

Does this PR require a minor or a major semver version increment?

Don't worry about versioning in the PR. We handle the release process separately.

Should we stick with the JSON Merge Patch merge behavior?

I think we should. Inventing new algorithms will make it harder for tooling implementers. I agree that maybe we can reverse the order in which the merge is applied though. My two cents. Would love to know what others think.

Proposal shared with the wider community:

LinkedIn
Twitter
Slack (need to join first- {invite link](https://www.asyncapi.com/slack-invite))

I am intrigued by the proposal, and if we move forward with a more reference based spec these rules will become increasingly important.  I will admit I'm not smart enough to fully understand the implications though, would it be possible for @Fannon or others to present at a SIG, or another meeting?

@jmenning-solace : Yes, this would benefit much from some explaining. I'd be happy to do that.
When is the next SIG meeting or a good occasion for it?

@Fannon next meeting is next week -> https://github.com/asyncapi/community/issues/51

@Fannon you have listed a bunch of options and ways to solve this, however, as a reader, it is hard to keep track of all the pros and cons. I have a hard time figuring out what this PR is trying to fix, and I guess it comes down to which direction we should take it.
Since you have the knowledge, my suggestion would be that you pick the direction you would like to see AsyncAPI adopt, regardless of breaking change or not. See it as a perfect world, which option would then be best suited?
That way you can focus the PR on one suggestion that highlights the changes it requires, as well as letting others know why you chose it and why not one of the other options.
You can also do it in multiple stages, so you start by Do not change the current trait behavior and just describe it and it's limitations, and then work towards major version change where you suggest the new behavior you would like to see 🙂
I think this issue is definitely something that should be addressed, so thanks for taking the time!

Hi @jonaslagoni,
yes, I see that this PR is hard to understand in its current state.
The problem is, we already discussed where we wanted to go and I wasn't sure if we already had agreement.
In this PR I described the compromise solution that I understood that AsyncAPI found best: Keep using the JSON merge path algorithm, change the order of merging and clearly define the previously undefined aspects.
Only in the code-example I have a second option (not using JSON merge patch, but an own definition of merge algorithm + implementatoin).
There is also one PR that only documents the status quo: https://github.com/asyncapi/spec/pull/517
Best,
Simon

So I've thought about this a bit more in another context.
My last state was that we didn't reach consensus and a decision on how to approach this.
In this PR I've tried to show a compromise solution, chaning the order of inheritance but keeping the JSON Merge Patch behavior. My personal opinion on this has changed even more in the direction that we should not use JSON Merge Patch for defining the merge behavior:

Like already stated, JSON merge patch is written and built for the purpose of patching (e.g. overwriting) the target objects. This has already led to some confusions
If we want to have more trait like or inheritance like behavior, we want to do basically the opposite. Of course, we can inverse the direction how the algorithm is applied, but this requires some inversions in your thinking :)
The JSON Merge patch has the feature of using a special null semantics, used for deleting properties in the target. If we keep this behavior and just apply it on the merged object instead of the target, we would do something that is not common in inheritance concepts. It even violates a well established principle, the Liskov Substitution Principle.

To sum it up: My proposal would be to define our own merge algorithm (It's not that much anyway) in written form and additionally as a reference code example, inkcl. unit tests with example data.
We still need to make up our mind how we interpret and explain the term trait. I understand that you can use traits to implement composition, but to me those are different things. Compositions are not using inheritance at all, they just add multiple aspects to one object and live side by side with each other. What we currently have with traits seems to be more like multi-parent inheritance / an object merge algorithm.

I think we even already have a nice definition which was filed within #108:

Traits are pieces of information that will be merged into the referencing object.

We could extend this definition to:

Traits are pieces of information that will be merged into the referencing object. Using traits reduces the amount of repetitive code within an AsyncAPI document.

So how do we want to proceed with this?
Right now, this PR / issue is in a complicated state, because to me it is not really clear which direction we want to take and how this would be decided.
We've discussed a few options, here are the ones that I find most sensible / realistic.
Fore more detailed description, see the PR description:

Option C) Remove trait feature from AsyncAPI 3 as it introduces too much complexity
Option B) Keep trait feature, but change how it is applied and describe it

Here we need to decide between the two B variants. My personal favorite would be B2, but this PR is following the B1 approach as this seemed to be the preference when we discussed it a while ago.

I can also imagine that with the restructuring of AsyncAPI 3, a few circumstances have changed and new insights have been gained. Maybe that also changes our perspective here ;)

Closing in favour of https://github.com/asyncapi/spec/pull/907


SB-509: npm package generator + npm publish UnitTest [ready]

It's not a constructor, this aproach called Builder pattern :) methods
return ‘this‘ so you can make a chined calls to construct instance you need
28 нояб. 2017 г. 23:25 пользователь "Martin Todorov" <
<EMAIL_ADDRESS>написал:

@carlspring commented on this pull request.
In strongbox-storage/strongbox-storage-layout-providers/
strongbox-storage-npm-layout-provider/src/test/java/org/
carlspring/strongbox/artifact/generator/NpmPackageGenerator.java
https://github.com/strongbox/strongbox/pull/391#discussion_r153545214:

private NpmPackageGenerator()

{

   super();

}

public NpmPackageGenerator of(NpmArtifactCoordinates c)
{

   packageJson.setName(c.getId());

   packageJson.setVersion(c.getVersion());

   this.coordinates = c;

   return this;

}

public NpmPackageGenerator in(Path path)

What is the purpose of this constructor and why is the name in?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/strongbox/strongbox/pull/391#pullrequestreview-79566266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVunQyOQq1h_oQC9UF2X-AxGUVbIf9TAks5s7DPwgaJpZM4QtUZH
.

So you construct npm package OF coordinates IN some base  folder :)
29 нояб. 2017 г. 7:10 пользователь "Serge Bespalov" <
<EMAIL_ADDRESS>написал:

It's not a constructor, this aproach called Builder pattern :) methods
return ‘this‘ so you can make a chined calls to construct instance you need
28 нояб. 2017 г. 23:25 пользователь "Martin Todorov" <
<EMAIL_ADDRESS>написал:

@carlspring commented on this pull request.
In strongbox-storage/strongbox-storage-layout-providers/strongb
ox-storage-npm-layout-provider/src/test/java/org/carlspring/
strongbox/artifact/generator/NpmPackageGenerator.java
https://github.com/strongbox/strongbox/pull/391#discussion_r153545214:

private NpmPackageGenerator()

{

   super();

}

public NpmPackageGenerator of(NpmArtifactCoordinates c)
{

   packageJson.setName(c.getId());

   packageJson.setVersion(c.getVersion());

   this.coordinates = c;

   return this;

}

public NpmPackageGenerator in(Path path)

What is the purpose of this constructor and why is the name in?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/strongbox/strongbox/pull/391#pullrequestreview-79566266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVunQyOQq1h_oQC9UF2X-AxGUVbIf9TAks5s7DPwgaJpZM4QtUZH
.

As always, thank you explaining your reasoning and for the lecture in
programming! :)
On Wed, Nov 29, 2017 at 12:20 AM, Sergey Bespalov<EMAIL_ADDRESS>wrote:

So you construct npm package OF coordinates IN some base folder :)
29 нояб. 2017 г. 7:10 пользователь "Serge Bespalov" <
<EMAIL_ADDRESS>написал:

It's not a constructor, this aproach called Builder pattern :) methods
return ‘this‘ so you can make a chined calls to construct instance you
need
28 нояб. 2017 г. 23:25 пользователь "Martin Todorov" <
<EMAIL_ADDRESS>написал:

@carlspring commented on this pull request.
In strongbox-storage/strongbox-storage-layout-providers/strongb
ox-storage-npm-layout-provider/src/test/java/org/carlspring/
strongbox/artifact/generator/NpmPackageGenerator.java
<https://github.com/strongbox/strongbox/pull/391#discussion_r153545214
:

private NpmPackageGenerator()

{
super();
}

public NpmPackageGenerator of(NpmArtifactCoordinates c)
{
packageJson.setName(c.getId());
packageJson.setVersion(c.getVersion());

this.coordinates = c;

return this;
}

public NpmPackageGenerator in(Path path)

What is the purpose of this constructor and why is the name in?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/strongbox/strongbox/pull/391#
pullrequestreview-79566266>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AVunQyOQq1h_oQC9UF2X-AxGUVbIf9TAks5s7DPwgaJpZM4QtUZH>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/strongbox/strongbox/pull/391#issuecomment-347709776,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXqad_TSNlCbln44LkyTIv-1XpTS8h1ks5s7KNOgaJpZM4QtUZH
.


Mabou/parametrize

For issue #97

I believe the build may be failing due to a preexisting conditional  in the master branch.
Let me confirm, and if so may have you use "admin commit".

@dciborow Could you please approve this? It shortens testing time.


on the map for postalcodes with leading 0 the 0 in some places is omitted

Here's what I did
https://maps.openrouteservice.org/directions?n1=50.780001&n2=12.681398&n3=15&a=50.778047,12.697792,50.784451,12.665863&b=0&c=0&d=100&k1=en-US&k2=km
Here's what I got
on some locations addresses the postalcodes leading 0 is missing
Here's what I was expecting
the postalcode has 5 letters no matter if it starts with 0

I checked the route but couldn't find any missing 0 in one of the points.
Maybe fixed with the recent geocoder update.


Incorrect behavior in watch mode

On removing single (spec) file karma with webpack reports about lot of removed files that doesn't actually been removed.
Here abstract_link_spec.jsx actually been removed:
PhantomJS 1.9.7 (Mac OS X): Executed 299 of 338 (skipped 39) SUCCESS (1.393 secs / 0.923 secs)
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/abstract_link_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/spec_helper.js".
INFO [karma]: Delaying execution, these browsers are not ready: PhantomJS 1.9.7 (Mac OS X)
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/factories/activities.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/factories/activities.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/factories/global_notifications.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/factories/global_notifications.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/factories/users.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/factories/users.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_gallery_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_gallery_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_group_offline_actions_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_group_offline_actions_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_group_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_group_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_groups_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_groups_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_preview_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activities_preview_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_header_properties_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_header_properties_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_header_property_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_header_property_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_header_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_header_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_preview_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/activity_preview_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/app_layout_overlay_page_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/app_layout_overlay_page_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/app_layout_overlay_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/app_layout_overlay_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/app_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/app_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/auth_form_user_notification_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/auth_form_user_notification_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/avatar_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/avatar_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/button_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/button_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/calendar_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/calendar_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/card_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/card_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_actions_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_actions_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_alt_action_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_alt_action_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_loading_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_loading_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_title_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_page_title_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/form_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/global_notification_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/global_notification_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/global_notifications_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/global_notifications_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/input_icon_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/input_icon_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/input_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/input_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/input_special_action_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/input_special_action_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/invitation_page_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/invitation_page_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/landing_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/landing_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/link_inner_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/link_inner_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/link_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/link_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/loading_screen_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/loading_screen_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/logotype_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/logotype_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/mixins/link_element_mixin_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/mixins/link_element_mixin_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/new_project_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/new_project_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/overlay_page_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/overlay_page_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/overlay_page_loading_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/overlay_page_loading_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/page_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/page_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/page_layout_wrapper_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/page_layout_wrapper_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/password_input_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/password_input_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/pending_project_invitation_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/pending_project_invitation_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/profile_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/profile_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/profile_worker_info_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/profile_worker_info_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/progress_line_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/progress_line_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_invitation_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_invitation_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_worker_header_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_worker_header_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_worker_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_worker_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_workers_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/project_workers_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/projects_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/projects_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/quick_stats_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/quick_stats_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/settings_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/settings_layout_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/side_navigation_link_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/side_navigation_link_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/side_navigation_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/side_navigation_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/sign_in_form_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/sign_in_form_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/sign_out_link_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/sign_out_link_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/sign_up_form_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/sign_up_form_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tab_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tab_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tabs_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tabs_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tape_calendar_date_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tape_calendar_date_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tape_calendar_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/tape_calendar_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/textarea_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/textarea_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/timeline_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/timeline_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/top_filter_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/top_filter_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/user_activities_preview_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/components/user_activities_preview_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/mixin_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/mixin_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/request_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/request_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/rrouter_context_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/rrouter_context_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/rrouter_webpack_chunk_context_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/rrouter_webpack_chunk_context_spec.jsx".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/schema_state_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/schema_state_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/schema_validator_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/schema_validator_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/utils_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/lib/utils_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/schemas/sign_up_schema_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/schemas/sign_up_schema_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/schemas/validators/email_validator_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/schemas/validators/email_validator_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/schemas/validators/emails_validator_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/schemas/validators/emails_validator_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/actions_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/actions_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/auth_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/auth_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/global_notifications_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/global_notifications_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/mixins/requests_mixin_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/mixins/requests_mixin_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/projects_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/projects_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/system_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/system_store_spec.js".
INFO [watcher]: Removed file "/Users/koss/src/project-front/spec/stores/user_store_spec.js".
I

+1, I'm having this same issue :(.

Need to know if this is still an issue. For the sake of efficiency, we are starting with current versions and the team can work back from there.
If this is still an issue on a recent version of the loader & it's peerDeps, please respond here so we can get this properly triaged.


Docked state wrong ?

https://forum.iobroker.net/post/296774

I have the same issue heere. Roomba 966 is dockes and state ist false. After the roomba leave the dock state change to true

Thanks for the confirmation. Is it always inverted like that? The value is delivered by the API and seems somehow random to me.

I will pay attention to it the next days and report you

For the last two days, docked state has always been set too 'true', whether it ran or was really on the station.


Fix phpunit filter for tests with and without data provider

https://travis-ci.org/przepompownia/phpunit-filter-example

This totally broke #227, I'll probably submit a new PR to make this work with data providers.


[BUG] CC2652P as router - internal temperature suddenly goes to 65.434

After a few hours of normal operation the internal device temperature goes to 65.534. Firmware 14-01-2022
Attribute report received: present_value=65534.0, status_flags=0, description=C
Other things such as sensors and inputs continue to work ok.
EDIT: Observed that this may be due to the temperature going below zero, thus being negative. Sensor is outside and today the temperature is -3 deg C

Your observation is correct:
65.534 = 0xFFFE = -2 (16 bit signed integer)

@glcos, I've fixed this issue in the latest version.

@ptvoinfo thanks a lot for the update. I will test it soon.


feat(app): update healthcheck results summary design

Overview
Update the ResultsSummary wizard
This will close RAUT-183
In design, the order is Tip Length -> Pipette Offset but Mel requested to align the order with other pages such as the RobotSettings Calibration tab.

Changelog

[ ] break ResultsSummary into a few components to make maintenance easy
[ ] add tests for new components

Review requests

[ ] align with the new design
[ ] test cases cover basic cases

Risk assessment
low

[ ] address feedback from Jethary and Brent


chore(main): release 1.26.35

:robot: I have created a release beep boop
1.26.35 (2023-10-07)
Bug Fixes

remove log (921a8dc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aidanaden/canvas-sync/releases/tag/v1.26.35 :sunflower:


Server crashes on startup if --max-backend-connections value is much lower than the number of databases

EdgeDB Version: 2.0-dev.6597+local
OS Version: WSL 2 Ubuntu 18.04

Steps to Reproduce:

Have an instance with a large number of databases. Bug initally occurred after running edb inittestdb, but it can also be reproduced by creating a number of empty databases, eg:

create database db01;
create database db02;
...
create database db24;
create database db25;

Start server with --max-backend-connections set to a low value:

$ edb server --max-backend-connections=4
INFO 25489 2022-05-18T20:39:42.997 edb.server: starting EdgeDB server 2.0-dev.6597+local, built on 2022-05-18T19:39Z from revision fdba24ad4 (2022-05-18T01:05Z) for x86_64-unknown-linux-gnu
INFO 25489 2022-05-18T20:39:42.997 edb.server: development mode active
INFO 25507 2022-05-18T20:39:43.961 postgres: starting PostgreSQL 14.2 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0, 64-bit
INFO 25507 2022-05-18T20:39:43.964 postgres: listening on Unix socket "/home/james/.local/share/edgedb/_localdev/.s.PGSQL.5432"
INFO 25507 2022-05-18T20:39:44.042 postgres: database system was shut down at 2022-05-18 20:39:40 BST
CRITICAL 25507 2022-05-18T20:39:44.043 postgres: the database system is starting up
INFO 25507 2022-05-18T20:39:44.241 postgres: database system is ready to accept connections
INFO 25489 2022-05-18T20:39:46.338 edb.server: Connection established to backend database: edgedb
INFO 25489 2022-05-18T20:39:46.338 edb.server: Connection established to backend database: db02
INFO 25489 2022-05-18T20:39:46.339 edb.server: Connection established to backend database: db01
===================================== Exception occurred: sorry, too many clients already ======================================
1. edb.server.pgcon.errors.BackendError: sorry, too many clients already

---------------------------------------------------------- Traceback -----------------------------------------------------------
    /home/james/dev/edgedb/edb/server/connpool/pool.py, line 514, in _connect
        > conn = await self._connect_cb(block.dbname)
    /home/james/dev/edgedb/edb/server/server.py, line 344, in _pg_connect
        > rv = await pgcon.connect(
    edb/server/pgcon/pgcon.pyx, line 326, in connect
        > pgcon = await _connect(connargs, dbname, ssl=ssl)
    edb/server/pgcon/pgcon.pyx, line 281, in _connect
        > raise
    edb/server/pgcon/pgcon.pyx, line 277, in edb.server.pgcon.pgcon._connect
        > await pgcon.connect()
    edb/server/pgcon/pgcon.pyx, line 1791, in connect
        > raise er_cls(fields=er_fields)

edb.server.pgcon.errors.BackendError: sorry, too many clients already
ERROR 25489 2022-05-18T20:39:46.595 edb.server: Failed to establish a new connection to backend database: db05
CRITICAL 25507 2022-05-18T20:39:46.597 postgres: sorry, too many clients already
===================================== Exception occurred: sorry, too many clients already ======================================
1. edb.server.pgcon.errors.BackendError: sorry, too many clients already

---------------------------------------------------------- Traceback -----------------------------------------------------------
    /home/james/dev/edgedb/edb/server/connpool/pool.py, line 514, in _connect
        > conn = await self._connect_cb(block.dbname)
    /home/james/dev/edgedb/edb/server/server.py, line 344, in _pg_connect
        > rv = await pgcon.connect(
    edb/server/pgcon/pgcon.pyx, line 326, in connect
        > pgcon = await _connect(connargs, dbname, ssl=ssl)
    edb/server/pgcon/pgcon.pyx, line 281, in _connect
        > raise
    edb/server/pgcon/pgcon.pyx, line 277, in edb.server.pgcon.pgcon._connect
        > await pgcon.connect()
    edb/server/pgcon/pgcon.pyx, line 1791, in connect
        > raise er_cls(fields=er_fields)

edb.server.pgcon.errors.BackendError: sorry, too many clients already
ERROR 25489 2022-05-18T20:39:46.598 edb.server: Failed to establish a new connection to backend database: db05
CRITICAL 25507 2022-05-18T20:39:46.599 postgres: sorry, too many clients already
===================================== Exception occurred: sorry, too many clients already ======================================
1. edb.server.pgcon.errors.BackendError: sorry, too many clients already

---------------------------------------------------------- Traceback -----------------------------------------------------------
    /home/james/dev/edgedb/edb/server/connpool/pool.py, line 514, in _connect
        > conn = await self._connect_cb(block.dbname)
    /home/james/dev/edgedb/edb/server/server.py, line 344, in _pg_connect
        > rv = await pgcon.connect(
    edb/server/pgcon/pgcon.pyx, line 326, in connect
        > pgcon = await _connect(connargs, dbname, ssl=ssl)
    edb/server/pgcon/pgcon.pyx, line 281, in _connect
        > raise
    edb/server/pgcon/pgcon.pyx, line 277, in edb.server.pgcon.pgcon._connect
        > await pgcon.connect()
    edb/server/pgcon/pgcon.pyx, line 1791, in connect
        > raise er_cls(fields=er_fields)

edb.server.pgcon.errors.BackendError: sorry, too many clients already
ERROR 25489 2022-05-18T20:39:46.600 edb.server: Failed to establish a new connection to backend database: db05
CRITICAL 25507 2022-05-18T20:39:46.602 postgres: sorry, too many clients already
CRITICAL 25507 2022-05-18T20:39:46.603 postgres: sorry, too many clients already
===================================== Exception occurred: sorry, too many clients already ======================================
1. edb.server.pgcon.errors.BackendError: sorry, too many clients already

---------------------------------------------------------- Traceback -----------------------------------------------------------
    /home/james/dev/edgedb/edb/server/connpool/pool.py, line 514, in _connect
        > conn = await self._connect_cb(block.dbname)
    /home/james/dev/edgedb/edb/server/server.py, line 344, in _pg_connect
        > rv = await pgcon.connect(
    edb/server/pgcon/pgcon.pyx, line 326, in connect
        > pgcon = await _connect(connargs, dbname, ssl=ssl)
    edb/server/pgcon/pgcon.pyx, line 281, in _connect
        > raise
    edb/server/pgcon/pgcon.pyx, line 277, in edb.server.pgcon.pgcon._connect
        > await pgcon.connect()
    edb/server/pgcon/pgcon.pyx, line 1791, in connect
        > raise er_cls(fields=er_fields)

edb.server.pgcon.errors.BackendError: sorry, too many clients already
ERROR 25489 2022-05-18T20:39:46.603 edb.server: Failed to establish a new connection to backend database: db05
INFO 25507 2022-05-18T20:39:46.618 postgres: received fast shutdown request
INFO 25489 2022-05-18T20:39:47.007 edb.server: Connection transferred in to backend database: db04
INFO 25489 2022-05-18T20:39:47.008 edb.server: Connection transferred in to backend database: db03
INFO 25507 2022-05-18T20:39:47.009 postgres: aborting any active transactions
INFO 25507 2022-05-18T20:39:47.009 postgres: terminating connection due to administrator command
INFO 25507 2022-05-18T20:39:47.009 postgres: terminating connection due to administrator command
INFO 25507 2022-05-18T20:39:47.009 postgres: terminating connection due to administrator command
INFO 25507 2022-05-18T20:39:47.009 postgres: background worker "logical replication launcher" (PID 25515) exited with exit code
1
INFO 25507 2022-05-18T20:39:47.014 postgres: shutting down
INFO 25489 2022-05-18T20:39:47.591 edb.server: Backend connections to database db01: 1 were transferred out in at least the last 1.0 seconds.
INFO 25489 2022-05-18T20:39:47.593 edb.server: Backend connections to database db02: 1 were transferred out in at least the last 1.0 seconds.
INFO 25489 2022-05-18T20:39:47.594 edb.server: Backend connections to database edgedb: 1 were transferred out in at least the last 1.0 seconds.
INFO 25507 2022-05-18T20:39:52.179 postgres: database system is shut down
 Exception occurred: unhandled errors in a TaskGroup; 1 sub errors: (BackendError)
 + BackendError: sorry, too many clients already
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 678, in introspect_db
 |     conn = await self.acquire_pgcon(dbname)
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 534, in acquire_pgcon
 |     conn = await self._pg_pool.acquire(dbname)
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 1126, in acquire
 |     conn = await self._acquire(dbname)
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 1087, in _acquire
 |     return await block.acquire()
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 258, in acquire
 |     await waiter
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 514, in _connect
 |     conn = await self._connect_cb(block.dbname)
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 344, in _pg_connect
 |     rv = await pgcon.connect(
 |   File "edb/server/pgcon/pgcon.pyx", line 326, in connect
 |     pgcon = await _connect(connargs, dbname, ssl=ssl)
 |   File "edb/server/pgcon/pgcon.pyx", line 281, in _connect
 |     raise
 |   File "edb/server/pgcon/pgcon.pyx", line 277, in edb.server.pgcon.pgcon._connect
 |     await pgcon.connect()
 |   File "edb/server/pgcon/pgcon.pyx", line 1791, in connect
 |     raise er_cls(fields=er_fields)

1. edb.common.taskgroup.TaskGroupError: unhandled errors in a TaskGroup; 1 sub errors: (BackendError)
 + BackendError: sorry, too many clients already
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 678, in introspect_db
 |     conn = await self.acquire_pgcon(dbname)
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 534, in acquire_pgcon
 |     conn = await self._pg_pool.acquire(dbname)
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 1126, in acquire
 |     conn = await self._acquire(dbname)
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 1087, in _acquire
 |     return await block.acquire()
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 258, in acquire
 |     await waiter
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 514, in _connect
 |     conn = await self._connect_cb(block.dbname)
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 344, in _pg_connect
 |     rv = await pgcon.connect(
 |   File "edb/server/pgcon/pgcon.pyx", line 326, in connect
 |     pgcon = await _connect(connargs, dbname, ssl=ssl)
 |   File "edb/server/pgcon/pgcon.pyx", line 281, in _connect
 |     raise
 |   File "edb/server/pgcon/pgcon.pyx", line 277, in edb.server.pgcon.pgcon._connect
 |     await pgcon.connect()
 |   File "edb/server/pgcon/pgcon.pyx", line 1791, in connect
 |     raise er_cls(fields=er_fields)

---------------------------------------------------------- Traceback -----------------------------------------------------------
    /home/james/dev/edgedb-dev/bin/edb, line 33, in <module>
        > sys.exit(load_entry_point('edgedb-server', 'console_scripts', 'edb')())
    /home/james/dev/edgedb-dev/lib/python3.10/site-packages/click/core.py, line 829, in __call__
        > return self.main(*args, **kwargs)
    /home/james/dev/edgedb-dev/lib/python3.10/site-packages/click/core.py, line 782, in main
        > rv = self.invoke(ctx)
    /home/james/dev/edgedb-dev/lib/python3.10/site-packages/click/core.py, line 1259, in invoke
        > return _process_result(sub_ctx.command.invoke(sub_ctx))
    /home/james/dev/edgedb-dev/lib/python3.10/site-packages/click/core.py, line 1066, in invoke
        > return ctx.invoke(self.callback, **ctx.params)
    /home/james/dev/edgedb-dev/lib/python3.10/site-packages/click/core.py, line 610, in invoke
        > return callback(*args, **kwargs)
    /home/james/dev/edgedb/edb/tools/edb.py, line 57, in server
        > srv_main.server_main(**kwargs)
    /home/james/dev/edgedb/edb/server/main.py, line 611, in server_main
        > asyncio.run(run_server(server_args))
    /usr/lib/python3.10/asyncio/runners.py, line 44, in run
        > return loop.run_until_complete(main)
    uvloop/loop.pyx, line 1501, in uvloop.loop.Loop.run_until_complete

    /home/james/dev/edgedb/edb/server/main.py, line 535, in run_server
        > await _run_server(
    /home/james/dev/edgedb/edb/server/main.py, line 212, in _run_server
        > await sc.wait_for(ss.init())
    /home/james/dev/edgedb/edb/common/signalctl.py, line 160, in wait_for
        > return fut.result()
    /home/james/dev/edgedb/edb/server/server.py, line 394, in init
        > await self._introspect_dbs()
    /home/james/dev/edgedb/edb/server/server.py, line 774, in _introspect_dbs
        > async with taskgroup.TaskGroup(name='introspect DBs') as g:
    /home/james/dev/edgedb/edb/common/taskgroup.py, line 170, in __aexit__
        > raise me from None

edb.common.taskgroup.TaskGroupError: unhandled errors in a TaskGroup; 1 sub errors: (BackendError)
 + BackendError: sorry, too many clients already
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 678, in introspect_db
 |     conn = await self.acquire_pgcon(dbname)
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 534, in acquire_pgcon
 |     conn = await self._pg_pool.acquire(dbname)
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 1126, in acquire
 |     conn = await self._acquire(dbname)
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 1087, in _acquire
 |     return await block.acquire()
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 258, in acquire
 |     await waiter
 |   File "/home/james/dev/edgedb/edb/server/connpool/pool.py", line 514, in _connect
 |     conn = await self._connect_cb(block.dbname)
 |   File "/home/james/dev/edgedb/edb/server/server.py", line 344, in _pg_connect
 |     rv = await pgcon.connect(
 |   File "edb/server/pgcon/pgcon.pyx", line 326, in connect
 |     pgcon = await _connect(connargs, dbname, ssl=ssl)
 |   File "edb/server/pgcon/pgcon.pyx", line 281, in _connect
 |     raise
 |   File "edb/server/pgcon/pgcon.pyx", line 277, in edb.server.pgcon.pgcon._connect
 |     await pgcon.connect()
 |   File "edb/server/pgcon/pgcon.pyx", line 1791, in connect
 |     raise er_cls(fields=er_fields)

To fix this properly we should make schema introspection lazy (i.e. do it on the first connection to a db)


Footer breaks on small screen sizes

The footer text breaks into a new line on smaller screen sizes because it is too wide. This breaks the layout because the footer uses a fixed height and the text is vertically centered by having a high line height.

 CELTS #34: Footer breaks on small screen sizes


improve docs maintainability

This commit introduces a few doc improvements like:

reduce the duplication between the WebSock @moduledoc and the README, this should improve the docs maintainability or at least reduce some out-of-sync information in the future.
fix some typos
Adds CHANGELOG and README to the ex_doc output
Makes the README the main (a.k.a. index) page for ex_doc

This is great! I'm stealing this approach for bandit and thousand island docs as well. Much nicer than having to repeat yourself between readme and main module.
One comment about a comment then we can merge this.

Caveat here is I very very fequently use go-to definition in my editor to jump within code in the deps/ directory to view docs/spelunk. While this thing helps docs maintainability and works fine for mix docs generated docs, it really harms reading the docs within the code so I am 👎 on this kind of thing – at the cost of some readme dup'd effort.

@chrismccord excellent point!


no audio on iPhone running iOS 9.2

I am using Ionic with this plugin.
The below code works on an iPhone 6 emulator running iOS 9.2 and an actual android device.
But when I run it on a real iPhone 5 running iOS 9.2 there is no audio. Any clue??
Here is my code snippet:
.run(function($ionicPlatform, PushNotificationsService, $rootScope, $ionicConfig, $timeout) {
console.log('app.run');
$ionicPlatform.on("deviceready", function(){
// Hide the accessory bar by default (remove this to show the accessory bar above the keyboard
// for form inputs)
if(window.cordova && window.cordova.plugins.Keyboard) {
cordova.plugins.Keyboard.hideKeyboardAccessoryBar(true);
}
if(window.StatusBar) {
StatusBar.styleDefault();
}
if( window.plugins && window.plugins.NativeAudio ) {

window.plugins.NativeAudio.preloadSimple( 'click', 'audio/driver.mp3',        function(msg){
    console.log('Playig click ...');
    window.plugins.NativeAudio.play('click');
    },
    function(msg){
    console.log( 'error: ' + msg );
    }
    );
}
PushNotificationsService.register();

});

i also no longer have audio on iOS 9.2

MP3's loaded via preloadComplex do play on iOS9.2, files loaded via preloadSimple do not
We've been using this Cordova plugin since ages, and it still works great for Android, but it seems severely broken on iOS9.2.

Same here, is there any solution?


docs: Add user guide for Deactivate your account feature

Automated message from Dropbox CLA bot
@synicalsyntax, it looks like you've already signed the Dropbox CLA. Thanks!

I'm not sure about changing administration.png could you check if it didn't break anything else that used this picture?

Sorry about that, I didn't know there was already another picture with that file name so it looks like I overwrited it. But now that I compare the pictures the two are pretty similar and it doesn't erase anything from the context of the previous file in which it was used, do you still want me to change it?

merged, thanks @synicalsyntax !


Update dependabot.yml

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

Comparison is base (c407eb3) 47.73% compared to head (8bebd5f) 47.73%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master       #5   +/-   ##
=======================================
  Coverage   47.73%   47.73%
=======================================
  Files          13       13
  Lines        2055     2055
=======================================
  Hits          981      981
  Misses        929      929
  Partials      145      145

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


File is missing. Thank you for your answer!

Excuse me, the X_template_add_X.npy in the result2np.py is missing. Can I replace X_edges_add_X.npy with X_template_add_X.npy? Thank you.

Thank you for your interest in GraphEdit!
Sorry, I just saw this issue. I made a mistake, the X_template_add_X.npy in the result2np.py actually is X_edges_add_X.npy. I have corrected it. Thanks!


matrix matmul

Is there any way of computing the matrix inner of a matrix  and a vector, I use the tf.matmul operation and it raised an error :
Shape must be rank 2 but is rank 3 for 'attention_query_1/MatMul' (op: 'MatMul') with input shapes: [?,1000,100], [100].
It seems that the operation does not support broadcasting.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?

I have solved the issue with the help of stack overflow and other experienced engineers. Thanks for your reply.
Yours
Sent from Yomail

Nagging Assignee @rmlarsen: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 31 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 46 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 61 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 76 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 91 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 106 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Automatically closing this out since I understand it to be resolved, but please let me know if I'm mistaken.Thanks!


Stopped working - "Error: Forbidden"

Everything has been working until now, on the 20.04. the library stopped working.
I am using the NPM package using a guest session.
Error:
error - Error: Forbidden     at FetcherService.handleHTTPError (/Users/myapp/node_modules/rettiwt-api/dist/services/util/FetcherService.js:123:19)     at /Users/myapp/node_modules/rettiwt-api/dist/services/util/FetcherService.js:178:123 {   page: '/api/myapp/fetch' }
My code using the library:
  const rettiwt = Rettiwt();  // seems to fail here ?
  const tweetService = rettiwt.tweets;
  const tweetFilter = new TweetFilter({fromUsers: usersToScrapeList, startDate: startOfSearch.toISOString()});
  const tweetBatch: {next: {value: string}, list: Tweet[]} = await tweetService.getTweets(tweetFilter, 18, nextCursor);

This is an issue that has come up just now. I'm working on fixing it.

Okay, I have some news.
First, twitter has blocked access to their advanced search feature for guest users. Therefore no more fetching tweets using the advanced search, without logging in.
Second (and slightly good), there is a way to circumvent this problem by fetching tweets from user's profile page instead of using the advanced search.
I'll be working on the second option.

Amazing

Second (and slightly good), there is a way to circumvent this problem by fetching tweets from user's profile page instead of using the advanced search.
I'll be working on the second option.

That sounds perfect, for my use case at least.


Error packaging project

Hi,
When i tried package my project with command "ionic package release ios" from my Mac, the console show error:
"Uploading app...
Successfully upload (65344f84)
ios release building ...
ERROR PACKAGING PROJECT, PLEASE TRY AGAIN LATER"
..., some solution ??
Thanks.

Hello @KarontePhonegap - we're still in the early stages of developing this. Please hang tight while we finish it up for release. Thanks.

Hi jbavari,
Thanks for your info.
Good work!!

So, if I understood this, I will be able to generate a build for iOS even if I'm using a windows platform? This is just amazing!!! There is a estimate to when this will be available? I really need this ;)

@murilolobato yep - this is correct. We're working hard on it!


Updated depends to use winssl for windows and darwinssl for osx

closes #594
closes #591

I've tested and is working with windows gitian build.
Will test with OSX gitian build once I get hands on a mac.

I've tested this build on OSX 10.14, and currencies won't load, but working on windows, I'm checking to see why.

I've found the reason for the OSX curl not getting the right certs and am working with the curl devs here: https://github.com/curl/curl/issues/4312

Binaries with patched curl:
http://static.codedmaster.com/nstake/navcoin-4.7.0-win32-setup-unsigned.exe
http://static.codedmaster.com/nstake/navcoin-4.7.0-win64-setup-unsigned.exe
http://static.codedmaster.com/nstake/navcoin-4.7.0-osx-unsigned.dmg

tested new build from @mxaddict from this address - http://static.codedmaster.com/nstake/navcoin-4.7.0-osx-unsigned.dmg and I was able to confirm that the price I was having (no prices or amounts showing when choosing any currency after USD in the drop down list) has been resolved. Attached image is proof that I can now see amounts in a different currency (i.e. NZD) when looking at the Transactions section of the core wallet.

Tested on 64bit Windows 10 virtual box. I don't have balance (and am not synced) on the VM though. Should i see (or not see) something in the logs if it's working correctly?

I ran the wallet successfully on;

64bit Windows 10 virtual box.
32bit Windows 8.1 virtual box.
MacOS High Sierra on a Mac mini.

I don't have balance (and am not fully synced yet) so not sure how to tell if it's working? I can switch currencies in the drop down and I don't see any errors appear on the Debug Window > Error Log. Should i see (or not see) something in the logs if it's working correctly?

There should be entries in the debug.log that state a successful price update should look like this: [INFO] Updated prices

Can confirm i see the info logs in Windows64 and MacOS. Turns out the Windows 8.1 box i thought was 32bit was actually 64bit. Is it enough to run the 32bit version in 64bit OS?

Can confirm i see the info logs in Windows64 running the 32bit binary.


Mention Phlex in README.md

Apparently Phlex actually has recent maintenance activity.
We should probably say something stronger in the README but the least we can do is mention Phlex's existence.

Thanks for this. ❤


use ensure_packages

I'm wondering if the test shouldn't be something like should contain_ensure_packages(['bind']), but that doesn't work.

No, I think this is exactly correct.  Because ensure_packages is a parser function, it's evaluated during catalog compilation so the catalog that rspec-puppet is testing simply contains a package resource.  There's no evidence in the catalog that it used ensure_packages.

perfect, my job is done here ;)

Merged, thanks @mmoll.  I upped the dep on stdlib to 2.6 which introduced the function.


fix: askRequire don't work

I recommend edit the commit message to fix: ... didn't work instead of fix: ... don't work.
But the fix is correct, so I approved it.

allright, I will fix it.

I recommend edit the commit message to fix: ... didn't work instead of fix: ... don't work.
But the fix is correct, so I approved it.

I will fix it then.

I'm sorry for my error that I only edit the name of pr and ignored the pr name isn't linked with commit message.
Because of Github Mobile, I got this mistake.
I will rebase those errors tomorrow, but it may cost many times because I need to reassign tags.


Pass grid search params to TensorFlowEstimator custom model

GridSearchCV is a great way to test and optimize hyper-parameters automatically. I use it with TensorFlowEstimator to optimize learning_rate, batch_size, ...etc. It would be a great addition if I can also use it to customize other parameters in my custom model.
For example, say I have a custom model with a convnet and I want to optimize the stride value. This pseudo code explains what I'm trying to achieve.
I used a custom "params" input to the model function just as an example, not to imply that this is necessarily the right way to implement this feature.
# My custom model.
# Feature request: New params dict with values filled by GridSearchCV
def cnn_model(X, Y, params):
  stride = params['stride']
  ... custom model definition here ...

# Create the Convnet classifier
cnn_classifier = learn.TensorFlowEstimator(model_fn=cnn_model)

# Grid search on different stride values.
parameters = {'stride': [1, 2, 3],}
grid_searcher = GridSearchCV(cnn_classifier, parameters)
grid_searcher.fit(X, Y)

It's on our TODO list. Just trying to figure out how to do it nicely to have a general way to pass hyper-parameters into the models.

@ilblackdragon Any update on this?

Model function has params argument. TensorFlowEstimator is deprecated, please use Estimator that takes params argument. This should work now, please re-open if this doesn't.


Should azure core add InstrumentationPolicy by default whenever azure core httpclient is used

We have a customer who used azure core http client and tracing failed to work.
The workaround was to add HttpPolicyProviders.addAfterRetryPolicies(policies) to their azure core HttpClient instance.
Then it started working as expected.
public static void addAfterRetryPolicies(List<HttpPipelinePolicy> policies) {
        policies.add(new InstrumentationPolicy());
        addPolices(policies, AFTER_PROVIDER);
}

Should azure-core handled this automatically? or have a doc somewhere along with azure core HttpClient emphasizing the fact that InstrumentationPolicy is mandatory in order for the instrumentation to work.

Context:

original HTTP client instrumentation is suppressed in presence of Azure HttpClient
when a plain client without instrumentation policy is used it suppresses the original client, but does not add instrumentation
we can't add instrumentation policy by default because we don't know where and logging policy has to be after it

Solutions:

short-term: change how suppression works - needs to react to context set by isntr policy
long term: get rid of instrumentation policy alltogether and rely on underlying client instrumentation. Need changes in otel spec.

I'm going to implement

short-term: change how suppression works - needs to react to context set by instr policy

Azure-core will need to coordinate with OpenTelemetry agent and change how HTTP suppression works so that we can turn off SDK instrumentation, but keep underlying HTTP spans coming from OTel agent coming.
Targeting the next azure-core release in early November


Added release notes for Azure Spring Boot

Hi @samvaity  In order to let users know about the latest version of Spring modules, I have added the versions in "Installation Instructions" section. While considering that Spring packages are not suitable for placing together with other services because when users import Spring, they don't need to import SDK packages, thus I put Spring packages independently from others. Do you thinks it can work?


TF2.11 Release Estimate?

Click to expand!
Issue Type
Others
Source
source
Tensorflow Version
TF2.11
Custom Code
No
OS Platform and Distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Noticed that there has been activity on the TF2.11 branch for release, and wanted to inquire if there was an ETA on this particular release, or a timeline on when we should expect another RC for TF2.11?

Standalone code to reproduce the issue
N/A

Relevant log output
No response

Hi @ohadkatz !
That is a good question actually.
Could you post it on TF forum too.
Thank you!


Feature/hive-support

Will merge after live notebook test with dogfood env if possible.

Oh man... this is so cool looking.


use express router pattern

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3d96bc2). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master      #33   +/-   ##
=========================================
  Coverage          ?   96.77%
=========================================
  Files             ?        1
  Lines             ?       62
  Branches          ?        0
=========================================
  Hits              ?       60
  Misses            ?        2
  Partials          ?        0

Impacted Files
Coverage Δ

source/index.js
96.77% <100%> (ø)

Continue to review full report at Codecov.

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


Attach active terminal doesn't work with screen on a remote server

Hey guys.
I'm connecting with ssh to a remote server. The extension works perfectly if I 'create R terminal' - I can plots just fine with httpgd, the attached R session updates in the status bar etc.. However I"d like to be able to log back into a pre-existing screen session and attach to one of the R sessions I've left runnning overnight or whatever.
I've followed the instructions in advanced usage, so I am running the init-R script, Sys.getenv('TERM_PROGRAM') gives 'vscode', and I can execute .vsc.attach() in the screen session. However this doesn't update the R session attached to vscode - the status bar doesn't change and I can't receive plots. This is kind of inconsistently the case - usually if I start a fresh screen session and open R there it works - but of course this then kind of defeats the purpose of screen. Clearly there's something not getting updated, but e.g. running .First.sys() again doesn't work. Any ideas?
(oh and thank you for writing an incredibly useful tool!)
My Machine: 12.6 (21G115)
remote machine: Linux comp-01-dd5 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Vscode version: Version: 1.74.0 (Universal)

Hi zlastman! I've been trying many times to reattach to a remote R session running on a screen.
After a long session of noobie trial and error, I found that attaching to a screen running the Radian terminal, instead
of the default one, works. All the environment variables are also automatically loaded.
Let me know if it works for you!
As a feature suggestion, I think it would be incredible to be able to attach to a remote R session through ssh
tunnelling, in a similar way to how you connect to a jupyter server through vscode. In this way you would just need a conda environment with the R kernel, instead of a vscode server with all the extensions installed remotely. Unfortunately I lack the coding skills and knowledge to formulate a solution.
Thanks for this amazing extension, now I'm almost able to completely replace Rstudio and work remotely without the need to use Rstudio server + Rstudio pro.


HDFS-16708. RBF: Support transmit state id from client in router.

https://issues.apache.org/jira/browse/HDFS-16708

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
buf
0m  0s

buf was not available.

+0 :ok:
buf
0m  0s

buf was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 13 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 21s

trunk passed

+1 :green_heart:
compile
23m  7s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
20m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 33s

trunk passed

+1 :green_heart:
mvnsite
7m 45s

trunk passed

+1 :green_heart:
javadoc
6m 32s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
6m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
12m 31s

trunk passed

+1 :green_heart:
shadedclient
22m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 25s

the patch passed

+1 :green_heart:
compile
25m 23s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
cc
25m 23s

the patch passed

-1 :x:
javac
25m 23s
/results-compile-javac-root-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
root-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 1 new + 2850 unchanged - 0 fixed = 2851 total (was 2850)

+1 :green_heart:
compile
20m 59s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
cc
20m 59s

the patch passed

-1 :x:
javac
20m 59s
/results-compile-javac-root-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
root-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 1 new + 2645 unchanged - 0 fixed = 2646 total (was 2645)

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

-0 :warning:
checkstyle
4m 26s
/results-checkstyle-root.txt
root: The patch generated 25 new + 697 unchanged - 1 fixed = 722 total (was 698)

+1 :green_heart:
mvnsite
7m 47s

the patch passed

-1 :x:
javadoc
1m 39s
/results-javadoc-javadoc-hadoop-common-project_hadoop-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-common-project_hadoop-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
javadoc
6m 53s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
spotbugs
2m 17s
/new-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.html
hadoop-hdfs-project/hadoop-hdfs-rbf generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
shadedclient
22m 58s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 49s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m 17s

hadoop-hdfs-client in the patch passed.

-1 :x:
unit
245m  9s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

-1 :x:
unit
30m 54s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch passed.

-1 :x:
asflicense
1m 44s
/results-asflicense.txt
The patch generated 2 ASF License warnings.

563m 38s

Reason
Tests

SpotBugs
module:hadoop-hdfs-project/hadoop-hdfs-rbf

Possible null pointer dereference of ConnectionManager.alignmentContexts in org.apache.hadoop.hdfs.server.federation.router.ConnectionManager.getConnection(UserGroupInformation, String, Class, String)  Dereferenced at ConnectionManager.java:ConnectionManager.alignmentContexts in org.apache.hadoop.hdfs.server.federation.router.ConnectionManager.getConnection(UserGroupInformation, String, Class, String)  Dereferenced at ConnectionManager.java:[line 228]

Failed junit tests
hadoop.hdfs.server.namenode.ha.TestMultiObserverNode

hadoop.hdfs.TestRollingUpgrade

hadoop.tools.TestHdfsConfigFields

hadoop.hdfs.server.federation.router.TestRBFConfigFields

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4666/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4666

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets cc buflint bufcompat xmllint

uname
Linux 662ae96c9a33 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b3d99b90195da0401ce838ee638fe5632628b492

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4666/1/testReport/

Max. process+thread count
3239 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-rbf U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4666/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.