multi time query crash

I have a class function that retrieve all objects from database and sort the results to get the latest one. And I test it in the testcase. And I run the testcase, it works well. But When I continue to run to testcase and about at my fourth attemp, it crashed. This situation occurs many times.

It do print the count variable's value.

This is the stack info:

@qingpengchen2011 thanks so much for reporting this issue. Since I can't really think of what could be causing this, would it be possible for you to share a sample project that reproduces the issue, either here or privately at<EMAIL_ADDRESS>Thanks!

@segiddins  Hello, I've sent an sample project to<EMAIL_ADDRESS>Thanks for help.

The gist of the problem is that you were linking your model class into both your app target and test target, and thus had different versions of the User class, which was confusing Swift's dynamic casting facilities. By only linking the model class to the app target and importing the app target into the test target, the issue goes away.

@segiddins  I've done what you suggest, and added the parent path to RealmSwift.framework to unit test’s “Framework Search Paths”. But there is linking error in test target. Saying: ld: framework not found Realm for architecture x86_64. I've done some searching, but I can not figure out.

@segiddins  @realm-ci  Hello, I've figure it out. Just by following the steps described in the Realm home page doc, Maybe I did some misconfigure before.  Thanks for your great help.


spread-operator: Set chromestatus link

Can you update README.md as well?

Oversight. Thank you, @jeffposnick :) Fix'd

:+1:


BUG: Speed up sparse compressed indexing with very many rows

Reference issue

See https://github.com/scipy/scipy/issues/14321
What does this implement/fix?

Remove unnecessary use of np.diff
Only a subset of the result of the diff was used which resulted in
poor scaling with very many rows.
Additional information

It might also make sense to backport this change to previous versions since 1.3.x?

So far we only backport things to a single release (ATM this would be 1.7.x).
And we typically limit backports to regressions I troduced in the last release.
The main reason is simply the amount of work for the RM.

Do you think it would be possible to see this change in 1.7.1?
Is there anything more I can do to help push this forward?

I think at this point it's the matter of the PR being reviewed. This may take some time, depending on the reviewer availability and your responsiveness to review comments if there are any. Then it'll be up to Tyler to decide on backporting.

Thanks for the improvement, @judahrand ! And thanks for the review and extra testing @pv

@tylerjereddy Could this be back ported to 1.7.x?

Is this an actual bug or more of a performance/efficiency improvement? In other words, were results numerically incorrect before this change?
There is a fair bit of disruption on 1.7.x already with the new doc theme, pythran things to clean up, and upcoming M1 mac support, so we probably don't want to start piling on things that aren't basically bug fixes.

Is this an actual bug or more of a performance/efficiency improvement? In other words, were results numerically incorrect before this change?
There is a fair bit of disruption on 1.7.x already with the new doc theme, pythran things to clean up, and upcoming M1 mac support, so we probably don't want to start piling on things that aren't basically bug fixes.

The results were numerically correct, however, the indexing was unusably slow for large matrices. I suppose it is up to you whether that passes the bug sniff test.
For example, indexing into CSR with 1e7 rows for 1e4 random rows got 10x slower in 1.3.0. This change speeds that same operation back up about 20x so we return to twice pre-1.3.0 performance.
That all sounds like performance improvements but as I say I'd argue it was a performance bug introduced in 1.3.0 which makes scripy>=1.3.0 completely unusable for some use cases.

I'll put a tentative backport label so it is at least considered then. If unusable slowness is the problem, have the improvements/restoration of performance been guarded with our usual asv benchmarking system?


Ads are actually 122 pixels tall

I know, its a very minor difference, but it should have the correct information

Thanks for the correction.


TXIMSDK_Plus_iOS  版本冲突

[!] CocoaPods could not find compatible versions for pod "TXIMSDK_Plus_iOS":
In Podfile:
tencent_cloud_chat_sdk (from .symlinks/plugins/tencent_cloud_chat_sdk/ios) was resolved to 5.1.2, which depends on
TXIMSDK_Plus_iOS (= 7.1.3925)
None of your spec sources contain a spec satisfying the dependency: TXIMSDK_Plus_iOS (= 7.1.3925).

建议删除所有Pods路径和podfile.lock文件，重装Pods依赖

建议删除所有Pods路径和podfile.lock文件，重装Pods依赖


Preserve scaling factors on transforms

Closes #556

To be clear; I'm sure we could propagate scaling signs down, but I don't think gives any benefits :)


Channels stuck in limbo closing

So i have 4 channels open 1 is pending force close which may take few days the other 3 are just stuck in closing no on chain is being made what do i do if i abandonchannels do i loose funds?
i am unable to close them cause they don t exist as channel but as pending channels do i wait it out and hope to get a on chain payment back
any ideas?

abandonchannel won't work here (see https://api.lightning.community/#abandonchannel). The easiest thing to do is to wait it out.

thanks i force closed channels all good


incoming calls doesn't work

Thank you for your work on this plugin!
Calling (while having the cursor on a method):
:lua vim.lsp.buf.incoming_calls()
displays
method textDocument/prepareCallHierarchy is not supported by any of the servers registered for the current buffer
Would this be something easily fixable?

That should probably be reported to roslyn itself. I am not maintaining the server, as I am only starting the server and adding a few off-spec things roslyn have.
It seems like it has some code related to that, so maybe it will work if you update the server version.
However, I have no idea🤷♂ not something I can do here at least

there's something fishy going on, they are fully implemented in the server and somehow they don't work for us
even worse, not even :lua vim.lsp.buf.declaration() works with the same error that textDefinition/declaration is not supported by any of the servers
the capabilities generated generated by default_capabilities are correct
maybe a custom hack like the one below is required, but I didn't find exactly what
-- HACK: Doesn't show any diagnostics if we do not set this to true
roslyn_config.config.capabilities = vim.tbl_deep_extend("force", roslyn_config.config.capabilities, {
    textDocument = {
        diagnostic = {
            dynamicRegistration = true,
        },
    },
})


Add GitHub holding page

Replacing this:

with this:

I think the message looks grand. Are we able to get rid of the manual step completely? We should be able to add additional state to the admin approval link or make it call a webhook or something right?

@sblausten How will they know when we have done our work? I don't think we are making that obvious to them.

@sblausten How will they know when we have done our work? I don't think we are making that obvious to them.

Yes was thinking of that - doesn't seem we have been telling them up till now that it is installed. Ideally we'd email them as part of the manual steps. I can add that and then say in the message that we'll let them know via their github email address?

@sblausten I'd suggest saying we will email them is in scope for this PR. We can do that manually. The automation of that process is out of scope and can be done separately.


Finished the Course..

Hello
This PR represents all the work I did to complete the raywenderlich.com Beginning Git video. I learnt a lot
Naren

Hey @naren100—congrats on submitting a PR at the end of the git course. I hope that you enjoyed working through the course, and I'm really happy to see that you learnt some new tips and tricks for using git. Did you have any problems following along?
If you weren't already using git for your code, hopefully this has inspired you to do so. I hope that you enjoy the "Mastering Git" video course as well—you'll soon be able to get git to bend to your will :)
You can now wear this #GitWarrior badge with pride—and Tweet your historic victory!

sam


Upgrade protobuf version 3.5.1 (Dec 2017) to a newer version

Pulsar currently uses an 3.5.1 version of protobuf. This is an old version which was released in December 2017.
The protobuf version is defined in https://github.com/apache/pulsar/blob/master/pom.xml#L125-L126 .
The old protobuf version causes issues within Pulsar functions when a functions jar file includes protoc generated classes which have been created with a recent protoc version. Protoc generated classes from a Protobuf version >= 3.8.0 fail with error message java.lang.NoSuchMethodError: 'com.google.protobuf.Descriptors$FileDescriptor com.google.protobuf.Descriptors$FileDescriptor.internalBuildGeneratedFileFrom(java.lang.String[], com.google.protobuf.Descriptors$FileDescriptor[])' in a Protobuf runtime version < 3.8.0 . There might also be some other incompatibilities.
Besides this concrete problem, it would be worthwhile to keep the protobuf dependency up-to-date while using a version that is compatible with the other dependencies used in Pulsar.
The suggestion is to upgrade protobuf to 3.11.4 since 3.11.x is used in Apache Avro (3.11.1 in https://github.com/apache/avro/blob/master/lang/java/pom.xml#L50) . Besides upgrading protobuf, it is suggested to upgrade Apache Avro version used in Pulsar since the Avro's protobuf support depends on protobuf. The latest Avro version is 1.10.0 . Pulsar uses currently 1.9.1 (https://github.com/apache/pulsar/blob/master/pom.xml#L137) .

Due to protobuf version conflicts and incompatibility issues, first roll back the protobuf version, and then resend a new pull request to fix this problem.


php.WARNING: Uncaught User Notice: Class "OpenTelemetry\SDK\SystemClock " is deprecated and will be removed in a future release

This is just a function of the alpha version of the opentelemetry php library, but unfortunately it throws exceptions for depracation warnings, which seems to break the ratings service
$ oc logs -f -n otel-shop otel-shop-ratings-566cb8d56b-d2sfg
[2022-05-24T11:26:56.923220+00:00] php.WARNING: Uncaught User Notice: Class "OpenTelemetry\SDK\SystemClock " is deprecated and will be removed in a future release. Please, use "OpenTelemetry\SDK\Common\Time\SystemClock" instead. {"exception":"[object] (ErrorException(code: 0): User Notice: Class \"OpenTelemetry\\SDK\\SystemClock \" is deprecated and will be removed in a future release. Please, use \"OpenTelemetry\\SDK\\Common\\Time\\SystemClock\" instead. at /var/www/html/vendor/open-telemetry/opentelemetry/src/SDK/Common/Dev/Compatibility/Util.php:51)\n[previous exception] [object] (ErrorException(code: 0): User Notice: Class \"OpenTelemetry\\SDK\\SystemClock \" is deprecated and will be removed in a future release. Please, use \"OpenTelemetry\\SDK\\Common\\Time\\SystemClock\" instead. at /var/www/html/vendor/open-telemetry/opentelemetry/src/SDK/Common/Dev/Compatibility/Util.php:51)"} []
$ oc get pods -n otel-shop otel-shop-ratings-566cb8d56b-d2sfg
NAME                                 READY   STATUS    RESTARTS   AGE
otel-shop-ratings-566cb8d56b-d2sfg   0/1     Running   0          46m

https://github.com/open-telemetry/opentelemetry-php/commit/99fba0d720785dfe9faba310e6e2e78fae9c075d

fortunately, there an easy fix for this
$ git diff
diff --git a/ratings/html/index.php b/ratings/html/index.php
index 2b34782..11ad0d2 100644
--- a/ratings/html/index.php
+++ b/ratings/html/index.php
@@ -6,7 +6,7 @@ require __DIR__.'/vendor/autoload.php';

 use Instana\RobotShop\Ratings\Kernel;
 use Symfony\Component\HttpFoundation\Request;
-
+OpenTelemetry\SDK\Common\Dev\Compatibility\Util::setErrorLevel(0)
 $env = getenv('APP_ENV') ?: 'dev';
 $kernel = new Kernel($env, true);
 $request = Request::createFromGlobals();

$ oc get pods -n otel-shop otel-shop-ratings-5df6d88fb4-9f55j
NAME                                 READY   STATUS    RESTARTS   AGE
otel-shop-ratings-5df6d88fb4-9f55j   1/1     Running   0          43s

would you like me to create a PR - while this is still in alpha, so the service comes up ready?


Correct enum naming style.

Based on https://google.github.io/styleguide/cppguide.html#Enumerator_Names

Thanks for the review Mark!:)


How do I enable NixOS, Flake-parts, and Home-manager options at the same time when using nixd?

The example in the README is not very clear on this. Copying this example leads to the obvious duplicate key errors, but there's also the <name> part. Is this supposed to be my username? Should it be .<myname>. or .myname.? Thanks
Relevant config:
"nix.serverSettings": {
    // settings for 'nixd' LSP
    "formatting": {
        "command": "nixpkgs-fmt"
    },
    "options": {
        "enable": true,
        "target": {
            // tweak arguments here
            "args": [],
            // NixOS options
            "installable": "<flakeref>#nixosConfigurations.<name>.options",
            // Flake-parts options
            "installable": "<flakeref>#debug.options",
            // Home-manager options
            "installable": "<flakeref>#homeConfigurations.<name>.options"
        }
    }
}

Currently not possible, as I understand. I requested of the author of Nixd to implement this for flakes, but as I understand, he doesn't use flakes and only supports such usage through flake-compat. That is until @edolstra finishes source tree abstraction, which would allow the LSP to provide file paths relative to your git directory.
Even still, if you manage to hack something together, you have to choose one installable or one expression, unless you want to create .vscode/settings.nix for each subdirectory of your flake.
I encourage you to pester the author of Nixd to implement a reasonable (even if hacky) solution to this.

There is now advanced settings example available in the readme. https://github.com/nix-community/vscode-nix-ide?tab=readme-ov-file#lsp-plugin-support


Review and update descriptions for schema

Note to reviewers: the Java code is the source for all of these descriptions. Please feel free to put comments in the *.md, *.yaml, or *.java files, but it is not required that you comment on the same string values more than once.

Okay, @rosemarymarano and @tbarnes-us, I believe that I've responded to all of the comments. Thanks! Can you please review again?

@rosemarymarano, thanks for the offer, but I'll make the changes. It's a bit of a pain, unfortunately, because the source is actually the Java code and then you have to build to update these files.


Is it possible to train models in Google Colab?

I've tried training both ruGPT3Large and ruGPT2Large in Google Colab using P100 as GPU. However, cuda runs out of memory at the very beginning of the training. Is it possible to use Google Colab for training models and if yes, how it can be done? A working example would be very helpful.

I had just add google colab for generation
For training we will add rugpt3small soon.


Add logging for AWS upload tasks

The AWS upload process takes a while to complete and can sometimes have
errors. By adding additional logging, users can see what has already
happened and they will have data available, such as snapshot import task
IDs, that they can use to check on status at AWS.
Signed-off-by: Major Hayden<EMAIL_ADDRESS>

Darn, I can't get logs to show up in the system journal with log.Printf or fmt.Printf. 😢

Schutzbot fail is unrelated, this just adds logging.
(if it is related, there's something really fishy in the world of Go and AWS)


[Apple Pay] presentApplePay() and timeout

Hi,
I've succesfully implemented Apple Pay with this flux:

presentApplePay to obtain paymentMethod
server side call using the paymentMethod to obtain the clientSecret
confirmApplePayPayment using the clientSecret

I've just one problem.
If the server side call tooks too long, the applePay sheet close itself saying the app hasn't be able to complete the payment.
I can't find any hint in documentation on how long is this timeout or (better) how to catch the sheet closing for timeout on frontend side (in order to cancel the request and don't proceed further and mark the payment as canceled for the user).
Any idea? Thank you.

In addition to this:
If i try to do:
const { error } = await confirmApplePayPayment(clientSecret);
After the timeout message has been received and the applePay sheet has been closed, the promise is never resolved.

Hello,
I also have a problem with the confirmApplePayPayment method which never resolve.
Here is what I do :

I execute presentApplePay method => Apple pay interface is properly displayed
The payment is processed in the backend (payment intent creation)
I click outside the apple pay payment interface before the process ends what closes the interface
The method confirmApplePayPayment then never resolves nor timeouts

const { error, paymentMethod } = await presentApplePay({...});
try {
    const stripeSecret = await processPaymentInBackend(...);
    const { error } = await confirmApplePayPayment(clientSecret);     // Never resolves if the apple pay interface is closed
catch(e) {...}

Expected behavior:

either : the confirmApplePayPayment throws a canceled error
or : the confirmApplePayPayment  throws a timeout error

Any idea ? Thanks 🙏


Biconnected components

@kolja-esders For this PR Travis reports "Build type disabled via repository settings (pull_request)". This did not happen earlier. Did we change the Travis settings? If yes, what is the rationale for this change?


update mix

I'm trying to use this package for package's development with override: true option in mix.exs.
But I've got this result below due to be set idna(override: true) and httpoison over than 0.11.1 version to mix.exs.
$ mix hex.publish
** (Mix) Can't build package with overridden dependency idna, remove `override: true`

Supposedly, hex.pm cannot accept that option. So please update package version!!
Thanks awesome package.

Thanks response and review comment.
I approgize that I don't know IDNA compatible between 1.2(3.0) and 5.0. But just know 'mix test' is all passed though..  So, I will be responded to change package to fix latest version.
I appreciate this PR is merged if you will be accepted.

This was obsoleted by #26 and can be closed.


CleverBot fails

When typing the command as an example "@NadekoBot Hello, how are you?" causes it to fail.
Giving the error "14:55:49 CommandHandler | Error in cleverbot"
After having a quick look through the bot, it appears that the bot is still using the old cleverbot APIs. As these APIs are now paid for, it might be worth changing over to https://cleverbot.io/ or getting users to pay ;)

#1076

also no to cleverbot.io

Is there a way that we can have our own api keys used?
Added the same way that say the google api is done

yes and read the kwoths comment


gdalinfo band field

As done with proj:projjson or proj:transform, this PR provides with a specific field in the raster:band object to host generated metadata about the band from gdalinfo CLI.

I also fear what @kylebarron mentions. This could be a way for people to bypass actually providing the right fields. Wouldn't it make more sense to add those fields that are missing and then provide a script that transforms the gdal output into a proper STAC Item?

I would hope that folks wouldn't use this to shortcut around placing the data in more appropriate places (e.g proj:shape). Also the structure of the gdalinfo object is a bit strange (e.g. the empty string key). But if this is what's produced by GDAL and we aren't placing any validation against the object this seems fine and useful.

Not at all. The item in the bands array of gdalinfo json does not include information about the projection. It only contains information about the bands.
This PR comes from a practical need of putting useful information about a raster band in the STAC item. In particular the histograms sampling information that you get with -hist of gdalinfo and some vendor metadata stored in geotiff at band level.
There are 2 alternatives
1/ propose fields for histograms and vendor metadata
2/ have a link at asset level that point to the gdalinfo json output but there are no link object at asset level.
This PR is intended to be a precursor for more specific fields in future releases but now reading the reviews, I am unsure of this proposal.

I like both of your alternatives better than the current proposal. Is there software that can actually read gdalinfo output and make use of it? Then 2 seems reasonable. For 1 I'd try to map to existing fields and add new fields that are missing and then provide a script that translates to STAC.

I prepared a new PR for the histograms (https://github.com/stac-extensions/raster/pull/14) which is the major information I need for now. Please review and if positive, I will close this PR.

Finally catching up on these issues. Sounds like the plan is to close this without merging, which is good. I don't think an unstructured string with this info is useful and we should just add new fields for info that isn't currently covered by existing fields.


Fix/issue354

this fixes #354 for both file and metadatasets
i added a test and a modified user fixture to grant site read -> the test errors unexpectedly, despite using the exact same logic as for the bulk deletion -> two different errors:

user_a owner and 'viewer' errors in unmarshallers.py
user_a owner, user_c with site_read 'viewer' returns 500

what am i doing wrong?

nvm, i based this on main; test still has issues, but i'll resolve those

this is a mess


[DO NOT REVIEW] Rebalance testing load [databricks]

Signed-off-by: Peixin Li<EMAIL_ADDRESS>under construction

build

build

build


gitlab-ci integration

Project no has ci tool running. I propose use of gitlab-ci. There has good interactions with docker containers and that can help us to run selenium/appium images.
Documentation to help
https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/github_integration.html

@fabricio-aguiar closes in #14 14


Does it supports inputstream ?

@protyposis
Does it accept to deliver video content by stream,
Like VLC.dotnet accepts, See
https://github.com/ZeBobo5/Vlc.DotNet/blob/develop/src/Vlc.DotNet.Forms/VlcControl.cs#L206-L209
But it is only for windows, I was looking for same approach in android,
Any advice ? Any solution please.
Please reply I will add more details.
I also msg you on your email.

no activity after 13 days so closing this

See https://github.com/protyposis/MediaPlayer-Extended/issues/115#issuecomment-612815866

Hi thanks I will check it later on


Add enum for ClinVar review status

Since we have one for clinical significance and even for modes of inheritance, it seems like a good idea to add this one as well

I have now added validation for the clinvar_rating to the somatic_mutation's evidence section as well, using definitions to avoid duplication.
Also, to avoid having to resolve multiple conflicts, I have rebased this PR on top of #95, so it now contains all changes from that one as well.

Sounds good, can I then close #95 without merging it?

@AsierGonzalez Yes, absolutely. In fact, if you merge this PR, #95 will close automatically, as GitHub can see that #96 is built on top of #95 and includes all changes from it as well.
Also, going even further, all of my four PRs are built on top of each other: #95 → #96 → #97 → #99. So, for example, if you review and merge #99, all others will automatically close.

That's good to know. I'll look into all of them and if everything's fine I'll merge #99, that makes it easier.


OpenGL error messages on ArkOS on RG503

Hi,
While testing alephone with a custom game, e.g. "Marathon Eternal" running it from SSH:
./alephone "/roms2/ports/alephone/Marathon Eternal"
it generates this error:
[ogg @ 0x5592d99040] 1922 bytes of comment header remain
OpenGL (Shader) renderer is not available (screen.cpp:971)
WARNING: Failed to initialize OpenGL renderer
WARNING: Retrying with Software renderer
It then runs using the Software rendered.
Looks like a shader issue with OpenGL, from what I've been able to read about it.
When I Ctrl+C out of alephone I get 8 instances of this message:
arm_release_ver of this libmali is 'g2p0-01eac0', rk_so_ver is '3'.
It also happens when I exit PortMaster.  Appears onscreen before the screen goes back to ES.
Not sure what's causing this.
ES

There's no OpenGL available.  Just OpenGLES.  The messages are just harmless libmali messages

I thought so.  Hate the messages though.  :) Thanks!


[DSO-1013] update-jupyterhub

Make file and Readme Explain the build process
Docker file is commented appropriately to explain the necessary steps
process is simplified a lot compared to previous jupyterhub image since gcs-connector supports java 11 so we do not have to build our own all spark notebook with java8 using jupyter docker stacks
updated build will have spark 3.4.1, py3.11, hadoop3, openjdk17, scala2.12

do not merge this branch before complete testing as  folders jupyter and jupyterhub in parent repo are deprecated and will get removed
I confirm that I have added:

[x] A comment to every Dockerfile with information about target repository and tag (version).
[x] Filled in readme on dockerhub and in this repo about how to build the image if some extra steps should be done.

@annoyingllama
Ran image locally. Jupyterhub loads. All packages are available. Spark session getting created.
On reading GS parquet with spark session failing with:
Py4JJavaError: An error occurred while calling o35.parquet.
: org.apache.hadoop.fs.UnsupportedFileSystemException: No FileSystem for scheme "gs"
at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3443)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3466)
at org.apache.hadoop.fs.FileSystem.access$300(FileSystem.java:174)

@Konstantinos-Chaitas-PubNative @mpasa https://almond.sh/docs/install-versions, which almond versions should I install?

@annoyingllama
Ran image locally. Jupyterhub loads. All packages are available. Spark session getting created.
On reading GS parquet with spark session failing with:
Py4JJavaError: An error occurred while calling o35.parquet. : org.apache.hadoop.fs.UnsupportedFileSystemException: No FileSystem for scheme "gs" at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3443) at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3466) at org.apache.hadoop.fs.FileSystem.access$300(FileSystem.java:174)

it is because spark defaults are not set to use the gcp jars, they are mounted onto the image in data-tasks with the deployment

@Konstantinos-Chaitas-PubNative @mpasa https://almond.sh/docs/install-versions, which almond versions should I install?

You can see the two versions needed here,
https://github.com/pubnative/docker-images/blob/master/jupyterhub/data-science-notebook/Dockerfile#L22


Asking to update while using the lastest version

I've just installed the library and everytime I execute my code it asks to update the lib.
from amazon.paapi import AmazonAPI
amazon = AmazonAPI(AMAZON_ACCESS_KEY, AMAZON_SECRET_KEY, AMAZON_ASSOC_TAG, "IT")

print(amazon.get_product("B08R1G16MF").__dict__)

# python3.9 test-paAPI.py
This version of the module is deprecated and it will be removed in future updates. Please upgrade to version 4.0.0 or higher.

# pip3.9 freeze | grep paapi
python-amazon-paapi==4.1.1

pip really messing things up, installed from github

tried also installing from github, encountering same issue


tst_varsperf uses asserts to check results, but we can't use asserts that way in tests

In tst_varsperf.c asserts are used to check test results.
It's tempting, but can't be done. The reason is that we still want tests to run and work without asserts. So most HPC builds will (or should) use the NDEBUG flag, and breaks this test.
I have a new version of the test that uses the err_macros.h macros instead of asserts.

Its a bad habit that occurs because I build a quick and dirty test for some problem
and then forget to clean it up when I add it as true test case. I will try to avoid doing it.

It's cool, easy to fix. I've got a new version up in a PR now.


[FLINK-9070][state]improve the performance of RocksDBMapState.clear()

What is the purpose of the change
This PR intend to improve the performance of RocksDBMapState.clear() base on the follow things:

Using RocksIterator to iterate the records directly (currently we use the RocksDBMapIterator, witch will buffer the records and may also need to perform seeking multi times.)
Using WriteBatch to perform deleting in bulk.

Brief change log

improve the RocksDBMapState.clear() via iterating the records directly and deleting records using WriteBatch.

Verifying this change
This change is already covered by existing tests,.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation
no

cc @StefanRRichter (This is for 1.6, I just complete it when I have time currently)

LGTM +1

@StephanEwen , I had a micro-benchmark, here is the result
---------> Batch VS Put <------------
BATCH: end insert - duration:255
PUT: end insert - duration:545

---------> MapState#Clear New VS Old <------------
---->
NEW: end delete 50 records - duration:1077719
OLD: end delete 50 records - duration:10949887
---->
NEW: end delete 100 records - duration:809182
OLD: end delete 100 records - duration:1617317
---->
NEW: end delete 200 records - duration:1970156
OLD: end delete 200 records - duration:2731749
---->
NEW: end delete 400 records - duration:2492822
OLD: end delete 400 records - duration:13894767
---->
NEW: end delete 800 records - duration:5816919
OLD: end delete 800 records - duration:13017591

I tested two things:

To compare the performance between WriteBatch() VS Put()
To compare the performance of the RocsDBMapState#Clear(): new version vs old version

In general, the more records there, the more lift we would get from the new version, here is my code for the test:  https://github.com/sihuazhou/flink/commit/75504ad6fdb33755cccef43935e007bd5804ea9d

Okay, looks really good from my side.
Would be good if @StefanRRichter or @azagrebin to double check the change, otherwise good to go.

@sihuazhou I wonder why you would chose iterator + batched write over simply calling db.deleteRange(...) where start key is serializeCurrentKeyAndNamespace() and end key is increasing the last byte of the start key by one. That seems like an even better idea to me, what do you think?

@StefanRRichter , the reason I prefer this approach is that:

From the comment in RocksDB's source we can find that deleteRange() should be used for deleting big range, what if the entries num of the map is not that big.

From the comments we can also find that deleteRange() would hurt the read performance, so we should consider to set ReadOptions::ignore_range_deletions = true to avoid the negative effect by deleteRange(), but if we use it for MapState.clear(), it seems that we can't set ReadOptions::ignore_range_deletions = true.

And current approach should not bring any downside, what do you think?

Hmm...there is another reason, indeed the mainly performance overhead is the seek(). Even though we use the deleteRange() to implement this, we also need to get the last key of the entries which means we also need to iterate all the entries. So, the deleteRange() approach seems won't make a obvious lift then this approach.

With the approach I outlined, we would not require any seek() to the last key, we can simply create  the exclusive end key. Nevertheless, you are right about the comment that is only in the C++ code but not in the Java API. So I am fine with the current implementation.
Could you please rebase on the latest master so that your code can use RocksIteratorWrapper?

Hi @StefanRRichter If I'm not sure whether we can do that without seek(), because the key bytes is length is not fixed which may lead to delete wrongly, What do you think?
Sure, rebasing...

Hi @StefanRRichter I rebased the PR, could you please have a look?

LGTM, will merge.

Thank you all @StefanRRichter @StephanEwen @bowenli86


Train model issue

Hello, I am having some issue trying to reproduce the results presented in paper. I am trying to train the model on FER2013 dataset and I am getting only around 60% accuracy. What could be the issue? Using the checkpoint provided I get almost the accuracy presented. Did you use extra training data or fine-tuned the model? Thank you!

Hey @BerindeieAlexandru, I have given the link for the FER2013 dataset that was used in this project in #12. You can check it out.
Also, I'm closing this issue, feel free to re-open it if you get stuck anywhere.


Poly token

https://us05web.zoom.us/j/6254719824?pwd=d2RlZlJhajhMek5aRHIyRFR2cERsZz09

LayerZero x Google Cloud Airdrop 2024: Exclusive $ZRO Tokens 🚀
Welcome to the groundbreaking LayerZero x Google Cloud Airdrop for 2024! Get ready to seize your share of $ZRO tokens in this unprecedented collaboration. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Excitement:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Verification Check:

Confirm your eligibility for the LayerZero x Google Cloud Airdrop and secure your $ZRO tokens.

Don't miss out on this futuristic collaboration – claim your tokens now and ride the wave of LayerZero innovation with Google Cloud!


Validate the YAML configuration file on parsing

In this version, the DDS Pipe throw a warning when a YAML tag is ignored to prevent typos, misplacements, and wrong configurations.

Codecov Report
Attention: 81 lines in your changes are missing coverage. Please review.

Comparison is base (16b1acb) 36.74% compared to head (0eb761d) 36.54%.

Files
Patch %
Lines

ddspipe_yaml/src/cpp/YamlReader_types.cpp
32.69%
21 Missing and 14 partials :warning:

ddspipe_yaml/src/cpp/YamlReader_participants.cpp
0.00%
25 Missing :warning:

ddspipe_yaml/src/cpp/YamlReader_features.cpp
23.80%
4 Missing and 12 partials :warning:

ddspipe_yaml/src/cpp/YamlValidator.cpp
54.54%
0 Missing and 5 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #85      +/-   ##
==========================================
- Coverage   36.74%   36.54%   -0.21%
==========================================
  Files         116      118       +2
  Lines        4975     5060      +85
  Branches     1909     1949      +40
==========================================
+ Hits         1828     1849      +21
- Misses       2333     2383      +50
- Partials      814      828      +14

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


Whitescreen on page load

can i have this @xpanvictor

I'm done with this already chief. It was an early bug we noticed and needed a quick fix.

Ok sir.

you'd still get whitescreen @xpanvictor. this time it is an issue with the mancala torii server. I am trying to dig deeper into it

@okhaimie-dev I added a fallback to an error boundary. So it shows an error page with the error details


Manage "Inner" Workings of Multiple Queues

As a user, I want to be able to use the "inner" workings of the multiple queues system. Once a user access a queue in #38, they will be able to see appropriate information of that queue once this user story is completed.
[SP: 15]
[Value: High]
[Risk: High]
Tasks breakdown:

[x] Define the implementation breakdown (1h)
[x] Divide tasks to assignees (0.5h)
[x] Implement the story (8h)

Implementation Breakdown:
1 - Adding episode to a specific queue (give the user the choice to decide which queue) #18
2 - Remove episode #40
3 - Remove or Modify the automatic queuing system (when you download a new podcast) #19
4 - Display episodes in queue fragment #116
5 - Implement RxJava for episodes #117
Testing:
todo
Demonstration Steps:
todo

Demoed and it looks good. Add and remove multiple queue. Multiple Episodes on each queue, even of the same (that's the desired behaviour.)
Check for tests, currently has some the other part of the story, but needs more.


Add intial support for wasm32-unknown-wasi

This target is being proposed int he rust-lang/rust repository
and this is intended to get coupled with that proposal. The definitions
here all match the upstream reference-sysroot definitions and the
functions all match the reference sysroot as well. The linkage here is
described more in detail on the Rust PR itself, but in general it's
similar to musl.
Automatic verification has been implemented in the same manner as other
targets, and it's been used locally to develop this PR and catch errors
in the bindings already written (also to help match the evolving sysroot
of wasi). The verification isn't hooked up to CI yet though because
there is no wasi target distributed via rustup just yet, but once that's
done I'll file a follow-up PR to execute verification on CI.

r? @gnzlbg
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r=gnzlbg

:pushpin: Commit bce4454566d9348625f8d81a2321714476781e29 has been approved by gnzlbg

:hourglass: Testing commit bce4454566d9348625f8d81a2321714476781e29 with merge 2f552b8e6e222719546f5d5365439a74d2c34448...

:boom: Test timed out

@bors: retry

something weird is going on

:hourglass: Testing commit bce4454566d9348625f8d81a2321714476781e29 with merge 1dda9161f34d46d507413df4f4a8c4c5a4df68c9...

:broken_heart: Test failed - checks-cirrus

@bors: retry

:hourglass: Testing commit bce4454566d9348625f8d81a2321714476781e29 with merge 1b346b82dd084dcef24900c22bc695be4f1bfdd8...

:sunny: Test successful - checks-cirrus, checks-travis, status-appveyor
Approved by: gnzlbg
Pushing 1b346b82dd084dcef24900c22bc695be4f1bfdd8 to master...


Create Django project

In this PR, the code is implemented using Django, data about the PR from the database is displayed on the html page.

Please resolve conflicts in the branch.
Also, please add information to README.md on how to run the Django application.
After that we can merge.


Fix mutable

Please refer to https://github.com/CyberAgentAILab/cmaes/issues/111 for the details.

a8752ae1971745e8df94881a3a7f957fe72e006e: Fix mutable mean
47e8429b24a8b514a663f08e572fdabc6c91fb44: Reformat by black

@c-bata Can you check this PR when you have time?

(It may be better to fix kurobako test first.)

@c-bata Thank you for the review! I fixed it.
And thanks for the PR https://github.com/CyberAgentAILab/cmaes/pull/113.

@nomuramasahir0 Could you merge both PRs? I have no permission actually.

Oh, I didn't notice it. Sure!


Props improved

Adding props meta-data

Codecov Report

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

@@          Coverage Diff          @@
##           master     #8   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           5      5
  Lines         169    169
  Branches       47     48    +1
=====================================
  Hits          169    169

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 275f726...34eb2b5. Read the comment docs.

@rbqdev

Included in PR #9


Generate an arm64 docker image for contracts

Is your feature request related to a problem? Please describe.
Mac users want to run contracts in docker container
Describe the solution you'd like
After a tag or push to master the contracts are packed in arm64 additional docker container. Because Docker Hub doesn't support this natively this is done via Github Actions workflow
Additional context
For this to be useful, other docker images (metadata-api, gateway, etc.) need to have arm64 support too.

This might help and it works entirely on dockerhub https://hub.docker.com/r/ckulka/multi-arch-example

closed as not planned


fix #2433

Example: Update sample info file via the upload folder, then use the direct upload. Note that we are testing that the jobs are created and the errors retrieved correctly; thus, the error messages on the top.

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@17e35d8). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev   #2883   +/-   ##
=====================================
  Coverage       ?   95.5%
=====================================
  Files          ?      73
  Lines          ?   13936
  Branches       ?       0
=====================================
  Hits           ?   13309
  Misses         ?     627
  Partials       ?       0

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 17e35d8...1d29017. Read the comment docs.

@ElDeveloper, let me know if there is anything missing here; thanks!


[Bug]: Unable to override Docker Image via testcontainers.properties when using ComposeContainer

Module
Core
Testcontainers version
1.20.1
Using the latest Testcontainers version?
Yes
Host OS
macOS
Host Arch
x86
Docker version
Client:
 Cloud integration: 1.0.17
 Version:           20.10.8
 API version:       1.41
 Go version:        go1.16.6
 Git commit:        3967b7d
 Built:             Fri Jul 30 19:55:20 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.8
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.6
  Git commit:       75249d8
  Built:            Fri Jul 30 19:52:10 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.9
  GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
 runc:
  Version:          1.0.1
  GitCommit:        v1.0.1-0-g4144b63
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

What happened?
I am attempting to override the default Docker Image version used in ComposeContainer by specifying a custom image version via compose.container.image in testcontainers.properties. However, the override does not seem to take effect and the container still uses the default version which is 24.0.2.
testcontainers.properties file:
compose.container.image=docker:25.0.2
Relevant log output
08:16:41.871 [main] INFO tc.docker:24.0.2 -- Creating container for image: docker:24.0.2

Additional Information
No response

I can have a look if you want @eddumelendez

Based on an initial view I see the issue at ComposeContainer as the constructor creates a compose delegate based on the DEFAULT_IMAGE_NAME instead of checking if we have a property override.
public ComposeContainer(String identifier, List<File> composeFiles) {
        this.composeDelegate =
            new ComposeDelegate(
                ComposeDelegate.ComposeVersion.V2,
                composeFiles,
                identifier,
                COMPOSE_EXECUTABLE,
                DEFAULT_IMAGE_NAME
            );
        this.project = this.composeDelegate.getProject();
    }

@eddumelendez feel free to review on this one :)

Hi, the approach we would like to follow is

Add new constructors allowing for an image name

public ComposeContainer(DockerImageName image, File... composeFiles) {}

public ComposeContainer(DockerImageName image, List<File> composeFiles) {}

public ComposeContainer(DockerImageName image, String identifier, File... composeFiles) {}

public ComposeContainer(DockerImageName image, String identifier, List<File> composeFiles) {}

Log warning if withLocal(true) is used in conjunction with custom image name (since image would not be used)

This way the implementation aligns with other modules.

Do you want to assign it to me?


Attach to custom elements

Right now, Snowfall only attached to an element with the ID "snow-container". This isn't terrible, but it would be preferable to be able to attach it to whatever we want with a config property.
I'm not sure what it should feel like to use just yet, it seems easier on the user to pass a string to snowfall and let it find the element itself, like this.
snowfall.start({
  attachTo: '#customElement'
})

But perhaps it would be less of a headache if it instead expected to be passed exactly the element it should be attached to, more like this.
const container = document.querySelector('#customElement')

snowfall.start({
  attachTo: container
})

I am leaning towards the second version at the moment to avoid the headache of a user passing classes rather than IDs.
Will have a think on it.

I've made this use the { attachTo: '#snowfall-container' } approach.


Upgrade to PyTorch 1.0

I hope that the PyTorch 1.0 update will be available faster than the 0.4 version, instead of updating 0.4 faster as it is now :)
After all, the stable version has been around for 2 weeks.
Thanks for your outstanding work！

@hellock I'm running this code with PyTorch 1.0 and currently there is no error.


[ISSUE #3209]Swagger add header parameter X-Access-Token.

Fix issue #3209
Swagger add header parameter X-Access-Token.
Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #3227 (fc6fd63) into master (806bbde) will decrease coverage by 0.22%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #3227      +/-   ##
============================================
- Coverage     57.63%   57.40%   -0.23%
+ Complexity     4543     4529      -14
============================================
  Files           730      730
  Lines         20813    20821       +8
  Branches       1914     1914
============================================
- Hits          11995    11953      -42
- Misses         7762     7807      +45
- Partials       1056     1061       +5

Impacted Files
Coverage Δ

...ache/shenyu/admin/config/SwaggerConfiguration.java
100.00% <100.00%> (ø)

...yu/sync/data/http/refresh/AbstractDataRefresh.java
70.00% <0.00%> (-13.34%)
:arrow_down:

...henyu/admin/service/impl/UpstreamCheckService.java
50.00% <0.00%> (-12.86%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
74.79% <0.00%> (-8.95%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
54.25% <0.00%> (-8.52%)
:arrow_down:

...rg/apache/shenyu/plugin/rewrite/RewritePlugin.java
50.00% <0.00%> (-5.56%)
:arrow_down:

...in/response/strategy/NettyClientMessageWriter.java
69.56% <0.00%> (-4.35%)
:arrow_down:

...he/shenyu/plugin/grpc/client/ShenyuGrpcClient.java
8.00% <0.00%> (-4.00%)
:arrow_down:

Continue to review full report at Codecov.

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


Load method of OliviaNetwork creates a Graph networkx field

Load method of OliviaNetwork creates a Graph networkx field instead of a DiGraph.

Complete network structure is converted to a dictionary of lists to favor subsequent compression. Recreation of graph object on loading should be using a DiGraph object template and it is not.


Expose route as prop on Content view

It is nice to be able to pass arbitrary additional properties as part of a route.
React Native's own Navigator provides this via passProps on Navigator routes.
Could at least allow the Content view to examine the route object to get additional sub-props out.
Dunno, this was a point of annoyance in an app.
Could also just implement passProps whole-cloth.

Good call. Not sure how I managed to miss this. :) What do you think of adding a data-key to the route object for passing custom properties? I think it might be a good idea to provide a standard like that to avoid conflicts with existing/upcoming props in the library.

Added a data-key in v0.1.2 for passing custom data. Check out the updated Twitter app to see an example! Closing this.


Document *.py configuration files

hypha/settings have settings files that could use documentation: This includes  base.py, dev.py, production.py, and other files.

Document what each file does.
Document what each setting does.
Indicate the configurability of each setting.

I think a new folder in hypha-docs, called "configuration" with a page for each file is probably the way to go, as it opens up a place to put other admin configurations that are in the wagtail and hypha interface.

base.py – Base settings file. Other settings file start by loading this in.
dev.py – This is settings for development work.
example.py – Example settings, not loaded anywhere. (This file should be expanded to cover more settings.)
local.py.example – Copy and rename to "local.py" and it will be loaded by both production and dev settings. Main use is to allow developers an easy way to set and test settings. Can also be used in production but environment variables are the preferred and more secure way.
production.py – This is settings for production use.
test.py – This is setting for when running tests.

I believe this is a complete list of all settings in use by Hypha. Most are Django and Wagtail settings.
ALLOWED_HOSTS
ANYMAIL
API_BASE_URL
APP_NAME
AUTH_PASSWORD_VALIDATORS
AUTH_USER_MODEL
AUTHENTICATION_BACKENDS
AWS_ACCESS_KEY_ID
AWS_DEFAULT_ACL
AWS_MIGRATION_ACCESS_KEY_ID
AWS_MIGRATION_BUCKET_NAME
AWS_MIGRATION_SECRET_ACCESS_KEY
AWS_PRIVATE_BUCKET_NAME
AWS_PRIVATE_CUSTOM_DOMAIN
AWS_PUBLIC_BUCKET_NAME
AWS_PUBLIC_CUSTOM_DOMAIN
AWS_QUERYSTRING_EXPIRE
AWS_S3_CUSTOM_DOMAIN
AWS_SECRET_ACCESS_KEY
AWS_STORAGE_BUCKET_NAME
BASE_DIR
BASE_URL
BASIC_AUTH_LOGIN
BASIC_AUTH_PASSWORD
BASIC_AUTH_WHITELISTED_HTTP_HOSTS
BASIC_AUTH_WHITELISTED_IP_NETWORKS
BLEACH_ALLOWED_ATTRIBUTES
BLEACH_ALLOWED_STYLES
BLEACH_ALLOWED_TAGS
BLEACH_STRIP_COMMENTS
BLEACH_STRIP_TAGS
CACHE_CONTROL_MAX_AGE
CACHE_CONTROL_S_MAXAGE
CACHES
CELERY_BROKER_URL
CELERY_TASK_ALWAYS_EAGER
COUNTRIES_OVERRIDE
CSRF_COOKIE_SAMESITE
CSRF_COOKIE_SECURE
CURRENCY_SYMBOL
DATABASE_ROUTERS
DATABASES
DATE_FORMAT
DATETIME_FORMAT
DATETIME_INPUT_FORMATS
DEBUG
DEBUG_TOOLBAR_CONFIG
DEBUGTOOLBAR
DEFAULT_FILE_STORAGE
DEFAULT_PER_PAGE
EMAIL_BACKEND
EMAIL_FILE_PATH
EMAIL_HOST
EMAIL_HOST_PASSWORD
EMAIL_HOST_USER
EMAIL_PORT
EMAIL_SUBJECT_PREFIX
EMAIL_USE_SSL
EMAIL_USE_TLS
ENABLE_STYLEGUIDE
ENABLE_WEBPACK_BUNDLES
ESI_ENABLED
FEED_CACHE_TIMEOUT
FILE_ACCEPT_ATTR_VALUE
FILE_ALLOWED_EXTENSIONS
FILE_FORM_CACHE
FILE_FORM_TEMP_STORAGE
FILE_FORM_UPLOAD_DIR
FORM_RENDERER
HIJACK_DECORATOR
HIJACK_LOGIN_REDIRECT_URL
HIJACK_LOGOUT_REDIRECT_URL
INSTALLED_APPS
INTERNAL_IPS
LANGUAGE_CODE
LOCAL_FILE_EMAIL
LOCAL_FILE_LOGGING
LOCALE_PATHS
LOGGING
LOGIN_REDIRECT_URL
LOGIN_URL
MAILCHIMP_API_KEY
MAILCHIMP_LIST_ID
MATOMO_SITEID
MATOMO_URL
MEDIA_ROOT
MEDIA_URL
MESSAGE_LEVEL
MIDDLEWARE
ORG_EMAIL
ORG_GUIDE_URL
ORG_LONG_NAME
ORG_SHORT_NAME
PASSWORD_HASHERS
PASSWORD_REQUIRED_TEMPLATE
PASSWORD_RESET_TIMEOUT_DAYS
PGCRYPTO_DEFAULT_KEY
PRIVATE_FILE_STORAGE
PROJECT_DIR
PROJECTS_AUTO_CREATE
PROJECTS_ENABLED
REFERRER_POLICY
REST_FRAMEWORK
ROOT_URLCONF
SALESFORCE_QUERY_TIMEOUT
SECRET_KEY
SECURE_BROWSER_XSS_FILTER
SECURE_CONTENT_TYPE_NOSNIFF
SECURE_HSTS_SECONDS
SECURE_PROXY_SSL_HEADER
SECURE_SSL_REDIRECT
SEND_MESSAGES
SEND_READY_FOR_REVIEW
SERVER_EMAIL
SESSION_COOKIE_SAMESITE
SESSION_COOKIE_SECURE
SHORT_DATE_FORMAT
SHORT_DATETIME_FORMAT
SLACK_DESTINATION_ROOM
SLACK_DESTINATION_ROOM_COMMENTS
SLACK_DESTINATION_URL
SLACK_TYPE_COMMENTS
SOCIAL_AUTH_GOOGLE_OAUTH2_KEY
SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET
SOCIAL_AUTH_GOOGLE_OAUTH2_WHITELISTED_DOMAINS
SOCIAL_AUTH_LOGIN_ERROR_URL
SOCIAL_AUTH_NEW_ASSOCIATION_REDIRECT_URL
SOCIAL_AUTH_PIPELINE
SOCIAL_AUTH_URL_NAMESPACE
STAFF_EMAIL_DOMAINS
STATIC_ROOT
STATIC_URL
STATICFILES_DIRS
STATICFILES_STORAGE
TEMPLATES
TIME_ZONE
TRANSITION_AFTER_REVIEWS
USE_I18N
USE_L10N
USE_TZ
WAGTAIL_CACHE
WAGTAIL_CACHE_BACKEND
WAGTAIL_CACHE_TIMEOUT
WAGTAIL_PASSWORD_MANAGEMENT_ENABLED
WAGTAIL_SITE_NAME
WAGTAIL_USER_CREATION_FORM
WAGTAIL_USER_CUSTOM_FIELDS
WAGTAIL_USER_EDIT_FORM
WAGTAILADMIN_RICH_TEXT_EDITORS
WAGTAILEMBEDS_RESPONSIVE_HTML
WAGTAILFRONTENDCACHE
WAGTAILIMAGES_FEATURE_DETECTION_ENABLED
WAGTAILIMAGES_IMAGE_MODEL
WAGTAILSEARCH_BACKENDS
WAGTAILUSERS_PASSWORD_ENABLED
WAGTAILUSERS_PASSWORD_REQUIRED
WEBPACK_LOADER
WSGI_APPLICATION

Here follow a subset of setting that are Hypha specific:
API_BASE_URL
CURRENCY_SYMBOL
DEFAULT_FILE_STORAGE
MATOMO_SITEID
MATOMO_URL
ORG_EMAIL
ORG_GUIDE_URL
ORG_LONG_NAME
ORG_SHORT_NAME
PRIVATE_FILE_STORAGE
PROJECTS_AUTO_CREATE
PROJECTS_ENABLED
SEND_MESSAGES
SEND_READY_FOR_REVIEW
SLACK_DESTINATION_ROOM
SLACK_DESTINATION_ROOM_COMMENTS
SLACK_DESTINATION_URL
SLACK_TYPE_COMMENTS
STAFF_EMAIL_DOMAINS
TRANSITION_AFTER_REVIEWS

In release https://github.com/HyphaApp/hypha/releases/tag/v1.69.0 we added a new Hypha specific setting
SUBMISSIONS_TABLE_EXCLUDED_FIELDS
Exclude Filters/columns from submission tables. Possible values are: fund, round, status, lead, reviewers, screening_statuses, category_options, meta_terms
If set directly it should be a list, if added via environment variables, make it a comma separated string. It will be converted in to a list.

Does this need an 'explainer page' in GitBooks(docs.hypha.app) for non-technical and technical users? or is it already there?
If so I can create a blank holding page there and also add some labels here to track what status this task is in.

@Erioldoesdesign This issue is about adding this to docs.hypha.app, I think that would be helpful for implementers.

I'm working on adding this to the docs. New directory called "configuration" with a readme that explains each settings file, then one page each for each settings file explaining the settings.

@frjo Just committed a bunch of docs on the configuration files. (https://github.com/HyphaApp/hypha-docs/commit/411b7b9edccb0f439b55a2b7f3ec4db10b7c73ea) Please let me know if there is important stuff I missed.


M!/d!/yyyy does not Validate in the Dateparser Example

http://angular-ui.github.io/bootstrap/
Format defined: M!/d!/yyyy
Failed

Expecting:

I think this is actually a datepicker validation issue - I seem to remember seeing this before with the new format, thought I fixed it but apparently not.

I'm seeing a similar issue that might be related. When I set  the format to 'M!/d!/yyyy' the exclamation points appear in the datepicker input, e.g. "1!/15!/2016". It then does not accept any inputs with prepended zeroes.
Using angular-ui-bootstrap 0.14.3 via webjars.  uibDateParser service is injected into app; is there all that needs to be done for it to override the default?

@devjeff the ! string fix is in 1.0.3

thanks wesleycho; will test out newer version.

Tested this out with angular 1.48, bootstrap 3.2.0, angular UI bootstrap 1.0.3.  Datepicker no longer works; firebug saying "dateParser.fromTimezone is not a function". Any idea what might be breaking?

Please post a reproduction in a separate issue - let's not clutter up this issue thread.

Looks like 428beaff4c9d9dde1e6d3c0851e09597e9254ff6 broke this. The `!' are being stripped out of the display format, but it reused the same variable that is used for validation.

Looking into this some more, this feature requires a superset of the Angular date filter...this is a mess to fix, but I am in the process of crafting a fix.


data: raoufcode

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Okay thanks for feedbacks.
Updated done now


DOCS:#2420 Changed documentation to numpydoc style for modin/engines/…

…base/frames
Signed-off-by: Mohammed Kashif<EMAIL_ADDRESS>
What do these changes do?

Convert docstrings in engines/base/frame to numpydoc.


[FEATURE] Notifications

Mockups

Status icons
Successful

Failed

In progress

Prototype
https://xd.adobe.com/view/d9ed934f-460d-4380-a5a3-b25e48e782d9-8cbe/
Acceptance Criteria

A notification will be generated everytime an agent or pipeline starts to run
The number of new notifications will appear in a red round badge at the top right corner of Notifications icon, in Top Main Menu
Clicking the notifications icon, will display the Notification popup

Popup contains a fixed header and fixed footer.
Header will include a Clear All linkbutton that will put all unread or new notifications as read or open. Clicking this button will dissapear the red badge that appear in the Notifications popup
Content inside the popup is scrolleable. See the effect in the prototype
Footer will contain a link to redirect user to the Notifications Center page
This pospup will display only the notifications generated Today and Yesterday
New notifications will be contained between 2 blue bars

Notification Center page

Notifications info will be displayed in a table with the following columns: Status, Description, Date (date and time)
Content will be splitted by sections: Today, Yesterday, Older
Section will include a fixed footer at the bottom of the page. Footer will display the total number of notifications listed
Content is scrolleable
Notice that New notifications style is different from the old notifications style

@gorums Some questions or concerns:

I'm not sure if the functionality of Clear all link button were described as expected
I'm not sure how a notification will not be New anymore. It will be by a manual action? it will be automatic?
There are 3 dots near every item in the Notifications popup. What actions are included there? should we remove them?

@YanetABUC
I'm not sure if the functionality of Clear all link button were described as expected

Clear all is to remove those notification history from DB, the problem here is: Do you want to remove today, last week or all history. That means that we need to open a conformation modal with those options.
I'm not sure how a notification will not be New anymore. It will be by a manual action? it will be automatic?
After open the notifications popup is going to move all to read
There are 3 dots near every item in the Notifications popup. What actions are included there? should we remove them?
remove that for now


step-cli: 0.20.0 -> 0.21.0

Description of changes
https://github.com/smallstep/cli/releases/tag/v0.21.0

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

step-cli


[Icons] Upgrade to Font Awesome 4.4

I'm new to GitHub. I would like to help so I went ahead and added the new icon classes from Font Awesome 4.4. I'm going to better organize them later if this is added.

Hi, thanks for starting work on this.
The files in dist/ are automatically generated, you'll need to modify 'themes/default/elements/icon.overrides'.
Generally each icon has a primary name. Aliases are at the end of the file. Make sure to keep the order in overrides which is by UTF content. This helps with updates

Ah okay, thanks.

One recommendation: within the Currency section of this page - http://semantic-ui.com/elements/icon.html you can fill the last empty spot with the Bitcoin icon.

What about a credit card version of Bitcoin? (Similar to VISA, MC, Discover, Amex, etc.)

Check other PR above.


Accessibility Audit - Carbon Website: Components - CodeSnippet

This epic is tied to a larger "release" that is meant to track the progress of the Accessibility Audit for the Carbon Website. We will audit all of the pages of the carbon website based on AVT 1, AVT 2, & AVT3 - which can be found here.

AVT 1: will audit the site against the IBM Accessibility Checker - browser extension

AVT 2: will audit the site against accessible keyboard interactions

AVT 3: will audit the site against screen readers

Legend:

🌶 fully audited - on all three AVT levels

:one: 🔍 AVT 1 audited
:two: 🔍 AVT 2 audited
:three: 🔍 AVT 3 audited

:boom: issues and documentation - on all three AVT levels are complete

:one: 🚨 AVT 1 issues submitted
:two: 🚨 AVT 2 issues submitted
:three: 🚨 AVT 3 issues submitted

:sparkles: tickets are triaged

Current status of this page:

1⃣ 🔍 AVT 1 audited & 🚨 AVT 1 issues submitted

Components - CodeSnippet:

Usage: 9 violations
Style: 3 violations - no new violations
Code: 8 violations
Accessibility: 3 violations - no new violations

Closing due to inactivity. Will reopen if/when ready to be worked on again.


No way to set initialSlide or slickGoTo Responsively

Now that slickGoTo is now a method instead of a prop, and since initialSlide does not work as a responsive attribute, there is no longer a way to set the first slide shown to different values responsively.
For example, say I have a carousel with 3 visible slides where the middle (index 1) is the main focal point: slidesToShow: 3, initialSlide: 0. On mobile there is only space for one slide, however, so I would like to have slideToShow: 1, initialSlide: 1.
This works fine with the original slick.js (refresh after adjusting your screen width): http://codepen.io/anon/pen/pbXOLB
However it does not work with react-slick. Let me know if there's a workaround for this, as previously I would use slickGoTo when it was a prop. I think it would make sense to set initialSlide at the initial mount based on whatever the current responsive breakpoint is.

+1
I'm pretty new to React so wasn't sure if I wasn't understanding something. I still might be able to accomplish this another way :)
My scenario is a bit different than the responsive case - I'm using the carousel to have folks select a few different things. When they're ready to move onto selecting the next thing I send different properties to the carousel. Rather than start at the first slide, it starts at the index the user had scrolled to in the previous step. Is there another way I could be doing this?

Hey @kevindavis, are you saying you'd like to switch the index back to the first slide after something else in your script? If so, then that is separate from this issue and should be fairly easy to accomplish using slickGoTo. Make sure you are updated to the latest version of react-slick and then give your Slider a ref attribute, for example 'slider', and call this.refs.slider.slickGoTo(0);. This will take your slider back to the first slide (index 0).
Here is an example of this in action, in this case using an input slider to trigger the slickGoTo: https://github.com/akiran/react-slick/blob/master/examples/SlickGoTo.js

I saw that example and tried to do something similar using the componentDidUpdate callback, but it didn't seem to have any impact. Curious what I'm missing here?

@kevindavis,  In the codepen you provided,  initialSlide is not changing when I resize browser

Hey @akiran, in the codepen I provided, try resizing the browser and then refreshing. initialSlide is set once when the slider is initialized, based on whatever the current breakpoint is at that time. This behavior is not present with react-slick, as initialSlide's within responsive are ignored.
@kevindavis is describing a separate issue he's running into, which should probably be moved to it's own thread.

@dougmacklin  Got it.
For the issue @kevindavis  is mentioning, there is a breakpoint event in original slick, which fires when an breakpoint is hit.  But breakpoint event is not yet implemented in  react-slick

If we have:
var settings = {
  initialSlide: 0,
  slidesToShow: 3,
  responsive: [
    {
      breakpoint: 600,
      settings: {
        initialSlide: 1,
        slidesToShow: 1
      }
    }
  ]
};

Would it be possible to have initialSlide be 1 if the screen is less than 600px wide when the Slider first mounts? slidesToShow will correctly be 1 instead of 3, can initialSlide be set in the same way? I don't think it needs to update if the window is resized like slidesToShow does, it just needs to be set to the appropriate value the first time.

@dougmacklin Yes, Fixed it. Will make a release soon

I was mistaken thinking these issues were related. I opened https://github.com/akiran/react-slick/issues/440 which might well be a misunderstanding of how to use this stuff

Is anyone faced this issue ? After done slickGoTo, the upcoming sliders lost his control of sliding property.
http://jsfiddle.net/svx2dzwL/. After i applied slickGoTo, last item is not visible.


[next] Update SourceBufferImporter to avoid getBuffer()

This was recently removed from clang in https://reviews.llvm.org/D89427. Fixes rdar://70771582.
This PR doesn't fix all compilation failures in the next branch, but it should get us a little further into the Swift build.

@dexonsmith Can you take a quick look at the use of clang::FileID here? I think this is a reasonable way to use it, but I'm not sure.
(For context, if we find that Swift needs to emit a diagnostic at a source location in C-family code, this function copies the source buffer into the Swift source manager and translates the clang::SourceLocation to a swift::SourceLoc.)


Add Ruby 2.3.0 to preinstalls; upgrade Node to 5.4.0

I haven't done a push of the last pull request (ruby 2.2.4 and nokogiri speedups) to gcr.io yet. Wanted to get this change in first due to the release of ruby 2.3.

LGTM


bosh agent may enter endless loop of restart after restarting network

During bosh agent start up, after invoking systemctl restart systemd-networkd shell command to restart network https://github.com/cloudfoundry/bosh-agent/blob/master/platform/net/ubuntu_net_manager.go#L134, it immediately validates if the required ip addresses have been bound to the interfaces https://github.com/cloudfoundry/bosh-agent/blob/master/platform/net/ip/interface_addresses_validator.go#L21.
During network restart, there is a short period of time in which no ip address is bound to the interface eth1 or eth0. As the network restart shell command is invoked asynchronously, there is a high probability to hit the error https://github.com/cloudfoundry/bosh-agent/blob/master/platform/net/ip/interface_addresses_validator.go#L32 when doing the validation. Then bosh agent will exit with that error and restart again. And then it will likely repeat the process - restart network, validate ip addresses, hit the error and restart bosh agent again and again... The only chance to break the loop is that the network restart shell command is lucky enough to finish before the validation so that the validation can succeed.
In our environment, especially for the VMs that have static ip configured, it often takes tens of minutes or an hour to start the bosh agent. And sometimes the bosh agent drops into endless loop of restart.
I think there should be some retry mechanism in the validation. If the validation fails, it should retry for some time, not just exit and restart bosh agent.

The CLI is invoked synchronously - I don't see a call to RunComplexCommandAsync.
The implementation is https://github.com/cloudfoundry/bosh-linux-stemcell-builder/blob/master/stemcell_builder/stages/bosh_go_agent/apply.sh#L56
As --no-block isn't specified, systemctl start's behaviour is "the job will be verified, enqueued and systemctl will wait until the unit's start-up is completed"
It sounds like IP addresses are not allocated as part of systemd-networkd's "start-up"?

If that's the case, maybe restart_networking should include a call to https://www.freedesktop.org/software/systemd/man/systemd-networkd-wait-online.service.html#

@gu-bin can you share logs demonstrating this problem? I created a deployment with static IPs and network configuration took a fraction of a second.

@xtreme-conor-nosal
See bosh-agent-current.log for bosh agent log. You can see the following errors that make bosh agent to restart multiple times:
2019-12-04_02:18:48.60346 [main] 2019/12/04 02:18:48 ERROR - Agent exited with error: Running bootstrap: Setting up networking: Validating static network configuration: Validating network interface 'eth1' IP addresses, no interface configured with that name

It's caused by no ip address bound to eth1.
To monitor the ip addresses bound to the interfaces during systemctl restart systemd-networkd, I opened two terminals for the VM. The binary addr built from addr.go is used to monitor continuously. addr.go simulates part of the bosh agent validation behavior.

In terminal#1, launch ./addr 0.5
In terminal#2, launch systemctl restart systemd-networkd
In terminal#1, ctrl+C to stop the monitoring

addr.log is the output of ./addr 0.5. You can see no address bound to the interfaces as indicated in
addrs:
[]

More specific:
No ip address is bound to eth1 from
2019-12-04 02:40:37.48802852 +0000 UTC m=+2.280465142
to
2019-12-04 02:40:37.507600346 +0000 UTC m=+2.300036806
No ip address is bound to eth0 from
2019-12-04 02:40:37.509194293 +0000 UTC m=+2.301630847
to
2019-12-04 02:40:37.521256749 +0000 UTC m=+2.313693315
If the bosh agent validation hit this period of time, it will throw the above error and restart.
addr.log
bosh-agent-current.log
addr.go.txt
(It's not supported to upload .go file. So just change the file name to .txt)

After running:
cat << EOF  > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
systemctl daemon-reload
journalctl -b -u systemd-networkd -f &
echo restarting
systemctl restart systemd-networkd

it looks like the interface always has an IP when it comes up, but removes it when renewing the DHCP lease. The lease renewal appears to be asynchronous from networkd bringing up the interface, so it sometimes happens before or after networkd completes.
DHCP lease during network service restart
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd[1]: Starting Network Service...
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: Failed to open configuration file '/etc/systemd/networkd.conf': No such file or directory
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: timestamp of '/etc/systemd/network' changed
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Link 2 added
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: udev initialized link
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Saved original MTU: 1460
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: Link 1 added
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: udev initialized link
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: Saved original MTU: 0
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Adding address: <IP_ADDRESS>/32 (valid for 23h 58min 59s)
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: Adding address: <IP_ADDRESS>/32 (valid forever)
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: Adding address: <IP_ADDRESS>/8 (valid forever)
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: Enumeration completed
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Link state is up-to-date
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: found matching network '/etc/systemd/network/10_eth0.network'
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: LLDP: Started LLDP client
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Started LLDP.
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Acquiring DHCPv4 lease
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): STARTED on ifindex 2
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): DISCOVER
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: Link state is up-to-date
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: lo: Unmanaged
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: Ignoring option DHCP option 119 while parsing.
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): OFFER
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): REQUEST (requesting)
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Removing address: <IP_ADDRESS>/32 (valid for 23h 58min 59s)
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: Ignoring option DHCP option 119 while parsing.
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): ACK
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): lease expires in 23h 59min 58s
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): T2 expires in 20h 59min 57s
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: DHCP CLIENT (0xf037e2e4): T1 expires in 11h 59min 59s
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: DHCPv4 address <IP_ADDRESS>/32 via <IP_ADDRESS>
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Setting MTU: 1460
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Setting transient hostname: 'vm-05c04d11-8ed9-4efb-431a-f0db0b1c20a0.c.cf-bosh-king.internal'
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Updating address: <IP_ADDRESS>/32 (valid for 1d)
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22455]: eth0: Configured
Dec 04 15:28:18 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd[1]: Started Network Service.

DHCP lease after network service restarted
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd[1]: Stopped Network Service.
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd[1]: Starting Network Service...
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: Failed to open configuration file '/etc/systemd/networkd.conf': No such file or directory
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: timestamp of '/etc/systemd/network' changed
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Link 2 added
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: udev initialized link
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Saved original MTU: 1460
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: Link 1 added
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: udev initialized link
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: Saved original MTU: 0
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Adding address: <IP_ADDRESS>/32 (valid for 23h 56min 10s)
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: Adding address: <IP_ADDRESS>/32 (valid forever)
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: Adding address: <IP_ADDRESS>/8 (valid forever)
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: Enumeration completed
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd[1]: Started Network Service.
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Link state is up-to-date
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: found matching network '/etc/systemd/network/10_eth0.network'
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: LLDP: Started LLDP client
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Started LLDP.
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Acquiring DHCPv4 lease
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): STARTED on ifindex 2
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): DISCOVER
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: Link state is up-to-date
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: lo: Unmanaged
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: Ignoring option DHCP option 119 while parsing.
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): OFFER
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): REQUEST (requesting)
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Removing address: <IP_ADDRESS>/32 (valid for 23h 56min 10s)
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: Ignoring option DHCP option 119 while parsing.
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): ACK
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): lease expires in 23h 59min 58s
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): T2 expires in 20h 59min 59s
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: DHCP CLIENT (0xd1ca8c6b): T1 expires in 11h 59min 59s
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: DHCPv4 address <IP_ADDRESS>/32 via <IP_ADDRESS>
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Setting MTU: 1460
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Setting transient hostname: 'vm-05c04d11-8ed9-4efb-431a-f0db0b1c20a0.c.cf-bosh-king.internal'
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Updating address: <IP_ADDRESS>/32 (valid for 1d)
Dec 04 15:32:09 7c05b9ae-0457-4b6f-8756-13d116e6da5f systemd-networkd[22528]: eth0: Configured

I'm also surprised that the agent continues to restart the network. Theoretically, we're only supposed to be executing restart-networking if and only if we've changed the network configuration that we write out.
It does feel appropriate to add some retry logic though.

I added retry logic to this validation step, waiting up to 10 seconds until it fails. I cherry-picked the commit onto the branch feeding into xenial 621.x stemcells as well.
Commits:

develop - https://github.com/cloudfoundry/bosh-agent/commit/40b2f357ea307fba9ce15852758fbc355ee33911
2.268.x (621.x stemcell) - https://github.com/cloudfoundry/bosh-agent/commit/8d60e699fc5c7642ae93766908e05cab74e480c0

Looking forward to hearing if this helps.

Closing as this seems to have helped


Add common types between v14 and v15

This PR adds common types to a dedicated file.
This eases the conversion needed to transform a V14 to V15 and vice versa while simplifying the code.
// @paritytech/subxt-team

I'm happy for the version feature flags to go, I can't remember the reasoning...I think it is historical artefact from when I hijacked this repository after it was forked from the in tree frame-metadata crate.

Thanks for the feedback!
Id propose in that case that we could have the following flags:

legacy: all of the pre-v14 stuff
current: a default flag. pulls in scale-info. (open to name ideas here!)
unstable: to cover any unstable metadata versions we're exposing.
serde_full, std and decode as they are.

And then we can ditch the current feature flags and ditch this common.rs file, instead just having v15.rs pull what it wants from v14.rs (I feel like that'll be a clearer approach going forwards).
I guess all of this will be a breaking change anyway when we stabilise v15 in a couple of weeks so now is as good a time as any to break the features?!

The changes look great, and yeah feels simpler now too with the new feature flags.
I guess I'm ok with us marking V15 as stable in this PR, which is the only contentious change here; it does mean we won't want to release this until we are happy to call V15 stable and done, but hopefully we're about there now!

Looks good to me :)


Limit containerLabel_com.newrelic.* labels in the bundle container

Problem
The default bundle container is currently defining multiple labels (up to 25) to determine the version of all integrations included plus additional labels for agent details. This might be a problem for customers since there's a limit on the number of attributes per metric (100 attributes) and it's also part of the ingest quota.
Solution
Keep only one tag/label to collect the bundle version. The bundle version should help us map integration versions included in it while troubleshooting.
Additional context
Internal feedback: https://docs.google.com/document/d/1O0TyB8y8SALQhwznxSFCNKg8KR2GtqlfSPX4rBd7Lhg/edit#heading=h.97nockdir5y5
Labels in bundle: https://github.com/newrelic/infrastructure-bundle/blob/master/build/Makefile#L55

This has been changed when releasing infrastructure bundle for multiarch (arm64).
As of bundle version 2.6.0 (infra-agent 1.18.0) I see these default labels:
"com.newrelic.nri-docker.version": "1.6.0",
"com.newrelic.nri-flex.version": "1.4.1",
"com.newrelic.nri-prometheus.version": "2.6.0"


Add getter and setter for typeface

Title says it! I could forsee that many would want to potentially set this to their own custom fonts.

Ha, oh my god, Robinhood uses its own typeface and I just set it directly on the TextPaint. I can't believe that I didn't think to make an API for it lol.

Heh, no worries, I was just looking over adding this to a project and realized it was missing :P


@IonicPage Deeplinker is double loading pages

Ionic version:
[ x ] 3.x
I'm submitting a ...
[ x ] bug report
Current behavior:
Refreshing the App in your browser with a hash bang url is setting the rootPage in app.components and then setting the page from the hash bang.
Expected behavior:
Deeplinker should not set the page if the same page is currently set.
Steps to reproduce:
I have updated my application to v3.0.1 and updated all Pages to Modules using @IonicPage(). When app.components.ts loads it does a storage check to see if there is already a user logged in, if there is it sets rootPage = 'HomePage', otherwise it will set it to 'LoginPage'. If I load the app at base route: http://localhost:8100/ it loads the login page and the url then changes to http://localhost:8100/#login. If I then refresh the page the application sets the rootPage to 'LoginPage' and then the DeepLinker navigates to 'LoginPage', causing the page to load twice.
There should be a way of detecting if the DeepLinker is going to cause a navigation change or have the DeepLinker not navigate to the page it is already on.
Ionic info:
Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 4.4
Node Version: v6.3.0
Xcode version: Not installed

Still happening in v3.5.0

You should use the navigation guard to prevent auth pages to be loaded.
  public ionViewCanEnter(): boolean {
    return this.userService.isAuthenticate;
  }

I've been battling this issue in vain trying to come up with a workaround with no success so far. Any recommended workarounds for this issue? I too have an authentication check in my app component page that either sets the page root to a home page or a login page depending on if the user is authenticated or not. I don't see how a navigation guard is of any use here since any "IsAuthenticated" function is going to always return true on page refresh as long as the token exists. I obviously can't require the user to re-authenticate every time they refresh the page.
One approach I've been trying is to somehow compare the current page/route and skip the setRoot for the page if the page being loaded via the route is the same. However I haven't figured out a way to do this yet and I'm not sure it's the correct approach at any rate.

Same Issue here

Yeah agreed and especially when your app has things like FCM notifications and logout (which is pretty common, such a refresh can mess a few things around. Like in my case i have widget page as "main page" which user gets to after login, if now they press "refresh" in their browser (and we should treat browser controls as source of truth ofc) - widget page gets loaded first and then gets loaded second time.
The current work around I have (not ideal) is to prevent loading that page second time completely:
if (this.nav.getActive() instanceof ViewController === false || this.nav.getActive().name !== 'WidgetPage')
     {
        this.nav.setRoot('WidgetPage');
      }