scuffed flame core lighting

(maybe this is intentional or a result of lighting engine changes or something, this is not definitive)

the exaggerated overall redness of the level was caused because of a lighting bug on comile, lightihg has been re-built and it should be now working as intended


ImportError: cannot import name _remove_dead_weakref

Automatically signing iOS for device deployment using specified development team in Xcode project: Q48Y4UFKL8
Running pod install...
Starting Xcode build...
Xcode build done.
Installing and launching...
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File<EMAIL_ADDRESS>line 52, in <module>
    import weakref
  File<EMAIL_ADDRESS>line 14, in <module>
    from _weakref import (
ImportError: cannot import name _remove_dead_weakref
5.4.0 - [Firebase/Analytics][I-ACS023007] Firebase Analytics v.50001000 started
5.4.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
Error connecting to the service protocol: HttpException: Connection closed before full header was received, uri = http://<IP_ADDRESS>:8100/ws

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v0.5.1, on Mac OS X 10.13.5 17F77, locale en-IN)
[!] Android toolchain - develop for Android devices (Android SDK 28.0.0-rc1)
    ✗ Android license status unknown.
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
[✓] Android Studio (version 3.1)
[✓] IntelliJ IDEA Community Edition (version 2018.1.5)
[✓] VS Code (version 1.23.1)
[✓] Connected devices (1 available)

! Doctor found issues in 1 category.
Process finished with exit code 0

I'm basically trying to implement Speech Recognition plugin found here: https://github.com/rxlabz/speech_recognition
While it works just fine on Android, a new iOS build in Swift finds one or more errors. Have been struggling for days. Please help me resolve this issue.

Duplicate of #17803

Thanks @dklinzh for spotting.
@sahil311289 I hope it's ok with you if I close as dup.
Otherwise add a comment and I'll reopen.

you don't need to remove it just
brew unlink python@2

There's another solution outlined here which involves using an alias to only modify your shell path while running swift.
Seems like a good strategy if you don't want to change the way you're managing Python system-wide (that is, with Homebrew 😄).


use USD for Paypal connect

Coverage remained the same at 75.894% when pulling 5303f560bdfd2571cb1974fca3aea0ba685e2df0 on paypal into a7df9f19b00193425614691a406d12e6c361c757 on master.


Revert "fix: use CI=1 for tidb make command"

Reverts PingCAP-QE/ci#2167
CI=true is  a default environment variable in jenkins. So it is unnecessary to set CI=1.

/lgtm


Show Liked Posts on Dashboard

Feature request-
We can have a section for liked post of a user
Is your feature request related to a problem? Please describe. (optional)
A clear and concise description of what the problem is.
Describe the solution you'd like
We can add a liked post section on dashboard and on user profiles (maybe)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Describe how this feature will be useful to our readers.
Users can retrieve their liked posts and if they are able to other peoples liked posts, then they may know the other person's interests
Additional context
Working under GSSOC'21

Note:

Do mention if your are working under GSSoC'21.
If you want to work on an issue, you should check if it has already been assigned to anyone. If the issue is free you can comment /assign to get the issue assigned to you.
If you are raising a new issue and want to work on it then also you should comment /assign under the issue to get it auto assigned.
Please refrain from adding labels to your issue/pull-request on your own. It is the job of the Project Admin and the Mentors to review your issue/pull-request and add labels accordingly.
According to the level of the issue, respective time will be allotted under which the task needs to be completed/resolved by the assigned person. If the issue is not resolved within the given time, it will be assigned to the next person. In case of any discrepancies, the decision of the maintainer will be final.

level - 0: 2 days
level - 1: 3 days
level - 2: 4 days
level - 3: 5 days

/assign


hassio-ecoflow not working after reinstall and updating EcoFlow-firmware to newest release with port 8055 working

We had the well know problem with this integration, broken by EcoFlow etc. You all know, what the case was.
Together with a lot of other users, we had put massive pressure on EcoFlow, because we are planning commercial usage of DeltaPro and bought more than one unit ... etc.
Our concern - absolutely strange:

We have the lastest versions of all HA-components, taking all the updates.
EcoFlow-firmware is newest release with port 8055 working
We downloaded the lastest version of hassio-ecoflow alpha-3 from HACS via the shop
The integration shows up after restart and we enter the correct IP. No question: EcoFlow is online, FING shows it, ping is working
The EcoFlow-integration tile shows up without any entities. It looks like it does not find the DeltaPro.
EcoFlow is working on the Wifi-based App on iPhone
We veryfied, that port 8055 is sending data ...

But my colleagues and I are standing in front of the forest and don't see this one tree ...
Any idea? Call us "fools" ... but please drop a hint, if you have any idea.

@michael5411 If you are using Home Assistant 2023.3 - I recommend to rollback to version 2023.2.
Version 2023.3 introduced some breaking changes for this integration (see this issue).


Add HybridCompatilityMixin subclass for use with RESTCapableHybridTopologyFactory

We'll want to subclass  HybridCompatilityMixin (used with HybridTopologyFactory) to work for running repex with RESTCapableHybridTopologyFactory.
Also need to add a test for running dipeptide repex, which will be specified as a GPU unit test.

From perses dev sync today:
Ivy's TODO:

In HybridCompatilityMixIn's setup(), set lambda_protocol=None and create an instance of the appropriate lambda protocol class depending on the name of the factory supplied to the init

Ivan's TODO (after Ivy's TODO):

John's feedback: We don't want to create a new lambda protocol class every time there is a new protocol. We will want to refactor such that the lambda protocol classes (in lambda_protocol.py) are part of the HybridCompatabilityMixin?


[BUG] CLI - Can't install app with rancher apps: missing unit in duration

Rancher Server Setup

Rancher version: 2.7.3
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: 1.25
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Hosted EKS

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom): Admin

If custom, define the set of permissions:

Describe the bug

Chart fails to deploy
 "failed to install app aws-load-balancer-controller. Error: invalid argument \"300\" for \"--timeout\" flag: time: missing unit in duration \"300\"",

Relates to https://github.com/helm/helm/issues/7375
To Reproduce

helm repo add eks https://aws.github.io/eks-charts  --helm-version v3
rancher apps install --set clusterName=demo-eks --set serviceAccount.create=false --set serviceAccount.name=aws-load-balancer-controller aws-load-balancer-controller aws-load-balancer-controller --version 1.7.1

Result
Expected Result

Be able to pass in a unit to rancher apps install command, or the install command append a unit.
Screenshots

Additional context

I ran into the same problem:
rancher apps install --namespace ava-test cattle-global-data:test-chart my-deploy
leads to the following rancher log outputs:
2024/05/03 15:24:09 [ERROR] error syncing 'p-xmhwr/my-deploy': handler helm-controller: failed to install app my-deploy. Error: invalid argument "300" for "--timeout" flag: time: missing unit in duration "300"

rancher apps install --helm-timeout=180s --namespace ava-test cattle-global-data:test-chart my-deploy
fails earlier (directly on the cli) as rancher-cli cannot parse time with an unit:
time="2024-05-03T17:33:59+02:00" level=fatal msg="invalid value \"180s\" for flag -helm-timeout: parse error"

Seems like rancher-cli argument validation is to strict here.
Does someone know a workaround?


Add label and title to trove classifier request link

Adds title and label :)

@nlhkabu The link doesn't add a label if you don't have commit access (just tested that with #3489). That bit of the URL could be dropped. :)

hmmm... I thought that it would work if I made the PR :(

updated @pradyunsg

@pradyunsg I've added you as a reviewer - could you please make a formal review?  Thanks


Added some consistency in the README.md

I tweaked a title capitalization so that the README.md looks a bit more consistent.

 You should sign our Contributor License Agreement in order to get your pull request merged.

 You should sign our Contributor License Agreement in order to get your pull request merged.

Merged in fb0e17a


Warp totems and the deconstructor

With this mod, 1.2.2 tested, one cannot place a consumable warp totem into a deconstructor. You are always warped, or the do you want to warp dialog is displayed.
I don't do this much, if at all. I got an island warp totem as loot in the volcano. I have the island obelisk, so I tried to put the totem into a deconstructor to get a dragon tooth. Then sell the tooth.

This should be fixed in the 1.2.3 alpha. Can you try it and let me know?

Alpha-1 does allow me to place a warm totem in a deconstructor.
I'll just also confirm that the warp menu does work in Alpha-1 without the need to do a GMCM option save (when after obelisk is config setting. always, always worked).


Problem with accessing g+ data

The line 251 right now looks like that: if (this.gplusProfileId === null && eventData['goo.contactsProfileId']) { .
However everytime it's run this.gplusProfileId is undefined in my case, not null and the line 252 is not called this.getInfoFromGPlus(eventData['goo.contactsProfileId']);.
I've done a quick workaround for it in 45aca7b995a61a434ddf648f7611af26667e2ee0, but I know it has to be done differently.
I have also question about G+ API. Is there info about activating it in the instruction of setting up the script? I didn't know I have to manually turn it on :/

Well it's not completly solved. It works correctly, but there's a problem on a day with my own birthday and the email looks like that:

And this is log:

[17-09-21 15:07:07:096 PDT] I: test() running.
[17-09-21 15:07:07:098 PDT] I: main() running.
[17-09-21 15:07:07:099 PDT] I: generateEmailNotification() running.
[17-09-21 15:07:07:100 PDT] I: Date used: Sat Apr 22 2017 06:00:00 GMT+0200 (CEST)
[17-09-21 15:07:07:254 PDT] I: Looking for contacts events on Sat Apr 22 2017 06:00:00 GMT+0200 (CEST) (2017-04-22T06:00:00Z / 2017-04-22T07:00:00Z)
[17-09-21 15:07:07:971 PDT] I: Found: 1
[17-09-21 15:07:07:972 PDT] I: Found 1 events.
[17-09-21 15:07:07:973 PDT] I: Extracting info from raw event object...
[17-09-21 15:07:07:975 PDT] I: Extracting info from Google Plus Profile...
[17-09-21 15:07:08:194 PDT] I: Built 1 contacts.
[17-09-21 15:07:08:346 PDT] I: Checking birthdays on 22-04-2017
[17-09-21 15:07:08:389 PDT] I: Found 1 birthdays
[17-09-21 15:07:08:391 PDT] I: Checking anniversaries on 22-04-2017
[17-09-21 15:07:08:392 PDT] I: No events found on this date.
[17-09-21 15:07:08:393 PDT] I: Checking custom events on 22-04-2017
[17-09-21 15:07:08:394 PDT] I: No events found on this date.
[17-09-21 15:07:08:395 PDT] I: Building the email notification.
[17-09-21 15:07:08:727 PDT] I: Sending email...
[17-09-21 15:07:08:835 PDT] I: Email sent.

I think that is a separate issue that I thought I had solved, but apparently I have not.
I'll describe what happens in my case; let me know if it's the same for you.
If I look in my clanedar I have two birthdays for myself:

the first one is generated by Google and is not directly linked to any contact (it's Google's way to wish me, as the owner of my account, a happy birthday). This is an event of type SELF;
the second one is generated from the contact "Giorgio Bonvicini" that I added to my own contacts to store my emails and phones. This is an event of type BIRTHDAY;

The script somehow fails to merge the data from the event and from the contact into a single notification.

In my calendar, I only have one event which says 'Happy birthday!' - I guess it's the self one. I don't have the second event and I don't have Bartosz Rodziewicz contact in contacts.

The other problem that I have found is my test contact (which doesn't have any g+ account) returns some g+ ID and throws

[22-09-2017 12:44:14 Europe/Paris]W: Invalid GPlus Profile ID:<PHONE_NUMBER>17068398484
into log. The because this is warning it sends log as a mail. I don't know why it reports this g+ ID, but I would suggest changing it from warning to normal log message, because other users may experience it as well.

@baatochan I've tracked down the problem that caused your own birthday to be split into two different lines. The birthday from the event was saved with label "SELF", while the birthday from Google Plus (which is obtained as the event contains your G+ id) was saved as "BIRTHDAY".
I have coded a solution for this, but will push it together with other fixes I am working on right now.
PS: Sorry for the triple notification: I answered to the wrong issue.

@GioBonvi While testing the newest version from #73 I see that it still isn't resolved.
However, the mail that I get on my birthday looks different and more strange for me:

Before it showed 2 birthday events and showed my google mail. Now it has 2 events (one birthday, one self) and can't access my google email (which is (and always was) hidden (accessible for my circles only) on g+) and shows my 'work' mail which is set (and always was) as public on g+. I don't know what's going on and to be honest I can't even track which commit made this changes.

I had noticed at at this line of this commit
that @GioBonvi had removed the SELF case from the switch statement, and had thought that was just because it was now handled elsewhere, but now I wonder if that was an accidental deletion? I just offer that as a pointer for investigation, because I can't help much beyond that with Google+ stuff as I don't use it.

@baatochan
Could you confirm that the double birthday bug is still present in the last version of giobonvi-development? I do not experience it anymore.

Yup, it's still present. The mail looks like that:

I would suggest that you don't experience this bug because default settings don't send info about custom events. I've got settings.notification.eventTypes all 3 set to true.

I pushed a new commit to giobonvi-development which fixes this issue for me. Could you confirm if this works for you as well?

Yup, the issue is resolved :)


[ci:component:github.com/gardener/oidc-webhook-authenticator:v0.7.0->v0.8.0]

Release Notes:
Scheduler will now try to distribute OWA pods between different nodes if possible.

OWA now requires that the OIDC providers that it connects to use version of TLS >= 1.2

Helm upgrade will now correctly trigger a deployment rollout when a kubeconfig secret is changed.

OWA is now built using `golang:1.17.8`.

/cla


Disable higlighting all occurences of selection in editor if it contains only whitespaces

As described in #28446 - do not highlight all occurrences of string in editor if selected string contains only whitespaces.
No weird highlight with whitespaces anymore:

Highlighting words still works:

Please review.
Bugsquad edit: Fixes #28446.

Thanks!


Task: geography based checklist (NatureServe)

As  curator, I want to produce a list of species scoped by geographic regions.

The initial set of data was produced through SQL query of SFdb for Plecoptera (of North America).  Taxa which had recorded TDWG distribution data were selected for valid, synonym, and nomen dubium name status.  Due to the particular way certain data are recorded only in the valid name, the parent taxon name ID (AboveID) is used to select taxa for nomina dubia and synonyms.
This is a sort of inverse to the report table of issue #2046.

I think it should be implemented as a part of OTU Filter development.

@proceps you are right, the otu/filter.rb will have the code to return the records, this is targeting a task/view that will display the result in the correct format.
@jrflood please post the export format here. @debpaul can you comment as to whether that format is in fact a DwC checklist when it arrives.

I would say, we should try to replicate Endemism task format where all distribution records normolized to valid names and all names returned in hierarchical order.

This comes out of a specific request to us from NatureServ, so generalizing it might be useful, but the issue does have a specific goal.

Looking now from these guidelines.

#GBIF DQ Requirements for Checklists.
And comparing to a sample dataset.

from GBIF Checklist Data Templates.

Feedback.

the screen shot from @jrflood has no associated geographic region information. Are these data for a given region? If so, would need to put in a separate related file. (see above example dataset).
a GBIF Checklist also has an eml.xml file.
Likely easiest to create a compliant checklist using the IPT which will generate the other expected files.

I don't know what NatureServ is hoping for/expects?
Checklist Expectations (minimal) and all of these are in the above screenshot.

[x] taxonID (req'd)
[x] scientificName (req'd)
[x] taxonRank
[x] kingdom
[x] parentNameUsageID
[x] acceptedNameUsageID

Dataset metadata (EML) (all fields req'd except bibliographicCitation)

[ ] title    (the title under which the dataset will be published at GBIF)
[ ] description   (English language text, describing the dataset.)
[ ] publisher    (title of the institution or organization that will be listed as the data publisher at gbif.org.)
[ ] type      (type of the dataset. Here: "checklist".)
[ ] license      (A machine-readable statement of the rights attached to the published dataset. Use either CC0 or CC BY.)
[ ] contact      (Contact data (minimum: name and email) for at least one administrative contact for the dataset.)
[ ] creator     (Contact data (minimum: name and email) for the creator of the dataset)
[ ] metadata provider      (Contact data (minimum: name and email) for the author of the dataset metadata)
[ ] bibliographicCitation     (a text specifying how your dataset should be cited in publications that make use of your data.)   (strongly recommended)

Is this what was needed @mjy? If you need more info, I can meet with Rich to go farther ...

This would also be useful to me.

Marking as duplicate of https://github.com/SpeciesFileGroup/taxonworks/issues/2069


regarding batch_size

Hi dear
can u please tell about how to choose batch size?
My system has one GPU(8 GB memory) and System memory is 64 GB.
when i tried to run with default batch size of 128 , it gave run time error: out of memory
Then i reduced it to 20, it started working.
But i want to know what should be appropriate batch size according to my system configuration, little about how to set appropriate batch size and whether it will affect accuracy?
I would be very much thankful for your suggestion on this....

I did not conduct experiments for searching the best batch size,
but I think it should be large like 128 and 256.
In preliminary experiments using ResNet-34 trained on ActivityNet,
using batch size 128 achieved better accuracies than smaller one.
If you have only one GPU, you should use batch size as large as possible.

Thanks
On Thu, 22 Mar 2018, 17:51 Kensho Hara<EMAIL_ADDRESS>wrote:

I did not conduct experiments for searching the best batch size,
but I think it should be large like 128 and 256.
In preliminary experiments using ResNet-34 trained on ActivityNet,
using batch size 128 achieved better accuracies than smaller one.
If you have only one GPU, you should use batch size as large as possible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kenshohara/3D-ResNets-PyTorch/issues/38#issuecomment-375284773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Adg6KYxwbxoxZ4V4lRluJgGBX8Np9xoVks5tg5cugaJpZM4S2icN
.


[Fix][Proxy] Avoid using synchronous operations in the async method to block metadata threads.

Fixes #15549
Master Issue: #15549
Motivation
See #15549
Modifications

Use validateTopicOperationAsync instead of checkAuthorization method and make it pure async.
Refactor code to make it more readable.

Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[x] no-need-doc

@leizhiyuan  Please take a look, thanks!

#15694 Has been fixed this issue. So, close this PR.


Deposit into Idle Finance Vaults giving 'Something went wrong error'

Overview
When depositing into an Idle Finance vault for the first time it allows you to select an amount to deposit but when you select continue then it gives a 'Something went wrong' error.
Not sure if its happening to vaults that already have a balance but when i select continue for the amount to deposit it goes through to the sign and broadcast screen so going to assume you can deposit
References and additional details

Log into app.shapeshift and connect to walk of choice
Navigate to DeFi page and select the 'Earn' Tab
Scroll to find an Idle vault that hasn't been deposited into yet (or use the CTA in Eligible Opportunities)
Select Deposit and enter an amount
Select Continue and notice the error come up and the continue button spins indefinitely.
*happens on approvals too

Acceptance Criteria
Should be able to deposit into Idle Vaults
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

@MBMaria this is currently being fixed by the Idle team on-chain, will comment here when that's done so you guys can retest it

@MBMaria this should now fixed on-chain as the new CDO contracts have been added into Idle's registry.
I wasn't able to test an actual deposit, but the pre-deposit, which is calling the same contract method, worked for me. Can we retest this one and close it? 🙏🏽

Tried this the other day and was successful in depositing. Closing this now.


Fix for boolean values in overflow

Boolean values in overflow fields were being converted to decimal due to isinstance(True, int) being True in Python 3.
Check to see if a value is a bool first to handle that special case, then fall back to treating it as a number.

Thanks! Note that I will be releasing 0.5 soon, which will remove the "overflow field" functionality entirely. I'll do a point release on 0.4 with this fix before that, though.


Provide matching service to PeerPrep

Backend for matching service.
Implemented using microservice architecture.
Use REST API for the communication between client and server for resources.
Implement findMatch and cancelMatch feature.
Provide a maximum 60 seconds matching service with specified matching criteria.
Use AMQP to facilitate the matching request queuing process.
Use MongoDB to store matchedPair results.
Containerize matching service.

Close #46


High-risk extensions [draft]

This is an update for a new feature that we have in works right now.

@microsoft-github-policy-service agree company="Microsoft"

@battle-born,
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.
We'll close this PR. Thank you.


Investigate cast outputs

Which components does the task require to be changed? (think hard pls)
sncast
Description
Ideally error messages should be helpful, and the output digestable by the user
It seems that this needs assessment and perhaps new approach in different places.
This task is about finding some incosistencies, documenting them and proposing a solution.

This is a draft of found issues (WIP)
UX issues

No RPC URL Validation (or poor one)
When not passing URL, there is a problem but it's not clear that it's a top-level argument (when passed normally after arguments, its' rejected. This issue happens for all global arguments
No numeric (range) validation for addresses
Requiring RPC url (i.e. for account add/account delete) is frustrating when you don't know why it's required
It is generally not known, which token i need to prefund with, when creating an account
Addresses (i.e. on account create) are not displayed with proper padding

Nice to have

Suggest that calldata is the issue when encountering "Failed to deserialize param"/"Input too long for arguments" errors

Corresponding issues were created, or enriched with findings from this task. Considering complete, closing.


Cherry-pick 4.0: support common names validation (#7134)

What problem does this PR solve?
cherry-pick #7134
What is changed and how it works?
cherry-pick
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Release note
Support common names validation.

Why close?

/merge


Network is unreachable

Hi, This repo is wonderful and helpful for my research. But I am struggling to reproduce the result.  When I run download_tst_classifiers.py, the error happened. I am wondering if the link has problems.
<Failed to establish a new connection: [Errno 101] Network is unreachable>
Also, can you give me some suggestions on how to construct a pipeline to apply RLprompt to the generation task? text-style-transfer is quite complex for me. Thanks :-).

Thank you for your interest!

Classifier Download: May I ask if you can access Google Drive? That is where our model files are hosted. If you do not, let us know and we can set up an endpoint available to you.
Generation Task: Please refer to our script run_tst.py for an example of the pipeline. To apply to your own task, you can simply create your own reward module. That is, simply swap out this line for your own implemented task.

Let us know if you have other questions. I am closing this issue now because it's a clarification question.


Add tests for generateAssets

Adding these now because it would be helpful when working on #1481.

it's also intended that any file added to assets gets copied to public
is this worth adding here? Or it might already be covered, I'm not that confident with test code

any file added to assets gets copied to public

Good point, I'll add a test for that.

@joelanman I've added a test for adding a file to app/assets/test/testtest

Approved


Move to separate components as recommended by Dagger

https://dagger.dev/dev-guide/testing

This PR was released with 0.22.1


Questions on benchmark

I find that you choose to use 'roi_Xconv1fc_gn_head_panet' as head in your model when training R50-PANet and get a 39.8 box mAP. I tried to train a panet using '2fc_mlp_head' with PA-structure unchanged and got a 37.1 box mAP, which is only 0.4 above the fpn baseline. Is there something wrong with this implementation, or is there any probability that PA-net has to be combined with a heavy head to have a good performance?

Hi,
I have uploaded the model trained with 2fc. The performance should be 39.6 box AP. Please try with the new model and corresponding config file.
Thanks!

Hi @ShuLiu1993 , thanks for this wonderful work! I wonder if pretrained model on Cityscapes can be provided(or converted) in this PyTorch implementation? Thanks!

Thank you for your response, I will try with your advice. : )

What if you use only '2fc_mlp_head' rather than '2fc_mlp_with_gn_head', which is more precise on evaluating the influence of 'pa structure'?

I tried to train the panet on res50-fpn without using any gn to get a precise evaluation on the influence of PA-structure and get the  37.1 bbox mAP. I find that your new model still use GN in both fpn-part and the 2fc-head. Does it mean that GN is really important for training PA-structure?

@JiamingSuen
Thanks a lot for your interest! Sorry that I really don't have much time on this currently. Maybe you can try this by yourself since the pre-trained model on COCO is already released.

@JrPeng
In our origin implementation, we used Sync BN. In this version, we us GN instead. Using this kind of normalization can help the network converge better and achieve better performance.

@ShuLiu1993 I can totally understand, thanks for your reply!

Thanks for your reply. I will try to figure out recently. Thank you.

@ShuLiu1993 I'm trying to reproduce cityscapes training with COCO pretrained model, and I'm currently having 34.4 mask AP on Cityscapes. I used the finetuing schedule described in the Mask-RCNN paper(4k iter in which reduce lr at 3k with initial lr 0.01 and 8 batch size). Did you choose the same finetuning steps and lr schedule in PANet? Thanks very much.

@ShuLiu1993 Any comment please? I didn't find any reference about finetuning parameters in your paper. Thanks very much!

@JiamingSuen Sorry for the late reply. We have listed several hyper-parameters in our paper, which are borrowed from Mask R-CNN. In other words, we strictly followed the training parameters used by Mask R-CNN.

@JiamingSuen can you give me a short tutorial on how to finetune the pretrained coco model? I would like to finetune the model for pedestrian detection on the Kitti Dataset but I don't know where to start.

You may start by trying to adapt cityscapes loader/model to KITTI since KITTI segmentation dataset is using cityscapes format. Cityscapes tools In this codebase would be helpful.

@Panxj I find that baseline of this implementation is higher than baseline of Detectron.pytorch by Roy. For example, res50-FPN without GN in this implementation has a 38.3box AP while it has a 37.7box AP in Roy's implementation. Besides, I add only PA structure in Roy's code, and find it only contributes 0.3AP improvment, but GN/adaptive fusion contributes a lot. Maybe there is something wrong with my implementation. You can try yourself and we can discuss based on your results.

@ShuLiu1993 thank you for sharing your work. I had run the ablation on PAnet with panet_R-50-FPN_1x_det_2fc.yaml config file. I also found that this repo has better baseline compared to original pytorch repo or official detectron in caffe. Without any GN, buttom up path, ada feature pool and multi scale training, this repo can achieve 37.9 mAP, it is higher than official detectron by 1.2 mAP. It seems like your original panet version using sync BN has different improvement factors. But could you please clear us why here we get so good baseline :D.

GN
BU path
ada pool
ms train
Result
Note

x
x
x
x
39.6
Default panet_R-50-FPN_1x_det_2fc.yaml

x
x
x

39
configSCALES=(1000,)

x
x

38.5
configSCALES=(1000,) ROI_BOX_HEAD=fast_rcnn_heads.roi_2mlp_head_gn

x

38.4
configSCALES=(1000,) ROI_BOX_HEAD=fast_rcnn_heads.roi_2mlp_head_gnCONV_BODY:FPN.fpn_ResNet50_conv5_body

37.9
configSCALES=(1000,) ROI_BOX_HEAD=fast_rcnn_heads.roi_2mlp_head_gnCONV_BODY:FPN.fpn_ResNet50_conv5_bodyFPN.USE_GN=False

Hi guys, thanks a lot for your interests!
This codebase is heavily based on Detectron.pytorch by Roy. In this codebase and released configs, I used multi-scale training larger testing scale as I noted in the paper. This may be the main reason that the baseline is with a better performance. I also made some minor modifications may also contribute a little bit.
With GN or SyncBN do help PANet to achieve a better performance with other settings kept the same. They can help the network to converge better. So that's why we should try GN or SyncBN first. Currently I haven't compared GN and SyncBN under the same codebase. But I think SyncBN will achieve comparable or even better performance.

hi @thangvubk
i use bu-path, ada-pool, and ms-train, and test use MIN_SIZE_TEST: 1000, only get 38.1 mAP. is there something i miss?

@zimenglan-sysu-512 just use panet_R-50-FPN_1x_det_2fc.yaml config file and dont make any modifications.

hi @thangvubk
do u try soft-nms instead of standard-nms? if use, can u share the results here?

@zimenglan-sysu-512  For bu_path + ada-pool + ms, i didnt make any modification, just clone the network and train. Did you do the same thing?

i did not use this repo, i just add some code maskrcnn-benchmark (w/o GN).

@zimenglan-sysu-512 It is hard to say when you implement in other repo. Ussually, it doesnt work as expected due to underlining implementation details. You can try to add GN to see if their is any improvement.

thanks @thangvubk
i will try to add GN to FPN and heads.

hi @thangvubk
i add GN to FPN and RoI head, but the performance only gets 38.3%. btw, when training, since the gpu memory limits, so each gph holds 1 image.

@zimenglan-sysu-512  i'm not sure where u are wrong. Btw, mmdet is planing to release PANet also, see here.

@zimenglan-sysu-512 I also re-implement the panet using maskrcnn_benchmark（2mlp without ms train， gn， sgn）. But the performance is worse than this repo. If convenient, can you share your code with me? I just want to make sure whether there is something wrong with my code.


chore: pre-commit autoupdate [ci skip]

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

v5.0.5
GitHub release

Your semantic-release bot :package::rocket:


Simple model quality stats

It would be very nice to have quality stats for the simple model, maybe in a new subtab of Annotation tab.
The idea is to do 10-CV predictions on the tagged training data, and produce a confusion table and accuracy / F1 stats.
Also, simple training accuracy (or macro F1) on the training set (+OOB accuracy for random forest) would be nice.

already on the tab in the top when the simplemodel is calculated no ?
Le ven. 15 nov. 2024 à 14:01, jboelaert @.***> a écrit :

It would be very nice to have quality stats for the simple model, maybe in
a new subtab of Annotation tab.
The idea is to do 10-CV predictions on the tagged training data, and
produce a confusion table and accuracy / F1 stats.
Also, simple training accuracy (or macro F1) on the training set (+OOB
accuracy for random forest) would be nice.
—
Reply to this email directly, view it on GitHub
https://github.com/emilienschultz/activetigger/issues/144, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACABSTFU4A4ATB3P4GFMSA32AXWBDAVCNFSM6AAAAABR3ERSX2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3DCOBZGI2TENA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Made it nicer


Modified FIP1 to include get_cancelled_fio_requests

I'll leave this to @pawmmm, but I assume it was made at his or Eric's request.


Update 4.how-to-start-jitting.md

fixed misprints

@amel-true thanks! This repo is an archived version of old blog, would you care to open similar PR for https://github.com/indutny/blog.ng instead?

shure
On Sun, May 28, 2017 at 10:24 PM, Fedor Indutny<EMAIL_ADDRESS>wrote:

@amel-true https://github.com/amel-true thanks! This repo is an
archived version of old blog, would you care to open similar PR for
https://github.com/indutny/blog.ng instead?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/indutny/blog/pull/7#issuecomment-304534753, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABqW-q0dPCbASLlAokkO3Fhid332oxaYks5r-coGgaJpZM4NouzC
.

--
Андрей Мелихов


Windows compilation: expected_span_name is not captured by the lambda with MSVC

Commit Message: Ensure expected_span_name is captured by lamda with MSVC
Additional Description: MSVC's lambda capture rules are more strict, it seems in this case this variable has to be explicitly captured or captured with the capture default
Risk Level: Low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A

If it is more desirable to explicitly capture the variable, I can make that change, just used the capture default since it was less verbose and wouldn't cause future breakages

This line has changed back and forth several times. Can you work with @marcomagdy to figure out the path forward here? Also, until we run the tests in Windows CI I'm not sure it makes sense to keep fixing small things like this.

@marcomagdy is the lambda change here a consequence of something that fixes coverage or potentially a merge conflict resolution issue: https://github.com/envoyproxy/envoy/commit/5dcfa7b44999f8493a343796ba9dc7194c9f05c4#diff-4d36e44b2a9f6b2cde56e3832154d528

Please merge master to fix CI.
/wait

@mattklein123 regarding your point about CI: agreed, these small fixes seem to be occurring less and less often while we work to get CI going with larger workers/RBE etc. but we can batch them up more while we're working to get tests passing, it was not a great time catching up when we had a huge batch of compilation issues to sort out so we've just been trying to avoid that again


specs expects 'unstable' feature of rayon-core

I have run into an issue compiling specs 0.9.0.
No matter what branch I utilize (1.17.0, 1.18.0, 1.19.0-beta, 1.19.0-nightly) I get the following error
cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: Package `rayon-core v1.2.0` does not have these features: `unstable`

I can't seem to track down what is specifically trying to request the unstable feature.
Though I may be screwing something up.

Relevant commit - https://github.com/nikomatsakis/rayon/commit/20de1ff12df93c739152e5ccfe48a91a66adac99
Please force an earlier version of rayon-core in the meantime, while we are going to fix specs.
@torkleyy this is rather unfortunate that we relied on an unstable feature, we shouldn't have released it then.

@robojeb Sorry for breaking your build. @kvark You're right, we shouldn't have. I fixed it and will release in a few minutes, please upgrade to Specs 0.9 then.


geeqie: 1.7.3 -> 2.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for geeqie is: "Lightweight GTK based image viewer"
meta.homepage for geeqie is: "https://www.geeqie.org/"
meta.changelog for geeqie is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.1 with grep in /nix/store/gkprmnpqlfa7d64zm3dc40iwr1q72ch0-geeqie-2.0.1
found 2.0.1 in filename of file in /nix/store/gkprmnpqlfa7d64zm3dc40iwr1q72ch0-geeqie-2.0.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
geeqie

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gkprmnpqlfa7d64zm3dc40iwr1q72ch0-geeqie-2.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A geeqie https://github.com/r-ryantm/nixpkgs/archive/44a7c41b57a5d4f0208baba466f30d66c1e0008a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gkprmnpqlfa7d64zm3dc40iwr1q72ch0-geeqie-2.0.1
ls -la /nix/store/gkprmnpqlfa7d64zm3dc40iwr1q72ch0-geeqie-2.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

geeqie

Maintainer pings
cc @jfrankenau @pSub @markus1189 for testing.

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

1 package built:

geeqie

Digging zombies here... That commit seemed to have updated the version without fixing the fetchFromGithub's sha256 ; making geeqie not updated in practice.
geeqie itself doesn't seem to include a version, but /nix/store/wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-2.0.1/share/man/man1/geeqie.1.gz says it's 1.7.2 which corresponds to the last time the hash was updated.
I'm not blaming anyone here (mistakes happen, and nix makes it easy to miss hash updates with old files in cache) but how did @r-ryantm 's bot, ofborg, onny, whatever build infra produces the cache all fall through that?
Build system changed with 2.0 I'll have a stab later

opened https://github.com/NixOS/nixpkgs/pull/218975 for 2.0.1 update

Still thinking of improving the checks, in particular:

found 2.0.1 with grep in /nix/store/gkprmnpqlfa7d64zm3dc40iwr1q72ch0-geeqie-2.0.1

I've looked in my derivation of the old 2.0.1 build, and all occurrences of 2.0.1 are actually the output path (only file with a match):
$ strings  /nix/store/wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-2.0.1/bin/geeqie | grep 2.0.1
/nix/store/wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-2.0.1/share
/nix/store/wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-2.0.1/bin/.geeqie-wrapped
makeCWrapper '/nix/store/wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-2.0.1/bin/.geeqie-wrapped' \
    --prefix 'XDG_DATA_DIRS' ':' '/nix/store/wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-2.0.1/share' \

Would it make sense to change the grep from '2.0.1' to something that doesn't include the path itself, this can be done with negative lookahead e.g. with ripgrep this won't match:
$ rg -a  --pcre2 -uuu '^(?!.*wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-).*2\.0\.1' /nix/store/wq054q6f4qypsn178z85zzgnrw9fff9q-geeqie-2.0.1/; echo $?
1

But it'll work on a the new build:
$ rg -a  --pcre2 -uuu '^(?!.*z9l2xakz7cgw6yfh83nh542pvc0g4rkq-geeqie-).*2\.0\.1' /nix/store/z9l2xakz7cgw6yfh83nh542pvc0g4rkq-geeqie-2.0.1/; echo $?
/nix/store/z9l2xakz7cgw6yfh83nh542pvc0g4rkq-geeqie-2.0.1/share/metainfo/org.geeqie.Geeqie.appdata.xml
36:    <release version="v2.0.1" date="2022-08-12"/>

/nix/store/z9l2xakz7cgw6yfh83nh542pvc0g4rkq-geeqie-2.0.1/bin/.geeqie-wrapped
2276:Exif.Image.DateTime%d:%d:%d %d:%d:%dExit Geeqie Cache MaintenanceBackground cache maintenancebackground_cache_maintenancegtk-closeS_tartFolder:Select folderCreate sim. filescreate_sim_filesgtk-stopCreate sim. files recursivelyclick start to beginCreate thumbnailscreate_thumbnailsInclude subfoldersgtk-clearClearing thumbnails...Removing old thumbnails...standard_maintenanceGuideReferenceManagement.htmlInvalid folder%s --cache-maintenance "%s"running...normallargefail/geeqie-2.0.1Location: %sstoppedfailed to delete:%s
2438:ף�����Q������S㥛��$��?;�O��n�?333333�?�C�l���?�v��/�?�?�I
                                                              +��?j�t����I
                                                                          +�������Mb`�{�G�z����~j�t������Mb����x�&1�?�rh��|�?;�O��n�����Q����$���{�G�zt�;�O��n��!�rh����V-���?pixbuf_renderer_scrollpixbuf_renderer_get_tilespixbuf_renderer_set_tiles_sizepixbuf_renderer_set_tilespr_source_tile_newpixbuf_renderer_set_colorpixbuf_renderer_get_parentpixbuf_renderer_set_parent@�@@@���A`��"�?bX9���?�v��/�?�i�i@Geeqie 2.0.1tEXt::SoftwareError saving png file: %s
0

@ryantm would this make sense to implement in your upgrade script?


Added BatchedBridge to Podfile in Integration-Doc as it is required for #15049

// If your PR references an existing issue, please add the issue number below:
#15049
In order to get the integration-guide done with already existing iOS-Apps, a specific Pod is required called BatchedBridge.
See https://github.com/facebook/react-native/issues/15049#issuecomment-316115595

Thanks @itinance, CxxBridge have been fixed in the latest releases and I've fixed remaining ones in #268.


Size optimisation of std.datetime (saves 12KB)

Large switch statements have been replaced by data-driven array lookups to reduce the amount of code generated and also improve performance. Using DMD 2.056 on OSX x86 this cuts 12KB off of a Hello World program.
The motivation for this change is to try and reduce the size of small D programs as their large size is a common (and valid) complaint amongst newcomers.

That saves 12KB?! Well, the code is shorter (which is good) and passes the unit tests, so it looks fine to me, but I'm very surprised that it would reduce the size of the executable by that much. dmd's code generation for switch statements must suck as far as the amount of code generated goes.

Merged.

@jmdavis: About 7KB is due to http://d.puremagic.com/issues/show_bug.cgi?id=6767 but the other changes save large amounts as well.


Unsupported TF Select ops: AddV2, Mul, Pad

System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04):
TensorFlow installation (pip package):
TensorFlow library ( 2.5.0 ):

Problem
I have an ONNX model, which itself is originated from pytorch. I'm trying to convert from ONNX format to tensorflow lite format without using Select ops.
First, I convert to TF SavedModel via onnx-tensorflow package, then I convert to TFLite with basic API:
converter = tf.lite.TFLiteConverter.from_saved_model( name )
converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS]

I get the following errors:
...
<unknown>:0: note: loc("PartitionedCall"): called from
<unknown>:0: error: loc(callsite(callsite("onnx_tf_prefix_Add_65@__inference___call___373" at "PartitionedCall@__inference_signature_wrapper_435") at "PartitionedCall")): 'tf.AddV2' op is neither a custom op nor a flex op
<unknown>:0: note: loc("PartitionedCall"): called from
<unknown>:0: error: failed while converting: 'main':
Some ops are not supported by the native TFLite runtime, you can enable TF kernels fallback using TF Select. See instructions: https://www.tensorflow.org/lite/guide/ops_select
TF Select ops: AddV2, Mul, Pad
Details:
        tf.AddV2
        tf.AddV2 {device = ""}
        tf.Mul {device = ""}
        tf.Pad {device = ""}

I've also had problem with SoftMax operator, but I've solved the issue. It turned out, that TFLite version of softmax operator doesn't support axis parameter, so I removed it and now converter is able to use non-flex softmax.
All modifications I do on ONNX graph, before converting to Tensorflow
What could be wrong with other operators: AddV2, Mul, Pad ?
What I tried
I've noticed that tfl.mul docs don't tell anything about broadcasting compared to tf.mul. So my hypothesis was that non-flex tflite can multiply only tensors of the same shape, but can't multiply tensor by scalar. So I've replaced Constant with Shape -> Cast (to float32) -> ConstantOfShape operators, but I still get the same errors.
I've also tried to convert all tensors with datatype int64 to int32 - no success.
Any suggestions? What do I have to pay attention first, when I get such select ops issues?

Please consider using the Select TF op option. https://www.tensorflow.org/lite/guide/ops_select

If you can fix the input shapes of AddV2 and Mul operators or lower the dimensions, those math operators can be replaced with the TFLite operators.
If you can lower the input dimension of the Pad operator (input dim <= 4), the converter will put the TFLite Pad op.

If you can fix the input shapes of AddV2 and Mul operators or lower input dimensions regardless of broadcasting support (e.g., input dim <= 4), those math operators can be replaced with the TFLite operators.
If you can lower the input dimension of the Pad operator (input dim <= 4), the converter will put the TFLite Pad op.

Thanks for solution! I'll experiment and try to reshape tensor before and after AddV2 and Mul operator (probably next week).
I'll write here when I succeed.

So, I did the following things:

Made all inmput dimensions in ONNX graph fixed, that fixed AddV2 and Mul operators
Lowered dimension of input for Pad operator

And this helped me to get rid of flex operators


Restarted node flushes pusher queue

Summary
I had a node which was trying (and failing) to push a bunch of chunks to closest peers, possibly due to #1503 .  This node was retrying the pushes over and over again.  I restarted the node and saw the entire pending push queue dump to the first peer that was successfully connected.  I can only presume that the node had somehow different or better connections into the required destination neighborhood, but have no way to be certain.
Steps to reproduce
Build up a pusher retry queue in a node for whatever reason.  It may be #1503 or a bunch of non-responsive nodes causing "stream reset" or "context deadline exceeded", but for whatever reason, your node cannot deliver one or more chunks to its closest nodes.
Restart that node and you should see the entire queue of pending chunks be delivered through the first connected peer.
Expected behavior
If the chunks can be delivered after a restart, why aren't they able to be delivered before the restart?  Rather than continuously trying and failing the same set of 5 "closest" peers, should pusher retries retain the peers that were previously failed and try a different, or increasing, set of peers on subsequent push retries?
Actual behavior
Pusher tries over and over until the node restarts and then the chunks are delivered.
The full node --verbosity 5 log is at: https://pastebee.com/?f031416fcefd6082e5ae54a5c6d5e4a0eb139a9804f312cb2e84134c75301fe6
But here's the gist of it:
time="2021-03-26T08:33:37-04:00" level=info msg="version: 0.5.3-23baf60-dirty"
time="2021-03-26T08:33:37-04:00" level=warning msg="clef is not enabled; portability and security of your keys is sub optimal"
time="2021-03-26T08:33:38-04:00" level=info msg="using existing swarm network address: 978a4128246abb0283a440d21731f629e4cc59394decae2bb01679fcda879d6e"
time="2021-03-26T08:33:38-04:00" level=info msg="swarm public key 03faf2886ae088aba53ca7f8e6427842b9a2e5c2cfab0bafd71e05ca9e45137252"
time="2021-03-26T08:33:38-04:00" level=debug msg="using existing libp2p key"
time="2021-03-26T08:33:38-04:00" level=debug msg="using existing pss key"
time="2021-03-26T08:33:38-04:00" level=info msg="pss public key 02aeae9c39c66ed030e5c309fc1d1bd4c01b479c0c7cc1156662d7f24f07e5c22e"
time="2021-03-26T08:33:38-04:00" level=info msg="using ethereum address 4a096258e359ecfc3a2161a7be5ad147bbd0df49"
time="2021-03-26T08:33:38-04:00" level=info msg="debug api address: [::]:6060"
time="2021-03-26T08:33:38-04:00" level=info msg="using default factory address for chain id 5: f0277caffea72734853b834afc9892461ea18474"
time="2021-03-26T08:33:38-04:00" level=info msg="using existing chequebook f857237cbdcd01427d4d6eb610623a0bd0af35d3"
time="2021-03-26T08:33:39-04:00" level=debug msg="p2p address: /ip4/<IP_ADDRESS>/tcp/7070/p2p/16Uiu2HAmE15aiZMvXi3HV8TckP6BaYgNWeCxWwP8ywnqG4eYDJx4"
time="2021-03-26T08:33:39-04:00" level=info msg="database capacity: 5000000 chunks (approximately 19.5GB)"
time="2021-03-26T08:33:43-04:00" level=trace msg="pusher timer.C after -1 chunks in batch, 0 inflight"
time="2021-03-26T08:33:43-04:00" level=info msg="name resolver: no name resolution service provided"
time="2021-03-26T08:33:43-04:00" level=info msg="api address: [::]:8080"
time="2021-03-26T08:33:43-04:00" level=debug msg="pusher chunk 9467b36b72b85847410b896d3c3344194386ec7a08337f74006874e28dea33be err closest peer: no peer found"
time="2021-03-26T08:33:43-04:00" level=debug msg="pusher chunk 94655f56a7644395a6812a5c8344317df66d8dc8eb77a3210250b4a846c294f7 err closest peer: no peer found"
time="2021-03-26T08:33:43-04:00" level=debug msg="pusher chunk 9466463bd0a1d63ea29e94816caafc74bbc82065dc08b526556c431c9d7b480f err closest peer: no peer found"
time="2021-03-26T08:33:43-04:00" level=debug msg="pusher chunk 94665b315fc894f23e342cb950b6a302164afba2e7be677d8dd1845bb2d2c375 err closest peer: no peer found"
time="2021-03-26T08:33:43-04:00" level=debug msg="pusher chunk 94663b9e9de19e9bbb6617a363667ff6d3d677eaa09024a888d548af94cb45e8 err closest peer: no peer found"
time="2021-03-26T08:33:43-04:00" level=debug msg="pusher chunk 94658a7a71a1c5485277768a57c45258ea5738678e2a99c96bda4944d9c959db err closest peer: no peer found"
time="2021-03-26T08:33:43-04:00" level=debug msg="pusher chunk 94659adc7cce198ecc0de03ba051bf1fcd5409f3fb390e88b544b1b6237618a3 err closest peer: no peer found"
And it repeatedly runs through the entire pending queue with them all failing due to "no peer found" as it should.  A few connection attempts are made and failed, until:
time="2021-03-26T08:34:30-04:00" level=trace msg="handshake finished for peer (outbound) 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf"
time="2021-03-26T08:34:30-04:00" level=trace msg="received payment threshold announcement from peer 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf of<PHONE_NUMBER>0000"
time="2021-03-26T08:34:30-04:00" level=trace msg="initial swap handshake peer: 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf beneficiary: 76e62c6d6cd231e0cc29c023f647a6cb9bbaca5e"
time="2021-03-26T08:34:31-04:00" level=trace msg="sending payment threshold announcement to peer 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf of<PHONE_NUMBER>0000"
time="2021-03-26T08:34:31-04:00" level=debug msg="successfully connected to peer [Overlay: 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf, Underlay: /ip4/<IP_ADDRESS>/tcp/1934/p2p/16Uiu2HAmFrn8LSwUN3sU8uDTM2CMTD8dGaELQREWKFJYuxGQMGR5] (outbound)"
time="2021-03-26T08:34:31-04:00" level=info msg="successfully connected to peer 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf (outbound)"
time="2021-03-26T08:34:31-04:00" level=debug msg="kademlia:connected to peer: 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf old depth: 0 new depth: 0"
So, we're only connected to 13c76752769c97a03e29f78aa1f2accd6e1d613a22ef04bec4bfa173711f8ddf from our node of 978a4128246abb0283a440d21731f629e4cc59394decae2bb01679fcda879d6e
And the next time the pusher wakes up - BOOM!  - The entire pending queue is pushed through that freshly connected peer.  And from the 2 peer IDs and the chunk IDs, I don't even think he's closer than my node, so I effectively pushed the chunks further away from my neighborhood to get them (supposedly) back closer than me in my own neighborhood?  But I didn't know that because my own neighborhood depth was still zero because I was still building up my connected peers.
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94655f56a7644395a6812a5c8344317df66d8dc8eb77a3210250b4a846c294f7"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9467b36b72b85847410b896d3c3344194386ec7a08337f74006874e28dea33be"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94665b315fc894f23e342cb950b6a302164afba2e7be677d8dd1845bb2d2c375"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9466463bd0a1d63ea29e94816caafc74bbc82065dc08b526556c431c9d7b480f"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94658a7a71a1c5485277768a57c45258ea5738678e2a99c96bda4944d9c959db"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94663b9e9de19e9bbb6617a363667ff6d3d677eaa09024a888d548af94cb45e8"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94665f45cfcd2186913aaba023b391988bdefb218c15964b971aad4fac47e618"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94659adc7cce198ecc0de03ba051bf1fcd5409f3fb390e88b544b1b6237618a3"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9466a824f65ae6cf3d01c9a9ced77e57c55d1031d460a359cf71602b3b538e97"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94677eb60ff1e74742baef2040bbd66a3fa7aff8cee688f4acfe11a57d78a4c6"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9464dc569260b88eb32ab676b9b2faa305b3e22acc1f9139d4c8fb627f8b0f1d"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94653d198df7f67faa110b02e584abd1b1b2eebd4ab3a1721602381556a84a80"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9466c5d016c56f022a385473ee9b83f715349c5544a698bf5e14c95d35327e8c"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk<PHONE_NUMBER>a02043a4493002b4bd45e2cc19a006927bf2d69bfffffbdee6d1dc"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 946537b98aeafcc6eb026f89c0858f7b901b2f1aee73228c540edf30216798b3"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 946434a939af04a1beab97a898a6ab2fb42038260ee04122a8ba8c2fce1426b6"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 94659d75f223d180d61d1c7bec7fa3c52e2ffdebfc4c5b03d7c254ddf2e561d7"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk<PHONE_NUMBER>83dab68754ebc4f984d0847a6118e875ffa838511e5472440b073b"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9466902b07417b8d100e1dbec075d555099a8eacb15d73cf2c16ccf397e1ea01"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 819dfa503907a89a662f6776945850223328303b3586a390534721ddf49caf20"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9466e97d34b14d658cfc0765391cb6a77ccca92f87bd7099368d54f46067324d"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 8784b0d1facc686d26c17434d1a616853a0c7da915c8556d0b80182eb578e25a"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9466d757d467c061431fcde09694949b46a64aab0d60be3e1b719921a2a91342"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 8624949fc1efe878d5a7dea55b8c6faf38aea8876e7ee06b4f8ffdfd1cd1da53"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 8621f1b874ff9c18e7a3688873dc9ee2f3af0e16ac2e21feeab9eab8e64c0cd2"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 82879c527e5b973a1fe10683186c4365a8c46091aea57bbb903e61b00ce5e5e2"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 8286f0f048454cb3f5dae484241dcd888455243e8286abca2c2dbcba5f525d6d"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 97b3c7a859e2b1bba764fb1e32f6f357e85c53af9ff43fee622d7b78a2643d8f"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 828583d813afc5f8dde63797e9c2d1d73e1110bb0bfd6e5cc9015a28bc8b645e"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9464d4d5c21beec13d478bd61789bcc95a8b19fd0c957de366918ab517e5ad6e"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 8286dc546969787f53f9c9fba3af9af79cc44bcdfde73527581c77780fd636de"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 828039c8e2ff47415269b87578360c9983a210d7e7f7c6caed9b9eb2c5fabd79"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9719d87c145afb8cc7beaf2ba6321025988730488eb7952cbf5bb5c574eb8c25"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9708f47cca1b295bb08aa6f540e34a00edf80ac59ea5bcbbcc8cab834e9d2859"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 971e1b17795e7663853300c3a89351582e860b066b53c892f68850f80d4d4a78"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 9040c757de11c22b1d259db911e72cb4f86fb32fa53ed5b509b48af0e0ffb252"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 970c749d4b6df5134fbb2ec64b5a7823726bb9653843a320089bdf4d6269c735"
time="2021-03-26T08:34:35-04:00" level=debug msg="pusher pushed chunk 97b183c2f7822eacff139824ffbaadb3ccad37cda8c0cf97af1d11d916baed48"

Am I correct in assuming that this is not a bug on it's own, but it is an example of the retry logic in pusher being detrimental?

Actually, I've learned more about this since writing up this issue.  The actual problem lies in the interaction between the pusher, pushToClosest, and kademlia's ClosestPeer.
When the node was fully running, it had lots of connected peers and ClosestPeer always had more than 5 connected peers for every pending chunk that pushToClosest was given to exhaust the 5 retries causing a retry-able error to be returned to the pusher causing the infinite retries.
But immediately after the restart, there were no connected peers, which is fine because ClosestPeer returns topology.ErrNotFound which is still a retry-able error for the pusher.
But as soon as one peer is connected, ClosestPeer now returns topology.ErrWantSelf for every chunk where the retrying peer is closer than the single connected peer.  This error passes through pushToClosest and back to pusher who then invokes s.storer.Set(storage.ModeSetSync) which stops the retries and keeps the node in the localstore.
But these chunks are not really "close" to the node that has incorrectly decided to quit pushing and keep them.  Any subsequent retrieval requests are not likely to get to this node, and therefore those chunks will be effectively missing.
So it's not a problem that the pusher retry logic can fix, but it is caused by kademlia's ClosestPeer making a pre-mature return of topology.ErrWantSelf when it is still actively trying to build up the connectedPeers.
With the current implementation of pullsync, these chunks might eventually get out to where they belong in the swarm, but with the 0.6.0 changes to have pullsync only do the local neighborhood nodes, that recovery will be eliminated.
I have heard that there are also changes coming to pushsync, but since the puller has already removed these chunks from the pushindex, I can't see how such changes will recover them.
It seems that kademlia somehow needs to somehow detect that it is in a "startup" mode while actively building connectedPeers and attempting to increase the neighborhood depth and prevent ClosestPeer from prematurely returning topology.ErrWantSelf, but stick to topology.ErrNotFound for a while (seems arbitrary) or until it has determined that sufficient connections have been achieved (relative to the size of knownPeers and/or saturation?) or that the neighborhood depth has stabilized (whatever that means).  I'm hard-pressed to figure out something that works for both large and small swarms other than the consideration of connectedPeers vs knownPeers (1%?) or the depth stabilization (depth hasn't changed after N passes of manageC?).
But since this premature topology.ErrWantSelf also affects new chunks coming through via PushSync's handler, the fix needs to be in kademlia's ClosestPeer, and not just the pusher.  We don't want the node to prematurely conclude that it should keep a chunk when it is still new to the (changing) neighborhood.  Although new chunks coming through the handler might be covered by the "push to local neighborhood" for newly received chunks, and then hope that the single connected peer isn't also new and will properly forward the chunk?

Aha. Great detective work, and thanks for the writeup. This is indeed a problem and it will cause uploads to fail.
There are already two related issues:

https://github.com/ethersphere/bee/issues/1437 makes any node in the forward chain to validate if the receipt was signed by a node from the neighborhood. We can then reject/retry if we got a receipt that did not come from the neighborhood.
https://github.com/ethersphere/bee/issues/1243 defines the desire to differentiate between an aspiring full node and a full node, from the perspective of redundancy and being able to respond to forward requests. As I get now, it is not only that a syncing node can be delayed when responding to forward request, it can also misbehave.

I updated the title to be more explanatory

This issue is mentioned in https://github.com/ethersphere/bee/issues/1639, and supposed to be fixed by https://github.com/ethersphere/bee/issues/1685 and https://github.com/ethersphere/bee/issues/1685 https://github.com/ethersphere/bee/issues/1653 .
It would be amazing if you can validate if that is indeed the case for v0.6.0. If not, please reopen this issue. If it is fixed, I would also be happy to read it here!


listener not removed after component unmount

Listener is not removed when a component is unmounted, I get a warning because a listener is called on an unmounted component.
In your code
https://github.com/yamill/react-native-orientation/blob/a7e5707e098ed9cabe714c8a5817b7b6608ebd65/index.js#L34-L46
you maintain a unneeded listeners array, but more importantly you forgot to do DeviceEventEmitter.removeListener with the good params or call the cb returned by DeviceEventEmitter.addListener with cb.remove()
please see https://github.com/inProgress-team/react-native-orientation-controller/blob/master/index.android.js#L29-L40 and https://github.com/inProgress-team/react-native-orientation-controller#removelistenercallback for a good implementation.
I now use react-native-orientation-controller to fix this issue.

Hi, I am having the same issue,
The problem is that they are using the callbacks as keys.
So when there are multiple components with the same callback function (the key), the DeviceEventEmitter listener references are overwritten on the same key.
This is the function where they add the listeners
  addOrientationListener(cb) {
     listeners[cb] = DeviceEventEmitter.addListener(orientationDidChangeEvent,
      (body) => {
        cb(body.orientation);
      });
  },

For example, with the next component
//Other imports here
import Orientation from 'react-native-orientation';

export default class MyComponent extends Component {
    constructor() {
        super();
        this._orientationCallback = this._orientationCallback.bind(this);
    }

    componentWillMount() {
        Orientation.addOrientationListener(this._orientationCallback,);
    }

    componentWillUnmount() {
        Orientation.removeOrientationListener(this._orientationDidChange);
    }

    _orientationCallback(orientation) {
        this.setState({orientation});
    }

    render() {
        return (
            <View>
                <Text>{'Hi'}</Text>
            </View>
        );
    }
}

If I create three instances of this component, and I unmount both, the only listener removed will be only for the first unmounted component.
The other components will get listeners[cb] = null because the reference is lost.
We need a fix for this please!

Why would you create 3 instances of the same View in your application? Not entirely sure of the issue here. If you believe it stands, we accept a PR and it will be reviewed.

@andrerfneves
disregard this, I suspended this orientation feature for a while, and I took it back today.
I think there was an issue with the old structure of the component, which is now improved.
I installed the plugin again, and the listener seems to be removed correctly!
I'll let you know if I have any trouble!
thanks!

Awesome! @facuescobar glad it's working. Closing this for now.


Deep update syntax/API

Currently, AFAICT, there is no convenient way to do deep updates such as setting a value in a List which is part of a Record (am I wrong?). For example:
var Foo = Immutable.Record({a: null});
var foo = new Foo({a: Immutable.List([42]));
foo = foo.set('a', foo.get('a').push(17));

This is awkward to say the least, and gets worse with deeper structures. Note that setIn() doesn't help here.
I would be great to have something like the update() method in the react's immutability helpers.

It's hard to tell from the docs, but Record has all the operations expected from a Map too, so you can write something like:
foo.updateIn('a', a => a.push(17))

or
foo.merge({ a: foo.a.push(17)})

Also, you don't need .get('a') for records, you can do foo.a directly.

@santiagoaguiar thanks, that's great! One thing I still can't find is a way to do a deep delete based on equality, in one step. I find myself doing a lot of this kind of thing:
let index = map.getIn([a,b,c]).indexOf(val);
map.deleteIn([a,b,c,index]);

Is there a better way to do that?

Agree, would love to have a delete on List by equality :). But, I think you only get it on Set collections.
Maybe is not your case, but I think one common pattern (on redux at least) is to avoid deleting the item and instead set a deleted flag, the main benefit being not having to remove the element id on every place where it has been added, and always filter by deleted instead. It feels right with the idea of flattening your state (which was why https://github.com/gaearon/normalizr was created).

I am indeed using Redux. Thanks for the suggestion.


[HW]

Name:
Email<EMAIL_ADDRESS>Linkedin Profile: <www.linkedin.com/in/jasleen-singh-81549b43>
Attach the homework screenshots below for both step II and step III:

Looks great Jasleen, thank you. Here's your badge -> https://api.badgr.io/public/assertions/xX8kuhF8Rtq5GIyvXw22MA?identity__email=jasleen3046%40gmail.com


Use newer extension syntax in example for Kotlin DSL and add in expli…

…citly needed cast for profile configuration
The Action {} cast is unforunately needed right now for plugins written in Kotlin.
issue https://github.com/gradle/kotlin-dsl/issues/522
Kotlin issue https://youtrack.jetbrains.com/issue/KT-20635

Ran into this in latest Gradle 4.3

I need badly a gradle script kotlin project so I can stay up-to-date with their changes ... In the long term maintaining both kotlin and groovy gradle scripts in the way to go. So we have both ways tested ...


Failed to build due to mismatched types

Hi ... I was attempt to walk through lightbeam's example when I failed to compile:

I compiled with: cargo build --example test
This is a fresh checkout. Are there some requirements I am unaware of for building or is this a real issue?

You can try using an older nightly eg from the date of the latest commit. It seema dynasm needs to be updated for the latest nightly.

Ugh, I've been wanting to get rid of dynasm for ages, the only reason I still have it is because getting rid of it would essentially mean writing my own assembler and I want to get all the Wasm spec tests passing first. I'll look into it.

The most recent nightly that appears to work is the one from 2018-02-01. Run rustup override set nightly-2018-02-01 and it should work. The ideal solution is for this to be fixed in dynasm but I absolutely do not want to get into that right now

@bjorn3 @Vurich .. Hi, thanks for the suggestion. Dynasm has had a couple of releases since the version that lightbeam is pulling in. Dynasm is at 0.3.1 while lightbeam requests 0.2.3. However while the 0.3.1 Dynasm lib compiles, it in fact seems to not register properly with rust when I try to compile their example. I did try nightly from 2018-02-01 (actually looks like 2018-01-31) but using that compiler leads to other errors warning of experimental features in cranelift-entity such as:
crate in paths is experimental
inclusive range syntax is experimental
Is the status that lightbeam simply doesn't work right now because of it's dependency on dynasm which doesn't compile with the latest rustc toolchain, but lightbeam also doesn't work with the older tool chain that does compile dynasm because of its simultaneous dependency on cranelift which doesn't compile with that older rustc tool chain?

The 0.3.x versions of dynasm, which use a proc macro instead of a plugin, appear to no longer work when put in macros. This is really unfortunate because there's basically no other way to have any amount of abstraction with dynasm - you can't have an instruction determined by a runtime value, for example. This unfortunately means that we'll never compile on the latest nightly until dynasm is replaced.

Marking as wontfix but I'm going to leave this open until we replace dynasm entirely

Hi @Vurich ... I see. Thanks for the explanation. I was hoping to experiment with lightbeam as a quick and simple code generator for wasm but I guess I will try cranelift/faerie instead. Not quite certain what it is doing, I was going to step through an example to understand how lightbeam was using dynasm. What will you use to replace dynasm?

@jlb6740 My intention is to just write my own assembler, I wish that I didn't have to but there's no generic assembler that allows for abstraction in Rust right now - because dynasm's only interface is a macro there's no good way to write code that uses it in an extensible, correct and ergonomic way. Your only option for code-sharing is macros and copy-pasting code. Lightbeam is currently not passing all the spec tests so that work will have to wait until they're passing, unfortunately.

@jlb6740 Update: Turns out the problem with dynasm is that I was using identin my macro_rules argument and the macro was looking for tt, the former captured the element and meant it couldn't be matched as a tt. I still want to replace dynasm eventually but this means that we can continue using it for now and it works on the latest nightly (the only remaining nightly feature needed is proc_macro_hygiene)


feat(trim-paths): set env CARGO_TRIM_PATHS for build scripts

What does this PR try to resolve?
Set profile options as environment variable CARGO_TRIM_PATHS for build scripts.
As a follow up of https://github.com/rust-lang/cargo/pull/12625.
How should we test and review this PR?
Docs and test should be pretty straightforward.
Additional information

RFC: rust-lang/rfcs#3127
Tracking issue: rust-lang/cargo#12137

spurious network error seems like?

Error: failed to read index metadata for crate 'cargo-credential'
Caused by:
0: error sending request for url (https://index.crates.io/ca/rg/cargo-credential): connection error: connection reset
1: connection error: connection reset
2: connection reset

https://github.com/rust-lang/cargo/actions/runs/6706964313/job/18224456440?pr=12900#step:5:552
@bors retry

@bors r=epage

:pushpin: Commit<PHONE_NUMBER>6be0db340683ad546a7b9d60e083d7 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit<PHONE_NUMBER>6be0db340683ad546a7b9d60e083d7 with merge 05cce738eb2bf731092b495d83dd21a41e660f36...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 05cce738eb2bf731092b495d83dd21a41e660f36 to master...


docker-compose up --- error

hi, I run run docker-compose up -d to start the container, finally, got the error:
..........................................................................
...........................................................................

Step 11/11 : ENTRYPOINT ["/custom-run.sh"]
 ---> Running in 3efaa137c276
Removing intermediate container 3efaa137c276
 ---> 3e677487c272
Successfully built 3e677487c272
Successfully tagged grafana-mongodb-docker_prod:latest
WARNING: Image for service prod was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating grafana-mongodb-docker_prod_1 ...
Creating grafana-mongodb-docker_prod_1 ... error

ERROR: for grafana-mongodb-docker_prod_1  Cannot start service prod: driver failed programming external connectivity on endpoint grafana-mongodb-docker_prod_1 (dbf0061c66e3d06739a3e7d7212b021cca0ce2b8c6ce480d2833d3af0f458244): Bind for <IP_ADDRESS>:3000 failed: port is already allocated

ERROR: for prod  Cannot start service prod: driver failed programming external connectivity on endpoint grafana-mongodb-docker_prod_1 (dbf0061c66e3d06739a3e7d7212b021cca0ce2b8c6ce480d2833d3af0f458244): Bind for <IP_ADDRESS>:3000 failed: port is already allocated
ERROR: Encountered errors while bringing up the project.

the 3000 port is using by Grafana default.
How to solve this, thanks.

It seems like you have something already running on port 3000, you can specify another port for the container in the ports section of docker-compose.yml.
You can find more info about port bindings for docker compose in the official documentation: https://docs.docker.com/compose/networking/
I'll close this issue for now as it's not related to the container itself.

@ajeje93 Thanks. After I changed the port no to 3030:3030 from 3000:3000, the container of  grafana-mongodb-docker_prod_1 is running.
But in Grafana dashboard, I cannot find the new Data Source, please help me again.

If you changed the port to 3030 you should access Grafana from that port. The container has both Grafana and the data source plugin inside.
I think you should change the port to something like 3030:3000 to map the port 3000 of the container (that is the Grafana port inside the container) to port 3030 of your PC, the access Grafana from http://localhost:3030.

@ajeje93 thanks. Got it!
the Grafana on http://localhost:3030.
and the data source on http://localhost:3000.


Update license headers

Similar to https://github.com/dapr/go-sdk/issues/231
Update license headers in files to meet CNCF guidelines.

Also enforce using eslint: https://www.npmjs.com/package/eslint-plugin-header

/assign


feat: disable id-length rules

Hi 👋
I saw in the last pull request of @antoine-coulon that he disables the rule.
I confess that I'd like to disable it also a lot of time.
So I'd like to discuss it with the team.

Ok for me. If someone want to contribute to this, then let's go :)

@all-contributors please add @tony-go for code


hello_world example is broken

After updating glium to 0.22 and glutin to 0.17 in #141, everything seems broken on my system.
Here is what the hello_world look like on b8baa82 when I compile it:

My system is currently Ubuntu 18.04 with rustc 1.28.0 and gcc 7.3.0.
I will try to investigate and see if the same issue occurs on other systems.

Fixed by #143 . I close.


[JOSS review] Tests

https://github.com/openjournals/joss-reviews/issues/6734
JOSS requires:

Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?

Do you have any tests implemented? I can't seem to find them.

@DorsanL unit tests are a best practice when creating packages and help detect if code is broken when changes are made. So, I would recommend that you add some tests.

I agree that unit tests are needed. The tests don't need to be automated; manual steps to run them are fine. You can have a look at any recent JOSS papers for suggestions, e.g. pyheatdemand.

Entry points for test have been added.
https://github.com/IPESE/REHO/commit/4a63b03aec4f85ae097582e4bd1ab2c3b5d03e0c
The "Checking proper installation" section of the documentation has been updated accordingly.
https://reho.readthedocs.io/en/main/sections/5_Getting_started.html#checking-proper-installation

I still can't seem to find any tests to verify the functionality and methods in the package, e.g. assertion and exception testing. The tests you currently have only seem to check whether the imports work and if the scripts manage to execute. (Please correct me if I'm wrong.)
The pyheatdemand package I linked in my earlier comment has these tests for example: https://github.com/AlexanderJuestel/pyheatdemand/blob/main/test/test_processing.py.

I started implementing some functionality tests with pytest (https://github.com/IPESE/REHO/commit/fda9b0ef9b6ff29f01211cc0b6a6e6cb66a8eca9). This is only a draft, I will extend them in the coming days.

A folder reho/test/ is now part of the package, containing the following files and functionality tests:

test_import.py verifies the import of the different REHO modules
test_clustering.py verifies the behavior of Clustering class
test_infrastructure.py verifies the behavior of Infrastructure class
test_run.py ensures that a classic optimisation works as intended (and thereby that the SubProblem, MasterProblem and REHO classes work properly)
test_plot.py (calls test_run to generate results) and verifies various plotting functions
test_examples.py runs each of the examples available in scripts/examples/ (and downloads them locally beforehand if they have not been cloned)

Developments have been pushed in https://github.com/IPESE/REHO/commit/254a8bc1476dc9250208d94b6446b4953017c783


Feature: reject invalid recipient emails

"Real" SMTP servers will reject invalid recipient emails, but you can send an email to 'test' with Mailhog and it's accepted. I think it will be a much more useful testing platform if it behaves like the real world and throws a delivery error on invalid email address or empty recipient.

Hi,
you're mistaken - "test" is a valid mail-address!
It's the local part of the address and addresses always a local User on the receiving Server. Because of MailHog doesn't know anything about local User it should accept such kind of Mails.
You can easily proof it with a Linux-PC

useradd atestuser
nc <IP_ADDRESS> 25 <<EOF

EHLO localhost.localdomain
MAIL<EMAIL_ADDRESS>RCPT TO:atestuser
data
Subject: Testmail
This is a Test!
.
EOF

cat /var/spool/mail/atestuser

Best Regards
Matthias

@swrobel Can you paste a SMTP session which demonstrates your expected result? (e.g. https://docs.microsoft.com/en-us/exchange/mail-flow/test-smtp-with-telnet?view=exchserver-2019)

Hi @swrobel, I believe you are talking about validate e-mail address based on all RFCs.
Based on this assumption, a regular expression can be used to validate e-mails but this will introduce a new challenge/problem described here. In summary, any regular expression will not be UTF-8 safe (think on people on Japan for instance). The regular expression needs to validate user/domains in all possible language.
Or, maybe, instead of "validation", just do some small verification like non empty value and presence of "@" signal (but then the test made by @mkrsn will be broken).

Thanks for the feedback, everyone. I now realize that the issue of recipient validation is much more complex and non-standard than I imagined, rather than being a simple spec that all SMTP servers could follow. I'm going to close this out.

@swrobel Thanks for your feedback and suggestion.


906: deletion of Annotation also removes it from AssetGroupSightings

annot.delete() also removes (references to) annotation from AssetGroupSighting(s) as applicable.

I guess I'm supposed to review it, although I got assigned to it, lol

I guess I'm supposed to review it, although I got assigned to it, lol

:joy:  oops!  yes, i meant to assign you as reviewer.  fixed!


date picker

This seems to be the only outstanding open date picker issue. Just leaving a heads up comment that this should be closed.


Check this error building Dockerfile

What I did
Test build Dockerfile
What I expected to happen
Errorless success!
What happened instead
ERROR: Cannot install -r /octodns/requirements.txt (line 5) and docutils==0.16 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

Additional info
I'm pretty sure that's come up before and has been mostly ignore-able.
Spend some time catching up versions and digging into any errors in the process.

This error didn't occur when I bumped versions in #27 🤷


Pub/Sub

This is pretty important.

Going to take a crack at getting this built. Will make pull request when it's done.


How to serialize object make the output the same as SerializeAsString() method of C++

In C++, I can call protobuf_object.SerializeAsString().
Which method is the same as above in nodejs?
The following code is not correct.
            let out = pbObj.serializeBinary();
            let serializeStr = Buffer.from(out).toString();

What are you trying to do with the output? Fundamentally, serializeBinary is giving you a Uint8Array, which Buffer.from seems ok with. However, Buffer.toString assumes utf8 encoding, which you can't guarantee.
I'm not particularly experience with node, but at a glance I think Buffer/Uint8Array in this circumstance is roughly the same as SerializeAsString's produced std::string (i.e. bag of bits).
If you're trying to pass this off to some API that truly needs a string, then I think you need to Base64 encode.

I change proto definition
bytes xxx
to
string xxx
then everything is ok.
I think there is some bug while use bytes for nodejs.

The problem is utf8 encoding as dibenede said. When you change your type to
string that will get utf8 encoded when you call serializeBinary(), so when
you wrap it in a buffer and call toString that will be reversed.
See
https://nodejs.org/api/buffer.html#buftostringencoding-start-end
What are you actually trying to do?  Why do you need a string?
On Thu, Mar 23, 2023 at 9:44 PM DinoStray @.***> wrote:

I change proto definition
bytes xxx
to
string xxx
then everything is ok.
I think there is some bug while use bytes for nodejs.
—
Reply to this email directly, view it on GitHub
https://github.com/protocolbuffers/protobuf-javascript/issues/167#issuecomment-1482242001,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABTJXHMHLV3RWS6QODDXC3W5URENANCNFSM6AAAAAAWD3CKAQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


BRS-322 and BRS-323: Convert A&R to use SAM

Jira Ticket:
BRS-322 and BRS-323
Jira Ticket URL:
#322
#323
Description:

Initial changes to convert A&R to use SAM (adding layers and functions)
Updates to deploy_dev.yaml workflow

New and improved branch here: https://github.com/bcgov/bcparks-ar-api/pull/340


Python Post-processing breaks non-canvas compliant layouts

Wire width in the capacitor are not same as used in the transistors; this is breaking the flow

Another issue is that the capacitor shape is getting changed in the python gds.

Post-processing for resistors and capacitors is creating issues.

Unsure of whether this is still an issue. Will follow up.

Lack of test case.


Add #each to ConfigView

Closes #705
I actually wrote a little dinky test for this in test_compiler_dsl.rb:
  def test_config_iteration
    hash = { :key_one => 1, :key_two => 2}
    @config = Nanoc::ConfigView.new(hash, nil)
    @config.each do |k, v|
      puts k, v
    end
  end

It works, but because no other ConfigView syntaxes are tested (and the fact that STDOUT is muted) I decided not to include it. I could if there's a better way to work this.

Oh, the lack of unit tests for ConfigView is an oversight on my part. I’ll fix in a future PR, but for now, I’m merging this!

So apparently there are ConfigView tests—except that they’re confusingly in spec/nanoc/base/views/config_spec.rb rather than …/config_view_spec.rb. So I renamed the files (f0cdb83) and added a test (aacdc00d9423cf487cb57f7e249c13b3ce967a86).


Incorrect link to the License chooser page

There's a typo for the link to the license chooser at Creative Commons Wiki:
https://wiki.creativecommons.org/wiki/Copyright_and_CC_for_grant_recipients#Step_3:_Select_Your_License
chose > choose

Thanks for reporting this. It's been fixed.


Develop a uniform way of the configuration system

Currently, the configuration of the system mostly relies onParams.js. However, there are instances where some parameters are defined in the code and the current state of the config file is confusing. Thus, this issue addresses the need for the development of a unified way of creating a config file for the system. As documented in users' stories, the system is a multipurpose system. Thus, it is essential to provide users with an easy and fast manner of parametrising the system according to their needs.
ToDo

[x] Review the existing configuration structure and identify inconsistencies or redundancies.
[x] Define a clear set of parameters that can be customized through the configuration file.
[x] Test the new configuration system thoroughly to verify its effectiveness and ease of use.
[x] Provide clear documentation and guidelines on how to utilize the configuration file for users' convenience.
[x] divide the entry point form app.js

I created evo-poster.config.jsto replace Param.js


Spotify Playlist

What went wrong?
Raspberry Pi
Spotify Playlist: https://open.spotify.com/playlist/1L0vaT3y0xnAGQ4ZpXORnH?si=f44a65061f534f01
ERROR: Sign in to confirm your age
This video may be inappropriate for some users.
How do we reproduce this?
!play https://open.spotify.com/playlist/1L0vaT3y0xnAGQ4ZpXORnH?si=f44a65061f534f01
Which version of the bot are you using?
No response
Which operating system are you using?
Other
Just checking...

[X] I have confirmed that my issue has not already been reported.
[X] I am using Python 3.8 or higher.
[X] I have updated my Python dependencies.

Since downloading songs from Spotify directly is against their ToS, we search for the song on youtube. If youtube now decides you have to log in, there's not much we can do.


Where is Node.setTransform()?

Hello,
What has happened to Node: setTransform() method?
I tried to replace all calls to Node: getAttributes().setTransform() but it did not have any effect.

GAHH! I truly hoped no one was using it. Working on shape intersections ( line to arc, etc ), and shape collisions, and heirarchical bounding boxes, H/V trees, etc.  The problem with setTransform() is that you could set a transform that is "non-affine", technically means that it doesn't follow the rules of http://en.wikipedia.org/wiki/Affine_transformation , which ALWAYS preserve that lines are still "parallel", as are planes and other geometry are well known. Next up in that we KNOW the order in which we apply x, y, rotation, scale, and shear. knowing these things allows us to then re-transform the intersections or collisions properly in affine space. With setTransform(), we don't really know how you arrived at the numbers and can't de-compose the order of operations. If you absolutely need setTransform() and CAN'T do it through a shape set x, y, rotation, scale, etc... then I COULD put it back, we'd just have to mark the shape outside the possibility of operations for intersections, collisions, etc...


HTTPS Leaking like crazy

The issue is the way you implementet https with letsencrypt, you forgot to ad a default_server for the https, so right now if you only got one https site every vhost you got on the server called true https will end up pointing on the one site that got https enabled.
This is actually inflicting harm on SEO since they popup on google search results, please fix this azap, this is a major concerne to be honest.

Are you trying that if you only have 1 enabled to use HTTPS and you then visit the another site on the server that does not use HTTPS, it redirects to the HTTPS site?
Am I understanding you correctly?

yes thats what im saying :) and that is a huge flaw in the configuration of Nginx.

To me that's a normal behaviour of any server.
Sent by mobile
On 10 Apr 2016 07:20, "jacobmmp"<EMAIL_ADDRESS>wrote:

yes thats what im saying :) and that is a huge flaw in the configuration
of Nginx.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/EasyEngine/easyengine/issues/698#issuecomment-207930273

The normal behaviour would be it to show the Nginx Page thats show as default when you call ex the ip or a domain thats pointing on the server not having a vhost.

The normal behaviour depends by the server settings really. If there is no
vhost, the server would not even respond to either HTTP or HTTPS request.
On 10 April 2016 at 09:58, jacobmmp<EMAIL_ADDRESS>wrote:

The normal behaviour would be it to show the Nginx Page thats show as
default when you call ex the ip or a domain thats pointing on the server
not having a vhost.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/EasyEngine/easyengine/issues/698#issuecomment-207947970

Still the standart config should make sure HTTPS for the server got a default so you dont get leaky https all over the place.


admin - products management

PRODUCT MANAGEMENT
...create and edit products with name, description, price and one or more photos, so that visitors can see the latest info on what we have to offer
...create categories for items, so that users can continue to have useful filters as our inventory grows in variety
...add/remove categories from items, so that users will see them when they refine their searches
Acceptance Criteria: items must have multiple categories
...manage the availability of a product, so that users will know whether or not they can purchase that product
Acceptance Criteria: If a product is no longer available, users will not see it while browsing, but they can view the product detail page if they've ordered it previously or have a direct link. On that product detail page, it should say "Currently Unavailable"


Translation Updates

This PR is generated by TPA.

Translation Process Automation generated line (DO NOT EDIT): [app/translations/webrtc-devices/de.json,app/translations/webrtc-devices/es.json,app/translations/webrtc-devices/fr.json,app/translations/webrtc-devices/it.json,app/translations/webrtc-devices/ja.json,app/translations/webrtc-devices/ko.json,app/translations/webrtc-devices/nl.json,app/translations/webrtc-devices/pl.json,app/translations/webrtc-devices/pt-br.json,app/translations/webrtc-devices/sv.json,app/translations/webrtc-devices/tr.json,app/translations/webrtc-devices/zh-cn.json]

This is a real PR. Like PR for ember-webrtc-troubleshoot yesterday, it appears that Transifex changes spacing (indentation). Otherwise it looks okay to me. Please merge this if you do not see any issues. Thanks!


Application number in App Settings should be at the bottom of the screen; content should not scroll under it

See screenshot from iPhone SE:
The last two items in the table scroll under the application number, make it feel like there is a visual bug, and covers the need to scroll in one remaining row in the table.  The user needs to scroll to reveal a remaining row in the table.

Done in https://github.com/project-vagabond/covid-green-app/pull/283 should be fixed in next build


chore: changes dev env to stage by default and fixes readme

Codecov Report

Merging #32 (3f854bd) into master (1af2c5a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 3f854bd differs from pull request most recent head a136626. Consider uploading reports for the commit a136626 to get more accurate results

@@          Coverage Diff           @@
##           master     #32   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          34      34
  Lines         498     498
  Branches      164     164
======================================
  Misses        451     451
  Partials       47      47

Continue to review full report at Codecov.

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


Unable to choose images on landing page, under content types on the search bar

Description
While selecting between all content, images, and audio. The selector does not highlight images, when hovered over it.
Reproduction
Please refer to the screen recording
[Screen capture] (https://drive.google.com/file/d/1V14ApXypuihar8FZg37zW79ln4AajHwL/view?usp=sharing)
Expectation
The image option should be highlighted, when the cursor hover right over it.
Screenshots
[Screen Capture] (https://drive.google.com/file/d/1V14ApXypuihar8FZg37zW79ln4AajHwL/view?usp=sharing) - attaching for your reference
Environment

Device: Laptops, Desktops
OS: Windows 10
Browser: Safari, Firefox

Tried to dig into this. Found out that the issue is related to z-index for <a> tag for the site logo.
On a screen resolution greater than 1024px when the logo and images element are stacked side by side - opening the content-type dropdown puts it over the logo.
Trying to hover over the Images button in the popover menu does not allow you to select and click it effectively due to he z-index value of the site logo anchor tag.
Please check the attached screenshot for reference:

Tried to dig into this. Found out that the issue is related to z-index for <a> tag for the site logo.
On a screen resolution greater than 1024px when the logo and images element are stacked side by side - opening the content-type dropdown puts it over the logo.
Trying to hover over the Images button in the popover menu does not allow you to select and click it effectively due to the z-index value of the site logo anchor tag.
Please check the attached screenshot for reference:

Here's an additional screenshot that makes the z-index issue quite obvious:

This issue can be solved by removing z-10 class here:
https://github.com/WordPress/openverse-frontend/blob/23b686270a5c131b7feb69dc6df683c221d81ce7/src/pages/index.vue#L18
Is there a reason to set the z-index on the NuxtLink here?