text:
[CROSS TEAM] - Migrate all non-production instances to use Okta Preview account.

Right now, the same Okta account is being used for localdev, staging and production. SimpleReport has created a specific "Okta Preview" account for doing all non-production activities.
High level tasks:

[x] 1. Create accounts for each member on our team on the Preview Okta account. (This requires email addresses.)

[x] Do this in slack for privacy and as a way to verify who should get access.
[x] Okta has bulk account adding feature. Chris to reach out in slack

[x] 2. Identify what okta data needs to change to switch over (urls, account numbers, etc).

[x] Otka URL: https://hhs-prime.oktapreview.com
[x] Okta Client ID: [not-secret but don't want to trigger github's secret detector]
[x] Okta "scope"?

[ ] 3. Identify all code areas that touch Okta and need to be changed

[x] react-app (url, clientid)
[x] Prime CLI?
[ ] Azure Vault key-stores values [⚠ these keys do not contain secrets but they exist, are they used]. Delete for staging and see if anything breaks?
[ ] ⚠Server EmailEngineFunction uses okta. Is sending email enabled on staging (subject line: "ReportStream Daily Email")?
[ ] Function app config stores url
[x] API authentication (Bearer) verification
[ ] Unit tests CI/CD? (Any test accounts on okta to be copied over to oktapreview?)
Didn't see any okta test accounts, but there are so many other accounts, it's hard to spot them.
[ ] ⚠ Server-side SubmissionFunctionTests.kt uses Bearer fdafads?
[x] Deployment processes?
[x] CSP header needs to allow hhs-prime.oktapreview.com on staging
[x] Okta signin page have a different image/temp message to alert users they are using Preview.
[x] Update onboarding documentation and any build instruction as needed. (Getting Started doc)

[x] 4. Identify people who are experts that need to be involved.

@TomNUSDS
@kevinhaube
@cwinters-usds

[x] 5. Migrate over okta data from production to preview (orgs, users, etc). Make sure everything is set up.
Main Groups:

[x] DHSender_all-in-one-health-ca, DHignore, DHPrimeAdmins, DHSender_test-not-in-database
[x] Single code branch for all changes server/client/cli.

[x] 6. Tests:

[x] React-client login/logout works
[x] Server-side testSmoke
[x] Server-side testEnd2End
[x] Server-side  ./prime test
[x] ./prime login --env=staging
[x] ./prime login --env=prod
[x] ./prime login --env=local
[ ] ⚠ ./prime login --env=test (is test supposed to be working?)

[ ] 7. Create a rollover schedule/plan to switch staging to use.

[x] Bulk add users (Engineers, Design, ?) Production has too many users to bring them all over.
[x] Decide which Organizations should be ported over and do those.
Step 5 did the four main orgs, we can move over more as we need them.
[x] Add some banner warning to React client?
[x] Verify Bearer is for the right server? (Rejected as too complicated)

[ ] 8. Post successful migration

[ ] Audit/remove/lower access to Okta production to a smaller set of folks.
[ ] Remove Okta Prime (test) app from production.
[ ] Any approve urls that may have snuck into Okta Prime app
[ ] Verify Trusted Origin in app
[ ] Remove unused Okta Trusted Origins admin/access/api/trusted_origins
[ ] Verify Security -> API list admin/oauth2/as
[ ] Remove our own members from groups like all_in-one
[ ] CSP header remove https://hhs-prime.okta.com

@MauriceReeves-usds See items from list marked with ⚠ ... (e.g. do we ever send mail from staging)?

@TomNUSDS are we clear to Close this?

@bgantick I think we can close this issue. Item 8 is going to be done as part of moving to a separate account I assume.

authors: TomNUSDS kevinhaube


text:
Website/Content Strategy Development

Problem statement
As users increasingly rely on the site for their work with ReportStream, we need a comprehensive strategy that will guide content and design work on needed updates and new additions. With an eye on the goals of ReportStream being pandemic-ready, user-centered, and eventually owned by the CDC, this strategy will also support scalable, sustainable, transferable, and user-centered content throughout the RS experience
Approach

My approach prioritizes stakeholder involvement for alignment, user knowledge, and ownership.
Work is planned around phases that answer the following questions: where are we, what are our users' needs, are we meeting them, and what needs to change to better meet them?
A robust discovery phase leads to more effective and efficient planning and execution.
It will take a holistic view of the web experience, rather than narrowing in on one user or feature.
This approach takes a content-first design mindset in focusing on implications of these questions on content that will set a foundation for further design work.
It will stay agile with the goal of moving quickly while not sacrificing being thorough and being flexible about how we are answering those primary questions.
Activities current planned and the desired outcomes are details more thoroughly in the Mural linked below.

Assumptions

We have access to SMEs and stakeholders for their feedback and engagement throughout the process.
This work is a priority feeding into the goal of being user-centered.
These activities will gradually influence smaller pieces of work that will happen concurrently throughout the quarter.
An implementation plan will be able to be completed for application next quarter.

Out of scope

More than one or two hours of research engagement with external users
Content considerations outside of what is on/will be on the website (e.g. emails)
Specific visual design decisions

Dependencies & risks

Engagement availability from necessary stakeholders

Open questions

CDC stakeholders/future owners to involve in the process for foundation of future ownership

What you need to know

Mural of general work roadmap/misc notes
#7999 feeds into this work
...

Definition of done/Acceptance criteria

[ ] Work is planned around answering the questions:

Where are we?

What are our users' needs?

Are we meeting them?

What needs to change to better meet them?

[ ] Artifacts reflecting the findings have been created and shared with the wider team

[ ] Action plan created based on answers to the above questions.

To do

[ ] ...

@lizzieamanning @chris-kuryak I'll begin adding tickets to this for this sprint.

@audreykwr Curious if you'd find value in adding any of the categories below:

Approach
Assumptions
Out of scope
Dependencies & risks
Open questions
Links and resources
Definition of done

I think some may be covered:

I think I have links that are relevant at the moment in there, but I'll try to add as more documentation is created along the way.
The broad definition of done seems like the ACs to me, but maybe those are too vague?
Would approach be adding some more details to planned activities? Or let me know more about what you're thinking for that one.
Assumptions, scope, dependencies are good to think about, so I can add those when I can as a start

@audreykwr I like it!
I see you two are discussing perhaps a bigger question of "what info is required to be in an epic." Happy take that to a verbal forum for quicker disposition if easier, as we as a team have not defined hard guardrails yet.
We will keep this epic in the "New" column until you have finished putting all of the necessary issues into it.
Regarding Lizzie's comments above, I agree with those bullets and also feel like Acceptance Criteria should be a definition of "done". However, I would also say that the epic may not need Acceptance Criteria as the issues should have all of the AC's to describe "done". So happy to chat this out with y'all at your convenience.

@lizzieamanning @chris-kuryak added some things. Let me know what you think or what could be added/clarified.

Looks good to me @audreykwr !
The details (above the basics) of what Design wants to include is up to y'all.
Also, it appears that the Synthesis ticket could still use some work.

All issues complete.

source: gharchive/issue

authors: audreykwr chris-kuryak lizzieamanning

repo: CDCgov/prime-reportstream

license_type: permissive

license_source: github-api


text:
16394 add ack functionality

This PR adds ACK functionality to the waters and report submission endpoints.
Test Steps:

Run ReportStream
Submit the following HL7. Ensure the content type header has been specified as "application/hl7-v2"

MSH|^~\&|Epic|Hospital|LIMS|StatePHL|20241003000000||ORM^O01^ORM_O01|4AFA57FE-D41D-4631-9500-286AAAF797E4|T|2.5.1|||AL|NE

The response body should be HL7

Changes

New ACK functionality
Ability to pick apart more MSH header segments

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[x] Added tests?

Linked Issues

Fixes #16394

@arnejduranovic
Just looked this up. Are we want to handle the SU value as well?

Are any tests required for the fields that have been "widened" or are our existing tests sufficient?

I tested locally with the test data in the PR description and got this response when I set the ignore.ignore-etor-ti sender's hl7AcknowledgementEnabled to true:
MSH|^~\&|ReportStream|CDC|Epic|Hospital|20241202194106.427+0000||ACK|372acc8a-8b21-4d6f-a78e-4f13dbabc920|T|2.5.1|||NE|NE
MSA|CA|4AFA57FE-D41D-4631-9500-286AAAF797E4

@brick-green FYI

source: gharchive/pull-request

authors: arnejduranovic jalbinson


text:
Default Deny

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/storage_account specifies:

"Note:
If specifying network_rules, one of either ip_rules or virtual_network_subnet_ids must be specified and default_action must be set to Deny."

This PR ...
If you are suggesting a fix for a currently exploitable issue, please disclose the issue to the prime-reportstream team directly outside of GitHub instead of filing a PR, so we may immediately patch the affected systems before a disclosure. See SECURITY.md/Reporting a Vulnerability for more information.
Test Steps:

Include steps to test these changes

Changes

Include a comprehensive list of changes in this PR
(For web UI changes) Include screenshots/video of changes

Checklist
Testing

[ ] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #issue

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Closing in favor of https://github.com/CDCgov/prime-reportstream/pull/11721


text:
Update manage users info on static site to reflect new designs

Why are we doing this?
With the new manage users design, we need to update the content on the static site to match.
We also have more functionality available now (reset password, MFA, change user name or email) and should add content for these flows.
Action requested

update screenshots on reactivate users and manage user permissions to reflect the new designs (manage permissions is especially important because it's now under a new tab)
add instructions for admins to reset password, reset MFA, change user's name, and change email address

@Rebecca-LM will this be part of the updates you are doing to static site + user guide? If so, I'll close this

@LGFranklin no I don't see it on the other ticket so let's leave this here.
@emmastephenson I don't see the option to reactivate users visible on training. Are you able to add this in there so I can grab the screenshots with the Snagit app we use for these? I'm able to see everything else except for this functionality.
I will also need a few new static pages (in draft mode, if possible) so I can input the new info there. Please see the screenshot below for the placeholders of where they should go. I also wanted to move the order of one of the existing Manage users menu items if possible, as shown. Lmk if you can do this or if you prefer to pair on it.

@Rebecca-LM we can't get this reactivate option in training because that environment isn't linked to Okta, but I just added a user in test that does have the option. I also re-invited you to the test env, lmk if you have any issues registering there.
Adding the new pages shouldn't be a problem, do you and @fzhao99 want to pair on it? He's been working on some static site changes recently.

Thanks, @emmastephenson I got into test and got the "Snagit" screenshot I needed. @fzhao99 I sent you a Zoom to pair on this later this week. Ty!

@emmastephenson the static site still says 90 days but I wanted to confirm it's now 60 days when people get deactivated? (The language on the test site says 60 days.)

@Rebecca-LM can confirm it's 60 days, good catch!

@emmastephenson the confirmation modal on training after clicking on reset pword for a user is still "Doing so will email this person a link to reset their password. The link will expire in 24 hours." Confirming it's still 24 hours?

@Rebecca-LM Yep, that one should still be 24 hours.

All copy updated by https://github.com/CDCgov/prime-simplereport-site/pull/267. Uploading screenshots today now that they are approved/in Github

All images updated via https://github.com/CDCgov/prime-simplereport-site/pull/268. This is only pending Bob review and will go live today. Closing ticket now.

authors: LGFranklin Rebecca-LM emmastephenson

repo: CDCgov/prime-simplereport


text:
可以尝试使用类似UDC网站子分类标签

目前HKC的网站看起来比UDC网站的网站更加现代化，但是UDC网站有做的更好的是它的每个分类都是可以点开的，即使是父分类也是可以点击，并且获得解释的。
将折叠/展开功能仅做在父分类前的小标签上可以达到这种效果，然后添加父分类的页面。我相信这样内容可以更加丰富。

非常感谢您的建议。我们会考虑您的建议然后更好的实现它。目前这个界面仅仅是个演示版本，后面还是需要进一步演化的。

authors: CHCP ciaranchen

repo: CHCP/hkc-docs


text:
Lookup table

mLab hookup and lookup table CRUD

#5


text:
Threading

Just thread it

Added a worker group of threads

repo: CJGutz/unchained

license: MIT


text:
Не смог поставить провайдер по инструкции для Linux

Команда для curl неправильная + надо форсировать filesystem_mirror в .terraformrc

Проблема решена, исправлена документация. .terraformrc не используется, т.к. провайдеры выкладываются в стандартное расположение в профиле пользователя

repo: CLOUDdotRu/evo-terraform


text:
Approver interface gone

When I log in as an approver, I get the same interface as a claimant.

Fixed. Silly bug

authors: bkhunter mfritze

license_source: bigquery


text:
Crash while on borrower page when other user accepts request

I made a request for a book previously and was on the borrower page. When the request was accepted by the owner, the application crashed.
To Reproduce

Make a request on a book and stay on the borrower page fragment.
Have the owner accept the request.
Crash

Expected behavior
Shouldn't happen.
Stack Trace
E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.example.atheneum, PID: 15086
    java.lang.IllegalStateException: Fragment BorrowerPageFragment{11bd535} not attached to a context.
        at android.support.v4.app.Fragment.requireContext(Fragment.java:696)
        at android.support.v4.app.Fragment.getResources(Fragment.java:760)
        at android.support.v4.app.Fragment.getString(Fragment.java:782)
        at com.example.atheneum.fragments.BorrowerPageFragment$4.onDataChange(BorrowerPageFragment.java:198)
        at com.google.firebase.database.core.ValueEventRegistration.fireEvent(com.google.firebase:firebase-database@@16.0.6:75)
        at com.google.firebase.database.core.view.DataEvent.fire(com.google.firebase:firebase-database@@16.0.6:63)
        at com.google.firebase.database.core.view.EventRaiser$1.run(com.google.firebase:firebase-database@@16.0.6:55)
        at android.os.Handler.handleCallback(Handler.java:751)
        at android.os.Handler.dispatchMessage(Handler.java:95)
        at android.os.Looper.loop(Looper.java:154)
        at android.app.ActivityThread.main(ActivityThread.java:6111)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

This could be because of the ValueEventListener listening for onDataChange.
Additional Context
We were on the current master branch.

I think this was a problem with trying to accept a book that already has a borrower, doesn't seem related to the UI of the borrower page.

authors: MarcusBoay ishchow


text:
fix README and setup people detection model script for updated model

This pull request fixes README and setup people detection model script for updated model.
This depends on following two other pull request.

https://github.com/CMU-cabot/cabot-common/pull/9
https://github.com/CMU-cabot/cabot-people/pull/12

@daisukes Please review this pull request for cabot.
This pull request depends on cabot-people pull request.

repo: CMU-cabot/cabot


text:
Fix TensorArray aggregations that produce ndarray of objects

TensorArray aggregations were producing a ndarray of TensorArrays for each group. This changes aggs to produce a TensorElement as a scalar, then allow construction of a new TensorArray using an ndarray of the resulting TensorElement objects.
Fixes #124

also checked the print out is correct:
In [3]:     df = pd.DataFrame({
   ...:         "a": ["foo", "bar"],
   ...:         "b": tp.TensorArray(np.array([[1, 2], [3, 4]]))
   ...:     })
   ...:     result = df.groupby("a").aggregate({"b": "sum"})
   ...:     print(repr(result["b"].array))
   ...:
array([[3, 4],
       [1, 2]])

will go ahead and merge since tests are green, cc @frreiss

repo: CODAIT/text-extensions-for-pandas


text:
取出變數

Fixed #7

COSCUP 當前年份
COSCUP 開始與結束時間
歷年網址

已更新 TypeScript 提示
但直接加會有lint no use錯誤，再麻煩看一下這樣是否OK


text:
Seperate waypoints for traffic light stops

Status
PRODUCTION / DEVELOPMENT
Description
This creates seperate waypoints on /tl_stop_waypoints_array for stopping at traffic lights. Uses tlid field of vector_map_msgs/Signal to assicate a stopline to a traffic light
Steps to Test or Reproduce
 rosrun runtime_manager runtime_manager_dialog.py

Load vector_map 'point_map'.  and TF
In computing tab  under lane_planner:

select lane_rule, lane_stop, lane_select
and run other nodes required for autonomous mode. The car should stop at a stop line which is near to the traffic light (instead of stopping a t a stop line which is near to the car).

This was tested with the wf_simulator and it works.

authors: dejanpan sumanth-nirmal

repo: CPFL/Autoware


text:
As a user with many tasks in the todo I can sort tasks by category

so I can locate a task easily

#7

license: mit


text:
Fix link to ror.org for affiliation autocompletes

Describe the bug
The autocomplete for affiliation places is not working.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://test-metadata.sd.csc.fi'
Proceed until adding DOI info
Try to add an affiliation for the creator
Autocompletion for affiliation is not working

Expected behavior

Affiliation places need to autocomplete with links and identifiers to the DOI info form
Additional context

A possible reason for the error is that the link to ror.org is starting with http://... but needs to be https://....

this is a frontend issue

repo: CSCfi/metadata-submitter


text:
Property for logical equivalence

Propose addition of property
loci:equivalent

to relate an individual feature from one geography or dataset with a feature from another geography or dataset which is intended to represent the same real-world entity.
Use of loci:equivalent would allow representations using slightly different geometrical bases (e.g. aggregates of DGGS cells, ASGS meshblocks, surveyed geometries) to be linked, in situations where a purely geometrical computation might not get to a geo:sfEquals relationships because of differing precision, slivers, etc,. When the data provider's intention is that they match, then this predicate can be used to make that assertion. The provenance of the assertion maybe be recorded in the usual way in a link-set.
Related to #11
Interested in views from @jyucsiro @benjaminleighton @ashleysommer @nicholascar

FWIW the canonical use-case is to relate a Feature to its equivalent DGGS aggregate.

That sounds ok to me. Is an alternative to describe the abstract entity that each geometry represents and link the geometries to that entity? That way the geometries are linked through the abstract entity. This is also handy because if there are other relationships from that abstract entity to, for example, governance structures, then it is possible to navigate from the spatial to these governance relationships.

Yes it might be. But we already have ontologies for ASGS, GNAF, Place-Names, etc that have additional properties on their feature-types, as well as conventions about their geometrical representations. So there needs to a feature-feature-equivalence predicate in the system to manage these. I think it is a small but clear gap.

@dr-shorthair could you provide an example? i understand the semantics, but would like to see them against some test-cases/examples

Gazetted-LGA-GlenEira* -equivalent-> ASGS-LGA-GlenEira

*anticipating that we might have actual LGA polygons at some point

AustraliaPost-postcode-3168** -equivalent-> ASGS-PostalArea-3168

**anticipating that we might have actual AusPost polygons at some point haha

Geofab-OvensRiver -equivalent-> AusPIX-OvensRIver

Note that this explicitly not the same as geo:sfEquals.
It is a logical/fiat relationship, not a geometrical equivalence.
How you choose to use this relationship would be application-specific.
It is complementary to the isPartOf/hasPart relations we added last month.

Closed by Commit https://github.com/CSIRO-enviro-informatics/loci-ont/commit/244662ef4cc3c752ce7226daa9b2201a2f4b3a51 standing in for PR #14

authors: benjaminleighton dr-shorthair jyucsiro nicholascar

repo: CSIRO-enviro-informatics/loci-ont


text:
Adds ability for /induct to remove an applicant role, and adds relevant applicant property, error, and startup warning.

Now when /induct  is called, it will remove the Applicant role from the user.
If they didn't have the applicant role, then it works fine too.
Outputs a warning if the applicant role doesn't exist and errors if /induct is called when it doesn't exist, with a new error code.
Bot.applicant_role can be used to get the applicant role, might be worth moving the error handling into them, and make them always return a role, rather than have to check every time a role is requested, but that's an issue for a different PR.
Resolves #4

I haven't tested but a quick scan through the code seems to suggest the induct command won't work if the applicant role doesn't exist. Would it not be better to still let it work in any case?

Probably, I can change it to a warning or just ignore if it doesn't exist.
Though I don't see any reason why we'd delete the Applicant role tbh

I think just ignoring it would be better - thinking from the perspective of it being as modular as possible if another society wanted to use it too for example but didn't want to implement applicant stuff.


text:
Input keydown user search

Input key down user search isn't working properly. It's submitting the API request with every key press need to add button for submit. To prevent Server overload.

Issue fixed.

repo: CSTRSK/Duino-Coin-PWA-Companion


text:
EOFError: Ran out of input

python make_source.py
Has generated 0 picetures
Has generated 100 picetures
Has generated 200 picetures
Bulding VGG19
src/PoseEstimation/network/rtpose_vgg.py:204: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(m.weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:206: UserWarning: nn.init.constant is now deprecated in favor of nn.init.constant_.
init.constant(m.bias, 0.0)
src/PoseEstimation/network/rtpose_vgg.py:209: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model1_1[8].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:210: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model1_2[8].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:212: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model2_1[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:213: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model3_1[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:214: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model4_1[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:215: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model5_1[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:216: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model6_1[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:218: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model2_2[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:219: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model3_2[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:220: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model4_2[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:221: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model5_2[12].weight, std=0.01)
src/PoseEstimation/network/rtpose_vgg.py:222: UserWarning: nn.init.normal is now deprecated in favor of nn.init.normal_.
init.normal(self.model6_2[12].weight, std=0.01)
Traceback (most recent call last):
File "make_source.py", line 54, in
model.load_state_dict(torch.load(weight_name))
File "/home/zhunan314/.local/lib/python3.6/site-packages/torch/serialization.py", line 303, in load
return _load(f, map_location, pickle_module)
File "/home/zhunan314/.local/lib/python3.6/site-packages/torch/serialization.py", line 459, in _load
magic_number = pickle_module.load(f)
EOFError: Ran out of input

Hi, there, please refer to one of the previous issue #6

authors: seaweiqing xuhongbabe


text:
Apply SPA best practices

Mainly, leverage browser caching, since there are lots of images to be dowloaded by the client.

Added caching for all GET requests, as well as "must-revalidate" header. Problem is, preflight requests are made this way, even with the addition of .WithExposedHeaders() within the middleware's CORS configuration. According to performance metrics in dev env, minimal overhead is added this way. Consider doing more research in the topic as per https://dunglas.dev/2022/01/preventing-cors-preflight-requests-using-content-negotiation/

repo: CaTwoPlus/net-core-angular-store


text:
Bug: Couldn't connect the persistent_peers

ENV
web3_clientVersion: cmp/0.0.1+de9d70b/linux/go1.15.2
os: ubuntu 22.04
Problem
the persistent_peers ("bf2b06ce3b52757183de26f7d90669744c16defb@15.197.254.158:26656" )can't connect suddenly. so my full node can't sync the chain.
Expected behaviour
could have a can connected persistent_peers, so the node can sync continue.
Actual behaviour
log
E[2024-08-10|19:09:06.243] dialing failed (attempts: 4): auth failure: secret conn failed: read tcp 172.31.192.217:50078->15.197.254.158:26656: i/o timeout module=pex addr=bf2b06ce3b52757183de26f7d90669744c16defb@15.197.254.158:26656
I[2024-08-10|19:09:06.848] New websocket connection                     module=rpc-server protocol=websocket remote=[::1]:46896
I[2024-08-10|19:09:06.848] Starting wsConnection                        module=rpc-server protocol=websocket remote=[::1]:46896 impl=wsConnection
I[2024-08-10|19:09:07.988] New websocket connection                     module=rpc-server protocol=websocket remote=[::1]:47074
I[2024-08-10|19:09:07.988] Starting wsConnection                        module=rpc-server protocol=websocket remote=[::1]:47074 impl=wsConnection
I[2024-08-10|19:09:15.964] Dialing peer                                 module=p2p address=bf2b06ce3b52757183de26f7d90669744c16defb@15.197.254.158:26656
I[2024-08-10|19:09:18.966] Error reconnecting to peer. Trying again     module=p2p tries=3 err="auth failure: secret conn failed: read tcp 172.31.192.217:51596->15.197.254.158:26656: i/o timeout" addr=bf2b06ce3b52757183de26f7d90669744c16defb@15.197.254.158:26656
I[2024-08-10|19:09:33.240] Ensure peers                                 module=pex numOutPeers=0 numInPeers=0 numDialing=0 numToDial=10
I[2024-08-10|19:09:33.240] Will dial address                            module=pex addr=bf2b06ce3b52757183de26f7d90669744c16defb@15.197.254.158:26656
I[2024-08-10|19:09:33.240] Dialing peer                                 module=p2p address=bf2b06ce3b52757183de26f7d90669744c16defb@15.197.254.158:26656
E[2024-08-10|19:09:36.243] dialing failed (attempts: 5): auth failure: secret conn failed: read tcp 172.31.192.217:53580->15.197.254.158:26656: i/o timeout module=pex addr=bf2b06ce3b52757183de26f7d90669744c16defb@15.197.254.158:26656

But telnet the 15.197.254.158 26656 is connected.


text:
Restore from Gist broken

@mstreit commented on Fri Nov 10 2017

Release number or git hash: deployed
Web browser version and OS: chrome

Steps to reproduce

save to gist
take link and past it in second browser window

Observed behavior

Only one item is contained in the restored table.

Expected behavior

Same items as in stored table.

Also the numerical values in the filter panel are not restored properly.

fixed, e.g. http://localhost:8080/#gist:c8380f6028cf9d06bf5679bc02418446

authors: mstreit sgratzl

repo: Caleydo/lineup


text:
Week 2

Grade: 2.7+

Using Objects Tech Talk (Links to an external site.).

Link

Code.org OOP Unit 1 (Links to an external site.).

Notes

Following Point Guideline

2.7+/3

Java menu with 2 new functions.

Good understanding of Java programming, used multiple for loops.

Quality note-taking of code.org OOP lesson
Proof of code.org completion

authors: CalissaT deimie

repo: CalissaT/ws


text:
Add Instagram button

Follow
Add link to follow 5/5 Instagram channel
Describe the solution you'd like
A button on the home page or maybe in the header
Tasks

[ ] UI design (or else this will be dev designed) :-1:
[ ] Find examples on the web of similar buttons
[ ] Research how to implement
[ ] Implement button

Acceptance Criteria
Click button open Instagram to 5/5 feed

link is https://instagram.com/fivefifthsvoter?igshid=Zjc2ZTc4Nzk=

@davidnixon I have raised the PR can you please review it.

Thank you @iamvinayvk ! looks great.

authors: GeraldMit davidnixon iamvinayvk


text:
Couldn't resolve the folder

I have VS Enterprise 2015 Update 2 and Open in Notepad++ 1.0.8;
I am not able to open any project or solution or a file using the plugin. I get the pop-up error "Couldn't resolve the folder"

Very interesting - you're running the same configuration I am.
Where is Notepad++ installed?  Was the plugin able to find the executable?  (Check Settings | Open in Notepad++)

Where is Notepad++ installed?
D:\Program Files (x86)\Notepad++
Issue:
Oh I see it.. The Install path field was empty in the Options dialog. you might have to check may be..
Resolved!

I set the "Install path" in VS->Tools->Options->Open in Notepad++ to "D:\Program Files (x86)\Notepad++\notepad++.exe"
Restart VS
Works cool!

Thanks so much Calvin! I am going to use this extension extensively now!!

Great, thanks @deepuHub !
Just out of curiosity, is "D" the system drive, or is that a separate drive where its installed?

"C" is the system drive running fast out of space :-) So, I had installed it on "D".

authors: CalvinAllen deepuHub

repo: CalvinAllen/OpenInNotepadPlusPlus


text:
Is this package still being supported?

@csdaw - What's your feelings about support for this package?
Personally, I don't see myself continuing to support this beyond the immediate future (<1 year) and I've already started a new package for LMB Proteomics Facility which lifts over most of what I need intially and makes it all work from QFeatures instead. I plan to add support for e.g DIA there and don't plan on using camprotR at all in future, which will massively reduce my motivation to make any changes here. I assume you feel similarly? If so, I think we just need to add a note to the README to make that clear.
Another consideration, is CCP even the right host github organisation any more? At some point, either or both of us could/should lose access here...

Hi @TomSmithCGAT :D
Hope you're going alright, sorry, haven't checked my GitHub notifications in a while!
I too have no intentions of continuing to support this package. I believe I use some of the GO functions in my thesis but otherwise have since moved away from MSnbase and camprotR entirely.
I think CCP continuing to host is fine. We can always fork it and those forks will remain on the off-chance the original is deleted.

authors: TomSmithCGAT csdaw

repo: CambridgeCentreForProteomics/camprotR


text:
load_and_authorize_resource and new with params causes ActiveModel::ForbiddenAttributesError

I create example app: https://github.com/znz/rails4-cancancan-example
In the app, http://localhost:3000/comments/new?comment%5Bpost_id%5D=1 causes ActiveModel::ForbiddenAttributesError.
In lib/cancan/controller_resource.rb,
resource_params called from build_resource returns params['comment'] directly instead of comment_params (includes permit) because param_actions does not include :new.
For now, I will use post_id=1 instead of comment[post_id]=1 and set comment.post_id = params[:post_id] in CommentController#new.

Thanks @victorpolko, after hours of digging your answer solved my problem.
load_and_authorize_resource relies on a standard name for you whitelist params method.  It needs to be singular!

authors: adampal znz

repo: CanCanCommunity/cancancan


text:
Indirect new calls

We have indirect regular calls but not with new yet. Blocks various test262 tests.

Done in 0564424f433683fef9afd9257ad06f2f211ee082

repo: CanadaHonk/porffor


text:
fritillaries, eaglelike

This pull request was generated by the 'mq' tool

/trunk merge

repo: Canva/mergequeue-trunk


text:
Update base image

failed to build docker image with mhart/alpine-node:4.4.7

Thanks. we'll need to rebuild the containers manually as we dont have a build pipeline for that yet /cc @enxebre

authors: collinmsn tayzlor

repo: Capgemini/mesos-ui


text:
Add responsibility of employer to (NEW)

After reading it again I agree even more with @tobyhodges
in that we should rephrase the text some.
Because lifelong learning pins somehow pins all responsibility on the individual.
We should make clear that even with a high skill level learning new things
will need time and that this time should be given if the skill is relevant to the work.

Making institutions for that available would be part of the next in this series.
But good point!

Even without institutions, getting the time during your work day to follow a tutorial on something is a need.

authors: CaptainSifff jpthiele


text:
question

我用的就是这个https://github.com/DingMouRen/LayoutManagerGroup，但是用RecyclerView滑动下一个全屏的item时，并不会全屏播放 @CarGuo ，往上滑，上边的视频可以自动播放，往下滑不可以自动播放 @CarGuo

自动播放demo中有啊

已解决

authors: CarGuo riseLishan

repo: CarGuo/GSYVideoPlayer


text:
播放暂停切换到其他app看视频再回来导致异常

问题描述：
播放视频途中，切换到浏览器（或者其他app），点开其中的视频播放，再回来，会导致视频播放终止，底部左边时间显示正常，右边总时长显示00：00，进度条跳到最后。
问题机型/系统：
所有机型
GSY依赖版本
implementation 'com.shuyu:gsyVideoPlayer-java:6.0.1'

请测试最新 demo ，其他视频播放默认情况下会直接释放播放器，如果需要自定义，参考 onLossAudio、onGankAudio、onLossTransientAudio等方法重载


text:
全屏（竖屏的时候），目前发现华为手机（其他手机没有留心），底部进度条等会被遮挡

设置这个全屏主题属性 android:windowTranslucentNavigation为true的时候，部分手机发现底部进度条会别遮挡，目前手里的华为手机有这个问题mate 30,而谷歌亲儿子原生机（pixel）上没有这个问题.

不是很理解什么情况，有截图么》我这边在p30pro 上看demo 好像没什么问题

pixel上没有问题的，返回按钮，下面的进度条是正常展示的

我找了另外一个华为荣耀的手机（30s）,进度条在下面。

如图所示，没有发现 30s 上有问题，也配置了 android:windowTranslucentNavigation

你可以下载一个xinhua news App，华为商店里面就有，版本2.2.0，在live tab下点开视频，全屏就可以复现

………这样的复现对我没意义啊😂

好吧，百思不得期解，那个locaiton_y不为0

authors: CarGuo gslovemy


text:
runData caues crash in dev

seems using runData can cause a null pointer exception from the minecraft instance being null
Caused by: java.lang.NullPointerException: Cannot read field "player" because the return value of "net.minecraft.client.Minecraft.getInstance()" is null
	at carbonconfiglib.networking.CarbonNetwork.getClientPlayer(CarbonNetwork.java:110) ~[carbon-config-VrESRvWV.jar%23184!/:1.19.2-1.1.1]
	at carbonconfiglib.networking.CarbonNetwork.isInWorld(CarbonNetwork.java:100) ~[carbon-config-VrESRvWV.jar%23184!/:1.19.2-1.1.1]
	at carbonconfiglib.impl.internal.EventHandler.onConfigChanged(EventHandler.java:106) ~[carbon-config-VrESRvWV.jar%23184!/:1.19.2-1.1.1]
	at carbonconfiglib.config.FileSystemWatcher.onConfigChanged(FileSystemWatcher.java:163) ~[carbon-config-VrESRvWV.jar%23184!/:1.19.2-1.1.1]
	at carbonconfiglib.config.ConfigHandler.save(ConfigHandler.java:362) ~[carbon-config-VrESRvWV.jar%23184!/:1.19.2-1.1.1]
	at carbonconfiglib.config.ConfigHandler.load(ConfigHandler.java:189) ~[carbon-config-VrESRvWV.jar%23184!/:1.19.2-1.1.1]
	at carbonconfiglib.config.ConfigHandler.register(ConfigHandler.java:161) ~[carbon-config-VrESRvWV.jar%23184!/:1.19.2-1.1.1]
	at trinsdar.ic2c_extras.Ic2cExtrasConfig.createConfig(Ic2cExtrasConfig.java:33) ~[%23179!/:?]
	at trinsdar.ic2c_extras.IC2CExtras.<init>(IC2CExtras.java:36) ~[%23179!/:?]```

will be addressed in tomorrows patch :)

authors: Speiger Trinsdar

repo: Carbon-Config-Project/CarbonConfig


text:
🛑 sitepb is down

In 44b9999, sitepb (190.181.131.163) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sitepb is back up in 6c968c8 after 190 days, 17 hours, 36 minutes.

repo: Careas/vps-monitor


text:
Add SNS publish SMS test

Added test for SNS publish SMS attributes. Tests to support #236

Awesome, is this good to go?

¯_(ツ)_/¯ Tests pass so if you're happy with it, sure.


text:
ODHack: Distinguish liquidable debt per lending protocol

"Distinguish parts of the liquidable debt coming from different lending protocols.
Steps:

Check out the current implementation of computing liquidable debt for each lending protocol: https://github.com/CarmineOptions/derisk-research/blob/master/update_data.py#L89.
Currently, the liquidable debt from all lending protocols is mixed together. Adjust the code so that we're able to distinguish between the liquidable debt, e.g., on zkLend, Hashstack V1, or Nostra Mainnet.
Save the adjusted data to a new file on the Google Storage.
Visualize liquidable debt from different lending protocols on the main chart on the dashboard. Run make app to validate the changes locally.  "

hi @lukaspetrasek  can i jump on this task

hi @lukaspetrasek can i work on this. it will take me 2 working days to finish this task
steps to t

Hi, assigning @petersdt  , because this task is not simple and they provided a better description of the approach.
@petersdt   Let me know if everything is clear and whether you'll be working on the issue. If you have any questions, please ask here. Since this task is quite complex, we can even schedule an introductory call. What is you TG handler please? 🙏🏼
Consider joining our TG group.
See also our contributor guidelines.

Hi. Can I take up this issue if noone else is working on this?
It would take me 3-4 working days to finish the task.
My approach:

I will take a look into deeper logic on how liquidable debt is computed and make necessary modifications in src and update data files.
I think Hashstack files may need some work. So will focus there first.
Then save the updated data to google dataset
Update the main chart file to visualise liquidable debts from different protocols
Run "make app" to ensure output works fine

authors: ManvithaMolakala NueloSE lukaspetrasek petersdt

repo: CarmineOptions/derisk-research


text:
Feature/angular update

Angular 13 update:

Updates Angular and Material UI and most dependencies to latest Angular 13 (LTS) versions
Updates Jest config to be able to understand latest module types
Fixes some errors that popped up due to more strict state immutability in NGRX library. State that is selected from the Store can't ever ever ever be assigned or modified, you have to clone the object and then update the Store with the new object; there were 4-5 places where this needed fixed.
Removes some dead dependencies

NOTE
This also contains a bump from Node 16.3.0 -> 16.15.0 for docker, as Angular CLI needs 16.15.0 or higher.
Keep an eye out for browser runtime errors that say something like 'cannot assign to read-only property of....', this indicates a place where a JavaScript object has been "frozen" and cannot be modified, likely by NGRX on state that has been read from the store. I tried to find these errors on my own, but TypeScript isn't picking up on them in the code itself for some reason.
Most code changes were minor, but some of the fixes mentioned above may cause code conflicts, I can help resolve. Otherwise it would very good to get this in (putting in draft status for now until others can verify it is working on their machines).

@jreddig let's hold off on merging this until we can test @VivekFitkariwala 's PR, this one also touches a lot of files. @ppratikcr7 how do you feel about being able to merge this in with your other frontend changes going on?

@jreddig let's hold off on merging this until we can test @VivekFitkariwala 's PR, this one also touches a lot of files. @ppratikcr7 how do you feel about being able to merge this in with your other frontend changes going on?

Okay, I will merge it in a day or two after my metrics stepper tab is ready.

repo: CarnegieLearningWeb/UpGrade


text:
🛑 monitorss.carnivore.kr is down

In 9a53ab0, monitorss.carnivore.kr (https://monitorss.carnivore.kr/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: monitorss.carnivore.kr is back up in de64e8d after 53 minutes.

repo: CarnivoreKR/status


text:
Add the different scenarios/states for datasets/maps list

[x] Global loading
[x] Search
[x] 0 results
[x] Error
[x] Small loader
[x] Add paginator
[x] Maps onboarding
[x] Tests

New branch: issue-1491

https://github.com/CartoDB/cartodb/pull/1889

repo: CartoDB/cartodb


text:
Fix Google login without Central

OS installs might not have Google login, template load fails.

Ok, recovering the template made old google login button back, but style is wrong. @matallo , could you apply the nice red button, please? :)

We're fixing this in #3902


text:
Choropleth maps with null values are drawn as '0'

If you have a table with, for example, percentages for the countries but some certain rows contain null values (perhaps because there's no data for that country, very typical scenario) a choropleth map will draw the null geometries as if they were a 0.
I think it could be interesting to take this into account because obviously in a map it's not the same that a country has a 0 value that the fact that there's no data for that country.
It seems that this is something that comes from the low part of the stack (CartoCSS? mapnik?) and not something that we are doing thoroughly.
Very #pecan related, I'd say :-)
cc @javierarce @javisantana

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.

authors: alonsogarciapablo iriberri


text:
Bulk actions in datasets and maps revised and fixed

We have revised the conditions that make options appear or appear as disabled in the bulk actions menu. In short, actions that appear should be related to all selected visualizations, and if there is any shared visualization selected that prevents any action, this should appear as disabled.
Acceptance
Make sure these are the actions that appear when selecting several visualizations.
https://docs.google.com/spreadsheets/d/1aXLj6CqqsF4ESqjFa-F0kDzttgO8x_WIKrqA1K6y9XE/edit#gid=0
Related Issue
https://github.com/CartoDB/product/issues/228
https://github.com/CartoDB/product/issues/256

Retest this please

Retest this please

Retest this please


text:
Stops changing the model as the view is being called

@javisantana

Frontend tests were OK :+1: (details)

:es:

authors: Cartofante fdansv javisantana


text:
the commit where i make some relics

adds the relics:
medic pouch, pocketknife, fencing gloves, feather boots, samurai sword

pushed a commit with the relevant changes


text:
Extensions PG::UndefinedTable: ERROR

i am using the extensions as shown in the wiki
when i try to run a test i always get that error:
Error:
AddressTest#test_should_not_save_address_without_street:
DRb::DRbRemoteError: PG::UndefinedTable: ERROR:  relation "install_postgre_sql_extensions" does not exist
LINE 8:  WHERE a.attrelid = '"install_postgre_sql_extensions"'::regc...
                            ^
 (ActiveRecord::StatementInvalid)
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:65:in `exec'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:65:in `block (2 levels) in query'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:64:in `block in query'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract_adapter.rb:722:in `block (2 levels) in log'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:26:in `block (2 levels) in synchronize'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract_adapter.rb:721:in `block in log'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract_adapter.rb:712:in `log'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:63:in `query'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/postgresql_adapter.rb:820:in `column_definitions'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/abstract/schema_statements.rb:114:in `columns'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/schema_cache.rb:76:in `columns'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/connection_adapters/schema_cache.rb:82:in `columns_hash'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/model_schema.rb:488:in `load_schema!'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/attributes.rb:247:in `load_schema!'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/attribute_decorators.rb:50:in `load_schema!'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/model_schema.rb:478:in `block in load_schema'
    /home/isoterik/.rvm/rubies/ruby-2.6.3/lib/ruby/2.6.0/monitor.rb:230:in `mon_synchronize'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/model_schema.rb:475:in `load_schema'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/model_schema.rb:357:in `columns'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/model_schema.rb:404:in `column_names'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/model_metadata.rb:25:in `timestamp_column_names'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_row.rb:79:in `fill_timestamps'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_row.rb:61:in `fill_row_model_attributes'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_row.rb:43:in `initialize'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_rows.rb:36:in `new'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_rows.rb:36:in `block in build_table_rows_from'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_rows.rb:35:in `each'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_rows.rb:35:in `map'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_rows.rb:35:in `build_table_rows_from'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixture_set/table_rows.rb:18:in `initialize'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:658:in `new'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:658:in `table_rows'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:603:in `block (2 levels) in insert'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:602:in `each'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:602:in `block in insert'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:599:in `each'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:599:in `insert'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:585:in `read_and_insert'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/fixtures.rb:545:in `create_fixtures'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/test_fixtures.rb:205:in `load_fixtures'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/test_fixtures.rb:118:in `setup_fixtures'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activerecord-6.0.3.4/lib/active_record/test_fixtures.rb:8:in `before_setup'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/setup_and_teardown.rb:40:in `before_setup'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest/test.rb:96:in `block (3 levels) in run'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest/test.rb:195:in `capture_exceptions'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest/test.rb:95:in `block (2 levels) in run'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest.rb:272:in `time_it'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest/test.rb:94:in `block in run'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest.rb:367:in `on_signal'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest/test.rb:211:in `with_info_handler'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest/test.rb:93:in `run'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest.rb:1029:in `run_one_method'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:89:in `block (3 levels) in start'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest.rb:367:in `on_signal'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest.rb:354:in `with_info_handler'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:88:in `block (2 levels) in start'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:75:in `fork'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:75:in `block in start'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:74:in `times'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:74:in `each'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:74:in `map'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/activesupport-6.0.3.4/lib/active_support/testing/parallelization.rb:74:in `start'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest.rb:138:in `run'
    /home/isoterik/.rvm/gems/ruby-2.6.3/gems/minitest-5.14.2/lib/minitest.rb:68:in `block in autorun'
    /home/isoterik/.rvm/rubies/ruby-2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    /home/isoterik/.rvm/rubies/ruby-2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    -e:1:in `<main>'

fixed the issue. was my own fault.
i dont know why i created the migration file with the generation of a model named "install_postgre_sql_extensions".
after destroying it and creating a soley migration for the extensions the error dissappeared.

fixed the issue. was my own fault.
i dont know why i created the migration file with the generation of a model named "install_postgre_sql_extensions".
after destroying it and creating a soley migration for the extensions the error dissappeared.


text:
Interpret html entites into their values when importing metadata.yaml?

The frontend does not render html entities in the metadata, and we are getting html entities in some of the metadata yaml files. It might be good if the backend interprets html entities to their values so that exported datasets have human readable yaml? If you disagree, we could transfer this to the frontend and render the html entities.

The HTML entities encoding were basically a bug/legacy issue in our metadata export, so not sure if this is still needed.

This should be done in the backend so it's correct in the API response.
We need to deal with html tags anyways already: https://github.com/CatalogueOfLife/backend/issues/1021

authors: bart-v gdower mdoering

repo: CatalogueOfLife/backend


text:
UI Improvement add box-shadow to months instead of border radius

Description
Removed black border on the months and instead added a box-shadow.
Type of Change:

Code
User Interface

Checklist:

[ ] My PR follows the style guidelines of this project
[ ] I have performed a self-review of my own code or materials

@aastha985 it looks clean but if you can use the border with shadow then it looks more pretty.

Yes, it does, made that change

Thanks @aastha985

repo: Catalyst-IN/OpenSourceEvents-Frontend


text:
RFC compliant URI parser/builder

I've started working on rfc3986 compliant URI parser/builder.
While URL is usable for now, I think it would be great to have standards compliant implementation with rfc matching terminology, etc.

Awesome! That definitely needs improvement.

The current version is now theoretically RFC compliant. Please open issues for any specific problems.

I've been working on RFC compliant URI implementation (see the commit for a progress) because:

Web architecture uses identifiers (URI) which in addition to URL includes URN as well.

Current URL implementation does not differentiate between non-existing and empty elements (password, host, path, fragment).
e.g. file:///etc/fstab is equal to file:/etc/fstab although they shouldn't be.

Code closely resembling specification is much easier to maintain.
e.g. URI's path defines pchar as

pchar         = unreserved / pct-encoded / sub-delims / ":" / "@"
  which in my case corresponds to the code
  ``` pony
  fun _pchar_at(start: USize): Bool? =>
    match _at(start)
    | let c: U8 if _unreserved(c) or _sub_delim(c) | ':' | '@' => true
    else
      _pct_encoded_at(start)
    end

URI is not the same as URI reference (URI reference is a superset). Having distinct types for each would make better API and provide compile time checks.

URI has to be validated. This has been mostly resolved with the fix for #454.

If you think it's no longer relevant -- that's all right. Better to learn this sooner than later :)

As part of the fix for #454 I pretty much rewrote the URL handling from scratch. There are quite probably still problems with it, which you are very welcome to fix.
If you think your changes are still relevant then by all means carry on. As long as you're aware that the fix for #454 changed everything, and you're not still trying to fix the old version.
One minor point re passwords. The RFC says in section 3.2.1 that if the data after the ':' in the user info is an empty string this indicates no password. I read that as meaning that no password and an empty password are considered to be the same thing. I may be wrong of course.

authors: andymcn jonas-l sylvanc

repo: CausalityLtd/ponyc


text:
🛑 Alist is down

In f5f2fa5, Alist (https://alist.hiripple.com) was down:

HTTP code: 530
Response time: 80 ms

Resolved: Alist is back up in c200f02 after 1 hour, 44 minutes.

repo: CelestialRipple/ripplelog


text:
[WIP] [feature fix] Vertically align lines of file tree

Purpose
fixes #3155
Due to the prebuilt CSS of the file tree system we use, several logos appeared slightly misaligned with the rest of the line in the tree.
Changes
I added some CSS that specifically affects anything within areas specified by the "treeGrid" id. This fixes the problem where it exists and makes the project dashboard and files pages look a bit better without affecting, for example, the user dashboard.
Side Effects
These CSS changes will affect any area specified by the "treeGrid" id, and will not always make it look better. I have checked, and I don't think that there are any of these ids that I do not know about, but it is entirely possible that I missed something.

@caneruguz Is this something that belongs in treebeard rather than OSF?

Pass finished. Would like to get Caner's feedback before merging.

@sloria in this case this belongs to OSF, treebeard does not necessarily use icons and vertical alignment of what is placed there is more properly done with the user of the library for most accurate results. Treebeard itself uses icons that are properly aligned vertically so the library doesn't need amendment.
@XTech2K did you test this with all instances of fangorn? You should check with a test project that has a lot of add ons and files.

@caneruguz is there a good way to fake a project with many addons on my local system? I don't have accounts with a lot of the services that I would need to activate.
Also, I searched the OSF, and the only places where the "treeGrid" ID is being used are the project dashboard and the files page, both of which I have checked to see if it works well.

Admittedly, though, this feels like it isn't exactly the right way to fix the issue, since for example I just noticed that it does not fix the problem in the file-editor page. Ideally we would simply change the icons so that they work anywhere, and avoid using random CSS patching to do this

@XTech2K there is also flake8 failure u need to handle for the code. Check out the travis build error.

@nanchen47 I am honestly not sure what to do in this circumstance. I tried merging develop to see if that would fix the issue, and it did, but instead a completely different travis issue appeared. The thing is, neither of them have anything to do with the very small-scale css changes that I made (first was in a random js file, second was archiver).
I would assume that it is not correct to try and find the problem in the depths of my osf's code, since everything outside of that css should be identical to develop and fixing that would mean expanding the PR beyond its purpose.
Should I try making a new branch from develop and PR, and see if that lacks the error?

This is just a simple flake8 issue. Like missing a space between code,
missing indent or so. no need to panic. click on the error sign on ur pr
will lead you to the error message.
On Thu, Jun 25, 2015 at 5:07 PM, XTech2K notifications@github.com wrote:

@nanchen47 https://github.com/nanchen47 I am honestly not sure what to
do in this circumstance. I tried merging develop to see if that would fix
the issue, and it did, but instead a completely different travis issue
appeared. The thing is, neither of them have anything to do with the very
small-scale css changes that I made (first was in a random js file, second
was archiver).
I would assume that it is not correct to try and find the problem in the
depths of my osf's code, since everything outside of that css should be
identical to develop and fixing that would mean expanding the PR beyond its
purpose.
Should I try making a new branch from develop and PR, and see if that
lacks the error?
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/pull/3280#issuecomment-115398770
.

@XTech2K The exact same file system is currently used in three places:

Files page
Project overview page
File details page

So you need to make sure your changes adapt to all. There is no way to fake a project with add ons, however there are add on credentials you can use to add it to your local environment: https://osf.io/m2hig/wiki/home/
You should set this up since allmost all file browser issues need to be checked with add ons as well. As for this issue, don't let it occupy too much time, add your custom spacing like you have done, make sure it works in all three areas I listed above, make sure it does not break project organizer and you should be fine.

Got it.
For some reason, I don't have access to that wiki (it tells me I do not have permission).

I'll send it to you in Flowdock if you can tell me who you are.

Xander Herrick

How it looks, by the way:

@XTech2K Have you checked all the instances that Caner mentioned? Is this ready for another pass?

I haven't technically tested every single possible icon, due to some weirdness with getting addons working on my osf, but I have tested all of the basic types of icons,   and  and they all seem to be fine.


text:
[Feature] Search includes user's previous jobs and schools

Purpose
Currently search only uses the users highest ranked school and employer in determining search results. This PR includes a users previous employers and schools in the this process. It also ensures a user who's primary employer/school matches a query should appear above a user who's non-primary employer/school matches a query.
closes https://github.com/CenterForOpenScience/osf.io/issues/3368
Changes

Added all_schools and all_jobs to the users indexed document.
Included in the search mapping boosts to the user's job/school related fields.
Added query time boosts to job/school related fields.

Looks good. :octopus:
Note to self: this change requires a search migration.

authors: brandonPurvis sloria


text:
Fix Visible Contributor Swap Bug

 Purpose
Fix bug where changing the first contributors visibility would raise unnecessary error. Close #3765.
 Changes
set_visible now can accept a list of user dicts being modified and check against that to see whether an error should be raised.
 Side Effects
None that I know of.

set_visible's responsibility is to toggle the visibility of a single user, so it feels incorrect to do a check over multiple contributors in that method. It might make more sense to do the check for >= 1 visible contrib in the manage_contributors method instead.

Pass finished.

The problem using manage_contributors to do the check is that it breaks a few tests, should I just change them?

The tests should reflect the expected behavior. If the expected behavior is changed, then the failing tests should be changed accordingly. If not, then there's a bug that needs to be addressed.

I think someone using the set_visible function has a reason expectation that the result will be validated. Also there are a few instance where validation is already done this way on the site that I don't want to root around and change. This new solution keeps the check in set_visible but ensure the end user can throw an error using manage_contributor

Great. @Johnetordoff Can you please add a regression test to verify the fix?

@sloria How's about that? Am I good?

Looks good

authors: Johnetordoff sloria


text:
[WIP][Hotfix] Show only published preprints [OSF-7433]

Purpose
Don't expose preprints with is_published==False
Changes

Permissions class
Limit number of tasks sent to SHARE

Side effects
Possible confusion for users who have seen unpublished preprints and expect them to remain public. Product is aware and has mitigated.
TODO
Duplicate model-property changes in Django models.
Ticket
[OSF-7433]

Changes required to enforce correct permissions behavior make this very slow, possibly prohibitively. Consider holding until after the Django release

Closing in favor of  #7054


text:
Sublevel property cleanup

Contains a few small fixes to the editor UI for georeferenced sublevels.

Swapped the latitude and longitude parameter of sublevels in the array so that they match the latitude/longitude standard. (Tested this in editor and the change did not seem to introduce any issues.)
Recategorized the sublevel-related parameters on the CesiumGeoreference so that the sublevels category is nested under the "Cesium" category and not as a separate category
Changed the display name of the CesiumSubLevels array to read "Georeferenced Sublevels". This is for clarity and consistency of documentation. Since the property name itself is unchanged, this should not be a breaking change.

Old on left, new on right.

I wasn't sure if the sublevel parameters had been in their own category for a particular reason. If they were, just let me know and I'll discard those changes.

Thanks for the pull request @argallegos!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

This looks good to me, thanks @argallegos!

authors: argallegos cesium-concierge nithinp7

repo: CesiumGS/cesium-unreal


text:
Plan to remove request lib

Hi, I am planning to remove the old dependency request, since it is deprecated for 2 years, and I prefer to use node-fetch to instead of it.

Here was an discussion about what libs can alternative with request: Alternative libraries to request #3143

There are two things confused me:

What type and value may proxy param is? Is it a URL string?
How to handle error

// server.js
request.get(
  {
    url: remoteUrl.toString(),
    headers: filterHeaders(req, req.headers),
    encoding: null,
    proxy: proxy,
  },
  //eslint-disable-next-line no-unused-vars
  function (error, response, body) {
    let code = 500;

    if (response) {
      code = response.statusCode;
      res.header(filterHeaders(req, response.headers));
    }

    res.status(code).send(body);
  }
);

Will be:
import fetch from "node-fetch";

// ...

let statusCode = 500;
fetch(remoteUrl.toString(), {
  headers: filterHeaders(req, req.headers),
  agent: proxy // I do not know whether correct or not to set proxy here
}).then((responseStream) => {
  statusCode = responseStream.status;
  res.header(filterHeaders(req, responseStream.headers));
  return responseStream.arrayBuffer(); // use `arrayBuffer()` to pipe responseBody in raw bytes format
}).then((responseBody) => {
  res.status(statusCode).send(responseBody);
}).catch((err) => {
  // How to handle error?
})

Thanks!

For code preview: server.js#L474

Hi @onsummer! We agree node-fetch would be the best replacement here, which was used as a replacement for request in gulpfile.js.

authors: ggetz onsummer

repo: CesiumGS/cesium


text:
Fix quantized vec3 colors in ModelExperimental

Fixes #9814
(Note: don't use the model from the original issue, it still won't load due to https://github.com/CesiumGS/cesium/issues/9956 which is a separate issue)
#9955 fixed vec3 colors in ModelExperimental, but a few more steps had to be done for this to work with quantized attributes (as even the offset/stepSize uniforms need to be promoted to vec4
@sanjeetsuhag could you review?

Thanks for the pull request @ptrgags!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

authors: cesium-concierge ptrgags


text:
Dangerous try / catch all in lodestar-db

Lodestar-db has a try / catch that swallows all errors, without doing any triage first. Is this expected? Can we define what types of errors do we want to ignore and catch only those?
https://github.com/ChainSafe/lodestar/blob/a5973ea9551e3feae25a9c53d04d73616fe1d770/packages/lodestar-db/src/abstractRepository.ts#L54-L56

We probably can remove the try/catch entirely.
I think it was originally there to convert "not-found" errors into null. Thats done within the leveldb IDatabaseController tho.

authors: dapplion wemeetagain

repo: ChainSafe/lodestar


text:
cli/options: remove preset flag

Motivation
Preset is not really relevant for users as this is something every network should depend on.
Description
Related to and discussed in: #2854
This removes globally the --preset flag and assumes that every --network depends on either minimal or mainnet preset implicitly.
WIP: Holding back and waiting for #2991 first.

@q9f #2991 merged :+1:


text:
Use web EventSource if available

Current implementation of EventSource, from package eventsource, uses many nodejs imports and apis.
All of that complicates web usage of our api client and is unnecessary since there's a native implementation in-browser.
This PR adds a switch to use the native EventSource if it exists.

failed CI


text:
fix: use next epoch for pending balance/consolidations processing

devnet3 branch

:tada: This PR is included in v1.22.0 :tada:


text:
chore: portable blst

Motivation
Just a temp PR to run full CI to validate code

@wemeetagain this branch was deployed last night to feat3 and the metrics look commensurate with unstable.  Going to let them soak for another 24hours to verify though.  @twoeths let me know if you see anything that jumps out at you.  We changed the way the blst rust code gets compiled in ChainSafe/blst-ts#154

So far metrics look good. Equivalent and better metrics in bls job time, peering, etc.

:tada: This PR is included in v1.23.0 :tada:

authors: matthewkeil wemeetagain


text:
image labeling question

Hi, I followed the steps outlined in the README to perform labeling for the video frames, and would like to validate the labeled dataset to make sure they are done correctly.  I ran video2img.py script with test.csv and test.mp4 provided in this repo, and saw both x_data and y_data jpg files in the train_data/match1 folder. So far so good. However,  when I open the jpg file in y_data folder, I observed the white point (produced through heatmap function) doesn't align with the ball in the corresponding jpg file in x_data. For some reason, the white point occurs at the top left corner of the jpg. I even tried running video2img.py script passing HEIGHT and WIDTH (720, 1080) matching the original size but the result is the same. I observed the similar output pattern with my own dataset. Any idea why this is hapenning, and any suggestions on how to fix it? Thanks!

I met exactlly the same problem.
Have you figure out is this situation normal or unnormal?

Hi guys!
I've been looking at this code too, as I had the same problem. I think that these lines (47-48):
else:
heat_map = genHeatMap(WIDTH, HEIGHT, int(label[2]/ratio), int(label[3]/ratio), sigma, mag)
Should actually be:
else:
heat_map = genHeatMap(WIDTH, HEIGHT, int(label[2]*WIDTH/ratio), int(label[3]*HEIGHT/ratio), sigma, mag)
Otherwise, converting the fractional part from imgLabe into an int makes it always equal to 1,1 . Training is working well, haven't tried predict yet.

Hi, @alexandrepdumont
To my understanding, for the dataset downloaded from original repo , the code is correct.
heat_map = genHeatMap(WIDTH, HEIGHT, int(label[2]/ratio), int(label[3]/ratio), sigma, mag)
For dataset generated by imgLabel.py, I think the code should be modified to:
heat_map = genHeatMap(WIDTH, HEIGHT, int(label[2]*WIDTH), int(label[3]*HEIGHT), sigma, mag)
(Notice that my modification is not the same with yours.)
Anyway, what we need to do is making x_data correspond with y_data.

Yes you are quite right, I took out the ratio on subsequent training, as all it did as far as I saw was expand the images into 2.5x the original image. Not sure why this would be desirable.  I've taken out all the ratios in predict.py as well so that it matches with the training.

The training is in progress for me.
But I don't think the eleluation result is quiet normal. The accuracy become 0.74 in the very beginning and start to zigzag.
==========Epoch 0 start validation==========
Epoch 0 accuracy: 0.644
Epoch 0 precision: 0.981
Epoch 0 recall: 0.597
Epoch 0 average = (accuracy + precision + recall)/3: 0.741
==========Epoch 1 start validation==========
Epoch 1 accuracy: 0.786
Epoch 1 precision: 0.944
Epoch 1 recall: 0.799
Epoch 1 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 2 start validation==========
Epoch 2 accuracy: 0.577
Epoch 2 precision: 0.982
Epoch 2 recall: 0.521
Epoch 2 average = (accuracy + precision + recall)/3: 0.693
==========Epoch 3 start validation==========
Epoch 3 accuracy: 0.816
Epoch 3 precision: 0.980
Epoch 3 recall: 0.799
Epoch 3 average = (accuracy + precision + recall)/3: 0.865
==========Epoch 4 start validation==========
Epoch 4 accuracy: 0.662
Epoch 4 precision: 0.977
Epoch 4 recall: 0.627
Epoch 4 average = (accuracy + precision + recall)/3: 0.755
==========Epoch 5 start validation==========
Epoch 5 accuracy: 0.699
Epoch 5 precision: 0.982
Epoch 5 recall: 0.676
Epoch 5 average = (accuracy + precision + recall)/3: 0.785
==========Epoch 6 start validation==========
Epoch 6 accuracy: 0.791
Epoch 6 precision: 0.978
Epoch 6 recall: 0.782
Epoch 6 average = (accuracy + precision + recall)/3: 0.850
==========Epoch 7 start validation==========
Epoch 7 accuracy: 0.825
Epoch 7 precision: 0.915
Epoch 7 recall: 0.868
Epoch 7 average = (accuracy + precision + recall)/3: 0.870
==========Epoch 8 start validation==========
Epoch 8 accuracy: 0.778
Epoch 8 precision: 0.959
Epoch 8 recall: 0.776
Epoch 8 average = (accuracy + precision + recall)/3: 0.837
==========Epoch 9 start validation==========
Epoch 9 accuracy: 0.660
Epoch 9 precision: 0.975
Epoch 9 recall: 0.628
Epoch 9 average = (accuracy + precision + recall)/3: 0.754
==========Epoch 10 start validation==========
Epoch 10 accuracy: 0.631
Epoch 10 precision: 0.990
Epoch 10 recall: 0.576
Epoch 10 average = (accuracy + precision + recall)/3: 0.732
==========Epoch 11 start validation==========
Epoch 11 accuracy: 0.857
Epoch 11 precision: 0.962
Epoch 11 recall: 0.864
Epoch 11 average = (accuracy + precision + recall)/3: 0.894
==========Epoch 12 start validation==========
Epoch 12 accuracy: 0.766
Epoch 12 precision: 0.964
Epoch 12 recall: 0.758
Epoch 12 average = (accuracy + precision + recall)/3: 0.829
==========Epoch 13 start validation==========
Epoch 13 accuracy: 0.733
Epoch 13 precision: 0.970
Epoch 13 recall: 0.723
Epoch 13 average = (accuracy + precision + recall)/3: 0.809
==========Epoch 14 start validation==========
Epoch 14 accuracy: 0.787
Epoch 14 precision: 0.979
Epoch 14 recall: 0.763
Epoch 14 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 15 start validation==========
Epoch 15 accuracy: 0.843
Epoch 15 precision: 0.960
Epoch 15 recall: 0.853
Epoch 15 average = (accuracy + precision + recall)/3: 0.885

I use original repo's dataset and all hyperpararmeter unchanged.

Yeah in doing the same on a tennis serve from Federer and the results are
just not great at all, in fact, I'm pretty certain that i need to do
something more on the predict so that the outputs are exactly the same as
my training data, I'll look at this tomorrow.
On Thu, Sep 9, 2021, 21:08 clover978 @.***> wrote:

The training is in progress for me.
But I don't think the eleluation result is quiet normal. The accuracy
become 0.74 in the very beginning and start to zigzag.
==========Epoch 0 start validation==========
Epoch 0 accuracy: 0.644
Epoch 0 precision: 0.981
Epoch 0 recall: 0.597
Epoch 0 average = (accuracy + precision + recall)/3: 0.741
==========Epoch 1 start validation==========
Epoch 1 accuracy: 0.786
Epoch 1 precision: 0.944
Epoch 1 recall: 0.799
Epoch 1 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 2 start validation==========
Epoch 2 accuracy: 0.577
Epoch 2 precision: 0.982
Epoch 2 recall: 0.521
Epoch 2 average = (accuracy + precision + recall)/3: 0.693
==========Epoch 3 start validation==========
Epoch 3 accuracy: 0.816
Epoch 3 precision: 0.980
Epoch 3 recall: 0.799
Epoch 3 average = (accuracy + precision + recall)/3: 0.865
==========Epoch 4 start validation==========
Epoch 4 accuracy: 0.662
Epoch 4 precision: 0.977
Epoch 4 recall: 0.627
Epoch 4 average = (accuracy + precision + recall)/3: 0.755
==========Epoch 5 start validation==========
Epoch 5 accuracy: 0.699
Epoch 5 precision: 0.982
Epoch 5 recall: 0.676
Epoch 5 average = (accuracy + precision + recall)/3: 0.785
==========Epoch 6 start validation==========
Epoch 6 accuracy: 0.791
Epoch 6 precision: 0.978
Epoch 6 recall: 0.782
Epoch 6 average = (accuracy + precision + recall)/3: 0.850
==========Epoch 7 start validation==========
Epoch 7 accuracy: 0.825
Epoch 7 precision: 0.915
Epoch 7 recall: 0.868
Epoch 7 average = (accuracy + precision + recall)/3: 0.870
==========Epoch 8 start validation==========
Epoch 8 accuracy: 0.778
Epoch 8 precision: 0.959
Epoch 8 recall: 0.776
Epoch 8 average = (accuracy + precision + recall)/3: 0.837
==========Epoch 9 start validation==========
Epoch 9 accuracy: 0.660
Epoch 9 precision: 0.975
Epoch 9 recall: 0.628
Epoch 9 average = (accuracy + precision + recall)/3: 0.754
==========Epoch 10 start validation==========
Epoch 10 accuracy: 0.631
Epoch 10 precision: 0.990
Epoch 10 recall: 0.576
Epoch 10 average = (accuracy + precision + recall)/3: 0.732
==========Epoch 11 start validation==========
Epoch 11 accuracy: 0.857
Epoch 11 precision: 0.962
Epoch 11 recall: 0.864
Epoch 11 average = (accuracy + precision + recall)/3: 0.894
==========Epoch 12 start validation==========
Epoch 12 accuracy: 0.766
Epoch 12 precision: 0.964
Epoch 12 recall: 0.758
Epoch 12 average = (accuracy + precision + recall)/3: 0.829
==========Epoch 13 start validation==========
Epoch 13 accuracy: 0.733
Epoch 13 precision: 0.970
Epoch 13 recall: 0.723
Epoch 13 average = (accuracy + precision + recall)/3: 0.809
==========Epoch 14 start validation==========
Epoch 14 accuracy: 0.787
Epoch 14 precision: 0.979
Epoch 14 recall: 0.763
Epoch 14 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 15 start validation==========
Epoch 15 accuracy: 0.843
Epoch 15 precision: 0.960
Epoch 15 recall: 0.853
Epoch 15 average = (accuracy + precision + recall)/3: 0.885
I use original repo's dataset and all hyperpararmeter unchanged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Chang-Chia-Chi/TrackNet-Badminton-Tracking-tensorflow2/issues/8#issuecomment-916553684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APFHTBRSUH5QQJQ5OUFQ7KTUBFLBVANCNFSM5BGTL3TQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Yes you are quite right, I took out the ratio on subsequent training, as all it did as far as I saw was expand the images into 2.5x the original image. Not sure why this would be desirable. I've taken out all the ratios in predict.py as well so that it matches with the training.

Maybe to make the output video resolution correspond with input. If you drop all ratio, output will always be 512*288. Is that right?

Really not sure tbh, but i don't think it's integral to the algorithm
On Thu, Sep 9, 2021, 21:15 clover978 @.***> wrote:

Yes you are quite right, I took out the ratio on subsequent training, as
all it did as far as I saw was expand the images into 2.5x the original
image. Not sure why this would be desirable. I've taken out all the ratios
in predict.py as well so that it matches with the training.
Maybe to make the output video resolution correspond with input. If you
drop all ratio, output will always be 512*288. Is that right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Chang-Chia-Chi/TrackNet-Badminton-Tracking-tensorflow2/issues/8#issuecomment-916556597,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APFHTBQU72VJC47QFRWEZFTUBFL4BANCNFSM5BGTL3TQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I met exactlly the same problem. Have you figure out is this situation normal or unnormal?

Hi, friend. Can u tell how to run this program,

I met exactlly the same problem. Have you figure out is this situation normal or unnormal?

Hi friend, I followed his readme and first generated the test.csv using the video he provided in repo, and then to the train step, I don't know how to prepare raw_ Data, and how to train this program? Could you give me some advice? thank you.

The training is still in progress.
But I don't think the eleluation result is quiet normal. The accuracy become 0.74 in the very beginning and start to zigzag.
==========Epoch 0 start validation==========
Epoch 0 accuracy: 0.644
Epoch 0 precision: 0.981
Epoch 0 recall: 0.597
Epoch 0 average = (accuracy + precision + recall)/3: 0.741
==========Epoch 1 start validation==========
Epoch 1 accuracy: 0.786
Epoch 1 precision: 0.944
Epoch 1 recall: 0.799
Epoch 1 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 2 start validation==========
Epoch 2 accuracy: 0.577
Epoch 2 precision: 0.982
Epoch 2 recall: 0.521
Epoch 2 average = (accuracy + precision + recall)/3: 0.693
==========Epoch 3 start validation==========
Epoch 3 accuracy: 0.816
Epoch 3 precision: 0.980
Epoch 3 recall: 0.799
Epoch 3 average = (accuracy + precision + recall)/3: 0.865
==========Epoch 4 start validation==========
Epoch 4 accuracy: 0.662
Epoch 4 precision: 0.977
Epoch 4 recall: 0.627
Epoch 4 average = (accuracy + precision + recall)/3: 0.755
==========Epoch 5 start validation==========
Epoch 5 accuracy: 0.699
Epoch 5 precision: 0.982
Epoch 5 recall: 0.676
Epoch 5 average = (accuracy + precision + recall)/3: 0.785
==========Epoch 6 start validation==========
Epoch 6 accuracy: 0.791
Epoch 6 precision: 0.978
Epoch 6 recall: 0.782
Epoch 6 average = (accuracy + precision + recall)/3: 0.850
==========Epoch 7 start validation==========
Epoch 7 accuracy: 0.825
Epoch 7 precision: 0.915
Epoch 7 recall: 0.868
Epoch 7 average = (accuracy + precision + recall)/3: 0.870
==========Epoch 8 start validation==========
Epoch 8 accuracy: 0.778
Epoch 8 precision: 0.959
Epoch 8 recall: 0.776
Epoch 8 average = (accuracy + precision + recall)/3: 0.837
==========Epoch 9 start validation==========
Epoch 9 accuracy: 0.660
Epoch 9 precision: 0.975
Epoch 9 recall: 0.628
Epoch 9 average = (accuracy + precision + recall)/3: 0.754
==========Epoch 10 start validation==========
Epoch 10 accuracy: 0.631
Epoch 10 precision: 0.990
Epoch 10 recall: 0.576
Epoch 10 average = (accuracy + precision + recall)/3: 0.732
==========Epoch 11 start validation==========
Epoch 11 accuracy: 0.857
Epoch 11 precision: 0.962
Epoch 11 recall: 0.864
Epoch 11 average = (accuracy + precision + recall)/3: 0.894
==========Epoch 12 start validation==========
Epoch 12 accuracy: 0.766
Epoch 12 precision: 0.964
Epoch 12 recall: 0.758
Epoch 12 average = (accuracy + precision + recall)/3: 0.829
==========Epoch 13 start validation==========
Epoch 13 accuracy: 0.733
Epoch 13 precision: 0.970
Epoch 13 recall: 0.723
Epoch 13 average = (accuracy + precision + recall)/3: 0.809
==========Epoch 14 start validation==========
Epoch 14 accuracy: 0.787
Epoch 14 precision: 0.979
Epoch 14 recall: 0.763
Epoch 14 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 15 start validation==========
Epoch 15 accuracy: 0.843
Epoch 15 precision: 0.960
Epoch 15 recall: 0.853
Epoch 15 average = (accuracy + precision + recall)/3: 0.885

I use original repo's dataset and all hyperpararmeter unchanged.

Hi! bro, i met some questions in trianning process.
this is the problem:
`tensorflow.python.framework.errors_impl.ResourceExhaustedError:  OOM when allocating tensor with shape[1,16,721,1281] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
[[node res_net__track/res_net__transpose_3/conv2d_transpose_3/conv2d_transpose (defined at /ggg/PoseEstimation/Tracknet_Tracking/TrackNet-Badminton-Tracking-tensorflow2-main/TrackNet.py:87) ]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info. This isn't available when running in Eager mode.
[Op:__inference_train_function_21661]
Errors may have originated from an input operation.
Input Source operations connected to node res_net__track/res_net__transpose_3/conv2d_transpose_3/conv2d_transpose:
res_net__track/res_net__transpose_3/activation_72/Relu (defined at /ggg/PoseEstimation/Tracknet_Tracking/TrackNet-Badminton-Tracking-tensorflow2-main/TrackNet.py:86)
Function call stack:
train_function
2022-03-28 10:10:46.709368: W tensorflow/core/kernels/data/generator_dataset_op.cc:107] Error occurred when finalizing GeneratorDataset iterator: Failed precondition: Python interpreter state is not initialized. The process may be terminated.
[[{{node PyFunc}}]]
Process finished with exit code 1
`

The training is still in progress.
But I don't think the eleluation result is quiet normal. The accuracy become 0.74 in the very beginning and start to zigzag.
==========Epoch 0 start validation==========
Epoch 0 accuracy: 0.644
Epoch 0 precision: 0.981
Epoch 0 recall: 0.597
Epoch 0 average = (accuracy + precision + recall)/3: 0.741
==========Epoch 1 start validation==========
Epoch 1 accuracy: 0.786
Epoch 1 precision: 0.944
Epoch 1 recall: 0.799
Epoch 1 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 2 start validation==========
Epoch 2 accuracy: 0.577
Epoch 2 precision: 0.982
Epoch 2 recall: 0.521
Epoch 2 average = (accuracy + precision + recall)/3: 0.693
==========Epoch 3 start validation==========
Epoch 3 accuracy: 0.816
Epoch 3 precision: 0.980
Epoch 3 recall: 0.799
Epoch 3 average = (accuracy + precision + recall)/3: 0.865
==========Epoch 4 start validation==========
Epoch 4 accuracy: 0.662
Epoch 4 precision: 0.977
Epoch 4 recall: 0.627
Epoch 4 average = (accuracy + precision + recall)/3: 0.755
==========Epoch 5 start validation==========
Epoch 5 accuracy: 0.699
Epoch 5 precision: 0.982
Epoch 5 recall: 0.676
Epoch 5 average = (accuracy + precision + recall)/3: 0.785
==========Epoch 6 start validation==========
Epoch 6 accuracy: 0.791
Epoch 6 precision: 0.978
Epoch 6 recall: 0.782
Epoch 6 average = (accuracy + precision + recall)/3: 0.850
==========Epoch 7 start validation==========
Epoch 7 accuracy: 0.825
Epoch 7 precision: 0.915
Epoch 7 recall: 0.868
Epoch 7 average = (accuracy + precision + recall)/3: 0.870
==========Epoch 8 start validation==========
Epoch 8 accuracy: 0.778
Epoch 8 precision: 0.959
Epoch 8 recall: 0.776
Epoch 8 average = (accuracy + precision + recall)/3: 0.837
==========Epoch 9 start validation==========
Epoch 9 accuracy: 0.660
Epoch 9 precision: 0.975
Epoch 9 recall: 0.628
Epoch 9 average = (accuracy + precision + recall)/3: 0.754
==========Epoch 10 start validation==========
Epoch 10 accuracy: 0.631
Epoch 10 precision: 0.990
Epoch 10 recall: 0.576
Epoch 10 average = (accuracy + precision + recall)/3: 0.732
==========Epoch 11 start validation==========
Epoch 11 accuracy: 0.857
Epoch 11 precision: 0.962
Epoch 11 recall: 0.864
Epoch 11 average = (accuracy + precision + recall)/3: 0.894
==========Epoch 12 start validation==========
Epoch 12 accuracy: 0.766
Epoch 12 precision: 0.964
Epoch 12 recall: 0.758
Epoch 12 average = (accuracy + precision + recall)/3: 0.829
==========Epoch 13 start validation==========
Epoch 13 accuracy: 0.733
Epoch 13 precision: 0.970
Epoch 13 recall: 0.723
Epoch 13 average = (accuracy + precision + recall)/3: 0.809
==========Epoch 14 start validation==========
Epoch 14 accuracy: 0.787
Epoch 14 precision: 0.979
Epoch 14 recall: 0.763
Epoch 14 average = (accuracy + precision + recall)/3: 0.843
==========Epoch 15 start validation==========
Epoch 15 accuracy: 0.843
Epoch 15 precision: 0.960
Epoch 15 recall: 0.853
Epoch 15 average = (accuracy + precision + recall)/3: 0.885

I use original repo's dataset and all hyperpararmeter unchanged.

Hi! bro, i met some questions in trianning process. did u met it? thank you.
this is the problem:
`tensorflow.python.framework.errors_impl.ResourceExhaustedError: OOM when allocating tensor with shape[1,16,721,1281] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
[[node res_net__track/res_net__transpose_3/conv2d_transpose_3/conv2d_transpose (defined at /ggg/PoseEstimation/Tracknet_Tracking/TrackNet-Badminton-Tracking-tensorflow2-main/TrackNet.py:87) ]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info. This isn't available when running in Eager mode.
[Op:__inference_train_function_21661]
Errors may have originated from an input operation.
Input Source operations connected to node res_net__track/res_net__transpose_3/conv2d_transpose_3/conv2d_transpose:
res_net__track/res_net__transpose_3/activation_72/Relu (defined at /ggg/PoseEstimation/Tracknet_Tracking/TrackNet-Badminton-Tracking-tensorflow2-main/TrackNet.py:86)
Function call stack:
train_function
2022-03-28 10:10:46.709368: W tensorflow/core/kernels/data/generator_dataset_op.cc:107] Error occurred when finalizing GeneratorDataset iterator: Failed precondition: Python interpreter state is not initialized. The process may be terminated.
[[{{node PyFunc}}]]
Process finished with exit code 1
`


text:
🛑 Alphalerts is down

In b6bd39d, Alphalerts (https://alphalerts.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Alphalerts is back up in bd12f9d.

repo: Chapati-Systems/status


text:
Cow: Blacklist hydrocodone

Cow requests the blacklist of the keyword hydrocodone. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

hydrocodone has been seen in 59 true positives, 4 false positives, and 0 NAAs.

Rejected by Cody Gray in Charcoal HQ. Reason: 'This should definitely not be blacklisted without exceptional evidence/conditions, and I see no evidence of either. The likelihood of false positives is simply too high. Hydrocodone is the generic name of a drug with many legitimate medical applications. This word is not the hallmark of spam or an otherwise inappropriate post. Consider, for example, the Biology and Medical Sciences sites, on which posts about hydrocodone would likely be perfectly on-topic.'

authors: SmokeDetector metasmoke

repo: Charcoal-SE/SmokeDetector


text:
Ollie: Watch security.com

Ollie requests the watch of the watch_keyword security\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

security\.com has been seen in 11 true positives, 21 false positives, and 1 NAA.

Rejected by Machavity in Charcoal HQ. Reason: 'Full domain is security.com.bd'


text:
Ollie: Watch geanimeds3(?:@gmail.com)?

Ollie requests the watch of the watch_keyword geanimeds3(?:@gmail\.com)?. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

geanimeds3(?:@gmail\.com)? has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


text:
Jesse: Watch thucungvpet.com

Jesse requests the watch of the watch_keyword thucungvpet\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

thucungvpet\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Nisse Engström in Charcoal HQ


text:
AlphaESS Website Change

Alpha ESS have changed from www.alphaess.com to cloud.alphaess.com, this seems to have broken the integration?

Thanks, This was reported already https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/20 and I have made the necessary fix. Details are in that other ticket.

Apologies, completely forgot to look at the closed issues!

authors: CharlesGillanders strickersuk


text:
如果有多个号该怎么操作

可以把CK分割开吗

GitHub action不是很适合拿来跑这种多账号的，它是从环境变量里获取配置，这种一个账号需要四个变量的就很麻烦了，暂时不打算支持。如果想要实现可以自己fork多个仓库自行配置。
本地运行的话可以运行多个docker。

本地运行已经支持多账号


text:
Migrated cheermotes to Helix API

Pull request checklist:

[ ] CHANGELOG.md was updated, if applicable

Description
WIP KKona

yes, I forgot about this stream content PR, will get to work on it

authors: alazymeme zneix


text:
Fail to load DDIMScheduler

Hi, thanks for releasing your excellent work!
When I try to train the second stage (i.e., mld module), I fail to load the DDIMScheduler. When I look into the config file ./configs/modules/scheduler.yaml，I think the definition of DDIMScheduler might be in some file under the directory diffusers. However, I can find this directory in the root directory of the project.  So, do I miss anything? Could you please tell me where the definition of DDIMScheduler is?
Thanks!

Hi, diffusers is a python library.

Diffusers provides pretrained diffusion models across multiple modalities, such as vision and audio, and serves as a modular toolbox for inference and training of diffusion models.

You can install it using:
conda activate mld
pip install diffusers
(suggested) pip install diffusers==0.7.2

It has been included in https://github.com/ChenFengYe/motion-latent-diffusion/blob/98c97c00d63757cf9da9f1dc4afc473dc3faf928/requirements.txt#L23
pip install -r requirements.txt

If this can't solve your problem, please tell us and provide your log or errors.

Thanks! It works for me.

repo: ChenFengYe/motion-latent-diffusion


text:
result on yolov5 compare with yolov5-tiny?

hi, any exp result on comparasion with yolov5? Retinanet itself didn't quite fast on mobile platform.
How about mAP compare with yolov5-tiny?

We have not evaluate yolov5  with our RepGhostNet as backbone yet. It would be straight to do this, that is, replacing the pretrained backbone directly and starting your training.
Note that we have released the pretrained models, please feel free to use RepGhsotNet for any wonderful things you want and we would be grateful if you could share your results with us.

Hi, jinfagang,
I get your concern. But notice that our experiments are all under strict control, such as similar FLOPs or latency for each backbone, to verify the effectiveness and efficiency of our method.
It seems that the very impressive AP boost you mean in MobileOne does not work in this way, such as Table 9 in MobileOne paper, MobileOne-S1 (825M) gets better performance than MobileNetV2 (300M), but not impressively (3.6 mAP in COCO, 1.6mIoU in VOC and 1.0mIoU in ADE20k gains but with almost 3 times the cost). And MobileOne-S0 (275M) is worse than MobileNetV2 in these tasks. Besides, all MobileOne models are much slower in our evaluation.
As for TinyNet and CSPDarknet-Tiny, we have not compare them to our networks yet. It would be interesting to work on this :)

@ChengpengChen Indeed. If am not wrong, repghost eliminated the 2 cat op in very single neck used. But for params it should not be count in, so actually repghost is much more faster then ghost neverthless higher accuracy, is that right?

Yep, you got it.
Our method focuses on improving efficiency of light-weight CNNs via re-parameterization.

authors: ChengpengChen jinfagang

repo: ChengpengChen/RepGhost