Type 'null' is not assignable to type 'SPFI'

[Enter feedback here]
cannot get along with this tutorial and did not find any help.
So, what could cause this happening?
in the pnpjsConfig file the line 11 (var _sp: SPFI = null;) has the error "Type 'null' is not assignable to type 'SPFI'"
all the rest of project has no erro at all.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 4b19eb96-192d-2d8b-8d4e-0de787f22093
Version Independent ID: e2cbd2b2-8bb7-a95f-0768-15f1b045b4c4
Content: Use @pnp/sp (PnPJS) library with SharePoint Framework web parts
Content Source: docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md
Service: sharepoint
Sub-service: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Hi there,
This definitely seems like an issue in the tutorial. SPFx 1.17.4 began enabling strict null checks by default in newly created solutions. So this error message is correct, you cannot assign null to an SPFI type.
To fix this in your local solution, please change:
var _sp: SPFI = null;
to:
var _sp: SPFI | null = null;
I have created a PR to update the tutorial.


Added the loading of save data for any level

Hello again, github was being wierd and I couldnt commit any changes to my fork unless I deleted the repo and forked the newest version of Super-Haxagon.
I needed to make my old code it compatable with the new custom level format and add some things to your code. It now uses the name of the level for the save file, while also categorizing the save data in the following folder format to try to minimize the amount of conflicting save data : "Creator/Difficulty/Mode/LevelName.txt". There shouldnt be any conflicting save data issues unless somebody, for some reason, creates two different packs of levels that have the same name and difficulty as one they've done before.
They would need to get creative with the names or change the name of the creator to keep compatability with other things they could make.
I could probably restructure the code a little bit, but Id like to get this in for version 2.0 as soon as i can since its so close to being completed. Everything appears to be working on my end, but please tell me if you have any problems with it.

Sorry It took so long, it was a mix of spending the holidays with my family and hardcore procrastination at its finest.

Hmm, my implementation was to save all of the scores in one db file.  Your implementation is quite... complicated. I'll review it and see what implementation I want to use!

Yeah, i guess it might be, huh. I thought it would be easier this way because I wasn't sure how to just change 1 line of the file without clearing it first if it had multiple scores in it. As far as im aware, though I may be wrong, you cant remove text from a file, only add to it or clear the entire file. So if you had one giant file of scores, you would have to first copy it to a second file, while also making sure you replace the correct score.
It doesn't matter to me which one you use, choose whatever one you think is better.

You are correct, you can't change one line of the file.  In order to update the score, you just  simply save all of the scores you have in memory (therefore you  only  ever need to read the file once). If you  really  wanted to make it efficient,  you could write to the  file in binary mode if you know the offset in the file, but  the speed at witch a 3DS can  write an ~500byte file makes that math worthless , so it's probably just  better to re-write the whole file.
...but right now I have to figure out why Citra is spitting out thousands of "unmapped Write32"s when I  launch a level ☹

That was happening to me when it was constantly checking for the save file. I made it check for the save file only when you change which level is selected. Otherwise, depending on where you have it check for the save file, it might be checking for it every frame, which isnt very good.

That was happening to me when it was constantly checking for the save file. I made it check for the save file only when you change which level is selected. Otherwise, depending on where you have it check for the save file, it might be checking for it every frame, which isnt very good.

No, I don't think it's that, I actually think  it's hitting the stack limit  for some reason. I'm trying  to  attach a debugger to citra but that's harder  than it sounds...

No, I don't think it's that, I actually think  it's hitting the stack limit  for some reason. I'm trying  to  attach a debugger to citra but that's harder  than it sounds...

Oh, i just reread you previous message and I read it wronf. I got that issue when I added a method call to the Main method. But only when I removed it, it started working again.

Oh, i just reread you previous message and I read it wronf. I got that issue when I added a method call to the Main method. But only when I removed it, it started working again.

It has something  to do with entering the  doPlayGame(...) method and I have no idea  what  is  triggering  it. I put an exit(1) before that method and Citra closes, but when I put exit(1) as the first line inside doPlayGame(...)  it hangs on the memory error!
C makes no  sense  right now 😠

It has something  to do with entering the  doPlayGame(...) method and I have no idea  what  is  triggering  it. I put an exit(1) before that method and Citra closes, but when I put exit(1) as the first line inside doPlayGame(...)  it hangs on the memory error!
C makes no  sense  right now 😠

Yeah, I was just going off of my experience. When I called my method that checks to see if the save data is there inside of the main method, it caused the game to crash as soon as a level was loaded. It was strange since I thought it would run when the game was started, but the moment I removed that call the level loaded correctly. So if you added a call to something in the main method, try to find a different place you can put it that will still make it work.

Yeah, I was just going off of my experience. When I called my method that checks to see if the save data is there inside of the main method, it caused the game to crash as soon as a level was loaded. It was strange since I thought it would run when the game was started, but the moment I removed that call the level loaded correctly. So if you added a call to something in the main method, try to find a different place you can put it that will still make it work.

If  you want to hear the  real kicker, changing #define TOTAL_PATTERNS_AT_ONE_TIME 3  from 3 to 2 will fix the problem.
WHAT?

If  you want to hear the  real kicker, changing #define TOTAL_PATTERNS_AT_ONE_TIME 3  from 3 to 2 will fix the problem.
WHAT?

That's certainly a wierd fix, but I guess as long as it still works, right?

That's certainly a wierd fix, but I guess as long as it still works, right?

I mean,  you'll only see two  patterns into the future instead of  three,  so patterns  will  randomly  appear (which is no good)! I'll see  what I can do.

I mean,  you'll only see two  patterns into the future instead of  three,  so patterns  will  randomly  appear (which is no good)! I'll see  what I can do.

Welp I fixed it.... Turns  out this whole time it was Track bgm  that was being audioFree()'d before it was initialized,  causing Citra to freak out about uninitialized memory BUT ONLY if the stars aligned and the memory set by Citra was not already 0.
FML.

Welp I fixed it.... Turns  out this whole time it was Track bgm  that was being audioFree()'d before it was initialized,  causing Citra to freak out about uninitialized memory BUT ONLY if the stars aligned and the memory set by Citra was not already 0.
FML.

Hey man, don't  take this the hard way, but I don't think I'm going  to implement scores like this. I was kind of focused on re-writing version 2.0 and at  the moment (as you  can  see) it's a little hard to accept new  pull requests.
Truly, it means a lot to me that you contributed to the project (considering I thought it was dead to the outside world), but I'm working hard to make sure that version 2.0's base features are  implemented before I can accept any new ones.
Please, please, please don't get discouraged from contributing to projects because of this! I'm 100% certain both of us learned more about C through this than if you never came along. I'll let everyone know when I am ready  to take new pull requests in the future (Most likely in a couple days,  no worries!)
Thanks for helping create a better  game for everyone!

Hey man, don't  take this the hard way, but I don't think I'm going  to implement scores like this. I was kind of focused on re-writing version 2.0 and at  the moment (as you  can  see) it's a little hard to accept new  pull requests.
Truly, it means a lot to me that you contributed to the project (considering I thought it was dead to the outside world), but I'm working hard to make sure that version 2.0's base features are  implemented before I can accept any new ones.
Please, please, please don't get discouraged from contributing to projects because of this! I'm 100% certain both of us learned more about C through this than if you never came along. I'll let everyone know when I am ready  to take new pull requests in the future (Most likely in a couple days,  no worries!)
Thanks for helping create a better  game for everyone!

Thats fine. As I said before, I dont mind which one you use. I just hope I helped out in some way.

Thats fine. As I said before, I dont mind which one you use. I just hope I helped out in some way.

You've  helped out more than  enough! Seriously, like thanks  for everything!
Quick question, what made you stumble across this  repo? Most of  the posts I  made have been buried by new content haha (considering they  were made half a year ago).

You've  helped out more than  enough! Seriously, like thanks  for everything!
Quick question, what made you stumble across this  repo? Most of  the posts I  made have been buried by new content haha (considering they  were made half a year ago).

We actually talked a little bit about 3DS hacking at the Prism Concert. I was the pleb that still had an emunand with A9lh while you had your CFW on your sysnand.
One of my friends actually found your github account cause he wasn't sure how to do something for one of the Computer Science projects. Since he codes better with examples, he googled the project name and saw your repo. We both recognized your name, but later I checked out your account and saw you asked for help on this, so I tried to see if there was anything I could do to help.
So thats pretty much it. Unfortunately, I'm not some random person from the internet. But I do hope that other people play this.

We actually talked a little bit about 3DS hacking at the Prism Concert. I was the pleb that still had an emunand with A9lh while you had your CFW on your sysnand.
One of my friends actually found your github account cause he wasn't sure how to do something for one of the Computer Science projects. Since he codes better with examples, he googled the project name and saw your repo. We both recognized your name, but later I checked out your account and saw you asked for help on this, so I tried to see if there was anything I could do to help.
So thats pretty much it. Unfortunately, I'm not some random person from the internet. But I do hope that other people play this.

Aha, that makes more sense! Thanks for helping out and being a beta tester for my software 😄

Aha, that makes more sense! Thanks for helping out and being a beta tester for my software 😄

No problem. I'll always be here, so I'll be keeping an eye on this project. To be honest, I didnt know anything about C before helping out with this. So I'm actually surprised that everything worked out the way it did, just by looking things up. So yeah, I'll always be here in case you need anything.

No problem. I'll always be here, so I'll be keeping an eye on this project. To be honest, I didnt know anything about C before helping out with this. So I'm actually surprised that everything worked out the way it did, just by looking things up. So yeah, I'll always be here in case you need anything.

I'm just surprised somebody other than me got this to compile without even asking me a single question! You just... did it!
Anyway, my implementation is here if you want to see it!


import 'reflect-metadata'

In BaseFirestoreRepository.ts, why is 'import reflect-metadata required?

This is a typescript requirement that is used to enhance the type reflection with Decorators :)
https://www.typescriptlang.org/docs/handbook/decorators.html


Get NHLBI Security Approval for DMC Tracker

We have received security approval for the DMC Tracker based on the original submission from Nimbus, pending minor changes of implementation: removing SendGrid and using Jira API as the system of record. Both of these changes reduce security risk surface area and should be approved with no concerns.


dont work

#367

request.open('GET', chrome.extension.getURL(fileName), false);

also 	var gameInitBase = mainModule.prototype[obfuscate.init];

hopefully IBlissin fixes it soon. I need to use it at school :D

ye


Dh/infra issue 532

Description
Fixes: infra #532
Changes data storage for term-apply from csv files stored in S3 to a dedicated DynamoDB table that can easily interface with future applicant review software.
The expected schema for each item is as follows:

applied_date: unix time - number - Sort DDB Key
email<EMAIL_ADDRESS>- string - Primary/Partition DDB Key
name: Candy Date - string
github: candydate100 - string - Secondary Global Index
role_applied: sr. software engineer - string
role_override: string - in the case were their role is different otherwise null
resume_review: bool - Resume passed or fail the review
resume_review_date: number - resume reviewed date
interviews: Map
1: {date: number, pass: bool, notes: binary}
2: {date: number, pass: bool, notes: binary}
ignore_workflow: bool - ignore from automation workflow
offer_given: bool
offer_date: number
offer_accepted:  bool
offer_accepted_date: number
rejected: bool
rejected_date: number
rejected_msg_override: binary - Message custom to applicant

However term-apply only interfaces with a subset of attributes:

applied_date: unix time - number - Sort DDB Key
email<EMAIL_ADDRESS>- string - Primary/Partition DDB Key
github: candydate100 - string - Secondary Global Index
name: Candy Date - string
role_applied: sr. software engineer - string
offer_given: bool
rejected: bool

term-apply users have the ability to modify their email after submitting an application. If this happens, the existing record will be deleted and recreated with updated fields using a transaction to ensure atomic changes. Other item edits are done in place.
This system supports repeated applications by checking if a user's previous application has been closed (either offer_given or rejected is set to true). If a user has a closed application, a new one is created. Users can only modify their most recent open application.
Tests

Submitted application as a new user in empty table and populated table

new record successfully created in DynamoDB with correct fields in both cases

Updated role for open application

Role successfully updated

Updated name for open application

Name successfully updated

Email updated for open application

delete and recreate transaction completed successfully

Email updated for open application with other attributes populated

delete and recreate transaction completed successfully, no fields lost

Role and Name updated for open with other attributes populated

Role and Name updated successfully with no other attributes changed

Tests ran with multiple open applications

No side effects observed in other table items

Application closed by setting rejected to true, then submitting a repeat application

User was able to reapply and a new record was created in DynamoDB

Tests ran with repeated application

Only the most recent open application was modified, as expected

publish

The following docker images:
{ "Name": "docker.io/nebulaworks/ansible-lint", "Digest": "sha256:8d98adef2d3d7f9f6705d4333b74b65d462bfc31cf3ca8b0d353563242f2ad15", "RepoTags": [ "09khh6sp0xvms4gd04px1gzl8z870g4f", "0hf3d665xh0zl1hkrqzr210la6ipjqap", "1ajycb8q319d6izc3jqpwi679im7kmrh", "1jwdvf5kay9bjb62bzxj9g2qlln06398", "1lj51767l00nnaa9fh8200bmjbxdg2gf", "4yfc0d6fdan57ki1bjq3jbjqmppkwapp", "5mcy6qkd450gl5b60gkwja56p3i18p0x", "5r3l0iz855gp7jsckfhnl0ffz8nyfhwm", "6855969dzfdzi6pna55sqgx2hsqz634h", "7qsq9l65llliyry1pga9j1fvnbf08yhx", "837q5ya631p2cw7lllvm2hgpx0v11pqy", "a4brdxng1h1895c4q5l8qvnlvrpyl3mc", "b8zd0f2nnnllxgkigmd3lxb9i938n33g", "cr6hg0p7gm15b14iviqiyn2bj7n6x5lk", "cx11fsg47srrbpg41x1kx9zd1ymyqmgr", "dgg92pz55sdwr6wq33n6v0f6sgpqxigl", "gr7cgqvghwcpkkj7br0h3wbyk0hg5cqw", "hqscjlf634xjjgbg2fl7lzxszn7wgb6b", "hwcsgcgg79l6r8x20zr0waiikxvfvk69", "jjvls57k805vip35hdn9ci97i2wlg7m9", "jzj8q80jcrwk95h6sd132mfs6m5hypam", "lbai3dcljiiv8a0b75ha78pias4immkd", "lrindarbbfdgs54y5k5r79lwrf15rp3y", "m53jbk97wxhm8s6xp4whp4zid61y1146", "mm7010awyqfk5c13mgmi272ifxhix4mi", "mr7wwg26dcxbg1cmmd96p3s197mp93nh", "pna5gc3ly83xn5y70isp3kbpl9j3x5m2", "qw32f5019xfm092yjkj0ia50bh8scyry", "s22k2b0fw9bpcg6xnwfjc13qlxyngwhl", "s8q0xm3hrshwqbzxgngn9kp938nj37c2", "vdc52l38cks6hxs5n1qb0fz3kfms4yl5", "wgal6rmrg4smiavzpykf8q70lddbsjiz", "wvnicnfkpsq8s97c33li28zyrlj8yqmp", "z6s893jx5nirjwab7l1jgqy238wzshns", "zn987jlcqrbwfabiza8x63dwg5cxiz8i" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,curl:7.82.0,git:2.35.3,gnumake:4.3,jq:1.6,nss-cacert:3.77,python3:3.10.4-env", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:be87f80b459c6cf1c63a5f04226c26f2d0a4392a08103a52dd9ea136ae783ac6" ], "Env": [ "PATH=/bin/", "SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt" ] } { "Name": "docker.io/nebulaworks/awsutils", "Digest": "sha256:0589df2c6c5593f088528a7c9dbb0921593684b6c3688c3af1c6f08a97d5fcd1", "RepoTags": [ "02mifqmi3b9r4vhhwiszc80h1rd87s0j", "062y3vxhs7hap0v279gy1wrcnmmnngy4", "0afjz2x6jzlqbyp6hlsn7xx1j4v595xj", "0q6n72i9f6w35qg70a8fddnh57jr25yb", "0wrw13hq33i9lvliwgrilimblm1by6ga", "1hx4387bjv85cs424znxr9fpbdbm8djk", "43pax9ygdpviwka1lvqkvsxk3qlkg32i", "4iyc3wm1kjz9lwqwsgvjz8g78hdgxc7p", "4yzrc2fjyajqaihgn3jycfjjsrwrdb7z", "548x109glkycnlfpbfa17skqy252d7by", "5cnip2b81k71qbap8493mmvfp02fk6wh", "5dq3sxqy6ql24adppr4abllkpq51ai25", "7ydhw282rks4v1pv3si8iv0cvaamypw5", "8qj3xh6k3q691phgmb9bzyjqak7s65rl", "9jfmk9gq677qhks1nagk6kagr21b80zh", "9mz9x2m35npczsjgxznwiwlzj85ij9hq", "a2x2gakpv9acj1zp6q4cfk0x34kakh84", "a5d61h3nvmigz60bins2pgwsq7hx63h1", "a5kccnv7dvfjg6p5z0kvv8f4gi8i6cln", "aajc2d2i99cd622pzjyc013z86gckiq8", "ajh8frs9cr2pw02w2h54mclnxp4biggm", "axjz9vl56z0lm8jwzlri7cb80zpiiv3j", "b2brn67ymrvbi8izvxvayi4bn4adwa27", "b2xpdz7r5fdlnyyalsxlzncwlvy1gh6m", "bcwvjifcwgd7mzn8gwx86xlnfl5mf030", "br0g08h90amarmcsl8ic7iji74wfzwhk", "c3skllz0pvp6a78nf3c4fck7xcg1yxq5", "c4vyb1p0lch8czxncl0nq685wick8fnd", "dn5a3qap4l4r83xb704277x5j6hcal7a", "dz783iaashdby6phqf9pcydxsw1bbjq0", "f9lc1bvrwz8wbjhccp6dyg2yvzy56npg", "fd6mchdar3ja13ph0jp1s8pnw7ixfahk", "g44npkrgrh2qj2y9j1a9n6frcyd2j45z", "gv99dxfp8hy5w9dl16p9wc7km3mg2n1f", "h952m39vshzpihy6cgmp17gjszqq3vks", "hbqmiwillbddpzdjdl0v8y5h1xxy1bwx", "hc1r0zhhmwdvz0ygyyypq0kav5yw6zfn", "hf40qkx21324n4gh7kkz0w663ja7hmd0", "hx1a61jwx4r2crri7iph7ygd19gbqab5", "ib0v6zkv2qqaidwda7sp64pa0jfc0vbs", "ic2z7iflfwvs0dxbxay38shg8bdky6dg", "k2c75rki35d8z8giwynras8nwrsr1l0z", "k3i9bp4w5ndn7ai6cylbimxybqln4nrc", "kbc4fdqiaiwgbiwxf7gbd123gf01ph2z", "kdrjhrxqp7a0zygv8x5cq4p88dv5vgm6", "kl55657f4yfpi6b8kj4f1vwgk3jdhvza", "kmnk9vx5d52q0rsjfzdsrs5600cfkjb0", "l4vf8g6g8wfahhhc7c1m90sm850s2sf2", "m11a8hm9d6g801l9mdfzsc9n17nzni3g", "m71b1r53cdzw1hlhziavgi0hfwjqrrl2", "mx2cxzj4sfb7rnvywwjm3rg6s5vx5dis", "mzqlmhc5gl3h3k10bn1l0ghr204n0pqv", "n2m55acawpn7y06h6ifjbyzmn9n44bhy", "naw88p3wd88v1wba1lh70zcrad89sl4r", "nzbazzwdq9vy9rg10jcp2dvc3fs3n1bp", "pbjgfkmi0wqiwd1flzwm7rz8snd50j36", "rrcibw1y1wxbjsjwwpgiw1qmxg7x7a7n", "rss9pb0cmnbhl49in406s3i7hiy466ps", "sg814n929qffnj1xd0637knpgaffzzpf", "sjr0mavplaws1dlxy3vr2880v0jkhh3x", "sy7z5ylf9j3jrbhgd8kcpnnndbch3v4j", "v0z5n26qg181476nkff5licn4p7s1jcn", "v7dw7988kyhzsgjzxaiybhk0a9wsbm2g", "vbp6wk6y3gn143g5sfsfgpih8shr2sml", "vswffwd7vfda4qhislvv27vnx48g7lcx", "vvwarqcmz7a9r6296y49jdq04q0phrhm", "w4cwy90aa2b1rrf9nqd5qjcflrjh0129", "xaacyvsd2q0z4yz111zrj8y0za422gh9", "yfws0rvz76xkiq0yid7cqcg0zi98ab1y", "ynizhwjmd25jf0np5wi4wq34fbd6n9db", "zc6w4ys5ka740i167bd0qp6v8f63dp0i", "zd1ilhdgfdppgwcm4xsj3nfwbid7fk9v" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "awscli:1.22.88,bash:5.1,coreutils:9.0,curl:7.82.0,git-lfs:3.1.4,git:2.35.3,gnutar:1.34,gzip:1.12,jq:1.6,nss-cacert:3.77", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:31d3904ee778486ecba2e05b987150e8f12d0d942cd46332a1fface881e63951" ], "Env": [ "PATH=/bin/", "SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt" ] } { "Name": "docker.io/nebulaworks/flasksample", "Digest": "sha256:96c7fcca49c569e1bdb9d43270324b3e23747adc2f398f3dbe2099a19e2df0e8", "RepoTags": [ "2x83r1dphcf3i50sv4m1pi286idcpxnf", "3hnryiq8q9hy0fm8cfzm92d0yj8anybk", "46436y8vy5dm1pcznyqnbjjsbcqfsa13", "4d3fpl6x67hikwa8p0vflb7miz4rnk63", "4l3pykmplqnvl6q6b13025frbf7s7ij2", "4z6g573skmq11kyg8agl515lysdadkqh", "54p4a6ri41prjrp9w9wni8v0bigs8j60", "5dki2i2pwniw5y1jhfrzp6qhsnh3b8nb", "5fi5d6s9qb0ayfxvd4czrwvrk0jv9q1r", "65j7jsrql5qicfadj3dqbinyaaisi5sg", "68rag50ayc9gsi7n4bwdbjq0ah2pcs0a", "6q1rg8nbx5yzhrs8y16l8czmy5xsqncc", "8mmc4ig1r5k37wc8xk5rx3mf7fbm0ds9", "8qzz162pgn7nhbic9g0vw209fs01n6s6", "8wp5sb35h86bygxchcv9cgcsxzh2dc5p", "96j0fwid588a3rdawijlmlswxbfhfl5q", "9dqy2plqw2n9nynz449adx8rd2633a16", "9m2k44fp1v7nvijz8mz7nkac10fs8wgv", "aggzwxjm6v6jfbjbwn1z0fvfp0xiqid6", "biayqv0sg5v36dvnl7yh6gg941gl0ba6", "c2n3c5vw5axr688bn4x91h5j1fl8388y", "c34ssc86npknkb6ppmfi4b9zvkxax4a8", "c44zddyvxg5b9qikb28gva9cznsys502", "d7m3af9b424fnb0niqs1s9428vqn7v76", "fgi5b0x05qfav9cg9ly8mn6pz7a2gibc", "fwwz8b6jm0q8m2w0lgw68mila23r08cp", "iiij8fj3jib4qyf6dzm64a9c79wrhk71", "jb78a05hixi8d08zlv5sg6ml3qsfzisd", "jd35ng454lzbzychimd6pcs0sx8w66ng", "jg3sxqk5msyl62asq4252m5faapqq0k7", "jy7q8lrajn09kg58psj6n3hmkj5ga9k4", "ka0wy2kixsvrlaiglz1l0cr76y5dfnam", "kxhh6w3c8fgn4sxw90j573vc2p4imnzh", "kxhq2jcijnkp8qhnlhy47023jcd0rj52", "lb5vs7x46v4skzigvkamsw1121v87gfh", "lg657j4bv178x5sav6vgq25qyi7hcl7l", "lrpkr89z5qgb9sacgy266j3yxgrxi80a", "mk0ldb79sxm75wy99zk195dngl3dk5k0", "n0cp44iqyw67mfqg18gqcfvqdkr22dz3", "nyqmq3dsyzgm84ifcv29f4xaa2g60mnr", "p028d080qwsa8mh0lzfm1vvdh1kw7a8m", "rzk3f7a3w0ww8rlzi3401z3bz4mkmrn4", "vq9wsp3l0yx3vmjazfjf7qmv5952pik9", "wm1j66cwg7chrliqhfawrqwwwwyzlwhs", "wq3kagq6zqjfklx4y1s12gqp8fhd32sk", "xsi7aqn2j1bri2wkgc1zzk159m2dib3f", "y5vsalf7nzfpvk9n4rlzxwkhx7d13scg", "yb0fhb8n6n0snampxmg49ka5c5jrb2y6", "yi1b05aik0iqjzpxqyy8nfzhy242s2y7", "z0qrlc5rpybi69hljcvdx3hlzac6f3g3", "zzpm4r45shaicn75lgvlnhxfqk3rgm9x" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,flasksample:0.1.0", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:35a4a7f33dc06ab38997070fbaaa563e4f9eb19b9663f36c61b97592f452f347" ], "Env": [] } { "Name": "docker.io/nebulaworks/helmsman-aws", "Digest": "sha256:ee3e8ece734b5937a23a3f008909688e12c6134e7704cbf99621d5508e837bbb", "RepoTags": [ "017agn5z2mr7pacaf09m8icbqwa5g01c", "0r4rskk3b5han0zzncj67sjhkm7lip1w", "144mz9zbhrcip75cyqnp4wac8pz3fxdi", "1bhgpxkhzfc42i0dgxqxaw6bd2lhhap0", "1l1jghmwiry8vdyvy6l1la292mx5z2v8", "2d8hynrlcc604m24v6lfxah1fr6lhjpp", "2i051yfnpypb2dljzdbxdz04h3a5qdqc", "2lzm28bwssv9apnf83sxgxwdfymmxm8g", "2slspfhan633vfgsgp8k1ny39yd55yy1", "2vil2iz4gz0lmcqsg92kxylhh4mds6jv", "2w05w5i610g4jqnhcbhv1ayd81gxysds", "30q2z6wbcbn88851pyyyns0bn5km4nwm", "36na3i0psj09247r3mswgf2czazg959m", "37yxlxhpyp3ai1xs464ldif2gmj3yyjr", "3dz3i6lqdnigfnq7mai6vccnmf4fyjbx", "3lfza5jmy2g9r6sjrgf58qq87mdwcv34", "3ml4yvayn282z32hpr50sl7ag5kdca72", "42ygsh6v9ns61hn7yrrvjrpa7dz0ypak", "4l98nwjjb5lz1875n5pmvi8i6s4gp9a0", "4szd9xflnkl3ab9h0mzjkfrybzps3hs4", "4x6ah6c8mgyn20awa9xrq16cw1yz9d4s", "52ifj8li3wjpraps049zyq67zqvw7m04", "54hq16h32rh3g6nbxmf755d40mvq30rg", "55836qcrmhfrfvn467n9dcrkpnq033ay", "63j2y1ys8q4l7qxh6p42lv50zrr71k5p", "686gs4mwpvsisq9c45n0f19wmp1zwada", "6xs7yjxg32fc3vsh2qqvh7901jgbfc3d", "72rs42ar65syxrgq6w0qyv98n97zkr6n", "787wzh711cg6l2s92vn5rlnkw24jslyd", "7ar2sigpxxyll06yvgan428qn74k0vqm", "7hl8p275d7f3gcnam52s7hg1d307a2ik", "7mc83swh71lgji4ar8fz8a1n13zq934p", "7vc5g5g4m6wvg75s527h5mfimixh1yl0", "91hn17cblaiv1wb26vvwz05m3787c4zv", "9xnr8m6mj35mh6fwxx1nsxp11arvm1sh", "a4ckfmdnkmya7asi0pvjwd5v8hy5b0fw", "a5kn44776qgdm8dgjmlym4z79qhnm6mn", "ajgcdsjx2hy33jgrvgqxkjfv28bazfz1", "axk5j5bhv0sv9ys1xj4bmhc34kfw5jkn", "bbjyib4li8ipq2yvyak79ck7kw9k2dkx", "cr9n83qbmcxkll790qhsmqk3x4733zdv", "d5vzm6xvcdv93dl327shyc5k8af6vh5f", "d8r0smi6314pygg8sblnx33h4xklgnzc", "fh5ba96qrhkkgilk03srysz5qm7kg0j8", "g9mxjnw3vmxnzc14hbyl5rvjmhrkzdcb", "h6a3l42pl14r96j5y1kcmwf5b4g8d5rg", "hwjzmzm50q20diz32nlmva91cpjjy0gn", "ibx9pd0yzvspf6gczmdmmhmam9sr25wr", "idrymiiylkvrcldbavjf4sjyscvkndkw", "ilpcmfgzgzskzshyd9j8rpxvrs3slxcc", "k345a553cr4aicxcl9l7ns2rjzhiv62v", "k5kcp1pk20jfx24cvjbnhf0h5ax25hxh", "k9g8l9d86xw2mk9dag8y6ix0jqq7w2l1", "knha5b2p70xhrqyy5awl8djdzisn2sal", "l0mz1yxw70ab4kmqnvjbcxklm088q7l8", "l1wxa42bzbgvfiakkjd2sqd9c6a9ka8g", "lf015xyadsq38mvllc2cvb0n9dfdj6zc", "lnv4scg68mn4ambxibzq7rswrfapcnrk", "lpsiwff3za9ma0hsvwz9kyvsc8han1nc", "m4p9y2j9jwvrlrzcyk0s7q5b1qh3i4xc", "m9kvdhzskjmvd6lbrmx9n195cm08amgq", "mpgikzzyqmx0x97jq9iwmf7r9xvm7x38", "nlpym68q25fyyzdzq7xd2gcbibbwmfyb", "paks7yd7laypwmpg3i3mbvw937hdgdnc", "pbj9q2qyw511wfy18g8lz9jw2mpc5qvw", "pfvnzcg5m26m0bd6cj4v6g7j6qndi2m0", "pjmiwhkh9ibil37479kf1m0fnvs591zd", "r1mqc8hpxd84g4w8cvzik9zsa2f7ff0z", "r61mylgybid4m0wrc3881fxvw3a97nr0", "rz9fgbx5kvzid11v516zk8l3x31bxph0", "s9nhvzqn3acjcfinaqlsd07hnc7bkm0i", "sa0vwq716pa3sgxga8r9m9vjq6h7b340", "saj7j4vdgy3infrgn865xlbb5n73lsd9", "sb47bkwd854ws9dc4gzsvnln06pidxjf", "sgv2bi85zdbbznixhpck8w5c29np1w87", "v4mlmsr2lpvjh3pykpg3b3755zsp5yip", "v7jsvzj6gr3p02s2lp36r3i7rlrij76w", "vibjzpbdqxyfxppd37sy8sskbn9knd10", "w01q6nzkxlxa2w0kiai4spxc17mq7a04", "wm8iq5xlnaj7p3xvla0v4jjxgb0qd5pf", "wpp95vzda4gwgmsi7s5dfsjhx738b4np", "xdahy9hh3fnsws09w7ksi65d27kra0i1", "xym39zji91ga5rbw6p8xbwy5dcbizbn3", "ydppjgwvhqd65w5l055r8xavylcwcaz0", "yzzsdlfn3d4ayp87f9k471ahpsz0hr47", "z0dqwwrcd09a14qp4nqk7ql2g91h3fdz", "z3rr5450fi5mzz2kb9i8a9bs4f1dq5l9", "zmz5fxsfpmjdf28mmknxaqwp9ig4kyxa" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "awscli:1.22.88,bash:5.1,coreutils:9.0,helm:3.8.2,helmsman:3.8.1,jq:1.6,kubectl:1.23.5,nss-cacert:3.77", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:4e0588d0d53360e0f3a00dbd1cb817a87408324088e8d47660ab3135d1aa9982" ], "Env": [ "PATH=/bin/", "HELM_PLUGINS=/share/helm/plugins/" ] } { "Name": "docker.io/nebulaworks/magic-wormhole-mailbox", "Digest": "sha256:b346ac86255d48d929143316ddf26815219880e6d7e512cc7e9180663d6eee61", "RepoTags": [ "0m7wg48v79y44sr6n7b9hiwhh8jq8dxh", "138ca83w6z67cqfj6j3qnrg0cwiq35zg", "183k39146rbnkjsd7ifkp6169g5sqrd7", "1b0l1kbsfnvsp2hc0825s66x6bm3j3w6", "350xjs0shfdl86h6wwn78jckhq2640l5", "3iyzjyd7rd4gghnvb2fs6xf01154922g", "3qsccb3a1wv9rrf5vvj7cpv1inmi1ah0", "4206dmnf9c18dcnxlvlbl423x3l2p6x3", "46f5vfsc69l1zmzw2f5z02isjnp7xfsd", "4l334b8hqhg051mwjanm159hmr1vj6zr", "63insgj15jx0qn14jmcixk8x5svq41cl", "63x6wry4921pwqj3qs72ykcggr4l7an2", "689cg14skn51dqs5rad4579lajq8qa32", "6gpp3wdlahx78lm0d3ymhwl301wjhxfn", "705kflnqwjdm0faxwf9rwsynglb51mi8", "7868xcav57m6jaak54z97b87g0016sv7", "7pdcv4l8yszm7s1za0xd06pbnhqqdjwm", "81j5zcmmz59azhqbyrz3qbp4sybnnsbk", "8zi126fnfyvb5825xpd5qpbiykgkbz72", "8zk1sf2vvxa2w0wzyc05v3qlvyrlsr6w", "9p6cm9d09flkscgdmh3zcp85a7kbyhdx", "9rld5c6wm2h5rg6pwcrmqjfa3lsn3l0j", "9s06afg8b3sgnq8mdx0g5sz6377ai8cb", "afm6v1gw9rk0ihga76gcpvkjcy8y3qk5", "bgm92hyjwmaayyagdpyadsz2wy0w7wb9", "bvmm32s0yadycqbyv2yw2m7hcjjgk0v7", "dcjzvca7cak7qlqz0ibwgc0k810v7fks", "dhcn2v5vrq6xskpi00ihnmvnh0wrqkc4", "dmlj2inrm7af7mfc412jkdn6n1s9hg3h", "f5d5asfq9a7d4969bpxn2l9x2p5x5gfb", "gcp4cly8dxh3ykmrzqx1j13dygjnf7ql", "i4aiffyr6501ism0si9jvp2ggi89x08k", "ijpafrbm4mdbp0314qdfir2lx9raqb8i", "ilijgx93k6pc9ih2bq39w6y3gvhlhzhi", "iphf9vs3ppknkagkfv4q02jbyxbwxpgc", "jd975cl6d7gvbhszy74zvh6k94m511gy", "jf9w4rj0gz8qnbnwwqcsrzp1bnmrw009", "k1kzqaw3p8vfz2h6p4ipzmnxa1wfg7gy", "kdwng0vdvf0s9vjz1lwgkr7l69g68fji", "kgj2b4lfv5xsci0r32n7z2kayp65xnhs", "lf9rigldbnkkqw7ahish34qyqc885ffh", "lizc5jamh39zy5xm4cjhnd3a9v3gxzm9", "lizqad1x8vf27gjanjz9sfvz772w7gw8", "mncbrkl3cvkqm6gd3hjiql2ci4djf1gp", "msahb86b470r5636v8imzs8sghgzg38b", "njf33wky3rf1fpfzs4f42nn3pzzqsjb7", "p3krs4mic049x5ljdjyqahfncg7mi4d2", "pxyn1sbddrafwaxnzzfw8bmakbhhb0fj", "qhz69y0vvcp6qhpm5pmrlrd5995pz4cv", "r3vf7jxiwd7jgddib176nxw3p37n3ipz", "rkg8cxiyg2z99620bmyxgzqllzj9lrfh", "rqzqdy8gxqvnv6zvm7i925zlp7zhrqcb", "s1gqq531a1r0aqzz11ia3v1sf9wigf9n", "s7wqd04glyvs2b7kfm7559g43lsxacd3", "szjnqqlf679f3i3gh66z0kv1fxcd06fv", "v57lk1gziq5d5hlkz99yvwzz91di205z", "xy3wmckpk7imbj3wv3yw9bfzh6bqyzkk", "yg38kbca7ahgm2nms4rddq3kr51lv41m", "yyx0aasi1ypf9jhq0q3qd7gw1v40h6xi", "z89yh6f8l98saakmrr65ahx30cl9jzab" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,procps:3.3.16,python3:3.9.12-env", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:c4c3a3802cf2e6f2fd426f3bcd4d71cc473ae5130434a02f096371de7b8d5e91" ], "Env": [ "PATH=/bin/" ] } { "Name": "docker.io/nebulaworks/nwi-pr-utils", "Digest": "sha256:0779d324d703dd93894735c1e9efcc0aed46e79f82e65a76f3f117486fe4c667", "RepoTags": [ "09pymw41x3d1zar4i46pbdjlhf51nc7i", "1qcv3ddhn173p8zzqpps4bgvi96c73gc", "1vvy146w2xc2ia145kn88blwyg9303zi", "3bvyfdl24iivz1ywgy27jjl6xpbaw9z8", "4ri9qfysqcry3zzjr1nmfwb0zalfl0li", "5f31skcm18r8x273by8bip4s974jdnaq", "5x5r35ws5h8r4pig32s80hw6qfc1wvxw", "6n087vdgnm05ipil8zkrj1ynsw6l1lqd", "7h37m4l837xgdpvil2gm13jql7sdzijf", "7w34va7ghlk4x5pj8h9f6xkb1xq60vlg", "8da78vfisd4431v063f59ybss8n6cgr2", "8glawain89wy3sp6i95ys7l7nyrsw38s", "8s3mm159mxlsgwa57fdfaarcm96m0z1z", "9gga1vwcxr09i95wxzsg0chmswdvsh84", "9n4k95fhxsy144rbnls6biyi74jpiz1m", "9w9qy1d813rxr9kdw4hvbzwjmdswycnp", "af48r4y9qz0rys0z2ph8av42hvg9ffx2", "bgf34wksafhan6a7wvvfd7h37na20566", "c72vkg7kkfl29fkbjkmii36nr77x3367", "c8a0x9ddsnb05nv16j8sj8ha4n3giq5h", "ciaif8kc0i1pqwcfpndgb88jpafw65cb", "dq1grw33viivjir4irdibn32vl49nqwn", "f0gah5pqksnhf4v79yaf6wzqnf80bmk7", "f4p6mkakbl58807jrhwsbl5p34xr1jmw", "grcyhn1x6514ipfksgm05mx25dn5srkp", "gxap22kxfa09znfw056hilmw44pq90qd", "haqgpad651zq3f94zgky4ydz1lw4j93v", "hkmxch5685cg662ibm4dmyvbx1cqlkm2", "hm76r6v16d686wr2blyypn1jw01gx2qf", "hpaj9r73fl3c65j21lhc2dfpb4x61lrr", "hqg743d0ply68g926p4q71gmzmrzbd84", "hz31r35m48i4sfr43zmnq1xi7ph8cjc6", "ic9a1h2pnmrzympwan1pyxf1y13736fw", "ilrnwfqykrxan42qcy421isabawjk0xy", "imnysry78shjwnaznjlmjhnixrgkhd07", "iqaqf4a5cq85f9xh22dr2d2jxl1bh27a", "jff36955m87va40f8cfzwgwb04gv0yig", "jnd9wmc78n88k1wz6x4rbprwwrh47gbb", "jrnhvxlar27ijx7vpfq5icsqwyd936v8", "kcg4l097kn841w814d425ar33y4alzsh", "kxfl84j0xyy3xhr0s6ga03xw9y784n5p", "l8azgxbr5xv6if0fa5jraxn61r9if6yq", "ldmmwra6z32jh7bqxp406c5kag8z492k", "lx98kzd4gy5604qhblmx4b8jmywjlf7r", "m414fr960g8i7v6a47grhlmd9ngvv7z4", "m6b010vncwjifnjrninllnrs5yvdlsyl", "m84gwswh2k38aif8psvja3mjhxsbp41g", "mkr89zsfj4dbf02b2n124cx6pgh94c9l", "q550kbmhsbm9y7yf5xkg1hghbpl8dgla", "q7bn3k5xgsa0a20wd99pib2h59whzla6", "qhf6flqw01v6wwaww9v1jj81k3y995nf", "qw1v97v9pwdhgasd755l33kzh1r1ydss", "r2d3pp1nhczk99084nihchn1rbrakiyf", "smyaf9jq68i7fx0r9jn1cc6dbx5abyjv", "w8n8sggdlcaad4cx50jfx5yv1r2z6qvj", "wrh9wh8124v3z8l7gnk0avzp09vsq6gb", "xvnir17gx4b2jc15wz55bamw90pzrjmk", "zp9846y8pdd3ydfp8bi170dr4rrprclk" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,tfsec:1.19.0,yamllint:1.26.3", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:cb8109467374f540cac5bff55015d61c50cbfab5e0f5033c08014fb9d91f36f2" ], "Env": [ "PATH=/bin/" ] } { "Name": "docker.io/nebulaworks/pki-validator", "Digest": "sha256:e4593bad42d2ed8411687828e9a71c88019f6da60ff67aecbc06c4b8b3e49065", "RepoTags": [ "009s2mqrl31kxcssdjcr8s6f9qhida7n", "0ky9lc8k9cjn8y1yjdrcyjysi4f5mpjn", "12x2y4s04wqd7vzblyknmb4i9wlrbyg7", "171fampm86jhqnb40x2s0n08r4hv55h2", "193ch432hry14dwwgfzw98pr41w36kz6", "2s0sq3h58kpm1gp5sa7xghww5gn9vgaa", "3lxckwmik3117lnxd7aj9nkhbnziv7ma", "4chfkkzn2pzl98fl56mjfzwwfcccm4dp", "4zdwvwli58ykjiigwqxm6ggwcbivd0ks", "5ydsd6yyfnhilz53bv5f31gwzrpp0yjf", "879vbhnlpb9fihpldnlwd6y2cxh449m7", "8hs2gsf3n1qq8rlg8md4m3571jkddg8g", "a5wnawgisj7l2995xy6jan6m8pyxxqrq", "a78vqgf0nk9m39f9jz56qcqkz3pg85vi", "axj6z1kljspj1101vj9pc3nmi0yxcq52", "bcykjxyzc4wpgfvz7ba4n389vcgls45v", "bh5r69n6br6bxddjg52k3rrlz7sskhrs", "bsnlb78w0hpzkx4m7ba40lm0qz2212js", "dn93l3z9qyh06y7i1ba0sdaxydlgqib2", "dnvg43r1cpmdjcfphknzgijmg7jx16cn", "ffydpxvbyb9ls5nyzkbzvhbjw8b8ls2b", "fjqp40jq1fvzl1br6mhhr171q27xzm46", "g7hfbpy7vw7xq84zqhqigydyzv60k6s7", "gj1vf5lrp83sr1k929l3slamy1k34di7", "h13qqs6wwmkz9g5hb9ca9hnyzchsp2al", "hg66vz8gd12bc035xaflv9bvyq9xi9yx", "hw5hqhalyr787sa0l73qzfgrs6r3xy4l", "i5h82x58h7qrvcyk2v1gzqwhb6w9kd0s", "ipamimb49hr2xw2l08d1p4r7jg6r5814", "ivfckf8dhlf3dnjgy6abs5rqswahb23b", "iy254z2954z7zanh9dfbyzw6n00rkych", "jqx100dphlsaqbv9h6abp8ci4a4v7ka5", "kb7qwr49yrsjzvh2kmayga6l0d89cd6d", "kvfqd087z62z3amrvkzpx48l1v0blcdp", "lkr5lv92r9lin6s156x7x005dyikb21n", "lq6c446k04lnv7y5gyrzmq9lign8n265", "mh0wm9hijxv1n580cki2fj7vvngcf0kj", "pmmsixyc79inwhsifks8vmj53f52i9ph", "pw9il8xx85cgrdszn1vxmv319pyifp72", "qwcky9z36f8q51kd3rjph1fajmgl7d7n", "rhpf73j3qcmzkb5crdjn977iffqd1zqx", "rqs2qm2w6pqkvm8qhg6fpg1ddkjfvyc2", "rwx2sxnrf9b5yyaqyhs28458pzfiw912", "s1l8jmzblv13rnzs9ggsd2xrssalj52a", "v8n2gd8gx7i2hwbmbvpy083gqng3rv4s", "yxdhv9knsflnpfihzksi2m7qix2kircl" ], "Created": "1970-01-01T00:00:01Z", "DockerVersion": "", "Labels": { "com.nebulaworks.packages": "bash:5.1,coreutils:9.0,gawk:5.1.1,gnugrep:3.7,gnumake:4.3,openssl:1.1.1n", "org.opencontainers.image.authors": "Nebulaworks Inc.", "org.opencontainers.image.source": "https://github.com/Nebulaworks/nix-garage" }, "Architecture": "amd64", "Os": "linux", "Layers": [ "sha256:91f107800fc4b27ddaae5466f0d9d1253b90f6794217cfb6c4cc6c283f602f1f" ], "Env": [ "PATH=/bin/", "SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt" ] } /nix/store/kjyip6ys5sbg6ycdsxrkqbawp0ihi924-docker-image-term-apply.tar.gz Getting image source signatures Copying blob sha256:ee75908ce35e92263469321f4038784a3deee958505c22d2ab53f355b763ee31 Copying config sha256:54bc32bcaacbd8f7dee7e15cd47a1f54546c0c7c59ca0d9ce5b0e4c877d8ea98 Writing manifest to image destination Storing signatures term-apply:kjyip6ys5sbg6ycdsxrkqbawp0ihi924
have been published on Docker Hub.


TypeError: cb is not a function

C:\indospace.io\services\node_modules\uid-number\uid-number.js:16
  if (!uidSupport) return cb()
                          ^

TypeError: cb is not a function
    at uidNumber (C:\indospace.io\services\node_modules\uid-number\uid-number.js:16:27)

My bad, I was running node app inside of my windows node JS environment, not my Windows Bash console. lol


Preview show error when change name of Cover Image field

I am using the default config.yml, when I change the name of the cover image field to "featureImage" like below:
 - label: 'Cover Image'         name: 'featureImage'         widget: 'image'         required: false         tagname: ''
the preview feature show this error:

If I change the name back to “image”, the error disappear.
Is this a bug or I must have a field with the name "image".
Thank you.

Hi @manlm, that field is also referenced by a custom preview template:
https://github.com/netlify/netlify-cms/blob/9627452de0eb15201a06de93d9d03e22fe0be9e0/dev-test/index.html#L123
so when you rename it, the template breaks.
I'm keeping this issue open in case anyone would like to improve the error message when it happens.

Hi @erezrokah, what error message should be displayed when this happens?
Or I need to configure things in a way such that  if we do change anything here:
https://github.com/netlify/netlify-cms/blob/9627452de0eb15201a06de93d9d03e22fe0be9e0/dev-test/config.yml#L47-L51
if the name and the widget change then it should be changed in the following places as well:
https://github.com/netlify/netlify-cms/blob/9627452de0eb15201a06de93d9d03e22fe0be9e0/dev-test/index.html#L123
https://github.com/netlify/netlify-cms/blob/9627452de0eb15201a06de93d9d03e22fe0be9e0/dev-test/index.html#L185
Am I right?
What should I go for?

Hi @devnamrits, yes that's tricky as the error is coming from user custom code that we don't control, and can't be sure of the underlying issue.
How about showing a part of the stack trace, so users know where the error originated from?

Hi @erezrokah , Then I'm integrating something like that. Since we have a common ErrorBoundary.js file for producing all types of error in UI as show below:
https://github.com/netlify/netlify-cms/blob/58d67963036509f0426ef1351e28e25f5c3eb897/packages/netlify-cms-core/src/components/UI/ErrorBoundary.js#L142-L145
So, if we show some stack trace, then it will be applied to all other kinds UI error as well. So we're good to go with that, Right?

So, if we show some stack trace, then it will be applied to all other kinds UI error as well. So we're good to go with that, Right?

Yes I think we're ok. Probably best to explicitly generate some errors to see how it looks in the UI

@erezrokah
Yepp, I'll try to integrate that and try different scenarios by generating intentional errors and then will get back to you! Thanks for your kind advice.

Hi @erezrokah, Will this work fine?? I tried producing a few more errors. The error stack trace was there. If it's okay then I'll raise PR for it.

Can you please elaborate? I'm not getting exactly this PR and draft PR thing. Are you saying to me to deploy a netlify-cms app with GitHub backend and then raise an error and see how it looks?
In the last comment, I was talking about just raising pull request for the changes that I made to display the stack trace.

In the last comment, I was talking about just raising pull request for the changes that I made to display the stack trace.

Sorry for the confusion - when you open a PR, there's an option to open it as a draft PR, see https://github.blog/2019-02-14-introducing-draft-pull-requests/.
It communicates that it's a work in progress


Authentication just stopped working

Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
Terraform v1.5.0
on windows_amd64
+ provider registry.terraform.io/hashicorp/aws v5.9.0
+ provider registry.terraform.io/hashicorp/random v3.5.1
+ provider registry.terraform.io/redislabs/rediscloud v1.3.1

Affected Resource(s)
Please list the resources as a list, for example:

data.rediscloud_acl_rule

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
I am creating multiple instances of this data source, but always the same one
Terraform Configuration Files
Both environment variables are set for authentication. Both were successfully tested using swagger API calls:
$env:REDISCLOUD_ACCESS_KEY = "OBFUSCATED"
$env:REDISCLOUD_SECRET_KEY = "OBFUSCATED

variable "user_list" {
  description = <<DOC
A list of maps defining users to create.
Each map must contain the following keys:
- name: The name of the user to create
- password: The password for the user
- role: The name of the ACL Role to create.
  - This will also define the matching ACL Rule to assign to the role. Eventually this will be changed for more flexibility

The name of the ACL rule to assign to the user
This can be any of the rules, default or custom, that can be found here:
https://app.redislabs.com/#/data-access-control/redis-acls
DOC
  type        = list(map(string))
  default = [
    {
      name     = "admin"
      password = "admin"
      role     = "Full-Access"
    },
    {
      name     = "writer"
      password = "writer"
      role     = "Read-Write"
    },
    {
      name     = "reader"
      password = "reader"
      role     = "Read-Only"
    }
  ]
}

terraform {
  required_version = "~>1.5.0"
  required_providers {
    rediscloud = {
      source  = "RedisLabs/rediscloud"
      version = "1.3.1"
    }
  }
}

data "rediscloud_acl_rule" "selected" {
  for_each = { for user in var.user_list : user.name => user }
  name     = each.value.role
}

resource "rediscloud_acl_user" "user" {
  for_each = { for user in var.user_list : user.name => user }
  name     = each.key
  role     = rediscloud_acl_role.role[each.key].name
  password = each.value.password
}

resource "rediscloud_acl_role" "role" {
  for_each = { for user in var.user_list : user.name => user }
  name     = each.key
  rule {
    name = data.rediscloud_acl_rule.selected[each.key].name
    dynamic "database" {
      for_each = var.databases != null ? var.databases : {}

      content {
        subscription = var.existing_subscription_name != null ? data.rediscloud_subscription.subscription[0].id : rediscloud_subscription.subscription[0].id
        database     = rediscloud_subscription_database.database[database.key].id
      }
    }
  }
}

Debug Output
Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Expected Behavior
Rules will be querried from RedisCloud and returned by the data source successfully
Actual Behavior
401 Authentication error
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

terraform init
terraform plan

I can only imagine that it is something I might be doing with the authentication...
I am getting the same error when attempting to create a cloud account resource
╷
│ Error: failed to cloud account: 401 - "Authentication error: Authentication failed for provided credentials"
│
│   with module.redis["poc"].rediscloud_cloud_account.account,
│   on ..\..\main.tf line 55, in resource "rediscloud_cloud_account" "account":
│   55: resource "rediscloud_cloud_account" "account" { #! open for testing
│
╵

Ok... so it owuld seem that the user that I created for this task need to have the account verified by clicking the link on the email sent on user creation.
I have done this and am now getting other errors... so I guess this case is closed and I will attempt to fix the new errors...
Thanks anyway


imp: deny selected client types from VerifyMembership rpc

Description
Deny Localhost and Solomachine clients from VerifyMembership rpc handler
closes: #5848

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

requires https://github.com/cosmos/ibc-go/pull/5870 to go first!


fix: remove chrono time dep

There's a possibility of a segfault in the time dependency on chrono and we don't actually use it, so this PR removes it.

@KartikSoneji any idea why CI isn't running on this branch?

@KartikSoneji any idea why CI isn't running on this branch?

Figured it out: needs to be branches: "**" instead of branches: "*", just FYI.

@KartikSoneji any idea why CI isn't running on this branch?

Figured it out: needs to be branches: "**" instead of branches: "*", just FYI.

Ah ok, good to know.


Trainer.predict on really large dataset cause CPU out-of-memory

Bug description
Trainer.predict(model, datamodule) on sufficiently large data would cause CPU out-of-memory due to the fact that results are appended to a list during predict (this is true even if setting return_predictions=False): https://github.com/Lightning-AI/lightning/blob/4e8cf85b0cd5128adcec3f3ad0f2254f417ae1ee/src/pytorch_lightning/loops/dataloader/prediction_loop.py#L103
What is the correct way of running prediction on a dataset that is orders of magnitude larger than CPU memory?
How to reproduce the bug
# Just always return `None` in `predict_step` and track ur memory usage:
def predict_step(self, batch, batch_idx):
    import objgraph
    objgraph.show_growth(limit=3)
    return None

Error messages and logs

# You will see memory for type list will increment at every prediction step like below
list    11320        +1

Environment

#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 1.10):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response

Sorry actually setting return_predictions=False would fix the problem, I read too much into the objgraph.show_growth(limit=3) results.


Version 3.4.4 Can't build OpenCvSharpExtern under the Windows 10, Visual Studio 2017 - Windows XP (v141_xp)

Summary of your issue
I  Can't build OpenCvSharpExtern under the Windows 10, Visual Studio 2017 - Windows XP (v141_xp)
Using Version 3.4.4 I try the following steps.
1 | git clone   https://github.com/shimat/opencvsharp
2 | git submodule update --init to get opencv_files
3 | Start Visual Studio 2017
4 | set the build configuration to x86/Release
5 | OpenCvSharpExtern  Properties |   Platform Set = Visual Studio 2017 - Windows XP (v141_xp)
After try to Build a got this error.
Warning | MSB8030 The linker switch "Minimum Required Version" requires "SubSystem" to be set
Error | LNK1181 cannot open input file ',5.01'
6 | OpenCvSharpExtern  Properties   |Linker | System | SubSystem =  Windows   (/SUBSYSTEM:WINDOWS)
After trying to Build again I got this error and don't know how to fix it. could you please advise.
Error | LNK2001 unresolved external symbol _gzopen
Error | LNK2001 unresolved external symbol _gzputs
Plus another 80 similar errors with other libraries.

Environment
Windows 10
Write your environment.
Visual Studio 2017 with all the updates
What did you do when you faced the problem?
I describe all the steps above.
//write here
Example code:
paste your core code

Output:
paste your output

What did you intend to be?

The OpenCV lib files that I made in opencv_files are not for XP. You probably have to make them for XP yourself.

Let me try it. In the meantime, do you think I need these steps?
.\vcpkg install tesseract:x64-windows-static
.\vcpkg install tesseract:x86-windows-static
.\vcpkg integrate install
what are they for?

Tesseract is required for the opencv_text module in the opencv_contrib. If you don't use the opencv_text module, you can skip the vcpkg steps.

Thanks for your answers. I try to compile the OpenCV 3.4.4 and send me back this error:
Error	C2065	'DXGI_FORMAT_NV12': undeclared identifier	opencv_core	\opencv-3.4.4\modules\core\src\directx.cpp	172

I don't think recent OpenCV has taken XP into account. https://stackoverflow.com/a/59700899
You need to either try with a much older OpenCV version or confront the error yourself. (I don't know much about it.)
I don't consider XP for OpenCvSharp, so I think it's better to use older native OpenCV in C or C++ instead of OpenCvSharp (C#) if you really need to support XP.

Thanks. I was am going to use Nuget OpenCVSharp 3.2 which seems to be working for XP.


How to ensure reproducibility of results

In version torchsparse v2.1, do fixed seeds guarantee reproducible results?

Hi, we don't rely on the fixed seeds since all the benchmark data used in our paper are real-world data.


VStack doesn't add spacing if a component is a custom functional component

See example: https://codesandbox.io/s/frosty-http-1scdrm?file=/src/App.js
In the above example, there is no space after <Link /> in the rendered result.
But if the same content in Link is rendered as it is, the space is added.
I'm not sure if this is a bug or if this is the way its supposed to be.
import React from "react";
import { Text, View } from "react-native";
import { VStack } from "@react-native-material/core";

function Link() {
  return (
    <>
      <Text>Link</Text>
      <Text>Link</Text>
    </>
  );
}

function App() {
  return (
    <VStack spacing={25}>
      <View>
        <Text>Hello</Text>
      </View>
      <View>
        <Text>Hello</Text>
      </View>

      <Link />
      {/* uncommnent the following and comment the prev line */}

      {/* <Text>Link</Text>
      <Text>Link</Text> */}

      <View>
        <Text>Hello</Text>
      </View>
    </VStack>
  );
}

export default App;

Hi @Pika-Pool,
Thank you for reporting this problem, doesn't seem to be an issue, try to add shouldWrapChildren={true} to the stack and it suppose to do the trick.
I'll close this issue now, please feel free to reopen it if it doesn't work.


SW-4541 Feature flag + split code paths for user drawn detailed sites

added opt-in flag
added new site type selection modal based on new feature flag
added new routes and empty placeholder components

Looks good 👍

Thanks for the review. I made one minor change following up on a figma conversation.


Add more details about AAD Groups being expanded

When viewing a Team or project membership that contains an AAD Group, can you elaborate on if you can see which users are in the AAD group, how users in the AAD group are invited and invites managed, etc.?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 07738454-4b1a-eff5-6c16-69e963ab2663
Version Independent ID: a63f1dad-0378-5ce3-97e9-ec66afffb206
Content: Add users or groups to a team or project - Azure DevOps
Content Source: docs/organizations/security/add-users-team-project.md
Product: devops
Technology: devops-security
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@chcomley - HI Chrystal, can you answer this customer's request for information?

Hi @eschrader, Thanks for reaching out. If you want to see all of the members of the Azure AD groups, you can click on the Azure AD group contact card in the UI. I'm not sure what you mean by "how users in the Azure AD group are invited and invitees managed, etc...", but you might be looking for group rules. If that's the case, please check the following article out:  https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/assign-access-levels-by-group-membership?view=azure-devops&tabs=preview-page. Please let us know whether you have any further questions. Thank you!

Hi @eschrader, I'm closing this issue, but again, please @mention me if you need any more clarification. Thank you!

#sign-off


Admin user create

Create a Admin Usercreate page

[x] backend api need to build
[x] frontend form needs to make

done


Add gulshanpr

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Thanks @Panquesito7 and @aparna2071 for approving and merging my first commit on GitHub.

Thanks @Panquesito7 and @aparna2071 for approving and merging my first commit on GitHub.

Congratulations 👏🎉 on your first contribution, Gulshan 🥳
Best wishes for your open source journey ahead !!


Suspense tests randomly fail

Describe the bug
This happens for me about half the time:
 FAIL  web/test/suspense.spec.tsx
  ● Console

    console.error
      Error: Uncaught [Error: expect(received).toBe(expected) // Object.is equality

      Expected: true
      Received: false]
          at reportException (C:\Users\Otonashi\solid\node_modules\jsdom\lib\jsdom\living\helpers\runtime-script-errors.js:66:24)
          at Timeout.task [as _onTimeout] (C:\Users\Otonashi\solid\node_modules\jsdom\lib\jsdom\browser\Window.js:521:9)
          at listOnTimeout (node:internal/timers:557:17)
          at processTimers (node:internal/timers:500:7) JestAssertionError: expect(received).toBe(expected) // Object.is equality

      Expected: true
      Received: false
          at C:\Users\Otonashi\solid\packages\solid\web\test\suspense.spec.tsx:51:25
          at Timeout.task [as _onTimeout] (C:\Users\Otonashi\solid\node_modules\jsdom\lib\jsdom\browser\Window.js:516:19)
          at listOnTimeout (node:internal/timers:557:17)
          at processTimers (node:internal/timers:500:7) {
        matcherResult: {
          actual: false,
          expected: true,
          message: [Function (anonymous)],
          name: 'toBe',
          pass: false
        }
      }

      at VirtualConsole.<anonymous> (../../node_modules/jsdom/lib/jsdom/virtual-console.js:29:45)
      at reportException (../../node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:70:28)
      at Timeout.task [as _onTimeout] (../../node_modules/jsdom/lib/jsdom/browser/Window.js:521:9)

    console.error
      Error: Uncaught [Error: expect(received).toBe(expected) // Object.is equality

      Expected: "Hi, Jo.Hello Jo"
      Received: ""]
          at reportException (C:\Users\Otonashi\solid\node_modules\jsdom\lib\jsdom\living\helpers\runtime-script-errors.js:66:24)
          at Timeout.task [as _onTimeout] (C:\Users\Otonashi\solid\node_modules\jsdom\lib\jsdom\browser\Window.js:521:9)
          at listOnTimeout (node:internal/timers:557:17)
          at processTimers (node:internal/timers:500:7) JestAssertionError: expect(received).toBe(expected) // Object.is equality

      Expected: "Hi, Jo.Hello Jo"
      Received: ""
          at C:\Users\Otonashi\solid\packages\solid\web\test\suspense.spec.tsx:54:29
          at Timeout.task [as _onTimeout] (C:\Users\Otonashi\solid\node_modules\jsdom\lib\jsdom\browser\Window.js:516:19)
          at listOnTimeout (node:internal/timers:557:17)
          at processTimers (node:internal/timers:500:7) {
        matcherResult: {
          actual: '',
          expected: 'Hi, Jo.Hello Jo',
          message: [Function (anonymous)],
          name: 'toBe',
          pass: false
        }
      }

      at VirtualConsole.<anonymous> (../../node_modules/jsdom/lib/jsdom/virtual-console.js:29:45)
      at reportException (../../node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:70:28)
      at Timeout.task [as _onTimeout] (../../node_modules/jsdom/lib/jsdom/browser/Window.js:521:9)

  ● Testing Suspense › Toggle with refresh transition

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      49 |     setTimeout(() => {
      50 |       expect(div.innerHTML).toBe("Hi, .Hello ");
    > 51 |       expect(pending()).toBe(true);
         |                         ^
      52 |     });
      53 |     setTimeout(() => {
      54 |       expect(div.innerHTML).toBe("Hi, Jo.Hello Jo");

      at web/test/suspense.spec.tsx:51:25
      at Timeout.task [as _onTimeout] (../../node_modules/jsdom/lib/jsdom/browser/Window.js:516:19)

  ● SuspenseList › revealOrder forwards

    expect(received).toBe(expected) // Object.is equality

    Expected: "Hi, Jo.Hello Jo"
    Received: ""

      52 |     });
      53 |     setTimeout(() => {
    > 54 |       expect(div.innerHTML).toBe("Hi, Jo.Hello Jo");
         |                             ^
      55 |       expect(pending()).toBe(false);
      56 |       expect(finished).toBe(true);
      57 |       done();

      at web/test/suspense.spec.tsx:54:29
      at Timeout.task [as _onTimeout] (../../node_modules/jsdom/lib/jsdom/browser/Window.js:516:19)

Summary of all failing tests
 FAIL  web/test/suspense.spec.tsx
  ● Testing Suspense › Toggle with refresh transition

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      49 |     setTimeout(() => {
      50 |       expect(div.innerHTML).toBe("Hi, .Hello ");
    > 51 |       expect(pending()).toBe(true);
         |                         ^
      52 |     });
      53 |     setTimeout(() => {
      54 |       expect(div.innerHTML).toBe("Hi, Jo.Hello Jo");

      at web/test/suspense.spec.tsx:51:25
      at Timeout.task [as _onTimeout] (../../node_modules/jsdom/lib/jsdom/browser/Window.js:516:19)

  ● SuspenseList › revealOrder forwards

    expect(received).toBe(expected) // Object.is equality

    Expected: "Hi, Jo.Hello Jo"
    Received: ""

      52 |     });
      53 |     setTimeout(() => {
    > 54 |       expect(div.innerHTML).toBe("Hi, Jo.Hello Jo");
         |                             ^
      55 |       expect(pending()).toBe(false);
      56 |       expect(finished).toBe(true);
      57 |       done();

      at web/test/suspense.spec.tsx:54:29
      at Timeout.task [as _onTimeout] (../../node_modules/jsdom/lib/jsdom/browser/Window.js:516:19)

Test Suites: 1 failed, 20 passed, 21 total
Tests:       2 failed, 316 passed, 318 total
Snapshots:   0 total
Time:        6.602 s
Ran all test suites.

To Reproduce

Run npm test
Maybe the test fails?
Rerun npm test until the test doesn't fail

Expected behavior
The behaviour should be deterministic.
Additional context
Windows 10 Pro 21H1 Build 19043.1348
npm 8.1.1

Yeah.. we can't depend on the timer resolution I guess and probably varies on the machine. I'd be open to suggestions. I've been having these sort of issues trying to test a lot of the async stuff. I guess we need a setup where we can force the sequence. Almost like async generators. I'd be interested if anyone has experience here. Most of the time I'd just set sufficiently long timeouts but it's awkward when you have a sequence of several steps.

Why are you using "real" timers in the first place?


Running doctests inside a notebook

Environment

Elixir & Erlang/OTP versions (elixir --version): Elixir 1.13.4, OTP 24
Operating system: Windows 11
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc): Livebook desktop app
Livebook version (use git rev-parse HEAD if running with mix): 0.6.3
Browsers that reproduce this bug (the more the merrier): Microsoft Edge
Include what is logged in the browser console:
Include what is logged to the server console:

Current behavior
See the attached notebook. I often run tests inside my Livebook notebooks, and this works great!

Today, I tried running doctests but received an error that the documentation for the given module couldn't be retrieved.

Expected behavior
I am not sure whether this is a bug or a feature request. I was hoping this would just work, but I am not knowledgeable enough about how Livebook manages the cells and modules under the hood and also about how doctests work.
If this is a bug, then the expected behavior would be for this to just work as it would in a normal Mix project. If it is a feature request, then I'd love for this to be able to work. I am really enjoying using Livebook as an all-in-one development environment for certain types of projects where I don't necessarily want to carry around a Mix project with the notebook.
Thanks for Livebook and looking forward to learning any details here.
doctests-in-a-notebook.zip

This is already main and we run do tests automatically. There were also previous issues around this. :)

Apologies if this is already fixed, and thanks for the heads up. However, I did perform a search and there is only a single issue that doesn't mention anything about it being fixed. It was just closed.
So do I just need to update my Livebook version? Do you happen to know what version this was fixed in?
Also, does the Livebook desktop app installer fall behind the latest Livebook version? It only installs 0.6.3 while it seems the latest Livebook version is 0.7.

As mentioned, it is main. So not released yet. :) and the installer from the website installed 0.7.0 for me. How did you install it and how are you checking the version?

Played around with this some more. It appears there are two issues or questions:

The Windows installer for Livebook basically silently fails. I had downloaded it and ran it, assuming that it upgrades to the latest available, but it doesn't, although it completes with no issue. The only way I could get it to upgrade to the latest of v0.7.2 is:

Shut down Livebook
Manually uninstall using C:\Users\<username>\AppData\Local\livebook\LivebookUninstall.exe.
Manually delete anything remaining, as the uinstaller doesn't seem to always remove everything.
Run the latest Livebook installer.

This issue isn't fixed in v0.7.2. By saying this "is already main", do you mean that it's fixed in the main branch but not yet deployed via a version?

Ah, I see your comment now. Didn't see it before I sent mine. Thanks for clarifying it hasn't been released yet, as you answered my question in (2).
Also, you can see the above notes for the installer issues. I can separate those into another issue if I get around to it. I'm checking the version by Livebook telling me the version in the top-left of the home page or in the dashboard.

Yes, please open up a separate issue for the installer issues, with steps to reproduce.

No worries! I'm all set at this point! Thanks. 🙂
Knowing that this will come into a release at some point is good enough for me, as I can feel confident to write doctests in my notebooks and that I will be able to run them (automatically it seems) in the future. I can circle back on the Windows installer stuff once a newer version of Livebook gets released to see if the above steps are still required then.

@bmitc we haven't changed anything regarding Windows install, so I don't expect something will change by then. Also, none of us really have experience with Windows installers, so if you could send PRs it would be even "awesomer"!

When I tried the doctests inside a Livebook (from main), it worked. 🎉 🚀
But after I wanted to use the import: true option, it gave me this error:

When I put the same module and test combo into a plain new Elixir project, it worked.
Some more info:
Erlang/OTP 25 [erts-13.1.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]

Elixir 1.14.2 (compiled with Erlang/OTP 25

Livebook is installed from main (HEAD at 2c684dc)

This is because Livebook automatically runs the doctests for you, so you don't need to do anything. However, our automatic runs do not import modules, which causes it to fail.
We could add a cell option to disable automatically running doctests, but ideally you would not use imports and use the default running instead of using your own. Does that make sense?

Got it! Makes perfect sense. Writing small doctests without the module name is nicer (imo), but it's not a big deal to write also the module name. Thank you, José. 💜


fix: #2469 - additional small space before action buttons for KP

Impacted file:

knowledge_panel_action_card.dart: additional small space before action buttons

What

additional small space before action buttons for KP

Screenshot

after
before

Fixes bug(s)

Fixes: #2469

Codecov Report

Merging #2472 (c9577e4) into develop (2ea0da3) will decrease coverage by 1.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop   #2472      +/-   ##
==========================================
- Coverage     8.86%   7.49%   -1.37%
==========================================
  Files          161     205      +44
  Lines         6623    9818    +3195
==========================================
+ Hits           587     736     +149
- Misses        6036    9082    +3046

Impacted Files
Coverage Δ

...kages/smooth_app/lib/widgets/attribute_button.dart
0.00% <0.00%> (-92.00%)
:arrow_down:

...s/smooth_app/lib/data_models/user_preferences.dart
8.73% <0.00%> (-23.57%)
:arrow_down:

packages/smooth_app/lib/themes/smooth_theme.dart
60.00% <0.00%> (-22.98%)
:arrow_down:

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
15.29% <0.00%> (-18.92%)
:arrow_down:

...mooth_app/lib/data_models/product_preferences.dart
24.65% <0.00%> (-6.78%)
:arrow_down:

packages/smooth_app/lib/main.dart
14.40% <0.00%> (-3.49%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <0.00%> (-3.13%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/scan_example.dart
0.00% <0.00%> (-2.28%)
:arrow_down:

...p/lib/pages/onboarding/consent_analytics_page.dart
0.00% <0.00%> (-1.57%)
:arrow_down:

...smooth_app/lib/pages/product/new_product_page.dart
0.00% <0.00%> (-0.88%)
:arrow_down:

... and 214 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dfff8ea...c9577e4. Read the comment docs.


 Would you like to help remove Makefile in the same PR but another commit? I suppose we shound't maintain them both.

@PeterDaveHello i've removed Makefile and updated package.json to reflect the functionalities present in Makefile.

@rpidanny thank you!

Looks good to me, just a small point here, @rpidanny would you mind me to squash the commits into one(so that I can help edit the commit message on GitHub) or would you like to help us writing more precise commit message with some details? We'd like to follow the conventions in this post, FYI. Thanks for your contribution!

Thanks for the link @PeterDaveHello .
I have updated the commit messages but please feel free to squash the commits if necessary.
Will keep the convention in mind next time :)

@PeterDaveHello Yes it does. Updated the commit messages.
Thanks for the feedback :+1:

@rpidanny thank you.


⚠ ClamAV has degraded performance

In 93b5157, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 83 ms

Resolved: ClamAV performance has improved in 78b5365.


Synapse ML support for OpenAIChatCompletion Apache Spark Client

Is your feature request related to a problem? Please describe.
GPT-4 model only works with ChatCompletion API. When calling GPT-4 model using existing OpenAICompletion API, receiving following error "The completion operation does not work with the specified model, gpt-4. Please choose different model and try again."
Describe the solution you'd like
Feature ask for SynpaseML's support for OpenAIChatCompletion Apache Spark Client in order to use GPT-4 model.

Thank you for your interest! Please use latest master to access the
OpenAIChatCompletion API. We will cut a new minor version (0.11.1) with
these changes too.
SynapseML Build and Release Information
Maven Coordinates
com.microsoft.azure:synapseml_2.12:0.11.0-40-469445b7-SNAPSHOT
Maven Resolver
https://mmlspark.azureedge.net/maven
Documentation Pages:
Scala Documentation
https://mmlspark.blob.core.windows.net/docs/0.11.0-40-469445b7-SNAPSHOT/scala/index.html
Python Documentation
https://mmlspark.blob.core.windows.net/docs/0.11.0-40-469445b7-SNAPSHOT/pyspark/index.html
On Wed, Apr 12, 2023 at 4:40 AM github-actions[bot] <
@.***> wrote:

Hey @Fawziya https://github.com/Fawziya 👋!
Thank you so much for reporting the issue/feature request 🚨.
Someone from SynapseML Team will be looking to triage this issue soon.
We appreciate your patience.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/SynapseML/issues/1913#issuecomment-1504537379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRIKPNEYRQKI3XT3ILVIKLXAYPZXANCNFSM6AAAAAAW3DASQ4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Awesome! Will try offline.
Close the request as the request is already taken by the team.


Formatting not beeing applied

Describe the bug
I've installed the extension in my VSCode but the Laravel Pint is not beeing ran on project nor files, as the GIF below shows.
To Reproduce
Steps to reproduce the behavior:

Install the extension.
Go to Settings extension
Check the "Enable" option
Uncheck the "Fallback to Global Bin"
Select "Laravel" on "Preset" option
Check "Run In Laravel Sail" option
Go to a PHP file
Unformat a line (e.g Adding extra spaces before a line)
Press Ctrl + Shift + P
Select "Format document using Laravel Pint"

Expected behavior
Laravel Pint beeing executed through Laravel Sail and the file beeing properly formatted.
Screenshots

Environment:

Operating system: Fedora 36 - KDE Plasma
IDE / version: VSCode 1.77.3 - Electron/19.1.11 Safari/537.36
Extension version: 1.1.4
Extension's config:

{
     "laravel-pint.enable": true,
    "laravel-pint.runInLaravelSail": true,
    "laravel-pint.fallbackToGlobalBin": false,
    "laravel-pint.preset": "laravel",
}

Additional context
I've tested Laravel Pint through command line and it works as expected running vendor/bin/sail php vendor/bin/pint

UPDATE: Using Dev containers solves the problem.
However I'm still unable to run it outside the container.

Same problem here, works through command line but auto-format on save just doesn't no matter what I try, and despite the fact that the output says that the file has been formatted. I'm running my project in WSL.

Same here

If what @medialoungeml says is right this might get fixed by #51 (issue #50)

v1.1.6 published, will close this issue as it might get solved with this
Feel free to comment or reopen this if find something similar


Add mouse-halo extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Updated the extension icon and added in some preferences to allow the user to select the fill color and opacity along with the border color. Thanks!


Why infinity loop?

while (true) {
        try {
          layout = StaticLayoutHelper.make(
              mParams.text,
              0,
              mParams.text.length(),
              mParams.paint,
              width,
              mParams.alignment,
              mParams.spacingMult,
              mParams.spacingAdd,
              mParams.includePadding,
              mParams.ellipsize,
              width,
              numLines,
              mParams.textDirection);
        } catch (IndexOutOfBoundsException e) {
          // Workaround for https://code.google.com/p/android/issues/detail?id=35412
          if (!(mParams.text instanceof String)) {
            // remove all Spannables and re-try
            Log.e("TextLayoutBuilder", "Hit bug #35412, retrying with Spannables removed", e);
            mParams.text = mParams.text.toString();
            continue;
          } else {
            // If it still happens with all Spannables removed we'll bubble the exception up
            throw e;
          }
        }

        break;
      }

the infinite loop is a workaround for this bug, so that if the IndexOutOfBoundsException is thrown, we can remove the spans and try again. it's possible to re-write this with a method instead (and just re-call the method without the Spannables in the IndexOutOfBounds scenario, but that's not much better either.
is there any specific issue your'e running into with this? this should never actually infinite loop (due to the break when no exception is thrown, a single loop if an IndexOutOfBoundsException is thrown and we are in the spannable case, or an exception being bubbled up.

Ok, then better remove loop
 try {
          layout = makeStaticLayout(numLines, width);

        } catch (IndexOutOfBoundsException e) {
          // Workaround for https://code.google.com/p/android/issues/detail?id=35412
          if (!(mParams.text instanceof String)) {
            // remove all Spannables and re-try
            Log.e("TextLayoutBuilder", "Hit bug #35412, retrying with Spannables removed", e);
            mParams.text = mParams.text.toString();
            layout = makeStaticLayout(numLines, width);

          } else {
            // If it still happens with all Spannables removed we'll bubble the exception up
            throw e;
          }
        }

private StaticLayout makeStaticLayout(int numLines, int width) {
    return StaticLayoutHelper.make(
        mParams.text,
        0,
        mParams.text.length(),
        mParams.paint,
        width,
        mParams.alignment,
        mParams.spacingMult,
        mParams.spacingAdd,
        mParams.includePadding,
        mParams.ellipsize,
        width,
        numLines,
        mParams.textDirection);
  }

If you try the workaround for a bug on some Android API version, then better to check current API version, because current solution is not optimal.

Can you please send in a pull request? Closing this for now.


Tesseract hangs

Environment

Tesseract Version:

tesseract 5.2.0
leptonica-1.82.0
libgif 5.2.1 : libjpeg 8d (libjpeg-turbo 2.1.4) : libpng 1.6.37+apng : libtiff 4.4.0 : zlib 1.2.12 : libwebp 1.2.4
Found OpenMP 201811
Found libarchive 3.6.1 zlib/1.2.12 liblzma/5.2.5 bz2lib/1.0.8 liblz4/1.9.4 libzstd/1.5.2
Found libcurl/7.85.0 OpenSSL/1.1.1o zlib/1.2.12 libpsl/0.21.1 (+libidn2/2.3.3) libssh2/1.10.0 nghttp2/1.48.0

Platform:
FreeBSD hostname.com 13.1-RELEASE-p3 FreeBSD 13.1-RELEASE-p3 GENERIC amd64

Current Behavior:
Tesseract hangs without any result. Hanged process even can not be killed.
Commands like  tesseract anyimage.png stdout or  tesseract -l eng+rus anyimage.png stdout
Expected Behavior:
Tesseract works (produces result and exits)

Did you install the Tesseract which is provided by FreeBSD?
 Or build it from source and debug the hanging process?

Yes, Tesseract is from binary packages (pkg install tesseract-5.2.0_1)
It's not possible to attach debugger or dump process with kill -QUIT.
Related discussion https://forums.freebsd.org/threads/process-hangs-in-run-state-and-can-not-be-killed-or-debugged.87035/

Commands like tesseract anyimage.png stdout or tesseract -l eng+rus anyimage.png stdout

Does this hang happen with any image (as the name of the image indicates)?
Does this hang happen with this command:
Tesseract /path/to/myimage.png /path/to/output_filename_without_extension
?

You can also try to prepend this to the tesseract command:
OMP_THREAD_LIMIT=1

Another thing I just noticed.
According to your tesseract -v output, tesseract does not detect any SIMD instruction. not even SSE4.1. How old is your machine?  Did you somehow disabled SIMD?

That's indeed very strange because any amd64 platform should at least show support for SSE 4.1.

any amd64 platform should at least show support for SSE 4.1

First 64-bit CPU from AMD came out in 2003, a few years before SSE4.1 was introduced.
https://en.wikipedia.org/wiki/X86-64
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level#background_of_the_x86_64_microarchitecture_levels
https://www.phoronix.com/news/GCC-11-x86-64-Feature-Levels
https://www.phoronix.com/news/LLVM-12-Clang-12-Feature-Over

Following trace may give additional info:
https://forums.freebsd.org/attachments/log_tail-txt.15069/

The discussion in the FreeBSD forum indicates the issue is related to OpenMP.

OMP_THREAD_LIMIT=1
Didn't get any visible changes

It's not clear how you used this environment variable.
You need to do either of these:

OMP_THREAD_LIMIT=1 Tesseract in.png output_name

Or

export OMP_THREAD_LIMIT=1
 Tesseract in.png output_name

According to your tesseract -v output, tesseract does not detect any SIMD instruction. not even SSE4.1.

That's a bug in Tesseract (fixed in commit adbefa83160c42371e7a4b0cf16a16a3aff26b08) which also caused bad performance for recognition and training on FreeBSD.

Looks very strange but now tesseract started working.
This happened before any software or OS updates.
So I can only suppose there was update of provider's virtualization software or something like that


std.stdio.File not thread-safe

dlang-bugzilla (@CyberShadow) reported this on 2014-11-13T02:45:48Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=13727
CC List

2krnk
bugzilla (@WalterBright)
greensunny12
jack (@JackStouffer)
johnnymarler (@marler8997)
petar.p.kirov
schveiguy (@schveiguy)

Description
////////////// test.d //////////////
import std.array;
import std.parallelism;
import std.stdio;

void main()
{
    foreach (fn;
        ["test.d"]
        .replicate(1000)
        .parallel
    )
    {
        // synchronized
        { File f = File(fn, "rb"); }
    }
}
////////////////////////////////////

On Windows 32-bit, this program will either deadlock, or print a dozen exceptions such as:

std.exception.ErrnoException@std\stdio.d(640): Could not close file `test.d' (No error)

Uncommenting the "synchronized" line, or commenting the ".parallel" line fixes the problem.

Works fine on 64 bits (with MSVC runtime).

schveiguy (@schveiguy) commented on 2014-11-13T14:37:51Z
(In reply to Vladimir Panteleev from comment #3)
> (In reply to Steven Schveighoffer from comment #2)
> > I'm going to throw a shot in the dark out here, and say it's an issue with
> > DMC runtime. Which means it's really a problem with DMC, not DMD or phobos.
>
> I agree. However, we might be able to work around thread safety issues in
> the DMC runtime using global locks.

Oh god! More locks :)

I strongly believe we should fix the issue in DMC. Can we create a C++ program that will exhibit the same issue?

>
> > I'll note that the DMC runtime has a limit of 64 file descriptors, including
> > the standard handles.
>
> This shouldn't be relevant except when running the test program on systems
> with 64 or more processors/cores.

Oh, I didn't realize how the parallel foreach worked.

dlang-bugzilla (@CyberShadow) commented on 2014-11-13T14:17:57Z
(In reply to Steven Schveighoffer from comment #2)
> I'm going to throw a shot in the dark out here, and say it's an issue with
> DMC runtime. Which means it's really a problem with DMC, not DMD or phobos.

I agree. However, we might be able to work around thread safety issues in the DMC runtime using global locks.

> I'll note that the DMC runtime has a limit of 64 file descriptors, including
> the standard handles.

This shouldn't be relevant except when running the test program on systems with 64 or more processors/cores.

dlang-bugzilla (@CyberShadow) commented on 2014-11-13T03:08:23Z
Note that even though the above example has all threads reading from the same file, this doesn't matter, as the problem occurs even when accessing distinct files.

schveiguy (@schveiguy) commented on 2014-11-13T13:49:33Z
I'm going to throw a shot in the dark out here, and say it's an issue with DMC runtime. Which means it's really a problem with DMC, not DMD or phobos.

I'll note that the DMC runtime has a limit of 64 file descriptors, including the standard handles.

bugzilla (@WalterBright) commented on 2018-03-13T06:16:46Z
(In reply to Steven Schveighoffer from comment #12)
> This was pulled in May 2016, so I'm assuming dmd release has been
> updated with new snn.lib?

The test case passes, so yes.

> In any case, there are still threading issues. Not
> sure whether they are all related.

In order to keep this open, it needs specifics.

dlang-bugzilla (@CyberShadow) commented on 2014-11-14T01:18:51Z
> I strongly believe we should fix the issue in DMC.

BTW, I agree in principle, but I don't know how realistic this is, considering it's closed-source and I don't know how hard or quick it is to get a patch in.

dlang-bugzilla (@CyberShadow) commented on 2015-10-08T04:49:24Z
https://github.com/DigitalMars/dmc/pull/2 (access required)

schveiguy (@schveiguy) commented on 2014-11-14T02:07:53Z
(In reply to Vladimir Panteleev from comment #6)
> > I strongly believe we should fix the issue in DMC.
>
> BTW, I agree in principle, but I don't know how realistic this is,
> considering it's closed-source and I don't know how hard or quick it is to
> get a patch in.

It's on github, but private. Ask Walter for access.

I fixed an issue once with pipes that was holding up std.process, so I still have access.

I will warn you, though, you can't build it unless you have some obscure assembler :)

At the very least, your sample code should be filed as a DMC bug, but I'm not sure where that goes.

CC'ing Walter on this.

dlang-bugzilla (@CyberShadow) commented on 2014-11-14T01:17:14Z
(In reply to Steven Schveighoffer from comment #4)
> Oh god! More locks :)

Assuming we don't need to lock for the actual I/O operations (read/write), I think the impact for locking on some O(1)-ish operations shouldn't be too bad compared to the cost of the actual I/O.

> I strongly believe we should fix the issue in DMC. Can we create a C++
> program that will exhibit the same issue?

Yes:

///////////////////////////// test.c ////////////////////////////
#include <windows.h>
#include <stdio.h>

DWORD WINAPI ThreadProc(LPVOID lpParameter)
{
    for (int i=0; i<100; i++)
    {
        int res;
        FILE* f = fopen("test.c", "rb");
        if (!f) { printf("fopen failed\n"); return 1; }
        res = fclose(f);
        if (res) { printf("fclose failed\n"); return 1; }
    }
    return 0;
}

void main()
{
    for (int i=0; i<10; i++)
    {
        DWORD dwThreadId;
        CreateThread(NULL, 0, &ThreadProc, NULL, 0, &dwThreadId);
    }
}
/////////////////////////////////////////////////////////////////

bugzilla (@WalterBright) commented on 2018-03-12T09:40:39Z
(In reply to Vladimir Panteleev from comment #8)
> https://github.com/DigitalMars/dmc/pull/2 (access required)

This was pulled.

jack (@JackStouffer) commented on 2016-06-23T14:24:11Z
See also: https://issues.dlang.org/show_bug.cgi?id=15768

bugzilla (@WalterBright) commented on 2016-05-09T07:55:21Z
Adding test case:

https://github.com/dlang/dmd/pull/5747

schveiguy (@schveiguy) commented on 2018-03-12T11:54:02Z
(In reply to Walter Bright from comment #11)
> (In reply to Vladimir Panteleev from comment #8)
> > https://github.com/DigitalMars/dmc/pull/2 (access required)
>
> This was pulled.

issue 18483 is related and was still showing there are threading issues recently. This was pulled in May 2016, so I'm assuming dmd release has been updated with new snn.lib? In any case, there are still threading issues. Not sure whether they are all related.

See also: http://bugzilla.digitalmars.com/issues/show_bug.cgi?id=327

dlang-bot commented on 2021-01-23T07:27:14Z
@WalterBright updated dlang/dmd pull request #5747 "fix Issue 13727 - std.stdio.File not thread-safe" fixing this issue:

- fix Issue 13727 - std.stdio.File not thread-safe

https://github.com/dlang/dmd/pull/5747

dlang-bot commented on 2019-05-29T06:49:14Z
@marler8997 created dlang/dmd pull request #9911 "Workaround issue 13727 only for DigitalMars CRuntime" mentioning this issue:

- Workaround issue 13727 only for DigitalMars CRuntime

https://github.com/dlang/dmd/pull/9911

dlang-bot commented on 2019-05-28T09:50:31Z
dlang/dmd pull request #9907 "Workaround issue 13727 (std.stdio.File not thread-safe)" was merged into master:

- 9f7229407b56fef77dfcca50f2d3b41535fac34c by Jonathan Marler:
  Workaround issue 13727

https://github.com/dlang/dmd/pull/9907

johnnymarler (@marler8997) commented on 2019-05-28T08:28:53Z
The new `build.d` script in dmd is running into these issues.  I simplified where it's getting stuck into 3 versions with this code snippet:

import std.stdio, std.algorithm, std.array, std.process, std.exception, std.parallelism;
void main()
{
    auto funcs = [() {
        // std.exception.ErrnoException@std\stdio.d(997): Enforcement failed (No error)
        version (a)
            ["git", "--version"].execute;
        // std.exception.ErrnoException@std\stdio.d(563): Could not close file `HANDLE(C0)' (No error)
        else version (b)
            ["dir"].execute;
        // std.exception.ErrnoException@std\stdio.d(563): Could not close file `somefile' (Bad file descriptor)
        else version (c)
            "bar".toFile("anotherfile");
        else static assert(0, "Please specify -version=a, -version=b or -version=c");
    }, () {
        "foo".toFile("somefile");
    }];
    foreach (func; funcs.parallel(1))
        func();
}

dlang-bot commented on 2019-05-29T08:00:06Z
dlang/dmd pull request #9911 "Workaround issue 13727 only for DigitalMars CRuntime" was merged into master:

- 97c4d5e0b2719a29a1ce1c617d77fac3d9f86c73 by Jonathan Marler:
  Workaround issue 13727 only for DigitalMars CRuntime

https://github.com/dlang/dmd/pull/9911

dlang-bot commented on 2019-05-28T08:47:21Z
@marler8997 created dlang/dmd pull request #9907 "Workaround issue 13727 (std.stdio.File not thread-safe)" mentioning this issue:

- Workaround issue 13727

https://github.com/dlang/dmd/pull/9907

schveiguy (@schveiguy) commented on 2018-03-13T10:32:21Z
It seems to be passing more frequently, but still seems to have issues: https://auto-tester.puremagic.com/show-run.ghtml?projectid=1&runid=3072904&isPull=true

Logged output:
Test runnable/test13727.d failed.  The logged output:
..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable    -odtest_results\runnable -oftest_results\runnable\test13727_0.exe  runnable\test13727.d  -map nul.map

test_results\runnable\test13727_0.exe

..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -inline -odtest_results\runnable -oftest_results\runnable\test13727_1.exe  runnable\test13727.d  -map nul.map

test_results\runnable\test13727_1.exe

..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -release -odtest_results\runnable -oftest_results\runnable\test13727_2.exe  runnable\test13727.d  -map nul.map

test_results\runnable\test13727_2.exe

..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -inline -release -odtest_results\runnable -oftest_results\runnable\test13727_3.exe  runnable\test13727.d  -map nul.map

test_results\runnable\test13727_3.exe

..\generated\windows\release\32\dmd.exe -conf= -m32 -Irunnable   -g -odtest_results\runnable -oftest_results\runnable\test13727_4.exe  runnable\test13727.d  -map nul.map

test_results\runnable\test13727_4.exe

std.exception.ErrnoException@std\stdio.d(576): Could not close file `runnable/extra-files/extra13727.txt' (No error)

----------------

0x0040805C in @safe bool std.exception.errnoEnforce!(bool, "std\stdio.d", 576u).errnoEnforce(bool, lazy immutable(char)[])

0x00403BCB in @safe void std.stdio.File.detach()

0x004025CD in void std.parallelism.ParallelForeach!(immutable(char)[][]).ParallelForeach.opApply(scope int delegate(ref immutable(char)[])).doIt() at C:\cygwin\home\braddr\sandbox\at-client\pull-3072904-Win_32\dmd\test\..\..\phobos\std\parallelism.d-mixin-4007(4053)

0x0040CFB1 in void std.parallelism.run!(void delegate()).run(void delegate())

0x00404C24 in void std.parallelism.TaskPool.executeWorkLoop()

0x00431934 in __threadstartex

0x77124A77 in RtlGetAppContainerNamedObjectPath

0x77124A47 in RtlGetAppContainerNamedObjectPath

schveiguy (@schveiguy) commented on 2018-03-13T10:34:34Z
(In reply to Steven Schveighoffer from comment #14)
> It seems to be passing more frequently, but still seems to have issues:

I take it back, it seems this is the only time the Win32 test has run since you reopened. So seems not to be fixed.

greensunny12 commented on 2018-04-02T13:24:20Z
There's currently a Phobos PR by Jack that might fix this:

https://github.com/dlang/dmd/pull/5747


Possible to inject a call higher in the queue than a long-running insert?

DBFlow Version: 4.0.0-beta5
Issue Kind (Bug, Question, Feature): Question
Description:
I looked through the docs, and I couldn't find anything regarding priority of calls. I'm running a ProcessModelTransaction with over 27K items, and during the insertion process, I need to access a different table in the same database. Right now it's waiting until those 27K rows are added before it allows my other call to go through. I'm wondering if there is a way to "cut in line" and make the separate call have a higher priority than the insertion process so that I don't have to wait. Is that possible?

Its kind of buried. but [here](usage2/StoringData.md#priority-queue


Render tags in note title

This is an absolutely fantastic plugin. It would be a great addition to have tags render in note titles. (I use these to keep track of what project an event/task is related to and what type of event/task).
Thanks!

Good idea! Thanks for submitting :)


FastAPI receives headers by joining rather than duplicate(multiple) headers

First check

[x] I added a very descriptive title to this issue.
[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.
[x] I already read and followed all the tutorial in the docs and didn't find an answer.
[x] I already checked if it is not related to FastAPI but to Pydantic.
[x] I already checked if it is not related to FastAPI but to Swagger UI.
[x] I already checked if it is not related to FastAPI but to ReDoc.
[x] After submitting this, I commit to one of:

Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
Implement a Pull Request for a confirmed bug.

Example
Here's a self-contained, minimal, reproducible, example with my use case:

from typing import List, Optional

from fastapi import FastAPI, Header

app = FastAPI()

@app.get("/items/")
async def read_items(x_token: Optional[List[str]] = Header(None)):

    return {"X-Token values": x_token}

Description

What I did with HTTPie(and same as what Swagger did with curl):

$ http -v :8000/items/ X-Token:first,second
GET /items/ HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host: localhost:8000
User-Agent: HTTPie/2.3.0
X-Token: first,second

It returns a JSON with

{
    "X-Token values": [
        "first,second"
    ]
}

But I expected it to return:

{
    "X-Token values": [
        "first",
        "second"
    ]
}

Environment

OS: macOS 11.2.3
FastAPI Version: 0.63.0
Python version: 3.9.4

Additional context
From Header Parameters docs, it said FastAPI can receive multiple values for a single header. However, It's not working properly. Thus, I had to pop it and split it with ,.
It's not a big deal, but I think the official doc must have reliability. Frankly, I'm confused this is a bug or a feature...

You didn't send multiple headers like the doc example:
X-Token: foo
X-Token: bar

You sent one header with a comma in it.

@four43 Oops, What a shame...you are right. Thanks.

That's a weird HTTP spec thing. Like with Accept it has multiple values and weights in there but it's a single header. It's weird. Glad it's working better for you.

Thanks for the help here @four43 ! 👏  🙇
Thanks for reporting back and closing the issue @hard-coders  👍

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Authentication for uploading pictures

Hey team! Please add your planning poker estimate with ZenHub @CarlosQ96 @mohammadranjbarz

This is done, it calls the checkIfUserInRequest and if user exists. If we do make another endpoint for cherik I'll include it on the other issue and reuse the same auth.