Autocast empty samples

🚀 🚀 Pull Request
Checklist:

[ ]  My code follows the style guidelines of this project and the Contributing document
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have kept the coverage-rate up
[ ]  I have performed a self-review of my own code and resolved any problems
[ ]  I have checked to ensure there aren't any other open Pull Requests for the same change
[ ]  I have described and made corresponding changes to the relevant documentation
[ ]  New and existing unit tests pass locally with my changes

Changes
ds = hub.empty("mem://test")
ds.create_tensor("labels", htype='class_label')
ds.labels.append(np.zeros((0,4), dtype = 'uint64'))  #  Fails

https://activeloop.atlassian.net/browse/AL-1312

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add more Unicorns

Hey Guys, As you know that in almost every 5 days a unicorn is added here. So, feel free to make the changes. Thanks :)

Hey Guys, As you know that in almost every 5 days a unicorn is added here. So, feel free to make the changes. Thanks :)
@Priyaraj17  Can I add bank name who also hire software interns and developer roles and I observer few typos too .

Sure, go ahead. You can make a PR


Improve float values validation for data and commands

Data documents:

[ ] Deprecate NaNs and infinity values
[ ] Document differences
[ ] Check tests

Command documents:

[ ] Deprecate NaNs
[ ] Documents differences
[ ] Check tests

Infinity values for command documents are allowed (checks like {"$lte", math.Inf(0)})
Refs #871

We need to decide about command documents validation - where to call from etc


EL 1656 remove k8s deploy directory

What does this pull request do?
Removes the kubernetes deploy
Moves the dashboards to their own directory and update the deploy config
Any other changes that would benefit highlighting?
I dont know how to check the existing dashboards. Before merging this I need to check those and ensure that the replacements operate as expected.
Checklist

[x] Provided JIRA ticket number in the title, e.g. "LGA-152: Sample title"

docs/kubernetes.md There is a whole README file that has instructions for kubernetes. Just check through this to make sure anything is or isn't needed anymore.


Look into disk IO isolation

As a storage framework running in a multi-tenant environment Mysos may require support from Mesos to properly isolate disk traffic.
The Mesos ticket to track: https://issues.apache.org/jira/browse/MESOS-1979

https://issues.apache.org/jira/browse/COTTON-14


Request: Add additional security and other enterprise features

It is common in enterprise environments that simple open-source tools and workflows fall a little short on meeting a few common requirements.
Typically, this includes (relevant to this tool):

Never pulling anything directly from internet during CI workflows

Any open-source GIT repos get forked to github enterprise or gitlab etc
All package manager access get proxied and cached through JFrog Artifactory, Sonatype Nexus, Gitlab, etc.

Never trust any public source download without explicit/manual checksum declaration and verification

This can cause pain for build engineers who need to use a wide range of tools (like this one).  Many old tools are simply deemed unusable, or sometimes get forked and sources modified to be used in these environments.  Either case is a bummer.
Many modern tools are in a better position to support these things first class, and many do.  In this case, there are a few trivial things which could be done if you are interested in supporting such cases:

Support overriding the URL's for all downloads
Support providing a SHA which gets validated right after download
In both cases supporting these values in all of Config, CLI Argument, and EnvVar would be ideal

Here is a pretty robust and mature example of how you could do it, taken from the Conan package manager:
https://github.com/conan-io/conan-center-index/blob/master/recipes/cpython/all/conandata.yml
Of note, conandata.yml only has deal with URL's for one "package" at a time because each package gets it's own conandata.yml.  For this tool, you download (and thus need to describe) URL's and shas for multiple "packages", so perhaps it makes sense for your data structure to be different.
You could still choose to support the monolithic single-file-yaml data structure, keyed entirely based on the python version (like in the Conan example). Or, you could support a simpler structure like this, and force the user to use different configs per-version like this:
configs/portable_python_3_9_12.yml
source_urls:
  cpython:
    url: https://my_local_server/Python3_9_12.tar.gz
    sha: "...."
  zlib:
    url: https://my_local_server/ZLib1_2_12.tar.gz
    sha: "...."

configs/portable_python_3_10_4.yml
source_urls:
  cpython:
    url: https://my_local_server/cpython-3_10_4.tar.gz
    sha: "...."
  zlib:
    url: https://my_local_server/zlib-1_2_12.tar.gz
    sha: "...."

I'm not sure which is better but I'd be extremely happy with either.
The good news is that either case seems fairly trivial to support, because you already have robust handling in place for the config file and it looks super easy to add overriding of the URL's thanks to your clean code.
Please let me know what you think about the prospect of this?

Great!
To be clear, I don't think this project needs to maintain a fully populated config file like that.  Instead, just implement all the conditional variable substitution and conditional verification of sha signature, and then enterprise users can add the file with the values they care about as-needed. From a unit test perspective, just need to assert that when a URL is defined, it's used instead of the hard-coded ones, and if a SHA is defined, the sha comparison function is called.
Does that make sense?
Finally, would you be willing to implement this, or only to review and accept PR?

Open to both :) I'll gladly take a swab at it, I also don't like unchecked downloads...
What do you think about this draft: https://github.com/codrsquad/portable-python/wiki/Configuring-download-urls

Looks great!  I would drop the .sum support and give it a go.
The next (and more complicated) thing you might be asked to add will likely be authentication support.  Often, internal web/file services like the ones I mentioned disallow anonymous downloads, even for pure open-source forks and binaries inside firewall.  Also, more people moving to cloud-hosted services, where allowing anonymous anything is never advisable.
The cheapest way for you to support this would be to support environment variable substitution in the yaml file.  Many of these services still support https://${user}:${pass}@service notation. So, by supporting env vars, you can basically punt on any special handling of credentials in your program.
There are lots of syntactical strategies different tools have supported, but ${} is basically standard.
If and when someone wants to support a different web service which doesn't support URL-based creds, the most likely thing it will need is a custom header.  In that case, you COULD theoretically add another yaml property called http_headers where people could describe the header in yaml:
source_urls:
  cpython:
    url: https://my_local_server/cpython-3_10_4.tar.gz
    sha: "...."
    http_headers:
        Authorization: "Basic ${BASIC_AUTH_HASH_ENV_VAR}"
  zlib:
    url: https://my_local_server/zlib-1_2_12.tar.gz
    sha: "...."
    http_headers:
        Authorization: "Bearer ${BEARER_TOKEN_ENV_VAR}"

As I said, both env var support and authentication support are extra, but I wanted to give you some ideas no in case it comes up in the near future.

Any progress on this one?

Unfortunately didn't get much time to look at this, may find some time this quarter

I just add proxies supported in download #46 .


Release 06-27-23

Changed stratgy to swot_linstring for SWOT_L2_NALT_GDR_SSHA_1.0 SWOT_L2_NALT_IGDR_SSHA_1.0 SWOT_L2_NALT_OGDR_SSHA_1.0

Did not trigger to uat, will retry.


$ionicScrollDelegate.anchorScroll() does not work reliably

Previous issue: https://github.com/driftyco/ionic/issues/508
The anchorscroll functionality does not work reliably. Check out this Plunkr:
http://plnkr.co/edit/4bPK01zF0e0euJetZbxD?p=preview
I see two issues:

Anchor elements can not be wrapped in another element.
In the Plunkr I have wrapped div id="day2" into another div. Jumping to that link does not work.
After clicking one or two times all anchor links won't work anymore.

this really works for me : http://www.saintsatplay.com/blog/2015/02/scrolling-to-a-page-anchor-in-ionic-framework#.VcvVmPmqqko

I can get the scrolling to work well enough, but it isn't consistently scrolling to the same spot. Sometimes it scrolls a little higher and then a second click will scroll to the right spot. A third will go to the higher location again.
Any thoughts?


Failed to create 'ipPool'

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG

Environment:

Cloud provider or hardware configuration:
4GB RAM, 2 CPU

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
Linux 3.10.0-693.5.2.el7.x86_64 x86_64
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Version of Ansible (ansible --version):

ansible <IP_ADDRESS>
Kubespray version (commit) (git rev-parse --short HEAD):
39ce1bd
Network plugin used:
default(calico)
Copy of your inventory file:
node	ansible_ssh_host=node   ip=<IP_ADDRESS>
master	ansible_ssh_host=master   ip=<IP_ADDRESS>
[kube-master]
<IP_ADDRESS>
[etcd]
<IP_ADDRESS>
[kube-node]
<IP_ADDRESS>
[k8s-cluster:children]
kube-node
kube-master
Command used to invoke ansible:
ansible-playbook -u vagrant -b -i inventory/my-cluster.cfg cluster.yml
Output of ansible run:

https://gist.github.com/prakashsingh08/23e81fae8698c7210d4fef9a3aa4a8f8
may be its using different IP(I guess).although My systems IP Addresses are <IP_ADDRESS> and <IP_ADDRESS> but it seems its trying different interface IP
Anything else do we need to know:

it got resolved.
instead of ip adress inside groups i used server name. it worked fine.


nuttx: use larger alignment for os_mmap and comment why

the ci failure looks unrelated to this PR.
Download action repository 'actions/checkout@v3' (SHA:f43a0e5ff2bd294095638e18286ca9a3d1956744)
Download action repository 'actions/cache@v3' (SHA:e12d46a63a90f2fae62d114769bbf2a179198b5c)
Warning: Failed to download action 'https://api.github.com/repos/actions/cache/tarball/e12d46a63a90f2fae62d114769bbf2a179198b5c'. Error: nodename nor servname provided, or not known (api.github.com:443)
Warning: Back off 18.599 seconds before retry.
Warning: Failed to download action 'https://api.github.com/repos/actions/cache/tarball/e12d46a63a90f2fae62d114769bbf2a179198b5c'. Error: nodename nor servname provided, or not known (api.github.com:443)
Warning: Back off 22.26 seconds before retry.
Error: nodename nor servname provided, or not known (api.github.com:443)

other platforms with malloc-based os_mmap might need similar changes too, depending on their target cpu arch.


Assignment 2 Solved

Hey, MLCC ! I have Solved Assignment 2

Next time while sending PR make sure you have not deleted the outputs.


Icon as eyebrow in Card component

We would like to use the Card in IBM docs project and display an icon in place of eyebrow,
as

Hi Miri, can you attach an example or design please?

Just use the eyebrow={}  in any card.
where Settings32 is a react icon from carbon. the Card component already displays this with no problem,
that's why I suggested just to edit the proptype for eyebrow to Object, to get rid of the error in console.
result looks like this

Wonil will talk to Andree Proulx.

meeting scheduled week of sept 21

Per agreement with Andrée, the Card with pictogram component will be used instead of this.
For details, see this FR:
https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/4093

Closing based on Wonil's comments above.  The future pictogram variations work will be managed under epic (#4093)


Bash Implementation

Thanks for the cool game, I was so addictive i made the bash implementation :smile:
https://github.com/rhoit/parity

Really cool implementation! I'm impressed.
Thanks for taking an interest in my game! :D
Regards,
--
Abe Fehr
(613) 404-2098
http://www.abefehr.com/
On Sat, Jul 23, 2016 at 9:12 AM, rho<EMAIL_ADDRESS>wrote:

Thanks for the cool game, I was so addictive i made the bash
implementation 😄
https://github.com/rhoit/parity
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/abejfehr/parity/issues/43, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADvGdCuj04ekBJ1AGQg5u0N6hCeRhSK-ks5qYb7tgaJpZM4JTTdu
.


Add node builders

This PR makes the configuration tree structure immutable, and provides new builders to create it.
Main changes :

ConfigNodeBuilder is the main way to create nodes
Every mutating method from Node has been moved to ConfigNodeBuilder
ConfigNodeBuilder and Node implement a new interface, NodeLike

note: this PR is built on #23 and #25

Thanks!


test for 993

ready for review

@whoburg, could you make a separate branch with the commit for #819, so I can merge that while we discuss #993?

yep, on it

(also, trying out not putting PRs in Release milestones, so they stay a bit more focused on Issues)

roger.

gonna rebase this and force push only the 993 commits

closing, this tests something we don't want.


FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

There's probably a memory leak somewhere in the post-importer.
It happens whenever I try to use the post-importer and select to convert HTML or BBCode to Markdown.

I have 89141 imported posts that I need to process. All coming from IPB.
Redis 3.0.2.
NodeBB v0.7.0 + convert plugin from master.
If I don't convert anything, it runs fast and well.
I'm only checking to convert "posts".
Markdown plugin and every other related plugin is deactivated.
It crashes after a long time processing - every minute that passes, processing speed is slower and slower. At first, it does 20-50 posts per second, and before it breaks 1-2 per second.

I can provide the Redis DB in private if anyone needs it (~300MB).
Is there anything I can do to find the culprit?

hmm..

which version of NodeBB?
which version of the importer?
which version of Redis?
give me the ALL the specs of your machine? (the server that is running NodeBB)
does it make a difference if you convert "HTML to Markdown" or "BBCode to Markdown"?
have you tried this > https://github.com/akhoury/nodebb-plugin-import#redis-note
do you have Server or Verbose logging on? you shouldn't

I've converted over 3 millions posts before, I suspect this is a new bug from recent changes. I'd love to test with your data - maybe send it over via Google Drive or dropbox - i will permanently delete it when done.

@akhoury the info you requested is on the OP.
does it make a difference if you convert "HTML to Markdown" or "BBCode to Markdown"?

No. But the HTML to Markdown takes a bit longer to crash.
have you tried this > https://github.com/akhoury/nodebb-plugin-import#redis-note

Yes.
do you have Server or Verbose logging on? you shouldn't

Yes. Let me try to disable it (but I'm pretty sure the problem occurs even when logging is completely disabled).
My VIRTUAL machine specs:
Kernel: 4.0.6-1-ARCH
i7 4770 - 4 cores + 4 threads
16GB
SSD 60GB RAID 0
I'll try to generate heap dumps on 0.5% and 12% (it crashes around 15%) and compare them to see what's destroying the memory.

the info you requested is on the OP.

Sorry, i just woke up, lol - i read FATAL ERROR and stop reading after that.
send me your db dump, I don't have a large at hand right now.

Here's a screenshot of the heap dump:

There are many thousands of occurrences of this error.
This is most likely the source of the problem.
Still want the DB dump? It'll take a while for me to upload it (slow connection), but I'll gladly do it if it helps sort this out.

Apparently this problem is solved on jsdom 1.0
https://github.com/apparentlymart/node-angularcontext/issues/5
But nodejs is stuck on 0.8.
What do you recommend?

Seems we're stuck with an ancient version of jsdom. Maybe it would help if we upgraded...

Tried with all kinds of logging disabled. Same problem, nearly identical memory heap.

can you send me just an example post-content that triggers this error, I think i might have a workaround.
<EMAIL_ADDRESS>

I'm sorry, I don't know what an example post-content is.
You mean a json object like this?
HGETALL post:30000
{
  "uid": "522",
  "_imported_category_slug": "",
  "_imported_user_path": "",
  "content": "
Admito que até o episódio 3 eu tava achando o anime normal,mas depois desse episódio 4,deu uma upada de nivel absurda.   Every time I run the convert process it breaks on a different post, because the memory usage grows gradually with every post.

i was hoping that some sort of a unicode character is breaking the conversion. It doesn't look like this is the case

I created this script on nodebb root for testing purposes...
"use strict";
var async = require('async'),
  //db = require('./src/database.js'),
  Data = require('nodebb-plugin-import/server/data.js'),
  CONVERT_BATCH_LIMIT = 10;
var memwatch = require('memwatch-next');

memwatch.on('leak', function(info) {console.log(info)});

var brRe = /
/gmi;
var entities = new (require('nodebb-plugin-import/node_modules/html-entities')).AllHtmlEntities();
var window = require("nodebb-plugin-import/node_modules/jsdom-nogyp").jsdom(null, null, {features: {FetchExternalResources: false}}).parentWindow;
var htmlMd = require('nodebb-plugin-import/node_modules/html-md-optional_window');
function convert(str){
  str = str || '';
  str = entities.decode(str);
  str = htmlMd(str, {window: window}).replace(brRe, "\n");
  return str;
}
var hd;
var diff;

var convertedString = {string: 'HAHAHA'};

Data.countPosts(function(err, total) {
  var index = 0;
  Data.eachPost(
    function(post, next) {
      console.log(index++);
      if (index == 100){
        hd = new memwatch.HeapDiff();
      }
      if(post._imported_pid == 2000) {
        diff = hd.end();
        console.log(require('util').inspect(diff, true, 10));
      }
      if (post && post._imported_pid && post._imported_content) {
        convertedString.string = convert(post._imported_content);
        var zuba = 'zzz';
        // do something with string
        delete convertedString.string;
        next();
        //db.setObjectField('post:' + post.pid, 'content', htmlMd(post._imported_content), next);
      } else {
        next();
      }
    },
    {async: true, eachLimit: CONVERT_BATCH_LIMIT},
    function(err) {
      // when ALL of them are done or an error occurs
      if (err) {
        throw err;
      }
      console.log("DONE!!");
    });
});

The console output is like this - I'm breaking on inspect(diff):
/usr/bin/node --debug-brk=53440 --nolazy htmltomd.js
Debugger listening on port 53440
db.ready
{ growth: 2233768,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 868256,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 104952,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 52528,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 72528,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 109512,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 53184,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 83480,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 3047048,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 2004936,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 196856,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 574992,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
{ growth: 262104,
  reason: 'heap growth over 5 consecutive GCs (0s) - -2147483648 bytes/hr' }
0
1
2
3
...
1110
{ growth: 70655080,
  reason: 'heap growth over 5 consecutive GCs (13s) - -2147483648 bytes/hr' }
1111
1112
...
1542
{ before: { nodes: 407918, size_bytes: 52833763, size: '50.39 mb' },
  after: { nodes: 943361, size_bytes: 159044905, size: '151.68 mb' },
  change:
   { size_bytes: 106211142,
     size: '101.29 mb',
     freed_nodes: 2439,
     allocated_nodes: 537882,
     details:
      [ { what: 'Arguments',
          size_bytes: 0,
          size: '0 bytes',
          '+': 2,
          '-': 2 },
        { what: 'Array',
          size_bytes: 8858512,
          size: '8.45 mb',
          '+': 143491,
          '-': 513 },
        { what: 'BreakPoint',
          size_bytes: 480,
          size: '480 bytes',
          '+': 6,
          '-': 0 },
        { what: 'Buffer', size_bytes: 0, size: '0 bytes', '+': 1, '-': 1 },
        { what: 'Closure',
          size_bytes: -13752,
          size: '-13.43 kb',
          '+': 110,
          '-': 301 },
        { what: 'Code',
          size_bytes: 60776,
          size: '59.35 kb',
          '+': 339,
          '-': 121 },
        { what: 'Command', size_bytes: 0, size: '0 bytes', '+': 1, '-': 1 },
        { what: 'FSReqWrap',
          size_bytes: -32,
          size: '-32 bytes',
          '+': 0,
          '-': 1 },
        { what: 'Module',
          size_bytes: 480,
          size: '480 bytes',
          '+': 6,
          '-': 0 },
        { what: 'Multi',
          size_bytes: -72,
          size: '-72 bytes',
          '+': 1,
          '-': 1 },
        { what: 'Native',
          size_bytes: 90262,
          size: '88.15 kb',
          '+': 3,
          '-': 3 },
        { what: 'NativeBuffer',
          size_bytes: 0,
          size: '0 bytes',
          '+': 1,
          '-': 1 },
        { what: 'Object',
          size_bytes: 3520352,
          size: '3.36 mb',
          '+': 83307,
          '-': 197 },
        { what: 'Queue', size_bytes: 0, size: '0 bytes', '+': 1, '-': 1 },
        { what: 'RegExp',
          size_bytes: 216,
          size: '216 bytes',
          '+': 3,
          '-': 0 },
        { what: 'String',
          size_bytes: 81101856,
          size: '77.34 mb',
          '+': 34438,
          '-': 1054 },
        { what: 'TypeError',
          size_bytes: 587376,
          size: '573.61 kb',
          '+': 24474,
          '-': 0 },
        { what: 'core.DOMException',
          size_bytes: 336,
          size: '336 bytes',
          '+': 6,
          '-': 0 },
        { what: 'system / Context',
          size_bytes: -9048,
          size: '-8.84 kb',
          '+': 67,
          '-': 200 },
        [length]: 19 ] } }

Process finished with exit code 130

The first detections are probably false positives, while posts are being counted, etc...
But you can see the difference is very big. This is not a problem specific to my system, I think.
You'll be able to reproduce this easily with this script, I believe.
I tried using the original html-md library instead of your fork, and the end result was the same (the original actually consumed a little more memory). Ultimately, I think this leak is probably happening on jsdom and this is where nodeJS stuff gets too complicated for me.
It would be dandy if we could somehow replace jsdom with cheerio (or something similar) on html-md.

for some reason i am not able to load the dump.rdb file you sent me :/ I am not sure what's going yet
I installed redis 3.0.2 and I can see the 300mb file getting loaded into memory, but my database is behaving like it had no keys/data at all.
Anyways, i was trying to reproduce the issue outside of NodeBB, if the problem was truly JSDOM, then we should be able to reproduce it, however, I wasn't able to reproduce it yet, can you? I tried 3 millions iterations - and I didn't see any leaks - there is another factor involved.
npm install async
npm install jsdom-nogyp
npm install memwatch-next
npm install html-md-optional_window

node test.js

h3. test.js file

var ITERATIONS = 3000000;
var CONCURRENT_LIMIT = 10;
var SAMPLE = "
Admito que até o episódio 3 eu tava achando o anime normal,mas depois desse episódio 4,deu uma upada de nivel absurda. Todo o lance do discurso me pareceu uma espécie de \"estopim\",acho que daqui pra frente vai pegar fogo.
\n";

var newFilledArray =  function(len, val) {
    var rv = new Array(len);
    while (--len >= 0) {
        rv[len] = val;
    }
    return rv;
};

var replaceLog = function (msg) {
    process.stdout.clearLine();  // clear current text
    process.stdout.cursorTo(0);
    process.stdout.write(msg);
};

var STRINGS = newFilledArray(ITERATIONS, SAMPLE);

var memwatch = require('memwatch-next');
var async = require('async');
var htmlToMd = require('html-md-optional_window');
var window = require("jsdom-nogyp").jsdom(null, null, {features: {FetchExternalResources: false}}).parentWindow;

var s = +new Date();
var count = 0;

memwatch.on('leak', function(info) {
    console.log('\nLEAK: ', info, '\n\n');
});

async.eachLimit(STRINGS, CONCURRENT_LIMIT,
    function(str, next) {
        var sss = htmlToMd(str, {window: window});
        count++;
        setTimeout(function() {
            sss += 'abc';
            replaceLog('count: ' + count + ', ' + (count/ITERATIONS*100).toFixed(1) + '%');
            next();
        }, 0);
    },
    function() {
        console.log("\n\ndone in", ((+ new Date()) - s)/ 1000, "seconds");
    });

ill try it next with these 2 statements
            str = parser.toHTML(str);
            str = entities.decode(str);

maybe the leak is there

Forgot to tell you, I actually use DB 5 for my nodebb and not DB 0.

I tried to comment this line:
str = entities.decode(str);

and there was still a leakage.
Now, commenting htmlToMd made the whole process go very fast, and no leakage - memory usage only grew 133.44 kb over 1900 records. When this line is uncommented, it grows ~105MB

I think I cracked this, @akhoury.
 I think the garbage collector is unable to kick in here because the window stays open, and this variable is still in scope, and jsdom is called repeatedly inside htmlMd.
I found two ways to fix this:
Run node with --expose_gc and call this after htmlMd:
// If memory usage is > 130MB, force GC.
if (process.memoryUsage().heapUsed > 130000000) {
    global.gc();
  }

Still not ideal, we can't ship code like this.
Or, instantiate the window in the beginning of every loop instead of only once, and after running htmlMd:
// Important! Prevent memory leak.
window.close();

This fixed the problem for me.

the whole point of html-md-optional_window is to NOT to that though. I am glad that worked out for you.
But actually you don't have to create window nor pass it in - is it optional - see the original issue behind this fork.
https://github.com/neocotic/html.md/issues/42
See source here
https://github.com/akhoury/html-md-optional_window/blob/master/lib/md.js#L118-L127
see my note here
https://github.com/akhoury/nodebb-plugin-import/pull/125/files#r33945391

I understand, that's why I removed the comment.
But we have to create the window because we also need to close it. The original html-md does not allow specifying the window parameter, does it?
I tested all of this on another real data set (Imported from SMF) on a different computer with a different OS and NodeJS version and Redis version.
I was able to reproduce everything, including the memory leaks and the fix.

But we have to create the window because we also need to close it. The original html-md does not allow specifying the window parameter, does it?

I see.. yea, not the original html-md does not allow the window parameter.

I was able to reproduce everything, including the memory leaks and the fix.

Ok, great. I'll merge your fix.

https://github.com/akhoury/nodebb-plugin-import/pull/125

also changed bbcode-to-markdown module, since this one also uses html-md
https://github.com/akhoury/bbcode-to-markdown/commit/85ef2666896ed70d6973e48c778d4558a34a4ad8

Thanks mate!
Perhaps some time in the future it would benefit speed if we ported html-md to use cheerio instead of jsdom, since we have to create the window on every loop.
Cheerio is considerably faster in my experience.

Thank you!
Sure! I don't have a problem with Cheerio, but the next 3 months are fully booked for me.


policy/api: Add reserved:health entity

With the introduction of CiliumClusterwideNetworkPolicies a policy has
the ability to select the 'reserved:health' endpoints. If a user applies
a policy such as [0], it will block all connectivity for the health
endpoints. As this does not seem expected, since Cilium will report that
the connectivity across Cilium pods is not working, the user will need to
deploy a CCNP that allows connectivity between health endpoints. This
can be done with [1].
This commit introduces 'reserved:health' as an entity that can be
selected by CNP and / or CCNP.
[0]
---
apiVersion: cilium.io/v2
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: ingress-deny-all
spec:
  endpointSelector:
    matchLabels: {}
  ingress:
  - {}
---
apiVersion: cilium.io/v2
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: egress-deny-all
spec:
  endpointSelector:
    matchLabels: {}
  egress:
  - {}

[1]
apiVersion: "cilium.io/v2"
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: "allow-reserved-health"
spec:
  endpointSelector:
    matchLabels:
      'reserved:health': ""
  ingress:
    - fromEntities:
      - health

Related: #11099 (which I couldn't reopen)
Signed-off-by: André Martins<EMAIL_ADDRESS>

cc @joestringer

test-me-please

Coverage increased (+0.001%) to 37.147% when pulling 0eb5de1c6f81bfbc90a83eaa58677a6880149cea on pr/add-reserved-health into 62e4558bf81826b950ec2a75ca468553f67784ca on master.

test-me-please

I updated the PR to also add entity health to entity cluster.

test-me-please

retest-runtime

@joestringer PTAL as you had concerns in the original PR

@joestringer's comment from the original PR:

I do wonder if we could handle this better on the internal side. Seems a bit weird that the user is forced to think about the policy implications for infrastructure-level checks run by the daemon. Suggestion is something like excluding cilium-health endpoint from CCNP. Though we also would need to be quite careful there to ensure that any such changes don't accidentally apply to other endpoints and open an unintended hole.

I'm fine with this approach, but for consistency, I would still expect a health entity to be there.
Also, would we want to backport the whitelisting as well?

I would still expect a health entity to be there.

:heavy_plus_sign:

Also, would we want to backport the whitelisting as well?

That would be subject to risk assessment but seems reasonable to me assuming we are confident we aren't allowing additional traffic unintentionally.
I'm fine to merge & backport this PR as-is, it provides a workaround for now but it'd be nice to follow up on the whitelisting approach so users don't have to care.

test-me-please

retest-net-next


Success message when member subscription link expired

Issue Summary
The link in the subscription confirmation email is only valid for 10 minutes (which is in itself very short - too short), but when someone clicks on it after this 10 minutes, the message still says "You've successfully subscribed to ...", which is absolutely misleading.
To Reproduce

Register as a member
Wait for more than 10 minutes before clicking the "Confirm email address" link
Message "You've successfully subscribed to ..." is displayed
But the subscription didn't actually work

Two things:

It should display a red error message, stating that the link has expired and offer to retry it
Why 10 minutes? This is way too short. I would at least raise this to 1 day

Technical details:

Ghost Version: 3.19.0

This a theme specific problem. There is a success flag which can be used to display a message. What theme are you using?

I'm using the default Ghost theme "Casper" Version 3.0.12


[3/29 bugbash] Is the bot warmed up when published?

from nick ericson https://fuselabs.visualstudio.com/BotFramework/_queries/edit/58596/?triage=true
It seems to take a while to respond to the 1st message. Is the bot warmed after deploy?
If not it would be nice to so JIT, etc are done.
Version
v1.4.0-nightly.228616.da1ac55

@garypretty FYI - there are a few scenarios where Composer publishes the bot successfully and it all looks good, but the bot is not ready to accept messages.


Add unit tests

Description
Adding new unit tests for the sub-modules in pmodel that do not have dedicated unit tests.
Fixes #23
Type of change

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist

[ ] Make sure you've run the pre-commit checks: $ pre-commit run -a
[ ] All tests pass: $ poetry run pytest

Further checks

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

Current setup for submodules with their unit tests in the pmodel module:

competition -> test_c3c4competition
functions -> test_functions
isotopes -> test_calc_carbon_isotopes
subdaily -> test_memory_effect, test_fast_slow_pmodel, FastSlowPModel_JAMES
fast_slow_scaler -> test_fast_slow_scaler
cal_optimal_chi -> UT not available
jmax_limitation -> UT not available
pmodel_environment -> UT not available

@surbhigoel77 I'm not quite sure what to review here? I only see the one line.

@surbhigoel77 I'm not quite sure what to review here? I only see the one line.

I have mentioned the existing unit tests for present submodules in pmodel. For some of these we already have unit tests. For some, we don't and I have commented 'UT not available' for those. I want a heads-up from you to start writing tests for these submodules.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (06cbeac) 94.09% compared to head (551c4e1) 94.09%.
Report is 171 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #153   +/-   ##
========================================
  Coverage    94.09%   94.09%
========================================
  Files           21       21
  Lines         1134     1134
========================================
  Hits          1067     1067
  Misses          67       67

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

LGTM - very clean. There does seem to be duplication between the two files - is one going to be retired?

@davidorme thanks for pointing out. The one with the name test_calc_optimal_chi is the outdated one and shall be removed.

@davidorme Could you share the soft-bound values for the inputs to OptimalChi? I will include a unit testcase for the module based on these bounds.

Thanks for sharing this @davidorme. Yes, using the actual test set is a decent idea.
But, what is the ideal response to crossing the soft bounds?

@davidorme could you review this PR?
There are 3 files to review as mentioned in the PR description.  A couple of special notes:

test_OptimalChi has a testcase for nan value check but is commented out as it would not let the github checks pass the file. The testcase gives assertion error.
test_pmodelenvironment has the testcases to check for photosynthesis variables' plausible out of bound values. I have used the available test dataset (tc, patm, co2) to verify the same and none of the variables (kmm, ns_star, gammastar, ca) have any out-of-bound values. (These testcases are linked to #191 )

@davidorme Could you accept the changes that you requested? I will only be able to merge once you approve them. A new PR is to be opened by me for putting imports within testcases


Roll engine e65beb89da8b..8f39cac12c98 (4 commits)

https://github.com/flutter/engine/compare/e65beb89da8b...8f39cac12c98
git log e65beb89da8b..8f39cac12c98 --no-merges --oneline
8f39cac12 Roll src/third_party/skia 7891994e89a3..3c4d533d8ebd (1 commits) (flutter/engine#6218)
e3133e0e3 Reapply "Some cleanups enabled by removing support for Dart 1." (flutter/engine#6216)
1fb01f335 Roll src/third_party/skia a2bc1ca21bbc..7891994e89a3 (9 commits) (flutter/engine#6217)
f19ee56e6 Roll freetype2 to 6581fd3e9c8645f01c0d51e4f53893f5391f2bf3 (flutter/engine#6214)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@rmistry @liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6313046544744448

Commit queue failed; closing this roll.


feat: devcontainer

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Classname for fixed elements not respected

Hello,
As of the manual we should be able to define any class name for fixed elements.
            fixedElements: {
               fixed: "navbar-fixed-top"
            }```

Unfortunately this setting is not respected.
Any idea?

Is there an online demo?
Make sure to put this option in the configuration-object (the second object):
$("#menu").mmenu({
   // options
}, {
   // configuration
});

The setup seams correct:
http://web12.skouhus.bombelli.ch/

Did you have a chance to look into it?

Sorry, no I hadn't.
Where exactly should I be looking for the JS? I couldn't find it in the source of that page :/

The code is in main.js, but minified. So here it is:
 $("#site-nav").mmenu({
            // options
            "offCanvas": {
              "position": "right",
              "zposition": "next"
          }
      },
      {
          // configuration
          clone: true,
          classNames: {
            fixedElements: {
               fixed: "navbar-fixed-top"
            }
         }
    });```

Pretty odd, I ran some tests and all worked as expected.
Could you tell me what is alerted if you add this JS:
var api = $("#site-nav").data( "mmenu" );
alert( api.getInstance().conf.classNames.fixedElements );

For now, I guess you could do a small workaround by adding the default classname "Fixed" to the fixed elements before firing the plugin:
$('.navbar-fixed-top').addClass( "Fixed" );
$("#site-nav").mmenu();

The alert returns: [object Object]
As for the workaround, did not work. Do I still need to add the classNames?
classNames: {
            fixedElements: {
               fixed: "Fixed"
            }
         }

Could it be related to the z-Index of the mm-menu?

I don't think the z-index or any other CSS property will have anything to do with this.
What if you replace the alert with a console.log?

This is the output: Object {fixed: "navbar-fixed-top"}

Is that what is logged for fixedElements or for fixedElements.fixed?

For fixedElements:
console.log(mmAPI.getInstance().conf.classNames.fixedElements);

Hmm, I think I found the issue.
The fixedElements add-on searches for ".Fixed" inside the "page".
So you need to wrap your ,
 and  in a
. Otherwise only the
 is considered to be the "page".
If that doesn't seem like a good idea, I guess you could also add the class "mm-slideout" manually:
$("#site-nav").mmenu();
$('.navbar-fixed-top').addClass( "mm-slideout" );

Hope this helps.


Rf-280 Only render avatar when audio visualizer gain difference is over a threshold

Which Issue was this PR made for?

Closes #280

What is within the scope with this PR
Refactor to lower the frequency of onAudioActivity getting called and improving performance.
What is NOT in the scope with this PR
Related Issue
Other sidenotes that reviewer should be aware of

Hmmm it's definitely more performant but I feel like it's less responsive and less satisfying

Hmmm it's definitely more performant but I feel like it's less responsive and less satisfying

Realized it was because I wasn't updating the previous average at the correct location.


intput format

Dear author, I would like to ask you a question, the input file is in fasta format. I am currently aligning some genomes in maf format, can I convert them to fasta format?

I don't really understand the question, sorry. You do not want aligned genomes as input, so use the original genome fasta files.

That means I just have to put multiple genome files in one directory, right?
------------------ 原始邮件 ------------------
发件人:                                                                                "slimsuite/deduce"                                                                                @.>;
发送时间: 2024年7月30日(星期二) 晚上9:12
@.>;
<EMAIL_ADDRESS>主题: Re: [slimsuite/deduce] intput format (Issue #1)
I don't really understand the question, sorry. You do not want aligned genomes as input, so use the original genome fasta files.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Yes, that is correct. One fasta per genome. You should be able to use hard or soft links to the genome fastas if you do not want to copy them.

Thank you for your reply. With best wishes
1187697462
@.***
---- Replied Message ----
@.>Date7/30/2024<EMAIL_ADDRESS>@.>SubjectRe: [slimsuite/deduce] intput format (Issue #1)
Yes, that is correct. One fasta per genome. You should be able to use hard or soft links to the genome fastas if you do not want to copy them.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

No worries.


OPA (Open Policy Agent) Support

Do you want to request a feature or report a bug?
Feature
What did you expect to see?
Open Policy Agent (OPA for now) is slowly becoming a standard in Cloud Native environments for Authorization management.
Right now, my team is using OPA for managing Authorization across our endpoints. With Traefik as an API Gateway, we are using an authorization middleware so we can easily proxy all of our requests through OPA. This works nicely, but it obviously introduces another hop in the network. It also introduces a SPOF in our system.
It would be nice if Traefik could support OPA out of the box (which can be embedded as a library in Golang) and the ability to choose which OPA policies apply to each Traefik Frontend. In the case of Kubernetes Ingress, this can be done with annotations.
By the way, I understand if this is out of scope for Traefik, but given that this project is already implementing third party tools (or concepts) like LetsEncrypt, Open Tracing, etc, maybe this idea isn't too crazy.
Thanks in advance!

I'm planning on adding opa support in some capacity to my auth server which works with the forward auth feature of traefik. It may or may not be a fit for your use-case but you're welcome to provide input.
https://github.com/travisghansen/external-auth-server/issues/33

Hi @travisghansen, that´s my setup as well. I've actually written an article explaining how we implemented authorization in my previous job](https://engineering.etermax.com/api-authorization-with-kubernetes-traefik-and-open-policy-agent-23647fc384a1). However, adding this functionality to Traefik will reduce latency and complexity.
Thanks btw.
PS. I've developed an authorization middleware for a talk I did a few months ago. It isn't fully featured though https://github.com/santiagopoli/middleman

@santiagopoli cool thanks for the links. I read through a bit of the code and follow what you've got going on. Performance is certainly a huge consideration with the forward auth pattern generally.
My setup tries to be sensitive to performance while affording very powerful and flexible features (and being proxy agnostic). For example you can run auth as a pipeline using various mechanisms such as oidc and basic for the same service.
As an example, my personal config for services running at home allows all OPTIONS requests, if it's not an OPTIONS request then I first check if the Authorization header exists and it's value starts with Basic, if so I validate the user and return the result, if it starts with Bearer then I trigger a check against the jwt, otherwise oidc kicks in for end-users (ie: using a browser vs machine-to-machine setups). It's easy to add specific paths or hosts or whatever to be allowed if desired.
The way the service is designed all config lives external to the server so a single instance can serve up as many combinations of the above (with pretty much any other logic you can dream up). opa will just add even more options to the mix.

@travisghansen would you mind sharing implementation details?

As an example, my personal config for services running at home allows all OPTIONS requests, if it's not an OPTIONS request then I first check if the Authorization header exists and it's value starts with Basic, if so I validate the user and return the result, if it starts with Bearer then I trigger a check against the jwt, otherwise oidc kicks in for end-users (ie: using a browser vs machine-to-machine setups). It's easy to add specific paths or hosts or whatever to be allowed if desired.

@patlachance sure, you just want an example config_token or something else?

@santiagopoli Thanks for the links. We also wanted to use OPA for authz, but did not want to run an extra shim server. We ended writing Traefik middleware plugin which allows you to connect to OPA and decline the request based on the outcome.
See https://github.com/team-carepay/traefik-opa-plugin
With Kubernetes, configuration is a breeze:
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: opa
spec:
  plugin:
    opa:
      URL: http://opa:8181/v1/data/example
      AllowField: allow
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test-server
  labels:
    app: test-server
  annotations:
    kubernetes.io/ingress.class: traefik
    traefik.ingress.kubernetes.io/router.middlewares: default-opa@kubernetescrd

https://github.com/team-carepay/traefik-opa-plugin is archived and https://github.com/team-carepay/traefik-jwt-plugin is way more than what I need. So I'm working on a lighter plugin https://github.com/edgeflare/traefikopa


fix unscaling of the constraints during post-processing

Should resolve the issue we observed with MOI 1.7

What was the new test that found this?

It has been caught by test_linear_complex_Zeros


OpenVINO inital commit

Initial commit to add OpenVINO to the ODH dashboard.
@taneem-ibrahim
@sophwats

@ryanloney

@mmgaggle when https://github.com/red-hat-data-services/odh-dashboard/pull/59 merges, we can update this PR to make use of the feature flags.

Tested against master. Adding the feature flag openvino will show the OpenVino card in explore, and the 3 doc cards in resources.


[Feature Request]: Token access on collection level with one-click button

This feature already exists in Postman and would be a useful in Bruno.
Technically it can be done using pre-request scripts but this does not seem like a clean alternative.

When you crafted a token request (its just a Form post to a token endpoint) you can just set a Post Response var (ex. cc.apiname.access_token). The var will be available to all your collection requests as long as you keep Bruno running. In your request just add an Authorization header with {{cc.apiname.access_token}}. You can also set a pre request script on your collection to add the Authorization header with access_token.

When you crafted a token request (its just a Form post to a token endpoint) you can just set a Post Response var (ex. cc.apiname.access_token). The var will be available to all your collection requests as long as you keep Bruno running. In your request just add an Authorization header with {{cc.apiname.access_token}}. You can also set a pre request script on your collection to add the Authorization header with access_token.

Yeah here's my point, technically you can do whatever you want using scripts but in this specific case my team would need the token to be updated every 30 minutes, hence why having a button to refresh it would be easier than re-running a request.


feat: add polish locales

Related Issue or Design Document

none

Checklist

[x] I have read the contributing guidelines and signed the CLA.
[x] I have referenced an issue containing the design document if my change introduces a new feature.
[x] I have read the security policy.
[x] I confirm that this pull request does not address a security vulnerability.
If this pull request addresses a security vulnerability,
I confirm that I got approval (please contact<EMAIL_ADDRESS>from the maintainers to push the changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added the necessary documentation within the code base (if appropriate).

Further comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Applied, thanks. Should've done them after bit more of sleep. 🥴


Client Pylance: connection to server is erroring.

I experienced the problem that Python Language Server cannot be started, thus checking function in the python code is not possible any more. after checking former articles and my testing, finally, I find out this problem seems to be related to the workspace limitation to contain the qty of project folders, do you have specific figures, how many project folders can be configured in a workspace file?
Environment:
vsCode version: 1.85.0
Python version: v2023.22.0
Pylance version: v2023.11.10
use workspace to contain multiple project folder
Picture of error messages:
Client Pylance: connection to server is erroring. wirte EPIPE
Connection to server got closed. Server will not be restarted.
Client Pylance: connection to server is erroring. Channel closed

I got this bug too on my remote explorer.
If I don't set the python interpreter on my remote explorer, the Pylance didn't work and showed a strange behavior:

But if I set the interpreter, the above error occurs:

Has anyone encountered this issue? I've tried uninstalling and reinstalling the Python and Pylance, but it didn't work.

uninstall and reinstall python and pylance did not help, the problem was solved today for my own requirement, I found that it will work well when directly openning a folder or open a workspace with limited folders inside; but when more folders added in workspace, this error will appear, thus I think there should be some limitation for the quantity of folders in workspace configuration file, it is better to know how many can be afforded.

Uploading 2023-12-12_10h51_44.jpg…

Can somebody guide how to attach a picture into this post?

It looks like you were in the process of uploading the image to GitHub when you saved the issue. IMO the simplest way is to drag the image file into the issue text editor.

this did not work for me, I tried, but still under uploading.

Can you provide us some logs as described in the troubleshooting guide?
if you can't get those logs, we will probably need some sample project we can use to repro.

please reopen if it still an issue.


style: simplify some statements for readability

Closes #270

dua-cli is an excellent command-line tool.
I like that development builds are really fast, especially relative to other Rust projects I've contributed to.
Would you want a check against build time regressions, to keep build times solid?
If you're interested, I can look into adding that to CI in a future pull request.

dua-cli is an excellent command-line tool.
I like that development builds are really fast, especially relative to other Rust projects I've contributed to.
Would you want a check against build time regressions, to keep build times solid?
I can look into adding that to CI in a future pull request if you're interested.

 We could add some leeway, maybe 10% of the average build time of a few runs, to circumvent some flakiness, but it's completely up to you.


dependencyOf relationship is one-sided in the UI

Expected Behavior

Specify a dependencyOf relationship indicating that component A is a dependency of component B.
Visit component B in the UI.
I expect the EntityDepdendsOnComponentsCard to list component A.

This behavior is what happens when I instead specify that component B dependsOn component A.
Current Behavior
Component A is not listed.
Possible solution

Fix the code (😄 )

Steps to Reproduce

Load this catalog-info file into Backstage.
Ensure the EntityDepdendsOnComponentsCard is present in the UI
Visit the passenger-backend service.

Here's a video showing me reproducing the problem.
Context
I'm trying to indicate dependencies between components in Backstage.
Your Environment
I'm using latest master as of today to reproduce this.

Alright, I got around to looking at this.
The answer, in the end, turned out to be that there is no such thing as spec.dependencyOf in the model at all :) These spec fields are added selectively, in places where they make the most sense, and may sometimes even have names that do not correspond to the relation type name at all. So there is no guaranteed relationship between spec and relations at all; it becomes what we make of it.
Adding the following to the BuiltinKindsEntityProcessor here:
      doEmit(
        (component.spec as any).dependencyOf,
        { defaultNamespace: selfRef.namespace },
        RELATION_DEPENDENCY_OF,
        RELATION_DEPENDS_ON,
      );

makes the requested table row appear. Note the as any since it does not exist on that type really.
So as far as the bug goes, this works as designed. Question is, should there be a feature request to add the ability to specify the inverse dependency. Maybe? Is that a "good practice" or just confusing? It kind of lets non-owners of a service declare that that service depends on them - confusing or good?

Let me add that it's super nice how you added video context and even test data, it made it so much easier to zoom in on what to actually look at and what the actual missing piece was. Really appreciated, I know it also takes a lot of effort to make thorough bug reports.

When I was opening the issue, I actually added "remove dependencyOf" as one of then the potential solutions but then I deleted it because I thought it would be too difficult a breaking change.
Just updating the docs to remove any mention of dependencyOf is a reasonable solution now imo.

If you agree, I can finish this out myself btw.

Oh remove from where? Not sure I follow. Is this wrong in the docs somewhere?
The relation type does exist and should keep existing.

@freben Maybe I'm misunderstanding your message but you seem to be saying that, while the Well-known Relations docs mention a spec.dependencyOf relation, none of the Kinds actually support it.
If that's true, my proposal is just to remove all mentions of spec.dependencyOf from the docs to prevent the kind of confusion I experienced.
Once that's done, we can have a separate RFC to discuss whether or not the relation should or should not exist. As you say, it might be a good practice or it might be kinda confusing.

No, let me clarify again.
Relations are arrows. They can pop into existence in many ways. Maybe by ingesting some third party graph database. Maybe as computed by some spec thing. Maybe as a side effect of some other file that lies next to the yaml file. The point is, relations are an entire thing of their own no matter what the entities as such are up to. There may be relations that are generated without ever being mentioned in any entity anywhere.
Relations, as a matter of fact, aren't even strictly attached to entities in the database. You emit arrows that float freely in space, in a table of their own. Then, as we form the actual generated JSON that you see when you query the REST API, we look for arrows that emanate from each entity and "stitch" them in. You are free to emit a relation that starts and/or ends in a void because there is no matching entity; it just won't be seen because it won't get stitched into anybody.
You expressed it as "none of the Kinds actually support it", which given the above is a statement that can never be true. Anything can have any type of relation with anything, in theory. What we do though, is we carefully choose what ways we expose for "popping into existence" of such relations.
Now also remember, these are always generated in PAIRS. Always, no matter what.
What you have seen now, is that there IS an ability to say

A.spec.dependsOn: B

but there is NOT an ability to say

A.spec.dependencyOf: B

... using the spec, specifically, currently.
However, it is perfectly possible to express the relation

A dependencyOf B

As a matter of fact, the single spec field

A.spec.dependsOn: B

generates the pair of relations

A dependsOn B
B dependencyOf A

And if we happened to introduce the spec field

B.spec.dependencyOf: A

It would generate the pair of relations

A dependsOn B
B dependencyOf A

Note how the relations would be the exact same ones, because it doesn't matter from "which side" the relation is generated, the outcome is the same. The same thing happens where you can choose whether you make the claim that your user is a member of a group, or whether the group has a user as a member. The generated relation pairs are identical either way. You can even duplicate the information and redundantly declare it from both ends simultaneously; the generated relations get deduplicated before stitching them into the final entities.

I think there's an underlying assumption that because spec.x exists, the relation x exists. But the two just aren't tied to each other. As a matter of fact I was a bit hesitant to introduce spec fields that happened to have the exact name as a relation, because this sort of confusion would inevitably arise :) I had hoped that the spec fields would typically be more ... you know, "semantic"? At the very least, on a noun form. spec.owner, which translates to ownerOf + ownedBy. spec.members which translates to memberOf + hasMember. Etc

Oh wait. I see that I am being dense here. I misread what you said but I'll leave in the wall of text just to be sure. What you explicitly said was to address spec.depencencyOf occurrences, which indeed would be a good thing to do! But I searched locally real quick here and I don't think I see any occurrences of that?

It'd be like me making the claim "I'm a friend of the king", but the king is likely to disagree and prefer to choose his friends himself.

😂
Totally take your point about specs and relations being different and so on and, like you think I realised late in the conversation, I'm not recommending that the relation be removed. The clarification does help though, because as a lay-person reading the docs and trying to map an architecture to Backstage terms, I didn't really grok that the spec.x properties are generators of relations rather than relations themselves.
When I read The Well-known Relations doc, this was my thought process:

I see "They can be attached to catalog entities and consumed by plugins as needed." and I think "attached to catalog entities" means I can attach them to the spec section in catalog-info.yaml files.
Further down I saw "dependsOn and dependencyOf" and they seem equivalent except for direction.

Through experimentation, I later learned that they are not equivalent because I, as a user, can make things happen with dependsOn but not with dependencyOf.
Looking again, with the benefit of your explanation above, I can see now that the YAML file format docs do distinguish between dependsOn and dependencyOf. They don't actually say that spec.dependencyOf exists, I just assumed it did because spec.dependsOn happens to have the same name as the other side of the relation.
With all of that knowledge now in place, I'm not sure what to do. Either the model needs to be more understandable or I need to be better at understanding it 😄 . I will close this issue though, because like you say, it is working as expected.

I'm totally understanding that the docs are not yet ascended to their fullest :P

I fell into tree same trap actually. We have a shared db resource that I thought it would be quicker and easier to use dependencyOf instead of going to each component using it. I then realized it didn't work the opposite way.

I fell into tree same trap actually. We have a shared db resource that I thought it would be quicker and easier to use dependencyOf instead of going to each component using it and saying dependsOn. I then realized it didn't work the opposite way.

+1


hotfix/disable-use-redirect-file-in-jupyterlab

Disable a default option from the newer jupterlab version
See https://noosenergy.atlassian.net/browse/NOOS-885

It won't solve the root cause, see description in Jira


 JWT use for Token based authentication
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

@sindresorhus I just updated the desciption

I think the description (JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties.) should be above the Contents section, as users should be able to see what the list is about right away. Also linkify JSON Web Tokens there to https://en.wikipedia.org/wiki/JSON_Web_Token
The JWT logo should be linked to https://jwt.io
NodeJS => Node.js
node.js => Node.js
Descriptions should not start with JWT and JSON Web Tokens as that's implied.
Many of the item descriptions could be improved.
I would like to see more than just libraries. Include some more blog posts, tutorials, and links to community resources (Stack Overflow tag, IRC, chat, forums, communities, Reddit, etc. Example: https://github.com/sindresorhus/awesome-electron#community), videos of talks, book, learning material, etc.

Has consistent formatting and proper spelling/grammar.
The link and description are separated by a dash.
Example: - AVA - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.

⬆ Please go through each entry and ensure they follow these.

Ping @iamchathu

@sindresorhus I have done some of the changes and working on the remaining sorry for the delay.

Ping

Closing for lack of response.
If you ever want to get back to this, open a new PR, and please also see #1363.


Showcase Contribution for 171

Adding my Wave Function Collapse contribution.

Thank you for this submission, can't wait to see these on the page!


Could hoodie-account integrated with Ember.js?

Ember has no account solution itself, so that I want to use hoodie-account as Ember's account solution.
Could you tell me that my thoughts are realistic or not?

@laplaceliu yes that should be possible :) I don’t have a lot of experience with ember, but I think you can install npm modules into your ember app, right?
Install with npm install --save@hoodie/account`. Then in the client code, you can do
var Account = require('@hoodie/account/client')

Then see all docs here: https://github.com/hoodiehq/hoodie-account-client
For the server part, if you use Hapi, you can do
server.register({
    register: require('@hoodie/account/server'),
    options: options
})

See all docs for the hapi server plugin here: https://github.com/hoodiehq/hoodie-account-server/tree/master/plugin
I’d love to see if you get it to work :) Let me know if you have any farther questions.
By the way, we are also migrating our Hoodie’s admin dashboard to the new Hoodie, and are using Ember for it. Let me know if you’d like to get involved :)

@laplaceliu If you need npm modules in your ember app, you'll need to use ember-browserify to get it loaded, but otherwise you should be able to look at Gregor's instructions.
@gr2m the admin dashboard sounds interesting!

check out https://github.com/hoodiehq/hoodie-admin for the work in new admin dashboard app (work in progress) made with ember


Node's coordinates in the SOM

Hi @fcomitani:
I have some problems to determinate the node's coordinate in the bidirectional map. If I took, the trainned net and I want to see the centroids of the node, only I need to do is:
#SOM 4X5
net45 = sps.somNet(4, 5, data, PBC=True)
#Train the network for 10000 epochs and with initial learning rate of 0.01.
s45 = net45.train(0.01, 10000)
#Visualize the centroids of each features into the node 0
s45[0]

But if I want only two coordinates from where is located in the MAP this node, I can´t do this. So, can you help me to find where I get this two values that I need, 'cause I review your code and I don't find it.
Thanks so much,

Hi @JessitaMS,
The nodes are stored in the nodeList attribute of your net object, to see where each node is located (in the 2d hexagonal map) you'll need the .pos attribute of each node.
So for example in your case, to find the coordinates of the first node you'll need
net45.nodeList[0].pos
I'm going to add a note about this in the README, since it's basic information and it should be easy to find.
Thanks for bringing this up.
Hope this helps!

I'm closing this issue. Please feel free to reopen it if anything else comes up.

Hi @JessitaMS,
The nodes are stored in the nodeList attribute of your net object, to see where each node is located (in the 2d hexagonal map) you'll need the .pos attribute of each node.
So for example in your case, to find the coordinates of the first node you'll need
net45.nodeList[0].pos
I'm going to add a note about this in the README, since it's basic information and it should be easy to find.
Thanks for bringing this up.
Hope this helps!

I'm sorry for my reply delayed. Thanks so much for you answer. I'll try to used it! :D


add docker-volume-vsphere suppport again

ref:
https://github.com/boot2docker/boot2docker/issues/1270
https://github.com/boot2docker/boot2docker/pull/1275

FYI there is also PR #1370, which partially overlaps with the listed modules.

docker-machine create --driver vmwarevsphere created VM without eth0 interface with boot2docker v18.09.0, fixed by this
--vmwarevsphere-boot2docker-url https://github.com/boot2docker/boot2docker/releases/download/v18.09.1-rc1/boot2docker.iso

What is the difference between value m and y?
VMWARE_VMCI_VSOCKETS depends on: CONFIG_VSOCKETS && CONFIG_VMWARE_VMCI
https://cateee.net/lkddb/web-lkddb/VMWARE_VMCI_VSOCKETS.html

Closed in favor of #1370 (which is now merged). :+1:


[Bug] ... D-pad keypad W,S,D,A bugging

Platform

Device: Desktop
OS: Windows
Browser: Edge Dev
Browser Version: 122.0.2325.0
Better xCloud Version: 3.0.3

Describe the bug
Keyboard of the directions W,S,D,A bugging when I press W the character goes to that direction, being necessary to deactivate the keyboard and mouse with F9, then it goes back to normal, but a few seconds later it bugs again
Screenshots/Videos

Duplicate #220


left to right swipe issue

Hi,
How to swipe the view from left to right way

Hi,
How to make it as horizontal swipe based on the position to change this flodable layout


In SimMaxLoss， why rank=rank-1 ？

class SimMaxLoss(nn.Module):
def init(self, metric='cos', alpha=0.25, reduction='mean'):
super(SimMaxLoss, self).init()
self.metric = metric
self.alpha = alpha
self.reduction = reduction
def forward(self, embedded_bg):
    """
    :param embedded_fg: [N, C]
    :param embedded_bg: [N, C]
    :return:
    """
    if self.metric == 'l2':
        raise NotImplementedError

    elif self.metric == 'cos':
        sim = cos_simi(embedded_bg, embedded_bg)  #(N,N)
        loss = -torch.log(sim)
        loss[loss < 0] = 0
        _, indices = sim.sort(descending=True, dim=1)
        _, rank = indices.sort(dim=1)
        rank = rank - 1
        rank_weights = torch.exp(-rank.float() * self.alpha)
        loss = loss * rank_weights
    else:
        raise NotImplementedError

    if self.reduction == 'mean':
        return torch.mean(loss)
    elif self.reduction == 'sum':
        return torch.sum(loss)

Hi. please note that the diagonal elements (=1.0) in 'sim' are the product of two same embeddings and they rank 0. rank-1 aims to give weights to other items from 1 (exp(0)=1) to 0. And because log(1)=0, the diagonal elements in 'loss' are 0 and it will not be affected by the rank-1 (0-1=-1).

Thanks, I get it. Excluding its own similarity terms, consider the weight of other terms as 0 to 1.

Exactly!


Convincing other factions to join you

First you need to unlock/convince a faction, which is done via a special encounter with a member of said faction (requiring the same mechanics as any other encounter + a few lines dialogue), and can then be further upgraded with faction-specific items.

make animal-fractions allies by getting special items they want
after they become allies you can use that item to hire more allies of that animal species

deer wants leaves
squirrel wants nuts
...

moved to discussions #42


enhanced icon images

This is the Epic to add enhanced icons. those icons will be available when module SUCC is enabled.
#10
#11
#9
#8

featured: https://github.com/mrcomac/enhancedcombathud-swade/releases/tag/0.0.8


issue purge when projects are transferred to/between orgs

Thanks @nnja for figuring out how to force an object to purge even when it hasn't directly changed!


Make the workflow callback_id generic

Summary
This makes it so that we respect the value passed into callback_id, rather than treating it as any old string. This is necessary for us to key off of callback_id to know what should be passed into a trigger's workflow parameter in the API.
Testing
There is no functional difference here, but you could test making and deploying workflows for a sanity check.
Requirements (place an x in each [ ])

[ ] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[ ] I've read and agree to the Code of Conduct.

LGTM


Log location on disc displayed for local backtests

Removes broken "Your logs can be downloaded from ..." message at the end of local backtests
Api implements a new method, StoreLogs, that returns the location of logs on disc.
Removed unnecessary log processing from BacktestingResultsHandler ProcessLogMessages method
Removed unnecessary log processing methods from Api.cs - ReadLogAllowance and UpdateDailyLogUsed

Nice work @andrewhart098, this has bugged people for ever.


Oracle session manager - show server-side execution plan

Contributed in #7427

I've added plaintext rendering for session details with plaintext content.

verified


fix of ajax response

in my usage this fixes problem https://github.com/ublaboo/datagrid/issues/519

I think that it was collison of snippet and block

Alright, lets get it in and see. @radekdostal test it out please :)

@juniwalk Yes, this PR fixes https://github.com/ublaboo/datagrid/issues/519. Great!

Great! Thank you @chapcz


some copy from campaign fields were wiped from production in translation deploy

it seems like the "What You Get" section has been wiped from production
example node 2930

This is one of translatable fields. Let's wait for the script to finish and clean cache. This may help.

got it thanks @sergii-tkachenko

Looks like it hasn't been erased from Thor, I expect this to be on same on prod: https://thor.dosomething.org/node/2930/edit

Hm, it looks like the field exists in other nodes on prod: https://www.dosomething.org/node/74/edit?destination=admin/content.
Could it be somebody removed it by an accident earlier?

i'm seeing a few fields that seem to be wiped right now @sergii-tkachenko
node 1508 is missing:

What You Get
Secondary Call to Action
Time and Place

@mikefantini Script executed 100%. Yes, it looks like some fields have been lost. Don't know why yet, there was no errors during the execution. Plus, I ran it over thor db (created from prod) and it was fine...

I'll re-run the deployment procedure to make sure everything is on.

Regarding 1508: field value is in the db, figuring out why it's not displayed:
+-------------+----------+---------+-----------+-------------+----------+-------+-----------------------------------------------------------+-----------------------------+
| entity_type | bundle   | deleted | entity_id | revision_id | language | delta | field_call_to_action_value                                | field_call_to_action_format |
+-------------+----------+---------+-----------+-------------+----------+-------+-----------------------------------------------------------+-----------------------------+
| node        | campaign |       0 |      1508 |       15274 | en       |     0 | Make and share Thumb Socks to reduce texting and driving. | NULL                        |
+-------------+----------+---------+-----------+-------------+----------+-------+-----------------------------------------------------------+-----------------------------+

What You Get field of 1508 doesn't exist in db:
mysql> SELECT * FROM `field_data_field_value_proposition` WHERE `entity_id` = 1508;
Empty set (0.00 sec)

cc @sheydari-ds

sorry @sergii-tkachenko a bit confused, I expect node 1508 to have each of

What You Get
Secondary Call to Action
Time and Place

which of these are you saying don't exist in the db?

So it looks like that for some fields records in data database got missed. I will create a script that restores it from the last data revision. Agreed with @sheydari-ds.

Campaign specific starter statement copy also seems to have disappeared from front end and back end for some campaigns:
https://www.dosomething.org/campaigns/get-lucky?source=node/1141
https://www.dosomething.org/campaigns/lead-stampede?source=campaigns
Seems to appear fine on:
https://www.dosomething.org/campaigns/birthday-mail
https://www.dosomething.org/campaigns/school-standstill?source=campaigns

Yellow staff pick label on homepage also seems to have disappeared:

@namimody created an issue for your comment as it appears to be unrelated. #4944

@mikefantini actually #4944 is not related.

it looks like https://www.dosomething.org/node/3501/edit had all of it's content wiped too. Sam says that she saw it all there on tuesday.

@sergii-tkachenko @sheydari-ds

@sergii-tkachenko another example https://www.dosomething.org/node/1536/edit
I think it might be any campaigns that were unpublished did not get updated in your last fix for this.

@mikefantini I found easy way to fix this. When you see such campaign, just click Translate tab, then Edit again. The fields will be restored automatically: https://www.dosomething.org/node/1536/edit

It looks like the translation module didn't create translation automatically for unpublished nodes. It does it automatically on the Translate tab.

hmm ok thanks @sergii-tkachenko


[SPARK-37727][SQL][TESTS][FOLLOW-UP] Add test cases for logs in SparkSession.builder.getOrCreate

What changes were proposed in this pull request?
This PR adds some test cases for https://github.com/apache/spark/pull/35001. Test cases were not added because there are related bugs but they are fixed now.
Why are the changes needed?
To avoid regressions.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
This PR adds test cases that were manually tested in https://github.com/apache/spark/pull/35001.

cc @AngersZhuuuu @yaooqinn FYI

+1，LGTM

Wait .. the tests pass in IDE but fails in SBT shall command. Let me investigate this a bit more.

Merged to master!


Feature idea: Lazy scrapes

This is more a discussion that an issue, but I didn't find a better place to toss this.
Basically, lazy scrapes would scrape a target every X time, but only record into the time series if

the value changed
timeout Y was reached
Prometheus shuts down gracefully.

As a specific example, I will scrape UPS systems quite aggressively to have near-instant alarms when power fails or fluctuates. Yet, in a normal year, I will have between one or two incidents at max.
Given a timeout of, say, four minutes, would allow me to scrape every five seconds, but only record every four minutes.
While I know that Prometheus already compresses static values quite efficiently, this scheme would allow another gain of up to 1:300.

I understand why that idea seems attractive for your use case, yet I think implementing it this way leads to a great deal of complexity through all layers.
Currently, our staleness handling will get in the way anyway.
How about running two Prometheus servers? One scrapes slowly, the other one in 1s intervals. The fast one alerts but has a very low retention, while the slower one keeps data for longer.
Alternatively, the slower can also federate from the faster one.

I can't judge the implementation cost and complexity, so I trust your call on this.
Having two parallel servers, or scraping one with the other, means I will lose blips, though. If not for that, I would already be doing so.
This is similar to what I meant with the exporting to long-term storage: Sometimes, you will need averages, sometimes an aggregate, sometimes min or max, and sometimes you need to catch blips.
Matter of fact, typing the above I just realized that the idea of lazy scrapes is motivated by the lack of well-defined degradation of data and/or its granularity in the long term.

With the current encoding, a non-changing value takes 1 byte of space. With planned changes, it might boil down to 1 bit or even less. So there is really not much to gain by all those fundamental changes and complexities @fabxc mentioned.


Refactor EmptyDisk to reduce cognitive complexity

Signed-off-by: Radim Hrazdil<EMAIL_ADDRESS>What this PR does / why we need it:
PR extracts new func createEmptyDiskForVolume from CreateTemporaryDisks to reduce
congnitive complexity.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/retest


Fix index of API docs

The current index of the API docs page seems to have broken links: when I
click on "Automatic differentiation" for example, I get sent to the "JIT"
section.
This change fixes the links.

Thanks, @shoyer!


Add demo video/GIF to README

To Do

[ ] Storyboard
[ ] Prepare recording environment

[ ] Update accessory names/icons.

[ ] Record
[ ] Format
[ ] Upload
[ ] Add to README.md

I think the easiest way to record the Scout app/dashboard and Apple Home app simultaneously would be to load them in split view on an iPad and do a screen recording.

The video should be brief (<10 seconds for sure, <5 ideally). With the Scout dashboard on one side, and the Home app on the other…

Arm a security mode in the Scout dashboard.
After the mode appears as "Arming" in the Home app, tap the Security System accessory in the Home app.
Disarm the Security System in the Home app.
Arm the Security System to another mode in the Home app.

Here's a first stab…


Prevent logReplace from being wrapped in

This is an attempt to make the download and upload speeds appear properly. At the moment they are not replacing the last P and are being wrapped in br tags, so that they do not appear. I don't think inserting br tags are necessary at all. Let me know if there are any issues.

This breaks support for video and audio streaming.

We need to insert the dom nodes directly, not change them to html.

Fixed this in https://github.com/feross/instant.io/commit/c7f1a21d581fdc560e8ba07e38e714dfc30ed04d


Add MetricsVerifier to simplify verification of metric values in tests

Changes:

Add MetricsVerifier
Update tests to use the MetricsVerifier methods

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.

Thanks for the review, @AmatyaAvadhanula!


CORS errors using GCP's cloud storage

Chrome: the latest
Framework: vue(nuxt.js)
File Pound The Latest
I use vuetify in my design framework, but it displays fine even if you use a direct link to cloudStorage.
When I put an image link to filepond for initial display, I get a CORS error.
I'm having trouble recovering even after setting up cloudStorage's CORS.
Why do I get a CORS error only when displaying with filepond?

Image data is resized and presented in a  element so CORS needs to be configured on the remove server.
Please, next time when you submit an issue, follow the issue template (it's the text in the issue text area). 👍


feat: Persist created ticket on rotation

Make final Ticket in presenter
Make Ticket binder set the ticket to binding

Fixes #392

@Shailesh351 @rohanagarwal94 @shreyasnbhat Please review.


Meta files in WebSocket assembly prevent .unitypackage from being installed correctly

The meta files in  CareBoo.WebSocket assembly are the same as the ones in com.community.netcode.transport.websocket. When importing the unity-algorand-sdk.unitypackage to a project that has the com.community.netcode.transport.websocket package installed, this causes some files to not be imported correctly.
1. Rewrite the websocket client implementation in CareBoo.WebSocket and regenerate the UUIDs
Instead of using the community implementation that depends on unity's netcode, I need to rewrite my own implementation from scratch while generating new .meta files.
2. Replace WebSocket library in CareBoo.WebSocket assembly with dependency on com.community.netcode.transport.websocket
A couple things need to be done for this

Since this is a community package, it needs to be stored locally in the test project so that when making a .unitypackage it's included automatically.
The package does not list com.unity.netcode as a dependency, which needs to be fixed.

I think option 1 is probably the best solution because this project does not need an unnecessary dependency on com.unity.netcode.gameobjects.


Support for Angular 15: Has Scully been abandoned?

There have been no new commits or releases since September 2022. And unless I'm mistaken there is no official support for Angular 13, 14 or 15.
Has Scully been abandoned?

@knoake No, it is not. But All contributors are currently working full-time on other projects. So, yes progress has slowed down.
Full Angular V15 support is there, but not ready for release by a long shot. I'm currently working on a refactor, but it will take at least a couple of weeks, probably months before anything will be visible.

Good to know. Thank you for all your hard work.


Fix Jest tests

Pull Request Test Coverage Report for Build 445

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.492%

Totals

Change from base Build 442:
0.0%

Covered Lines:
103

Relevant Lines:
103

💛  - Coveralls


Update UR numbers

From https://www.ur.ch/mmdirektionen/63967

@kschibli thanks for your PR! UR case numbers have been added shortly after you've submitted it (without checking for open PRs, sorry) . I'm closing.


Basic tractography

Adds support for tractography streamlines (TRK/TCK). The API still needs work (they are now meshes, but have unique properties and shaders). However, the basic implementation is solid. In general, there are four ways to represent streamlines with a graphics API, listed in ascending demand on resources:

Line strip, makes minimal demands on GPU, but lines limited to one pixel in thickness.

bill board imposters requires about three times the resources of line strips but allow thick lines with emulated lines.

geometry shaders like MRtrix dixel views. Geometry shaders do not exist in WebGL (or Metal).

Triangulated mesh cylinders - this would use the same shader as all NiiVue meshes, but places the highest demand on GPU.

The current implementation uses line strip with just 16 bytes per vertex (XYZ positions as 32-bit float and 32-bit RGBA color). In the future, we might want to add support for imposters, but this may not be suitable to phones and other portable devices.

Taylor,
The rationale for the changes observed for the tests is an experimental solution for issue 287. The clip plane is now slightly translucent over tissue. If we like this, we should think of an easy way to influence the visibility of clip planes (e.g. they vanish after a few seconds, or some gesture to toggle clip plane visibility).