[BEAM-1950] Add missing 'static' keyword to MicrobatchSource#initReaderCache

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Run Spark ValidatesRunner

R: @staslev

LGTM (pending tests).

Coverage increased (+0.007%) to 70.576% when pulling 5751c0df58a747acc9c6138dfeef45fcb5dc9ec2 on aviemzur:fix-microbatchsource-readercache-lock into 571631a5ef83ef31ea9f652c5698cea3cc95ad43 on apache:master.

Run Spark ValidatesRunner

retest this please

Coverage increased (+0.008%) to 70.576% when pulling 5751c0df58a747acc9c6138dfeef45fcb5dc9ec2 on aviemzur:fix-microbatchsource-readercache-lock into 571631a5ef83ef31ea9f652c5698cea3cc95ad43 on apache:master.

Retest this please

Coverage decreased (-0.5%) to 70.096% when pulling 5751c0df58a747acc9c6138dfeef45fcb5dc9ec2 on aviemzur:fix-microbatchsource-readercache-lock into 571631a5ef83ef31ea9f652c5698cea3cc95ad43 on apache:master.


Build new ACI based on another ACI

In https://github.com/sgotti/acido I implemented a basic way to build an ACI starting from another one with only the differences between them.
Acido depends on acirenderer #297.
I'd like to drop acido and integrate it with rocket. A workflow will be to start a container, rkt enter it, do changes and then save them to a new ACI.
Does this makes sense or will be better to keep acido as a separate project?

The workflow definitely makes sense and is something we want to provide tooling to support. I am on the fence about baking it into rkt proper. What do you have in mind? rkt save? rkt export? What would the semantics look like?
Related: https://github.com/coreos/rocket/issues/284

I'll try to summarize my idea:
A generic library to build an aci from a base one

Inputs:

An extracted ACI path (an app path inside a container, a rendered aci ecc...)
The base ACI infos (depending on the way to get differences from the base one)
The new aci manifest (it should be provided by the tool calling the library functions, it can be a modified base ACI manifest, a new manifest etc... the library doesn't need to know how it was created)

Implementation:

Get the differences (added, changed and removed files). This can be done in different ways, based on the workflow and features:

An fs differ (like the one in https://github.com/sgotti/acido/blob/master/fsdiffer/fsdiffer.go)
Use overlayfs metadata to detect changes (this can be used with #387)
Get the infos directly from the image tar without extracting it (if possible)

Modify the provided ACI manifest:

populate the pathwhitelist with the files provided by the new ACI (this handles file deletions).
Add a dependency section referencing the base ACI

Uses
Given that IMHO I'll always prefer building an ACI from a build script (like a Dockerfile) sometimes there's the need to directly modify an ACI or a running container's contents.
This library will be useful for:

appc/docker2aci#4:
A build file like a DockerFile is (if not a base layer) based on another layer so it will:

Extract the base ACI
Execute commands on it
Create the new manifest
Use the proposed library to build the new ACI

manual container changes:

rkt run app|crm
rkt enter $uuid $shell
do your changes and tests
Optionally update the new manifest
rkt save $containeruuid. This will use the proposed library to build the new ACI and save it in the cas. How the manifest is provided:

Use the actual manifest in the container app path (default):

this manifest can be previously hand edited by the user
provide some options to change the most important properties:

--version to update the version label

Provide an external manifest file (--manifest $path)

Totally hand made ACIs like something done now by acido (see https://github.com/sgotti/acido/blob/master/README.md)

PS:
I think that a rkt export command should be generally useful to export an ACI from the cas (using the GetACI function in #395). (perhaps also with an optional --squash option)

@jonboulle I implemented this proposal in https://github.com/sgotti/acibuilder, it uses https://github.com/sgotti/fsdiffer and by now you can test it with acido (https://github.com/sgotti/acido).

Super cool! I am keen for some of the diffing and building to stuff land upstream in the spec libraries, then implement this stuff in a workflow tool in Rocket.

Moving this to https://github.com/appc/acbuild
@sgotti seems like we should leverage a lot of this work you've done there?


voyager admin page redirects to laravel welcome page

Laravel Version: 5.3
Voyager Version: 0.11.10
PHP Version:
5.6.4
Database Driver & Version:
mysql 5.5.5

Description:
I can't access voyager admin page anymore. It was working before then it just stopped. Now after admin login, if I try to access it, I get redirected to laravel welcome page. Please any suggestions?
Steps To Reproduce:

Hi @AdeSamson,
What role does the user you are trying to login as have?

Sorry I didn't mention earlier. I gave it a role of admin by doing this: php artisan voyager:admin<EMAIL_ADDRESS>

This happened to me too, I had been assuming that migrate:refresh --seed was working correctly but AFAICT none of the Voyager seeders are being referenced.
[root]/seeds/DatabaseSeeder.php is blank (with the UsersTableSeeder commented out), I assume because I already had a user when I ran the voyager admin install.
Anyway, editing DatabaseSeeder to add the voyager seeders back in should work, I simply did this to get all the default Voyager data populated which fixed everything
php artisan db:seed --class=DataTypesTableSeeder php artisan db:seed --class=DataRowsTableSeeder php artisan db:seed --class=MenusTableSeeder php artisan db:seed --class=MenuItemsTableSeeder php artisan db:seed --class=RolesTableSeeder  php artisan db:seed --class=PermissionsTableSeeder php artisan db:seed --class=PermissionRoleTableSeeder

This is also happening to me :-(
I have just installed Voyager and I added admin permissions to one user with php artisan. After that first login, I was able to view the admin area. I then logged out.
When logging in again, I get redirected to my main site upon successful login.

@bealers, you're correct, we don't add the Voyager seeder to the default seeder, and adding the --seed flag to migrate:refresh doesn't let you specify what seeder class should be run.  The solution there is to either do as you've done, or add the single VoyagerDatabaseSeeder instead of the list like you've done, or just call it manually:
> php artisan migrate:refresh --seed
> php artisan db:seed --class=VoyagerDatabaseSeeder

My issue got fixed.
I'm still not sure what the original issue was, but I deleted my app's database, recreated it then ran:
php artisan migrate
php artisan db:seed --class=VoyagerDatabaseSeeder

And created my admin user again. All good.

My issue got fixed too. Thanks

tengo el mismo problema y no e podido resolverlo

Having the same issue.
Push the files into production.
Run the migration files.
Added a user with admin privileges.
Got redirected to the welcome screen.
Any advice?

Please do not comment on old issues. You can create your own or ask in the slack group

Sorry. I was aware of that. But I wasn't able to find my comment to delete it.
For the record this was a permission issue, at it was fixed by re-running voyager install on the production server after deployment.
Cheers, and, again, sorry for the inconvenience.
Marcio

after creating.. php artisan voyager:admin<EMAIL_ADDRESS>--create   . It leads to your home page or welcome page of ur laravel.. So.. bcz.. it does not have a permission on it in its voyager databases, or its behavies like this..
just.. after creating ur admin i.e (php artisan voyager:admin<EMAIL_ADDRESS>--create ).
install this: $ php artisan voyager:install
after this .. it works perfectly..
Try it.. bcz I GOT it.

@VedPrakashN, please don't comment on old issues.  The last comment here was nearly a year ago, and it's been closed for a few months longer.  It's also for a MUCH older version, which can't even be installed anymore.


Option to ignore ports in docker-compose files

When using DockerComposeContainer to launch an existing docker-compose file, Testcontainers expose random ports for the services, which can be picked up with the .getServicePort(..., ...) method.
However, if the docker-compose file includes ports definitions, Testcontainers will also expose those fixed ports, defeating the purpose of avoiding collisions by randomizing ports.
I am aware that the documentations states that "it is not necessary to define ports to be exposed in the YAML file; this would inhibit reuse/inclusion of the file in other contexts". But at the same time, DockerComposeContainer is meant to be used in situations where docker-compose files are already in use, and for me, it is convenient that those existing docker-compose files do include the port definitions.
So it would be convenient if Testcontainers could simply ignore the ports in the docker-compose files, and only expose the randomly assigned numbers. As far as I can see, this is not currently an option(?)

While we already parse Docker Compose files, we only do this for pulling the images and ultimately delegate everything else to Docker Compose, with a verbatim version of the Docker Compose file.
While I can absolutely understand this feature request from a UX perspective, I feel this is out-of-scope of DockerComposeContainer, at least for the time being.

This is the dirty workaround I'm using, posting it here in case someone else find it useful:
    public static final DockerComposeContainer<?> environment = new DockerComposeContainer(patchDockerCompose("../docker-compose.yml"));

    @SneakyThrows
    public static File patchDockerCompose(String pathName) {
        var mapper = new ObjectMapper(new YAMLFactory());
        var realDockerCompose = new File(pathName);
        var yaml = mapper.readTree(realDockerCompose);

        var services = ((ObjectNode) yaml.get("services"));
        services.elements().forEachRemaining(service -> ((ObjectNode) service).remove("ports")); // don't expose ports to the host

        var patchedFileContent = mapper.writeValueAsString(yaml);

        var modifiedDockerCompose = createTempFile("docker-compose-test-", ".yml", realDockerCompose.getParentFile());
        modifiedDockerCompose.deleteOnExit();
        return Files.writeString(modifiedDockerCompose.toPath(), patchedFileContent).toFile();
    }


ValueError when adding support for Libgcrypt 1.8.4

So right now I'm trying to add support for identification of the library libgcrypt. This time, I created a new JSON configuration file from the non-inlined and compiled version of libgcrypt. When I run karta_matcher.py on a test case for this library, it is capable of identifying libgcrypt. However, when it reaches the point of Linking the binary functions to their respective tentative files, Karta throws this exception:
C:\Users\wyin\Documents\Karta\src\karta_matcher.py: None is not in list
Traceback (most recent call last):
  File "C:\Program Files\IDA Pro 7.3\python\ida_idaapi.py", line 572, in IDAPython_ExecScript
    execfile(script, g)
  File "C:/Users/wyin/Documents/Karta/src/karta_matcher.py", line 193, in <module>
    pluginMain()
  File "C:/Users/wyin/Documents/Karta/src/karta_matcher.py", line 183, in pluginMain
    matchLibraries()
  File "C:/Users/wyin/Documents/Karta/src/karta_matcher.py", line 144, in matchLibraries
    matchLibrary(lib_name, actual_version)
  File "C:/Users/wyin/Documents/Karta/src/karta_matcher.py", line 95, in matchLibrary
    startMatch(cur_config_path, lib_name)
  File "C:/Users/wyin/Documents/Karta/src/karta_matcher.py", line 60, in startMatch
    matching_engine.locateFileBoundaries()
  File "C:/Users/wyin/Documents/Karta/src\core\matching_engine.py", line 587, in locateFileBoundaries
    file_match = file_class(file_name, src_start_index, src_end_index, local_bins_ctx, local_bin_start_index, local_bin_end_index, src_end_index - src_start_index + 1, self)
  File "C:/Users/wyin/Documents/Karta/src\file_layer.py", line 29, in __init__
    super(FileMatcher, self).__init__(name, src_index_start, src_index_end, fuzzy_bin_functions_ctx, bin_limit_lower, bin_limit_upper, src_scope, engine)
  File "C:/Users/wyin/Documents/Karta/src\core\file_layer.py", line 142, in __init__
    bin_range = range(self._bin_functions_ctx.index(self._lower_match_ctx), self._bin_functions_ctx.index(self._upper_match_ctx) + 1)
ValueError: None is not in list

Again, the identification script I'm using for libgcrypt is just a slightly edited version of the identification script for zlib. I'm running Karta on IDA Pro 7.3
Do you know what could be causing this error and what I can do to fix it?

The only option in which self._lower_match_ctx will be None and/or self._upper_match_ctx will be None is in the case that the binary file will be marked as located but with size of 0 function. It looks like the for loop preform no iterations and this is why the contexts won't get initialized.
I can better handle this error case on my side, however I still want to know why the binary file looks empty. Can you post the number of functions in each src file, and the len(self._bin_functions_ctx) at the beginning of this function? Maybe the compilation of your configuration file contained errors / wasn't without optimizations

Thanks for the quick response, these are the function counts(extracted from the JSON config file) for each of the source files used:

dumpsexp-dumpsexp.o is 16
hmac256-hmac256.o is 10
mpicalc-mpicalc.o is 21
.libs\hwf-x86.o is 5
.libs\libgcrypt_la-context.o is 4
.libs\libgcrypt_la-fips.o is 23
.libs\libgcrypt_la-global.o is 35
.libs\libgcrypt_la-hmac256.o is 8
.libs\libgcrypt_la-hwfeatures.o is 5
.libs\libgcrypt_la-misc.o is 26
.libs\libgcrypt_la-secmem.o is 24
.libs\libgcrypt_la-sexp.o is 41
.libs\libgcrypt_la-stdmem.o is 6
.libs\libgcrypt_la-visibility.o is 217
When I try to obtain the length of self._bin_functions_ctx, I still get ValueError: None is not in list. The command I used to run karta_analyze_src.py is python karta_analyze_src.py libpython 2.7.0 C:/Users/wyin/Documents/libpython C:/Users/wyin/Documents/libpython/libpython2.7.a. When I compiled the makefile for libgcrypt, I changed the CFLAGS from -g -O2 -fvisibility=hidden -fno-delete-null-pointer-checks -Wall to -g -O0 -fno-inline-functions -fno-builtin -fno-delete-null-pointer-checks -Wall and the CCASFLAGS from -g -O2 to -g -O2 fno-inline-functions -fno-builtin -fno-delete-null-pointer-checks. I've attached the makefile and the JSON configuration file below. Are there any optimizations or issues with the way I'm making the JSON config file?

Makefile.zip
libgcrypt_1.8.4.zip

Added a commit to better handle this edge case, including clearer logs so the relevant file will be shown too.
We had similar errors in the past when IDA's analysis wasn't perfect / missed a few functions. My suggestion is to check again if you can help IDA better detect all of the functions - even functions without xrefs should be marked as functions so Karta will work as intended. I recommend using Thumbs Up: https://karta.readthedocs.io/en/latest/Thumbs Up.html

Closing for now.
If the fix didn't solve the issue, feel free to re-open the ticket.


Add documentation

It will be great to have a detailed documentation that covers directory structure, app functionalities. This will really help new users to be able to grasp your work easily.

Hi!
Most of this is already covered in the readme. As for the functionality abilities, then they can be found in the repository, which contains the spec for this backend.

Closed as stale. If anyone still wants to submit a PR with that, they can safely do so, although I'll archive this repository soon, so I'm not sure if it will be useful.


feat: add gas estimation to the signer

The eventual goal is to have the signer be able to automatically estimate gas

Blocked on https://github.com/celestiaorg/cosmos-sdk/pull/371

Does estimation add a roundtrip?

Does estimation add a roundtrip?

Yes it would


Question about gt_sampling

Hi,
My understanding of gt_sampling is that it addresses the class imbalance by over-sampling some of the less frequent classes. If this understanding is correct, why do models like voxel_rcnn_car use gt_sampling when it is only training on the car?
Since it's only focusing on the "car" class, does it have any noticeable improvement when using gt_sampling vs not using gt_sampling?

Hi @darrenjkt ,
I believe it's not a matter of fighting class imbalance, but foreground/background points imbalance. It was introduced in  SECOND: Sparsely Embedded Convolutional Detection  object detector:

The major problem we encountered during training was the existence of too few ground truths,
which significantly limited the convergence speed and final performance of the network. To solve this
problem, we introduced a data augmentation approach. First, we generated a database containing
the labels of all ground truths and their associated point cloud data (points inside the 3D bounding
boxes of the ground truths) from the training dataset. Then, during training, we randomly selected
several ground truths from this database and introduced them into the current training point cloud
via concatenation. Using this approach, we could greatly increase the number of ground truths per
point cloud and simulate objects existing in different environments. To avoid physically impossible
outcomes, we performed a collision test after sampling the ground truths and removed any sampled
objects that collided with other objects.

In fact, this is really powerful data augmentation technique, and you can see how much improvement it gives in @MartinHahner 's paper: Quantifying Data Augmentation for LiDAR based 3D Object Detection

I see that makes sense. Thanks for clarifying this gap in my knowledge and for showing me where to find more information.


Documentation updates

Resolves #408 , #409
Added basic documentation for mapper configuration, removed references to email-verification - now there is a dependency on the BC Wallet Showcase to obtain a demo credential.

Not sure why but tore everything down, got this branch and built fresh, and in the demo app to test I see
{"detail":"The requested verifier configuration wasn't found"}
controller-1     | parsed authentication_request: {'scope': 'openid vc_authn', 'state': '3pe-BXt864Px6-s_2cFS72HOklrThn-YyHCtZTN2aPE.o10se4o3qBM.T02DEr3QRTmMUfjegc9fQQ', 'response_type': 'code', 'client_id': 'keycloak', 'redirect_uri': 'http://localhost:8880/auth/realms/vc-authn/broker/vc-authn/endpoint', 'pres_req_conf_id': 'verified-email', 'nonce': 'XLFrocwUntjzMOueovYGVQ'}

Api is still getting a verified-email request from somewhere but I can't find it yet...


NIFI-1423 Allow to penalize FlowFiles to No Retry

+1

I believe flowfiles should be removed from the penalized list when MockProcessSession.remove() is called: https://github.com/apache/nifi/blob/fd35b8ffd7d4a66ef149c1bd1341dfee3ede80c7/nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java#L430

When MockProcessSession.rollback(boolean)[1] is called it is, the boolean is telling the session whether or not the flowfiles should be penalized. In the event the boolean is true if the session shouldn't it clear the penalized list then add all the flowfiles to the list?
[1] https://github.com/apache/nifi/blob/fd35b8ffd7d4a66ef149c1bd1341dfee3ede80c7/nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java#L522-L522

I know this isn't part of the ticket but, there are numerous lines in the unit tests that say " // getMyFlowFiles();". I believe they're relicts from before the refactor. Could you remove them in this commit?

Did a maven contrib check build and verified the functionality using a test http server. Once the comments are addressed I can merge in.

Agree with @JPercivall regarding the rollback to be able to get a full handle on rolled back files for a given session/execution to understand how the processor behaved.  Scanning through the codebase, these are a minority of usages and typically would only get invoked when there is a dev issue causing exceptions, but could see it getting more usage within AbstractionSessionFactory based processors where that functionality could be preferred.  Seems like a quick effort for consistency.

All very valid points there, I'll have a look at them.
The merge request will be updated with the fixes soon and will also be up-to-date with the current master

I've pushed the new version that includes all the fixes for the comments above.
Contrib check done and up-to-date to master.


docs: Miscellaneous fixes

Pull Request Checklist

[x] New code has 100% test coverage
[x] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[x] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR

Description

Miscellaneous typo and punctuation fixes.
Adjusted emphasized lines of example code blocks in the tutorials; many were misaligned most likely due to changes to the underlying .py files which were not reflected in the docs.
Modified descriptions of SQLAlchemy repository functions in the docs to be more consistent with each other.
Updated links to external Real Python articles to use hyperlinked article names instead of raw URLs.
No code changes, pre-commit was run before pushing.


After updating, get axios version error

I have updated the bot using git pull and I am now receiving the following error:
Unsupported "axios" version!.
Please delete your "node_modules" and "package-lock.json".
And restart the bot.
Please make sure to check and remove "npm install" command from your startup params.

I have also tried deleting the entire bot, recloning the repository and I still get the same error.

try manually install axios:
npm install<EMAIL_ADDRESS>

Yep, that worked! Thank you.


Default export

https://github.com/buz-zard/postcss-stats/issues/11

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cannot augment UMD module definition if the global variable name is different than module name

Bug Report
🔎 Search Terms
module UMD augmentation name variable export declare
🕗 Version & Regression Information
This is the behavior in every version I tried, and I reviewed the FAQ for entries about declaration merging
⏯ Playground Link
Not working example:
// @allowJs: false

// @filename<EMAIL_ADDRESS>declare namespace awesomeness {
  interface AwesomenessApi {
    base(): void;
  }
}
declare var awesomenessModule: awesomeness.AwesomenessApi;
export = awesomenessModule;

// @filename: src/augs.d.ts
import 'awesomeness';
declare module 'awesomeness' {
  interface AwesomenessApi {
    aug(): void;
  }
}

// @filename: src/app.ts
import * as awesomeness from 'awesomeness';
awesomeness.base();
awesomeness.aug();

Workbench Repro
Working example:
(The only difference is at lines 9-10)
// @allowJs: false

// @filename<EMAIL_ADDRESS>declare namespace awesomeness {
  interface AwesomenessApi {
    base(): void;
  }
}
declare var awesomeness: awesomeness.AwesomenessApi;
export = awesomeness;

// @filename: src/augs.d.ts
import 'awesomeness';
declare module 'awesomeness' {
  interface AwesomenessApi {
    aug(): void;
  }
}

// @filename: src/app.ts
import * as awesomeness from 'awesomeness';
awesomeness.base();
awesomeness.aug();

Workbench Repro
🙁 Actual behavior
You can perform augmentation of UMD module definitions only if the global variable's name used for export matches the name of the module (i.e. folder in node-modules). I also tried changing declare module 'awesomeness' to declare module 'awesomenessModule', so that the module itself can be resolved, with no luck.
It is possible that this is intended behavior, I've missed something or alike. In that case, how can I force the code above to work (as I obviously cannot modify original module definition)?

The original module is, perhaps intentionally, written in a way that prevents augmentation because there's no accessible name by which to augment AwesomnessApi. The impact-free fix in the upstream declaration is to write it this way (note that the module name is not really relevant here):
// @allowJs: false
// @skipLibCheck: false

// @filename<EMAIL_ADDRESS>declare namespace awesomenessModule {
  interface AwesomenessApi {
    base(): void;
  }
}
declare var awesomenessModule: awesomenessModule.AwesomenessApi;
export = awesomenessModule;

// @filename: src/augs.d.ts
import awesomeness = require("awesomeness");
declare module "awesomeness" {
  interface AwesomenessApi {
    aug(): void;
  }
}

// @filename: src/app.ts
/// <reference path="./augs.d.ts" />
import * as awesomeness from 'awesomeness';
awesomeness.base();
awesomeness.aug();

The original module is, perhaps intentionally, written in a way that prevents augmentation because there's no accessible name by which to augment AwesomnessApi. The impact-free fix in the upstream declaration is to write it this way (note that the module name is not really relevant here):
// @allowJs: false
// @skipLibCheck: false

// @filename<EMAIL_ADDRESS>declare namespace awesomenessModule {
  interface AwesomenessApi {
    base(): void;
  }
}
declare var awesomenessModule: awesomenessModule.AwesomenessApi;
export = awesomenessModule;

// @filename: src/augs.d.ts
import awesomeness = require("awesomeness");
declare module "awesomeness" {
  interface AwesomenessApi {
    aug(): void;
  }
}

// @filename: src/app.ts
/// <reference path="./augs.d.ts" />
import * as awesomeness from 'awesomeness';
awesomeness.base();
awesomeness.aug();

Ok, so if it is intended (or just known), is it stated somewhere that the module name must match the variable? Because it took me quite more than quite a lot of time to figure this out. Ideally it'd be nice if there was a warning of some kind but I'd assume this is too niche of a scenario for that. On the other hand, module authors might not be aware of this requirement on their side.
I also assume you just can't make it work for some many internal and compatibility issues, which I'm fine with.

// @filename<EMAIL_ADDRESS>declare namespace awesomenessModule {
  interface AwesomenessApi {
    base(): void;
  }
}

You just changed the namespace in the upstream, right? Then that won't resolve the issue. Fortunately the module in question just got a fix for that (renamed a var); I'm asking just in case someone else or I come to this situation again.

Ok, so if it is intended (or just known), is it stated somewhere that the module name must match the variable? Because it took me quite more than quite a lot of time to figure this out. Ideally it'd be nice if there was a warning of some kind but I'd assume this is too niche of a scenario for that. On the other hand, module authors might not be aware of this requirement on their side.
I also assume you just can't make it work for some many internal and compatibility issues, which I'm fine with.

// @filename<EMAIL_ADDRESS>declare namespace awesomenessModule {
  interface AwesomenessApi {
    base(): void;
  }
}

You just changed the namespace in the upstream, right? Then that won't resolve the issue. Fortunately the module in question just got a fix for that (renamed a var); I'm asking just in case someone else or I come to this situation again.

They don't "have to match"; it's simply a consequence of the definition of what export =  means and the fact that augmentation can only function on exported identities (which is a logical consequence of non-exported entities being opaque, by design). It's like if I said "You can take all the blue things out of this box" and then you wanted something from the box that was red - it's not an error or even suspicious to not have all things be blue, and it's not an error or even suspicious to restrict takings to a specific color.
There's nothing wrong with the declaration file as written per se, and again, the author may have written it that way on purpose.

They don't "have to match"; it's simply a consequence of the definition of what export =  means and the fact that augmentation can only function on exported identities (which is a logical consequence of non-exported entities being opaque, by design). It's like if I said "You can take all the blue things out of this box" and then you wanted something from the box that was red - it's not an error or even suspicious to not have all things be blue, and it's not an error or even suspicious to restrict takings to a specific color.
There's nothing wrong with the declaration file as written per se, and again, the author may have written it that way on purpose.


dotnetCorePackages.fetchNupkg: override avalonia to include upstream fix

Description of changes
Backport https://github.com/AvaloniaUI/Avalonia/pull/16835 to versions 11.1.0 through 11.2.0-beta1
These versions have a runtime error when built with dotnet publish --no-build. When attempting to draw a window, Avalonia will throw "No precompiled XAML found".
Upstream

Introduced in https://github.com/AvaloniaUI/Avalonia/pull/13840
Fixed by https://github.com/AvaloniaUI/Avalonia/pull/16835

Packages affected

Affects retrospy since https://github.com/NixOS/nixpkgs/pull/338143
Will affect nexusmods-app; has been blocking https://github.com/NixOS/nixpkgs/pull/331150

AFAICT these are the only affected packages in nixpkgs, but I included the list of affected release versions anyway to avoid regressions when updating other packages and to aid anyone using nixpkg's dotnet built-support functions outside of nixpkgs.
See https://github.com/NixOS/nixpkgs/pull/331150#discussion_r1749031290 where this was originally discussed.
cc @corngood @Naxdy @NickCao

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

retrospy


Create PvMRandomize

Randomize PvM drops, if you get a whip as a drop it may unlock ability to use bandos tassets but you cannot use the whip until you get the item that unlocks it.

This appears to just be the example plugin with names changed in a handful of places. Please don't submit things to the hub before you've actually written them.

I think this plugin uses your imagination to function. It's fully functional as is.


CI tries to run non-existent script in 2.1 branch

Description

Type: Bug
Priority: Blocker

Bug
OS
Any.
mbed TLS build:
Version: 2.1.x branch
Expected behavior
The CI succeeds.
Actual behavior
The CI fails due to trying to run non-existent test script tests/scripts/doxygen.sh
For example: https://jenkins-internal.mbed.com/job/mbedtls-restricted-pr/384/execution/node/293/log/
Steps to reproduce
Was observed in this restricted PR: https://github.com/ARMmbed/mbedtls-restricted/pull/509

Suggested fix: let's backport that test script to the 2.1 branch!

ARM Internal Ref: IOTSSL-2515

PR #2011 has now been merged, so this issue is fixed and can be closed.
As an aside - this wasn't the only possible fix! We could have selectively chosen to execute tests/scripts/doxygen.sh based on which branch we were executing from. I think this was the best option, but it wasn't the only option, and we should be careful about backporting features for the sake of the CI.


Update CCG boundaries and fix import

This updates the test fixture to use the latest CCG boundaries, obtained using this script.
It also fixes the import so that it updates the org models in-place rather than replacing them and contains some workarounds for a nasty GDAL incompatibility.

Great. Is there somewhere we could make some nice public acknowledgements for the NHSX pals who helped out here?

Also I think the whole docstring in the management commands describing the manual rigmarole could be replaced by a link to that fetcher script?

Is there somewhere we could make some nice public acknowledgements for the NHSX pals who helped out here?

Yes, happy to but not sure where. I'll update the original issue once this is deployed and the boundaries imported.


gh-1995 Include io.github.classgraph:classgraph in Accumulo iterator JAR

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


Add testing of controllers

These tests look at searchController and LandingController

@sndsgn @dutchers @PhongHPham if one of you wants to merge this in - testing the controllers (some of them)

I will merge it in.
On Fri, Oct 2, 2015 at 3:37 PM, Aaron Norby<EMAIL_ADDRESS>wrote:

@sndsgn https://github.com/sndsgn @dutchers
https://github.com/dutchers @PhongHPham https://github.com/PhongHPham
if one of you wants to merge this in - testing the controllers (some of
them)
—
Reply to this email directly or view it on GitHub
https://github.com/visceral-tambourine/visceral-tambourine/pull/77#issuecomment-145172590
.

Looks good.

@aaronnorby, nice one, doc !


Compile webcam.swf with flexsdk

Hi,
Can you provide a method to compile webcam.swf by flex sdk by command line (with mxmlc or compc) ?
Thank you,
Boris

I'm sorry, but I don't know anything about Flex, nor the tools you mention.  I wouldn't have the foggiest clue how to do that.  Perhaps the community can come up with something, and offer a pull request?

To make this work I had to change mx to mx2. Details on this part:
First I changed mx directory to mx2, edited mx2/utils/Base64Encoder.as and change mx.utils to mx2.utils. Also changed import mx.utils.Base64Encoderto mx2.utils.base64Encoder in Webcam.as.
(The reason why rename is required to mx2 is to make mxmlc load this file, and not the one in frameworks.swc which I don't know how to link, and I don't want to because it may increase library size.)
After that, assuming you have Flex SDK installed (I used 4.5) and mxmlc command is in your path:
$ mxmlc  Webcam.as -debug=true -output webcam.swf
Here's info how to install Flex SDK:
$ mkdir ~/flex_sdk_4.5
$ cd ~/flex_sdk_4.5
$ wget http://download.macromedia.com/pub/flex/sdk/flex_sdk_4.5.zip
$ unzip flex_sdk_4.5.zip
$ rm flex_sdk_4.5.zip
$ export PATH=~/flex_sdk_4.5/bin:$PATH
$ export FLEX_HOME=~/flex_sdk_4.5

Then I also had to edit by hand ~/flex_sdk_4.5/frameworks/flex-config.xml and change:
      <external-library-path>
          <path-element>libs/player/{targetPlayerMajorVersion}.{targetPlayerMinorVersion}/playerglobal.swc</path-element>
      </external-library-path>

to,
      <external-library-path>
          <path-element>libs/player/{targetPlayerMajorVersion}.2/playerglobal.swc</path-element>
      </external-library-path>

Note that you my not need to do this step.


Update rollbar.js snippet to 1.9.3

@jondeandres there are some failing tests in Travis. Can you take a look?

@coryvirok tests are passing now. we want to merge this or we would be interested on pushing rollbar js 2.x? @rokob ?

Let's push the latest rollbar.js. It should be backwards compatible with 1.9.x.

Ok, I opened https://github.com/rollbar/rollbar-gem/pull/600 for that


IE11 Compatibility

Do you still supporting IE11? Some components and functions is not working in IE11.

Hello @iHunt101,
Thank you for your interest in working with our products, please provide more details about this issue, we have updated the product so please check again.
All the best,
Stefan


Updated sharp version

Fixed conflicting sharp versions when using PNPM

You can use new sharp version installing the dependency in your app (or use resolutions, depending on your package manager).
Anyway, you also need to send pnpm lock file.


how to use AtomicShared when Ptr is not send

I am trying to integrate AtomicShared in my codebase, however creating an async function and spawning it in a thread is impossible when Ptr is !Send.

Unfortunately, Ptr can never be Send since it relies on its thread-local storage to pin the referenced instance in memory; that's what epoch-based reclamation is for: same applies to Guard.
In order to send a reference to the data, you'll have to make Shared out of AtomicShared through AtomicShared::get_shared. Shared holds a strong reference to the instance, so it can be sent across threads and awaits.
Hope this explanation helps you!

Please add more examples in the examples folder.

In short, Ptr and Guard cannot be sent across await and spawn.

I'll enhance the examples, but you'll be able to find a lot of resources on the internet for crossbeam_epoch. scc::ebr is a subset of crossbeam_epoch (though the implementation is substantially different) + reference counting for easier use.

Updated examples in https://github.com/wvwwvwwv/scalable-delayed-dealloc/


C3 refactor

Pull MS API call from client to server side
Update UI to show enrollment status

Maybe use AZURE_COGNITIVE_SERVICE_KEY and AZURE_COGNITIVE_SERVICE_ENDPOINT? I feel like MS_API_KEY is too general. Otherwise LGTM.


Making formatQuery handle string operators like "contains" and "begins with"

Hello everyone,
I am using react-querybuilder and I noticed that the formatQuery function does not handle some operators like "contains" or "begins with".
I want to format the query in sql. I read in the documentation that I can use the valueProcessor argument to process the value but for the operators mentioned above, the corresponding operator in sql is the same (like). I want to add a fix in the formatQuery function by adding cases in processRule.
Can I open a PR ?
Thanks in advance for your reply.

@oumar-sh absolutely feel free to open a PR if you have a fix or enhancement in mind.

Thank you. I opened the PR #111

Hello @jakeboone02 , could you please make a quick review of my pull request please ?
Thank you.


Update default delay.

This PR fixes #9046.
It sets a default delay of 5s, also it updates customs delays to 5s declared in some views.
cc @xavijam

Fine by me! :es:


Configuration File Location?

When configure is first run
Example:
passbolt configure --serverAddress https://passbolt.example.org --userPassword '1234' --userPrivateKeyFile 'keys/privatekey.asc'
Where is the local configuration file stored?

By default, a subfolder for go-passbolt-cli is created in your OS's Application Configuration Folder in which the config file is created.
To determine this Folder Go's  "os.UserConfigDir" is used. Its Documentation States:

On Unix systems, it returns $XDG_CONFIG_HOME as specified by https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html if non-empty, else $HOME/.config. On Darwin, it returns $HOME/Library/Application Support. On Windows, it returns %AppData%. On Plan 9, it returns $home/lib.

So on Linux it would Typically be ~/.config/go-passbolt-cli/go-passbolt-cli.toml.
Since this config contains sensitive information it uses a 600 Permission Mask.
You can override this location using the --config parameter.
You can see the logic here.

Thank you @speatzle for the quick response.
I installed go-passbolt-cli on MacOS using go and couldn't find anything in my $HOME.
So i did a ~$ find / -name go-passbolt-cli and can you guess where i found the go-passbolt-cli.toml?..
In /System/Volumes/Data/Users/$USER/Library/Application Support/go-passbolt-cli/go-passbolt-cli.toml of all places...
Thanks again.

@Stenstromen, that path is the long form for ~/Library/Application\ Support/go-passbolt-cli/go-passbolt-cli.toml.
What scared me though, is seeing that this just stores both the userprivatekey and its passphrase in plaintext. The file appears to have mode 0600 by default, so by understatement it's not blatantly unsafe, but still...
At least the javascript client just relied on provengpg architecture to manage this stuff.

Hey @cueedee,
go-passbolt-cli is "just" a wrapper around go-passbolt and in the beginning was for testing go-passbolt but evolved over time into a usable project.
Since go-passbolt is made to be portable and not depend on anything external, go-passbolt-cli can't really use gnupg without major modifications.
From what i have seen, go-passbolt-cli is mostly used in scripts without any direct user interaction which means that the Script or go-passbolt-cli need to be able to retrieve the Private Key and Password by themself in which case "gpg infrastructure" is just as safe as a file that only the user can access.
You can also just store the Private Key without the Password and go-passbolt-cli will Prompt you for the Password each time, the same applies to MFA. The Passbolt Browser Extension also just stores the Private Key in the Browser, so the Security level is the exact same in that case.
Using the Config is completely optional as stated in the README.md and you can instead specify everything using Environment Variable or Flags Instead.
As such i don't see how this is unsafe.


[ Layer copy ] copy function for conv2d & pooling

This PR fixs the copy member function of covn2d and pooling layer.
. include copy of layer varaibles for conv2d
. implemnet copy of pooling2d layer
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #176. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.


Xbox Signin (UWP) - when signed in elsewhere

I have a Unity game with Xbox Live & Azure PlayFab working - building a UWP app and deploying to Xbox in dev mode.
Everything seems good except for one scenario that is crashing the xbox app ...
if I logon to my PC and start the game - so the game is logged on with my Gamertag.
if I then start the Xbox version - it seems to be crashing in the Signin.  (as part of crashing it signs the user out of the xbox)
Should the Xbox version be able to detect that the user is logged in elsewhere - and offer the user the opportunity to sign out from elsewhere.
how best should I handle this case ?   thx for any pointers

                SignInResult signInSilentResult = await xlu.SignInSilentlyAsync(m_uiDispatcher);

                LogLine("XboxAuthentication signInSilentResult: " + signInSilentResult.Status.ToString() );

                switch (signInSilentResult.Status)
                {
                    case SignInStatus.Success:
                        strXboxGamertag = xlu.Gamertag;
                        LogLine("XboxAuthentication silent sucesss : " + strXboxGamertag);
                        await Task.Run(() =>
                        {
                           XboxLoginGetToken(xlu);
                        });
                        break;
                    case SignInStatus.UserInteractionRequired:
                        LogLine("XboxAuthentication user interaction");

                        SignInResult signInLoud = await xlu.SignInAsync(m_uiDispatcher);
                        LogLine("XboxAuthentication user interaction: " + signInLoud.Status.ToString() );
                        switch (signInLoud.Status)
                        {
                            case SignInStatus.Success:
                                strXboxGamertag = xlu.Gamertag;
                                LogLine("XboxAuthentication loud sucesss: " + strXboxGamertag);
                                await Task.Run(() =>
                                {
                                   XboxLoginGetToken(xlu);
                                });
                                break;
                            case SignInStatus.UserCancel:
                                LogLine("XboxAuthentication cancel");
                                bXboxLoginComplete = true;
                                break;
                            default:
                                break;
                        }
                        break;
                    default:
                        break;

-Mark

Solution seems to be use GDK not UWP


[BUG] POST /conversation/related-documents 500 in local

Describe the bug
In local development the POST  /conversation/related-documents route throw a 500 , in the local UI, ( like a timeout or so) even having filled in the env variables ( DB_NAME, DB_USER, DB_PASSWORD, DB_PORT). Am I missing something about this ?
To Reproduce
Set all the env var according to the local development backend and frontend Readme.
VITE_APP_API_ENDPOINT pointing on the local python backend.
And exporting all the env vars according to the backend local dev README +  DB_NAME, DB_USER, DB_PASSWORD, DB_PORT.
Backend is plug to AWS services and nothing in local ( Nor Docker, Postgres or anything) pointing straight out to AWS services.
1.Launch local UI.
2.Ask a question ( for a RAG answer)
Network console show a 500 on the /conversation/related-documents route
Can't create a connection to host xxxxxxxxxxxxxx and port xxxxxxxx( timeout is None and Source address is None)

Because the aurora database is on the private subnets, which is not allowed to access from outside of the vpc.
To test functionality related to aurora, we need to add bastion as a proxy.

@statefb Thank you for the explanation.

@ClementVanPeuter Your welcome, let me close the issue

Hey guys, I'm having the same issue for production. Can anyone suggest the fix? thanks


Explicitly call exthosttelemetry on command failure

Fixes #172132

FYI @jrieken I removed a duplicate test and merged another one because there was warnings about them in the editor. Feel free to revert that if you don't want those changes since I was just cleaning up while in the area.

Integration tests failing

Integration tests failing

Yeah waiting to hear back from @jrieken about possible thoughts. The IExtHostTelemetry initiates RPC messages to sync the levels across processes so now by adding it to a dependency of commands there is an RPC message that goes through when the service is instantiated that wasn't there before. It's just 1 so not really a perf issue, but we were asserting no RPC messages at all before.


core: add filter to clear the headers route cache when direct responses are specified

On Envoy Mobile, the primary use case for direct responses is being able to write integration tests against the library (i.e., by starting an instance of Envoy Mobile, configuring it with filters, and performing requests through the library that receive direct responses mocked via config).
However, this can result in a routing bug in the following scenario:

Envoy is started with a configuration that contains a direct response with a header match
Request is sent that does not meet the header match criteria
Internally, Envoy computes the route for this request before invoking the filter chain
Filter chain gets invoked, and a filter modifies the request headers in a way that makes the request meet the route header match criteria
Request 404s because routing was done before the headers were mutated, even though those headers were mutated before the router filter was invoked

To get around this, Envoy provides the ability for filters to reset the route cache for an individual stream. This is only necessary for our purposes when direct responses are used in the library, and we should avoid unnecessarily resetting this cache. The easiest way to go about solving this problem is to add a filter to clear the stream's route cache when direct responses are specified in the Envoy Mobile config.

https://github.com/envoyproxy/envoy-mobile/pull/1298


Fix incomplete Windows support of MultiSpawnServer

This commit intents to fix the following issues of Fluentd:

https://github.com/fluent/fluentd/issues/3066: Unexpected error Broken pipe when trying to shutdown fluentd with multiple workers
https://github.com/fluent/fluentd/pull/3131: Add win32 events alternative to unix signals

Current implementation of MultiSpawnServer has following issues. This PR fixes these them:

multiple workers feature isn't supported correctly on Windows
graceful stop & restart aren't supported on Windows
reload commands isn't supported on Windows

In addition, this PR also fixes default behavior of stop and restart methods of MultiSpawnServer.
They do nothing by default because these methods expect that auto_tick is enabled although MultiSpawnServer disables it by default. When auto_tick is disabled, users of this class will expect that it sends a signal (or command) immediately.
(If you don't want to change this behavior, I'll remove this commit.)

Test failed. Could you check it?

In addition, this PR also fixes default behavior of stop and restart methods of MultiSpawnServer.
They do nothing by default because these methods expect that auto_tick is enabled although MultiSpawnServer disables it by default. When auto_tick is disabled, users of this class will expect that it sends a signal (or command) immediately.

I misunderstood it. tick method of ProccessManager is called in run method of MultiWorkerServer.
Although tick isn't called on Windows, it's caused by another reason.
To implement graceful stop for Windows instead, I'll add another fix.

I'll remove this commit so that failed tests will be fixed.
To implement graceful stop for Windows instead, I'll add another fix.

I've pushed the fix.

Thanks!

Thanks! BTW there are few tests for MultiSpawServer, I'm considering add more tests.


feat(network): verify chain id during protocol handshake

What this PR does / why we need it:
This PR redesign identify protocol handshake to support chain id verification.
Below is basic handshake flow:

client send its identity to server
server verify it then send back an acknowledge
client verify it then open other protocols

This PR also add new UnidentifiedSession event to peer manager. When tentacle throw out new session, this
new event is created and hold inside peer manager. Peer manager will register an wait future through identify
protocol. This future will get resolved when peer finish identify protocol handshake. After it, original NewSession is fired, and peers are connected.
Special Note:
The main handshake logic is reside in identify/protocol.rs.
Which issue(s) this PR fixes:

Fixes #
Which docs this PR relation:
Ref #
DOC PR
Which toolchain this PR adaption:
No Breaking Change
Special notes for your reviewer:

/test chaos

/test chaos

/test chaos

/lgtm


Better ToC everywhere

Now that we have a nice ToC generator, should we add it as a sidebar element to all pages with a handwritten ToC (e.g. /stats, /tools)?

Sounds good! Note that I would quite like to reorganise the tools docs / all docs generally: https://github.com/nf-core/tools/issues/670 https://github.com/nf-core/nf-co.re/issues/352 so the pages may be affected by that work. But no reason not to have sidebar navs generally I guess..?
Could maybe have a test to check for the length of the page if markdown, plus a variable to enable manually. That's how auto-ToCs work with Hugo and it's quite nice.


New HTML parser

This closes most of the issues we had with the HTML parser, and reorganizes the entire thing.

I think I addressed all of your comments, @chrishtr. Here's a few things it would be good to have your comment on before calling this done:

Right now print_tree is not actually a pretty-printer—it adds quotes and doesn't print close tags. I should rewrite it to actually pretty print, right?
Is the syntax highlighting exercise still doable? I like it quite a bit, but the lexer is now bound very tightly to the parser, so I'm not sure it's still doable.
I'm going to do some automated testing on the parser using your Chrome debugging tools branch before committing. There might be easy ways to improve compliance.

I think I addressed all of your comments, @chrishtr. Here's a few things it would be good to have your comment on before calling this done:

Right now print_tree is not actually a pretty-printer—it adds quotes and doesn't print close tags. I should rewrite it to actually pretty print, right?
Is the syntax highlighting exercise still doable? I like it quite a bit, but the lexer is now bound very tightly to the parser, so I'm not sure it's still doable.
I'm going to do some automated testing on the parser using your Chrome debugging tools branch before committing. There might be easy ways to improve compliance.

If the comments are addressed then LGTM!
Pretty print: Yes it should pretty-print and match the output from the node script.
Syntax highlighting: why is it not still doable exactly? I think it should be possible with a little more refactoring or some choice lines of code?

If the comments are addressed then LGTM!
Pretty print: Yes it should pretty-print and match the output from the node script.
Syntax highlighting: why is it not still doable exactly? I think it should be possible with a little more refactoring or some choice lines of code?

It's doable but I think you'll need to copy-and-paste the lexer. And if you want to highlight attribute values separately then you'll need to merge it with get_attributes. Instead of reusing the lexer directly. That might be fine—I do like the syntax highlighting exercise.

It's doable but I think you'll need to copy-and-paste the lexer. And if you want to highlight attribute values separately then you'll need to merge it with get_attributes. Instead of reusing the lexer directly. That might be fine—I do like the syntax highlighting exercise.

I think it's ok; let's put a task for us to do the exercises ourselves and verify how hard it is. We could make some small changes to the chapter code to make it a bit easier.

I think it's ok; let's put a task for us to do the exercises ourselves and verify how hard it is. We could make some small changes to the chapter code to make it a bit easier.

Ok, I've done several passes over the text and it looks good. I've also tested against the Chrome parser and it works well enough on well behaved pages—that's probably all we can promise. I'm ready to ship.

The upper-case code was in the pretty-printer, not the parser, luckily. I added it so I could test against the headless Chrome, but in retrospect it's better for the case-conversion code to live in that script, not in the book's code.

Please merge if you think this is ready!


Please merge revision #33f360cc38c23d82ee0c02a9792466062f3225cf into dev channel

@whesse @mit-mit @kasperl
Reverts Stream.groupBy.
Merge revision 33f360cc38c23d82ee0c02a9792466062f3225cf.
This did not merge cleanly. Use the following patch instead:
https://codereview.chromium.org/2914053003

Merged in 1.24.0-dev.6.6


Collections-817: Reworked calculations and updated javadoc for estimateN(), estimateIntersection() and estimateUnion()

Fix for COLLECTIONS-817
Issue was converting Converting Double to Int.  Solution is to document the calculations.  Shape returns the double for estimateN() while BloomFilter does some other checks and returns a rounded int solution.
Added documentation concerning n(), intersection, and union calculations in Shape class.
Modified BloomFilter.estimatedIntersection() to account for infinite values in calculations.

@aherbert I can not figure out why the checks are failing.  It looks like the code the checks are using is out of sync with the actual code base.  Do you have any suggestions for how to fix this?

The git diff line for AbstractBloomFilterTest:291 does not match the compile error on the CI build. So I cannot see what is wrong. Since there are new changes in master if you rebase and force push then it may fix the issue using a new base for the diff.

The only way to generate a NaN ins the BloomFilter.estimateIntersection() is with a broken cardinality.  Test case was added.

Codecov Report

Merging #358 (795218a) into master (9bbfad5) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #358      +/-   ##
============================================
+ Coverage     81.17%   81.20%   +0.03%
- Complexity     4603     4613      +10
============================================
  Files           289      289
  Lines         13452    13473      +21
  Branches       1979     1987       +8
============================================
+ Hits          10919    10941      +22
  Misses         1935     1935
+ Partials        598      597       -1

Impacted Files
Coverage Δ

...apache/commons/collections4/bloomfilter/Shape.java
100.00% <ø> (ø)

.../commons/collections4/bloomfilter/BloomFilter.java
100.00% <100.00%> (+5.88%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Language tagged strings and i18n

I noticed that language tagged strings are already supported internally in Cayley. It would be nice to be able to use this functionality through the HTTP APIs somehow (mostly Gizmo and GraphQL). I'm not entirely sure yet what would be the best way to include this. I would think it work somewhat similarly to the labeled sub-graphs, so I could imagine a Lang directive for Gizmo and a @lang and @language directive for GraphQL (similar to what I proposed in #614). Maybe it makes more sense though to have it work like the @opt directive where it doesn't propagate implicitly to the nested query. In any case, curious to hear what you think about it!

Good point, language strings are implemented for quite some time, but we don't have any queries for them yet. Also, KV/memstore has no indexes for lang, while SQL/Mongo can be easily extended to provide support for these queries by enabling an index on this field.
This feature is not implemented mostly because we wanted to postpone this work after reification is done, since lang will look like a custom metadata field on string nodes, and all custom metadata queries will work for language as well. But it makes sense to add @lang in current implementation, since it's not that hard and internal details about implementation will change under the hood of the query and will not affect GraphQL.
And, more details should be discussed before starting this. For example, what is the default behavior for name @lang("en") query in case "en" language string does not exists? Should it assume that there is no such predicate, or fallback to string without language tags? What if only German string is available, but not a generic version?

SPARQL treats language tagged strings and non-language tagged strings as different values because they are not the same RDF literals. This makes  sense, since the RDF spec also states that the datatype differs for language-tagged strings. As such, I would think that when not using the @lang directive the name has to be the regular type of string and with the @lang directive the name would have to be the language-tagged type of string. Therefore, there is no generic version of a language-tagged string since they are distinct values within their type, so no fallback, just a null result if a particular language doesn't have a value defined. The specification of the language is standardized as well by the RDF spec.

Hey, I need to get literals language literals in my Gizmo queries but I can't. I tried to look into the code of Gizmo but I was not able to figure out where the values are formatted and why LangString is not formatted correctly. @dennwc can you help me out?

Found it! My fix is here: https://github.com/cayleygraph/cayley/pull/819

@dennwc  as far as I understand we currently load language strings correctly from files and when inserting quads through the UI.

@iddan Correct. The only issues is a query-side support. Right now it's possible to query for exact match, but not with a wildcard in the language, for example.

Got it.

https://github.com/cayleygraph/cayley/pull/834 solved querying for lang strings with regex filter


functorch build is broken on CI

Due to op removal : https://github.com/pytorch/pytorch/pull/69901 functorch can't be build : https://app.circleci.com/pipelines/github/pytorch/functorch/972/workflows/e2f7fdf8-a899-47b0-9601-fceb644bcd72/jobs/5817?invite=true#step-103-81
/home/circleci/project/functorch/csrc/BatchRulesModules.cpp: In function ‘std::tuple<at::Tensor, long int, at::Tensor, long int> at::functorch::cudnn_conv_per_sample_grad_rule(const Tensor&, c10::optional<long int>, const Tensor&, c10::optional<long int>, const Tensor&, c10::optional<long int>, c10::IntArrayRef, c10::IntArrayRef, c10::IntArrayRef, int64_t, bool, bool, bool, std::array<bool, 2ul>)’:
/home/circleci/project/functorch/csrc/BatchRulesModules.cpp:168:20: error: ‘cudnn_convolution_backward_input’ is not a member of ‘at’
   auto grad_self = at::cudnn_convolution_backward_input(
                    ^
error: command 'gcc' failed with exit status 1

Exited with code exit status 1

I fixed the build failure. There are a lot of test failures that I'm going through right now though

Fixed by https://github.com/pytorch/functorch/commit/7a9ae5f7fc5f1737f0224ffc8f267197e9158622


Adds stage to generate docs in gh-pages branch for Jenkins

Submission Checklist

[x] Run unit tests: ./runTests.py test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary:
Adds a stage to Jenkins so that the doxygen is made and pushed to the gh-pages branch
Intended Effect:
Users will be able to go the the doxygen generated website to view documentation for the math library
How to Verify:
I'm now sure how we verify this works on Jenkins without running it? Should I change isBranch('master') to this branch?
Side Effects:
The creation of the gh-pages branch with doxygen website
Documentation:
How should we document this?
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Stephen Bronder
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Oh, this is a cool idea. Not sure if you can see my comments anymore, I put them on what is now an outdated part of the diff. Here's the link: https://github.com/stan-dev/math/pull/794#discussion_r173627598

@seantalts  I'm getting
+ git push<EMAIL_ADDRESS>+gh-pages:gh-pages
To<EMAIL_ADDRESS> ! [remote rejected] gh-pages -> gh-pages (permission denied)
error: failed to push some refs to<EMAIL_ADDRESS>
http://d1m1s1b1.stat.columbia.edu:8080/job/Math Pipeline/job/PR-794/10/console
Is this because I am on Roks fork? If so I can close this branch and make this within dev

I'm going to test that in a new PR and if it works I'll close this one


Get the current logged user in the template

I'm trying to get the current user object in my templates after successfully logging in with Twitter but it's not working.
Here's what I'm trying to do in my templates:
Welcome, {{ request.user.first_name }}
I already have the "django.core.context_processors.request" on TEMPLATE_CONTEXT_PROCESSORS. I have already tested with no success putting it before and after:
'social.apps.django_app.context_processors.backends',
'social.apps.django_app.context_processors.login_redirect',
Am I doing something wrong?

It happens you don't need to use "django.core.context_processors.request" to achieve that. The issue was that I was using "render_to_response" instead of "render".
And in your template you want to use:
{{ user.first_name }}
instead of
{{ request.user.first_name }}

It happens you don't need to use "django.core.context_processors.request" to achieve that. The issue was that I was using "render_to_response" instead of "render".
And in your template you want to use:
{{ user.first_name }}
instead of
{{ request.user.first_name }}


HOTFIX - async task manager - running same task several times!!!

Very tricky issue due to Promise.map!
When n async tasks were in a PENDING state. The async task manager was running n times the lastest one!
This leading to an exception when the task tries to acquire an exclusive lock.

@LucasBrazi06 : Please call me to discuss that one!

@LucasBrazi06 : Please call me to discuss that one!

Thanks!

Probably https://www.npmjs.com/package/eslint-plugin-no-closure.


Date is coming different on localhost and on prod env.

When I am selecting a past date from calender then it is showing correct output at first place(fig-1).

But when I am printing that same date on pdf from backend then it is showing one day back(fig-2)

But it is working fine in local env but not working fine in Test & Prod env.

Check well with your configs. It's likely the logic.

Thanks @xpanvictor
You were right, moment was giving default host time zone.
To Fix it:

We can use moment(time in milliseconds).utcOffset(330). To know more refer this
Here 330 minutes mean utc time + 5:30(it is Indian Standard Timezone)
We can use moment timezone package.


Have 2 Dyson fans. Only one will connect

I hooked up a Dyson cool link fan I've had for a while a few months ago and everything has been working great. Today I purchased another fan and added it to my config file. It shows up in HomeKit but I am unable to do anything with it. It just says it's powered off (even when running) and errors on all the sensors. I'm unsure of what to troubleshoot as I set it up the same as the other fan I have.
I have double checked that my serial number and wifi password for the fan are correct.

homebridge-dyson-pure-cool


Automatic sysroot creation

Although we depend on miri from https://github.com/rust-lang/miri directly, we require that the user installs a sysroot manually using cargo miri setup (since that comes from the miri rustup component). This means we are locked to the version of miri which is in https://github.com/rust-lang/rust. However, it would be better if we could instead use the rustc version which https://github.com/rust-lang/miri compiles with. This would allow us to update more frequently.
In particular, if we make changes to miri (such as https://github.com/rust-lang/miri/pull/1736) then we need to wait for the miri update to reach nightly to use those changes.
cc @ralfjung the easiest way for us to make this possible would be for cargo miri [setup] to be callable as a library, although I suppose we could also install cargo miri directly from the repository. That does seem like a worse solution however.

we could use something like the ./miri script: https://github.com/rust-lang/miri/blob/master/miri
This should allow us to work completely locally. Maybe we can even the miri script be a wrapper around another script that serves the base functionality that priroda and miri need?

Hmm, we could do something cargo install --git https://github.com/rust-lang/miri -p cargo-miri --target-dir ../target Ideally though we'd be able to ship a single priroda binary, and be able to run it on any rust program, without having to worry about the version of miri the user has installed being incorrect.
It's possible that we'll need some custom setup stuff anyway - I'm not certain what cargo miri setup actually creates, and whether we'd need to create anything custom in that output.

I don't understand what this has to do with using miri master vs the miri pinned in the rustc submodule, but if there's a way to make cargo miri a library I'd be open to that.

Although we depend on miri from https://github.com/rust-lang/miri directly, we require that the user installs a sysroot manually using cargo miri setup (since that comes from the miri rustup component).

The two binaries miri and cargo-miri both come from the same repository and are handled the same by rustup. I don't understand why you are saying there is a difference between the two here.

Priroda depends on miri the library directly, not miri the executable. It is currently not possible to have executable dependencies.

Could we ship the miri library together with the binary so priroda can just use the one from rustup instead of having a git dependency?

That could happen, however the reason I want to depend on main miri is so that we don't have to wait for any updates to miri which we would depend on to reach the submodule update of rust-lang/rust.

I see, you are doing
miri = { git = "https://github.com/rust-lang/miri.git", rev = "ea86335318fd06ec964d9a86b187995bda1b6c7d" }

but there is no way to do that for cargo-miri.
From what I know, splitting a crate like cargo-miri into a lib and a bin crate and making the bin crate just a thin wrapper around the lib is pretty straight-forward, so that seems totally acceptable in terms of Miri-side overhead.

Yeah, exactly. I'm sure I'll make the PR after I do #40


How to process the wiki dataset so that it can run on GCN?

Hi @jzm-123 !
Raw GCN only accepts attributed graphs (graphs with feature). Since wiki dataset does not contain node features, you can create a node feature file which tells the model that it has zero dimension features, and load it as a self-defined dataset.
The format of feature file should be: each line describes one node, in which the first number is the node number, and the following numbers are node feature vectors (which in this case you should leave empty), like:
0
1
2
3
...


BUG: where gives incorrect results when upcasting (GH 9731)

closes #9731
The main issue is when the destination and source arrays have different lengths, np.putmask doesn't behave like arr[mask] = values:
"Sets a.flat[n] = values[n] for each n where mask.flat[n]==True"
We have to use np.place instead. A secondary issue is that np.place doesn't automatically convert an integer to a datetime64 like np.putmask does (I created a numpy issue for this), so we need an additional check for that case. The rest of the commit is just cleaning up _maybe_upcast_putmask, which had some parameters that were never used, and a confusing docstring.

@evanpw thanks!
this was subtle!

I assume you changed to use np.place because some OTHER tests were initially failing on your change. Or do we need some tests for the same operation but with dtype = M8[ns] or m8[ns]?

The tests that were failing after I changed np.putmask to np.place were the ones testing idxmax and idxmin, but the new tests in GH #9804 are more direct.


Add support for mixed ESM and CJS

This adds support for mixing ESM and CJS so that we have feature parity with ncc, which is basically webpack.
This will fix all the issues that were reported in the latest release:

https://spectrum.chat/zeit/general/now-deploys-suddenly-not-working~a052cb8f-e95e-4eef-9e81-5e799d1e5ef4
https://spectrum.chat/zeit/now/did-you-forget-to-add-it-to-dependencies-in-package-json~6b370740-866c-4404-bdcc-cc51a3bc9aec
https://spectrum.chat/zeit/now/cannot-build-ts-api-with-now-node-anymore~a24f6eb3-201a-4ecb-8688-94b4a56d4abe
https://github.com/zeit/now-builders/issues/791

Update
I spoke with Timer and it sounds like Next.js might want to follow the Node.js behavior. If that's the case maybe we don't want this PR to land. We need to discuss with the whole team.
Perhaps we should enable backwards compatibility through a config flag like mixedModules: true. That way user's who have broken deployments can opt-in to this behavior.

Codecov Report

Merging #26 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #26   +/-   ##
=======================================
  Coverage   89.88%   89.88%
=======================================
  Files          10       10
  Lines         979      979
=======================================
  Hits          880      880
  Misses         99       99

Impacted Files
Coverage Δ

src/analyze.js
96.15% <100%> (ø)
:arrow_up:

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 248eba1...0359d9f. Read the comment docs.

@Timer I just confirmed that ncc works with the unit test I added.
cd test/unit/mixed-esm-cjs
ncc build input.js
node dist

This change is necessary to maintain backwards compatibility. I would be open to using a flag to opt-in to this non-standard behavior if you prefer.

Ah, this is because ncc uses webpack's legacy javascript/auto source handling method instead of javascript/esm or javascript/dynamic.

@Timer I added a flag mixedModules so that we can opt-in to this legacy behavior.


Sagemaker is not running

Sagemaker is not running while local training deepracer aws.i have checked that all docker files are correct and also made docker type swarm.Still it fails to load sagemaker after creating rl coach and robomaker containers.
No other errors are showing other than sagemaker is not running.

Support is easier to get in our forums - deepracing.io - otherwise update the ticket with log-files; combine docker ps -a with a docker logs <containerid> to get more details.


level=error msg="gateway: could not handle packet: gateway: could not base64 decode data: illegal base64 data at input byte 0"

level=error msg="gateway: could not handle packet: gateway: could not base64 decode data: illegal base64 data at input byte 0"
What happened?
What's the problem?

?

Could you let me know how to reproduce this issue?


[ISSUE #1457] Dynamically effective namesrvAddr for name server auto-scaling

What is the purpose of the change
Fix issue #1457
Brief changelog

Update all broker config when using -c param in mqadmin updateBrokerConfig subcommand
Make namesrvAddr parameter effective dynamically for name server auto-scaling triggered by mqadmin updateBrokerConfig command.

Verifying this change
Use mqadmin updateBrokerConfig -c clusterName -n oldNameServerList -k namesrvAddr -v newNameServerList to see if all brokers in the cluster has log register broker[0]to name server newAddress:9876 OK
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.03%) to 49.506% when pulling e3c70c1f148dba11e2294cf7717d7ff21c14ceae on liuruiyiyang:fix_issue_1457 into faef36455e273f2a2e2ceedc9497e61b994f999d on apache:develop.

Should it be under consideration that fetchNamesrvAddrByAddressServer is true when you configure watchNamesrvAddr to true and update the namesrvAddras  as you mentioned ? Maybe this two configurations are contradictory.

@wqliang Thanks for your question. The scheduled thread has been removed. The updated namesrvAddr applying process is triggered by the mqadmin updateBrokerConfig command only once now.


X.L.ImageButtonDecoration doesn't reexport shrinkText

Problem Description
The documentation for XMonad.Layout.ImageButtonDecoration shows an example where shrinkText is expected to be in scope, but the module doesn't reexport it from X.L.Decoration. Currently you must manually import X.L.Decoration to get it.
Steps to Reproduce
Try to compile the minimal config specified in X.L.ImageButtonDecoration.
Configuration File
Please include the smallest full configuration file that reproduces
the problem you are experiencing:
module Main (main) where

import XMonad

myL = imageButtonDeco shrinkText defaultThemeWithImageButtons (layoutHook def)
main = xmonad def { layoutHook = myL }

Checklist

[x] I've read CONTRIBUTING.md

I tested my configuration

[x] With xmonad version 0.17.0 (commit XXX if using git)
[x] With xmonad-contrib version 0.17.0 (commit XXX if using git)

While the direct issue is closed with the reexport, arguably it should reexport the rest of the Shrinker infrastructure like every other module that uses it.

And that's just two more exports, so done.


async on_ws_frame hooks

Hi, do you have any idea how to make reading the data asynchronous? Eg. making the on_ws_frame function async? I tried asyncio.create_task and pushing the data into asyncio.Queue, but both is pretty slow.

Yes, that was the reason why I decided not to provide async iteration interface like aiohttp and websockets do.
Because both create_task and Queue are slow and introduce significant delay and a lot of churn for the event loop.
Which is very undesirable when there is a spike in market activity.


Perf rearchitecting

This PR is a dramatic rearchitecture of the way that we handle modifiers in react-dates on the whole.
Instead of passing down an object of modifier string => modifiers functions to each CalendarDay component (one that gets rebuilt on every render call) and expecting the CalendarDay component to take care of updating itself, we now put the burden on the top of the tree instead of on the leaves. The previous model meant that whenever an interaction happened on an individual day, even a hover interaction, every single CalendarDay would have to recalculate its modifiers and rerender as a result. The idea was that an interaction on one day might have effects elsewhere in the calendar (like the hovered-span).
In this new model, the DayPickerRangeController maintains a map with the following structure:
{
  MONTH_ISO_1: {
    DAY_ISO_1: Set(['modifier_1', 'modifier_2', ...]),
    DAY_ISO_2: Set(['modifier_1', 'modifier_2', ...]),
    ...
  },
  ...
}

It passes this down the tree such that each CalendarMonth and each CalendarDay only gets the information that pertains to it. This means that the updating of these modifiers is also handled at the top-level and is done in the componentWillReceiveProps, onDayMouseEnter, and onDayMouseLeave methods of the DayPickerRangeController. Fortunately, this allows us to more finely tune which days get updated and speeds up the rerendering/updating process dramatically.
I did some preliminary testing and saw the following improvements:
Before:

After:

I will update those graphs when everything is in place.
I still need to finish writing some tests, clean up some other tests, and also get this working with enableOutsideDays and the SingleDatePicker.  The bulk of the work is in DayPickerRangeController right now, but I've been musing on ways to pull that in an HOC or something. SUGGESTIONS ARE WELCOME.
In any case, I would appreciate a first review pass while I finish up the above points! <3
@lencioni @ljharb @moonboots @backwardok

Coverage decreased (-3.5%) to 80.497% when pulling 6faae02466f58925ff8896ccaf7ba9d22ba022bb on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

Coverage decreased (-56.8%) to 27.181% when pulling 5473b4ffd22aa91d517f80a1d09b4619874ddb37 on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

Coverage increased (+2.6%) to 86.593% when pulling 37eafddb1b45360f72280bf75c9bc0c5f77a13c1 on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

Coverage increased (+2.6%) to 86.593% when pulling 37eafddb1b45360f72280bf75c9bc0c5f77a13c1 on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

Coverage increased (+2.6%) to 86.593% when pulling 37eafddb1b45360f72280bf75c9bc0c5f77a13c1 on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

Coverage increased (+3.0%) to 86.961% when pulling c3b5350bb0b63278cc13253cd062fbfba7be5361 on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

Coverage increased (+4.6%) to 88.576% when pulling 04a1e5ef6280b37bbcff1f711e3449720a87bc3c on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

Coverage increased (+4.7%) to 88.673% when pulling 9220ddb3421adebc8fb9b73252c72af604b0de39 on maja-prototype-perf-idea into 3815516a6d9f1400b51f94782f845b8e328b66d3 on master.

@ljharb I think I addressed your concerns! Can you take a look?

Coverage increased (+2.2%) to 86.12% when pulling 3c1bd25b7759178c64d9e75ee7d1f070370e5bcc on maja-prototype-perf-idea into 767bebcab43a5e99b8cf981e573652fbd63c120f on master.

Coverage increased (+2.2%) to 86.12% when pulling 0b20ab4c99bff58c479d514b19f58bc887e32c01 on maja-prototype-perf-idea into 767bebcab43a5e99b8cf981e573652fbd63c120f on master.

Coverage increased (+2.2%) to 85.737% when pulling c95cbed47d9ef80d4812919ab646c9a107fc0435 on maja-prototype-perf-idea into c4bc6d6d6f22ba2f13ce71edf346f77fff304644 on master.

Hey guys, I have the following on a DayPicker component in order to highlight a range of dates that contain information, along with highlighting the currently selected day. However it now no longer works after this refactor. Is there another approach I can take to make it work? thanks.
            modifiers={{
              selected: day =>
                moment(this.props.selectedDay).isSame(day, 'day'),
              'highlighted-calendar': day1 =>
                this.props.highlightedDays.some(day2 =>
                  moment(day2).isSame(day1, 'day'),
                ),
            }}

Hey @dburles, can you open an issue for this so that we can have a convo on a separate thread?

@majapw sure thing! #562


Update README.md

Update README.md to use a List for authorized_keys config instead of a heredoc. The heredoc fails with
protocol Enumerable not implemented for "..."

Switching to a List resolved the issue for me.

👍
yeah i changed that to a list recently @fhunleth


Add CP3R space

Add space for ...
Etherscan: https://etherscan.io/address/0x7Ef1081Ecc8b5B5B130656a41d4cE4f89dBBCC8c
CoinGecko: https://coinmarketcap.com/currencies/compounder/
Website: https://compounder.finance/
Twitter: https://twitter.com/gocompounder

@compounder-finance It's now possible to create and edit a space without doing pull requests but using ENS and IPFS instead. Could you use this new method to create your space? Here is the guide: https://docs.snapshot.page/guides/create-a-space

We have made a major update. You should now use ENS and IPFS method to create your space. Here is the guide: https://docs.snapshot.page/guides/create-a-space. I'm closing this PR for now, you will need to open a new one to add your space images. Thank you.


Update README.md

Spelling corrections:
sychronously 🠞 synchronously
demostrate 🠞 demonstrate

Closing, as these changes are in PR #28.


Issue with Git Push

Hi ,
Something went wrong with git push . Seems that git push command work but it never pushed code on repo.

Hi @burhandodhy
Please provide further information such as screenshots, the process you were following, confirmation that your config details are correct, and whether the GIT PUSH command process works from the command line on your machine, but it does not from within git-plus.
If not, please close the issue, thanks.

I'm closing this because there isn't any detail to work with. Also changes have been made to the push feature which may have resolved your issue.


Use temporary directory instead of build_path

Hi @drowzy I fell into an atypical situation where I'm running protobuf-generate inside a container and I received the undefined error for Mix.Project.build_path/0. This pr solves this problem by using a temporary directory to generate the protobufs.

Thank you @drowzy

Hi @drowzy Would it be possible to generate a new version of the hex package with this change? Unfortunately, in my software I can only use dependencies downloaded directly from hex and not from github. This ends up stopping me a little

ping @drowzy

Hey @drowzy any news about new releases?


feature request - filter for too high values

is it possible to add a filter for L1-3 values that are not possible on a normal home connected to the grid with 32A.
i have a tasmota sml mqtt source that sometimes a day gets me 999999W for 2-3 sec.
The batterie than goes unnecessary to 100%.
this would help me a lot

Would appreciate a little donation :)


closes #17 adding response to SetWebhook Method

Here is the change to add the proper response to the SetWebhook method, its simple but its something :D

Awesome, thanks!


Search Function not working for Qiskit Nature

Information

Qiskit Nature version: NA
Python version: NA
Operating system: NA

What is the current behavior?
The Search Function of Qiskit Nature is not working.
Steps to reproduce the problem
Just go to this https://qiskit.org/documentation/nature/ and type anything you want to search.
What is the expected behavior?
It will not work as expected.
Suggested solutions
I think search function have some sort of bug internally and needs to be fixed ASAP

Well then I think there is no point in opening this issue now. I am closing this and consider this discussion further on Qiskit/qiskit#1223.

Fwiw, this issue should be fixed by https://github.com/Qiskit/qiskit_sphinx_theme/pull/34


Removing vaccination clinics from repo

On Sunday 20 Aug, I'll be separating out vaccination clinics from the vaccine PDF repo to help speed up the checkout process in the GitHub action.
If you are a consumer of the hosted CSV and JSON files, you will not be impacted.
If you use this repo directly, the git history will be rewritten.  You can either reset your HEAD to the latest in master OR if you have pending changes, you may need to merge these changes or maintain a separate fork.

This change will be delayed until Thursday, 26 August


feat: graphs in the home page

This is a draft PR

graphs look good!
When hovering over the market cap chart I get this error:
EChart.js:29
   Uncaught RangeError: Invalid time value
at Object.formatter (EChart.js:29:1)
at t.value (apexcharts.common.js:6:1)
at t.value (apexcharts.common.js:6:1)
at t.value (apexcharts.common.js:6:1)
at t.value (apexcharts.common.js:6:1)
at t.value (apexcharts.common.js:6:1)
at t.value (apexcharts.common.js:6:1)
at t.value (apexcharts.common.js:6:1)
at t.value (apexcharts.common.js:6:1)


About the inference time

@zhijian-liu Thank you very much for your sharing! I am reading your paper recentely. I see that your optimized model can run about 100ms per frame. So I am curious about what is the efficiency bottleneck now. Is it the Swin-T process?

Hello @zyl1336110861, thanks for your interest in our work! The efficiency bottleneck is the LiDAR backbone, which is a SparseConvNet. Previously we also study the optimization of SparseConv in the system-level and hardware-level. You are welcomed to check out our recent papers TorchSparse and PointAcc.

@kentang-mit Ok! I will refer to these papers! Thank you very much!

You are welcome.

@kentang-mit Hi, please see here , is that true? It says that spconv2.x is greatly faster than torchsparse.

@kentang-mit Hi, please see here , is that true? It says that spconv2.x is greatly faster than torchsparse.


ARROW-17340: [Go] Use T.TempDir to create temporary test directory

A testing cleanup.
This pull request replaces ioutil.TempDir with t.TempDir. We can use the T.TempDir function from the testing package to create temporary directory. The directory created by T.TempDir is automatically removed when the test and all its subtests complete.
This saves us at least 2 lines (error check, and cleanup) on every instance, or in some cases adds cleanup that we forgot.
Reference: https://pkg.go.dev/testing#T.TempDir
func TestFoo(t *testing.T) {
	// before
	tmpDir, err := ioutil.TempDir("", "")
	if err != nil {
		t.Fatal(err)
	}
	defer os.RemoveAll(tmpDir)

	// now
	tmpDir := t.TempDir()
}

@Juneezee Looks like there's an issue with Windows here, I think you just need to add a defer o.Close() line 58 of ipc/cmd/arrow-stream-to-file/main_test.go can you give that a try?

Thanks @Juneezee!


I can't build the sites, Error: timed out initializing value, after use hugo server

$ hugo server
Start building sites …
Built in 14482 ms
Error: Error building site: "C:\Hugo\ZzoTheme\content\en\posts\rich-content.md:1:1": timed out initializing value. You may have a circular loop in a shortcode, or your site may have resources that take longer to build than the timeout limit in your Hugo config file.
installed the Hugo-extended version

               | EN

-------------------+-----
Pages            |  3
Paginator pages  |  0
Non-page files   |  0
Static files     |  0
Processed images |  0
Aliases          |  0
Sitemaps         |  1
Cleaned          |  0
Built in 2 ms
Watching for changes in C:\Hugo\myblog{archetypes,content,data,layouts,static}
Watching for config changes in C:\Hugo\myblog\config.toml
Environment: "development"
Serving pages from memory
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at http://localhost:1313/ (bind address <IP_ADDRESS>)
Press Ctrl+C to stop
WARN 2021/04/20 08:38:13 found no layout file for "HTML" for kind "home": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.


eslint: fix import resolution in oidc-dev/playwright-tests

Closes #977

@ktuite can you give this branch a try and see if the issue with make lint is resolved?

Still getting the errors :(
$ make test
node lib/bin/enforce-node-version.js
npx eslint --cache --max-warnings 0 .

/Users/ktuite/Desktop/code/odk/central-backend/oidc-dev/playwright-tests/playwright.config.js
  10:29  error  Unable to resolve path to module '@playwright/test'  import/no-unresolved

/Users/ktuite/Desktop/code/odk/central-backend/oidc-dev/playwright-tests/src/global-setup-teardown.js
  23:43  error  Unable to resolve path to module 'http-proxy-middleware'  import/no-unresolved

/Users/ktuite/Desktop/code/odk/central-backend/oidc-dev/playwright-tests/src/oidc-login.spec.js
  10:26  error  Unable to resolve path to module '@playwright/test'  import/no-unresolved

/Users/ktuite/Desktop/code/odk/central-backend/oidc-dev/playwright-tests/src/utils.js
  22:28  error  Unable to resolve path to module '@playwright/test'  import/no-unresolved

✖ 4 problems (4 errors, 0 warnings)

make: *** [lint] Error 1

@ktuite I think probably simplest just to disable it for now.  Can you give the PR another try now?


Upgrade Examples from .NET 6 to .NET 8

I don't think that this PR needs a description

@dotnet-policy-service agree

@jonas1ara, thank you for your first PR! Your contribution is much appreciated, it's really nice to see people eager to help out!
A description is not necessary, but I need to think about whether upgrading to .NET 8.0 is right for the examples, especially the language version. It may tempt us to use features that earlier versions don't allow, and as long as we have to support .NET 6 and .NET FX 4.7, that may be risky... :-)

Another thing -- in order to work, the azure_pipelines.yml file would have to be updated to install .NET 6 on the build machines.


What are the prerequisites for running OpenEBS on RHEL?

This query is raised by @kasim457 in community channel
I have iSCSI on the nodes with following status.
how to check iscsi running status in rhel 7.4
rpm -qa|grep iscsi
iscsi-initiator-utils-iscsiuio-<IP_ADDRESS>4-7.el7.x86_64
iscsi-initiator-utils-<IP_ADDRESS>4-7.el7.x86_64
[root@node1 ~]#
error in journlctl -xe output

Unit iscsid.service has begun starting up.
Jan 22 12:42:03 node1 iscsid[20154]: iSCSI logger with pid=20155 started!
Jan 22 12:42:03 node1 systemd[1]: Failed to read PID from file /var/run/iscsid.pid: Invalid argument
Jan 22 12:42:03 node1 systemd[1]: Started Open-iSCSI.
-- Subject: Unit iscsid.service has finished start-up
-- Defined-By: systemd

[root@node1 ~]# systemctl status iscsid
● iscsid.service - Open-iSCSI
Loaded: loaded (/usr/lib/systemd/system/iscsid.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2019-01-22 13:05:27 IST; 23min ago
Docs: man:iscsid(8)
man:iscsiadm(8)
Process: 27555 ExecStop=/sbin/iscsiadm -k 0 2 (code=exited, status=0/SUCCESS)
Process: 27558 ExecStart=/usr/sbin/iscsid (code=exited, status=0/SUCCESS)
Main PID: 27561 (iscsid)
Memory: 1.5M
CGroup: /system.slice/iscsid.service
├─27560 /usr/sbin/iscsid
└─27561 /usr/sbin/iscsid
Jan 22 13:05:27 node1 systemd[1]: Starting Open-iSCSI...
Jan 22 13:05:27 node1 iscsid[27558]: iSCSI logger with pid=27560 started!
Jan 22 13:05:27 node1 systemd[1]: Failed to read PID from file /var/run/iscsid.pid: Invalid argument
Jan 22 13:05:27 node1 iscsid[27560]: iSCSI daemon with pid=27561 started!
Jan 22 13:05:27 node1 systemd[1]: Started Open-iSCSI.

@kasim457 The iSCSI check on RHEL is added in the prerequisites section of documentation.
https://docs.openebs.io/docs/next/prerequisites.html#rhel
Let us know this is useful for you.


Merging in GPU

If the module is in the GPU, put lora in it as well

LycorisNetwork is an nn.module
once you call the .apply_to()
you can directly do network.to(base_model.device) or something like that.
create module in GPU is not recommended, normally we only init modules in cpu or meta device.
but lycoris require weight initialization so only cpu here.


Try to fix patch in master

try and fix code coverage patch.  I'm not sure this will work,

Codecov Report

Merging #585 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #585      +/-   ##
==========================================
- Coverage   91.72%   91.68%   -0.04%
==========================================
  Files          64       64
  Lines        5304     5304
==========================================
- Hits         4865     4863       -2
- Misses        297      298       +1
- Partials      142      143       +1


remove unneeded id and type cover methods

Ruby 1.8.7 had Object#id and #type, both of which were deprecated,
which Hashie::Mash wanted to cover with more reasonable methods.
These methods in Object were removed in ruby 1.9.  The cover methods
are unneeded, and can cause problems with Mash::SafeAssignment
preventing you from using these as keys.
Fixes #290

I think this needs a CHANGELOG entry, please.

okay, CHANGELOG added.

Merged via https://github.com/intridea/hashie/commit/61fc9a9cbce3999df515f4f291135b51372789c4, thanks.


Duplicate code in htmilify.p6

The problem
There are a few lines duplicated in htmilify.p6 (https://github.com/perl6/doc/blob/26236dff03d5f3afbfe6c47345e4f57961c6cac8/htmlify.p6#L321)
Suggestions
Delete them.

Fixed in 26236dff03d5f3afbfe6c47345e4f57961c6cac8


Keyboard shortcuts not working in MJML on Chrome/Edge

Describe the bug
I cannot seem to use keyboard shortcuts such as CTRL + C, CTRL + V when using the online MJML editor in Chrome/Edge.
Firefox seems to work fine.
Seems to be just the editor pane that is affected, I can for example use CTRL + C on the version text above the editor pane.
To Reproduce
Steps to reproduce the behavior:

Go here in Chrome or Edge: https://mjml.io/try-it-live
Try to copy code from left hand editor pane using keyboard CTRL + C, try to paste code in left hand editor pane using CTRL + V

Expected behavior
The code to be copied, and then pasted within the editor
MJML environment (please complete the following information):

OS: Chrome: Version 106.0.5249.119 (Official Build) (64-bit)
MJML Version [version 4.9.3]
MJML tool used: Online editor: https://mjml.io/try-it-live/pv0ECBWUV

Can't reproduce the issue on Chrome with OSX and Windows 🤔


Vulnerability: protobufjs

We use gherkin-lint, and out security scans have started showing this message:

└─ protobufjs: 6.11.3
├─ ID: 1092429
├─ Issue: protobufjs Prototype Pollution vulnerability
├─ URL: https://github.com/advisories/GHSA-h755-8qp9-cq85
├─ Severity: high
├─ Vulnerable Versions: >=6.10.0 <7.2.4
├─ Patched Versions: >=7.2.4
├─ Via: gherkin-lint
└─ Recommendation: Upgrade to version 7.2.4 or later

For reference, it appears that this is where protobufjs is in the dependency tree:

<EMAIL_ADDRESS>node_modules/protobufjs
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>node_modules/cucumber-messages

<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
node_modules/gherkin

<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
node_modules/gherkin-lint

<EMAIL_ADDRESS>from the root project

It looks like the repo gherkin has been deprecated in favor of @cucumber/gherkin, which does not seem to have the vulnerability in its dependency tree.
Is it possible for gherkin-lint to update its dependencies to remove any vulnerable versions?

I'll be rolling a release containing this update in the coming week or two when I get access to roll releases. As the dependabot change has already landed for this, I'm going to close this issue.