text:
Hide/show child nodes of a branch

closes #105

Do we want this to be a client-side only feature or server-side as well? Right now, there's still a bug left that the hidden state is not updated across all clients immediately (though I'd assume it calls map.draw.update() whenever something changes), but nodes are correctly hidden if the client updates the page.
Regarding an icon: Somehow very tricky to implement correctly and synchronize across all clients simultaneously.

Do we want this to be a client-side only feature or server-side as well? Right now, there's still a bug left that the hidden state is not updated across all clients immediately (though I'd assume it calls map.draw.update() whenever something changes), but nodes are correctly hidden if the client updates the page.
Regarding an icon: Somehow very tricky to implement correctly and synchronize across all clients simultaneously.

good question, I would say as it only affects visibility it should only be on the client side? otherwise people might confuse this for that a user deleted a branch.

good question, I would say as it only affects visibility it should only be on the client side? otherwise people might confuse this for that a user deleted a branch.

Does it make sense to keep the changes to the data model then? Since those changes are synced server-side, inevitably leading new clients to consider selected nodes hidden as well.

good question, I would say as it only affects visibility it should only be on the client side? otherwise people might confuse this for that a user deleted a branch.

Does it make sense to keep the changes to the data model then? Since those changes are synced server-side, inevitably leading new clients to consider selected nodes hidden as well.

Either we sync it across clients so everybody is watching the same and we have it in our data model - or we just store that property on the client side without adding it to the data model. I think I would prefer the latter one.

Works up to 99% percent, but there's still a weird and oddly specific bug where if two clients hide the same branches at the same time (so branch A and B), client A will unhide branch A when clicking on branch B.
Also missing: Changing the eye icon in the toolbar based on whether or not any child nodes are hidden.

Works up to 99% percent, but there's still a weird and oddly specific bug where if two clients hide the same branches at the same time (so branch A and B), client A will unhide branch A when clicking on branch B.
Also missing: Changing the eye icon in the toolbar based on whether or not any child nodes are hidden.

i dont really understand this problem if hiding/showing is a local operation 🤔

Works up to 99% percent, but there's still a weird and oddly specific bug where if two clients hide the same branches at the same time (so branch A and B), client A will unhide branch A when clicking on branch B.
Also missing: Changing the eye icon in the toolbar based on whether or not any child nodes are hidden.

i dont really understand this problem if hiding/showing is a local operation 🤔

It's not really consistently reproducible, but it's there - I'm trying to figure out if it maybe has something to do with how nodes selected by other users are rendered (maybe it affects the selectedNode variable in nodes.ts?). It's purely a client side issue though, most probably in how D3 renders the nodes, especially when other clients are involved.

Think I found the issue: The NodeUpdated event gets called for Client B whenever Client A hides certain nodes. However, if Client B has already hidden the same set of nodes, the "hidden" values gets overwritten with null, since UtilsService.get(newNode, propertyPath) doesn't return a proper value. That means Client B needs to click twice to unhide already hidden nodes, since it's set from null to true to false.
This can also lead to very funny issues when Client A hides a child, Client B hides every node except the root node and Client A then decides to also hide the root node, because this then hides every node except the originally hidden child.

a web socket update. An mmp event is fine as it's the local map that was updated. That should, however, not trigger a web socket

notifyWithEvent is true by default, forgot to change that to false.
Good point about the local data model - I'll have to test that. Hiding nodes is much more stable now, though I do have odd one-off cases where the parent nodes get hidden whilst children are still visible. I'll set the PR to open for review soon and then we can both test and iron out any kinks.

Updating the data model works fine even when nodes are hidden. One thing that's still missing is some visible way to tell nodes are hidden, either by updating the icon in the toolbar or by attaching an SVG icon inside the drawing area to nodes.

Updating the data model works fine even when nodes are hidden. One thing that's still missing is some visible way to tell nodes are hidden, either by updating the icon in the toolbar or by attaching an SVG icon inside the drawing area to nodes.

a small svg icon somewhere in the node sounds good 👍 the toolbar should also change (thats already done for add/remove image). But I think an additional item inside the node makes also sense as otherwise one might forget it.

Looks good. Two bugs that need more checking:

Undo/Redo is bugged - I got very strange results with it with nodes flying around in space without being attached. If possible I wouldn't consider visibility changes as un/redoable. But thats just on first thought.
Hiding nodes and then exporting the image looks like this:

Not sure what the preferred behavior for this feature is on exports. Either completely hide it (like it is now) or just show it - but without this visibility note thingy. The same is btw true for the link, which just shows "link" - but thats a separate issue.

Not sure what the preferred behavior for this feature is on exports. Either completely hide it (like it is now) or just show it - but without this visibility note thingy. The same also happens for attached links, which just show "link" - but thats a separate issue.

Re this: I think keeping notes invisible when exporting is the preferred option. However, it seems like it doesn't work with Material Icons, so I'm guessing removing the link text ("visibility_off") is the better option.

I'll take a look at undo/redo.

I don't think there's much we can do about undo/redo without a rework. The issue is that if we hide two nodes, that's two steps in the snapshot, with the farthest node being the first step in the snapshot to be undone. Similar weird behaviour can be observed when creating a node with text and undoing it: Creating the node is one step, with the text being a separate step, so it takes two presses of undo to delete a single node.

Not sure what the preferred behavior for this feature is on exports. Either completely hide it (like it is now) or just show it - but without this visibility note thingy. The same also happens for attached links, which just show "link" - but thats a separate issue.

I've removed all text on export now, so neither "link" nor "visibility_off" should appear on export.

There are still bugs: If another user adds nodes to a hidden parent node, it gets weird:

authors: JannikStreek sorenjohanson


text:
[New Feature] Add new route for dllama api for embeding models

std::vector<Route> routes = {
    {
        "/v1/chat/completions",
        HttpMethod::METHOD_POST,
        std::bind(&handleCompletionsRequest, std::placeholders::_1, &api)
    },
    {
        "/v1/models",
        HttpMethod::METHOD_GET,
        std::bind(&handleModelsRequest, std::placeholders::_1)
    }
};

in ddlama api at master branch we have only 2 routes /v1/chat/completions and /v1/models but some model looks like llama3:8b has embedding functionality. Can add you add new route for /api/embeddings ?

@b4rtaz what do you think about new route?

i mean this for ddlama api
Generate Embeddings
POST /api/embeddings

Generate embeddings from a model

i hope that i explain) @b4rtaz

what do you think about this revision or should I explain in more detail? @b4rtaz

Hello @testing0mon21 I'm not too familiar with embedding, but if I see correctly, llama.cpp supports it. This is not a priority for me, but contributions are welcome.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Update to newest Om

Signed-off-by: Robert Young rwy0717@gmail.com

Went ahead and merged--sorry if it breaks anyone. Don't forget to git submodule update --remote

source: gharchive/pull-request


text:
Added autoid to seeding scripts, changed post req, and changed CSVwrite files

Hi Andrew and Asyun,
Please review my pull request when you get a chance:
a) added auto-ID to postgres seeding scripts
b) changed post request to add actor AND link movie to actor in movie info table (db PGindex file and server index file)
c) changed csv scripts to not include id
d) installed some dependencies that somehow got removed (csv writer and faker)
e) changed read me to reflect new endpoints and descriptions
Thanks,
Uma

@ahchung23 Thanks Andrew for your review, I will merge this version and make your requested changes in my next pull request.
Best,
Uma


text:
added examples for in browser environment (and other cases)

Added examples for different ways to add plugins

@thejameskyle Since babel's plugin manager tries to load the plugin during the transformation, and if the transform occurs in the browser, plugin is unavailable.
PluginManager's code that throws the exception:
var loc = _tryResolve2["default"].relative("babel-plugin-" + name) || _tryResolve2["default"].relative(name);
if (loc) {
  var plugin = require(loc);
  return {
    position: position,
    plugin: plugin["default"] || plugin
  };
} else {
  throw new ReferenceError(messages.get("pluginUnknown", name));
}

var loc, is always null because:
resolve.relative = function (loc) {
  // we're in the browser, probably
  if (typeof Module === "object") return null;

Therefore, you have to load the plugin before the transformation, using the code in the example.

You're talking about usage with browserify or webpack?

@thejameskyle I can't tell you about browserify, becuase I haven't used it. Webpack is my use case.

To be more detailed, I am working on a fork of https://github.com/FormidableLabs/component-playground, which gives you a playground for demoing react components. The playground transforms the javascript code as it changes in the browser.

I'd rather not have that code comment (// Useful for in browser environment)

Comment removed

authors: omerts thejameskyle


text:
Add upgrade validation test

Description

To test upgrade in real scenario there should be user defined objects dependent on babelfish objects.
This commit adds upgrade validation test to identify dependencies on babelfish objects using pg_catalog.pg_depend. It runs as a part of the version upgrade test framework in the set up base version composite action.
The dependencies being tracked are :
User defined to babelfish objects

Views to view
Views, computed columns to functions
Views, computed columns to operators
Views, tables, functions, procedures, type to type
Views, table to collation
The dependencies on cast are not tracked by pg_depend.
Also, procedures and functions are stored as string, so dependencies within body is not tracked by postgres.

The check has expected dependency file based on the base version that contains the objects for which tests are not present currently. It then compares the expected and output file to validate upgrade tests present.
If the test fails, it gives the expected dependency file and a csv file containing dependency count to analyse the coverage of dependencies on the babelfish objects in the upgrade logs of the respective upgrade.

Signed-off-by: Dhruvi Sheth sdhruvii@amazon.com
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

One of the upgrade test is failing. Please resolve that.

Looks good to me!


text:
between SQL语句拼接错误

在BetweenPredicate中的renderTo方法里面，builder.sql(if (negative) " not between " else "between")，由于between前后没有空格导致SQL语句拼接错误

OK, thanks

This problem has been fixed in v0.2.22.
Please close it after your validation

repo: babyfish-ct/jimmer


text:
有关于 DTO specification 的一些疑问

BookView {
    id(authors) as authorIds   // List<Long> authorIds
}

input BookInput {
    id(authors) as authorIds   // List<Long> authorIds
}

specification BookSpecification {
    id(authors) as authorIds   // Long authorIds
}

从前两个 View 和 Input 来看, 都是符合直觉的,
specification 来说, 有点突然, 这里应该也是和 View / Input 一样返回List
这里单独使用一个关键字, 来区分 Long /  List 是不是更合适

Try 0.8.161
id is forbidden in specification, associatedIdEq must be used.

authors: babyfish-ct zhengchalei


text:
Additional help hint are printed

We see two hints to decribe and cancel a job, and different ones to call executions or stop a job. Also Printout canceled due to timeout (the job is still running). even though the jobs finished just fine
→ bacalhau-1.5.0 docker run ubuntu echo hello
17:55:07.047 | INF pkg/config/config.go:211 > Config loaded from: [], and with data-dir /Users/walid/bacalhau-versions/v1.5.0/data-dir
Job successfully submitted. Job ID: j-4acf9db1-928c-42f2-aa79-8a03ebdb2264
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):

 TIME                 EXEC. ID    TOPIC         EVENT
 Sep 19 17:55:07.549  e-e8ae2cd9  Execution     Completed successfully
 Sep 19 17:55:07.558              State Update  Completed
To get more details about the run, execute:
	/Users/walid/bacalhau-versions/v1.5.0/bacalhau job describe j-4acf9db1-928c-42f2-aa79-8a03ebdb2264

To get more details about the run executions, execute:
	/Users/walid/bacalhau-versions/v1.5.0/bacalhau job executions j-4acf9db1-928c-42f2-aa79-8a03ebdb2264

Printout canceled due to timeout (the job is still running).

To get more information at any time, run:
   bacalhau job describe j-4acf9db1-928c-42f2-aa79-8a03ebdb2264

To cancel the job, run:
   bacalhau job stop j-4acf9db1-928c-42f2-aa79-8a03ebdb2264

Fixed

repo: bacalhau-project/bacalhau


text:
export private key bash history dangers

https://protos.com/brazilian-crypto-streamer-loses-60k-after-showing-private-keys-recovers-it/#:~:text=A Brazilian crypto streamer lost,but it was too late.
In the docs one is asked to export their ethereum private key into a bash variable, this exposes it in bash history and thus reverse search.
If its possible I would change this setup to use docker compose with the .env_file variable, so one can create a .env and run the docker container that way

i added a comment to this effect here https://github.com/bacalhau-project/lilypad#run-a-job

authors: lukemarsden polus-arcticus

repo: bacalhau-project/lilypad


text:
Convert discovery processors into entity providers

Feature Suggestion
The following discovery processors would benefit from being converter to using the EntityProvider interface instead, as among other things that will enable immediate deletions rather than orphaned entities, as well as more granular control of the update interval. More details about entity providers can be found in the catalog customization docs.

[x] AwsS3DiscoveryProcessor #10480
[ ] GithubDiscoveryProcessor #12334
[x] GitLabDiscoveryProcessor #11886
[x] BitbucketDiscoveryProcessor #11345
[x] AzureDevOpsDiscoveryProcessor #11604

I'm interested in awsS3, bitbucket, and github. I didn't start working on any of these yet, but I'm open to contributing. If anyone starts to work on these, would be great to share it here (to prevent double work).

@Rugvip as an MVP would it be enough if the providers do the same as the discovery processors and create Location entities which then get picked up by the other processors? Or might that still cause orphans?

@pjungermann yeah that should be alright, probably the way we wanna implement it tbh. Eager deletions happen recursively so if a deleted location is the only thing referencing an entity then the entity will be deleted as well

I will look at replacing/converting the BitbucketDiscoveryProcessor next. Hereby, I plan to consider #9923 and create separate providers for Bitbucket Cloud and Bitbucket Server (fka. Stash).

https://github.com/bitcoin/bitcoin/issues/24783#issue-1194493518 @pjungermann

I'm interested in taking on the GithubDiscoveryProcessor and converting it to an Entity Provider.

@pjungermann Have you started with converting the BitbucketServerEntityProvider yet? Otherwise I can grab that one.

@goober No, I'm working on Bitbucket Cloud at the moment. I'm nearly done, need to polish a few things. I plan to create a PR soon. I decided to put this into a new module plugins/catalog-backend-module-bitbucket-cloud(may change still) instead of plugins/catalog-backend-module-bitbucket (I want to have both separated so you can pull in the one(s) you actually need/use).

@goober No, I'm working on Bitbucket Cloud at the moment. I'm nearly done, need to polish a few things. I plan to create a PR soon. I decided to put this into a new module plugins/catalog-backend-module-bitbucket-cloud(may change still) instead of plugins/catalog-backend-module-bitbucket (I want to have both separated so you can pull in the one(s) you actually need/use).

Thanks. Then I will wait until you have contributed your changes and will then finalize the BitbucketServerEntityProvider

The PR above is for the Azure DevOps implementation

PR #12334 will contribute the provider for GitHub

@goober are you still up for taking on Bitbucket Server?

@goober are you still up for taking on Bitbucket Server?

I moved on to another employer so unfortunately not. However, we got it working internally before I left, so maybe @ONordander wants to take a look at a contribution?

@namco1992 sounds good. Feel free to reach out if you run into challenges. You can drop your questions at the support channel in Discord, too.
@ONordander in case you have something which you could share and therefore, @namco1992 would not need to invest time, please let us know.

PS: we only have Bitbucket Server and GitHub (PR under review) left still.

@ONordander Cool! I will leave it for you then, look forward to your PR 😃

@pjungermann looking into what we are running locally and realized that I need to make changes to https://github.com/backstage/backstage/tree/master/packages/integration/src/bitbucketServer, to add possibility for username/password authentication.
What's the easiest way of doing that, a separate PR for the integration?

@ONordander I got you covered with that via PR #12711 related to another issue. It is waiting for confirmation by a Bitbucket Server user. Currently, we were hoping that @namco1992 can test it. But maybe you can give it a shot, too :)

@ONordander I got you covered with that via PR #12711 related to another issue. It is waiting for confirmation by a Bitbucket Server user. Currently, we were hoping that @namco1992 can test it. But maybe you can give it a shot, too :)

Nice, I'll try to get it running today for testing.

@Rugvip I think this issue is complete now? 🤔

Indeed, thanks! 😁
And thank you everyone that helped out with this! 🙏

authors: ONordander Rugvip arslan-raza-143 brentg-telus goenning goober marcus-crane namco1992 pjungermann

repo: backstage/backstage


text:
🐛 Bug Report: Bitbucket catalog fetch does not allow specifying path or port

📜 Description
If the bitbucket integration has a path or port appended to the apiBaseUrl (for example: https://myorganization.com/bitbucket/rest/api/1.0 or https://mybitbucketinstance.com:1234/rest/api/1.0), the catalog fetch fails as it only uses the host and protocol part of the URL for file fetching.
👍 Expected behavior
The bitbucket catalog should include possible paths or ports to the URLs used
👎 Actual Behavior with Screenshots
The catalog fetch fails with error "catalog warn Unable to read url, NotAllowedError"
👟 Reproduction steps

Set up bitbucket server to run in subpath or in different port
Set up bitbucket server integration config apiBaseUrl and host to point to the instance
Start backstage and wait for the catalog refresh

📃 Provide the context for the Bug.
Host and protocol only used here:

https://github.com/backstage/backstage/blob/master/plugins/catalog-backend-module-bitbucket-server/src/lib/BitbucketServerClient.ts#L70
https://github.com/backstage/backstage/blob/master/plugins/catalog-backend-module-bitbucket-server/src/lib/BitbucketServerClient.ts#L93

🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Also port is not supported, maybe I should update the title of this issue.

I'm more on the Bitbucket Cloud side of things. However, maybe my generic understanding is enough.
Also, I might need a few more details here :)
Overall, we have two URLs:

The Location target pointing to a catalog file. Usually, this is the same URL as you would see in a browser when you open the file there.
The " fetch URL" / API URL used to fetch the content of the catalog file.

BitbucketServerUrlReader will receive the Location target and uses getBitbucketServerFileFetchUrl with that URL as well as the matching integration to convert it into the "fetch URL".
An UrlReader instance is always for one integration and matching for that one is host-based (incl. potential port I believe).
getBitbucketServerFileFetchUrl will return
return `${config.apiBaseUrl}/projects/${owner}/repos/${name}/raw/${pathWithoutSlash}?at=${ref}`;

where apiBaseUrl is a required config property:
  /**
   * The base URL of the API of this provider, e.g. "https://<host>/rest/api/1.0",
   * with no trailing slash.
   *
   * The API will always be preferred if both its base URL and a token are
   * present.
   */
  apiBaseUrl: string;

Instead of "https://<host>/rest/api/1.0" you should be able to add a port there as well.
The code does not care about details of the apiBaseUrl value (whether it contains a port or a path prefix. As in the docs, it must not end with a slash character and has to include the API path prefix as of your installation (usually, /rest/api/1.0).
ScmIntegrations itself will find the right BitbucketServerIntegration using the host as matching criteria.
  /**
   * The host of the target that this matches on, e.g. "bitbucket.company.com"
   */
  host: string;

In case your host value is not just the host but also contains a port and/or path prefix, this part will fail. (see ScmIntegrationsGroup.byUrl implementation of basicIntegrations which will use new URL(url).host to be matched against the config value).
In that case, you can leave the host only at the host config but have port and/or path prefix at the apiBaseUrl config (which needs to be valid (base) URL).
@drodil Would be great to share some more details about your config and the whatever you can find about the errors (stacktraces, ...).

Hi,
Apparently, this was my own mistake. After reading the source code it looks like the catalog URL is actually using the repository.links.self[0].href as a baseline. Also with a quick look, it seems that neither of those functions outside tests is used in the plugin (?). I am closing this issue, for now, thanks for your quick support!

authors: drodil pjungermann


text:
Generate app config documentation from schema

Feature Suggestion
In order to make life easier for new and current adopters alike, is a place to read up on all possible configuration options.
There is a good source of truth for configuration in form of a configuration schema, that is built up dynamically where plugins provide a schema for the relevant parts.
Taken this schema, it should be feasible to generate documentation in markdown format for inclusion in the official docs.
Possible Implementation
Suggesting to add a config:schema command to backstage-cli that outputs the current configuration schema, which may then be used by a separate tool to generate the desired docs.
Context
I have the first part already as a POC locally, and will continue work on the second part.
Help would be appreciated (either pointers in the right direction, or as code :) ) to get this into a GH action to populate the docs site; given that is the way to go. I have not looked into how this is done, atm.
Discord comment from @freben on the topic

Thanks! Will close this as a duplicate of #3367 though, please continue the discussion there. It's assigned but a bit stale so do chime in 😁

Did a quick search, not good enough though, obviously ;)

authors: Rugvip kaos


text:
[RFC] UX change of entity horizontal tabs to left nav

Status: Open for comments

Need

As noted in Discord and I think I've seen @freben mention it a few times:

remove the tabs entirely and instead make it a filter in the left side of the page

This RFC is intended to drive feedback/comments into a more concrete UX spec which could then be picked up by someone to implement.
The demo's Spotify has shared publicly of their internal instance show this:

They've grown and have many many more tabs than most example instances (at least that I've seen) yet of Backstage.
Versus what is in the open source app today:

Proposal

Movement of an entity's horizontal navigation to the left side of the screen.
A very simple change of modifying the Material-UI <Tabs> element with a new orientation="vertical" property does some of this easily. (Note this is used in multiple places, see Risks section)
Custom theming?
Ability to define a tab's name with some sort of alpha property, or potentially elevate plugin metadata into the tab.

In @backstage/core in the HeaderTabs.tsx file, making this one line change:
<Tabs
        indicatorColor="primary"
        textColor="inherit"
        variant="scrollable"
        scrollButtons="auto"
        aria-label="scrollable auto tabs example"
+        orientation="vertical"
        onChange={handleChange}
        value={selectedTab}
      >

And then forcing the menu on left in Tabbed.tsx via these sort of changes:
    return (
      <>
+        <Box>
          <HeaderTabs
            tabs={tabs}
            selectedIndex={selectedIndex}
            onChange={onTabChange}
          />
+        </Box>
+        <Box>
          <Content>
            <Helmet title={title} />
            {currentRouteElement}
          </Content>
+        </Box>
      </>
    );

Gets us PART of the way there:

Alternatives

Retain horizontal nav with the right arrow chooser which lets more and more tabs extend out to the right (but are hidden from view).

Risks

The open source Backstage already has a left nav which drives to certain parts of the app and by convention is usually used for plugins which are not entity specific but could be more broad reaching (like Cost Insights which today isn't widget or entity based, but GCP project based). Adding another left nav to it begins to complicate the left side of the screen and reduces overall real estate horizontally.  This makes it even harder to view the app on smaller screens without a dynamic way of handling these menus.
The current <HeaderTabs> component is used in multiple places in the app, including to select different entity kinds in the catalog, and so wholesale replacing some of the elements in this tab may not be possible. So I think the risk is in making any key changes to the existing tabbing needs to ensure it doesn't change where horizontal tabs may want to be kept? (if they do at all)

Oh, I thought @freben actual meant the tabs above the catalog table?
I have to admit that I actual like the tabs on the entity page. Right now the tabs don't take up much space compared to a vertical layout. But they might not scale well with many entries.

All the better to collect comments 😀

We do have some ongoing design research that might touch on this, so will hopefully have some updates in the future.
Will add that the horizontal tabs is the newer design, which we use in some places internally as well

authors: Fox32 Rugvip adamdmharvey


text:
Add config visibility to the frontend

SonarQube config visible in the frontend
We need to get the urls to the instances in the frontend, but they're not visible, despite being @visibility frontend in the config - although the backend config. I saw that there's a shadow config in the frontend package for the baseUrl, but this only works if you don't have multiple instances.
This PR adds the config values of the baseUrl (and other non-sensitive fields) to the frontend for multi-instance configurations.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks! Please trigger a release of this too 🙏

repo: backstage/community-plugins


text:
WIP: Upgrade to new nodejs LTS and migrate to async/await

TODO:

[ ] fix istanbul to support async/await syntax.

Coverage increased (+0.7%) to 92.188% when pulling 245820931b99563280843d6433f2c1888cd3d5f1 on new-node-lts into 73780c822822131b79666f059793aa6fd3949851 on master.

Coverage increased (+0.7%) to 92.188% when pulling 245820931b99563280843d6433f2c1888cd3d5f1 on new-node-lts into 73780c822822131b79666f059793aa6fd3949851 on master.

Coverage decreased (-0.2%) to 91.356% when pulling e65157a8c1ffe1c22907340b7f7e1296a6210ec7 on new-node-lts into 73780c822822131b79666f059793aa6fd3949851 on master.

Coverage decreased (-0.2%) to 91.356% when pulling e65157a8c1ffe1c22907340b7f7e1296a6210ec7 on new-node-lts into 73780c822822131b79666f059793aa6fd3949851 on master.

Coverage decreased (-0.2%) to 91.356% when pulling e65157a8c1ffe1c22907340b7f7e1296a6210ec7 on new-node-lts into 73780c822822131b79666f059793aa6fd3949851 on master.

Coverage decreased (-0.2%) to 91.356% when pulling 229e98515e0ea4331d4ed078aeb6d7cb62ae8a77 on new-node-lts into 73780c822822131b79666f059793aa6fd3949851 on master.

Coverage decreased (-0.2%) to 91.356% when pulling 736ee747576ce28e51e619de258dda81b9e71a88 on new-node-lts into 73780c822822131b79666f059793aa6fd3949851 on master.

authors: coveralls wpjunior

repo: backstage/functions

license: mit

license_source: bigquery


text:
add back ska distance and ska annotate?

ska distance (from version 1) was helpful in clustering and created a cluster. tsv and a .dot file for uploading to Microreact, which was quite handy for visualisation. Would you consider adding that function? (correct me if I need to be corrected, becos pp-sketch can only calculate the distance with fasta/fastq, but not with skf?!)
Also, would like to ask if we use bedtools to replace ska annotate. If I'm using a reference-free approach, how am I supposed to transfer the file formats from skf to bedtools-compatible formats?
Appreciate your reply and help.

I've also had another request for the distance method to be added, so that meets my current threshold for doing this! Tracking here https://github.com/bacpop/ska.rust/issues/26 and will endeavour to add in the next month
Annotation is only possible using a reference (as in v1 of ska). I would probably use ska map to generate a VCF, then you can annotate function with many different tools. If you wanted to annotate all the split k-mers, you can use ska nk --full-info to print out all of the k-mers, map these to reference positions with something like bwa fastmap, then use bedtools intersect on the coordinates.
Currently I feel this is too specialised a use case to add direct support for.

Thank you for your prompt response and for considering the addition of the distance method.
I appreciate your effort in addressing the requests from the community. As for the annotation, I understand that it's a specialized use case, and I appreciate your suggestions on how to achieve this using other tools in conjunction with SKA. I will explore the suggested workflow using ska map, bwa fastmap, and bedtools intersect to annotate the split k-mers.
I also wanted to mention that I've been encountering memory issues while using ska merge with a larger number of samples (90 in my case). Despite dividing the samples into smaller groups and merging them sequentially, I still face issues when merging certain groups. I was wondering if you could consider optimizing memory usage for the ska merge function to handle larger sample sizes.

I also wanted to mention that I've been encountering memory issues while using ska merge with a larger number of samples (90 in my case). Despite dividing the samples into smaller groups and merging them sequentially, I still face issues when merging certain groups. I was wondering if you could consider optimizing memory usage for the ska merge function to handle larger sample sizes.

Would you be able to provide some more information here? How much memory do you have i.e. at what point are you running out. How many k-mers do you have in the files (ska nk)? If the samples are divergent the number of k-mers when merged will increase a lot, so it may be one or two samples causing the issue.
I do have potential plans to offset some memory use to disk #22 at the expense of increased runtime, but this is more involved so can't guarantee I'll have time to do it.

I am currently working with a dataset consisting of 90 samples, and each sample has around 19 million k-mers, totaling approximately 1.7 billion k-mers across all samples. My system has 1 TB of RAM, which should be sufficient for most computational tasks. However, given the large number of samples and the k-mer count in each, I encountered a "killed" message during the analysis, possibly due to running out of memory.
I would appreciate any suggestions on how to optimize the workflow or use alternative approaches that can handle the large dataset efficiently. I am open to using more memory or distributed computing resources if needed to successfully complete the analysis.
Looking forward to your guidance and suggestions.

An estimate for RAM use is k-mers * (samples + 8), so even if these k-mers are all unshared I'd guess around 200-400Gb. Can you give the command you ran? Using one thread would be sensible.
Memory use should be lower than this though, as where ska works well most of the k-mers will be shared between the samples. Can you try running build on a few smaller numbers of your samples (e.g. 2 samples, 4 samples, 8, 16, 32) and 1) check the memory use with /usr/bin/time -v (or gtime on OS X), reported under max resident set size at the end 2) see how many k-mers are in the final .skf files by running ska nk on them, and/or also adding the verbose flag -v to your run.


text:
🛑 Linx is down

In 8093e32, Linx (https://i.zhem.us/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Linx is back up in f688225.

repo: baddate/uptime-monitor


text:
@badeball/cypress-cucumber-preprocessor/browserify doesn't work with aws-amplify latest versions (since v4.3.8)

Current behavior

An error occurs when bundling JavaScript via Browserify preprocessor
Error: Can't walk dependency graph: ENOENT: no such file or directory, lstat '/Users/Anna_Mkrtchyan/WebstormProjects/cypress-cucumber-browserify-amplify-issue/process'
required by /Users/Anna_Mkrtchyan/WebstormProjects/cypress-cucumber-browserify-amplify-issue/node_modules/@aws-sdk/client-lex-runtime-v2/node_modules/@aws-sdk/util-user-agent-node/dist-cjs/index.js
Desired behavior
I should be able to bundle JS code with browserify when using aws-amplify to authorize my Cognito user in autotests.

Test code to reproduce

Clone repository - https://github.com/anna-mk/cypress-cucumber-browserify-amplify-issue
Install dependencies - npm i
Create cypress.env.json file in the project's root directory and add Cognito user credentials to it. It should look like
{
"PASSWORD": "",
"USERNAME": "",
"POOL_ID": "",
"CLIENT_ID": ""
}
Run code - npm test

Notes

I simplified the code to the minimum reproducible state. Removed Cucumber related code.
Issue started to occur since aws-amplify v4.3.8.
The file mentioned in the error log is unnecessary and unknown for the project.

Versions

Cypress version: 12.14.0
Preprocessor version: 18.0.1
Node version: 18.12.1

Checklist

[x] I've read the FAQ.
[x] I've read instructions for logging issues.
[x] I'm not using cypress-cucumber-preprocessor@4.3.1 (package name has changed and it is no longer the most recent version, see #689).

I should be able to bundle JS code with browserify when using aws-amplify to authorize my Cognito user in autotests.

This might very well be true, but it's not my problem and I can't help you with it. It also seems to be a known issue.

authors: anna-mk badeball

repo: badeball/cypress-cucumber-preprocessor


text:
Badge request: SDK constraint and dependency version for Dart packages

The support for Dart packages is currently pretty basic: we can only get a bagde for the latest version of a package (i.e. https://img.shields.io/pub/v/<package_name>.svg).
It exists a specification for the API endpoints exposed by Pub package manager:
https://github.com/dart-lang/pub/blob/master/doc/repository-spec-v2.md
The API let us access two missing things from shields.io:

the SDK constraint: we can get the Node.js constraint from a npm package, the PHP constraint from a Packagist package, but it's currently impossible with a Dart package.
the version of a dependency: same here. The badges are available for npm and Packagist packages but not for Pub packages.

It would be very cool if more kind of badges could be generated for Dart projets.

Hello @cedx !
Thank you for your suggestions! Would you like to contribute to Shields and have a go at implementing these new Dart badges?
Cheers,
Pyves

I'm not sure that I'm sufficiently skilled to contribute, but I will try to look at the docs. Currently, I'm having problems with the install (tested on Windows 10 and Ubuntu 19.04 with Node.js 12.2.0):
$ npm ci

[...]
Warning: .then() only accepts functions but was passed: [object Object]
    at Installer.updateInstallScript (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:366:8)
    at /usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:284:18
From previous event:
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:282:10)
From previous event:
    at promiseMap (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:180:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:76:16
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:276:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:75:14
    at processImmediate (internal/timers.js:439:21)

Warning: .then() only accepts functions but was passed: [object Object]
    at Installer.updateInstallScript (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:366:8)
    at /usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:284:18
From previous event:
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:282:10)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:75:14
From previous event:
    at LogicalTree.forEachAsync (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:74:33)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:78:22
From previous event:
    at promiseMap (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:180:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:76:16
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:276:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:75:14
    at processImmediate (internal/timers.js:439:21)
From previous event:
    at LogicalTree.forEachAsync (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:74:33)
    at Installer.updateJson (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:272:17)
    at Installer.timedStage (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:79:34)
    at /usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:89:24
From previous event:
    at Installer.run (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:89:8)
    at EventEmitter.ci (/usr/local/lib/node_modules/npm/lib/ci.js:13:52)
    at Object.commandCache.<computed> (/usr/local/lib/node_modules/npm/lib/npm.js:156:13)
    at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/bin/npm-cli.js:130:30)
    at processTicksAndRejections (internal/process/task_queues.js:82:9)

Warning: .then() only accepts functions but was passed: [object Object]
    at Installer.updateInstallScript (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:366:8)
    at /usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:284:18
From previous event:
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:282:10)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:75:14
From previous event:
    at LogicalTree.forEachAsync (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:74:33)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:78:22
From previous event:
    at promiseMap (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:180:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:76:16
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:276:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:75:14
    at processImmediate (internal/timers.js:439:21)

Warning: .then() only accepts functions but was passed: [object Object]
    at Installer.updateInstallScript (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:366:8)
    at /usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:284:18
From previous event:
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:282:10)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:75:14
From previous event:
    at LogicalTree.forEachAsync (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:74:33)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:78:22
From previous event:
    at promiseMap (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:180:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:76:16
    at tree.forEachAsync.concurrency (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:276:14)
    at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:75:14
    at processImmediate (internal/timers.js:439:21)
From previous event:
    at LogicalTree.forEachAsync (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:74:33)
    at Installer.updateJson (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:272:17)
    at Installer.timedStage (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:79:34)
    at /usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:89:24
From previous event:
    at Installer.run (/usr/local/lib/node_modules/npm/node_modules/libcipm/index.js:89:8)
    at EventEmitter.ci (/usr/local/lib/node_modules/npm/lib/ci.js:13:52)
    at Object.commandCache.<computed> (/usr/local/lib/node_modules/npm/lib/npm.js:156:13)
    at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/bin/npm-cli.js:130:30)
    at processTicksAndRejections (internal/process/task_queues.js:82:9)

[...]
> jsonpath@1.0.1 postinstall /repo/shields/node_modules/jsonpath
> node lib/aesprim.js > generated/aesprim-browser.js

> fast-xml-parser@3.12.16 postinstall /repo/shields/node_modules/fast-xml-parser
> node tasks/postinstall.js || exit 0

Love fast-xml-parser? You can now support the project on following:
 > https://opencollective.com/fast-xml-parser/donate
 > https://www.patreon.com/bePatron?u=9531404

> styled-components@4.2.0 postinstall /repo/shields/node_modules/styled-components
> node ./scripts/postinstall.js || exit 0

Use styled-components at work? Consider supporting our development efforts at https://opencollective.com/styled-components

> pose-core@2.1.0 postinstall /repo/shields/node_modules/pose-core
> node ./scripts/postinstall.js || exit 0

      +-------------------------------------------------+
      |                                                 |
      |          Hey! Using Pose commercially?          |
      |                                                 |
      |         Pose is completely open source.         |
      |       Its continued development relies on       |
      |          contributions and sponsorship.         |
      |                                                 |
      |          Join us: patreon.com/popmotion         |
      |                                                 |
      +-------------------------------------------------+

> fsevents@1.2.8 install /repo/shields/node_modules/fsevents
> node install

internal/modules/esm/default_resolve.js:69
  let url = moduleWrapResolve(specifier, parentURL);
            ^

Error: Cannot find module '/repo/shields/node_modules/fsevents/install' imported from /repo/shields/node_modules/fsevents/
    at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:69:13)
    at Loader.resolve (internal/modules/esm/loader.js:70:33)
    at Loader.getModuleJob (internal/modules/esm/loader.js:143:40)
    at Loader.import (internal/modules/esm/loader.js:127:28)
    at internal/modules/cjs/loader.js:812:27
    at processTicksAndRejections (internal/process/task_queues.js:89:5)

> nodemon@1.19.0 postinstall /repo/shields/node_modules/nodemon
> node bin/postinstall || exit 0

internal/modules/esm/default_resolve.js:69
  let url = moduleWrapResolve(specifier, parentURL);
            ^

Error: Cannot find module '/repo/shields/node_modules/nodemon/bin/postinstall' imported from /repo/shields/node_modules/nodemon/
    at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:69:13)
    at Loader.resolve (internal/modules/esm/loader.js:70:33)
    at Loader.getModuleJob (internal/modules/esm/loader.js:143:40)
    at Loader.import (internal/modules/esm/loader.js:127:28)
    at internal/modules/cjs/loader.js:812:27
    at processTicksAndRejections (internal/process/task_queues.js:89:5)

> husky@2.3.0 install /repo/shields/node_modules/husky
> node husky install

internal/modules/esm/default_resolve.js:69
  let url = moduleWrapResolve(specifier, parentURL);
            ^

Error: Cannot find module '/repo/shields/node_modules/husky/husky' imported from /repo/shields/node_modules/husky/
    at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:69:13)
    at Loader.resolve (internal/modules/esm/loader.js:70:33)
    at Loader.getModuleJob (internal/modules/esm/loader.js:143:40)
    at Loader.import (internal/modules/esm/loader.js:127:28)
    at internal/modules/cjs/loader.js:812:27
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! husky@2.3.0 install: `node husky install`
npm ERR! Exit status 1

The trace is VERY long: it exceeds 10000 lines! Some errors are probably related to the fact that I'm using Node.js 12.x.
Installing the package using npm install --ignore-scripts works.

This should be taken into account as part of #3404

My annual summer cleaning of open issues 😄 Closing this one because it's still not resolved after one year... and I don't use Dart anymore, so this is no longer a problem for me.

Closing this one because it's still not resolved after one year... and I don't use Dart anymore, so this is no longer a problem for me

I'm going to reopen this one @cedx. It's not uncommon for feature requests to be outstanding for an extended period of time, especially in a project of Shields' size. Though you may no longer be interested in this one yourself, other Shields users could be and may be sufficiently motivated to implement it!
Thank you again for the suggestion

authors: PyvesB calebcartwright cedx

repo: badges/shields


text:
Wrong GitHub tag is shown

[This](https://github.com/HaxeFlixel/flixel uses ) repo uses this badge:

It shows the latest version as 3.3.9, even though the latest tag / most recent version is 3.3.11.
I suspect this might be caused by the double digit patch number.

Thanks for raising this!
One of the tags is 1.09, which is not semver compliant. Since we can't use semver ordering, we fall back on to the next best thing, ASCII ordering. It is bad, but dealing with arbitrary complex versionning schemes (as are found in the wild) is hard. If you can think of a better algorithm, it would be welcome!

Ah, I see... that's from before we followed semver.
In this case (and most cases I'd imagine?) simply using the most recent tag would work just fine. That's how I thought it works until now, actually.
Different urls to deal with different versioning schemes would be another option.. tag/latest, tag/semver etc.. that might overcomplicate it though?

simply using the most recent tag would work just fine

Hehe, it worked that way until someone told us that they had the wrong version on their badge… They had made a 3.2.14, then a 3.3.0, then a 3.3.1, then performed a bugfix patch tagged 3.2.15.
The use of a different URL is an interesting idea. It is an issue for all badges dealing with versions, though.

We have the same issue here: ![Latest Release](https://img.shields.io/github/tag/robotology/yarp.svg?label=Latest Release)
We have a tag start that is probably causing the issue.
Would it be possible to add a list of tags to skip to the URL? i.e. something like
https://img.shields.io/github/tag/robotology/yarp.svg?label=Latest Release&skip=start;foo;bar

@drdanz We filter out things that don't look like a version. In your case, you have a non-semver v2.3.20.1, which throws off the semver detection, which makes it fall back to ASCII comparisons.

I intend to switch to a simplified three-tier version analysis: semver / a custom dotted-version comparator / ASCII. The ASCII tier will no longer have non-versions filtered out, while the new custom dotted-version will use integer list comparison (and trailing data ASCII comparison for the -alpha and the like). Initial testing shows that Flixel and Yarp will be fixed by that new design. Versions that follow a different convention than dots (eg, v1-3-10) won't be fixed, and will be handled by the third tier.
(It is irrelevant for https://github.com/badges/shields/issues/261, which now uses the PHP algorithm. The same goes for https://github.com/badges/shields/issues/377, which uses GitHub's /latest version.)

authors: Gama11 drdanz espadrine


text:
WIP Configure max-age header for frontend

I'll get rid of 12240df and replace it with a pin to a NPM release once we publish an updated package to NPM. Then I'll mark it ready to review.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against badfc2d4fabc924a643ef1adb639b5eb0f4a9c0f

I realised the other day that I have push access on the scoutcamp repo and package so I just went ahead and did it. This is ready for review.

Am I correct in understanding this is a continuation/final step of https://github.com/badges/sc/pull/3? I've just realized I didn't have my notifications enabled for that repo so have missed all the discussion there

Yeah exactly. Sorry probably should have linked that and #5014 in the top post

authors: calebcartwright chris48s shields-ci


text:
deprecate [redmine] plugin rating badges

Redmine badges have been failing for some time due to a consistent 500 error from the upstream API.

https://img.shields.io/redmine/plugin/stars/redmine_xlsx_format_issue_exporter
https://www.redmine.org/plugins/redmine_xlsx_format_issue_exporter
https://www.redmine.org/plugins/redmine_xlsx_format_issue_exporter.xml

The badge receives little traffic and despite being broken for months, nobody has complained. If we a look at a bunch of different redmine plugins, we see the same thing for all of them:

https://www.redmine.org/plugins/redmine_issue_dynamic_edit.xml
https://www.redmine.org/plugins/redmine-x-upgrade-plugin.xml
https://www.redmine.org/plugins/redmine-x-gantt-chart-plugin.xml
https://www.redmine.org/plugins/redmine_issue_to_email.xml
etc

Suggest we deprecate this service.

The reason this didn't auto-merge is because it was missing an approving review.


text:
return empty error?

Hello,
sometimes I jsut want to return an error but with no value, for the moment I do this :
return Result.err(new Error())

But I would prefer something like this
return Result.err()

I just did a PR for that, waiting for reviewer right now. #7

I'm sorry for the huge delay for reviewing the pull request, I managed to miss the notification about it.
@pawndev's PR has now been merged, and I also added a test and docs for the new functionality. Updated the dependencies as well. The new version has now been published as v0.2.7 in npm.
Thank you 🙂

I'm sorry for the huge delay for reviewing the pull request, I managed to miss the notification about it.
@pawndev's PR has now been merged, and I also added a test and docs for the new functionality. Updated the dependencies as well. The new version has now been published as v0.2.7 in npm.
Thank you 🙂

authors: Grummfy jviide pawndev

repo: badrap/result


text:
Feedback: Awesome

Hi, I just got to know about your MiaB-Custom-UI and I wanted to say, that this is absolutely great. I was looking for couple of these UI/UX Improvements for such a long time. I will give it a try on a test machine.
Anway, I checked the screenshots and the demo and I really liked the collapsed domain feature. I think a great enhancement would be some kind of status icon next to a domain, if there are warnings or errors for this specific domain and a "collapse all" link. So you would be able to minimize the list but also immediately see, which section to open for details.
Anyway, keep the great work going!

Hey, thanks for the kind words! I built this project as an experiment and also as means to upskill a bit in react. I never actually used this interface in production and for that reason it's unlikely I'll make other changes tbh. I did ask the MiaB maintainers if they wanted to adopt this new interface and they mentioned it would be too hard to maintain, which is fair.
Saying all of the that, if people do end up using this interface, I'd be happy to maintain it, but afaik no one is using it. I haven't yet figured out how best to use it in prod without it being reset when MiaB updates. If I make any further changes it would be to figure out how best to use it in prod.

Hmm, I totally understand. I linked your project with @ddavness who created a mailinabox fork with some improvements/adaptions. Maybe this would be the right place for such an endeavor.

authors: badsyntax cmasterdelphi

repo: badsyntax/mailinabox-ui


text:
Proficiencies should container a pointer to the referenced resource

Given a proficiency, I should be able to look up the referenced resource.
There should be an additional field on the proficiency resource:
"references": [{
  "name": "Dagger",
  "type": "equipment",
  "url": "/api/equipment/dagger"
}]

Examples:

the daggers proficiency should contain a reference to the dagger equipment
the martial weapons proficiency should contain a reference to the martial weapons equipment category
the acrobatics proficiency should contain a reference to the acrobatics skill

I'll take this one, but can't assign to myself

Assigned to you! Also, closing out since you did an awesome job of handling it!

authors: bagelbits dgoetsch


text:
Change the column name in filter from "Target Currency" to "Currency Name".

Framework Version: 0.1.1

Issue Fixed.
Framework Version : 0.1.2

repo: bagisto/bagisto


text:
Duplicate Address Creating in checkout page.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
Master
Issue Description
If the customer is clicking on save this address on the checkout page then. the duplicate addresses are created.
Preconditions
The customer should be on the checkout page.
Steps to reproduce
1. Go to 'shop'
2. Login as a customer.
3. Add any product to the cart.
4. Process for checkout.
5. Add a new shipping address.
6. Click on save this address after filling in all required fields.
7. click on the back button at the top of the address section.
8. Click on add new address button.
9. Click on the save this address button after filling in all required fields.
10. See the error
Expected Result
Duplicate addresses should not be created.
Actual Result
If the customer is clicking on the save address checkbox duplicate addresses are created on the checkout page.
Screenshots

Additional context
No response

Please assign this issue to me.

authors: Sanjaybhattwebkul shivamtiwariwebkul


text:
Added drag and drop

Description
Added drag and drop

@akathuria289
Please link the issue for which this PR is created.

@akathuria289
Not working, the rows are not updating after drag-drop.

@Sanjaybhattwebkul  Updating is not possible. Only Drag and Droping of row

@akathuria289
Please resolve the conflicts.

@akathuria289
Any update??

@Sanjaybhattwebkul @akathuria289 how to use this feature? could you add some documentation?


text:
After and Before data-vv-as doesn't match

Versions:

VueJs: 2.1.10
Vee-Validate: 2.0.0-rc.14

Description:
As you can see in the captures, I use vv-data-as for my date inputs.
It translate its own field name to the 'vv'data-as', but no other 'vv'data-as' names.
Problem (Messages are in English for better understanding)

Original Problem (Messages are in Spanish)

Code

Sorry if this issue is already archived or I missed something important

this is a duplicate of #488
Although I think it is possible to implement a solution for it since PR #616 was merged some time ago

@logaretm Maybe implementing the solution require a lot of work,
What about a workaround: creating a attribute target-vv-as in the same input,
is this aproach more likely-easy to be done?

Don't worry about it, already implemented in https://github.com/baianat/vee-validate/commit/6e4b8a312989765cb8ebfb03b3bddc13b733dc27
so it will be up in next tag.

Glad to see this already resolved!

authors: logaretm saintplay

repo: baianat/vee-validate


text:
[WIP] Do not apply delay to blur event

As mentioned by @ssendev in #620 the validation delay does not make a lot of sense on blur. The primary objective of the delay would pretty much always be to stop error messages while typing. Since the blur event needs to be triggered by the user manually, there is no point in applying the delay there too.
Of course, the topic of #620 originally was more complex: The delay and events should be dynamic based on the status of the field. It makes a lot of sense, but it does require more changes.
Now I will admit, my solution is all but ideal, but it works (locally tested) and it does solve the issue. I do hope it can be improved further (config option, separate delay for blur events, less awful code).
Since the code quality isn't great and I couldn't figure out how to properly test specific event delays I don't think it should be merged necessarily. If anyone needs this feature in this hacky form, they can use my repo and npm link locally.

[x] Disable delay on blur
[ ] Make the behaviour of blur configurable
[ ] Make the code less terrible
[ ] Allow configuration of delays on a per event basis
[ ] Allow configuration of delays and events on field status basis

Thanks for the PR, configuration of delay per event basis is relatively easy to implement (API wise):
Vue.use(VeeValidate, {
  delay: {
    input: 0,
    blur: 0
  }
});

and have the field array map to those values and apply the delay properly, now applying delays per field basis via the data-vv-delay attribute wouldn't make sense. Maybe data-vv-delay should only affect the input event?
As for the per field status, this could be hard to do. The field behavior is evaluated only if the rules has changed or if their parameters change. Adding other evaluation conditions may slow down the update pipeline (the re-evaluation happens every directive update cycle), maybe negligible though.

I think having data-vv-delay only apply to the input event makes sense, since that really is the only event where delay matters.
Per event delays are the next thing I will add, since they seem to be the "easiest" of the bunch. Though that ties in with the above point, since the data-attribute shouldn't override the config attribute for blur if we want blur to stay at 0. So it seems the two need to come in together.
The field status is the biggest issue and becomes very complex in it's configuration alone. What might a config for such a thing look like?
<input name="title" data-vv-validate-on="pristine:{input:3000, blur}|dirty:{input, blur}">

Config equivalent:
Vue.use(VeeValidate, {
  delay: {
    input: 0,
    blur: 0,
    pristine: {
      input: 3000,
    },
  },
});

The result would be that it would, while pristine, validate 3 seconds after input or instantly on blur and then it would validate all other input changes immediately.
It looks like it wouldn't be easily implemented, but I do believe the above would be the general idea.

So far I'm not liking the config per field status, I would rather choose the best UX possible and enforce it without configuration, which is hard in its own way.
The issue is that delays are applied to the listeners, so each time the field status change the listeners will be re-applied which I don't really like. A better approach is to instead of adding a debounced listener, is to have a dynamic debouncer inside the validate function, so it would scan the delay value each time.

Regarding your concern @logaretm, the fields available would have to be limited. Dirty and pristine make sense, maybe have them limited to only direct opposites. I do agree that it's kinda dirty.

Alright the current tested behaviour checks many of the boxes we wanted to check. All events now default to 0 delay but can configured to have more delay globally using the config. This also means that not specifying any configuration for delay means that all events will stay without any delay, since only the input event can be configured using data-vv-delay.
Vue.use(VeeValidate, {
  delay: {
    blur: 1000,
    input: 2000,
  },
});

The above config would cause all blur events to have a delay of 1000. It also gives all input events a delay of 2000. Now the input event can be modified using the data-vv-delay directive.
<input name="name" data-vv-delay="3000">

The input above would have a delay of 3000 on input events, given the above config it would also have a delay of 1000 on blur events. Again, all events that may be present in configuration or data-vv-validate-on will receive a delay of 0 automatically.

Looks very good to me, do you have further changes or should I merge?

Yeah, it'll need to be documented. I'll get to that later today.

Alright, looks about ready. I suggest you do some testing for yourself, but it handled every example I threw at it so far. I've made sure it's backwards compatible, so a simple number instead of a delay object will do the same thing it has been doing.

Thanks for the amazing work Sebastian, I will review it tomorrow and merge it afterwards. I very much appreciate the work you've done here.

authors: logaretm sebastianbarfurth


text:
怎样设置请求体和返回体？

设置 payload，但是实际没有payload，是URL增加长度，是否可以随机在reqbody和respbody中增加数据包长度吗？

数据长度目前不能变化

被测设备默认做4层统计，同时也支持解析body，取决是否开启。想测试开启body解析的情况下，看对整体性能的消耗。

http get request只有header没有Body，http response是有Body的

换成http post是不是可以同时都有Body？

是的
现在还不支持post，这个特性在规划中

现在可以临时在get response加上Body吗？

不能
因为get加body不符合规范

好的，还有个问题请教。
设置payload_random后，url是随机了，但并不是每一个get都随机吗，有办法让每一次请求都不一样吗？
背景是我们存数据会做压缩，但如果每条流全都一样，压缩比会很高，跟用户场景不太符合，实际用户场景是不一样的。

是的 现在还不支持post，这个特性在规划中

post的特性有大概的时间计划吗？

大概在第二季度

好的

试一下这个分支
https://github.com/pengjianzhang/dperf/tree/post
配置方法：
http_method POST
payload_size 1K

可以了，但是现在payload都是一摸一样的，可以每个包不一致吗？或者多久切换一次也可以

暂时做不到

方案1可以的，方案2可能会需要配置较多的cpu。url是否也可以通过方案1这种方式，配置不同的url，轮流发？

你可以用其他工具如ab, hey, wrk发一些不一样的流量，作为补充

好的，多谢

请向周围小伙伴推荐、宣传一下dperf 谢谢

好的

authors: alongpan pengjianzhang

repo: baidu/dperf


text:
Můj vlastní program

Zdravím,
napsal jsem si python program, který mi ukáže co si z tašky vyndat a co si do ní na zítra přidat podle rozvrhu z Bakalářů. Můžete ho přidat přidat do Programy postavené na tomto API? Najdete ho zde. Díky!

Díky 👍

@kokolem Můžeš ho tam přidat sám. 😉 Stačí ho nahrát do organizace přes nastavení.

authors: JosefKuchar kokolem vitkolos

repo: bakalari-api/bakalari-api


text:
Oracle Improvements

Double check Band oracle against our ema DEX oracle.
Verify price data  update on ICON with data on Band chain on our backend.
Include price data from other chain oracles with BTP calls.

I'd like to include cross-chain oracle data calls as a feature here

We will build a solution for this for the ICON blockchain so we can use it to optimise BTP costs and call fees on top of what balanced needs it to do.
Closing this card

authors: BennyOptions FezBox dbrehmer

repo: balancednetwork/balanced-java-contracts


text:
How do you train your neural network?

I've managed to prepare the images and run the batching tests.
When I run the main > python3 -m colorization.main. I get a couple of errors. I've used the folder structure you suggested, but I believe I have the wrong configuration. I'd appreciate if you could outline the steps to train the network. Thanks 🚀

I hope our skype call solved those issues ;)

authors: baldassarreFe emilwallner

repo: baldassarreFe/deep-koalarization


text:
The documentation page is not responsive

Node version:
Sails version (sails):
ORM hook version (sails-hook-orm):
Sockets hook version (sails-hook-sockets):
Organics hook version (sails-hook-organics):
Grunt hook version (sails-hook-grunt):
Uploads hook version (sails-hook-uploads):
DB adapter & version (e.g. sails-mysql@5.55.5):
Skipper adapter & version (e.g. skipper-s3@5.55.5):

The documentation page is not responsive.

Hey @rohinish404, our documentation pages are not responsive.
If you want to view a more mobile-friendly version of our docs, you can view them directly on GitHub in this repo.

Hey @rohinish404 our documentation pages are now responsive. You can check it out.
Fun fact: I documented the process of making it responsive in this thread on X

authors: DominusKelvin eashaw rohinish404

repo: balderdashy/sails