SEARCH alias in view query is not using index.

My organisation is using ArangoDb collections and views. But getting slow queries.
Query:
FOR e IN inspection_view_asc filter  e.inspectionType IN [ "MRL", "MRL_PDI"] AND e.invalidated != true  and e.country == "IN" AND e.vehicleType == "CAR" AND e.locationCode IN ["IN_CAR_CC_243_SC_11"] AND e.data.inventoryStatus IN ["STOCK_IN"] and e.archived == "0"  SORT e.createdAt LIMIT 0, 20 RETURN {data:{derivedStatus:e.data.derivedStatus,additionalEstimatePDI:e.data.additionalEstimatePDI,diagnosticStatus:e.data.diagnosticStatus}}
below is my query. When I profiling this query it is not using any index.
I have created multiple indexes on the linked table.

Still it is not using any index.

don't know why?
Also the issue is I am trying to optimise the query.
When the above query is executed first time it is taking around 10-15 seconds, but after that it is taking time in ms. Don't know why.
this is my view
{
    "writebufferSizeMax": 33554432,
    "writebufferIdle": 64,
    "consolidationIntervalMsec": 1000,
    "name": "inspection_view_asc",
    "type": "arangosearch",
    "consolidationPolicy": {
        "type": "tier",
        "segmentsBytesFloor": 2097152,
        "segmentsBytesMax":<PHONE_NUMBER>,
        "segmentsMax": 10,
        "segmentsMin": 1,
        "minScore": 0
    },
    "writebufferActive": 0,
    "commitIntervalMsec": 1000,
    "links": {
        "inspection": {
            "analyzers": [
                "identity"
            ],
            "fields": {
                "attributes": {
                    "fields": {
                        "INSPECTION_TAG": {},
                        "REFURB_TYPE": {}
                    }
                },
                "reviewType": {},
                "appointmentId": {},
                "stage": {},
                "createdBy": {
                    "fields": {
                        "uid": {}
                    }
                },
                "invalidated": {},
                "locationCode": {},
                "inspectionType": {},
                "country": {},
                "registrationNumber": {},
                "reviewedBy": {
                    "fields": {
                        "uid": {}
                    }
                },
                "assignedTo": {
                    "fields": {
                        "uid": {}
                    }
                },
                "inspectionStatus": {},
                "poolType": {},
                "vehicleType": {},
                "inspectionSubType": {},
                "createdAt": {},
                "assigned": {},
                "archived": {},
                "data": {
                    "fields": {
                        "derivedStatus": {},
                        "additionalEstimatePDI": {},
                        "tag": {},
                        "inventoryStatus": {}
                    }
                }
            },
            "includeAllFields": false,
            "storeValues": "id",
            "trackListPositions": false
        }
    },
    "id": "378285290",
    "storedValues": [],
    "cleanupIntervalStep": 2,
    "globallyUniqueId": "c378285290/",
    "primarySort": [
        {
            "field": "createdAt",
            "asc": true
        }
    ],
    "primarySortCompression": "lz4"
}

This is the same issue #17221

https://docs.arangodb.com/3.11/develop/http-api/views/arangosearch-views/ using the 'cached' property of our enterprise offering could offer a solution to this.
With ArangoDB 3.12 more improvement in this direction are expected.


components do not render by default

If a component is very simple, nothing will initially trigger render. Either connectedCallback should always trigger queueRender or it needs to be smarter about whether it needs to call it.
In particular, if a component has an attribute that is inserted on render and that attribute isn't changed from its initial value, then it won't be rendered.
<doesnt-render> should end up showing its name, even if its name doesn't get overridden:
class DoesntRender extends Component {
  name = "bob"
  constructor () {
    super()
    this.initAttribute("bob")
  }

  content = Component.elements.span({dataRef: 'name'})

  render() {
    const {name} = this.refs
    name.textContent = this.name
  }
}

If you then set the attribute 'name' to 'fred' it would render correctly. Similarly, manually telling the element to render (or to queueRender) works as expected.

fixed


Fix CSS file for API reference

closes: #97

bug introduced in PR #95

Hi @tengqm . Thanks for quickly fixing this bug. Ping me if there is a PR to review. I thought self approving is discouraged.

@kbhawkey As I have commented, the bug was introduced in PR #95, which was approved by me. It is kind of cleaning up a mess made accidentally. Yes, I get the idea of democracy, I get the idea of having more eyes reviewing things is better. This repo, like many others, is not hot one. There are not many eyes on it, TBH. You can see that from the history of commits. As one of the owners, I have to take the ownership and sometimes take the informed risks of making mistakes.
As a side note, we are all busy, so we don't have a lot of cycles revisiting the same nimble, trivial thing again and again. There are a lot of more interesting, more important things to do in life.
With that, I'm glad you are watching this repo and you really care about it. Thank you.


Add Best Paper Belonging and Inclusion Award

There was also one we got from CSCW that we should list too. Need to look it up. Emma's paper

Also need to update the output on the html side:


compare/create PR produces a 404

Gitea version (or commit ref): 1.7.3
Git version: 2.21.0
Operating system: CentOS 7
Database (use [x]):

[ ] PostgreSQL
[X] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[X] No
[ ] Not relevant

Log gist:

Description
when trying to create a PR gitea shows a 404.
Happens both on

clicking on the "compare" button
using the api https://myserver.example/api/v1/repos/myowner/myrepo/pulls

No relevant entries in the log files.
After downgrading to 1.7.2 everything works fine again.
Screenshots

It looks like this problem comes from:
https://github.com/go-gitea/gitea/blob/7884353a04dfcb1e03b4b26801dc90e7d0d67a5b/routers/repo/pull.go#L636
QueryUnescape will turn a literal + into a blank space. Heres a test:
https://play.golang.org/p/i19lnB9Q7-M
I think we might want PathUnescape here:
https://golang.org/src/net/url/url.go?s=5107:5151#L173
Based on
// PathUnescape is identical to QueryUnescape except that it does not
// unescape '+' to ' ' (space).

@mrsdizzie I think you meant to reply to #6333 - We need to use PathEscape or its slightly dumber brother EscapePound (which I suspect might need a bit of work) far more liberally throughout our compare url generation, and probably elsewhere.
(I don't think we've got any clear security issues but there will be lots of gotchas on pathological cases.)

My log which apparently is related to this issue and not #6225 : https://gist.github.com/ptman/f76b398d0503e5c50424c1ea8cbfafec .
The permissions should be correct. It worked nicely with 1.7.2. How can I check? I haven't been able to figure out a URL that would work. I mostly end up on the 404 page by following the URL that's returned via git command line, but also create new pull request takes me to the same 404 URL.

OK so this issue is related to:
https://github.com/go-gitea/gitea/commit/5c30817b5fa1fdeedc8d4fc02cf228dc0e6dc556
Which was reverted by:
https://github.com/go-gitea/gitea/commit/fe99c9901d302921eb1e4a67ba687ca3fe543425
This bug report appears to be related to workflows for which original commit worked and its reversion breaks.

Related bug reports are #3727, #5924

OK @ptman,
I assume from your statements you're trying to try do a PR from a user's forked repository on to an organisation's private repository?
Is the user a member of a team in the organisation and is that repository in that team? Does that team have permission to read pull requests? Could you check whether the PR url works if you happen to be an admin?
Presumably the PR url is the same on v1.7.2 and v1.7.4? If not could you paste the differences?

Yes, the URL is exactly the same. The user is an admin and owners team in organisation. Should have all permissions.

Just check that a) the user is in the team b) the repository is in the team and c) that the team has permission to read pull requests.
It's notable that there are two things that change between 1.7.2 and 1.7.4:  the permission check, and possibly the URL.
If you tell me that the URL is the same on 1.7.2 then it must be the permission check.

Yes, I understood you the first time. My user is an admin according to site administration. There is only one team in the organisation. The default team called owners. My user is part of that team. That team has administrator access to the organisation.
The URL is the very same. It's shown in the logs. I sanitized it by renaming the organization to org etc., but didn't change the structure otherwise

Hi @ptman, Sorry I think I got distracted with a few other things.
OK. So where did we get to?

It's a 404, which means that my recent PR shouldn't fix this.
The same url works in 1.7.2 but doesn't work in 1.7.4 - which implicates #6098

The fact that it's 404 and #6098 is implicated places this at:
https://github.com/zeripath/gitea/blob/189b3341dcbab2b13feeea4117910c85d1f772f4/routers/repo/pull.go#L687-L691
You could confirm this by setting log to Trace.

Ran into the same with 1.7.5 (did the very loooooooong upgrade from Gogs this weekend, using all versions in between).
log level set to trace:
2019/04/13 17:29:39 [T] ParseCompareInfo[5]: cannot create/read pull requests
2019/04/13 17:29:39 [D] Template: status/404

Will check the downgrade to 1.7.2

(Dirty) Downgrade to 1.7.2 worked.... (without DB restore from 1.7.2)

aha Thank you @morph027
Now before you suggest staying on 1.7.2 - there is a major security bug in Gogs and Gitea earlier than 1.7.6 so I think we need to fix this.

OK so here's a good test. Your user who can't create a pull on 1.7.5 - can they create comments on a pull  that they did not post? Because that's the same test that is being used from 1.7.4.

Hi!
Thanks for your answer. Yes, just tried and i was able to comment on another users PR.

Ok that's extremely odd. Here's the test involved (L1158):
https://github.com/go-gitea/gitea/blob/c168095afb80b7d17f7b7e34dc61eaa37b3ba0c2/routers/repo/issue.go#L1152-L1157
That's very odd that that would succeed but this fails:
https://github.com/go-gitea/gitea/blob/c168095afb80b7d17f7b7e34dc61eaa37b3ba0c2/routers/repo/pull.go#L706

No this really doesn't make sense. Let's break down L1158:
https://github.com/go-gitea/gitea/blob/c168095afb80b7d17f7b7e34dc61eaa37b3ba0c2/routers/repo/issue.go#L1158
Looking at the definition of ctx.Repo:
https://github.com/go-gitea/gitea/blob/c168095afb80b7d17f7b7e34dc61eaa37b3ba0c2/modules/context/repo.go#L34-L56
We see that ctx.Repo  has an embedded models.Permission so how is that set?
Within repoAssignment in the same file we see:
https://github.com/go-gitea/gitea/blob/c168095afb80b7d17f7b7e34dc61eaa37b3ba0c2/modules/context/repo.go#L226
And this is called from RepoAssignment https://github.com/go-gitea/gitea/blob/c168095afb80b7d17f7b7e34dc61eaa37b3ba0c2/modules/context/repo.go#L336
Which is a handler wrapped around /:username/:reponame
This is a equivalent to if !perm.CanReadIssuesOrPulls(true)) { if you're not the original poster of a PR so how can this work?
I genuinely don't understand why if you can comment on a PR on the head repo you can't do the pull-request.

Weird, of course.
Comment on PR (which works):
[Macaron] 2019-04-14 09:07:16: Started POST /organization/repository/issues/192/comments for x.x.x.x
...
[Macaron] 2019-04-14 09:07:17: Completed POST /organization/repository/issues/192/comments 302 Found in 390.850882ms

Trying to create a PR:
[Macaron] 2019-04-14 09:09:06: Started GET /organization/repository/compare/master...my-fork:ci for x.x.x.x
...
2019/04/14 09:09:06 [T] ParseCompareInfo[58824]: cannot create/read pull requests
2019/04/14 09:09:06 [D] Template: status/404
[Macaron] 2019-04-14 09:09:06: Completed GET /organization/repository/compare/master...my-fork:ci 404 Not Found in 99.870623ms

BTW....as this was an migration from Gogs, we do have warnings (which should be safe to ignore as i've read on other issues):
2019/04/14 09:12:33 [W] Table user Column must_change_password db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table user Column allow_create_organization db default is , struct default is true
2019/04/14 09:12:33 [W] Table user Column prohibit_login db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table repository Column is_fork db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table repository Column size db default is , struct default is 0
2019/04/14 09:12:33 [W] Table repository Column size db nullable is true, struct nullable is false
2019/04/14 09:12:33 [W] Table repository Column is_fsck_enabled db default is 1, struct default is true
2019/04/14 09:12:33 [W] Table action Column is_deleted db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table action Column is_private db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table mirror Column enable_prune db default is 1, struct default is true
2019/04/14 09:12:33 [W] Table release Column is_draft db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table release Column is_prerelease db default is , struct default is false
2019/04/14 09:12:33 [W] Table release Column is_prerelease db nullable is true, struct nullable is false
2019/04/14 09:12:33 [W] Table release Column is_tag db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table login_source Column is_actived db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table login_source Column is_sync_enabled db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table protected_branch Column can_push db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table protected_branch Column enable_merge_whitelist db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table user_open_id Column show db default is 0, struct default is false
2019/04/14 09:12:33 [W] Table deleted_branch Column deleted_by_id db nullable is false, struct nullable is true
2019/04/14 09:12:33 [W] Table repo_indexer_status Column repo_id db nullable is false, struct nullable is true
2019/04/14 09:12:33 [W] Table review column type db type is VARCHAR(255), struct type is INT
2019/04/14 09:12:33 [W] Table comment has column old_assignee_id but struct has not related field
2019/04/14 09:12:33 [W] Table hook_task has column signature but struct has not related field
2019/04/14 09:12:33 [W] Table issue_user has column repo_id but struct has not related field
2019/04/14 09:12:33 [W] Table issue_user has column milestone_id but struct has not related field
2019/04/14 09:12:33 [W] Table issue_user has column is_poster but struct has not related field
2019/04/14 09:12:33 [W] Table issue_user has column is_closed but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column enable_wiki but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column enable_external_wiki but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column external_wiki_url but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column enable_issues but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column enable_external_tracker but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column external_tracker_format but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column external_tracker_style but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column enable_pulls but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column external_tracker_url but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column allow_public_wiki but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column allow_public_issues but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column pulls_ignore_whitespace but struct has not related field
2019/04/14 09:12:33 [W] Table repository has column pulls_allow_rebase but struct has not related field
2019/04/14 09:12:33 [W] Table two_factor has column user_id but struct has not related field

But as this is totaly weird, probably there's something buried deep in it.

@morph027 does that user have the permission of reading code on this repository?

Yes, i can browse the web repo view and clone the repo using git.

Ok I've put up a pr to 1.9 to heavily log.Trace all permissions and denials.
It's #6618
One thing I've noticed looking at this code is that the wrong repo id is returned on that trace message you've got but that's by the by.
If you are able to could you build this pr #6618, take a safe copy of your db and test again with trace on to get the permissions?
On master you can target your logs so that all the trace logs don't appear eg:
[log]
Mode=console,permissiontrace
Level=info
Redirect_macaron_log=true
Xorm=file

[log.permissiontrace]
Mode=console
Level=trace
Expression=permission

Making it easier to see what you're looking for.

Thanks, will try tonight (or probably spawn a test clone).

Pulled 1.9-dev branch, applied the PR, built and tested:
404 when comparing
2019/04/15 19:28:14 ...s/repo_permission.go:154:func1() [T] Permission Loaded for<PHONE_NUMBER>44:my-user in<PHONE_NUMBER>24:organization/repository:
	Permissions: AccessMode:<PHONE_NUMBER>84:owner, 5 Units, 0 UnitsMode(s): [
	Units[0]: ID:<PHONE_NUMBER>20 RepoID:<PHONE_NUMBER>52 Type:<PHONE_NUMBER>16:UnitTypeCode Config: {}
	Units[1]: ID:<PHONE_NUMBER>16 RepoID:<PHONE_NUMBER>48 Type:<PHONE_NUMBER>48:UnitTypeIssues Config: {"EnableTimetracker":true,"AllowOnlyContributorsToTrackTime":true,"EnableDependencies":false}
	Units[2]: ID:<PHONE_NUMBER>12 RepoID:<PHONE_NUMBER>44 Type:<PHONE_NUMBER>80:UnitTypePullRequests Config: {"IgnoreWhitespaceConflicts":false,"AllowMerge":true,"AllowRebase":true,"AllowRebaseMerge":true,"AllowSquash":true}
	Units[3]: ID:<PHONE_NUMBER>08 RepoID:<PHONE_NUMBER>40 Type:<PHONE_NUMBER>12:UnitTypeReleases Config: {}
	Units[4]: ID:<PHONE_NUMBER>04 RepoID:<PHONE_NUMBER>36 Type:<PHONE_NUMBER>44:UnitTypeWiki Config: {} ]
2019/04/15 19:28:14 ...s/repo_permission.go:154:func1() [T] Permission Loaded for<PHONE_NUMBER>20:my-user in<PHONE_NUMBER>96:%!s(*interface {}=0xc0045fb570)/repository:
	Permissions: AccessMode:<PHONE_NUMBER>92:owner, 2 Units, 0 UnitsMode(s): [
	Units[0]: ID:<PHONE_NUMBER>04 RepoID:<PHONE_NUMBER>16 Type:<PHONE_NUMBER>40:UnitTypeCode Config: {}
	Units[1]: ID:<PHONE_NUMBER>12 RepoID:<PHONE_NUMBER>44 Type:<PHONE_NUMBER>04:UnitTypeReleases Config: {} ]

everyhing ok when commenting
2019/04/15 19:29:38 ...s/repo_permission.go:154:func1() [T] Permission Loaded for<PHONE_NUMBER>84:my-user in<PHONE_NUMBER>64:organization/repository:
	Permissions: AccessMode:<PHONE_NUMBER>24:owner, 5 Units, 0 UnitsMode(s): [
	Units[0]: ID:<PHONE_NUMBER>60 RepoID:<PHONE_NUMBER>92 Type:<PHONE_NUMBER>56:UnitTypeCode Config: {}
	Units[1]: ID:<PHONE_NUMBER>56 RepoID:<PHONE_NUMBER>88 Type:<PHONE_NUMBER>88:UnitTypeIssues Config: {"EnableTimetracker":true,"AllowOnlyContributorsToTrackTime":true,"EnableDependencies":false}
	Units[2]: ID:<PHONE_NUMBER>52 RepoID:<PHONE_NUMBER>84 Type:<PHONE_NUMBER>20:UnitTypePullRequests Config: {"IgnoreWhitespaceConflicts":false,"AllowMerge":true,"AllowRebase":true,"AllowRebaseMerge":true,"AllowSquash":true}
	Units[3]: ID:<PHONE_NUMBER>48 RepoID:<PHONE_NUMBER>80 Type:<PHONE_NUMBER>52:UnitTypeReleases Config: {}
	Units[4]: ID:<PHONE_NUMBER>44 RepoID:<PHONE_NUMBER>76 Type:<PHONE_NUMBER>84:UnitTypeWiki Config: {} ]
2019/04/15 19:29:38 ...s/repo_permission.go:154:func1() [T] Permission Loaded for<PHONE_NUMBER>24:a.u in<PHONE_NUMBER>04:organization/repository:
	Permissions: AccessMode:<PHONE_NUMBER>64:owner, 5 Units, 0 UnitsMode(s): [
	Units[0]: ID:<PHONE_NUMBER>00 RepoID:<PHONE_NUMBER>32 Type:<PHONE_NUMBER>96:UnitTypeCode Config: {}
	Units[1]: ID:<PHONE_NUMBER>96 RepoID:<PHONE_NUMBER>28 Type:<PHONE_NUMBER>28:UnitTypeIssues Config: {"EnableTimetracker":true,"AllowOnlyContributorsToTrackTime":true,"EnableDependencies":false}
	Units[2]: ID:<PHONE_NUMBER>92 RepoID:<PHONE_NUMBER>24 Type:<PHONE_NUMBER>60:UnitTypePullRequests Config: {"IgnoreWhitespaceConflicts":false,"AllowMerge":true,"AllowRebase":true,"AllowRebaseMerge":true,"AllowSquash":true}
	Units[3]: ID:<PHONE_NUMBER>88 RepoID:<PHONE_NUMBER>20 Type:<PHONE_NUMBER>92:UnitTypeReleases Config: {}
	Units[4]: ID:<PHONE_NUMBER>84 RepoID:<PHONE_NUMBER>16 Type:<PHONE_NUMBER>24:UnitTypeWiki Config: {} ]

(redacted the real values to my-user, organization and repository)

Did you change the id numbers too? I actually needed those to compare against.

Now this bit is interesting:
Permission Loaded for<PHONE_NUMBER>20:my-user in<PHONE_NUMBER>96:%!s(*interface {}=0xc0045fb570)/repository
Why is %!s(*interface {}=0xc0045fb570) happening?
It means that the owner is not a user here and if you look at the permissions that you're receiving it only has Code and Releases. I suspect it's a Team? I'd have to go back and add some more code to the PR I think to determine it though.
Now the units returned here are interesting because they're precisely the reason the permissions is failing - it is testing if you can read UnitTypePullRequests. So is it possible adjust the team permissions?
I'll add some more things to #6618 to hopefully figure out what the<PHONE_NUMBER>96:%!s(*interface {}=0xc0045fb570) could be.

Hi!
No, i did not change the ids. This happens to users in team, yes.

I think this was missed in my earlier comment - your team doesn't appear to have the read pulls unit for the head repository. Could you check? It might be that you need to turn it off save and then put it back on in case this was an error in schema migration.
Could you also try adding a new team to see if that new team has permission too?
Many thanks

Ah, okay, sorry ;)
Doublechecked the permissions, removed, saved, added and saved again (see screenshots). Read Pull exists for the Team within the Organization which owns the repo.

Just created a a local test clone and tried to reproduce our git:

created a new organization (me as owner)
created a repo inside this org.
forked into my users namespace
tried to create a PR and it works :tada:

So there must be something inside the database regarding all the "old" (migrated) repos. I'll try to create a useful database diff between a non-working and this working repo.

created a new repo within an existing organization (where the other "broken" repos are located too)
created a fork
bam, comparing works :tada:

So the old repos do have something which is bogus.

Deleting and re-forking the repos also make PRs work again. I can try to debug further (got multiple sql dumps to compare to each other), but for now, deleting and forking again looks like valid option (especially when using the API).

OK, I might drop my PR #6607 then. @ptman has @morph027 given you any ideas about what is odd with your teams?

What should I change for the repo (in the DB, using SQL) so that I don't have to remove the repo?

Not sure, still trying to figure out. This is the diff after re-creating the fork:
$ diff -Naur gitea-1.7.6-old-fork.sql gitea-1.7.6-new-fork.sql

--- gitea-1.7.6-old-fork.sql	2019-04-23 11:55:40.000000000 +0200
+++ gitea-1.7.6-new-fork.sql	2019-04-23 11:53:52.000000000 +0200

-INSERT INTO `repo_unit` VALUES (4879,60396,1,'{}',1555586779);
-INSERT INTO `repo_unit` VALUES (4881,60396,4,'{}',1555586779);
+INSERT INTO `repo_unit` VALUES (6919,61117,1,NULL,1556013194);
+INSERT INTO `repo_unit` VALUES (6920,61117,2,'{\"EnableTimetracker\":true,\"AllowOnlyContributorsToTrackTime\":true,\"EnableDependencies\":true}',1556013194);
+INSERT INTO `repo_unit` VALUES (6921,61117,3,'{\"IgnoreWhitespaceConflicts\":false,\"AllowMerge\":true,\"AllowRebase\":true,\"AllowRebaseMerge\":true,\"AllowSquash\":true}',1556013194);
+INSERT INTO `repo_unit` VALUES (6922,61117,4,NULL,1556013194);
+INSERT INTO `repo_unit` VALUES (6923,61117,5,NULL,1556013194);

-INSERT INTO `repository` VALUES (60396,21,'repo-name','repo-name','','','master',0,0,0,0,0,0,0,0,0,1,0,0,0,0,'',0,0,'','numeric',0,1,5,1541068250,1552487739,66701312,'',0,0,0,0,1,NULL);
+INSERT INTO `repository` VALUES (61117,21,'repo-name','repo-name','','','master',1,0,0,0,0,0,0,0,0,1,0,0,1,NULL,NULL,1,NULL,NULL,NULL,1,1,5,1556013194,1556013195,65684480,NULL,NULL,NULL,0,0,0,'null');

-INSERT INTO `user` VALUES (21,'user-name','user-name','','user-name@example.com','[redacted]',0,0,'',0,'','','[redacted]','[redacted]',1541066617,1555587133,1,-1,1,0,0,0,0,'56f5d9b46d28a329f5b932a0c74c8041','user-name@example.com',1,0,0,0,134,'',0,0,1555587133,'',1,0,NULL,0);
-INSERT INTO `user` VALUES (21,'user-name','user-name','','user-name@example.com','[redacted]',0,0,'',0,'','','[redacted]','[redacted]',1541066617,1555587133,1,-1,1,0,0,0,0,'56f5d9b46d28a329f5b932a0c74c8041','user-name@example.com',1,0,0,0,134,'',0,0,1555587133,'',1,0,NULL,0);

+INSERT INTO `watch` VALUES (3031,21,61117);

The repository table itself does not change much besides having the proper default values in some columns.
Interesting that the repo_unit table is only losing 2 entries but get's 5 after the new fork exists.
No changes in the access table.
@zeripath any useful hints in this diff?

It's so strange. Create repository and fork repository will also insert defaultRepoUnits into repo_unit. It should be 5 records not 2 whatever v1.7.2 or v1.7.6
	defaultRepoUnits = []UnitType{
		UnitTypeCode,
		UnitTypeIssues,
		UnitTypePullRequests,
		UnitTypeReleases,
		UnitTypeWiki,
	}

I have removed some features for my fork so I only have UnitTypeCode and UnitTypeReleases on my fork. But how could I check the permissions from the database? The fork was created ages ago. Was there previously some problem with setting the correct permissions on a fork?

So that's maybe a bug, we should check the original repository's UnitTypePullRequest but not forked repository's.

Yes, that's correct.

Yes, works for me as well, thanks!


Make tooltip togglable (push to show, push to hide)

Is your feature request relasted to a problem? Please describe.
Sometimes it is handy to let the BarTouchData() stay until the user push the screen/mouse again.
Describe the solution you'd like
An option in BarTouchData() -> boolean: "toggleToolTip"
When  enabled the last tooltip shown stays until the user click on it (close) or push another rod (new tooltip)
Describe alternatives you've considered
I tried to override the handleBuiltInTouches and show it myself, but it never worked for me.

Hi. You can implement it yourself by overriding the touch flow.
Unfortunately, there is no implementation to mention, but I can implement it if I found some free time.

Hmm.... I tried several solutions to get the tooltip to stay, only way was to modify FLTouchEvent
https://github.com/imaNNeoFighT/fl_chart/blob/cff6ef797278bc1cc6841d09c2eab3b248937071/lib/src/chart/base/base_chart/fl_touch_event.dart#L26-L28
Modifying to something simple as this :)
     if (this is FlTapUpEvent) {
       return true;
     }

Only problem then is that toggling only work with longpress or pan :)
As you probably figured out my Flutter skills are not best, but I'm learning each day.
This was more like a "hack" to get this working, but the touch-events got to complex for me to handle.
In the "touchCallback" for BarTouchData() you don't have any control over the events sent to the tooltip, so it goes away when releasing button/touch.

Check this sample (source code). It's so easy.
https://user-images.githubusercontent.com/7009300/156784816-53f95dd9-f387-4600-8a92-d05b1aeea3da.mov

Thank you for this! Worked like a charm!

Is there any example for line chart also?

Check this sample (source code). It's so easy.
toggle.mov

the code page is loseing

Sorry about that invalid link,
It should be fixed now (I edited my comment)
Here is the link

thank you


Please check :) thanks

Inscription #49587960--17841
Inscription #49587742--17647
Inscription #49587723--17649
Inscription #49587682--17658
Inscription #49587682--17416
Inscription #49587683--17427

find the double check your inscription number double check results here -> https://github.com/orc721/monkes21/blob/master/DBLCHECK.md


⚠ Processors has degraded performance

In 32a8309, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 57 ms

Resolved: Processors performance has improved in 9ab555b.


Add SeqAn

It will be nice to have SeqAn (The Library for Sequence Analysis) on vcpkg,
The github repo https://github.com/seqan/seqan

Hi @alienzj, thanks for posting this issue and submitting the PR.


improve text rectangular

bring back improvements from John
@gJDelavega
@95-martin-orion
https://github.com/gdsfactory/gdsfactory/pull/2471/files#diff-f3f7f9f60670ce617d7d6e9c0ab2d855778cf325a52a98ac00a9aa2f6467d567R44

Tested ok.
Just need
@cache
def rectangular_font_litho() -> dict[str, str]:

that fetches font definition


[Feature Request] Jump to Object Type beside field type

version: chrome extension 1.7.0
let's have schema:
type Person {
  name: String
}

Current Behavior:
We search name in doc search bar, the search result comes, but we can only click on the field name, we can not jump to type Person.(graphiql can do it).

I'll look into this.

I've added that functionality. However, I'm not going to be promoting it. It should be available in the next release.


Unable to locate 'moment' module

As of Sept. 25, pulling and running the project on Mac yields an error suggesting 'moment' cannot be found.
 Cannot find module "moment
I've tried adding it via NPM, added it to nonTreeShakableModules, added a reference in markup to momentjs via a CDN, and tried adding like jquery
new webpack.ProvidePlugin({ $: 'moment', moment: 'moment' })
The error happens both client side and server side when pages are pre-rendered.  Any idea what needs to happen to eliminate the error?

I, too, have this issue. However, with windows.

Have you already tried to rebuild the vendor bundle?
webpack --config webpack.config.vendor.js
That did the trick for me.

moment-js is removed removed from ngx-bootstrap dependency list, due to its very huge size.
Now you can define your own locale translation.
https://github.com/valor-software/ngx-bootstrap/issues/1963#issuecomment-324002615

Should be ok now that I added moment to packagejson dependencies, but ideally we should come up with a better solution.

Closing for now, but if anyone has any better suggestions, I'm all ears! @davidsekar


[FLINK-17149][debezium][canal] Introduce Debezium and Canal changelog format

What is the purpose of the change
Introduce DebeziumFormatFactory and CanalFormatFactory to read changelogs.
CREATE TABLE my_table (
  ...
) WITH (
  'connector'='...',  -- e.g. 'kafka'
  'format'='debezium-json',
  'debezium-json.schema-include'='true' -- default false, Debeizum can be configured to include or exclude the message schema
  'debezium-json.ignore-parse-errors'='true' -- default false
);

CREATE TABLE my_table (
  ...
) WITH (
 'connector'='...', -- e.g. 'kafka'
 'format'='canal-json',
 'canal-json.ignore-parse-errors'='true' -- default false
);

Brief change log

Introduced DebeziumJsonDeserializationSchema and DebeziumFormatFactory to deserialize Debezium messages.
Introduced CanalJsonDeserializationSchema and CanalFormatFactory to deserialize Canal messages.
Throw exception in DebeziumFormatFactory#createSinkFormat and CanalFormatFactory#createSinkFormat to tell users they can't be as sink for now.

Verifying this change

Added DebeziumJsonDeserializationSchemaTest and CanalsonDeserializationSchemaTest to deserialize debezium messages and canal messages.
Added DebeziumFormatFactoryTest and CanalFormatFactoryTest to unit test factories.

Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? not documented

cc @danny0405

Thanks for the reviewing @danny0405 . PR updated.

Thanks for the reviewing @danny0405 .
Merging...

The failed kafka case is related to FLINK-16383.


Styles: refactor navigation.scss

It's almost 1,000 lines long and has both styles for the main hero navigation and for the local navigation which is wrong.

@justintemps Do you have more specific suggestions for how this can be refactored? Perhaps split into two, similar to the navigation and local nav components?

@bashlk exactly, it should be refactored so there are two different scss files, one for each component.

@bashlk, @GGKapanadze I'm thinking this can wait for after the version 1. What do you think?

@justintemps I don't think we have worked a lot with the Navigation component so far so it is hard for us to weigh in on this. But since this is an internal detail of the design system, I think it can be postponed.

@justintemps We had a chat about this and we think that the Navigation component should probably be down in several separate components (e.g. language selector, search box, dropdown menu, horizontal nav).
We also think that we should avoid having compound elements like the Navigation since they are not reusable and instead have simpler components like the ones listed above so that a consumer can combine them on their own.


Add Linode DNS Support

Ref janeczku/rancher-letsencrypt#81.
@asdek I submitted this to the base repo a year ago but it never got merged. Would like to get wildcard support using Linode as the DNS provider!

This could be updated to https://go-acme.github.io/lego/dns/linodev4/

@displague Unfortunately I don't have an account in this provider to check compatibility. If you make pull request I can add it to my fork.

@asdek This would require moving up to acme/lego 1.1.0, at least.


make e2e-setup-certmanager: E2E_CERT_MANAGER_VERSION now works

Richard reported this issue in #7048. He found that the command:
E2E_EXISTING_CHART=true E2E_CERT_MANAGER_VERSION=1.14.2 make e2e-setup-certmanager

fails with the error:
Error: unknown flag: --version1.14.2

It looks like this comes from a change in https://github.com/cert-manager/cert-manager/pull/6795. In the Makefile:
$(addprefix --version=,$(E2E_CERT_MANAGER_VERSION))

expanded to an empty string most of the time (when E2E_CERT_MANAGER_VERSION is left empty), which was OK. But when setting E2E_CERT_MANAGER_VERSION, addprefix would prepend --version without a space, causing the problem.
Closes #7048
NONE

/approve
/lgtm


smaller github pages distro

We can probably get the GH pages distro under 1MB by using the web-specific build of SWIPL wasm (and setting up locateFile to look for the .wasm in github pages) once https://github.com/rla/npm-swipl-wasm/pull/8 is merged.

Please note - I am unlikely to action this issue unless someone explicitly asks for it as it does not seem to provide much added value at this point in time.


Resizing operation flips the image 90 degrees

Check the get_pixel_at function

The problem lies in the calculation of the location. It should be y * self.width + x instead of x * self.width + y. This is because the image data is typically stored in row-major order, where each row is stored sequentially.


Cleanup unused Jenkins files and scripts

Fix issue : https://github.com/NVIDIA/spark-rapids/issues/1568
Move Databricks scripts to GitLab so we can use the common scripts for the nightly build job and integration tests job
Remove unused Dockerfiles

MR to move scripts to GitLab: https://gitlab-master.nvidia.com/nvspark/blossom-jenkins/-/merge_requests/123

build

change to target to branch-0.5

build


Make output optional

Replaces all loggin related couts in the code with a log function.
this log function is would only print if  DISABLE_OUTPUT is not defined.

We can just use Boost.Log v2 for the logging btw.

Well the hard part was the find+replace, but sure why not


Seems the HDFS file path contains ':' colon will throw exception

I had download this whole source code and built it successfully. When i tried to run a crawl test:
bin/crawl urls/ TestCrawl/ http://localhost:8983/solr/nutch 2
I run into this URI path name issue.
hadoop.log.zip
i have this log file attached. It seems the HDFS file path name special characters issue is still there?
2016-01-03 13:27:08,405 INFO  fetcher.Fetcher - Fetcher: starting at 2016-01-03 13:27:08
2016-01-03 13:27:08,405 INFO  fetcher.Fetcher - Fetcher: segment: TestCrawl/segments/drwxr-xr-xnn4nstevennstaffnn136nJannn3n13:24n20160103090925
2016-01-03 13:27:08,406 INFO  fetcher.Fetcher - Fetcher Timelimit set for :<PHONE_NUMBER>406
2016-01-03 13:27:08,631 WARN  util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2016-01-03 13:27:08,677 ERROR fetcher.Fetcher - Fetcher: java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative path in absolute URI: drwxr-xr-xnn4nstevennstaffnn136nJannn3n13:24n20160103090925
at org.apache.hadoop.fs.Path.initialize(Path.java:148)
at org.apache.hadoop.fs.Path.(Path.java:126)
at org.apache.hadoop.fs.Path.(Path.java:50)

Hi,
You could try the fix given in this thread.
Or simply use the following command to start the crawl:
runtime/local/bin/nutch crawl urls/ -solr http://localhost:8983/solr/ -dir TestCrawl -depth 3 -topN 50


Setting scrollTop/scrollLeft on a Collection does not scroll in 9.19.0 or later.

Example:  https://codesandbox.io/s/9j5v53ryq4?module=%2FExample.js
React-virtualized versions 9.19.0 and later (9.19.1, 9.20.0) do not apply the scrollTop/scrollLeft values from ScrollSync to a Collection component properly. The end result is that the items to be drawn are updated to match what should be in the view window, but the view window is not scrolled to show those items. So what is visible is an unmoving Collection that slowly has the upper rows go invisible until there are no more rows being drawn in the view window instead of the Collection's view window scrolling to match.
Reverting to react-virtualized 9.18.5, the above example works as expected. The lower Collection does scroll in response to changes to the scrollTop value. You can test this by changing the dependency version for react-virtualized in the above sandbox without making any other changes.

Any news on this? I have also pinned 9.18.5 now after chasing a initialization problem of a Collection + scrollTop/scrollLeft values.

Thnx, dawnmist. Let's hope your fixes will be integrated soon.

Is this update dead? Also running into this issue.

No idea. I've had absolutely no feedback other than the initial "bug" label on the issue and nothing at all on the pull request I submitted 10 months ago that fixes it (and explains what broke it). At this point, I'd suggest using a package called [patch-package](https://github.com/ds300/patch-package) to apply the patch to later versions of react-virtualized any time that node_modules gets updated/installed/removed.

please please patch this!!!

please please patch this!!!

Just ran into this, and it cost me quite a bit of time before I found that it was a bug.  Downgrading to 9.18.5 resolved it for me.  Putting in a vote to patch please.

@wuweiweiwu Is there any chance that someone could look into this. It's been 2 years since the report, it's had a pull request fixing the bug for more than 18 months, and the only feedback ever received from the react-virtualized team has been to set the status to "bug" a few hours after it was first reported.


Screen is not responsive on smaller devices on donate page

On width  less than 500 px the donate page is not responsive it overflows like this ->

Desired Solution -> it should be responsive for all resolutions.

See https://github.com/exercism/exercism/issues/6036


Mention in docs that ignored properties do not benefit from the single-instance-autoupdating magic

I just spent a long while debugging some unusual behavior with my User subclass of RLMObject. In the end I came to the rather obvious conclusion that ignored properties do not autoupdate and you should avoid them. Let me elaborate on my confusion:
Being the good Realm citizen that I am, I didn't want to pass my User all over the place, rather its primaryKey ID, something which is threadsafe.  So I have a Database class which encapsulates a lot of Realm logic and ultimately calls [User createOrUpdateInRealm:[RLMRealm defaultRealm] withValue:dictionary]; where dictionary has the primaryKey inside.
My mistake was that I tried to override createOrUpdateInRealm:withValue: to re-derive the properties I'm ignoring. This, however, had no effect on my User object being held elsewhere in the app, waiting for updates.  That object did receive new values for the tracked properties, but not for the ignored properties.
I know it seems obvious in retrospect, but there should definitely be more than "Realm won’t interfere with the regular operation of these properties" in the docs.

Thanks for the suggestion @skensell, what do you think the docs should say specifically to make this clearer?


Intermittent TTI failures on Travis OSX

The travis OSX builders frequently, but not regularly, segfault on the the standalone TTI example test. Presumably this might be due to the shaky nature of the travis OSX builders, so OSX testing is temporarily disabled. If anyone is interested in debugging and fixing this, simply remove the allow_failures line from the build matrix in .travis.yml.

It seems to be fine now right?

Well, it's disabled and not really fixed. However, travis doesn't support Python projects on OSX natively at the moment, so I think we can close the issue for now.


FirebaseStorage getData function

Create a new PR to resolve original PR #207 CLA problems. Added some doc comments as well.

@goderbauer can you review, please?

cc @kroikie who can also help with review

This looks fine to me. Would be cool if you could add an example usage of the new API to the example app in the example directory.
@collinjackson Maybe you can take a quick look as well. As the original author of this plugin you're more familiar with the storage API.

Please bump the version and add a changelog entry so we can publish this after you merge it. If you don't want to write a test (since this plugin has no tests yet), adding to the example app as @goderbauer suggested would be fine. Thank you!

I tried to pub publish the new version, but currently pub seems to be rejecting all package updates. I'll try again in a little bit.

It's live: https://pub.dartlang.org/packages/firebase_storage

Thanks!


Add a GET event by atom

Description of the change

Description here

Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

Fix #1

Describe multi-tenancy segmentation
Adds a function to be able to get an event by atom and also adds a generic GET request

/gcbrun

/gcbrun


Site http://www.jsonschema2pojo.org/ is down

Hi y'all,
The site doesn't seem to be working :frowning:
Thanks for all your help and contributions!

Thanks for mentioning this. It appears site is down due to problems at Heroku right now: https://status.heroku.com/


Crashed by "Assertion failed" with packaged game ".exe"

After packaged, Every time I quit the game, either  BP node "Quit Game" or  console command "exit",  the game will pop up an error window as below:

It's not caused by my code or any other logic because I test it with an almost "empty" ue4.26 project and crashed as well.
Map: default level. (from file ->new level ->Default)
Actor: Basic actor with a node component inside, the component runs a script that has only 1 line js code:

Console.log("hello world")

UE4 level outline

My js script

Inside the BP actor

Runs Ok within UE4 editor

**After packaged, I run the .exe ** , then pop up a crash error windows as mentioned firstly above.
I think something caused Memory Leak, and I tried to figure it out.
After serveral days flew away  (I first noticed this on August 3rd), now I know I can never do it.
Can you spare some time to  help me ?
Hope your reply and any help will be highly appreciated.
Thank you again.
You Sincerely.

@getnamo @hikingyoung
In NodeCmd.cpp
void FNodeCmd::StopMainScript()
{
	if (bIsMainRunning)
	{
		/*FCULambdaRunnable::RunLambdaOnBackGroundThread([this]
		{
			StopMainScriptSync();
		});*/

		StopMainScriptSync();
	}
}

I modified it,
It might be because of this asynchronous,
It doesn't crash now,
I don’t know if there will be consequences,
But now it will not crash after packaging,
I guess it may be caused by the callback.
My English is not good, I don’t know if this explanation is correct.


MaterialEntry doesn't use the DisableTextColor when the dark mode is enabled (happens on iOS devices)

We are excited to announce that we are working on a new generation of controls based on Material Design V3, which we will be releasing soon.
This ticket has been included/fixed in the upcoming version of this NuGet package, which will include both current and new generations of controls.


Adds additional docs for dedup step

Adds a section in the gremlin-semantics docs for the dedup step.
Main purpose of this is to highlight some extra considerations with dedup implementation which are somewhat beyond the scope of the reference docs.

LGTM


Q. is --time-fields working?

The default timestamp fields parsing seems to work well:
$ echo '{"ts":"2023-03-17T15:31:58.242777327Z","message":"msg"}' | humanlog -m 'message' --time-format '2006-01-02T15:04:05.000000000Z'
humanlog> reading stdin...
2023-03-17T15:31:58.242777327Z || msg

However, if I try and use the custom --time-fields option, that doesn't seem to be working?
$ echo '{"xts":"2023-03-17T15:31:58.242777327Z","message":"msg"}' | humanlog --time-fields 'xts' -m 'message' --time-format '2006-01-02T15:04:05.000000000Z'
humanlog> reading stdin...
0001-01-01T00:00:00.000000000Z || msg xts="2023-03-17T15:...

$ humanlog -v
humanlog version 0.7.5+9612436

Hmm I'll try to take a look. This should work.

Fixed by https://github.com/humanlogio/humanlog/pull/69


cv2.error: OpenCV(4.5.2) :-1: error: (-5:Bad argument) in function 'line' > Overload resolution failed:

<array_function internals>:5: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray.
Exception in thread Thread-2:
Traceback (most recent call last):
File "C:\Users\heishen\AppData\Local\Programs\Python\Python38\lib\threading.py", line 932, in _bootstrap_inner
self.run()
File "C:\Users\heishen\AppData\Local\Programs\Python\Python38\lib\threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "F:\smart_classroom-master\detection_system\alphapose\utils\writer.py", line 201, in update
self.draw_pose(self.pose_estimator, img, pose_list)
File "F:\smart_classroom-master\detection_system\alphapose\utils\writer.py", line 381, in draw_pose
pose_estimator.draw_axis(
File "F:\smart_classroom-master\detection_system\pose_estimation\pose_estimator.py", line 282, in draw_axis
cv2.line(img, tuple(axisPoints[3].ravel()), tuple(
cv2.error: OpenCV(4.5.2) :-1: error: (-5:Bad argument) in function 'line'

Overload resolution failed:

Can't parse 'pt1'. Sequence item with index 0 has a wrong type
Can't parse 'pt1'. Sequence item with index 0 has a wrong type

救救孩子

把opecv版本降到4.5.1


Add migration entrypoint

Pull Request Test Coverage Report for Build 322

1 of 3 (33.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.9%) to 95.78%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

openregistry/lots/loki/migration.py
1
3
33.33%

Totals

Change from base Build 320:
-0.9%

Covered Lines:
3609

Relevant Lines:
3768

💛  - Coveralls


CameraImage ResolutionPreset.veryHigh's (1080 * 1920) width * height * 4 not equal planes[0].bytes.length.

Hello,
IOS environment
When I using CameraImageStream, what I get in ResolutionPreset.veryHigh's planes[0].bytes.length is 8355840, but width * height * 4 is only 829440. the planes[0].bytesPerRow is  4352, what I wish is 1080 * 4, but I got 1088 * 4.
Can anyboy tell me why?
Image.fromBytes(cameraImage.width, cameraImage.height, cameraImage.planes[0].bytes, format: Format.bgra)
out of range hanppend.
Thanx.

@obf1313
Please provide flutter doctor -v and a minimal complete reproducible code sample that shows the issue you are facing along with expected and actual behavior.
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Race when using WithContext on multiple goroutines

Version: v7.0.0-beta.3
My application would like to use *ClusterClient.WithContext or *Client.WithContext per Redis-command to specify a timeout. Here's an example
package main

import (
	"context"
	"log"
	"sync"
	"time"

	"github.com/go-redis/redis/v7"
)

func main() {
	const n = 50
	var wg sync.WaitGroup
	wg.Add(n)

	client := redis.NewClient(&redis.Options{
		Addr: "localhost:6379",
	})

	for i := 0; i < n; i++ {
		go func() {
			defer wg.Done()

			ctx, cancel := context.WithTimeout(context.Background(), 5*time.Second)
			defer cancel()

			c := client.WithContext(ctx)
			_, err := c.Ping().Result()
			if err != nil {
				log.Println(err)
			}
		}()
	}

	wg.Wait()
}

Running the above program with the -race flag prints data races
WARNING: DATA RACE
Read at 0x00c0002460e0 by goroutine 56:
  github.com/go-redis/redis/v7.(*Client).ProcessContext()
      /Users/user/go/pkg/mod/github.com/go-redis/redis/v7@v7.0.0-beta.3/redis.go:539 +0x5b
  github.com/go-redis/redis/v7.(*Client).Process-fm()
      /Users/user/go/pkg/mod/github.com/go-redis/redis/v7@v7.0.0-beta.3/redis.go:535 +0x85
  main.main.func1()
      /Users/user/go/pkg/mod/github.com/go-redis/redis/v7@v7.0.0-beta.3/commands.go:328 +0x227

Previous write at 0x00c0002460e0 by goroutine 53:
  github.com/go-redis/redis/v7.(*Client).WithContext()
      /Users/user/go/pkg/mod/github.com/go-redis/redis/v7@v7.0.0-beta.3/redis.go:513 +0xa5
  main.main.func1()
      /Users/user/workspaces/scratch/goredisrace/main.go:28 +0xff

*Client.WithContext and *ClusterClient.WithContext may need to clone *client and *clusterClient respectively too. init() will assign to c.process, which is currently shared memory.
*Client code:
https://github.com/go-redis/redis/blob/2c55c0b55a2b6cb28c73b59bef091a0790ee1937/redis.go#L509-L517

Done


reduce and reduceRight support other accumulator types, fix #10

What does this pull request add, improve or fixes?
Fixes https://github.com/nicolas-van/modern-async/issues/10
Can you explain why this improvement or fix may be useful?
As discussed in the issue. Note that the solution involves overloading the reduce and reduceRight definitions to have versions that don't include an initial value. This matches with the way it's done in the TypeScript definitions for the native reduce and reduceRight
If you changed the code, have you added enough unit tests?
This is a TypeScript definitions fix, so there's no tests to add

Seems good to me, I merged it and will make a new release.

Version 1.1.3 was released with that fix. Thank you for your contribution.

Version 1.1.3 was released with that fix. Thank you for your contribution.

Very happy to contribute, you've developed a really great package.


Sticky did not work well

TypeError
Cannot read property 'sticky' of undefined
https://codesandbox.io/s/react-table-sticky-official-jivux

Hi @jtamm-red
Please, take a little time to explain what you do with react-table and your data, before juste say "TypeError" like a simple error logger.
So, I take time to understand what you try to do with your data, and you simply use an undefined column firstElement . So sticky work well, your columns props is just invalid.


Is there any way to for more control via controlnet?

Only way currently is using the CogVideoX-Fun 1.1 "pose" version, it's meant to be used with dwpose/openpose inputs but it does seem to accept all kinds of inputs. It's text conditioned only so no img2vid available with control yet.

@kijai
https://github.com/TheDenk/cogvideox-controlnet
I've just found this.


Cleanup register-device getting started page

Fixed trademark and heading issues. Changed markdown to use semantic newlines. Reduced wordiness.
QA Steps: Ran linkcheck. Final run an issue on a different page with an external link showed up, this is an external issue and can be ignored. Rendered and checked html output for correct visual formatting. Linted.
No Jira issues to tag, routine cleanup.
Signed-off-by: Katrina Prosise<EMAIL_ADDRESS>Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Routine cleanup.
Checklist

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[x] Review for wordiness
[x] Match tone and style of page/section.
[x] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[x] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Docs for b13bf9d19b066050b1019549027974a2a787a9d4 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/1915/docs/artifacts/html/index.html

Docs for 89c6c2ab67461a30acb11ab8839ce546aea01f98 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/1918/docs/artifacts/html/index.html

Docs for 2b9aa394a7a79cb49f75324b508ae6235fbfe040 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/1919/docs/artifacts/html/index.html


[warning] can't connect to cluster node

Environment

VerneMQ Version: 0.15.3
OS: 64bit Amazon Linux 2016.09

Expected behavior
No warning in console.log
Actual behaviour
In a two node cluster setup, on both machines, the following warning is printed to console.log every second.
Node<EMAIL_ADDRESS>2017-04-14 18:53:55.133 [warning] <0.599.0>@vmq_cluster_node:connect:215 can't connect to cluster node<EMAIL_ADDRESS>due to econnrefused

Node<EMAIL_ADDRESS>2017-04-14 18:53:55.133 [warning] <0.599.0>@vmq_cluster_node:connect:215 can't connect to cluster node<EMAIL_ADDRESS>due to econnrefused

I have a setup described in https://github.com/erlio/vernemq/issues/363, except all the listeners use CONTAINER_IP_ADDRESS instead of AWS_HOST_IP_ADDRESS

Hi @rpavlovs
The address/port  configured in listener.vmq.clustering has to be reachable from the other VerneMQ instances. The log message indicates that it cannot setup the connection.

Hm... This means that currently there is no way to set up clustering with Docker+AWS. If I use instance host IP for listener.vmw.clustering, Verne errors out and exits (see linked issue).

Would using the host network help in this case?

Oh, I didn't know about the host networking mode. Will try and let you know.
Thanks

Great. Host networking should also give you better networking performance, which is definitely beneficial for VerneMQ clustering.

i guess using <IP_ADDRESS> inside the container can fix it.

@dergraf
I did some testing and host networking mode solves the problem. Unfortunately, ElasticBeanstalk that I was hoping to use, doesn't support it... (https://forums.aws.amazon.com/thread.jspa?threadID=177850)
I've set up ECS service, but ECS does not support exposing more that one container port to load balancer. This means that http interface can't be exposed :( (https://groups.google.com/forum/#!topic/terraform-tool/0WDwGbaDqYQ)
I'm still looking for a good Verne setup architecture on AWS...
It's interesting that, even though the warning appears in logs I'm still able to receive messages sent to nodes different than the one I'm connected to. Are there any other functionality that is broken when I see this warning?
@codeadict
listener.vmq.clustering = <IP_ADDRESS>:44053 generates the following warning every second:
[warning] <0.1977.0>@vmq_cluster_com:loop:74 terminate due to remote_node_not_available

See @dergraf comment: https://github.com/erlio/vernemq/issues/364#issuecomment-294221671

@rpavlovs I don't know Elastic Beanstalk. However, if it doesn't allow you to use the host networking mode with Docker I would discourage to use it due to performance penalties.

Closing this, please reopen if the issue remains


[flutter_conductor] Support publishing to multiple channels

Fixes https://github.com/flutter/flutter/issues/94578

FYI @itsjustkevin


Proposal: A dedicated kaiascan SDK in rust

Description
This proposal outlines the need for a dedicated KaiaScan SDK in Go, detailing its benefits and functionalities. KaiaScan, a blockchain explorer specifically designed for the Kaia ecosystem, provides real-time data tracking and insights into token movements, transactions, and more.
Core functionalities:
Token information retrieval
Transaction tracking
Block information
Contract Interaction
Why proposal?
It simplifies the integration of kaiascan functionalities into application.
It encapsulate api calls making it a user-friendly approach to access kaia blockchain information.
Enhanced developer experience
Bounty track
Developer tool

Approved to proceed.

Done: https://dorahacks.io/buidl/20040
Github: https://github.com/PaulElisha/kaiascan-sdk-rs

Approved for 1500 KAIA bounty

closing


Allow txindex to be off in full mode

I originally made this change to see how stuff would break... But then I had a problem... Nothing broke!
I'm not sure if the break if actually much deeper, and I just don't see everything breaking, but this change allowed me to start a wallet, with txindex off. When I did so, I expected IS to crash the wallet or something, but it... didn't... IS worked... Chainlocks worked... I think this is a result of the implementation of LLMQ based IS. Under the old IS model, individual inputs received locks, whereas in the new model (If I recall / read the code correctly) the entire tx gets locked. So whereas in the old system, you needed txindex when receiving IS, now you don't.
This also has the added benefit of allowing people to run pruned nodes which have all of Dash's lovely features like privatesend, instantsend and chainlocks enabled automagically
(Assuming everything is good in this PR) Regarding whether to merge into 0.16 or 0.17 I don't have much of a preference, ofc since it is my change I am going to want to see it in 16, however, this isn't a bug fix, and would likely cause more testing to be needed. Basically emotionally I want it in 16, but logically I think it should probably be after 16

In theory, https://github.com/dashpay/dash/pull/3484/commits/c78bd0b47fcd265537d9ba77ff7fd765259f75d6 would solve that issue. However I'm not sure this is the best way to go about this.
Probably best to do https://github.com/dashpay/dash/issues/3485 first and then once all is said and done with fLiteMode maybe look at being able to disable txindex w/o losing IS/CL functionality

Would also have to tweak this https://github.com/dashpay/dash/blob/develop/src/masternode/masternode-payments.cpp#L119

Superseded by https://github.com/dashpay/dash/pull/3488


ENH: Check more FIF constants

[x] remove remaining XXX from test_constants.py
[x] make sure we completely represent some of the fiff-constants fields, such as coils
[x] ensure that the coils all have entries in coil_def.dat
[x] merge Elekta's coil_def.dat with ours

This is now complete


Ignore tests requiring firrtlEquivalenceTest() if yosys isn't available.

Users may not have yosys installed. Ignore ConstantPropagationEquivalenceSpec tests using firrtlEquivalenceTest() if yosys is not available.

Is it possible to add the assume to firrtlEquivalenceTest? It might require some trickery but it would be cool because then we couldn't mess it up by forgetting to add that assumption.
Also is there a way to make this less easy to mess up. Imagine if we were to port our CI from Travis to Circle but forget to install yosys, sbt test would then pass for these tests even when in that case we want it to error if yosys isn't installed. Any thoughts?

@ducky64 had a similar response to my PR to tag chisel tests requiring a backend. Perhaps it's time to delve into the ScalaTest machinery.
This shouldn't be an issue on a move to CircleCI, since we run the tests inside a docker container that has yosys installed - required by .circleci/run_formal_checks.sh.
sbt does report ignored tests. Anything diligent about running tests, should pay attention to that.

Yeah I agree we're unlikely to mess this up (especially because of run_formal_checks). However, as a general pattern and for future maintainability, I'm a little concerned about tests passing due to an incomplete setup.

Just to be clear, these tests don't pass if there's no yosys; they're CANCELED (not IGNORED as I reported earlier).
If testing FIRRTL requires yosys, then that should be made explicit. We should have a testPrepSpec that verifies that for any external tools required for testing, the correct version is installed.

CANCELED still gives a green [success] at the end of sbt test though, I'm happy to have them cancelled but as you suggested, we should have a TestingEnvironmentSpec or something that checks for Verilator, Yosys, and any dependencies of theirs (Verilator needs a c++ compiler for example)

Don't want sbt test to pass if someone is missing verilator, yosys, or future dependencies
It would be fine to have an additional option to sbt test to make it skip those tests (like sbt test --skip-nonScalaTests?

There's some feature for this (probably)

Also problematic, yosysEquiv can fail with the exact same input.

Decision - make yosys required for all tests to pass.


YouTube API

Describe the feature
I would like to request a YouTube API integration. It will be great to be able to start/stop Live Streaming direct from Bitifocus Companion.
Is this platform dependent (windows, mac, ..)?
Not applicable
If documentation is required to implement, do you know where to find it?
If applicable, add screenshots, protocol description PDFs, etc to help the developers along
https://developers.google.com/youtube/v3/live/getting-started
https://developers.google.com/youtube/v3/live/docs/liveStreams
Usecases
Anybody who is using YouTube Live Streaming will be able to start/stop their live stream from a single location. For example, we deployed a ATEM, AJA HELO to allow us to live streaming our services, we automated everything to use a Elgato Stream Deck using Bitifocus, and the only task that we were not able to accomplish, it is the YouTube Live Streaming end event.

Most excellent! I'll test as soon as I can. Thanks so much for working on this!

So, I apologize for the noob question, but on a Mac, how can I install this module? I read the companion module development guide (which is quite nice, by the way) but it doesn't explain how to install someone else's module, specifically on a Mac. . . Thanks in advance!

Hi @whizkidTRW!
I have quickly looked into the Companion 2.0 package for Mac and I don't know how to add it there. However, it should be possible to git-clone the main Companion repository, then clone this module to the lib/module subdirectory and then follow DEVELOPER.md.
git clone https://github.com/bitfocus/companion.git                     companion
git clone https://github.com/bitfocus/companion-module-youtube-live.git companion/lib/module/youtube-live
# < developer.md >

Best regards,
Jakub

Hi all,
Development update:
youtube-live module was added into Companion by core developers. Now it is available in experimental releases: https://bitfocus.io/companion/download/builds/

So I’m using this now in production and it works great. Is there a way to add a preset that toggles an event based on the stream key specified? Or just whatever the current live event is? That way we don’t have to reconfigure companion each week just to control a new event.

Is there a way to add a preset that toggles an event based on the stream key specified?

I think this is implementable, but there are some caveats. Currently buttons are bound to specific YT events/broadcasts. The good thing about this is that each event has exactly one stream bound to it and YouTube makes it easy to obtain the ID of that stream. Finding the event ID corresponding to a stream ID is more difficult: one stream key can be bound to multiple events & multiple YT events have to be checked to see if they are bound to the given stream ID.

Or just whatever the current live event is?

This would allow us to preserve the current event->stream mapping, but we would still have to choose one event from zero to N live events. Picking the newest or the oldest one might be sufficient though.
While it does feel a bit hackish to me, I would instead propose adding a "default event" field to the module configuration. Then a special event named "default" could be selected for each button/feedback/.... This would keep the configuration deterministic and it would simplify this type of reconfiguration.

What we need is the next live event of the channel loaded in a toggle button in Companion when we start Companion (or refresh the youtube info). That way we do not have to change the button every week. It is almost the same question of  whizkidTRW, but related to the channel.

Agreed! This would be so great to have.
Todd Witten
<EMAIL_ADDRESS>On Mon, Nov 9, 2020 at 8:05 AM Frans Bosman<EMAIL_ADDRESS>wrote:

What we need is the next live event of the channel loaded in a toggle
button in Companion when we start Companion (or refresh the youtube info).
That way we do not have to change the button every week. It is almost the
same question of whizkidTRW, but related to the channel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-youtube-live/issues/34#issuecomment-724034029,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWZ2KR73TE2XJFLJXP64M3SO7ZMBANCNFSM4NERN7YA
.

Amazing work! Tested out the module and no apparent bugs yet:)
Would be amazing to have that feature mentioned earlier that would allow the latest stream created to be selected. We have probably a set of 5-6 buttons (such as refresh, start stream, end stream, stream status, etc.) that have to be updated individually every time we create a new stream (having an option to select the newest event would be PERFECT).
Please do let us know if there is any way we could help ::)

I agree, this is a fantastic add on for automating youtube control.
I managed to set it up at home without real hassle using the provided guide and deployed it on streaming site just by importing configuration.
After testing, I second that I would like to have a few streams that could be configured in the button setup to be stream #1, #2, #3 etc. and using corresponding variables for button text in such a way that the Stream Deck configuration can be "statically defined" and still be able to show and test/start/stop and get feedback status on the streams configured in the Youtube channel.

I agree, this is a fantastic add on for automating youtube control.
I managed to set it up at home without real hassle using the provided guide and deployed it on streaming site just by importing the companion configuration.
After testing, I second that I would like to have a few streams that could be configured in the button setup to be stream 1, 2, 3 etc. and using corresponding variables for button text in such a way that the Stream Deck configuration can be "statically defined" and still be able to show and test/start/stop and get feedback status on the streams configured in the Youtube channel.
In our configuration, a Church, we typically have one active stream pending for each Sunday and it would be really nice not having to change all the parameters for the youtube buttons just to get the new stream to show up.

I am in the exact same boat.  I just setup streaming for my church and I am looking for ways to make things easier for our volunteers so I do not need to be running the live stream every Sunday.  I am almost where I want to be and this kind of update to automatically have it work with the next live stream would be great.

I know this has been dormant for a while, don't know if anyone is still interested.
I notice that, if I set "How many broadcasts to fetch from YouTube" to 1, and periodically execute a "YouTube: Reload everything from YouTube" the the volunteers only need to click on the various "Broadcast" drop-downs and the right answer is the only one available to them. Still more work - and more access to the configuration pages - than I'd like for them, but it's bearable.
I like to have a button that shows YouTube's reported statuses with the variable text, $(YouTube:health:aBcDeFghI)\n$(YouTube:lifecycle:aBcDeFghI) but copying these from the variable list and putting them on the button is really a bridge too far for the volunteers.
I'd love if someone could make these work with index numbers instead of the literal names of the streams

Mark, I couldn’t agree more!
On Tue, Aug 3, 2021 at 9:41 PM mark-epstein @.***>
wrote:

I know this has been dormant for a while, don't know if anyone is still
interested.
I notice that, if I set "How many broadcasts to fetch from YouTube" to 1,
and periodically execute a "YouTube: Reload everything from YouTube" the
the volunteers only need to click on the various "Broadcast" drop-downs and
the right answer is the only one available to them. Still more work - and
more access to the configuration pages - than I'd like for them, but it's
bearable.
I like to have a button that shows YouTube's reported statuses with the
variable text, $(YouTube:health:aBcDeFghI)\n$(YouTube:lifecycle:aBcDeFghI)
but copying these from the variable list and putting them on the button is
really a bridge too far for the volunteers.
I'd love if someone could make these work with index numbers instead of
the literal names of the streams
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-youtube-live/issues/34#issuecomment-892315503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWZ2KTENBGWXJVLK5A6ZODT3CSFVANCNFSM4NERN7YA
.
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&utm_campaign=notification-email
.

--
Todd Witten
@.***

I’m working on an update for this nice module which add’s an “upcoming” broadcast to the choices, feedbacks and variables. This will address the first planned broadcast after “now”.
It will take me some days.
Regards,
Frans Bosman
Verstuurd vanaf mijn iPhone
Op 4 aug. 2021 om 04:43 heeft whizkidTRW @.***> het volgende geschreven:

Mark, I couldn’t agree more!
On Tue, Aug 3, 2021 at 9:41 PM mark-epstein @.***>
wrote:

I know this has been dormant for a while, don't know if anyone is still
interested.
I notice that, if I set "How many broadcasts to fetch from YouTube" to 1,
and periodically execute a "YouTube: Reload everything from YouTube" the
the volunteers only need to click on the various "Broadcast" drop-downs and
the right answer is the only one available to them. Still more work - and
more access to the configuration pages - than I'd like for them, but it's
bearable.
I like to have a button that shows YouTube's reported statuses with the
variable text, $(YouTube:health:aBcDeFghI)\n$(YouTube:lifecycle:aBcDeFghI)
but copying these from the variable list and putting them on the button is
really a bridge too far for the volunteers.
I'd love if someone could make these work with index numbers instead of
the literal names of the streams
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-youtube-live/issues/34#issuecomment-892315503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWZ2KTENBGWXJVLK5A6ZODT3CSFVANCNFSM4NERN7YA
.
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&utm_campaign=notification-email
.

--
Todd Witten
@.***
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

That would be amazing. Can’t wait to see the progress and let me know if you need any help or testing done! :)
On Wednesday, August 4, 2021, 12:49:54 AM PDT, Frans Bosman @.***> wrote:
I’m working on an update for this nice module which add’s an “upcoming” broadcast to the choices, feedbacks and variables. This will address the first planned broadcast after “now”.
It will take me some days.
Regards,
Frans Bosman
Verstuurd vanaf mijn iPhone
Op 4 aug. 2021 om 04:43 heeft whizkidTRW @.***> het volgende geschreven:

Mark, I couldn’t agree more!
On Tue, Aug 3, 2021 at 9:41 PM mark-epstein @.***>
wrote:

I know this has been dormant for a while, don't know if anyone is still
interested.
I notice that, if I set "How many broadcasts to fetch from YouTube" to 1,
and periodically execute a "YouTube: Reload everything from YouTube" the
the volunteers only need to click on the various "Broadcast" drop-downs and
the right answer is the only one available to them. Still more work - and
more access to the configuration pages - than I'd like for them, but it's
bearable.
I like to have a button that shows YouTube's reported statuses with the
variable text, $(YouTube:health:aBcDeFghI)\n$(YouTube:lifecycle:aBcDeFghI)
but copying these from the variable list and putting them on the button is
really a bridge too far for the volunteers.
I'd love if someone could make these work with index numbers instead of
the literal names of the streams
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-youtube-live/issues/34#issuecomment-892315503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWZ2KTENBGWXJVLK5A6ZODT3CSFVANCNFSM4NERN7YA
.
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&utm_campaign=notification-email
.

--
Todd Witten
@.***
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Hi,
I have a first alpha version for testing: https://wetransfer.com/downloads/a86a62aa2e3ef5473c3e6c09d5c8789e20210806135531/adc1d441547cdbd47b824824ce9f3abb20210806135604/d2a05b?utm_campaign=WT_email_tracking&utm_content=general&utm_medium=download_button&utm_source=notify_recipient_email
In the presets you will find an extra category "Upcoming". This has a latch button which will display the upcoming broadcast. First press will start the broadcast, second press will stop the broadcast. The feedback is standard like other feedbacks.  If you add a button to refresh the youtube info, the next upcoming broadcast will be loaded. Can you please run some tests? It is still alpha!!

My apologies @fbosman, but I won’t be downloading an .exe file to test this out. What exactly is that file anyways? Seems fishy to me. Too much of a risk.
Why not create a fork of the project?
Thanks.

This is a companion installer. Nothing more than that. But I can setup a fork.
Met vriendelijke groet,
Frans Bosman
Verstuurd vanaf mijn iPhone
Op 6 aug. 2021 om 16:53 heeft validlogin @.***> het volgende geschreven:

My apologies @fbosman, but I won’t be downloading an .exe file to test this out. What exactly is that file anyways? Seems fishy to me. Too much of a risk.
Why not create a fork of the project?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@fbosman Any update on the new feature and/or Pull Request?

It worked during my first test but unfortunately I just get a "instance(YT): YT Broadcast query failed: TypeError: Cannot read property 'id' of undefined" error ever since my first reboot. Any ideas?

@fbosman, do you have the possibility to check in your update to your forked repo?

Hi,
Due to holiday and illness I was not able to setup a forked repo. I made the changes on the JavaScript library and am busy to set them up for the typescript sources. This will take me this week or so as I have to do this in my free time.
I'm sorry the development cannot be faster.

No problem @fbosman, thanks for breaking the silence. 😀
Hope you are well now, take care!

I really hope that this can be updated to work in the following fashion:

Add variables for CurrentScheduled stream, which look at the list of scheduled livestream events and by their scheduled time picks the one which is either ongoing now, or closest to now in the future.
(much lower priority) Add support for various languages in the output strings or status strings.

This will allow us to configure one button, once and for all, that will always automatically be tied to the nearest future or current show. The language support will make this more useful globally.
I am a developer and although I have zero experience with this particular environment and programming language, I can read the code and try to figure it out on my own. But I would appreciate some help or pointers. I will probably fork the code soon and take a stab at it.

Following!
Todd Witten
@.***
On Mon, Jan 17, 2022 at 9:57 AM scientastic @.***>
wrote:

I really hope that this can be updated to work in the following fashion:

Add variables for CurrentScheduled stream, which look at the list of
scheduled livestream events and by their scheduled time picks the one which
is either ongoing now, or closest to now in the future.
(much lower priority) Add support for various languages in the
output strings or status strings.

This will allow us to configure one button, once and for all, that will
always automatically be tied to the nearest future or current show. The
language support will make this more useful globally.
I am a developer and although I have zero experience with this particular
environment and programming language, I can read the code and try to figure
it out on my own. But I would appreciate some help or pointers. I will
probably fork the code soon and take a stab at it.
—
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-youtube-live/issues/34#issuecomment-1014687116,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWZ2KXIKTWO2E3JPETMZRDUWQ4ANANCNFSM4NERN7YA
.
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.
You are receiving this because you were mentioned.Message ID:
@.***>

@scientastic  - Support for the variables for the next scheduled stream is now merged in #64 #66
I don't think an official release has been made since it merged, but if you build source or grab one of the nightly's it's in there. Been using this functionality for a few weeks and it's a game changer!

Thanks! I actually did fork the code and started looking at it and saw the "unfinished_" variables. I suspected it was in progress but hadn't had a chance to get further.
Is there a good quick guide to how to build this module and then start using it? I have the 'companion' project cloned and am going through the developer guide, but maybe you could help me cut to the chase?
Thanks again!

Easiest way to run a recent dev build is to grab one of the latest versions from https://bitfocus.io/user/downloads .
Once you sign in, click the beta builds link here:

That page has the most recent test builds that should have the code.  If you want to build it yourself you can get started here: https://github.com/bitfocus/companion/wiki/Module-Development. It will depend on your platform and specific setup on how to best do that.

Thanks again! I will probably work with the beta builds and not try to build myself at the moment. However, I have been all over the Wiki and don't yet see any instructions for 1. compiling/building a module and 2. how to load it into Companion once it is built. I'm not a Node developer so maybe it is something that seems obvious to everyone on the project but is not obvious to me? Anyways, a brief write-up on that would be very welcome :)

@scientastic currently there isn't a way build individual modules then "load" them to Companion.  The software has to be built as a single package.  The beta builds are the way to go.

I see, thanks. The fact that the modules have their own separate github repos was confusing me. I now see they also exist in 'companion/node_modules' as well.

Yeah, they used to live in companion/lib/module/ as git submodules but that became a scaling problem.  The separate repos are for permissions control since there are a ton of developers and the load in the Companion repo would be unmanageable in terms of pull requests and issues for the individual modules.  Keeps things tidy this way.  And eventually we're working toward what you've asked for documentation on, but that day has not yet arrived.

Am I supposed to have to frequently reauthenticate my authorization token?  I just started using this module on a weekly basis for my church's live stream and every week I have to go in and reauthenticate for some reason.  I don't see an option anywhere obvious in the google services API for a "keep alive" or something similar.  Am I missing something, or is this just how it works?
Thanks for all of your efforts!  Aside from the frequent login issue I'm experiencing, this does the job well!

This is related to #72.

I'm curious why this issue remains open. Does anyone think that there are items in here that are not complete? I don't see any.


Needs 2 Factor Authentication

https://us-cert.cisa.gov/ncas/current-activity/2021/08/30/cisa-adds-single-factor-authentication-list-bad-practices
Now single factor authentication is a bug.


Unchecking TestCase appear to activate rollup/down

This is a regression between the old dialog to the new.

Can't reproduce now. Might be small hit area. Can revisit once final UI is in place.


markeplace link forwards to incorrect idp

Date:2016/10/19
[Steps to reproduce]

IDPs IDP1(used as default), and IDP2 exist
administrator (platform) uses IDP1, creates organization Org1 (tech provider and supplier), Org1Admin
which is in IDP2
administrator creates marketplace M1, M2 and owner is set as Org1, and marketplaces are in IDP2
log in as Org1Admin with http://estsdehn.intern.est.fujitsu.com:8180/oscm-portal/?tenantID=IDP
work in portal only and publish a service to M1 (I do not switch to marketplace)
create Customer organization in IDP2 (customer admin id already exists in IDP2) and assign M1
logout
customer receives mail with marketplace link
customer presses on link, and is brought to M1
e.g. http://estsdehn.intern.est.fujitsu.com:8180/oscm-portal/marketplace?mId=a8b9eb74
customer presses login

[Expected result]
customer is forwarded to IDP2 (which is defined for M1)
[Observed result]
customer is forwarded to IDP1 (default IDP)
[Details]
Blocker because customer cannot log in at marketplace

If we use directly the marketplace link, without going to the administration portal previously, the user is redirected to the default tenant IDP, not the one from the marketplace.
@DawidCh, as we've discussed, the tenantID is expected in the SessionBean for the marketplace access. If it is empty, it is taken from the http session. The AuthorizationFilter saves tenantID in the http session.  During the debugging, I can notice that the direct request of the marketplace URL does not hit the code, where the tenantID is saved in the http session. So the SessionBean will find an empty tenantID and set the default one.

@DawidCh
Please improve the spelling of added message in
/oscm-portal/javares/org/oscm/ui/resources/Messages_de.properties, f.e.
error.tenant.marketplaceRemoved=The selected marketplace doesn''t exist anymore.
Pass to @misako0927 for Japanese translation.

[Details of fix]
The bug was caused by issue with registering customer process. Tenant was not assigned to customer's organization during that process. All the customers were assigned to the same (default) tenant.
Code has been adapted and tenant is being assigned to the customer's organization.

verified with Build 24.10.2016


Tan11389/navigate route fix

Description
Comments out Esri.samples because the QTextToSpeech-based class registered to it is not supported
Type of change

[x] Bug fix
[ ] New sample implementation
[ ] Sample viewer enhancement
[ ] Other enhancement

Might consider backporting to main as well for 200.0


Upgrade version.mockito 3.5.9 -> 3.5.10

This PR contains the following updates:

Package
Update
Change

org.mockito:mockito-inline
patch
3.5.9 -> 3.5.10

org.mockito:mockito-core
patch
3.5.9 -> 3.5.10

Release Notes

mockito/mockito
v3.5.10
Compare Source
Release notes were automatically generated by Shipkit
3.5.10

2020-09-03 - 2 commits by Rafael Winterhalter - published to
Escape mock during method dispatch on mock to avoid premature garbage collection. (#2034)
Exception "The mock object was garbage collected." (#1802)

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade Mockito 3.5.9 -> 3.5.10

See:
- https://github.com/mockito/mockito/blob/release/3.x/doc/release-notes/official.md
- https://github.com/mockito/mockito/releases/tag/v3.5.10
- https://github.com/mockito/mockito/compare/v3.5.9...v3.5.10


SQLDroid connection pooling issue

I am getting random errors like below (attempt to reopen closed connection etc).
It seems SQLDroid keeps track of open connections and closes the underlying database when no connections are left open. But it seems to close live connections sometimes - I am not sure how.
When I do getConnection and close on a connection - I assume no one else can close these connections before I close it. But it seems SQLDroid does close the connection in the background. How do I stop this ?
11-01 19:52:13.523: E/MetarMap(26622): java.lang.IllegalStateException: attempt to re-open an already-closed object: SQLiteDatabase: /storage/sdcard0/Android/data/com.metarmap.tab/files/databases/prefs.sqlite
11-01 19:52:13.523: E/MetarMap(26622):     at android.database.sqlite.SQLiteClosable.acquireReference(SQLiteClosable.java:55)
11-01 19:52:13.523: E/MetarMap(26622):     at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1310)
11-01 19:52:13.523: E/MetarMap(26622):     at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1253)
11-01 19:52:13.523: E/MetarMap(26622):     at org.sqldroid.SQLiteDatabase.rawQuery(SQLiteDatabase.java:116)
11-01 19:52:13.523: E/MetarMap(26622):     at org.sqldroid.SQLDroidPreparedStatement.executeQuery(SQLDroidPreparedStatement.java:212)

This should be fixed by my pull request https://github.com/SQLDroid/SQLDroid/commit/4666757512f8019ad1f11eed3c5d5c16c7bb7297

The pull request 4666757 looks good to me.


Use makefile instead of calling build-sphinx ?

Users may have customised their makefile to include additional steps while building the html, but these are then lost when using because instead of calling
make html
it calls
sphinx-build -b html "$doc_dir" "$tmp_dir" $INPUT_SPHINX_OPTIONS
Is there any reason not to call like this?
make html BUILDDIR="$tmp_dir" SPHINXOPTS="$INPUT_SPHINX_OPTIONS"
which would, I think, achieve the same.
The only change later in main.sh would be
rm -rf $tmp_dir/.doctrees
cp -vr $tmp_dir/. $INPUT_TARGET_PATH

becomes
rm -rf $tmp_dir/html/.doctrees
cp -vr $tmp_dir/html/. $INPUT_TARGET_PATH

because make by default will add /html for that build

Sure, I will add this in v3.


Monolog 2.x compatabiliy

New Requirement: PHP 7.2+
This should fix https://github.com/koraktor/steam-condenser/issues/329
Testing output seemed to be identical to the current branch
One caveat, the default handler right now only prints to STDOUT, i'm not entirely sure if that was the configuration on the original, but it's what it seemed to be, if you want to log to STDERR, or a log file, or something else, just let me know, or of course feel free to edit the PR
Thanks!

The above build errors seem to be from mostly upstream errors (5.4 and 5.5 binaries don't exist and 404) the 5.6 fails because we require php 7.2 now, I don't know if telling travis to run on 7.2 is something that can be done via a PR or not..

Run 72
On Mon, May 4, 2020, 1:24 PM Zachary Craig<EMAIL_ADDRESS>wrote:

The above build errors seem to be from mostly upstream errors (5.4 and 5.5
binaries don't exist and 404) the 5.6 fails because we require php 7.2 now,
I don't know if telling travis to run on 7.2 is something that can be done
via a PR or not..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/koraktor/steam-condenser-php/pull/24#issuecomment-623596326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMJ5EDLY77PJXTWQJSSLALRP325RANCNFSM4MYYT4TQ
.

7.2
On Mon, May 4, 2020, 2:13 PM Jack Paior<EMAIL_ADDRESS>wrote:

Run 72
On Mon, May 4, 2020, 1:24 PM Zachary Craig<EMAIL_ADDRESS>wrote:

The above build errors seem to be from mostly upstream errors (5.4 and
5.5 binaries don't exist and 404) the 5.6 fails because we require php 7.2
now, I don't know if telling travis to run on 7.2 is something that can be
done via a PR or not..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/koraktor/steam-condenser-php/pull/24#issuecomment-623596326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMJ5EDLY77PJXTWQJSSLALRP325RANCNFSM4MYYT4TQ
.

I'm probably going to run php 7.3 in the CI stuff, since 7.2 is actually unsupported.
https://www.php.net/supported-versions.php
I'd feel silly going through all this trouble to update only for it to be updated to a non-supported php version.
Thoughts?

@koraktor how do you feel about upgrading the tests / some other changes?
PHPUnit removed the assertAttribute method a while back, I started upgrading the tests, but haven't poked at those changes with the assertAttribute changes yet, as I didn't want to go modifying the source files to add accessors before you said so
https://github.com/zack6849/steam-condenser-php/tree/travis-php7
I've gotten it more or less even with master, build status wise, aside from the risky tests because of no assertions (i just commented out the assertAttribute lines to be filled in later)

When it comes to this type of thing I would have to trust that you would
make the right decision to help me and I would be grateful for that. My
knowledge of this sort of thing only goes so far.
On Mon, May 4, 2020, 2:21 PM Zachary Craig<EMAIL_ADDRESS>wrote:

@koraktor https://github.com/koraktor how do you feel about upgrading
the tests / some other changes?
PHPUnit removed the assertAttribute method a while back, I started
upgrading the tests, but haven't poked at those changes with the
assertAttribute changes yet, as I didn't want to go modifying the source
files to add accessors before you said so
https://github.com/zack6849/steam-condenser-php/tree/travis-php7
I've gotten it more or less even with master, build status wise, aside
from the risky tests because of no assertions (i just commented out the
assertAttribute lines to be filled in later)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/koraktor/steam-condenser-php/pull/24#issuecomment-623625738,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMJ5EBRQLJYNWUAYBILWUDRP4BRBANCNFSM4MYYT4TQ
.

Yes mavprolucky is me
On Tue, May 5, 2020, 8:57 AM Zachary Craig<EMAIL_ADDRESS>wrote:

@zack6849 commented on this pull request.
In lib/SteamCondenser.php
https://github.com/koraktor/steam-condenser-php/pull/24#discussion_r420087384
:

return new Logger($name);

$logger = new Logger($name);
$logger->pushHandler(new StreamHandler("php://stdout"));
return $logger;

Also, is @mavprolucky https://github.com/mavprolucky you or something?
I'm very confused about these comments being left on this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/koraktor/steam-condenser-php/pull/24#discussion_r420087384,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMJ5EE52K2N7B6R2AAOKJTRQAENBANCNFSM4MYYT4TQ
.

@koraktor i've removed the handler, this has been sitting for a while, is there anything else needed testing wise for this to get merged?

@koraktor i've removed the handler, this has been sitting for a while, is there anything else needed testing wise for this to get merged?


torchaudio.models is not imported on top-level

Par #1660. The following should work.
import torchaudio

model = torchaudio.models.XXX(...)

Shall we add models in __init__.py?

Shall we add models in __init__.py?

Yes!

addressed by #1664


explorer looses mouse over hover

#6536

reveal explorer
notice how files change background on mouse over
select a file for preview
close file from then Open Editors group
the last files has no background mouse over behaviour anymore

Can not repro any more. There have been a lot of changes coming in regarding open editors so some might have fixed this. Please reopen if you still see this.


Non static method shouldn't be called statically

I'm trying to use Twitter::getSearch() in a laravel seeder, getting the error that Non static method shouldn't be called statically.

I was using the wrong use statement


compile forces .sln save

since I updated to the latest version (skipping ~ 2 month time), I get my .sln file force-saved as I invoke clang compoile.
My projects include a machine-local .props and it has some project renaming like:

0 fem

this works fine and is needed to make the projects appear in prop[er order in the solution explorer.
This causes the following change in the .sln:
-Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "fem", "fem.vcxproj", "{2C5475D2-ED0E-439B-9E19-FF085365FAE3}"
+Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "0 fem", "fem.vcxproj", "{2C5475D2-ED0E-439B-9E19-FF085365FAE3}"
In normal VS work the sln is not marked dirty internally, only actual change like add/remove project forces a save. But current CPT does something along those lines.
The effect is more than annoying, as the .sln file is obviously under git and creates a delta, it must be reset before any operation or risk getting committed with changes.  Ignore does not work on contained files....
Please locate the change that caused this and at least allow to turn it off.

Hi,
This issue was fixed and it will be available in the next Clang Power Tools version.
Thank you for your feedback!

Hi,
I made a fix which will be available in the next Clang Power Tools version (v4.8).
After you install the latest build coming out very soon could you please confirm the issue was solved and close it.
I will let you know when the CPT v4.8 will be online.
Best regards,
Ionut

Clang Power Tools v4.8 is now online. Please let me know if the issue is still there.

Looks fixed now! :)


the binder URL should be changed from master to main

The widget at the top of this page
https://ml.dask.org/
points to
https://mybinder.org/v2/gh/dask/dask-examples/master?filepath=machine-learning.ipynb
but should point to
https://mybinder.org/v2/gh/dask/dask-examples/main?filepath=machine-learning.ipynb

Thanks for pointing this out @murphyk. This should be fixed by https://github.com/dask/dask-ml/pull/792


Do upload a webjob via kudu api still work ?

I use postman to upload a webjob zip file using kudu url https://mysite.scm.azurewebsites.net/api/continuouswebjobs/my_webjob
but it always throw 403 error something like
`Error 403 - This web app is stopped.
The web app you have attempted to reach is currently stopped and does not accept any
	requests. Please try to reload the page or visit it again soon.
If you are the web app administrator, please find the common 403 error scenarios and`
I am pretty sure that I have provided Authorization header properly.
Anything to modify to make it work
Thanks,
NT

I guess the reason is I am using not enough permission account.


Add support for determining trap "status"

Determine severity based on MIB data.

The extension currently defaults the check status to 0 or "OK". The check status is determined by trap varbind mapping or special conditions (e.g. trap oid symbolic name contains "down").