text:
fix(hmr): close modal views during livesync #7669

PR depends on this one to be release first: https://github.com/NativeScript/NativeScript/pull/7669
PR Checklist

[x] The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
[x] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
[x] You have signed the CLA.
[x] All existing tests are passing: https://github.com/NativeScript/nativescript-angular/blob/master/DevelopmentWorkflow.md#running-the-tests
[ ] Tests for the changes are included. (as this is an issue only observed during HMR there is no way to add an unit test for it in this repo)

What is the current behavior?
Any opened modal views are not updated or closed during HMR livesync
What is the new behavior?
Any opened modal views are closed during HMR livesync
Fixes/Implements/Closes #[Issue Number].
#1854

run ci

test tns-core-modules#rc

test tns-core-modules#rc


text:
revert(router): page navigation with RouteReuseStrategy

Due to problems with lazy loaded routes.

uitests

Hi @sis0k0 I'm curious if this fixes this issue on latest at moment when navigating to pages at times:
ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'reusedRoute' of undefined
JS: TypeError: Cannot read property 'reusedRoute' of undefined
JS:     at PageRouterOutlet.activateOnGoBack (file:///data/data/com.ugroupmedia.pnp.client.mobile/files/app/tns_modules/nativescript-angular/router/page-router-outlet.js:270:18)
JS:     at PageRouterOutlet.activateWith (file:///data/data/com.ugroupmedia.pnp.client.mobile/files/app/tns_modules/nativescript-angular/router/page-router-outlet.js:217:18)
JS:     at ActivateRoutes.activateRoutes (file:///data/data/com.ugroupmedia.pnp.client.mobile/files/app/tns_modules/@angular/router/bundles/router.umd.js:4764:40)

If so, curious if any reasonable estimate on a merge to master? Just curious :)

Hi @NathanWalker
This is just a revert of the changes form last week related to the router. They don't work when there is lazy loading involved, so we decided to revert the changes until we have a more stable implementation.
That said, I'm not sure which exactly is the issue you mentioned - is it logged?

uitests

source: gharchive/pull-request

authors: NathanWalker sis0k0 vakrilov

repo: NativeScript/nativescript-angular

license_type: permissive

license_source: github-api


text:
Google Play service fused location

Are there any plans to support Google Play service fused location. According to Google’s documentation,this is much better than the current Location provider used in Android.

Already does: https://github.com/NativeScript/nativescript-geolocation/blob/master/src/geolocation.android.ts#L21

source: gharchive/issue

repo: NativeScript/nativescript-geolocation

license_source: bigquery


text:
Chat/Hud Bug

Since the new update came out I ran into an issue. When I do /back my HUD and Chat move. It also happened to my friend.

This doesn't happen on every /back, just a weird bug maybe a one-time thing?

This means you don't have the latest Nebula Texture Pack for our server, as you can see in that gastrodon in the picture.
You can download it in our #Intro channel in our discord. Here's an invitation to our discord and the texture pack itself:
https://discord.gg/3Upda7kP
https://cdn.discordapp.com/attachments/184691649778155521/1004792718070911056/NebulaMC-1.16.5-Resources-v1.0.7.zip

repo: NebulaMC-GG/Support

license: MIT


text:
Crash occuring with some collisions

For some reason, the game crashes with an "non existing entity" message when some collision appear.
It's not easy to reproduce as it happens only a few time.
I suspect the crash happens during an entity despawn. We're trying to despawn something already gone.

thread 'main' panicked at 'Entity does not exist', /home/oragon/.cargo/git/checkouts/bevy-f7ffde730c324c74/653c103/crates/bevy_ecs/src/world/mod.rs:214:37
stack backtrace:
   0: rust_begin_unwind
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/core/src/panicking.rs:92:14
   2: core::option::expect_failed
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/core/src/option.rs:1292:5
   3: <bevy_ecs::system::commands::Insert<T> as bevy_ecs::system::commands::Command>::write
   4: bevy_ecs::system::commands::CommandQueue::apply
   5: <bevy_ecs::schedule::stage::SystemStage as bevy_ecs::schedule::stage::Stage>::run
   6: <bevy_ecs::schedule::Schedule as bevy_ecs::schedule::stage::Stage>::run
   7: bevy_winit::winit_runner_with::{{closure}}
   8: winit::platform_impl::platform::x11::EventLoop<T>::run_return
   9: winit::platform_impl::platform::x11::EventLoop<T>::run
  10: winit::platform_impl::platform::EventLoop<T>::run
  11: winit::event_loop::EventLoop<T>::run
  12: bevy_winit::run
  13: bevy_winit::winit_runner_with
  14: core::ops::function::Fn::call
  15: bevy_app::app_builder::AppBuilder::run
  16: asteroids::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
fish: Job 1, 'RUST_BACKTRACE=1 cargo run --re…' terminated by signal SIGSEGV (Address boundary error)


text:
Gateway only requests blocks from outgoing peer-to-peer connections.

It seems like a node will only request blocks from peers that it connects to and not from incoming connections. That caused a NDF in some tests in which all the nodes of a TestGroup would actively connect to a new peer which prevented the new peer from syncing.

This will be fixed in #3029

if so, the issue should be closed by referencing it in the commit message.

authors: ChrisSchinnerl lukechampine

repo: NebulousLabs/Sia

license: mit


text:
🛑 Becpl Angular UI is down

In 4acbbd4, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in 3c17290 after 5 minutes.

repo: NehalDamania/becpl-uptime


text:
🛑 Becpl Angular UI is down

In 9a0922f, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in 15cd759 after 27 minutes.


text:
🛑 Becpl Angular UI is down

In 40b81ed, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in 6441b3c after 5 minutes.


text:
🛑 Becpl Angular UI is down

In 7d28b31, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in d3ce987 after 10 minutes.


text:
🛑 Becpl Angular UI is down

In b3f3be3, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in 777f3a7 after 5 minutes.


text:
Dialog does not open for PERMISSION.SEND_SMS

Hello,
I try to request SEND_SMS permission, but dialog does not open.  What could be the problem?
this.androidPermissions.checkPermission(this.androidPermissions.PERMISSION.SEND_SMS).then(       result => {         if (result.hasPermission) {          //send sms         }         else {         this.androidPermissions.requestPermission(this.androidPermissions.PERMISSION.SEND_SMS)         }       },       err => {         this.androidPermissions.requestPermission(this.androidPermissions.PERMISSION.SEND_SMS)       });
Thanks!

Have you declared those permissions in the config.xml?

I forgot about that.. thanks

authors: NeoLSN davidremus


text:
add LinearRegressionOutput op to ngraph emitter

Description
add LinearRegressionOutput op to ngraph emitter
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@louisfeng added feedback to PR.

repo: NervanaSystems/ngraph-mxnet


text:
fix: updating data matrix while adding new instances

Instead of generating new Matrix for new instances in go plugin, Updating the data Matrix itself with extra instances generated from plugin, So that Label_agent plugin can be applied as is.

Tested against the 7mode zapi response data shared by customer.

Before PR changes:
shelf_labels:

shelf_new_status:

shelf_status_reads_attempted:

shelf_fan_labels:

shelf_fan_rpm:

After the PR changes:
shelf_labels:

shelf_new_status:

shelf_status_reads_attempted:

shelf_fan_labels:

shelf_fan_rpm:

repo: NetApp/harvest


text:
Support for Kubernetes 1.17

Hello everyone!
Thank you for providing this useful tool as OpenSource. We use it in production, to integrate our NetApp storage infrastructure into Kubernetes.
We want to upgrade your Development Cluster to Kubernetes 1.17. Basically to enable the new Service Topology feature for testing.
As trident is documented to support Kubernetes 1.16 at max, I want to ask:

Is it really not compatible, or is it not tested to work against 1.17?
It there any plan to support 1.17 in the near future?
How to you integrate new Kubernetes versions in general? Is there a kind of policy for this?

If you need further information, please let me know.
If you want me to help on this Issue, I would appreciate it.

Hi @gprossliner - the installer has a version limiter to prevent installing Trident in a version of Kubernetes that we couldn't test (because it wasn't available at time of Trident release). In other words, we don't support forward compatibility. The Trident 20.01 version (to be released in January) will support 1.17. Our goal is to always provide new versions of Kubernetes in the closest Trident release as possible.

Hi korenaren - thank you for this incredible fast response! If it is included in the v20.01 version, this would be perfect. Thanks

we just tried to install 20.01 on 1.17 and got a version limit still.  So are you planning to change this in the future or should it be working now?

The 20.01-beta did not have support for 1.17. Sorry. But we are planning to support at 20.01 final release.

authors: gprossliner korenaren lucidqdreams

repo: NetApp/trident


text:
azure: Properly return errors when setting up the Azure provider

We weren't properly returning an error when attempting to load the Azure
credentials. This caused cluster to think that the Azure provider was usable,
when it really wasn't.

sigh . . . this is why we need unit tests  . . .

authors: ejj kklin

repo: NetSys/quilt


text:
Reporte CFDI por clave SAT

Carlos pasara el formato

Se genero reporte en base a formato
ManarinaCFDI_201809.xlsx

repo: NetVaIT/SOFOM


text:
FR: Volvo Trucks Configurator Embed to website

Oct 11th: We still have some minor tweaks before we can provide an example for the embedding of VTNA, but attached is a similar file to use for testing - a pure html file with a few lines. This shows what you need to add to the page where you want the configurator to live.
It will look almost identical to how we already are doing it for VTG (global) - https://www.volvotrucks.co.uk/en-gb/tools/truck-builder.html#/en-gb
Nov 13th:
Below the zip file contains the build of the configurator for you to test with. It includes an HTML file which you can use as reference for how to link to the files. The configurator will render into an element with the id #configurator. It relies on its parent having a height of 100% so that it fits the full viewport.
Right now, there are a handful of CSS classes which are defined in the global scope – let me know if this causes styling conflicts on the development and Rapid Images team will try to scope them. If there’s any questions let’s take a short call.
VTNA Configurator.zip

@manuel-vara Please share discovery for Volvo Group's solution for their configurator. We'd like to repurpose the same code in a component block.

@manuel-vara Please go back to the global AEM team and repurpose what's being done for Volvo Trucks in EU with Configurator. Please advise next steps.

We will need to create a custom block enabling js framework apps.
FYI @cogniSyb

Agile Requirement
As a user, I want to configure a truck to my liking to see how it would look before making the purchase.
Description
Create a new custom block called "Truck Configurator" that allows editors to add a route to the HTML in a JS Framework (React/Angular) developed app page.
Acceptance Criteria

Communication throughout the sprint will be needed with the application development agency (Rapid Images) to make design adjustments.

Reopening and sending back to In Progress due to the two Major bugs logged
Bug - Major - iPhone - Volvo Truck Configurator - X close window button is out of view in the Compare models pop-up
https://github.com/Netcentric/vg-volvotrucks-us-rd/issues/311
Bug - Major - Mobile - Volvo Trucks Configurator - User is not able to scroll down in landscape view #312
https://github.com/Netcentric/vg-volvotrucks-us-rd/issues/312

confirmed as done as per the two bugs above

authors: Andrei-Boiangiu BeckyMedlin DanielaPedrochevd ZoeBeykirch manuel-vara

repo: Netcentric/vg-volvotrucks-us-rd


text:
Question: AbstractPollingScheduler Delete From Source

The property ignoreDeletesFromSource in the AbstractPollingScheduler is used to remove properties that are deleting from the source that backs the Property provider. The current implementation has just one property store in memory which has the environment properties and also the properties that are dynamically loaded from a configuration source.
If the ignoreDeletesFromSource is set to false, the properties that are loaded as part of environment variables or other sources that are not from the dynamic configuration source will all be deleted when the configuration is installed. Can this be prevented somehow?

I am also interested in this fix.

V1 is deprecated and no longer maintained. V2 does not have this flag.

authors: rajc28 rgallardo-netflix sandy-adi

repo: Netflix/archaius


text:
How to compensate task failures

This is more of a support request than an issue.
I was wondering what is the proper way of compensating task failures.
Let's assume that I have a provisioning flows which involves two steps in series. However if the second step in the flow fails, I need to revert whatever I did in the first step. How am I supposed to do that?
From what I am understanding I cannot use a DECISION task. The only option at hand seems to use Events and EventHandlers. Can someone guide me in the right direction?

@marcolenzo there are two ways you can do this.

Mark the task as optional and let a decision task ( ${taskRef.status} ) take care of handling compensation.
Keep the task as it is and let the workflow fail.  Add a failure handler workflow (https://github.com/Netflix/conductor/blob/master/common/src/main/java/com/netflix/conductor/common/metadata/workflow/WorkflowDef.java#L48) to be executed when the workflow fails.  Add the logic  for compensation in this failure handler workflow.

@v1r3n thank you for the prompt support!

@v1r3n I am re-opening the issue because I have some additional questions after I had chance to try out your suggestions.
1- It does not seem possible to specify the version of the failureWorkflow. I noticed that the failureWorkflow shares the input of the original workflow, thus the version as well. Is it intentional?
2- Is there a way to access the output of the original workflow?

This is a known limitation that failure workflow does not allow specifying the version.  We are adding that in the coming releases.  (no ETA as yet)
Failure workflow should get the output of main workflow that failed as input.  Again, not in the current release, but we will add in the coming releases.

repo: Netflix/conductor


text:
COMPLETED workflows remain in RUNNING state

Describe the bug
When I try to launch a high number of workflow executions (of the same workflow definition, and concurrently), it happens that a lot of the executions even if they reach and complete the last task in the workflow, they reamain in the RUNNING state.
Details
Conductor version: 3.13.2
Persistence implementation: Dynomite
Queue implementation: Dynoqueues etc
Lock: Redis
Workflow definition:
{
"name": "scoring_wf",
"description": "Scoring wf",
"version": 1,
"tasks": [
{
"name": "decisionManager_exactMatch_task",
"taskReferenceName": "decisionManager_exactMatch_task_ref",
"inputParameters": {
"data_handle": "${workflow.input.data_handle}",
"configuration_path": "${workflow.input.devicewithjb_configuration_path}"
},
"type": "SIMPLE",
"startDelay": 0,
"optional": false,
"asyncComplete": false
},
{
"name": "switch_task",
"taskReferenceName": "switch_task",
"inputParameters": {
"switchCaseValue": "${decisionManager_exactMatch_task_ref.output.result[0]}"
},
"type": "SWITCH",
"decisionCases": {
"no": [
{
"name": "fork_join",
"taskReferenceName": "my_fork_join_ref",
"inputParameters": {},
"type": "FORK_JOIN",
"forkTasks": [
[
{
"name": "decisionManager_script_task",
"taskReferenceName": "decisionManager_script_GPSCheck_task",
"inputParameters": {
"data_handle": "${workflow.input.data_handle}",
"configuration_path": "${workflow.input.gpscheck_configuration_path}"
},
"type": "SIMPLE",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
],
[
{
"name": "decisionManager_script_task",
"taskReferenceName": "decisionManager_script_checkLocationConsistency_task",
"inputParameters": {
"data_handle": "${workflow.input.data_handle}",
"configuration_path": "${workflow.input.checklocationconsistency_configuration_path}"
},
"type": "SIMPLE",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
],
[
{
"name": "decisionManager_script_task",
"taskReferenceName": "decisionManager_script_checkNoA_24h_task",
"inputParameters": {
"data_handle": "${workflow.input.data_handle}",
"configuration_path": "${workflow.input.checknoa24h_configuration_path}"
},
"type": "SIMPLE",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
],
[
{
"name": "decisionManager_script_task",
"taskReferenceName": "decisionManager_script_checkNoA_1h_task",
"inputParameters": {
"data_handle": "${workflow.input.data_handle}",
"configuration_path": "${workflow.input.checknoa1h_configuration_path}"
},
"type": "SIMPLE",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
],
[
{
"name": "decisionManager_script_task",
"taskReferenceName": "decisionManager_script_checkNoA_5m_task",
"inputParameters": {
"data_handle": "${workflow.input.data_handle}",
"configuration_path": "${workflow.input.checknoa5m_configuration_path}"
},
"type": "SIMPLE",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
]
],
"startDelay": 0,
"optional": false,
"asyncComplete": false
},
{
"name": "join",
"taskReferenceName": "join_ref",
"inputParameters": {},
"type": "JOIN",
"startDelay": 0,
"optional": false,
"asyncComplete": false
},
{
"name": "sum_task",
"taskReferenceName": "sum_task_ref",
"inputParameters": {
"data_handle": "${workflow.input.data_handle}",
"configuration_path": "${workflow.input.sumtask_configuration_path}"
},
"type": "SIMPLE",
"startDelay": 0,
"optional": false,
"asyncComplete": false
}
]
},
"startDelay": 0,
"optional": false,
"asyncComplete": false,
"evaluatorType": "value-param",
"expression": "switchCaseValue"
}
],
"inputParameters": [],
"outputParameters": {
"result": "${sum_task_ref.output.result}"
},
"schemaVersion": 2,
"restartable": true,
"workflowStatusListenerEnabled": false,
"ownerEmail": "example@email.com",
"timeoutPolicy": "ALERT_ONLY",
"timeoutSeconds": 0,
"variables": {},
"inputTemplate": {}
}
Tasks definition:
[
{
"name": "decisionManager_script_task",
"description": "Decision manager Script task",
"retryCount": 3,
"timeoutSeconds": 0,
"inputKeys": [],
"outputKeys": [],
"timeoutPolicy": "TIME_OUT_WF",
"retryLogic": "FIXED",
"retryDelaySeconds": 60,
"responseTimeoutSeconds": 600,
"inputTemplate": {},
"rateLimitPerFrequency": 0,
"rateLimitFrequencyInSeconds": 1,
"ownerEmail": "example@email.com",
"backoffScaleFactor": 1
},
{
"name": "decisionManager_exactMatch_task",
"description": "Decision manager task",
"retryCount": 3,
"timeoutSeconds": 0,
"inputKeys": [],
"outputKeys": [],
"timeoutPolicy": "TIME_OUT_WF",
"retryLogic": "FIXED",
"retryDelaySeconds": 60,
"responseTimeoutSeconds": 600,
"inputTemplate": {},
"rateLimitPerFrequency": 0,
"rateLimitFrequencyInSeconds": 1,
"ownerEmail": "example@email.com",
"backoffScaleFactor": 1
},
{
"name": "sum_task",
"description": "Sum scores task",
"retryCount": 10,
"timeoutSeconds": 0,
"inputKeys": [],
"outputKeys": [],
"timeoutPolicy": "TIME_OUT_WF",
"retryLogic": "FIXED",
"retryDelaySeconds": 1,
"responseTimeoutSeconds": 10000,
"inputTemplate": {},
"rateLimitPerFrequency": 0,
"rateLimitFrequencyInSeconds": 1,
"ownerEmail": "example@email.com",
"backoffScaleFactor": 1
}
]
Expected behavior
It should mark the workflow as COMPLETED
Screenshots

Additional context
I'm launching in the order of 100 workflow executions for testing (all with the same input).
In the program starting the workers I create 10 sum_task workers, 30 decisionManager_script_task workers, and 10 decisionManager_exactMatch_task workers

Also facing the same issue .
Conductor version: 3.13.8
Persistence implementation: redis_cluster
Lock: Redis

Facing the same issue
Version: 3.14.0
Persistence: Postgres

authors: bendonio nehaMittal18Git solomonmetta


text:
Truncated logging in docker-compose

This patch reduces the amount of logs that get stored on the filesystem with the docker-compose. Running throughput tests on my local machine consumes gigs per minute without this.

Pull Request Test Coverage Report for Build 2091

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 63.408%

Totals

Change from base Build 2048:
0.04%

Covered Lines:
7096

Relevant Lines:
11191

💛  - Coveralls

authors: coveralls jwulf


text:
Skip auto-generation for type-mapped entities

We have some app-wide enums which we want to use in our schema. This works well enough with custom type-mappings, like this:
typeMapping = [
       'RoastBatchStatus': 'com.fabscale.core.enums.RoastBatchStatus'
]

However, it still generates a RoastBatchStatus enum class, which is a bit annoying in auto-complete as you always have to make sure to pick the correct one. Would it make sense to skip generating classes for manually mapped types? Or otherwise provide an option to opt out of certain classes to be generated?

@mydea - Thanks for reporting. Yes, it should actually skip types. We probably missed handling of enums, will fix this in the next release.

Resolved in PR: https://github.com/Netflix/dgs-codegen/pull/290

I think this bug is resolved.

authors: mydea npwork srinivasankavitha

repo: Netflix/dgs-codegen


text:
Post legacy removal cleanup

This issue tracks items we can clean up after removing the legacy modules end of 2024.

Remove `disableIntrospectionContextContributor` from `DgsAutoconfiguration`. It's also registered from `DgsSpringGraphQLAutoConfiguration`.

Done

repo: Netflix/dgs-framework


text:
Adds support for incident updates

This PR adds support for writing and distributing incident updates. These updates are aimed at leadership and stakeholders rather than status updates (aka tactical updates), which are aimed at incident participants/ responders.
This PR introduces a new env var called INCIDENT_STORAGE_INCIDENT_UPDATE_FILE_ID.

With so much overlap between status reports and these higher level status updates is there an opportunity here to consolidate between them into a "reports" module?  It seems rather limiting that every time we want to create a new kind of report we would create an entirely new service/table/view for that data, when essentially we would only change the fields themselves and maybe a template?

It's more than fields and a template, but I see what you're saying. Let me rethink it.

authors: kevgliss mvilanova

repo: Netflix/dispatch


text:
Use AWS metadata IP in CloudInstanceConfig

I'm trying to get Eureka running in AWS EC2 Container Service (ECS).
Unfortunately, CloudInstanceConfig relies on InetAddress.getLocalHost().getHostAddress() to get the IP address. In case of Docker, this is the IP inside the Docker network (typically something like 172.17.0.2) which isn't very helpful.
Using MetaDataKey.localIpv4 should fix this problem without changing current behavior:
@Override
public String getIpAddress() {
    return ((AmazonInfo) info).get(MetaDataKey.localIpv4);
}

here's the current implementation of getHostName(..):
@Override
public String getHostName(boolean refresh) {
    if (refresh) {
        refreshAmazonInfo();
    }
    return ((AmazonInfo) info).get(MetaDataKey.publicHostname);
}

Alternatively, there could be a new property to enable this behavior.

CloudInstanceConfig depends on Amazon metadata. If access to metadata
fails, and flag 'eureka.validateInstanceId' is set to false, as a fallback
a local host address is read. Possibly this is happening in your case.
You can always override the default CloudInstanceConfig implementation, and
provide your custom version that better handles docker environment.
/Tomasz
On Fri, Dec 4, 2015 at 7:16 AM, Stefan Fussenegger <notifications@github.com

wrote:

I'm trying to get Eureka running in AWS EC2 Container Service (ECS).
Unfortunately, CloudInstanceConfig relies on
InetAddress.getLocalHost().getHostAddress() to get the IP address. In
case of Docker, this is the IP inside the Docker network (typically
something like 172.17.0.2) which isn't very helpful.
Using MetaDataKey.localIpv4 should fix this problem without changing
current behavior:
@Overridepublic String getIpAddress() {
return ((AmazonInfo) info).get(MetaDataKey.localIpv4);
}
here's the current implementation of getHostName(..):
@Overridepublic String getHostName(boolean refresh) {
if (refresh) {
refreshAmazonInfo();
}
return ((AmazonInfo) info).get(MetaDataKey.publicHostname);
}
Alternatively, there could be a new property to enable this behavior.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/eureka/issues/715.

There is actually some work in progress that will address this exact issue
(for a different use case). The changes should make it into the next
release.
On Dec 4, 2015 9:13 AM, "tbak" notifications@github.com wrote:

CloudInstanceConfig depends on Amazon metadata. If access to metadata
fails, and flag 'eureka.validateInstanceId' is set to false, as a fallback
a local host address is read. Possibly this is happening in your case.
You can always override the default CloudInstanceConfig implementation, and
provide your custom version that better handles docker environment.
/Tomasz
On Fri, Dec 4, 2015 at 7:16 AM, Stefan Fussenegger <
notifications@github.com

wrote:

I'm trying to get Eureka running in AWS EC2 Container Service (ECS).
Unfortunately, CloudInstanceConfig relies on
InetAddress.getLocalHost().getHostAddress() to get the IP address. In
case of Docker, this is the IP inside the Docker network (typically
something like 172.17.0.2) which isn't very helpful.
Using MetaDataKey.localIpv4 should fix this problem without changing
current behavior:
@Overridepublic String getIpAddress() {
return ((AmazonInfo) info).get(MetaDataKey.localIpv4);
}
here's the current implementation of getHostName(..):
@Overridepublic String getHostName(boolean refresh) {
if (refresh) {
refreshAmazonInfo();
}
return ((AmazonInfo) info).get(MetaDataKey.publicHostname);
}
Alternatively, there could be a new property to enable this behavior.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/eureka/issues/715.

—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/eureka/issues/715#issuecomment-162024552.

Any sort of ETA on the release? I am interested in running clients in ECS as well.

Sorry for not updating. This is actually already fixed and released in release 1.3.7. Will update the release notes also.

authors: jhmartin qiangdavidliu sfussenegger tbak

repo: Netflix/eureka


text:
#267 issue : update settings.gradle (uncomment the relevant line)

Context
Explain context and other details for this pull request.
Checklist

[ ] ./gradlew build compiles code correctly
[ ] Added new tests where applicable
[ ] ./gradlew test passes all tests
[ ] Extended README or added javadocs where applicable

@sundargates could you review this PR, if any changes are required?

repo: Netflix/mantis


text:
Apache HttpClient that extends AbstractLoadBalancerAwareClient

I am looking into create a LoadBalancerAwareClient that uses Apache Client.
I've found NFHttpClient but it doesn't do what I need.
Is there such an implementation?
Would you like me to add it as a patch?
Not clear from documentation what is the purpose of NFHttpClient in the first place.

@allenxwang  I haven't had the time to contribute but am now interested again. Was this already done by someone?

repo: Netflix/ribbon


text:
DB query for drop down on search page slow

Once a large number of issues are in the DB, the drop downs for account, tech, etc gets painfully slow to populate. I am pretty sure this has to do with the many joins followed by the 'like()' method calls in the query from security_monkey/views/distinct.py. Believe the 'like' is causing it to do a table scan. I have had luck in similar circumstances by breaking these into two queries, first query the smaller tables (account, account_type and technology) with a like() to get a list of matching id's, then do the main query where you are matching the id, not a partial string. If I have time before moving off of this contract I will implement it, but wanted to record it in case I don't.
    query = Item.query
    query = query.join((Account, Account.id == Item.account_id)).join(
        (AccountType, AccountType.id == Account.account_type_id))
    query = query.join((Technology, Technology.id == Item.tech_id))
    query = query.join((ItemRevision, Item.latest_revision_id == ItemRevision.id))
    if 'regions' in args and key_id != 'region':
        regions = args['regions'].split(',')
        query = query.filter(Item.region.in_(regions))
    if 'accounts' in args and key_id != 'account':
        accounts = args['accounts'].split(',')
        query = query.filter(Account.name.in_(accounts))
    if 'accounttypes' in args and key_id != 'accounttype':
        accounttypes = args['accounttypes'].split(',')
        query = query.filter(AccountType.name.in_(accounttypes))
    if 'technologies' in args and key_id != 'tech':
        technologies = args['technologies'].split(',')
        query = query.filter(Technology.name.in_(technologies))
    if 'names' in args and key_id != 'name':
        names = args['names'].split(',')
        query = query.filter(Item.name.in_(names))
    if 'arns' in args and key_id != 'arn':
        names = args['arns'].split(',')
        query = query.filter(Item.arn.in_(names))
    if 'active' in args:
        active = args['active'].lower() == "true"
        query = query.filter(ItemRevision.active == active)

    if key_id == 'tech':
        if select2:
            query = query.distinct(Technology.name).filter(func.lower(Technology.name).like('%' + q + '%'))
        else:
            query = query.distinct(Technology.name)
    elif key_id == 'accounttype':
        if select2:
            query = query.distinct(AccountType.name).filter(func.lower(AccountType.name).like('%' + q + '%'))
        else:
            query = query.distinct(AccountType.name)
    elif key_id == 'account':
        if select2:
            query = query.filter(Account.third_party == False)
            query = query.distinct(Account.name).filter(func.lower(Account.name).like('%' + q + '%'))
        else:
            query = query.distinct(Account.name)

Neat.
It always bothers me when the region dropdown takes a noticeable amount of time...

Hey @aebie - I found a couple ways to speed these dropdowns up.  See #613.

I moved some of the loads so they only occur if necessary.
I modified Item.issue_count to be deferred.  (It's a column_property, which triggers a subquery)
I added a unique constraint and index to Technology.name.

10x-30x speed increase depending on the field.

Fixed in #613.

authors: aebie monkeysecurity


text:
Add more logging for tasks and referer

Description of the Change
Trying to get parity between IMDS logging that we had in baseami with titus.  Just adding a couple of fields to make correlation easier.

Hold off on merging this.  i'm gonna use this to build some other metadata service changes

lgtm.

authors: nabilschear sargun

repo: Netflix/titus-executor


text:
Implement L1 Verification

[ ] #697
[ ] Determine whether a full Ethereum node can be used for L1 state retrieval instead of an archive node.
[ ] Incorporate ethclient

We may need to use something like eth_getStorageAt while syncing (we can binary search over a subset of the Ethereum chain to find state updates). Once synced with L1, we can use eth_subscribe.

I'll a second issue for "L1 verification while syncing". That way #699 can be merged as an MVP while we take more time to think about the problem mentioned above.

authors: jelilat joshklop

repo: NethermindEth/juno


text:
Error fetching finalized block

Describe the bug
Error fetching finalized block from remote using checkpoint.gnosischain.com.
execution-client  | 2022-12-27 16:44:10.9936|Waiting for peers... 43s
execution-client  | 2022-12-27 16:44:11.9929|Waiting for peers... 44s
consensus-client  | Dec 27 16:44:12.244 CRIT Failed to start beacon node             reason: Error fetching finalized block from remote: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("checkpoint.gnosischain.com")), port: None, path: "/eth/v2/beacon/blocks/finalized", query: None, fragment: None }, source: TimedOut })
consensus-client  | Dec 27 16:44:12.244 INFO Internal shutdown received              reason: Failed to start beacon node
consensus-client  | Dec 27 16:44:12.244 INFO Shutting down..                         reason: Failure("Failed to start beacon node")
consensus-client  | Failed to start beacon node
consensus-client exited with code 1
execution-client  | 2022-12-27 16:44:12.9938|Waiting for peers... 45s
consensus-client  | Dec 27 16:42:12.195 INFO Logging to file                         path: "/var/lib/lighthouse/beacon/logs/beacon.log"
consensus-client  | Dec 27 16:42:12.195 INFO Lighthouse started                      version: Lighthouse/v3.3.0-bf533c8
consensus-client  | Dec 27 16:42:12.195 INFO Configured for network                  name: gnosis
consensus-client  | Dec 27 16:42:12.195 INFO Data directory initialised              datadir: /var/lib/lighthouse
consensus-client  | Dec 27 16:42:12.196 WARN Ignoring --eth1-endpoints flag          info: the value for --execution-endpoint will be used instead. --eth1-endpoints has been deprecated for post-merge configurations
consensus-client  | Dec 27 16:42:12.196 INFO Deposit contract                        address: 0x0b98057ea310f4d31f2a452b414647007d1645d9, deploy_block: 19469077
consensus-client  | Dec 27 16:42:12.225 INFO Starting checkpoint sync                remote_url: https://checkpoint.gnosischain.com/, service: beacon
consensus-client  | Dec 27 16:43:12.236 WARN Remote BN does not support EIP-4881 fast deposit sync, error: Error fetching deposit snapshot from remote: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("checkpoint.gnosischain.com")), port: None, path: "/eth/v1/beacon/deposit_snapshot", query: None, fragment: None }, source: TimedOut }), service: beacon
consensus-client  | Dec 27 16:44:12.244 CRIT Failed to start beacon node             reason: Error fetching finalized block from remote: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("checkpoint.gnosischain.com")), port: None, path: "/eth/v2/beacon/blocks/finalized", query: None, fragment: None }, source: TimedOut })
consensus-client  | Dec 27 16:44:12.244 INFO Internal shutdown received              reason: Failed to start beacon node
consensus-client  | Dec 27 16:44:12.244 INFO Shutting down..                         reason: Failure("Failed to start beacon node")
consensus-client  | Failed to start beacon node
consensus-client  | Dec 27 16:44:13.036 INFO Logging to file                         path: "/var/lib/lighthouse/beacon/logs/beacon.log"
consensus-client  | Dec 27 16:44:13.037 INFO Lighthouse started                      version: Lighthouse/v3.3.0-bf533c8
consensus-client  | Dec 27 16:44:13.037 INFO Configured for network                  name: gnosis
consensus-client  | Dec 27 16:44:13.037 INFO Data directory initialised              datadir: /var/lib/lighthouse
consensus-client  | Dec 27 16:44:13.037 WARN Ignoring --eth1-endpoints flag          info: the value for --execution-endpoint will be used instead. --eth1-endpoints has been deprecated for post-merge configurations
consensus-client  | Dec 27 16:44:13.038 INFO Deposit contract                        address: 0x0b98057ea310f4d31f2a452b414647007d1645d9, deploy_block: 19469077
consensus-client  | Dec 27 16:44:13.085 INFO Starting checkpoint sync                remote_url: https://checkpoint.gnosischain.com/, service: beacon
execution-client  | 2022-12-27 16:44:13.9938|Peers | with known best block: 0 | all: 0 |

To Reproduce
Steps to reproduce the behavior:

setup sedge with the following .env

# --- Global configuration ---
EL_NETWORK=xdai
CL_NETWORK=gnosis
# --- Execution Layer - Execution Node - configuration ---
EC_IMAGE_VERSION=nethermind/nethermind:1.14.7
NETHERMIND_LOG_LEVEL=INFO
EC_ENABLED_MODULES=[Web3,Eth,Subscribe,Net,]
EC_NODENAME=Nethermind
NETHERMIND_METRICS_PUSH_GATEWAY_URL=http://localhost:9090/metrics
NETHERMIND_PRUNING_CACHEMB=2048
EC_DATA_DIR="/media/Extreme SSD/gnosis-data/execution-data"
EC_SNAP_SYNC_ENABLED=false
EC_JWT_SECRET_PATH=/home/user/gnosis-validator/docker-compose-scripts/jwtsecret
# --- Consensus Layer - Beacon Node - configuration ---
CC_PEER_COUNT=50
CC_LOG_LEVEL=info
EC_API_URL=http://execution:8545
EC_AUTH_URL=http://execution:8551
CC_INSTANCE_NAME=Lighthouse
CC_IMAGE_VERSION=sigp/lighthouse:v3.3.0
CC_DATA_DIR="/media/Extreme SSD/gnosis-data/consensus-data"
CC_JWT_SECRET_PATH=/home/user/gnosis-validator/docker-compose-scripts/jwtsecret
CL_FEE_RECIPIENT=0x7D678b9218aC289e0C9F18c82F546c988BfE3022
CHECKPOINT_SYNC_URL=https://checkpoint.gnosischain.com
CL_BOOTNODES="enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk,enr:-Ly4QFoZTWR8ulxGVsWydTNGdwEESueIdj-wB6UmmjUcm-AOPxnQi7wprzwcdo7-1jBW_JxELlUKJdJES8TDsbl1EdNlh2F0dG5ldHOI__78_v2bsV-EZXRoMpA2-lATkAAAcf__________gmlkgnY0gmlwhBLYJjGJc2VjcDI1NmsxoQI0gujXac9rMAb48NtMqtSTyHIeNYlpjkbYpWJw46PmYYhzeW5jbmV0cw-DdGNwgiMog3VkcIIjKA,enr:-KG4QE5OIg5ThTjkzrlVF32WT_-XT14WeJtIz2zoTqLLjQhYAmJlnk4ItSoH41_2x0RX0wTFIe5GgjRzU2u7Q1fN4vADhGV0aDKQqP7o7pAAAHAyAAAAAAAAAIJpZIJ2NIJpcISlFsStiXNlY3AyNTZrMaEC-Rrd_bBZwhKpXzFCrStKp1q_HmGOewxY3KwM8ofAj_ODdGNwgiMog3VkcIIjKA,enr:-L64QC9Hhov4DhQ7mRukTOz4_jHm4DHlGL726NWH4ojH1wFgEwSin_6H95Gs6nW2fktTWbPachHJ6rUFu0iJNgA0SB2CARqHYXR0bmV0c4j__________4RldGgykDb6UBOQAABx__________-CaWSCdjSCaXCEA-2vzolzZWNwMjU2azGhA17lsUg60R776rauYMdrAz383UUgESoaHEzMkvm4K6k6iHN5bmNuZXRzD4N0Y3CCIyiDdWRwgiMo"
# --- Consensus Layer - Validator Node - configuration ---
CC_API_URL=http://consensus:4000
GRAFFITI=nethermind-lighthouse
VL_LOG_LEVEL=info
VL_INSTANCE_NAME=LighthouseValidator
VL_IMAGE_VERSION=sigp/lighthouse:v3.3.0
KEYSTORE_DIR=./keystore
VL_DATA_DIR="/media/Extereme SSD/gnosis-data/validator-data"

start nodes sudo docker compose -f docker-compose.yml up -d execution consensus
see errors

Expected behavior
consensus node should start syncing
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: ubuntu 22

@critesjosh thanks for opening an issue. Did you happen to try the setup again in another moment? My guess here is that checkpoint.gnosischain.com was receiving a lot of traffic or was down for a while. This node is an official checkpoint sync node from Gnosis, we are not maintaining it. If you still face issues with this endpoint you can stop using a checkpoint sync endpoint:

Clean consensus data dir (rm -r consensus-data)
Remove the CHECKPOINT_SYNC_URL=https://checkpoint.gnosischain.com line from the .env
Remove the - --checkpoint-sync-url=${CHECKPOINT_SYNC_URL} flag from the consensus service in the docker-compose.yml file Sedge generated for you.
Run  sudo docker compose -f docker-compose.yml up -d execution consensus again

thanks ill try that and get back to you.
some additional context, i followed the server config steps here https://docs.gnosischain.com/node/guide/configure-server

hmm now i just see bunch of errors from the consensus client about not being able to communicate with the EC
onsensus-client  | Dec 27 17:20:32.501 WARN Low peer count                          peer_count: 0, service: slot_notifier
consensus-client  | Dec 27 17:20:32.501 INFO Searching for peers                     current_slot: 6633658, head_slot: 0, finalized_epoch: 0, finalized_root: 0x2356…6a75, peers: 0, service: slot_notifier
consensus-client  | Dec 27 17:20:32.501 WARN Syncing deposit contract block cache    est_blocks_remaining: initializing deposits, service: slot_notifier
consensus-client  | Dec 27 17:20:33.502 ERRO Execution engine call failed            error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
consensus-client  | Dec 27 17:20:33.502 ERRO Unable to get transition config         error: Api { error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }) }, service: exec
consensus-client  | Dec 27 17:20:33.502 ERRO Not ready for merge                     hint: try updating Lighthouse and/or the execution layer, info: Could not confirm the transition configuration with the execution endpoint: "EngineError(Api { error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: \"http\", cannot_be_a_base: false, username: \"\", password: None, host: Some(Domain(\"execution\")), port: Some(8551), path: \"/\", query: None, fragment: None }, source: TimedOut }) })", service: slot_notifier
consensus-client  | Dec 27 17:20:34.504 ERRO Error during execution engine upcheck   error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
consensus-client  | Dec 27 17:20:34.817 ERRO Error during execution engine upcheck   error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
consensus-client  | Dec 27 17:20:37.501 WARN Low peer count                          peer_count: 0, service: slot_notifier
consensus-client  | Dec 27 17:20:37.501 INFO Searching for peers                     current_slot: 6633659, head_slot: 0, finalized_epoch: 0, finalized_root: 0x2356…6a75, peers: 0, service: slot_notifier
consensus-client  | Dec 27 17:20:37.501 WARN Syncing deposit contract block cache    est_blocks_remaining: initializing deposits, service: slot_notifier
consensus-client  | Dec 27 17:20:38.502 ERRO Execution engine call failed            error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
consensus-client  | Dec 27 17:20:38.502 ERRO Unable to get transition config         error: Api { error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }) }, service: exec
consensus-client  | Dec 27 17:20:38.502 ERRO Not ready for merge                     hint: try updating Lighthouse and/or the execution layer, info: Could not confirm the transition configuration with the execution endpoint: "EngineError(Api { error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: \"http\", cannot_be_a_base: false, username: \"\", password: None, host: Some(Domain(\"execution\")), port: Some(8551), path: \"/\", query: None, fragment: None }, source: TimedOut }) })", service: slot_notifier
execution-client  | 2022-12-27 17:20:39.0395|Waiting for peers... 33s
consensus-client  | Dec 27 17:20:39.504 ERRO Error during execution engine upcheck   error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
consensus-client  | Dec 27 17:20:39.818 ERRO Error during execution engine upcheck   error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
execution-client  | 2022-12-27 17:20:40.0371|Waiting for peers... 34s
execution-client  | 2022-12-27 17:20:41.0370|Waiting for peers... 35s
execution-client  | 2022-12-27 17:20:41.4691|No incoming messages from Consensus Client. Please make sure that it's working properly
execution-client  | 2022-12-27 17:20:42.0368|Waiting for peers... 36s
consensus-client  | Dec 27 17:20:42.501 WARN Low peer count                          peer_count: 0, service: slot_notifier
consensus-client  | Dec 27 17:20:42.501 INFO Searching for peers                     current_slot: 6633660, head_slot: 0, finalized_epoch: 0, finalized_root: 0x2356…6a75, peers: 0, service: slot_notifier
consensus-client  | Dec 27 17:20:42.501 WARN Syncing deposit contract block cache    est_blocks_remaining: initializing deposits, service: slot_notifier
execution-client  | 2022-12-27 17:20:43.0373|Waiting for peers... 37s
consensus-client  | Dec 27 17:20:43.502 ERRO Execution engine call failed            error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
consensus-client  | Dec 27 17:20:43.502 ERRO Unable to get transition config         error: Api { error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }) }, service: exec
consensus-client  | Dec 27 17:20:43.502 ERRO Not ready for merge                     hint: try updating Lighthouse and/or the execution layer, info: Could not confirm the transition configuration with the execution endpoint: "EngineError(Api { error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: \"http\", cannot_be_a_base: false, username: \"\", password: None, host: Some(Domain(\"execution\")), port: Some(8551), path: \"/\", query: None, fragment: None }, source: TimedOut }) })", service: slot_notifier
execution-client  | 2022-12-27 17:20:44.0367|Waiting for peers... 38s
consensus-client  | Dec 27 17:20:44.503 ERRO Error during execution engine upcheck   error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec
consensus-client  | Dec 27 17:20:44.819 ERRO Error during execution engine upcheck   error: Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("execution")), port: Some(8551), path: "/", query: None, fragment: None }, source: TimedOut }), service: exec

I see the authentication scheme is not working. Can you please put here the docker-compose.yml you are using? Did you created the jwtsecret as per instructed here https://docs.gnosischain.com/node/guide/configure-server?

here is the docker compose file
version: "3.9"
services:
  execution:
    stop_grace_period: 30s
    container_name: execution-client
    restart: unless-stopped
    image: ${EC_IMAGE_VERSION}
    networks:
    - sedge
    volumes:
    - ${EC_DATA_DIR}:/nethermind/data
    - ${EC_JWT_SECRET_PATH}:/tmp/jwt/jwtsecret
    ports:
    - 30303:30303/tcp
    - 30303:30303/udp
    - 8008:8008
    expose:
    - 8545
    - 8551
    command:
    - --config=${EL_NETWORK}
    - --datadir=/nethermind/data
    - --log=${NETHERMIND_LOG_LEVEL}
    - --Sync.SnapSync=${EC_SNAP_SYNC_ENABLED}
    - --JsonRpc.Enabled=true
    - --JsonRpc.Host=0.0.0.0
    - --JsonRpc.Port=8545
    - --JsonRpc.EnabledModules=${EC_ENABLED_MODULES}
    - --JsonRpc.JwtSecretFile=/tmp/jwt/jwtsecret
    - --JsonRpc.EngineHost=0.0.0.0
    - --JsonRpc.EnginePort=8551
    - --Network.DiscoveryPort=30303
    - --HealthChecks.Enabled=true
    - --Pruning.CacheMb=${NETHERMIND_PRUNING_CACHEMB}
    - --Metrics.Enabled=true
    - --Metrics.ExposePort=8008
    logging:
      driver: json-file
      options:
        max-size: 10m
        max-file: "10"
  consensus:
    stop_grace_period: 30s
    container_name: consensus-client
    restart: unless-stopped
    image: ${CC_IMAGE_VERSION}
    networks:
    - sedge
    volumes:
    - ${CC_DATA_DIR}:/var/lib/lighthouse
    - ${CC_JWT_SECRET_PATH}:/tmp/jwt/jwtsecret
    ports:
    - 9000:9000/tcp
    - 9000:9000/udp
    - 5054:5054/tcp
    expose:
    - 4000
    command:
    - lighthouse
    - bn
    - --disable-upnp
    - --datadir=/var/lib/lighthouse
    - --port=9000
    - --http
    - --http-address=0.0.0.0
    - --http-port=4000
    - --network=${CL_NETWORK}
    - --target-peers=${CC_PEER_COUNT}
    - --boot-nodes=${CL_BOOTNODES}
    - --execution-endpoints=${EC_AUTH_URL}
    - --execution-jwt=/tmp/jwt/jwtsecret
    - --eth1-endpoints=${EC_API_URL}
    - --debug-level=${CC_LOG_LEVEL}
    - --suggested-fee-recipient=${CL_FEE_RECIPIENT}
    - --validator-monitor-auto
    - --subscribe-all-subnets
    - --import-all-attestations
    - --metrics
    - --metrics-port=5054
    - --metrics-address=0.0.0.0
    logging:
      driver: json-file
      options:
        max-size: 10m
        max-file: "10"
  validator-import:
    container_name: validator-import-client
    build:
      context: github.com/NethermindEth/lighthouse-init-validator
      args:
        LH_VERSION: ${VL_IMAGE_VERSION}
        NETWORK: ${CL_NETWORK}
    networks:
    - sedge
    volumes:
    - ${KEYSTORE_DIR}:/keystore
    - ${VL_DATA_DIR}:/data
    logging:
      driver: json-file
      options:
        max-size: 10m
        max-file: "10"
  validator:
    container_name: validator-client
    image: ${VL_IMAGE_VERSION}
    depends_on:
      validator-import:
        condition: service_completed_successfully
    networks:
    - sedge
    ports:
    - 5056:5056
    volumes:
    - ${VL_DATA_DIR}:/data
    command:
    - lighthouse
    - vc
    - --network=${CL_NETWORK}
    - --beacon-nodes=${CC_API_URL}
    - --graffiti=${GRAFFITI}
    - --debug-level=${VL_LOG_LEVEL}
    - --validators-dir=/data/validators
    - --suggested-fee-recipient=${CL_FEE_RECIPIENT}
    - --metrics
    - --metrics-port=5056
    - --metrics-address=0.0.0.0
    logging:
      driver: json-file
      options:
        max-size: 10m
        max-file: "10"
networks:
  sedge:
    name: sedge_network

i did not create the jwt like in the instructions on gnosischain.com, i see the hex secret in the file called jwtsecret in the docker-compose-scripts dir

The configuration is ok. My guess is that error is related to your network interface. There are a couple of checks we can do. The easiest one is to use the --map-all flag with sedge cli to expose all the ports to the localhost. Then you can execute the following command to check if the execution client is accesible:
curl -X POST http://localhost:8545/ --data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' -H "Content-Type: application/json"

If the above command works then the execution client is accesible for the consensus client through your network interface.

I see a bunch of these errors when i run sedge cli -c lighthouse -e nethermind -n gnosis --map-all
2022-12-27 19:51:53 -- [ERRO] [GetRequest] request failed. Error: Get "http://192.168.80.2:4000/eth/v1/node/syncing": dial tcp 192.168.80.2:4000: connect: connection refused
2022-12-27 19:51:53 -- [INFO] [GetRequest] Retrying request
2022-12-27 19:51:55 -- [ERRO] [GetRequest] request failed. Error: Get "http://192.168.80.2:4000/eth/v1/node/syncing": dial tcp 192.168.80.2:4000: connect: connection refused
2022-12-27 19:51:55 -- [INFO] [GetRequest] Retrying request
2022-12-27 19:51:57 -- [ERRO] [GetRequest] request failed. Error: Get "http://192.168.80.2:4000/eth/v1/node/syncing": dial tcp 192.168.80.2:4000: connect: connection refused
2022-12-27 19:51:57 -- [INFO] [GetRequest] Retrying request

if i stop the log output and restart it with sedge logs. i see nethermind logs, but it doesn't connect to any peers.
the curl command to nethermind works with result
{"jsonrpc":"2.0","result":{"startingBlock":"0x0","currentBlock":"0x0","highestBlock":"0x0"},"id":1}j

Did you created the jwtsecret as per instructed here https://docs.gnosischain.com/node/guide/configure-server?

Should I be creating the jwtsecret as outlined in the gnosischain.com docs? or should sedge handle this automatically?

repo: NethermindEth/sedge


text:
price_in_fri incorrectly json encoded as price_in_strk

When marshalling a PendingBlockHeader into json, the ResourcePrice's price_in_fri field is incorrectly named as price_in_strk.
Expected:
When marshalling to json, the field should be named price_in_fri.

Yup, thanks for catching this!

authors: cll-gg rianhughes


text:
[Bug] Cannot install elephant with new Neo 0.7.2

Neo 0.7.2 was just released today (NeuralEnsemble/python-neo#687). However, until the typo that was fixed in #218 makes it onto PyPI in a new version of elephant, pip cannot resolve dependencies that include
neo>=0.7.2
elephant>=0.6.2

To fix this, elephant 0.6.3 (or 0.6.2.1) would need to be released including the fix from #218.

As an aside, I find the current requirement neo<0.8.0 for elephant to be very annoying.
I understand it's motivated by the intention to provide paired releases between elephant and Neo. However, if I have the development version of Neo installed, pip sees my Neo version as 0.8.0.dev, which violates the requirement neo<0.8.0, and automatically replaces it with an old version. Very obnoxious. When I manually reinstall Neo dev, I get this warning, though I can ignore it:
elephant 0.6.2 has requirement neo<0.8.0,>=0.7.1, but you'll have neo 0.8.0.dev0 which is incompatible.

Is anyone with the appropriate privileges willing to create a maintenance branch called "0.6.x" starting at the "v0.6.2" tag?
Once that is done, I can create a pull request against that branch that backports a67b33f into it. After it is merge, I will politely ask again if anyone is willing to create a release from the maintenance branch containing the fix (called 0.6.2.1 or 0.6.3, dealer's choice).
If a new version of elephant containing this tiny fix is released, I will finally be able to announce a new package that depends on it. Until then, my package cannot be installed from pip properly thanks to the conflict between elephant 0.6.2 and neo 0.7.2. 😢

You introduced two issues here.
The first one, dependency conflict between elephant v0.6.2 and neo v0.7.2, will be fixed by creating a new elephant release v0.6.3 once https://github.com/NeuralEnsemble/elephant/pull/239 is merged.
Regarding the second issue, I don't know an easy fix for this. I tried to find out how other packages deal with dev version, but I have not found any mentions. Did you find the workaround neo<0.8.0a just by trying or you have a link that someone else does this? For me, neo<0.8.0a seems like a hack and is not obvious at all, and thus I don't want to include it.

You introduced two issues here.

Mea culpa.

The first one, dependency conflict between elephant v0.6.2 and neo v0.7.2, will be fixed by creating a new elephant release v0.6.3 once #239 is merged.

Thank you!

Regarding the second issue, I don't know an easy fix for this. I tried to find out how other packages deal with dev version, but I have not found any mentions. Did you find the workaround neo<0.8.0a just by trying or you have a link that someone else does this? For me, neo<0.8.0a seems like a hack and is not obvious at all, and thus I don't want to include it.

I can't remember exactly how I discovered it, I think I was working with some automated tool, perhaps pyoxidizer, which created a file for me containing a requirements spec like <0.8.0a, and it piqued my curiosity. I tried it locally for elephant and found it made a difference. I started drafting a separate issue containing a proposal to change how elephant specified requirements, but when I searched for references I found contradictory information!
For example, PEP 440 states that the version ordering should be 0.8.0.dev < 0.8.0a < 0.8.0. If that's how pip actually resolved version ordering, then we wouldn't have this problem in the first place!
So I decided to drop it and deleted my draft. 🤣 Sorry for the time you have already spent looking into that issue with me. I agree that it seems like a hack. Perhaps tomorrow the pip team will realize they aren't following PEP 440 and will change it, and adopting the hack for elephant will have been a mistake. I'll find a way to continue living with neo<0.8.0 in my dev environment. 😊
However, the first issue of conflicting versions is harder to work around, since it affects how my users install my package, rather than just how I set up my local dev environment. I appreciate your willingness to create a new release soon that includes the fix in #218. Thanks again!

The release v0.6.3 is published.
I checked the pep 440 about version resolving you linked and I also find that pip does not follow it. Maybe, one should fire an issue for pip or at least ask for clarification. I don't feel I'll do it soon. For now, I leave it as it is, keeping it running in the back of my mind.

Thank you for the release!

repo: NeuralEnsemble/elephant


text:
IntanRawIO: Fix memmap order for Intan one-file-per-stream

Fixes #1556
Data before fix:

Data after fix:

Basically, since Intan was designed to be easily read with Matlab (their example work is to use fread which is column-major reading) we should make our memmap with order='F'.
@h-mayorquin want to look over this quickly and @alejoe91 I think this can be a quick review as long as everyone is agreed. See the linked issue for more information.
Can you test this @Tevin-yue?
NOTE: this is simulated data so it should look like a repeating motif of simulated "spikes".

I don't have your experimental expertise so this is for my learning. How do you know based on your plots (before and after fix) that your fix is right?

I don't have your experimental expertise so this is for my learning. How do you know based on your plots (before and after fix) that your fix is right?
The values are really weird on the axis (almost like we are summing spikes ie the samples and channels values are mixed up). And for intan simulated data it should like a regularly spiking (regular in the non FS/RS way) neuron so it should have a nice downward followed by upward deflections on a background of some level of noise. The "bad" graph looks to sinusoidal (again from in appropriate summing of the voltages).
so this meant either we scaled wrong. I double checked and we weren't. Or we loaded the data in wrong (easy to mix up samples and channels when making the memmap). Since we did the documentation from intan (I think this part was me so mea culpa), I did the F-major style but didn't specify. Sam's tip was just flip the sample and channel to allow us to read the C style.
So to summarize I would accept amplifier/wideband data to be noisy with spikes in it. Not weird sinusoidal things.
Or do you have an additional question related to this?

Maybe this will help you @h-mayorquin if I plot all channels instead of one channel.

You see we have sinusoidal noise (because this is simulated data. In real data it wouldn't be so clean ahah) with a bunch of spikes!

Honestly dude you should propose that to Numpy! They just link to the wikipedia to explain this, but at least with your example you show what is actually happening with Numpy code. That's great!
@alejoe91 or @samuelgarcia. this is good to go now :) Tested and everyone is happy!

repo: NeuralEnsemble/python-neo


text:
Make KlustaKwikIO py3 compatible. Fix for #467

To fix #467.

Hello @samuelgarcia! Thanks for submitting the PR.

In the file neo/io/klustakwikio.py, following are the PEP8 issues :

Line 55:100: E501 line too long (100 > 99 characters)
Line 56:100: E501 line too long (100 > 99 characters)
Line 58:100: E501 line too long (101 > 99 characters)
Line 112:9: E265 block comment should start with '# '

In the file neo/test/iotest/test_klustakwikio.py, following are the PEP8 issues :

Line 61:9: E265 block comment should start with '# '
Line 62:9: E265 block comment should start with '# '
Line 63:9: E265 block comment should start with '# '
Line 65:9: E265 block comment should start with '# '
Line 66:9: E265 block comment should start with '# '
Line 67:9: E265 block comment should start with '# '

Coverage decreased (-0.02%) to 48.967% when pulling cf9ac07601f00d2f63720c7e414c2edc26a8b146 on samuelgarcia:py3_fix_klustakiwkio into 6e2cdfcc682973388cd22335aa2dc46a679aad72 on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 48.967% when pulling cf9ac07601f00d2f63720c7e414c2edc26a8b146 on samuelgarcia:py3_fix_klustakiwkio into 6e2cdfcc682973388cd22335aa2dc46a679aad72 on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 48.967% when pulling cf9ac07601f00d2f63720c7e414c2edc26a8b146 on samuelgarcia:py3_fix_klustakiwkio into 6e2cdfcc682973388cd22335aa2dc46a679aad72 on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 48.967% when pulling cf9ac07601f00d2f63720c7e414c2edc26a8b146 on samuelgarcia:py3_fix_klustakiwkio into 6e2cdfcc682973388cd22335aa2dc46a679aad72 on NeuralEnsemble:master.

Nobody for merging this beautiful and useless piece of work ?

:)

authors: coveralls pep8speaks samuelgarcia


text:
"Publications and preregistration" provides different suggestions in the two tutorials

An example from the ICA part:
MNE:
Example text "The data were down sampled to 200Hz prior to Independent Component Analysis (ICA) and bandpass filtered at 1 – 40 Hz. Next the fastICA algorithm (Hyvärinen and Oja, 2000) was applied to the segmented data as implemented in MNE Python. Clear components containing cardiac artefacts and eyeblinks (identified in time course and topographies of the ICA components) were removed in each subject (3 – 5 over subjects) in the raw unfiltered data. "
FieldTrip:
Pre-registration: ICA will be used to 'project out' artefacts. Prior to the ICA, downsampling will be performed to 200 Hz. The runica algorithm will be applied. Ocular, cardiac and muscle artefacts will be identified in the components based on time-course and topography. These components will be projected out in the non-downsampled data.
Publications: beyond the details above report the mean number of ICA components (incl. standard deviation) rejected in each subject.
EXAMPLE: "The data were downsampled to 200Hz prior to Independet Component Analysis (ICA). Next the 'runica' ICA algorithm (see Bell & Sejnowski, 1995, Amari, Cichocki & Yang, 1996) was applied on the segmented data as implemented in Fieldtrip. Clear components containing cardiac artifacts and eyeblinks were removed in each subject (XX+/-YY over subjects)."

@TamasMinarik  Please update FieldTrip FLUX tutorial from MNE FLUX scripts

repo: Neuronal-Oscillations/FLUX


text:
Solutions downloader

Could you allow also downloading of posted solutions, please?

It seems this could be done by POSTing to https://leetcode.com/graphql/ userSolutionTopics operation. The query is:
query userSolutionTopics($username: String!, $orderBy: TopicSortingOption, $skip: Int, $first: Int) {
  userSolutionTopics(
    username: $username
    orderBy: $orderBy
    skip: $skip
    first: $first
  ) {
    pageInfo {
      hasNextPage
    }
    edges {
      node {
        id
        title
        url
        viewCount
        questionTitle
        post {
          creationDate
          voteCount
        }
      }
    }
  }
}

The variables are like:
{
  "username": "...",
  "orderBy": "newest_to_oldest",
  "skip": 0,
  "first": 15
}

Thank you for sharing your suggestion! I had a quick look and found that exporting community solutions would be possible by using the userSolutionTopics graphql api you mentioned as well as the following to actually retrieve the solution:
query communitySolution($topicId: Int!) {
  topic(id: $topicId) {
    id
    viewCount
    topLevelCommentCount
    subscribed
    title
    pinned
    solutionTags {
      name
      slug
    }
    hideFromTrending
    commentCount
    isFavorite
    post {
      id
      voteCount
      voteStatus
      content
      updationDate
      creationDate
      status
      isHidden
      author {
        isDiscussAdmin
        isDiscussStaff
        username
        nameColor
        activeBadge {
          displayName
          icon
        }
        profile {
          userAvatar
          reputation
        }
        isActive
      }
      authorIsModerator
      isOwnPost
    }
  }
}

Right now, I don't have the bandwith to implement this, so I'll keep it unresolved for now. Contributions are welcome!

authors: NeverMendel garncarz

repo: NeverMendel/leetcode-export


text:
Ignore large files for field view to avoid memory issues on phones

for now we will put uber large files in the photos directory as this is ignored on the phone by default.  We will likely want to change the name of that directory on future versions and tuck a photos directory inside

As long as the large file in question is not selected in the layer view it won't cause any grief on the phone. Not sure what you're asking in regards to themes. As long as the available themes also do not include any large files when viewing on phone we should be ok.

dealt with through ignore_mobile directory creation and mergin-config.json


text:
add KeyboardAwareScrollViews

Fixes #282
Creator

[ ] Build relevant tests if any apply
[ ] Ensure there are no new warnings
[ ] Upload an animated GIF showcasing the solution (if it applies)
[ ] Set a relevant reviewer

Reviewer

[ ] Run test and make sure all tests pass
[ ] Review function and form on iOS
[ ] Review function and form on Android
[ ] Review function and form on Web
[ ] Review new test logic

@burkeshartsis I made this better. It's not perfect, but I think it should be putting most inputs close to in-view now. It's an improvement over current master, that's for sure :-D
Might need to go back to drawing board long-term in figuring out how better to support keyboard in android

repo: NewSpring/Apollos


text:
Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter aio for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.aio
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
[X] :heavy_exclamation_mark: [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.5.1 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 2.5.2 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[X] :heavy_exclamation_mark: [E039] "keywords" within package.json must contain some keywords besides "ioBroker, template, Smart Home, home automation" related to adapter
[ ] :heavy_exclamation_mark: [E049] "keywords" within package.json must contain some keywords besides "ioBroker, template, Smart Home, home automation" related to adapter
[ ] :heavy_exclamation_mark: [E157] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[X] :heavy_exclamation_mark: [E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E518] "@alcalzone/release-script" (>=3.0.0) is used, but ".releaseconfig.json" not found. Please create.
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2024 Newan info@newan.de" at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2024 Newan info@newan.de" at the start of LICENSE
[ ] :heavy_exclamation_mark: [E955] iob_npm.done not found in .npmignore

WARNINGS:

[X] :eyes: [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[X] :eyes: [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[X] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W127] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W134] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W135] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[X] :eyes: [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W154] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W168] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[X] :eyes: [W170] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[X] :eyes: [W853] .npmignore found - consider using package.json object "files" instead.
[ ] :eyes: [W953] .npmignore found - consider using package.json object "files" instead.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Wed, 11 Sep 2024 08:52:07 GMT based on commit ed1ac24ecffdd91d41fa85450baec0da2f0af892
ioBroker.repochecker 3.0.2

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
[E039] "keywords" within package.json must contain some keywords besides "ioBroker, template, Smart Home, home automation" related to adapter
[E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[W145] Missing suggested translation into uk of some "common.news" in io-package.json.
[W170] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[W853] .npmignore found - consider using package.json object "files" instead.
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
[E049] "keywords" within package.json must contain some keywords besides "ioBroker, template, Smart Home, home automation" related to adapter
[E157] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[E955] iob_npm.done not found in .npmignore
[W127] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[W134] Missing suggested translation into uk of "common.desc" in io-package.json.
[W135] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[W154] Missing suggested translation into uk of some "common.news" in io-package.json.
[W168] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[W953] .npmignore found - consider using package.json object "files" instead.

Issue closed due to RECREATE request. Folloow up issue #3 has been created.
This issue can be closed.
your
ioBroker Check and Service Bot


text:
section_id 存在于course_section table 但是section_class table 缺失

基于最新的data, 运行benchmark, 到searchCourse1这一步，抛出很多异常信息，是section_id不能在section_class表找到。查看了原因，发现是test_add_course中间读入到 section_id = await rcs.add_course_section(...) 返回 67，然后 cls = cscs[f"{ss['id']}"] 得到的cls是空的list, 具体是cscs[153] 也就是这个section_id下面没有任何section_class数据。这个是有意设计的还是遗漏的？

一个section不一定有class。这种情况正常导入，但是查课时不显示这门课。


text:
Do we need a shortcut for the detail page too?

I am working issue #68
While I was wondering if a shortcut is needed for the detail page, I suggest it.
Now

After Edit

That'll be nice! thanks! :) @Joylish

authors: Joylish ralfyang


text:
bibliografia senza YAML options

quando vado a generare il pdf tramite il gitbook alla fine la bibliografia ha la fromattazione generale del pdf: linespace: 1,5, margini 2.5 etc. Devo toglierla perchè non si può vedere.

Formatting issues solved since it has to be included in the index.Rmd instead of the _output.yml 🥇

repo: NiccoloSalvini/thesis


text:
[Support]: Container will not start

Describe the problem you are having
Im running unraid and using the official unraid appstore version of swatch with all the default docker configs (i've placed a config.yaml in the correct location i believe. container maps to /config/config.yaml).
Version
crzynik/swatch:latest
Swatch config file
# REQUIRED: Define a list of objects that are expected to be seen. These can be specific
# to one camera or common between many / all cameras
objects:
  # REQUIRED: Name of the object
  trash_can:
    # REQUIRED: the list of color variants that this object can be detected as. Useful for
    # different lighting conditions
    color_variants:
      # REQUIRED: the name of the color variant
      default:
        # REQUIRED: the lower R, G, B values that are considered a potential match for the
        # color variant of the object.
        color_lower: 70, 70, 0
        # REQUIRED: the upper R, G, B values that are considered a potential match for the
        # color variant of the object.
        color_upper: 110, 100, 50
        # OPTIONAL: the time range for when this color variant is allowed
        # NOTE: make sure that /etc/localtime is passed to the container so it has valid time
        time_range:
          # OPTIONAL: Color variant is valid if current time is > this 24H time (Default: shown below).
          after: "00:00"
          # OPTIONAL: Color variant is valid if current time is < this 24H time (Default: shown below).
          before: "24:00"
    # OPTIONAL: the min area of the bounding box around groups of matching R, G, B pixels
    # considered a true positive. This is not recommended to be set as a super small amount
    # could be a false positive. (Default: shown below)
    min_area: 1000
    # OPTIONAL: the max area of the bounding box around groups of pixels with R, G, B
    # values within the bounds to be considered a true positive (Default: shown below).
    max_area: 100000
    # OPTIONAL: the min ratio of width/height of bounding box for valid object detection (default: shown below).
    min_ratio: 0
     # OPTIONAL: the max ratio of width/height of bounding box for valid object detection (default: shown below).
    max_ratio: 24000000
# REQUIRED: Define list of cameras that will be used for color detection.
cameras:
  # REQUIRED: Name of the camera
  porch:
    # OPTIONAL: Frequency in seconds to run detection on the camera.
    # a value of 0 disables auto detection (Default: shown below).
    auto_detect: 0
    # OPTIONAL: Configure the url and retention of snapshots. (Default: Shown Below)
    snapshot_config:
        # OPTIONAL: but highly recommended, setting the default url for a snapshot to be
        # processed by this camera. This is required for auto detection (Default: none).
        #url: "http://ip.ad.dr.ess/jpg"
        # OPTIONAL: Whether or not to draw bounding boxes for confirmed objects in the snapshots (Default: shown below).
        bounding_box: true
        # OPTIONAL: Whether or not to save a clean png of the snapshot along with the annotated jpg (Default: shown below).
        clean_snapshot: true
        # OPTIONAL: Whether or not to save the snapshots of confirmed detections (Default: shown below).
        save_detections: true
        # OPTIONAL: Whether or not to save the snapshots of missed detections (Default: shown below).
        save_misses: false
        # OPTIONAL: Variations of snapshots to keep. Options are all, mask, crop (Default: shown below).
        mode: "all"
        # OPTIONAL: Number of days of snapshots to keep (Default: shown below).
        retain_days: 7
    # REQUIRED: Zones are cropped areas where the object can be expected to be.
    # This makes searching / matches for efficient and more predictable than searching
    # the entire image.
    zones:
      # REQUIRED: Name of the zone.
      driveway_entry:
        # REQUIRED: Coordinates to crop the zone by.
        # NOTE: The order of the coordinates are: x, y, x+w, y+h starting in the top left corner as 0, 0.
        coordinates: 225, 540, 350, 620
        # REQUIRED: List of objects that may be in this zone. These correspond to
        # the objects list defined previously and are matched by name.
        objects:

Relevant log output
ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (/usr/local/lib/python3.11/site-packages/werkzeug/urls.py)
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/opt/swatch/swatch/__main__.py", line 6, in <module>
    from swatch.app import SwatchApp
  File "/opt/swatch/swatch/app.py", line 16, in <module>
    from swatch.http import create_app
  File "/opt/swatch/swatch/http.py", line 10, in <module>
    from flask import (
  File "/usr/local/lib/python3.11/site-packages/flask/__init__.py", line 7, in <module>
    from .app import Flask as Flask
  File "/usr/local/lib/python3.11/site-packages/flask/app.py", line 27, in <module>
    from . import cli
  File "/usr/local/lib/python3.11/site-packages/flask/cli.py", line 17, in <module>
    from .helpers import get_debug_flag
  File "/usr/local/lib/python3.11/site-packages/flask/helpers.py", line 14, in <module>
    from werkzeug.urls import url_quote
ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (/usr/local/lib/python3.11/site-packages/werkzeug/urls.py)

Any other information that may be helpful
I've also tried configuring this with docker-compose using the following but with the same issues. The config locations are a bit different but still map to the correct locations in the container.
  swatch:
    container_name: swatch
    image: crzynik/swatch
    #depends_on:
    #  - nginx-proxy-manager
    privileged: true
    network_mode: swatch_network
    restart: always
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
    ports:
      - "4500:4500"
      - "4501:4501"
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${ROOT}/config/swatch/config/config.yaml:/config/config.yaml:ro #also tried just mapping the directories
      - ${ROOT}/config/swatch/media:/media

Would be really great to get a docker-compose example in your documentation. I am running HA in a container and cant rely on HA Addons so i typically stand up my own containers and go from there.

I'm having this issue with the latest release as well.  I was able to get it working by rolling back to the 3.1.0 tag with the following docker-compose entry.
version: '3'
services:
  swatch:
    container_name: swatch
    image: crzynik/swatch:3.1.0-2717ec6
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - swatch:/config/:ro
      - swatch_media:/media/
    ports:
      - "4500:4500"
    restart: unless-stopped

volumes:
  swatch:
  swatch_media:

According to https://stackoverflow.com/questions/77213053/why-did-flask-start-failing-with-importerror-cannot-import-name-url-quote-fr this is caused by a dependency conflict

authors: funkybunch ginkel janstadt


text:
Specify c++11 in node-gyp settings

OS: macOS Sierra
I already have Xcode and Xcode developer tools installed.
As per the README, I installed ghostscript with brew and set the GS4JS_HOME environment variable.
When I yarn install --force, I get the following error:
error /Users/aaronsmith/Documents/XXXX/XXXX/node_modules/ghostscript4js: Command failed.
Exit code: 1
Command: sh
Arguments: -c node-gyp rebuild
Directory: /Users/aaronsmith/Documents/XXXX/XXXX/node_modules/ghostscript4js
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@3.4.0
gyp info using node@6.11.0 | darwin | x64
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp info spawn /usr/local/bin/python2
gyp info spawn args [ '/Users/aaronsmith/.nvm/versions/node/v6.11.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/aaronsmith/Documents/XXXX/XXXX/node_modules/ghostscript4js/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/aaronsmith/.nvm/versions/node/v6.11.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/aaronsmith/.node-gyp/6.11.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/aaronsmith/.node-gyp/6.11.0',
gyp info spawn args   '-Dnode_gyp_dir=/Users/aaronsmith/.nvm/versions/node/v6.11.0/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/aaronsmith/Documents/XXXX/XXXX/node_modules/ghostscript4js',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
  CXX(target) Release/obj.target/ghostscript4js/src/ghostscript4js.o
In file included from ../src/ghostscript4js.cc:20:
../src/ghostscript4js.h:34:10: fatal error: 'mutex' file not found
#include <mutex>
         ^
1 error generated.
make: *** [Release/obj.target/ghostscript4js/src/ghostscript4js.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/aaronsmith/.nvm/versions/node/v6.11.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Darwin 16.6.0
gyp ERR! command "/Users/aaronsmith/.nvm/versions/node/v6.11.0/bin/node" "/Users/aaronsmith/.nvm/versions/node/v6.11.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/aaronsmith/Documents/XXXX/XXXX/node_modules/ghostscript4js
gyp ERR! node -v v6.11.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

It appears that the C++ 11 headers could not be found (mutex.h), so I specified them in the binding.gyp file.
uWebSockets had a related issue with node-gyp, and their solution was what worked for me. The comment is at the bottom (couldn't link to it directly).
https://github.com/uNetworking/uWebSockets/issues/93

Hi @dblarons,
thanks for your contributions!

Got below error whiel running c++ code:
#include <uWS/uWS.h>
int main()
{
uWS::Hub h;
h.onMessage([](uWS::WebSocket<uWS::SERVER> *ws, char *message, size_t length, uWS::OpCode opCode) {
    ws->send(message, length, opCode);
});

if (h.listen(3000)) {
    h.run();
}

}

$ g++ -std=c++11 -std=gnu++11 uw_ex2.cpp
ERROR:
/tmp/cc6sXr4A.o: In function uWS::Hub::Hub(int, bool, unsigned int)': uw_ex2.cpp:(.text._ZN3uWS3HubC2Eibj[_ZN3uWS3HubC5Eibj]+0x36): undefined reference to uS::Node::Node(int, int, i
nt, bool)'
uw_ex2.cpp:(.text._ZN3uWS3HubC2Eibj[_ZN3uWS3HubC5Eibj]+0x5a): undefined reference to uWS::Group<true>::Group(in t, unsigned int, uWS::Hub*, uS::NodeData*)' uw_ex2.cpp:(.text._ZN3uWS3HubC2Eibj[_ZN3uWS3HubC5Eibj]+0x86): undefined reference to uWS::Group::Group(i
nt, unsigned int, uWS::Hub*, uS::NodeData*)'
uw_ex2.cpp:(.text._ZN3uWS3HubC2Eibj[_ZN3uWS3HubC5Eibj]+0xd6): undefined reference to inflateInit2_' uw_ex2.cpp:(.text._ZN3uWS3HubC2Eibj[_ZN3uWS3HubC5Eibj]+0x13d): undefined reference to uS::Node::~Node()'
/tmp/cc6sXr4A.o: In function uWS::Hub::~Hub()': uw_ex2.cpp:(.text._ZN3uWS3HubD2Ev[_ZN3uWS3HubD5Ev]+0x1a): undefined reference to inflateEnd'
uw_ex2.cpp:(.text._ZN3uWS3HubD2Ev[_ZN3uWS3HubD5Ev]+0x7d): undefined reference to `uS::Node::~Node()'
collect2: error: ld returned 1 exit status

authors: NickNaso aatronics dblarons


text:
getPokemonsByFamily() function missed a NOT operator

Hello, a Not (!) operator is missing from the PokemonFamilyId::isValid check in getPokemonsByFamily() function like the !PokemonId::isValid in the getPokemonsByType() function

Resolved. Thanks

authors: NicklasWallgren khitas

repo: NicklasWallgren/PokemonGoAPI-PHP


text:
how to install api to xampp, composer

Sorry, I'm a new member, i downloaded API to my computer and setup composer. But when i go to http://localhost/pokemon/examples/RetrievePlayerProfile.php
Warning: require(D:\xampp\htdocs\pokemon\examples/../vendor/autoload.php): failed to open stream: No such file or directory in D:\xampp\htdocs\pokemon\examples\RetrievePlayerProfile.php on line 3
Fatal error: require(): Failed opening required 'D:\xampp\htdocs\pokemon\examples/../vendor/autoload.php' (include_path='D:\xampp\php\PEAR') in D:\xampp\htdocs\pokemon\examples\RetrievePlayerProfile.php on line 3
Please help me.. thank you.

Go to D:\xampp\htdocs\pokemon\, open a shell, type composer install (the Windows installer should have put it in your path).

Thank you very much. I did it. Thank you  Thank you Thank you Thank you Thank you Thank you

That assertion is there for a reason. In another project ( jaspervdm/pogoprotos-php ) we tried another Protobuf lib ( protobuf-php/protobuf-plugin ), that doesn't have that check, but at least for me a bunch of other errors occurs if I try to run it with a 32bit PHP :cry:

OK,, tks, I will try again with PHP 64bit.

I setup window 64bit and wamp 64bit but when i run localhost,
http://localhost/pokemon/examples/RetrievePlayerProfile.php
For now we only support PHP on 64bit platforms \n
Help me....

Consider this an reply also to #64
What do you get if you run php -r "echo PHP_INT_SIZE;"? It has to return 8, otherwise it's not a 64bit PHP version. I'd suggest using a PHP installation directly provided from windows.php.net, I have one of them working on my Windows machine (not using WAMP/XAMPP, though).

authors: DrDelay mahiepit


text:
Blog posts appear to be broken.

This article appears to have a page (https://nickvision.org/posts/0123/addressingMemoryIssuesInDenaro.html) and contents (https://github.com/NickvisionApps/nickvisionapps.github.io/blob/ac9bbe16ebb861cca211b15626b2ae63f20bb9f9/_posts/2023-01-16-addressing-memory-issues-in-denaro.md) but it is not displayed on the page.

That's because that article was written for our old site, which was in markdown and the new site that we have now is html. I never converted the article properly to HTML, plus it's kind of old, so I just left it like that.
If and when I write new blog posts, they will be in proper HTML and displayed correctly on the site.

authors: lionirdeadman nlogozzo


text:
Text alignment breaks with this plugin

You can normally set text-alignment by placing : on the sides of the dashes under the header row. This does not work with this plugin on. I am assuming this could be related to issues with conflicting styles when cells are merged. Have I missed the way you're supposed to do this with this plugin or is this a bug? Either way, it would be nice if the normal syntax was supported.

Ah, I haven't yet pushed that change to the latest release. It should be fixed and allowed in the latest release, let me know if it still isn't working as expected.

authors: LFalch NicoNekoru

repo: NicoNekoru/obsidan-advanced-table-xt


text:
Prevent moving periods and commas to a new line

Before Xaml Styler:
<TextBlock>
  <Hyperlink Click="HyperlinkCheckForUpdates_Click">
    <TextBlock Text="check for updates" />
  </Hyperlink>.
</TextBlock>

After Xaml Styler:
<TextBlock>
  <Hyperlink Click="HyperlinkCheckForUpdates_Click">
    <TextBlock Text="check for updates" />
  </Hyperlink>
  .
</TextBlock>

It moves ending period to a new line and I can't find any setting to prevent it.Otherwise took is amazing but this behavior makes the extension unusable, because it changes the look of the result:
check for updates. vs check for updates .

add xml:space="preserve" to your page, that prevents this behavior

authors: Alex-Butenko NicoVermeir

repo: NicoVermeir/XamlStyler


text:
Disable/Lock only one dot

Is there a simple way to lock a specific dot, for example the right one and dont let the left one overtake the right one?
Thanks in advance

the version 2.7.5 supports disabling a single dot.
e.g. https://jsfiddle.net/2xy72dod/5272/

Thanks a lot!

authors: NightCatSama boehmli

repo: NightCatSama/vue-slider-component


text:
Migrate the ZkpKeys class from Nightfall to SDK

The migration of the class ZkpKeys from Nightfall to Nightfall SDK is necessary, since the platform is going to heavily use it in order to generate the accounts for the actors and other additional things.

Closing this one for now since there's already a util that allows ZK keys creation. This is via Client (far from ideal), but bringing class from Nightfall into SDK will require some work - not priority.

Hello @imagobea, this task shouldn't be closed, but be kept in the TODO list, since it is a desirable feature.

authors: imagobea israelboudoux

repo: NightfallRollup/nightfall-sdk


text:
Classification of Exchange Traded Funds(ETFs) on the Basis of Profitability

ETFs are a collection of investments, such as equities or bonds, that trade on exchanges and generally track a specific index. They can be bought or sold like a common stock on a stock exchange, and can be bought or sold intraday at different prices.
pls assign me @Niketkumardheeryan i'm GSSoc'24 contributor

pls assign @invigorzz313 I'm gssoc'24 contributor

repo: Niketkumardheeryan/ML-CaPsule


text:
Dinosaur game added

Worked on issue no. #36
Added the dinosaur game folder and connected it with the main page.
Changes on main page:

Game:

@Sohamkayal4103 Just check what the conflicts are and resolve the conflicts in index.html


text:
Android plugin fails to resolve some of the discovered services

There's two bugs in the plugin:
First, you should not reuse the resolve listener. See https://stackoverflow.com/questions/25815162/listener-already-in-use-service-discovery
Secondly, and this is more problematic, having discovered multiple services, even if resolve listener is not shared, only one of the discovered services will be resolved. See: https://stackoverflow.com/questions/24665342/nsdmanager-doesnt-resolve-multiple-discovered-services
This can be reproduced by creating a couple of services with the same service type,
e.g. in Macos dns-sd -R Foo _http._tcp . 8899 mydevice=1 and dns-sd -R Bar _http._tcp . 8899 mydevice=2
You can see that the problem goes away if you add some delay to before calling nsdManager?.resolveService, but of course that wouldn't be a proper fix.
This is a critical bug, and I would be grateful for fixing it!

Oh, it seems this has been fixed? https://github.com/Nimrodda/flutter_nsd/commit/7caf86a64d7289baba1daeedb132b28af1de301d#diff-d522d7763ab9c2fbd638d00d7042d518aa2f9a15e0a7ae3da32a9ca782b5baf9
But flutter package repository has old code!?

I haven't had the chance yet to test the latest code in master so that's why I haven't published it. Have you tried cloning the repo and trying it locally to see if it fixes the issue? You can use a path instead of a version in pubspec.yaml to try it out.
dependencies:
  flutter_nsd:
    path: /path/to/repo

Thanks, I tried it earlier quickly, but not comprehensively, just by replacing the plugin file locally in the cache.
I didn't review the code properly but hopefully it works even when one of the resolving fails, so that the rest of the queue will be handled.
Great to know you can reference by repo, thanks!

I did a brief test of master branch yesterday evening and found out that the discovered service is emitted twice in my case. Prior to #6 the same test resulted in one emitted service. I'll have to take a deeper look either in the following evenings or in the weekend before I publish 1.2.0 to pub.dev.
Have you noticed the same issue on your end?

No, I just re-tested by , and everything works, without duplicates.
Sure, you get duplicates if you press start / stop multiple times. e.g. If you press the start, and a little bit later again, you might see multiple values, but that's because the example code adds new values to the services.
In the listen callback, no duplicates, either.
Also if I register a new service, the listener finds it 👍🏼 .
I tested with Android Pixel 3a and also verified that iPhone works the same.
Of course, I have done this only a couple of times, so there could be some problem. Did you get a duplicate just by pressing start once and with a fresh build/run?
I ran flutter clean and build having this dependency definition for flutter_nsd:
flutter_nsd:
    git:
      url: git://github.com/Nimrodda/flutter_nsd.git

1.2.0 is released to pub.dev

authors: Nimrodda egaga


text:
🛑 Portal is down

In baa4ef7, Portal (https://rekursion-vithack2020.netlify.app/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal is back up in 69f28c0.

repo: Nirmitjatana/upptime-personal