user-1
June 9, 2023, 3:12am
1
This topic was automatically generated from Slack. You can find the original thread here .
Hey, having the same issues as Raymond above. RSS feed fired off randomly with roughly 10 items deep each time. You can see the code there, the feed, and what it should look like. This has happened a few times now and is somewhat disruptive. Just wondering if there’s a fix or something I can do, or if it’s something more inherent in the system.
user-1
June 9, 2023, 3:12am
2
Hi, can you please share the URL to the source that is over-emitting?
The unique code in the URL (formatted like dc_*********) is what we need to help troubleshoot.
user-1
June 9, 2023, 3:12am
3
It looks like async options accepts an object with arbitrary keys like org here:
async options() {
const organizations = await this.getOrganizations();
return organizations.map((organization) => organization.login);
},
},
repoFullname: {
label: "Repository",
description: "The name of the repository. The name is not case sensitive",
type: "string",
async options({ org }) {
const repositories = await this.getRepos({
org,
});
return repositories.map((repository) => repository.full_name);
},
},
repoOrg: {
label: "Organization Repository",
description: "The repository in a organization",
Or like repoFullname here:
const repositories = await this.getOrgRepos({
org,
});
return repositories.map((repository) => repository.full_name.split("/")[1]);
},
},
project: {
label: "Project",
description: "The project in a repository",
type: "integer",
async options({ repoFullname }) {
const projects = await this.getRepositoryProjects({
repoFullname,
});
return projects.map((project) => ({
label: project.name,
value: project.id,
}));
},
},
user-1
June 9, 2023, 3:12am
4
I think it’s related to propDefinitions, but I wouldn’t like to define an async options method without the use of an app file and propDefinitions if possible
user-1
June 9, 2023, 3:12am
5
I’m so sorry, but I don’t know what most of those words are.https://palewebserial.wordpress.com/feed/
user-1
June 9, 2023, 3:12am
6
Here’s a link to the project, hopefully that has the information you need
user-1
June 9, 2023, 3:12am
7
That’s alright, we’ve found the cause. It was an issue with how our system caches already seen events. The issue should be resolved.
user-1
June 9, 2023, 3:12am
9
I’m not sure if this is residual things, but I had a few more trigger earlier today after you sent that message, which was, in my time at 10:23 am
