Release version 0.2.6 not available https://github.com/stoplightio/api-spec-converter/releases

I am not able to find released version for 0.2.6 in https://github.com/stoplightio/api-spec-converter/releases, however we see the same version available in npm.

+1

This is confusing, everywhere latest version 0.2.6 but in releases it shows latest version is 0.1.16. Could you please check and update in the releases.

Hi guys, we will build and put the zip in the releases list. However, note that if this is urgent you can always do an "npm i api-spec-transformer" and then take the folder that is added. Or you can clone this repository and just run the build command to get the built release.
That said, will get the release on that list soon :).

In fact, I forgot. If you look at the release zip, it's just the repository files zipped... so you guys can download the repository code and it's the same thing.

Hi Marc, Thanks for the updates. In case i need the source code for for different versions i would could get the same from the tagged releases (Current latest tagged release is 0.1.16) and i am also expecting to see 0.2.6 in tagged released as it is already released.
I master branch is see 0.2.6 as well. should'nt this be pointing to the next version of the software?


[Question] Big file support

Does it supports an big file to be splitted into chunks between peers?

There's nothing out of the box for this, but it's technically possible. A contribution for this feature would be very welcome.

Well, since december 2017, ZeroNet haves it implemented. Hope to get it on Dat, then it will receive better multimedia apps

I'm not sure why splitting chunks is necessary for using Dat for multimedia. You can already serve videos and audio through a hyperdrive.

I'm pretty sure dat splits files into chunks and those chunks can be downloaded from multiple peers

I interpreted this as sharding between peers so that a single peer doesn't need to hold all the data for a large file. Which is possible to do, but there's nothing that does it automatically.
Streaming files in chinks has been supported for a while.

Yes this is possible with hyperdrive but an app would have to be built to manage that. each node could request a different block range


add python to dependabot's duties

Is this the correct way to add python package version updating to dependabot's duties?

https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#pip-and-pip-compile seems to indicate that yes it is.
I'm not quite sure how this handles >= constraints or HD_BET @ https://.... For these we may need to set allow or versioning-strategy options in the dependabot config.


Bad amount of spaces in error reporting for NAME CLASH

Quick Summary: fn arg {arg} = arg has the first red squiggle in a wrong place
SSCCE
https://ellie-app.com/7vMDwMWwSFna1
fn arg {arg} = arg

Elm: 0.19.1
Browser: non-applicable
Operating System: Linux 64bit

Additional Details
When I found the bug, the red squiggles were not at the beginning of the next line but ~65k chars away (!), which suggests some underflow. It is a private code and I wasn't able to make a SSCCE for this particular underflow yet. I can give it another try if you'll want it.
The code looked something like this:
config =
  foo
    { some = 1
    , fields = 2
    , thisOne =
        \currentSize { currentBasesCount, currentSize, totalLimit } ->
            ...
    }

Another way to trigger this:
case ( foo1, foo2 ) of
    ( Start bar, End bar ) -> -- these two `bar`s throw Elm compiler off
        baz


Create a database accessor for safe access across threads.

This change makes it possible to pass an SqliteCppDb to a thread. A new connection will be created not just in the constructor but also in any member function in case it doesn't exist in this thread.

Codecov Report
Base: 77.00% // Head: 77.51% // Increases project coverage by +0.50% :tada:

Coverage data is based on head (7b03953) compared to base (4bac5bf).
Patch coverage: 94.44% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   77.00%   77.51%   +0.50%
==========================================
  Files          22       23       +1
  Lines         535      556      +21
==========================================
+ Hits          412      431      +19
- Misses        123      125       +2

Impacted Files
Coverage Δ

src/db/sqlite_cpp_db/DatabaseAccessPoint.cpp
81.81% <81.81%> (ø)

src/db/sqlite_cpp_db/SqliteCppDb.cpp
100.00% <100.00%> (ø)

src/db/sqlite_cpp_db/SqliteCppDb.h
100.00% <100.00%> (ø)

test/db/sqlite_cpp_db/SqliteCppDb.test.cpp
97.87% <100.00%> (+1.09%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


yarn install error

os: os x 10.10.4
node: 6.6.0
yarn: 0.16.1
Error:
$ concurrently "install-app-deps" "node node_modules/fbjs-scripts/node/check-dev-engines.js package.json"
[0] Installing app dependencies for arch x64 to /Users/FTAndy/Project/gs-robot/gs-dagger-electron/app
[0]
[1] node node_modules/fbjs-scripts/node/check-dev-engines.js package.json exited with code 0
[0] Error: /usr/local/Cellar/node/6.6.0/bin/node exited with code 1
[0] Error output:
[0]
[0]   error: unknown option `--cache-min

See https://github.com/electron-userland/electron-builder/issues/861

This is a yarn specific issue. I will close this and update the readme to reflect yarn's instability.


Expose command to Obsidian

Can the two buttons please be exposed to Obsidian so that we can add them to menus like Editing Toolbar"?
https://github.com/cumany/obsidian-editing-toolbar
The second little menu seems to always be in the way. It would be great to have this integrated.

Thank you for your advice. I will try to realize your needs, which may take some time 🤟

Can the two buttons please be exposed to Obsidian so that we can add them to menus like Editing Toolbar"?
https://github.com/cumany/obsidian-editing-toolbar
The second little menu seems to always be in the way. It would be great to have this integrated.

The latest version 1.5.0 exposes two commands to Obsidian, You can associate these commands


Mike/7277 content audit csv bulk results upload

FRONTEND PULL REQUEST
Related Issue

Resolves #7277

Changes Proposed

Updates copy to the proposed changes

Testing

Deployed on dev6

Screenshots / Demos
Bulk results upload guide header

Comment field description copy

@kenieh I pushed these copy changes up to dev6, let me know when you get a chance to give design signoff on this

@tomi is currently taking a look! she was the one that made the suggestions of changes for this page.

@mpbrown just reviewed the changes - design signoff granted.


Fix nested routes children wrong path problem

Hi paulgv,
Sorry, I haven’t done enough test for the previous PR.
The new PR have fixed the Nested Routes problem completely.

Thanks @MengWeiChen !
I never used nested routes in Nuxt and don't have any test case but I'll try and write some tests specifically for this. Merging this in the meantime!


Moving all Generics into generics.R after merging branches

As pointed in the answer to @I-Bouros 's stackoverflow question, duplicated declarations of generics are not allowed in R. To avoid ambiguity structurally, after merging the model branches we can

move all generics declarations (setGeneric.(..)) into generics.R,
add #' @include generics.R to the front of each model R file, and setMethod can be used as usual.

An extra step might be documenting all shared generics into the same .Rd file in man (e.g. generics.Rd), while keeping class-specific generics in their class-specific Rd files.

We also need to change the documentation of the generics function so they apply to all models. Currently the documentation for the generics refers to the basic SEIRD model specifically.

Merged by #37


[Bug] Infinite gray modal loading on staging/prod - working locally

Bug Report
Describe the bug
I'm using the CloudinaryUploadButton and have no issues in using it locally. Now I made a build of my NextJs app and put it on Staging (secure url). Whenever I click on the button, I get a gray modal which loads indefinetly. No errors in the console or network tab.
Expected behaviour
To simply open and work ;)
CodeSandbox or Live Example of Bug
This is my component
import { Button } from '@mui/material';
import { CldUploadWidget } from 'next-cloudinary'

interface CloudinaryUploadButtonProps {
  onUpload: (result: any, widget: any) => void;
}

const CloudinaryUploadButton = ({ onUpload }: CloudinaryUploadButtonProps) => {
  return (
    <CldUploadWidget uploadPreset="..." onUpload={onUpload}>
      {({ open }) => {
        function handleOnClick(e: any) {
          e.preventDefault();
          open();
        }
        return (
          <Button onClick={handleOnClick}>
            Upload an Image
          </Button>
        );
      }}
    </CldUploadWidget>
  )
}

export default CloudinaryUploadButton;

Screenshot or Video Recording

Your environment

OS:
Node version: Dockerimage node:18-alpine
Browser name and version: Chrome Version 111.0.5563.64
next-cloudinary: "^4.0.0"

Okay it seemed there was an underlying issue. The problem is that you need to take the NEXT_PUBLIC_ variables into account when using pipelines as they are only set during build time. As my cloudname was undefined, it got stuck. It would have saved me some time if there was an error message :)

Id be happy to add one but could you elaborate a little bit? Is it because it wasn't available in the CI?


Docs change from yesterday (12-5-19) broke link to useTable

In the API doc (https://github.com/tannerlinsley/react-table/blob/master/docs/api/README.md) the link to useTable returns a 404

Fixed


Not support IPV6 address.

redis-cli support IPV6 address.
rdb-cli Not Support。

sorry,forgot pic.

hi @zwfha-oss,
I'll make an effort to incorporate this support when time allows.
If you're inspired to contribute code, please feel free to do so. Appreciate it!


fix rare occurence of new window not being tiled

SLSCopySpacesForWindows can return an empty array even though a window is created on a space in certain situations, leading to window_space(window) returning 0.
This was most noticable when creating a new alacritty window with alacritty msg create-window and happened 1/10 times.

I've also noticed similar behavior with Zoom, which has a tendency to unexpectedly open a new window when a meeting begins after sitting in a waiting room.

Fixed in: https://github.com/koekeishiya/yabai/commit/5cb55e398ede077d08344f25b9c71f8ccc0b2df2


Cover docs/docs_src/ scripts by tests

There are a lot of tests to write

@Lancetnik did you fix this last week?

There are a little bit more

You can watch by current coverage with coverage budge link: https://smokeshow.helpmanual.io/321e0k6u5d3d5n6e3g50/


How to generate GraphQLQueryRequest

I added:
<generateClientApiV2>true</generateClientApiV2>
and now I do see generated files:
WebhookSubscriptionDeleteGraphQLQuery.java
WebhookSubscriptionDeleteProjectionRoot.java
but I am not finding GraphQLQueryRequest:

To fix this add this to your pom.xml:
<dependency>
              <groupId>com.netflix.graphql.dgs.codegen</groupId>
              <artifactId>graphql-dgs-codegen-shared-core</artifactId>
              <version>7.0.3</version>
</dependency>
The docs indicate it will be automatically added - but that is not the case.


Support more ServiceContract method signatures

According to the last protobuf-net.Grpc documentation you can use following signatures for unary call with code first approach:

Task<MultiplyResult> MultiplyAsync()
Task<MultiplyResult> MultiplyAsync(MultiplyRequest request)
Task<MultiplyResult> MultiplyAsync(MultiplyRequest request, CallContext context)
Task<MultiplyResult> MultiplyAsync(MultiplyRequest request, CancellationToken cancellationToken)

First is for Empty request.
Last option could be useful

If you wish to allow optional cancellation in a general purpose way, and do not require access to headers/trailers/etc

It would be great to handle all theese options in grpc-browser. Now first and last are filtred at Index page.

Thanks for highlighting this, I will look to add support for these methods in the next version.

Hi @Gotcha7770, this should be resolved now as of version 1.3.3

Hi @thomaswormald, awsome! Thank you!


examples/dll-app-and-vendor

(supersedes https://github.com/webpack/webpack/pull/4746)
🆕📘 added dll-example with a minimal multi-config setup (as suggested by @simon04 here)
related:

https://github.com/webpack/webpack/issues/4748 (updates existing dll example readme)
https://github.com/webpack/webpack.js.org/pull/1121 (dll documentation)

From https://github.com/webpack/webpack/pull/4746#issuecomment-295241754:

How does the dll-app-and-vendor example relate to the already existing explicit-vendor-chunk example?

@simon04 that was a typo in the first pr readme. https://github.com/webpack/webpack/pull/4746/files#diff-1c0f522a61adc59307209c8e0296db49R57

@sokra @simon04 any tips for dealing with the integration tests for examples?

@sokra
https://github.com/webpack/webpack/pull/4749#issuecomment-295480467
https://github.com/webpack/webpack/pull/4749#discussion_r112375736

You could allow subfolders in the examples:
examples/dll-app-and-vendor/app/webpack.config.js
examples/dll-app-and-vendor/vendor/webpack.config.js
But you need to update the integration test to capture these files.

@sokra perfect! I will see about doing that tomorrow. Thanks :-)

@sokra does this setup work for you? I put them into the folders initially, then since tests had to be updated anyway, added the ability to use a test.js.

@sokra ping

Let me stress my https://github.com/webpack/webpack/pull/4749#issuecomment-295428900 again: This example mostly duplicates https://github.com/webpack/webpack/tree/master/examples/explicit-vendor-chunk without any real value added. Plus, this PR (again) contains 54 changed files.

@simon04 ah yes I seemed to have updated all examples again... there is real added value, this is exactly the example you specifically asked for - just hard to see it with all of the changed files.
the example is here https://github.com/aretecode/webpack/tree/3a6f6f27b9af9acd47d3f3fb53d6b0f912f1b0d2/examples/dll-app-and-vendor
the main thing is the testing is good as mentioned here https://github.com/webpack/webpack/pull/4749#issuecomment-296434848
I redid the test running for examples here https://github.com/aretecode/webpack/commit/5d4bcb68fa0275b0975ea12252885ccff0f853d0 which runs here https://github.com/aretecode/webpack/blob/3a6f6f27b9af9acd47d3f3fb53d6b0f912f1b0d2/examples/dll-app-and-vendor/test.js

@simon04 @sokra so if that way of doing testing for examples is good, then I can polish it up, and finish the other example.

see #5388


Split multibyte class names from Marshal fixtures into their own file

This removes the dependency on module_eval. It does use the magic comment to force the file encoding, but that one is present in the main fixture as well.

Yeah, makes sense. Thank you!

The only concern I have is that a file in the fixtures directory requires another sibling file. I would place the new file into a subdirectory. Actually the spec/ruby/core/marshal/fixtures/marshal_data.rb file's content is what usually stored in classes.rb files (in <class>Spec module).


SyntaxError in Python 3.11 when unpacking sequences inside of []

Ruff version: 0.0.237
Python version: 3.11.1
Command run:
ruff check --isolated code.py

Contents of code.py:
my_dict = {}
my_dict[*"ab"] = 1

This is valid Python 3.11 code, with the string 'ab' being unpacked into a tuple, resulting the in they key with tuple ('a','b') being assigned a value of 1. The above invocation of ruff however throws this error:
E999 SyntaxError: invalid syntax. Got unexpected token '*'

The snippet itself doesn't work in Python 3.9 or 3.10 (throwing SyntaxErrors), so this seems like a syntax enhancement in 3.11 that should be supported. That said, I can't find where this is documented as a change in 3.11. All I can see is this reference to Starred unpacking expressions can now be used in for statements. , which references this CPython issue, but that looks to be a different context for using *, and was only documenting behaviour that changed in 3.9.

Oh just occurred to me, would this be better submitted to the RustPython project?

Oh interesting! Yes, I think this would be at-home on RustPython. Do you mind filing there?

Done: https://github.com/RustPython/RustPython/issues/4479
As I mention in that issue, I wonder if it's related to the new except* syntax that was introduced in 3.11 for ExceptionGroups. The change I picked up on above doesn't seem to be documented, whereas except* is - maybe it's a side-effect of the change.

Ok so it turns out this is an expected change in 3.11, but it wasn't called out in the changelog. See the section Change 1: Star Expressions in Indexes in PEP 646, which was accepted for 3.11.

The parser parts are resolved
https://github.com/RustPython/RustPython/pull/4531
https://github.com/RustPython/RustPython/pull/4532

@charliermarsh, I'm still getting an error when trying to annotate *args as a type variable tuple:
def f(*args: *tuple[int]) -> None: ...

error: Failed to parse file.py: invalid syntax. Got unexpected token '*' at line 1 column 14
file.py:1:15: E999 SyntaxError: invalid syntax. Got unexpected token '*'

Although, this is a valid syntax according to PEP 646, and it passes static type checking using Pyright.
ruff 0.0.252

Moreover, Ruff seems not to support exception groups.
print(ExceptionGroup)

file.py:1:7: F821 Undefined name `ExceptionGroup`

Should I create a separate issue for this?

Thanks @LeeeeT, can you file a separate issue for the *tuple thing? (I had no idea that was allowed, I guess it's only allowed after specifically after a starred positional argument like that in a function definition?)

@LeeeeT - Nevermind, I filed as https://github.com/charliermarsh/ruff/issues/3170. ExceptionGroup was fixed via #3167.

Thank you for fixing it so quickly! ❤


In read-only view, the 'Save Group' button should be disabled

User shouldn't be able to create a new group when it's read-only.

Those buttons are now gone, e.g. open this link https://graphomics.glasgowcompbio.org/app/linker/explore_data/6 in private mode.


Add option to add ALLOW FILTERING to the update query

Previously it was only possible to use AllowFiltering() on the select query builder.
This PR adds the option to add ALLOW FILTERING to the update query.
Fixes: #288

@dkropachev should different types of queries also have this option?

@dkropachev should different types of queries also have this option?

yes, select as well

@dkropachev  select already has it

@dkropachev select already has it, any other?

Then it is all good


misc(libs/header/p2p): allow server to return all stored headers that correspond to the requested range

Overview
Allow the server to return a partial range if it's not ready(not synced to the requested height yet) to return the full one.
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates

Codecov Report

Merging #1807 (9f681bb) into main (e48ffd5) will increase coverage by 0.27%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1807      +/-   ##
==========================================
+ Coverage   57.11%   57.39%   +0.27%
==========================================
  Files         242      242
  Lines       16189    16210      +21
==========================================
+ Hits         9247     9304      +57
+ Misses       5988     5959      -29
+ Partials      954      947       -7

Impacted Files
Coverage Δ

libs/header/p2p/server.go
78.14% <100.00%> (+8.02%)
:arrow_up:

libs/header/p2p/session.go
90.64% <100.00%> (+8.39%)
:arrow_up:

share/ipld/get.go
93.38% <0.00%> (+1.23%)
:arrow_up:

core/listener.go
51.42% <0.00%> (+4.28%)
:arrow_up:

libs/header/mocks/store.go
73.68% <0.00%> (+5.26%)
:arrow_up:

libs/header/p2p/helpers.go
78.26% <0.00%> (+5.79%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This PR is not misc


Installation with Plug ?

I'm still using https://github.com/junegunn/vim-plug/.
Do you know how to install live-command.nvim with that ?
It would be great having this info in the README. I think it is using packer.nvim in your installation instructions but I'm not sure about that.

You should be able to install it as follows from your init.vim:
Plug 'smjonas/live-command.nvim'
lua << EOF
require("live-command").setup {
  -- ... put your commands here (see readme)
}
EOF

Notice that I called the setup function directly from Vimscript. Alternatively, you can also call it from a separate Lua file (e.g. with a init.lua).

Can you add this exact command to your readme for other users ?
I really like this plugin !

Yes I could do that :) Glad you like the plugin!


Refactor address structure using polymorphism

Refactored address class structure to use polymorphism and differentiate between empty and non-empty address

Closes #97

LGTM


Art: Nighttime Cubemap for Homespace

We need a simple cubemap for the Homespace scene.
It should be a nighttime cubemap, night sky with faraway stars.

cube.zip
^ Example cubemaps for formatting

Initial cubemap created: https://drive.google.com/drive/folders/11xp4F9svFCIiAyG4w89IPmMG4XFevSHM?usp=sharing
We have the .blend file as well, and can adjust it as needed

here is a basic night time scene,
night_time.zip


Thrust functions are undocumented

These two modules are entirely undocumented:

https://github.com/poliastro/poliastro/tree/master/src/poliastro/twobody/thrust/
https://github.com/poliastro/poliastro/tree/master/src/poliastro/core/thrust/

How could I not notice this? It's my Master thesis work after all :cry:
(coming from #964)

Closed in #1000


Explore the usage of GATK's ReadsDataSource instead of custom data source

After exploring a bit code of ReadsDataSource, it looks like it is suitable for our purpose instead of the current implementation. This will simplify our code but requires a lot of refactoring:

ReadsDataSource seems to interleave the files, and thus it is suitable for processing the data for pair-ends using the InterleavedGATKReadPairedIterator and removed the rest of the code regarding this. If we find that this is not the case, we should use two ReadsDataSource instead, but always with just one file.
ReadsDataSource open the files with a SamReaderFactory. We should make our custom factory to provide a reader from FASTQ and other data sources. This will simplify the code because we only need to have a SamReader implementation for each read source (e.g. FASTQ) and the rest will be handled by the GATK's implementation.

This will also have the benefit of being able to use methods from SAMRecord instead of GATKRead. The putative problems that we should explore are:

Merged header seems like returning always coordinate sorted, which is not true. This is something that should be fixed at the GATK's level to provide a real sort order derived from the inputs.
Internally, the ReadsDataSource could change the use of the SamReaderFactory, so we require a safe design of all this engine.
We should cover a huge variety of test cases for assess that nothing will break if they change the implementation.

Merged header from GATK is already fixed by a PR
The internal usage of SAMReaderFactory is a blocker: htsjdk v3 should have a more consistent implementation and extensible (currently is not)
Test cases are not a blocker because all the tools have good coverage


Set-ConsoleColors.ps1 should update Windows Terminal colors

Support for adding/updating/choosing the schemes in $env:LocalAppData\Microsoft\Windows Terminal\profiles.json would be nice.

The Terminal settings handles colors nicely.


Files Not Saving

Hey, I'm on a Mac running macOS Big Sur – version 11.6.4 (20G417). I'm using VS Code as my text editor.
Clicking the save button does not actually change the file but the changes are saved in Copilot, even if I close Copilot, set the theme directory, and edit the same file—I see my changes but it's not changing the actual file (looking at it in VS Code and Finder). Thoughts?

Never mind: I set my Theme Directory to the root of my project, which contains a src and dist folder. Copilot is loading the fields.json files from both of the folders and I was editing the wrong one.

Got it -- yea I recommend setting the theme directory to the root theme directory.


Fix instances of incorrect if(ENV{...}) usage and ENV{PKG_CONFIG_PATH} not being reset

I was experimenting with vcpkg in a way that required setting the environment variable PKG_CONFIG_PATH, but I was getting errors in vcpkg. As it turns out, there is a mistake in a few locations where the variable isn't tested correctly. if(ENV{PKG_CONFIG_PATH}) does not work (at least on my setup, macOS 10.14), and always results in the condition being evaluated as false/OFF. This is fixed by changing it to if(DEFINED ENV{PKG_CONFIG_PATH}). Performing a grep for if(ENV{ found one other instance, so I fixed that too.
While looking into this, I noticed that while (almost) all instances of modifying ENV{PKG_CONFIG_PATH} was setting a variable of the form BACKUP_ENV_PKG_CONFIG_PATH_*, not all of them were using it. Based on the variable's name, I assume this is a mistake and corrected all the instances of it (for this specific environment variable). This resulted in touching a few ports that used the environment variable. I'm not sure if it's appropriate to increment the Port-Version in this case (as it's more of a tooling update even in the ports), but I went ahead and incremented them, as that seems to be the protocol for this.

cc @Neumann-A for review this PR because he is the pkgconfig author.

we should define some helper macros for this kind of environment stuff

I could use some clarification/direction for this. I see the tag "requires author response" was added. I'm assuming this means you want me to attempt turning the handling of ENV{PKG_CONFIG_PATH} into a macro(s). I can see this being reasonable to do with two macros (one to set the value, and one to revert it), and it can even be generalized to handle any ENV variable containing a list of paths (eg. ENV{PATH}).
@Neumann-A I haven't done much with macros in CMake. Are you talking about specifically using macro(), or would using function() be better here? Where exactly would I put this macro in the project? Would it be another .cmake file in scripts/cmake, or should it be added to an existing file somewhere? Also less pressingly, what would the naming convention be for these sorts of macros? I'm not sure I've seen anything like what you're talking about in the project already, so I don't have any references to go off of.

Ok, I spent some time looking into the build error that CI found. I was able to confirm the build errors in my VM. After a lot of investigating, I finally figured out the source. As it turns out, one of the typos that this fixed resulted in a latent bug appearing. In vcpkg_configure_make.cmake, it is using the line to setup pkg-config a specific way (i.e. with a specific prefix):
set(ENV{PKG_CONFIG} "${PKGCONFIG} --define-variable=prefix=${_VCPKG_INSTALLED}${PATH_SUFFIX_${_buildtype}}")

This definition of the environment variable is never reset, which results in subsequent steps being affected by this line. This wasn't an issue before because vcpkg_find_acquire_program.cmake was incorrectly checking for the existence of this environment variable and was ignoring it. When I fixed the check in vcpkg_find_acquire_program.cmake, its behavior was being changed by calling vcpkg_configure_make() beforehand.
vcpkg_configure_make.cmake isn't the only file that's changing ENV{PKG_CONFIG}. Most notably, pretty much all the vcpkg_configure_* functions affect it. This means that fixing this properly will require updating quite a few files, so this is probably another good use case for a macro.

@Neumann-A Do you have anyother questions?

@JackBoosY No not really we should introduce something like vcpkg_internal_(set|prepend|append)_and_backup_env(envvar valuetoset config), vcpkg_internal_restore_env(envvar config) and vcpkg_internal_check_env_restored()

Ok, a few quick comments / responses @Neumann-A
What exactly would vcpkg_internal_check_env_restored() be doing and what would its goal be. Is the idea that it checks if previously called functions / build scripts changed the ENV variables without reverting them? If so, wouldn't it need to be two functions, one to establish what the ENV variables should be and the other to check them?
The (set|prepend|append) set makes sense, but may not be entirely descriptive enough. The prepending that's going on here is specifically path-list prepending. There's behavior specific to path-lists going on, namely adding VCPKG_HOST_PATH_SEPARATOR between the added and existing values, but only when the existing value is non-empty. I was thinking the functions could be vcpkg_internal_set_and_backup_env and vcpkg_internal_prepend_path_and_backup_env. Appending could be added if there's any cases of it being used (which I haven't seen so far), and simple non-list prepending could be done with just set, as in vcpkg_internal_set_and_backup_env(VAR "prefix $ENV{VAR}" config).
Speaking of path-lists, there are a few instances with ENV{PKG_CONFIG_PATH} in particular where it's prepending multiple paths at once. Since they need to be separated by VCPKG_HOST_PATH_SEPARATOR, this makes the code for it fairly lengthy and hard to read. I was thinking it would be nice if the prepend_path function could take a list of paths to prepend and handle adding the separators itself. (this would require the path arguments to not be last, so it would be called like vcpkg_internal_prepend_path_and_backup_env(VAR config path1 path2 ...)). If it's a function, it would require converting from the CMake list separator (';') to the paths separator, which could cause issues if paths contain semicolons (though that's already a messy thing to be doing on Linux and macOS anyways). I think it should be possible to avoid this problem with a macro from what I understand, but I haven't worked with macros enough to know for sure.
Looking at the cases I found for this, I'm not sure how necessary the config argument is. There aren't any instances of the ENV variables being set in a nested context (from what I saw), and the current usage of this sort of config was setting it either to DEBUG or RELEASE, which doesn't really help in the case where called functions are affecting the ENV variable. Perhaps this should be removed or instead replaced with an automatic value that will result in less name collisions (such as the script filename if that's a thing that can be done).
Lastly, should these macros be strictly internal? This PR already found two instances in ports where the macros would be useful, and there's likely more for other ENV variables. It might be nice to allow the functions to be utilized from there.

If so, wouldn't it need to be two functions, one to establish what the ENV variables should be and the other to check them?

vcpkg_internal_(set|prepend|append)_and_backup_env will append the added variable to an internal list
vcpkg_internal_restore_env will remove it from that list
vcpkg_internal_check_env_restored checks if the list is empty

he prepending that's going on here is specifically path-list prepending.

no it might not be path specific e.g. CFLAGS etc.. You would always use a set(ENV (${NEWVALUE}${SEP}${ENV}|${ENV}${SEP}${NEWVALUE})) here and let the caller decide how to do that. So the function requires an additional seperator argument (which will either be a space or the HOST_PATH_SEP).

Looking at the cases I found for this, I'm not sure how necessary the config argument is.

it is required there a cases where you want to first setup general configuration independent falgs and then configuration dependent flags. It also avoiding issues to to forgetting to correctly unset the previous configuration

@ras0219 Ping for review again.

@LRFLEW, could you resolve the conflicts?

I've updated the code here, but the CI is showing regressions. The codebase has changed a lot since I first made this PR. One of the files was already fixed, so I removed that from this PR. The regressions are likely due to other ports having or being affected by the underlying bug. I'll take a closer look at this and try to get all the regressions fixed.

This PR has been inactive for a long time, please reopen it if there is any progress.


Does not auto tag when mapping in .astro file but works with .tsx

When I type an element while mapping in a .astro file, the auto-tagging does not work.
In the example below, typing out the
 inside the map method does not trigger the auto-tagging. However, this works fine in a .tsx file.
---
import Layout from "../layouts/Layout.astro";
import { publications } from "../publications";
---

<Layout title="Publications">

      {publications.map((pub) =>
{pub.title}
)}

</Layout>

Config
Neovim Version: v0.9.5
Package Manager: Lazy
return {
	"windwp/nvim-ts-autotag",
	opts = {
		enable_close_on_slash = false,
	},
}

Hello, this should be resolved with the merging of #173.
I'll be closing this as a result. If you're still facing issues, please ping me and I'll reopen this.
Thanks 🙂


Added a convenience method to retrieve latest log entry from a job

I'm having a harrd time getting tests to go green: I have random reds but I think they are due some idiosicracy of the laptop I'm using
This convenience method is to have less boilerplate code in my typical use cases

Looks good @marcoalbarelli. Two things:

The job-add-log and variable jobAddLog should probably be renamed to job-log and jobLog. I can do this if you want. It is a big change with find/replace on the entire code base.
Documentation.

With regards to the tests, if it is the idle event causing the issue, it can be ignored. I am considering removing the idle tests and maybe doing a once off test on idle.

I just ran the tests, all good.

@marcoalbarelli This is live now in v1.0.2.


Lidar to imu calibration

Dear author,
Thanks for your wonderful work. I have few questions:

The lidar to imu auto calibration, dump the pcd files in the current directory but doesn't visualize the trajectory overlapped on point cloud. How can I visualize pointcloud overlaped with pose trajectory as shown in the README
What is the initial transformation this repository requires: lidar wrt imu or imu wrt lidar?

Currently, the visualization code has not been added, and the visualization program can be added in the following versions.


Additional BlackboxBoundedContext tests

This PR introduced method to register event dispatchers with BlackBoxBoundedContext.
This PR follows up on those changes by adding a method to register command dispatchers, as well as testing both registering event and command dispatchers.

@armiol, PTAL.

@armiol, I think the build should pass once https://github.com/SpineEventEngine/core-java/pull/981 is merged.

@armiol, PTAL again.


[BUGFIX] Git-ignore the PHPUnit result cache

The corresponding file gets created by more recent versions of PHPUnit.

Yes, exactly.


Configuration page has bad information.

on https://github.com/KatanaCode/blogit/wiki/Configuration it recommends ````include_admin_actions='``` which is now deprecated.

Thanks - I've removed those :)


Add schema to GET responses in OpenApi definition

Right now the OpenApi definition does not provide a schema for the GET responses.
Those definitions already exists (they are e.g. used for POST parameters) and it would be nice to also have them included in the GET responses.
This would make the API definition more complete and enable clients, for example swagger-ui, to always show the model or even example results of the endpoint.
See for example: http://petstore.swagger.io/#!/pet/getPetById
Currently the OpenApi definition for a GET endpoint response looks like this:
"responses": {
    "206": {
        "description": "Partial Content"
     },
     "200": {
         "description": "OK"
     }
 }

Including the schema would look like this:
"responses": {
    "206": {
        "description": "Partial Content"
     },
     "200": {
         "description": "OK",
         "schema": {
             "$ref": "#/definitions/film"
          }
     }
 }

I think the change is necessary, otherwise when using swagger-codegen, the generated library will return none for any get method

fixed by #885


Allow the fetch function to be supplied in defaults

As fetch becomes more and more a thing it's likely we wont' want to keep using the same fetch lib. Let users supply their own!

This would be easy enough to do, but I'm not sure I see the point in overriding it?

Just sort of a nice to have - prevents projects from being tied to old version of fetch. A quick solution for people too lazy to rewrite this repo (or who don't have access) to use whatever fetch library they deem most good.

IMO the goal should be to eliminate the fetch polyfill altogether at some point in the future. It's already native in Chrome and FF. My thought was this repo just assumes there is a global fetch available. Do you think that's a bad idea? Not really opposed to being able to override it since it's so trivial, just wondering why you'd need to.

I suppose we could make that assumption, it just means that whoever uses this will have to know that they need to have fetch polyfilled already, which isn't so much of a stretch.
I didn't even think about just assuming fetch was already in global space.

As long as it's documented that it may be needed (and we will probably have it already in our frontend template bootstrapping), we can probably drop the polyfill requirement from this library.

:+1: i'll close this and make a "remove fetch lib" issue


More Timing Information For cleos Commands In Integration Tests

Change Description

#6148
Added timing information for cleos commands that were missed in previous pull request.  Also fixed an error handling error that was exposed at the same time.
Consensus Changes

N/A
API Changes

N/A
Documentation Additions

N/A

Forgot to change merge branch


Quants, Quotes, Caps, and Comments

I went ahead and finished up groups and quantification with associated syntax options. I added in quotes and comments too.
This demonstrates some the brokenness of the lexer's current approach, beyond brokenness from custom character classes. It also shows some of the absurdity of trying to model with nested enums.
I have this as a draft PR because it probably makes sense to fix the tokens and lexer instead of piling on hacks.

This is superseded by https://github.com/apple/swift-experimental-string-processing/pull/53


ci: Write a cron job to detect leaked di-tester spot machines

Migrated to https://trello.com/c/StpWRnrk


chore(release): 2.38.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 3ff172b633a83dfc0dc841960ffc2c71ee23c272
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Unlinked Mentions Backlinks do not show up.

Unlinked Mentions Backlinks do not show up. The plugin only works for Linked mentions. Obsidian V1.7.7 on Windows.

If it's not too complicated I would love to have it work for Unlinked Mentions as well! This makes my life so much easier when I have multiple of the same names in different folders. Already been massively helpful in the linked mentions section!

@Robinaite I implemented it in 0.3.1, so please give it a try.
Due to the lack of capabilities of Obsidian's API, this is a heuristic implementation.
Let me know if you find there are something wrong.


liquibase.exception.UnexpectedLiquibaseException: java.lang.ClassCastException: liquibase.database.DatabaseFactory cannot be cast to liquibase.SingletonObject

Environment
Gradle 5.6.4
Kotlin:       1.3.41
Groovy:       2.5.4
Ant:          Apache Ant(TM) version 1.9.14 compiled on March 12 2019
JVM:          1.8.0_242 (Amazon.com Inc. 25.242-b08)
OS:           Windows 10 10.0 amd64
Liquibase Version:
org.liquibase:liquibase-core:4.6.2
Liquibase Integration & Version:
org.liquibase:liquibase-gradle-plugin:2.1.0
Liquibase Extension(s) & Version:
Database Vendor & Version:
PostgreSQL 12
Operating System Type & Version:
Windows 10
Description
One of the upgrade steps at Liquibase 4.0 Extension Upgrade Guide is to change a DatabaseFactory.getInstance() to the Scope.getCurrentScope().getSingleton(DatabaseFactory.class) as far as getInstance() was marked as depricated.
Scope.getCurrentScope().getSingleton(DatabaseFactory.class) returns instance of <T extends SingletonObject> T.
SingletonObject is a marker interface added in version 4.
But DatabaseFactory does not extend any classes and does not implement any interfaces.
As a result when we try to get the instance of DatabaseFactory in a way described in the Guide we faced an exception (see Actual Behaviour).
Steps To Reproduce
The issue is reproduced in any situation when Scope.getCurrentScope().getSingleton(DatabaseFactory.class) was called.
Actual Behavior

Caused by: liquibase.exception.UnexpectedLiquibaseException: java.lang.ClassCastException: liquibase.database.DatabaseFactory cannot be cast to liquibase.SingletonObject
at liquibase.Scope.getSingleton(Scope.java:326)
at liquibase.Scope$getSingleton$0.call(Unknown Source)
...
...
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:103)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:49)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:42)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:28)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:717)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:684)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$5.run(ExecuteActionsTaskExecuter.java:476)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:461)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:444)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$200(ExecuteActionsTaskExecuter.java:93)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:237)
at org.gradle.internal.execution.steps.ExecuteStep.lambda$execute$1(ExecuteStep.java:33)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:33)
at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:26)
at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:58)
at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:35)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:48)
at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:33)
at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:39)
at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:73)
at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:54)
at org.gradle.internal.execution.steps.CatchExceptionStep.execute(CatchExceptionStep.java:35)
at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:51)
at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:45)
at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:31)
at org.gradle.internal.execution.steps.CacheStep.executeWithoutCache(CacheStep.java:208)
at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:70)
at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:45)
at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:49)
at org.gradle.internal.execution.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:43)
at org.gradle.internal.execution.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:32)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:38)
at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:24)
at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:96)
at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:89)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:54)
at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:38)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:76)
at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:37)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:36)
at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:26)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:90)
at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:48)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:69)
at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:47)
at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:33)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:140)
... 34 more
Caused by: java.lang.ClassCastException: liquibase.database.DatabaseFactory cannot be cast to liquibase.SingletonObject
at liquibase.Scope.getSingleton(Scope.java:323)
... 91 more

@kataggart hi,
may I ask is there any result of this issue?
As I can see it was closed but I cannot see any changes in documentation or PR. Was the issue irrelevant or smth else?

It seems like it should still be open and unresolved

@oleksii-syromolotov 100% my error! apologies.. I shouldn't have closed. Thanks for pointing it out.. reopening

Hi @kataggart,
We need to upgrade our liquibase-core version due to security issues and we are blocked on this issue.
Any updates?
Thanks
Natan

we also need this ASAP. should we create PR to add tagging interface on DatabaseFactory?

What is the status of that? I also need that!!!

The fix is planed to be included in the next release later in January.

Close by PR https://github.com/liquibase/liquibase/pull/3624 merged just now.

@filipelautert thanks for the merge. Is there a way to get a release candidate in Maven repo so we can check it out and verify on our end our usage of liquibase will work?

Hi @yairogen - usually we don't do release candidates, but you can get the build artifacts from master here: https://github.com/liquibase/liquibase/suites/10205393148/artifacts/499783593 . It's a zip file that contains the liquibase-core-0-snapshot.jar file, you can use it to run your tests. It also has all the other required files by maven so if you prefer you can just copy them to your .m2/repository/org/liquibase/liquibase-core/0-SNAPSHOT directory and use this version to test.


Can't resolve './styles/font/styles/font/MaterialIcons-Regular-v48.woff2'

packages

"@angular/animations": "~10.0.7",
"@angular/cdk": "~10.1.1",
"@angular/common": "~10.0.7",
"@angular/compiler": "~10.0.7",
"@angular/core": "~10.0.7",
"@angular/forms": "~10.0.7",
"@angular/material": "^10.1.1",
"@angular/platform-browser": "~10.0.7",
"@angular/platform-browser-dynamic": "~10.0.7",
"@angular/router": "~10.0.7",
"@auth0/angular-jwt": "^5.0.1",
"@covalent/core": "^3.0.1",
"angular2-notifications": "^9.0.0",
"bootstrap": "^4.5.0",
"hammerjs": "^2.0.8",
"module": "^1.2.5",
"npm-check-updates": "^7.0.2",
"rxjs": "~6.6.2",
"tslib": "^2.0.0",
"zone.js": "~0.10.3"

styles.scss:

// Angular Material + Coavalent
@import '~@angular/material/theming';
@import '~@covalent/core/theming/all-theme';
// Define a custom typography config that overrides the font-family
// or any typography level.
$typography: mat-typography-config( $font-family: 'Roboto, monospace', $headline: mat-typography-level(32px, 48px, 700) );
@include mat-core($typography); // $typography is an optional argument for the mat-core
$primary: mat-palette($mat-orange, 800, 100, 900);
$accent: mat-palette($mat-light-blue, 600, 100, 900);
$warn: mat-palette($mat-red, 600, 100, 900);
$theme: mat-light-theme($primary, $accent, $warn);
@include angular-material-theme($theme);
@include covalent-theme($theme, $typography); // $typography is an optional argument for the covalent-theme

When I launch the server, I got this error:

ERROR in<EMAIL_ADDRESS><EMAIL_ADDRESS>Module Error (from ./node_modules/postcss-loader/src/index.js):
(Emitted value instead of an instance of Error) CssSyntaxError: C:\Users\xx\source\repos\Leav-Web\src\client\styles\font_font.scss:8:4: Can't resolve './styles/font/styles/font/MaterialIcons-Regular-v48.woff2' in 'C:\Users\XX\source\repos\Leav-Web\src\client\node_modules@covalent\core\common'
6 |     font-style: normal;
7 |     font-weight: 400;

8 |     src: url($mat-font-url+'MaterialIcons-Regular-v48.woff2') format('woff2');
|    ^
9 |   }
10 |   .material-icons {

What do you suggest?

Covalent is not yet material 10 compatible

I have the same problem but with "@angular/material": "^9.2.4" and "@covalent/core": "^3.0.1", i see the line in error:
CssSyntaxError: C:\Users\xx\source\repos\Leav-Web\src\client\styles\font_font.scss:8:4: Can't resolve './styles/font/styles/font/MaterialIcons-Regular-v48.woff2'
And the part './styles/font/styles/font....' appears to be duplicate, so i went to<EMAIL_ADDRESS>and in the first line change:
this: $mat-font-url: 'styles/font/' !default;
for: $mat-font-url: '' !default;
And worked for me, no more error.

This error looks like _font.css was in ".../node_modules/@covalent/core/common/" and was moved into ".../node_modules/@covalent/core/common/styles/font/" without change the $mat-font-url, the file MaterialIcons-Regular-v48.woff2 is in ".../node_modules/@covalent/core/common/styles/font/" too.

Same issue here, and it looks like exactly like you described (file moved without url update).
btw this also works: $mat-font-url: '/styles/font/' !default;
But this is not a solution as it is not possible to run build in pipelines.
Any news regarding this? Seems like a quick fix.
Thank you

I'm experiencing the same issue. I've fixed it for now using https://www.npmjs.com/package/patch-package to patch it post install...

Hi,
Any updates?
I saw that Covalent is now compatible to Angular 11, but I continue to have the issue on a fresh install.

@ArminAg where did you $mat-font-url: '/styles/font/' !default;?
I put at first line of styles.scss but I still have the issue

@ranouf

You have to do $mat-font-url: '' !default; without the /styles/font/
You hotfix it by changing the first line in<EMAIL_ADDRESS>If you're running CI you'll need to monkey-patch it after an install, e.g. using patch-package as @jessevandenbossche said:

$ yarn add patch-package postinstall-postinstall --dev
( make the change )
$ yarn patch-package @covalent/core

It's important to make the change after installing patch-package, since yarn will clobber the change when installing packages.

I finally was able to use it with angular 11 without any manual patching.
I basically followed this guide: https://teradata.github.io/covalent/v3/#/docs/theming/sass-mixins
Which resulted in REMOVING the include of platform.scss from angular.json.
And adding this to my styles.scss above @include mat-core($typography);
$mat-font-url: './';

@include covalent-core();
@include covalent-material-icons();
@include covalent-utilities();
@include covalent-layout();
//@include covalent-colors(); // if you use the colors


3 add code style checker to repo

This add a .clang-format file to define the code style as well as a setup a github action to enforce it.

@jsdomingo this seems like a pretty good guide on how to set it up on vscode


Additional PutObjectAcl action

This was required for publishing publicly accessible items in my bucket.
http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUTacl.html

Awesome, thanks!


Record the version of the Godot engine for the Android platform

This introduces two meta-data tags use to record the version of the Godot Android library and the version of the Godot Android editor used to generate a Godot binary.
By default, the versions are populated by the version info in version.py.
For custom builds, the version is retrieved from the engine at runtime and passed to the gradle build.

Thanks!

Cherry-picked for 3.2.4.


Cursor issue with clickable widgets on Bot UI WebChat v4

When you hover over the menus, links or any clickable controls, you don't see the cursor showing as pointer, it shows the default standard arrow. That is bad user experience we need fix for our production Bot.

This is by-design.
Please see the discussion here, https://github.com/microsoft/BotFramework-WebChat/issues/1767.

Seems that this behavior was and still is supported in Webchat v3


Test on PHP74

Let's see if Travis has updated their list of runtimes =)

@Nyholm oh look, it works, and no bad surprises. can you adjust the .travis.yml thing?

hm, why does coverage time out with 7.4? maybe we should run the coverage build with 7.3 after all - i guess its very unlikely that this is an issue in our code.

the dev build should also use 7.4 btw

fixed in #369


Samba Server Performance Low

Version: <IP_ADDRESS>4
OS/Distro: Centos 6.7 / Samba4 File Server  samba4-4.2.10-7.
Issue/Impact:
Note: replace content with your own

systemctl status lwsmd.service
service lwsmd status
lwsmd (pid 41387 41318 41234 41164 41095 41023 40956) is running...

/opt/pbis/bin/lwsm list
/opt/pbis/bin/lwsm list
lwreg          running (container: 41023)
dcerpc         stopped
eventlog       running (container: 41318)
lsass          running (container: 41234)
lwio           running (container: 41164)
netlogon       running (container: 41095)
rdr            running (io: 41164)
reapsysl       running (container: 41387)
usermonitor    stopped

/opt/pbis/domainjoin-cli query
domainjoin-cli query
Name = HOSTNAME
Domain = DOMAINNAME.COM
Distinguished Name = CN=HOSTNAME,OU=Servers,OU=Local,DC=domainname,DC=com

pbis status

/opt/pbis/bin/enum-users
TotalNumUsersFound: 2426

my problem here is with slow samba server performance since I start using pbis-open with the file server.
I can see many running processing belongs to lwsmd  lw-containers lsass, lw-containers lwreg, lw-container lwio, lw-container netlogon ,lw-container eventlog and lw-container reapsysl
I have 3 sessions only opened with samba and about 32GB of RAM Used, 0 memory left.
normally it is normal for a file server with huge memory used, but never seen it with only 3 sessions, I mean before I use pbis-open
I wish if you can advice me here about this issue

We are having a look into some other samba issues. I'll make a note to check on this also.

This has been improved a lot in the recent releases. I would recommend upgrading to BeyondTrust Active Directory Bridge for continued support.  https://www.beyondtrust.com/privilege-management/active-directory-bridge
pbis-open will longer receive updates and will be archived. Closing all outstanding issues.


Are there any plans to publish a new release to npm?

Yup, my bad.
Done as<EMAIL_ADDRESS>


KFold for SVC in 0.3.0

I'm submitting a
not sure if I misused the function or this is a feature not supported yet.
Current Behaviour:

use smartcore::api::SupervisedEstimatorBorrow;
let results = cross_validate(
    SVC::new(),
    &x,
    &y,
    Default::default(),
    &KFold::default().with_n_splits(3),
    &accuracy,
)
.unwrap();

error
the trait `SupervisedEstimator<_, _, _>` is not implemented for `SVC<'_, _, _, _, _>`

Snapshot:

Environment:

rustc version 1.65.0 (897e37553 2022-11-02)
cargo version 1.65.0 (4bc8f24d3 2022-10-20)
Pop!_OS 22.04

Do you want to work on this issue?

Hi, thanks for using smartcore and finding this.
It looks like at the moment cross_validate works only for types that implement SupervisedEstimator trait; SVC implement SupervisedEstimatorBorrow instead, that is a variant that allows saving memory allocation. The solution can be:

or we implement SupervisedEstimator for SVC in place of SupervisedEstimatorBorrow
or we change cross_validate to accept SupervisedEstimatorBorrow and implement it for the other models (linear regression, ...); this way SupervisedEstimator will be used only with cross_val_predict (because it actually need a predict method).
or we develop a cross_validate_borrow function that takes types that implement SupervisedEstimatorBorrow

SVC was not meant to be used with cross_validate in the first place as we didn't have a use case for that. At the moment cross_validate works only with estimators that have also Predictor trait (SupervisedEstimator is a composed with Predictor while the "borrow" version is not). There is note about this in the documentation but I admit it should be referenced in the cross_validate documentation.
If you have any idea about how to fix this it would be great to hear, you can also open a Pull Request to fix it. If it is indeed deemed useful and we find a solution it will be released with the next version.
NOTE: model_selection module is missing the documentation, it would be also great if you can provide it.


[Important] Compare to STOA

Hi,
First, thank you for your contribution and congratulations!
I would have a question here, concerning Table 1 and Table 2 in your paper.
I think the true STOA methods are missing here. Please refer to Table 1 in the paper [Self-supervising Fine-grained Region Similarities for Large-scale Image Localization]
Adding the full results to Table 1 would make this paper friendly to follow up works.
Furthermore, when I check Table 2, I get the info. that the reported numbers of the proposed method are based on the usage of RANSAC, known as Ours (Multi-RANSAC-Patch-NetVLAD).
I strongly expect a fair comparison as the reported recalls of ALL methods in the paper [Self-supervising Fine-grained Region Similarities for Large-scale Image Localization] did not use RANSAC.
It is well-known that using RANSAC [two-view matching] can boost recalls. To validate the effectiveness of the proposed `Patch-NetVLAD' descriptor, please refrain from using RANSAC or using RANSAC for all baseline descriptors of STOA methods.
Please make fair comparisons.
Last, even for the out-of-the-date Netvlad baseline, its recalls on the Tokyo 24/7 are much better than the numbers reported in your paper. Please refer to Table 1 in the paper [Self-supervising Fine-grained Region Similarities for Large-scale Image Localization]
Please reflect these changes to your Arxiv and final version.
Without comparing to true STOA methods, the contribution of the proposed `Patch-NetVLAD' is questionable.
Congratulations again!

Dear @Autotalker,
Many thanks for your interest in our work, and thank you for your congratulations!This GitHub repository is for the (upcoming) code of Patch-NetVLAD, and the Issues tracker here is meant for reporting questions/bugs related to the code only (see https://guides.github.com/features/issues/).
Re. the research itself - we have received a lot of useful feedback and suggestions including yours and will try to incorporate as much as is possible into the revision, as well as in future work - noting that due to the constraints of the process we are unlikely to be able to do it all in this specific publication.
Many wishes,Tobias
P.S. Please note that we may not reply to anonymous emails as they are likely to be filtered out by our university’s spam filter (mentioning this as you inadvertently created an anonymous account here on GitHub when you posted this issue – fresh email addresses might be filtered out and non-anonymous communication is our preferred means of talking about scientific questions).
You are welcome to send me an email<EMAIL_ADDRESS>if you prefer, feel free to also include the other authors) with any queries that you may have related to the paper itself.

Hi Tobias,
 Thank you for your reply. I would expect your positive, point-to-point responses to my questions [Comparing to state-of-the-art methods]. It's your right to discuss [Point out my wrong statements] or ignore.
 At this stage, please don't close this issue. I want to read your revised version [arxiv does not have a deadline].
 Thank you!


chore(WEG-105): Add second seelsorge nr.

[x] Change label to "Telefonseelsorge Berlin"
[x] Add second phone number: 0800 111 0 222

:tada: This PR is included in version 1.3.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Headless task still running even after executing "BackgroundGeolocation.stop()"

I've used BackgroundGeolocation.headlessTask() to get location updates even if the app is killed, which works fine but as soon as I stop the tracking using BackgroundGeolocation.stop() everything stops but as soon as I close the app, the headless task again starts keep on sending locations even without executing BackgrounGeolocation.start() first.
Your Environment

Plugin version: "^0.6.4"
Platform: iOS or Android: Android
OS version: Any
Device manufacturer and model: Any

Running in Simulator: Pixel 3a
React Native version: "0.63.4"
Plugin configuration options:

BackgroundGeolocation.HIGH_ACCURACY,
stationaryRadius: 5,
distanceFilter: 1,
notificationTitle: 'Tracking',
notificationText: "Don't mind me just watching",
notificationsEnabled: true,
startForeground: true,
debug: false,
startOnBoot: true,
stopOnTerminate: false,
locationProvider: BackgroundGeolocation.ACTIVITY_PROVIDER,
interval: 10 * 1000,
fastestInterval: 5000,
activitiesInterval: 10000,
stopOnStillActivity: false,
url: null,
});

BackgroundGeolocation.on('location', (location) => {
  // handle your locations here
  // to perform long running operation on iOS
  // you need to create background task
  BackgroundGeolocation.startTask((taskKey) => {
    // execute long running task
    // eg. ajax post location
    // IMPORTANT: task has to be ended by endTask
    console.log('ON location: ', location);
    BackgroundGeolocation.endTask(taskKey);
  });
});

BackgroundGeolocation.headlessTask(async (event) => {
    if (event.name === 'location' || event.name === 'stationary') {
      const location = event.params;
      console.log(location);
    }
});

BackgroundGeolocation.on('error', (error) => {
  console.log('[ERROR] BackgroundGeolocation error:', error);
});

BackgroundGeolocation.on('start', () => {
  console.log('[INFO] BackgroundGeolocation service has been started');
});

BackgroundGeolocation.on('stop', () => {
  console.log('[INFO] BackgroundGeolocation service has been stopped');
});

BackgroundGeolocation.checkStatus(({ isRunning }) => {
  if (isRunning) {
    BackgroundGeolocation.start(); // service was running -> rebind all listeners
  }
});

Link to your project: N/A

Context

The headless task is still executing after closing the app after stopping tracking using BackgroundGeolocation.stop(). The foreground notification starts showing in the notification bar, without even executing BackgroundGeolocation.start().
Expected Behavior

After executing BackgroundGeolocation.stop() all tracking related services should stop (which happens perfectly but not if I use headless task)
Actual Behavior

All tracking related services stop after executing BackgroundGeolocation.start() but as soon as I close the app, the foreground notification pops up and headless code starts executing.
Possible Fix

Steps to Reproduce

Define a headless task
Start the service using BackgroundGeolocation.start()
Stop the service using BackgroundGeolocation.stop()
Close the app
You will see foreground notification as soon as you close/kill the app with headless code executing

Context

I am trying to successfully stop the tracking of a user whenever he marks his out attendance. After the attendance gets successfully marked, I try to stop the tracking with BackgroundGeolocation.stop() but then the above issue happens.
Debug logs

I think the code below is weird.
BackgroundGeolocation.checkStatus(({ isRunning }) => {
  if (isRunning) {
    BackgroundGeolocation.start(); // service was running -> rebind all listeners
  }
});

BackgroundGeolocation.start() doesn't bind anything.
You don't have to restart it.

@darron1217 But if I don't do this:
BackgroundGeolocation.checkStatus(({ isRunning }) => {
  if (isRunning) {
    BackgroundGeolocation.start(); // service was running -> rebind all listeners
  }
});

then location doesn't log in the console after closing and reopening the app again. Also If I define a headless task to get locations even if the app is killed, the next time I open the app while service is running, it throws an error:
registerHeadlessTask or registerCancellableHeadlessTask called multiple times for same key 'com.marianhello.bgloc.react.headless.Task'
I've tried commenting the headless task, I thought that was preventing locations to show up in console after closing and re-opening the app but the same thing happened. Location does not show up in console after re-opening the app.

@raghav-ado I found bug on Android targetSdk 29+ and fixed it.
Please update your plugin version to 0.6.6

@darron1217 still same error registerHeadlessTask or registerCancellableHeadlessTask called multiple times for same key 'com.marianhello.bgloc.react.headless.Task after upgrading to version 0.6.6

@raghav-ado I guess your code allows calling start() multiple times.
You should run start() only if status is not running

@raghav-ado did you solved it?

@darron1217 Even after starting service only when it's not running, whenever I close the app, wait for headless task to log location and open the app again, I still get registerHeadlessTask or registerCancellableHeadlessTask called multiple times for same key 'com.marianhello.bgloc.react.headless.Task' and location updates stop even when app is open after this error. Maybe service is being stopped after encoutering this error.

@raghav-ado Thanks for your feedback.
I'll check this issue if available.

Same problem here

@walterdl I kind of got it to work. I have moved my headless task inside BackgroundGeolocation.on('start', ...) then everything works as expected.
BackgroundGeolocation.on('start', async () => {
  console.log('[INFO] BackgroundGeolocation service has been started');

  // headless task
  BackgroundGeolocation.headlessTask(async (event) => {
    // your task
    }
  });
});

I think that way your headless task only gets registered once and doesn't cause 'multiple times for same key' error.
It stops on BackgroundGeolocation.stop() as well.


For countries where admin 1 levels are spelled out, the total alerts displayed under the admin1 levels appear to be higher than the overall number for the entire state. Examples include Norway, Tanzania, and Brazil. Is this because alerts are issued for multiple admin 1s and then shown for each one, or is it an error?

I think this is a related issue:

When I filtered by extreme severity and country South Africa, it said there were three alerts, and those three alerts appeared under the 'Alerts' section without problem, however, when I switched to the 'Admin-1' view I saw this:

Where the count per region doesn't seem to be right. When I click in each admin-1, I see the three alerts, but it is just in this summary version that I think is presenting the total count, rather than the country+severity filtered count

@barshathakuri did you look into the above issue yet?

Is this because single alerts are issued for multiple admin 1s and this is not a bug.
cc: @nnjemie

In the photos shown above, if there are 3 ongoing alerts in the whole country, shouldn't there be a maximum of 3 alerts for each admin 1 level even if they are issued for multiple admin 1 regions? However, it shows 3 ongoing alerts for the country and 5 alerts for each admin 1 level. Maybe we can check if the filtering works for the admin 1 levels as well? @barshathakuri


Bumped grpc-tools version

For the 0.15.1 patch of grpcio-tools.

LGTM

I've updated all the package version numbers.

LGTM


compileSdkVersion 21 due to apache dependencies

Can you please replace deprecated org.apache.http lib with HttpURLConnection to allow to increase sdk version?

You can fork our code if it is urgent.
I will merge your update.

I did one
https://github.com/matrix-org/matrix-android-sdk/pull/92

I merged your UrlPostTask update but not your target updated : we have to keep the compliancy with the former console application.


Strange result with clumsy and defib

Description
When you clumsy with a defibrillator, you are put into a weird state where you briefly appear to be in crit yourself. Fixes itself after a second or two, which is possibly it being some sort of client misprediction. Possibly comes from the assumption that a defibrillator cannot be normally used on a standing person.
Works the same before and after #31147 .
Reproduction
Become a Cluwne.
Kill something.
Defib it.
Screenshots

Likely happens because the defib is not predicted.
#30044 should probably fix this.


4.0.0 in npm is not compatible with RN v0.40.0

The npm bundle for v4.0.0 still has the old header structure and is not compatible with RN v0.40.0
For now updated my package.json dependency to this
git+https://github.com/oblador/react-native-vector-icons.git#380b3a5661c25dae4a50baaebe22aac0f2ed07cd

Pretty sure you're wrong :-)

Yeah sorry @oblador my bad, maybe was something wrong with my yarn cache.


CatchGPT

@talaaalotaobi
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
Could you elaborate your question so we can assist you according to that.

@talaaalotaobi
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Reimplement Tests

While moving over work done on the Azure Explorer, testing was lost - mostly because it assumes that it runs in NW.js. We need to reimplement testing and get cracking on some good integration and unit tests. It's fine if tests are failing - I actually assume that good tests would find a bunch of edge cases we're currently not handling well.

[x] Reimplement JavaScript Code Style Testing
[x] Reimplement Phantom.js Testing
[x] Mock Login API and write tests (#22)
[x] Mock Device API and write tests (#24)

Done!


docs(locales): fix lint:locales errors

fixes #614

Codecov Report

Merging #615 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #615   +/-   ##
=======================================
  Coverage   81.27%   81.27%
=======================================
  Files         194      194
  Lines        3001     3001
  Branches      499      499
=======================================
  Hits         2439     2439
  Misses        495      495
  Partials       67       67

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 5b2f108...44b9793. Read the comment docs.


feat: add example for preview storage client

I may have to leave the bug bash a little early so started early with the Rust SDK. This might have been in your backlog/WIP already but since I was about to follow examples pattern anyway, just decided to PR it.
Note that I did NOT update the CI workflows to run this due to alpha instability.
my_momento_store was created
Key foo was successfully persisted in my_momento_store
Key foo found in my_momento_store with value String("bar")
Key foo was successfully deleted from my_momento_store
Store was deleted

pushed a few commits to rebase and add to CI


Use env var for container base image name

Fixes #22
Signed-off-by: Juraci Paixão Kröhling<EMAIL_ADDRESS>

Thanks! I'll merge it, as the only way to really know whether it works is by merging and attempting a release.


XCode 10 ios 12 Could not find module Adyen for arm64 architecture

Hi @dmitry-blackwave ,

I was getting the above error when i did your installation steps and these were my Adyen Pods that got installed,
Installing Adyen 2.8.1
Installing Adyen3DS2 (0.9.6)
Installing AdyenInternal 2.8.1
Using AdyenReactNative (1.2.0)
My Pod File,
`
platform :ios, '11.0'
use_frameworks!
target 'fermynt' do
pod 'AdyenReactNative', :path => '../node_modules/adyen-react-native'
end
post_install do |installer|
installer.pods_project.targets.each do |target|
if target.name == 'Adyen'
target.build_configurations.each do |config|
config.build_settings['SWIFT_VERSION'] = '4.2'
end
end
end
end
`
But it didn't workout,so I did the manual linking as below and that too didn't work,

Could not find module Adyen for arm64 architecture
Compile Time Error.

same here.

After surfing through the internet,I raised a issue with adyen ios sdk as below,
https://github.com/Adyen/adyen-ios/issues/72

Hi @dmitry-blackwave ,
Adyen has released a new version today 2.8.3 which solves the above problem but ends up with another,

Then i added the implementation for PaymentControllerDelegate in AdyenReactNative.swift which was missing as per the new migration given below
https://github.com/Adyen/adyen-ios/blob/master/MIGRATION.md
func provideAdditionalDetails(_ additionalDetails: AdditionalPaymentDetails, for paymentMethod: PaymentMethod, detailsHandler: @escaping Completion<[PaymentDetail]>){
}
Then i removed the following lines from the Podfile
post_install do |installer|   installer.pods_project.targets.each do |target|     if target.name == 'Adyen'       target.build_configurations.each do |config|         config.build_settings['SWIFT_VERSION'] = '5.0.1'       end     end   end end
and then ran 'pod update' which ended with these libraries version,
Installing Adyen 2.8.3 (was 2.8.1)
Installing Adyen3DS2 2.1.0-rc.1 (was 0.9.6)
Installing AdyenInternal 2.8.3 (was 2.8.1)
Using AdyenReactNative (1.2.0)
After this i replaced the Adyen framework in your nodemodules ios folder with the newly swift 5 compiled version ,linked the project manually and was able to proceed but while building at the final stage I am getting these errors,
`
Showing Recent Messages
:-1: Could not find auto-linked library 'swiftCoreGraphics'
:-1: Could not find auto-linked library 'swiftFoundation'
:-1: Could not find auto-linked library 'swiftMetal'
:-1: Could not find auto-linked library 'swiftDarwin'
:-1: Could not find auto-linked library 'swiftUIKit'
:-1: Could not find auto-linked library 'swiftCoreFoundation'
:-1: Could not find auto-linked library 'swiftObjectiveC'
:-1: Could not find auto-linked library 'swiftDispatch'
:-1: Could not find auto-linked library 'swiftCoreImage'
:-1: Could not find auto-linked library 'swiftQuartzCore'
:-1: Could not find auto-linked library 'swiftCore'
:-1: Could not find auto-linked library 'swiftSwiftOnoneSupport'
:-1: Undefined symbol: Foundation.URL._bridgeToObjectiveC() -> __C.NSURL
:-1: Undefined symbol: type metadata accessor for Foundation.URL
:-1: Undefined symbol: value witness table for Builtin.UnknownObject
:-1: Undefined symbol: (extension in Foundation):Swift.Dictionary._bridgeToObjectiveC() -> __C.NSDictionary
:-1: Undefined symbol: Swift.Dictionary.init(dictionaryLiteral: (A, B)...) -> [A : B]
:-1: Undefined symbol: (extension in Foundation):Swift.String._bridgeToObjectiveC() -> __C.NSString
:-1: Undefined symbol: static (extension in Foundation):Swift.String._unconditionallyBridgeFromObjectiveC(__C.NSString?) -> Swift.String
:-1: Undefined symbol: Swift.String.init(_builtinStringLiteral: Builtin.RawPointer, utf8CodeUnitCount: Builtin.Word, isASCII: Builtin.Int1) -> Swift.String
:-1: Undefined symbol: type metadata for Swift.String
:-1: Undefined symbol: protocol witness table for Swift.String : Swift.Hashable in Swift
:-1: Undefined symbol: protocol witness table for Swift.String : Swift.Equatable in Swift
:-1: Undefined symbol: (extension in Foundation):Swift.Array._bridgeToObjectiveC() -> __C.NSArray
:-1: Undefined symbol: generic specialization <Swift.String> of Swift.Array.init(arrayLiteral: A...) -> [A]
:-1: Undefined symbol: type metadata accessor for Swift.Array
:-1: Undefined symbol: type metadata for Swift.Bool
:-1: Undefined symbol: type metadata for Swift.Int
:-1: Undefined symbol: Swift.fatalErrorMessage(: Swift.StaticString, _: Swift.StaticString, file: Swift.StaticString, line: Swift.UInt, flags: Swift.UInt32) -> Swift.Never
:-1: Undefined symbol: Swift._allocateUninitializedArray(Builtin.Word) -> ([A], Builtin.RawPointer)
:-1: Undefined symbol: generic specialization  of Swift._allocateUninitializedArray(Builtin.Word) -> ([A], Builtin.RawPointer)
:-1: Undefined symbol: Swift.== infix<A where A: Swift.RawRepresentable, A.RawValue: Swift.Equatable>(A, A) -> Swift.Bool
:-1: Undefined symbol: protocol descriptor for Swift.Error
:-1: Undefined symbol: Swift.print(_: Any..., separator: Swift.String, terminator: Swift.String) -> ()
:-1: Undefined symbol: type metadata for Any
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftCoreFoundation
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftCoreGraphics
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftCoreImage
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftDarwin
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftDispatch
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftFoundation
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftMetal
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftObjectiveC
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftQuartzCore
:-1: Undefined symbol: _swift_FORCE_LOAD$_swiftUIKit
:-1: Undefined symbol: _swift_allocObject
:-1: Undefined symbol: _swift_beginAccess
:-1: Undefined symbol: _swift_bridgeObjectRelease
:-1: Undefined symbol: _swift_bridgeObjectRetain
:-1: Undefined symbol: _swift_deallocObject
:-1: Undefined symbol: _swift_dynamicCast
:-1: Undefined symbol: _swift_endAccess
:-1: Undefined symbol: _swift_errorRelease
:-1: Undefined symbol: _swift_errorRetain
:-1: Undefined symbol: _swift_getExistentialTypeMetadata
:-1: Undefined symbol: _swift_getInitializedObjCClass
:-1: Undefined symbol: _swift_getObjCClassFromMetadata
:-1: Undefined symbol: _swift_getObjCClassMetadata
:-1: Undefined symbol: _swift_getTupleTypeMetadata2
:-1: Undefined symbol: _swift_getWitnessTable
:-1: Undefined symbol: _swift_isaMask
:-1: Undefined symbol: _swift_release
:-1: Undefined symbol: _swift_retain
:-1: Undefined symbol: _swift_unknownObjectRelease
:-1: Undefined symbol: _swift_unknownObjectRetain
`

I was able to successfully make the adyen ios to work :)
Here are the Steps for XCode 10.2.1 & above

Your PodFile should look like ,

platform :ios, '11.3'
use_frameworks!
target 'Your Target Name' do
pod 'AdyenReactNative', :path => '../node_modules/adyen-react-native'
end
'pod update' would add these libraries ,
Installing Adyen 2.8.3 (was 2.8.1)
Installing Adyen3DS2 2.1.0-rc.1 (was 0.9.6)
Installing AdyenInternal 2.8.3 (was 2.8.1)
Using AdyenReactNative (1.2.0)

Add  the implementation for PaymentControllerDelegate in AdyenReactNative.swift which was missing as per the new migration given below

https://github.com/Adyen/adyen-ios/blob/master/MIGRATION.md
func provideAdditionalDetails(_ additionalDetails: AdditionalPaymentDetails, for paymentMethod: PaymentMethod, detailsHandler: @escaping Completion<[PaymentDetail]>){
}

Modify the OS Version for AdyenReactNativeProject to 11.3 to avoid armv7 missing architecture

Replace the Adyen framework in your nodemodules ios folder with the newly swift 5 compiled version from the Pods to /node_modules/adyen-react-native/ios like below

Link the project manually

As per the facebook link below create a empty swift file and create the bridege in your parent RN project,

Thats it you should be able to get the adyen working in iOS.

3.0.0 was released on 18th of June.
Can you create a PR for 2.8.4 with your changes?

@GituBojan added a Pull request and I have also created a issue for 3.0.0 release as well.

Installing Adyen 2.8.3 (was 2.8.1)
Installing Adyen3DS2 2.1.0-rc.1 (was 0.9.6)
Installing AdyenInternal 2.8.3 (was 2.8.1)
Using AdyenReactNative (1.2.0)
I could only find Adyen3Ds2 in the pods folder. Adyen, AdyenInternal is installed but there is no .framework file inside the POD
By linking them manually you mean a second link within the Linked Frameworks and Libraries even if we install the pod file?

@GituBojan

Copy Adyen3DS2 from Pods/Adyen3DS2/Frameworks and then Copy from Products Folder Adyen.Framework,AdyenInternal.framework and AdyenInternal.bundle

@mkharibalaji do you know how to apply your fixes to the RN60 autolinker... if I manually link it can't find the react bridge... if I don't there's no module...

@mkharibalaji I have same problem as @GituBojan can't see Adyen.framework not either AdyenInternal.framework, build is without errors. But when I run app and include adyen-react-native I get error with native module.

@mkharibalaji Anything new?

I figured out that this error message doesn't have anything to do with architectures, the framework search paths are just wrong
Try setting these paths on the AdyenReactNative target

After that Adyen.framework should be compiled and end up in the build directory.
If AdyenInternal can't be found from the Adyen module, add "${BUILD_DIR}/AdyenInternal" to the Adyen search paths as far as I remember.

Hi @jannisch,
You are correct !!! I tried several times even cearing of the xcode cache but still recieving this error and thats why went on with Manual reference.

@voslartomas - Please try @jannisch way...

@jannisch - Can you raise a PR for the Path Fix ??

@mkharibalaji sure I'll submit a PR as soon as I got time and try everything step by step. So far it only works with the quickstart repo (0.59)
react-native 0.61 even builds automatically and compiles Adyen, however I get the Native module cannot be null error from the first post in this thread. Please let me know if you have any ideas how to fix this

@jannisch - Did you add react-native.config.js file to this  library and have you given a try ???

@jannisch
have you found the solution?

Hi @jannisch @voslartomas @jrwpatterson ,
Sorry for the late response.I was busy with other work.
update the AdyenReactNative.podspec file with this for RN 0.60 and do a 'pod install' it should work.
``
require 'json'
package = JSON.parse(File.read('package.json'))
Pod::Spec.new do |s|
s.name = "AdyenReactNative"
s.version = package["version"]
s.summary = package["description"]
s.homepage = "https://github.com/dmitry-blackwave/adyen-react-native#readme"
s.license = "MIT"
s.author = { "author" =><EMAIL_ADDRESS>}
s.platform = :ios, "11.0"
s.source = { :git => "https://github.com/author/AdyenReactNative.git" }
s.source_files = "ios/*.{h,m,swift}"
s.requires_arc = true
s.dependency "React"
s.dependency "Adyen","2.8.4"
s.dependency "Adyen/ApplePay","2.8.4"
end
``
In the meanwhile I will raise a PR for this.


Warn about obviously malformed results files instead of terminating with an error

Fixes gh-461

Coverage increased (+0.08%) to 57.141% when pulling 4cb3b629207200f8a89e4fe8eff470d81573d8d7 on pv:ignore-malformed into b1cc0a9aa5107e237cd608b9f87da44e1004d27b on spacetelescope:master.

Coverage increased (+0.2%) to 57.222% when pulling 4439323ec05c88772eaf09cb9d2524f86f19a887 on pv:ignore-malformed into b1cc0a9aa5107e237cd608b9f87da44e1004d27b on spacetelescope:master.

Merging, should be ok.


ccv link error on Linux

@headupinclouds Can't file an issue on your Hunterised fork of ccv, so filing here.
ccv in Hunter won't like on Linux:
/home/ubuntu/workspace/hunter/PROJECT/ccv/TOOLCHAIN/default/_testing/Hunter/_Base/d686e4c/326318e/6e3ae24/Install/lib/libccvd.a(ccv_algebra.c.o): In function `ccv_normalize':
/home/ubuntu/workspace/hunter/PROJECT/ccv/TOOLCHAIN/default/_testing/Hunter/_Base/d686e4c/326318e/6e3ae24/Build/ccv/Source/lib/ccv_algebra.c:72: undefined reference to `sqrt'

The reason is that Linux keeps its maths functions in libm.
Here is an example of how I fixed it for libtiff, which needs libm for pow.  I've not used Sugar, which you're using for ccv, so I'm not confident to apply the fix to ccv myself.

I've applied your fix to my local fork, but am unable to test in my Linux VM right now (some kind of libcurl openssl/https problem during hunter package downloads).
https://github.com/headupinclouds/ccv/commit/c25b2fd1615f5c3477a60f9120a966d1c47efcdd

If you can confirm this fix works, I'll push the changes up and update the package.

some kind of libcurl openssl/https problem during hunter package downloads

What is the error message about?

Thanks @alamaison.  I just submitted a pull request for your ccv libm fixes (v0.7-p5).

What is the error message about?

I don't think this has anything to do with hunter.  From a quick search, my guess is that CMake is using a libcurl without openssl (directly or indirectly) for the ExternalProject_Add command.  This is the error I get:
cmake version 3.2.2

> cmake -H. -B_builds
-- [hunter] Initializing Hunter workspace (7103f0ab481523ca93a06c1c55abcd56741d3a97)
-- [hunter]   https://github.com/ruslo/hunter/archive/v0.8.13.tar.gz
-- [hunter]   -> /home/dhirvonen/.hunter/_Base/Download/Hunter/0.8.13/7103f0a
CMake Error at Build/Hunter-prefix/src/Hunter-stamp/download-Hunter.cmake:27 (message):
  error: downloading 'https://github.com/ruslo/hunter/archive/v0.8.13.tar.gz'
  failed

    status_code: 1
    status_string: "Unsupported protocol"
    log: Protocol "https" not supported or disabled in libcurl

  Closing connection -1

make[2]: *** [Hunter-prefix/src/Hunter-stamp/Hunter-download] Error 1
make[1]: *** [CMakeFiles/Hunter.dir/all] Error 2
make: *** [all] Error 2

[hunter ** INTERNAL **] Build project failed
[hunter ** INTERNAL **] [Directory:/home/dhirvonen/devel/work/ccv]

------------------------------ WIKI -------------------------------
    https://github.com/ruslo/hunter/wiki/error.internal
-------------------------------------------------------------------

CMake Error at cmake/HunterGate.cmake:76 (message):
Call Stack (most recent call first):
  cmake/HunterGate.cmake:86 (hunter_gate_wiki)
  cmake/HunterGate.cmake:312 (hunter_gate_internal_error)
  cmake/HunterGate.cmake:450 (hunter_gate_download)
  CMakeLists.txt:6 (HunterGate)

My CMake version is 3.2.2 (compiled from source).

My CMake version is 3.2.2 (compiled from source)

You need to add CMAKE_USE_SYSTEM_CURL=YES. I'm not sure, but I think curl version of cmake is kind of broken or limited.
See https://github.com/ruslo/polly/wiki/Jenkins#other:
build.py --install --toolchain default --config Release --verbose --fwd "CMAKE_USE_SYSTEM_CURL=YES"

Fixed in branch develop or in release: https://github.com/ruslo/hunter/releases/tag/v0.10.1
@headupinclouds Thanks, David!


Implement inverseResourceOffers

This should fix #57. If the changes to the interface seem strange, I'd like to discuss alternative choices that would support this feature.

@haosdent can you help me to comfirm if the interface change is OK?

@kaysoky implement an example about how to use inverseOffer, may refer https://github.com/kaysoky/InverseOfferExampleFramework/blob/master/example.cpp#L198-L209

Would inverseOffers be a better name for the interface?

@efritz I think inverseOffers is better
thanks for the PR

Thanks! Would it be possible to bump the version and make this version accessible through PyPI?

Of coz! We are just evaluated the new version, and will release it soon.

Great news! Thanks so much.


repo-stream update

Opened by mondeja/repo-stream-config/upstream.yaml

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 75.766%

Files with Coverage Reduction
New Missed Lines
%

blender_downloader/init.py
1
75.77%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
272

Relevant Lines:
359

💛  - Coveralls


Add API to Add/Remove virtual device

Verified the changes using wssdagent and the following sequence:
-> Create HCS VM on host with 'NVIDIA TESLA T4' GPU
-> Verify - VM is in Running state, has proper IP address, login to the VM and verify GpuDevice is visible in the VM (lspci -v), note down vmBusID (returned by AssignDevice)
-> Stop VM
-> Verify - VM is in Offline state, RemoveDevice succeeds with the vmBusID obtained in Start
Repeat above steps - Make sure the GpuDevice is visible in the VM after Start...


Icon request for WazirX and CoinDCX

I'd like to request icons for the cryptocurrency exchanges WazirX and CoinDCX.
Their URLs are as follows:
WazirX.com
CoinDCX.com

Here you go!
For Aegis v2.0 and above (recommended):
https://github.com/aegis-icons/aegis-icons/blob/master/SVG/WazirX.svg
https://github.com/aegis-icons/aegis-icons/blob/master/SVG/CoinDCX.svg
For Aegis v1.4.2 and below:
https://github.com/aegis-icons/aegis-icons/blob/master/PNG/WazirX.png
https://github.com/aegis-icons/aegis-icons/blob/master/PNG/CoinDCX.png
❓ How to add icon(s) to Aegis?


fix: Failing rundownPlaylist test

This test was failing for three reasons:

Test data had not been updated with the move to the timing type
The sort function to produce the default rundown ordering was incorrect
Rundown ordering now uses externalId rather than _id, so how the mock data is created needed to be updated, otherwise all of the rundowns had the same externalId and so got assigned the same ranks

Codecov Report

Merging #78 (8871493) into mirror/release37 (32b1b6f) will not change coverage.
 Consider uploading reports for the commit 70b20da to get more accurate results

@@                Coverage Diff                @@
##           mirror/release37      #78   +/-   ##
=================================================
  Coverage             82.35%   82.35%
=================================================
  Files                    12       12
  Lines                  1009     1009
  Branches                196      196
=================================================
  Hits                    831      831
  Misses                  177      177
  Partials                  1        1

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 32b1b6f...70b20da. Read the comment docs.


[Anaconda] Address GHSA-q3qx-c6g2-7pw2 vulnerability

Dev container name:

anaconda

Description:
This PR patches the following vulnerability:

GHSA-q3qx-c6g2-7pw2 - related to the aiohttp package;

This vulnerability comes from the continuumio/anaconda3 image used upstream for the anaconda devcontainer.
Changelog:

Updated Dockerfile:

Locked version for patched Python package;

aiohttp - minimum package version set to 3.9.0;

Updated tests to verify aiohttp minimum version (Minimum package version set to 3.9.0 which fixes GHSA-q3qx-c6g2-7pw2);

Checklist:

[x]   Checked that applied changes work as expected

Merge conflicts have been resolved


S3Store backup failure handling across VRG and DRPC

While discussing S3Store unavailability in a case where east cluster backs up PVs to west and vice-versa, on a failover, VRG will not promote the volumes to Primary as the alternate cluster is down and the backup will fail.
Towards this the following possible actions needs to be taken,

Change VR state first and backup PVs later in VRG
DRPC needs to check if Primary VRG is healthy before taking action on relocate
On a failover action, user needs to ensure DRPC last known status  (which would carry VRG last known status) has met all required Conditions to recover the workload on an alternate cluster

I believe this issue can be closed given that it is addressed in commit  https://github.com/RamenDR/ramen/commit/074a46438f52c9c41d9cae97631a3e7b1f0b8d98.


Fall of the Camarilla

text: An impersonator (eg. Kemintiri merged) can still play cards requiring a Prince or Justicar
link: https://groups.google.com/g/rec.games.trading-cards.jyhad/c/HVy8iPUxNbI/m/ZjCzAzmQFMwJ

Duplicate #770


Upgrade all examples to new beta client w/ new connection manager

This PR is for testing purposes only, not intended to be merged.

Oops. I published FSM2 incorrectly. Publishing FSM3 now.

Not sure what's up with Vercel. Seems like I need to open a new PR now every time to trigger a redeploy :( Pushing/adding commits no longer works it seems. Not sure what's up.


Can not find node binding files from @node-rs/jieba-win32-x64-gnu,@node-rs/jieba-win32-x64-msvc and...

Hello, When I use it in my nodejs project. After I packaged a application for windows use electron-builder. App can work normally on most machines. But this error appeared on a small number of machines. I don't know about "gnu" or "msvc". Do you know the reason for this?

Hey @StevenMichael3213 , I've met this issue once, and I found it's because windows firewall prevent the Node.js to load the unsigned dll file. In your case, is the jieba.win32-x64-msvc.node file in the electron asar folder.

👍You're right. Today I tried to install nodejs on the computer where the above error occurred and then recompile my application. After installing nodejs, I didn't compile it again, just ran the previous application package and found that no errors were reported. My software is running normally. 😄
But how to make the firewall not prevent nodejs from loading unsigned dll files? Is it the same as my operation above, install nodejs once? It seems a bit out of date. Because some users do not have nodejs installed on their computers. On the other hand, they don't want to install it either.

But how to make the firewall not prevent nodejs from loading unsigned dll files?

I know a way is signing the dll file with system trusted cert