text:
About mAP

According to the operation of read me file, the value of mAP is 47.8%, which is a little different from what the author said. Is this normal? Can I adjust the parameters to make it larger?

Hi,
Thanks for your question.
I have run the PASCAL VOC 2007 experiment on my own machine multiple times using the parameters provided in the repo. Due to the fixed random seed, all these times I got the same experimental results: mAP 49.2% and CorLoc 65.0%. I'll provide a trained model soon.
You can also feel free to change the parameters such as the random seed (__C.RNG_SEED).
By the way, what is the CorLoc number you got?

I can't find the discovery.pkl. That's weird.

Have you run the command python tools/test_net.py --cfg configs/baselines/vgg16_voc2007.yaml \   --load_ckpt Outputs/vgg16_voc2007/$MODEL_PATH \   --dataset voc2007trainval?

Yes.I find the detections.pkl and calculated the mAP(47.8%).
However,I can't find the discovery.pkl.

Are you sure that you set --dataset to voc2007trainval instead of voc2007test? If you set --dataset to voc2007trainval, there should be a discovery.pkl

You're right.Thank you very much!

I forgot to tell you the CorLoc number！
Mean CorLoc = 0.6397
Mean AP = 0.4780

Hi,
The model trained on PASCAL VOC 2007 is available on Baidu Yun (please use code bch4).

I have the same problem.
The two evaluation values are about 1.2% lower than the results of the paper.
I tried to change the random number.（__C.RNG_SEED.But it didn't work.
Do you have any suggestions for improving the results?

Hi, I'm not sure about the reason. In my experiments, I can always get the same 49.0% mAP.
Maybe you can download my trained model here. #5

authors: Mickeybaby ppengtang zwyyy215


text:
Error: error in tensorpack setup command: 'extras_require' requirements cannot include environment markers, in 'all': 'tornado; python_version < "3.0"'

I got the error message when tried to install tensorpack:
Collecting git+https://github.com/ppwwyyxx/tensorpack.git
Cloning https://github.com/ppwwyyxx/tensorpack.git to /tmp/pip-IxEFVq-build
Complete output from command python setup.py egg_info:
error in tensorpack setup command: 'extras_require' requirements cannot include environment markers, in 'all': 'tornado; python_version < "3.0"'
----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-IxEFVq-build/
please help!
PS: python: 2.7 with anaconda.
tensorflow: 1.2

You probably need to upgrade setuptools and pip.

Switched to another syntax following https://github.com/pypa/setuptools/issues/1087, so it works with older version of setuptools.

Solved by upgrading setuptools
Thank you!

source: gharchive/issue

repo: ppwwyyxx/tensorpack

license_type: permissive

license_source: github-api


text:
Verify command

Just scoped to pp for now due to YESTERDAY'S CHAOS.
Running at about 1m rows per minute. ~36 hours for a full process.

[x] Depends on https://github.com/ppy/osu-queue-score-statistics/pull/192 for conflict avoidance.

Is this ready for review, or is there a possibility of further changes still?

It's fine for now. The Watch command less so, but this one is holding up.

source: gharchive/pull-request

authors: bdach peppy

repo: ppy/osu-queue-score-statistics

license: MIT


text:
ADD:iOS demo

添加iOS 的demo。
因为没其他分支，所以这次的 PR是 提示你创建一个iOS分支。 你拒绝以后我重新PR。

这次 PR 先 close 掉？

是的，你先创建一个iOS的分支，然后我再提交。

分支已建：feature/log4i

authors: Coneboy-k pqpo


text:
Not listing all VMs

This is critical, as it is preventing me from bringing my mailserver up.
root@amethyst:~ # ls /iohyve/pbx.gewt.net/
device.map
root@amethyst:~ # ls /iohyve/mailer.gewt.net/
device.map
root@amethyst:~ # iohyve list
Guest         VMM?  Running  rcboot?  Description
pbx.gewt.net  NO    NO       NO       Sat Feb 27 16:51:07 CST 2016

Fixed with:

Fixed with: zfs set iohyve:name=

Was mailer.gewt.net created with iohyve create? Also, what version is this? iohhyve version

Yes - the VM was created with iohyve create, but it looks like it was done before a change in ZFS properties.

Does this continue to happen on your current version? (Hopefully at  0.7.6 ;) )

I haven't created any new VMs yet - I need to know how to use multiple bridges before that happens ;)

Can you please test? This would be a serious issue.
Just running iohyve create testvm 512M && iohyve getall testvm would suffice.

root@amethyst:~ # iohyve create testvm 512M && iohyve getall testvm
Creating testvm...
Getting testvm iohyve properties...
bargs          -A_-H_-P
boot           0
con            nmdm4
cpu            1
description    Wed Jul 13 20:37:03 CDT 2016
loader         bhyveload
name           testvm
os             default
persist        1
ram            256M
size           512M
tap            tap4
template       NO
vnc            NO
vnc_h          600
vnc_ip         127.0.0.1
vnc_tablet     NO
vnc_w          800
vnc_wait       NO
root@amethyst:~ # iohyve list
Guest              VMM?  Running  rcboot?  Description
cheshire.gewt.net  YES   YES      NO       Fri Jan 22 14:20:56 EST 2016
mailer.gewt.net    YES   YES      NO       Fri Jan 22 14:42:20 EST 2016
ns1.gewt.net       NO    NO       NO       Fri Jan 22 14:02:15 EST 2016
pbx.gewt.net       NO    NO       NO       Sat Feb 27 16:51:07 CST 2016
testvm             NO    NO       NO       Wed Jul 13 20:37:03 CDT 2016
Looks like it was "using very old version to create the VM" issue

Rad :sunglasses:
I'll close out the issue.

license_source: bigquery


text:
Live - Gestão de documentos no Mesa Virtual: aspectos legais e práticos (12/07 - 14h)

Informações da Transmissão Ao Vivo
Titulo: Gestão de documentos no Mesa Virtual: aspectos legais e práticos
Data e Hora: 12/07 - 14h as 17h
Solicitante: Fabiano Geremia
Realizador(es): Reitoria e Assessoria Especial de Governança e Integridade (ASEGI)
Palestrante Principal: Cinara Reis Flores - Servidora TAE
Solicitação no Mural: por enquanto via e-mail (fabiano.geremia@uffs.edu.br) / https://practice.uffs.edu.br/mural/servico/65
Link Transmissão: https://youtu.be/nj6P5zthfHA
Com os dados e roteiro em mãos, o responsável pela Live deve seguir os padrões do PRACTICE e estabelecer contato com o solicitante, enviando inicialmente o Protocolo de Execução de Lives.
Planilha de Lives
Protocolo de Execução de Lives
TeleCurso 2000
CC: @con-midia / lives

Criei as pastas dessa issue no Google Drive:

 Pasta da issue
🔽 Entrada
🔼 Saída

Entrei em contato via e-mail já que estamos com o mural fora do ar.
O formulário foi respondido e o link da transmissão criado no YouTube. Como não se deseja capa, coloquei uma provisória do PRACTICE. Não haverá divulgação da live.
Haverá interpretação em libras em uma sala já fornecida. E os documentos recebidos estão na pasta.

Live finalizada e planilha atualizada.

LUIZA DALL BOSCO TONIAL comentou o seguinte no mural:

Para fins de esclarecimento, como o Mural esteve fora do ar, o contato se deu via e-mail.
A transmissão foi realizada na tarde de hoje!
Então a demanda está sendo encerrada. Obrigada!

authors: PracticeUFFSBot luizatonial

repo: practice-uffs/programa


text:
Informar no mural que os serviços de cartilha e manual estão indisponíveis

Conforme a issue 74 do repositório website, é necessário adicionar no mural também a informação de que os serviços de gravação em estúdio estão indisponíveis devido a pandemia e que os serviços de cartilha e manual estão indisponíveis. Pode ser adicionado uma tarja nesses serviços ou um aviso em cor diferente.

Perfeito @alissonpeloso , ficou muito bom!

authors: CleissonVieira alessandrapedrotti

repo: practice-uffs/web-feedback


text:
[FEATURE] Restart button

There should be a restart test button while the user is attempting problems so that one can always restart if they need to or wish to. If there exists a restart button while problems are being attempted then it'll only be better. It is a basic feature and can be in function very well.

please assign it to me under GSSoC'23.

Hello @deveshidwivedi  it's good to see you want to contribute to the project.
I am unable to understand clearly, I want to know if the button will be reloading the page or do something else. Please describe more about the functionality of the button and why & how to implement it.
Also, I would highly recommend you first learn about Open Source, Git &GitHub, and the best practices to be followed while contributing. You can watch this video by Eddie on FreeCodeCamp to get a good idea of everything.
After learning about it well, you can actually contribute to the project and help make it better!
Happy Contributing!

Hey, @deveshidwivedi do you want to work on this issue?
I am temporarily closing this issue. If you want to work on this issue reopen it and start contributing.


text:
Add static database of questions and answers

Add questions and answers of multiple topic for the quiz.
Add this in json format.

The feature has been added.

repo: pranavsilimkhan/web-game


text:
Dijkstra's algorithm

Describe the project you want to add with tech stack
Dijkstra's algorithm is an algorithm for finding the shortest paths between nodes in a weighted graph.
Tech Stack : C
Expected behavior

A graph and source vertex are requirements for Dijkstra's Algorithm. This Algorithm is established on Greedy Approach and thus finds the locally optimal choice (local minima in this case) at each step of the Algorithm.

@pranjay-poddar @MohitGupta121 @TusharKesarwani please assign me this issue.

repo: pranjay-poddar/Dev-Geeks


text:
Adblock

Can you add ad blocking feature?

Can you provide some more details regarding that

Ads appear while watching video

addition

I can't completely remove the ads but i can skip them , if you have any method for completely removing them.
Please share it as it would be helpful

Reklamları tamamen kaldıramıyorum ancak reklamları tamamen kaldırmak için herhangi bir yönteminiz varsa atlayabilirim.
Faydalı olacağı için lütfen paylaşın

I'm not an expert on this subject

authors: prateek-chaubey senolfndk

repo: prateek-chaubey/YTPro


text:
[POC][WIP] Upload snapshots to GH after test

Don't mind me, just trying out a few Travis builds.

Visual diff testing failed for 25 images: https://gist.github.com/filoozom/c46a89f9960d092e4fe4febba22ae0d9/raw/data.zip

Visual diff testing failed for 25 images

repo: prateekbh/preact-material-components

license: mit


text:
🛑 ChatGPT + DALL-E is down

In 483959e, ChatGPT + DALL-E (https://streamlit-chatgpt-dalle2.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT + DALL-E is back up in af7a35a after 19 minutes.

repo: prateekralhan/status


text:
🛑 ChatGPT Beyond 2021 is down

In 54e5103, ChatGPT Beyond 2021 (https://chatgpt-beyond-2021.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT Beyond 2021 is back up in 524dfb2 after 4 minutes.


text:
(#1164) Add types to reddit/comment.py

#1164
-> ./praw/models/reddit/comment.py

Thanks!

authors: PokestarFan bboe

repo: praw-dev/praw


text:
08 July 2015 - Fix multi-scope methods; add leave_moderator

Changes

Add support for multiple-scope methods by using lists for has_scope check
Use above to fix add_wiki_ban and add_wiki_contributor
Add [modcontributors, modwiki] relationship scope for above
Add modcontributors relationship scope as seen in #451
Fix WikiPage.remove_editor raising an AssertionError when using OAuth
Add refresh key and tests for modwiki
Add refresh key and tests for modwiki+wikicontributors

Concerns

You'll notice that test_scope_modwiki shows me first loading the wikiread scope. This is required to perform subreddit.get_wiki_page, else it 403s. I would consider this a bug / shortcoming, because it means we're implicitly adding a scope dependency that isn't required by reddit. I'm not sure why modwiki doesn't allow you to load the page in the first place.

I'm debating whether I should add a leading underscore to leave_status. On one hand, the user shouldn't be calling it directly, they should use leave_moderator. On the other hand, this method has all of the docstring info, so I feel it shouldn't be privatized. I mean, privatizing doesn't stop them from reading it, it's just a formatting thing.

Notes

The leave_moderator method had to go through a few evolutions to get to where it is now. Many of the reddit forms accept {'r': 'reddit_api_test'}, but leavemoderator and leavecontributor insist on requiring the subreddit's fullname. I tried everything to add this method to either the relationships section or the _methods section, but in the end I had to make it separate.

Critique.

I would consider this a bug / shortcoming, because it means we're implicitly adding a scope dependency that isn't required by reddit. I'm not sure why modwiki doesn't allow you to load the page in the first place.

I don't think we're adding any dependencies. Getting pages simply requires a separate scope.
Overall this looks great! Thanks as always for the effort.

Can we make this private

Alright, no problem. Extra docstrings added.

I don't think we're adding any dependencies.

No, we certainly are. Here I am bypassing it:

Getting pages simply requires a different scope

This is true, but add_editor isn't supposed to get the page, it's supposed to add an editor -- no wikiread required for that. Personally I don't consider this the highest of priorities, but it's worth noting.

I see. So we need a lazy get_wiki_page method? Would that solve it?

Yes, r.get_wiki_page will need to call the WikiPage constructor instead of request_json. Do you remember if there's any particular reason you used request_json for that? I wonder what kind of parameters can be used for getting a wik page...
Secondly, wiki pages will need to pass this hasattr check without causing a lazyload and receiving 403. This check was implemented before Redditor had the fastname attribute, so _fast_name originally would have been an indicator that it was a Subreddit object. I'm assuming this should be replaced with an isinstance
As far as I can tell, that will be all it takes for add_editor to pass.

I'm very close to fixing the WikiPage scopes bug, but I've run into a problem.
I wanted to replace hasattr with isinstance(cls, Subreddit), but importing that creates a circular dependency (init -> decorators -> objects -> init.AuthenticatedReddit as AR).
The easy way out is to give WikiPage a _case_name so that it passes the hasattr, but that's pretty hackish. We could also make it so that this check is not performed when the requested scope is something like modwiki, which can never be applied to a Subreddit object, but I don't know if that'll open the door to outlining a bunch of "special cases" for each scope.
How would you solve this?

I think I tried the exact thing you did before and came up with the same error. To be honest the restrict_access decorator is very hacky, so a hacky solution on top of that isn't too bad.
What would probably be better is to rewrite it to not use a decorator, but instead do an access check at by calling some method at the beginning of the currently decorated methods. Alternatively when we move to OAuth only, we could dynamically only make the functions available when the set of credentials allow that method to be used.

Oh, it looks like this works:
    if hasattr(cls, 'reddit_session'):
        # Defer access until necessary for RedditContentObject.
        # This is because scoped sessions may not require this
        # attribute to exist, thus it might not be set.
        from praw.objects import Subreddit
        subreddit = cls if isinstance(cls, Subreddit) else False

I don't usually use imports in places like this, but it's probably better than abusing the casename. Do you have anything against it? Otherwise I'm keeping it.
I wouldn't mind replacing restrict_access with smaller, more specialized checks that can make better choices.

If that works, then let's go with it for now.

r.get_wiki_page now uses the object constructor
WikiPage is now Refreshable
Added missing wikiedit restriction to edit_wiki_page
restrict_access now uses isinstance instead of hasattr.
Removed the now-unecessary wikiread login from test_scope_modwiki
Fixed test_edit_wiki_page which relied on r.get_wiki_page in its older form.

I also discovered some very strange behavior in which reddit will 403 wiki pages through OAuth that you can access through Password Auth, even if you have all of the scopes enabled. As far as I can tell, this is not PRAW's fault.

I also discovered some very strange behavior in which reddit will 403 wiki pages through OAuth that you can access through Password Auth, even if you have all of the scopes enabled. This only happens when the subreddit has the wiki in "disabled" mode, which means only moderators can see it. As far as I can tell, this is not PRAW's fault.

Maybe you can file a bug with reddit on that one?

Any insight as to why removing this was necessary?

It points to add_editor with an inverse flag, similar to hide / unhide. If you stack a decorated method on top of another decorated method, you fail this check. All of the leave_moderator methods point to the single _leave_status which holds the decorator, for instance. This is another reason restrict_access will need a makeover when password auth leaves.

I don't know if there's any reason to support directly passing the fullname

The thought process there was that if you only pass in the subreddit name, then praw will have to perform a get_subreddit, and then fetch the fullname attribute. If the user knows the fullname they could skip that request.
Granted, the act of leaving moderator and contributor positions is probably infrequent enough that it's not very important to save those 2 seconds (1s when we go full oauth), but maybe somebody's time is really precious. It's nice to have it done in the minimum number of steps.
I don't really mind removing that if it's an eyesore. You could bypass it by creating the Subreddit object manually and forcing the fullname to whatever you want.

Added ModSelfMixin
Added leave_moderator and leave_contributor to Subreddit._methods
Changed _leave_status to accept the url parameter instead of status string parameter.
leave_moderator and leave_contributor within test_scope_modself now use the subreddit and fullname parameters so they each get tested.
Reinstated the subreddit.get_wiki_page line to ensure it's being tested.
Added more assertions to test_scope_modself to make sure the user is no longer a moderator.

Hey, can we add some way to make objects.Refreshable.refresh bypass the cache and hard refresh the object? That would make the tests a lot easier so I don't have to bypass the cache with letter casing and tricks. Just a boolean flag for hardreset would be great, but I'm not sure how I would implement it. I'm really bad at using r.evict.

Refresh should already do a hard reset. Can you point out where it's not working? Take a look at its tests. T

I'll make the changes to merge this, so I can then merge my PR in.

No, wait, I'm going to push in just a second.

Removed note from docstring that says it will return cached content
Applied uniq to Redditor, Subreddit, and WikiPage refresh methods
Removed cache bypasses thanks to new refresh method
Simplified _leave_status to not use the fullname
Now that fullname is gone, the test for leave_contributor will use the object version of the method to make sure that works too.
Removed default value from _leave_status, and no more type checking. Also removed the corresponding assertRaises from the test.
Fixed _leave_status docstring for statusurl.

Will wait :)

Okay, I've edited my previous comment with some more stuff that I did. Took the opportunity to fix a Multireddit property too.

Clarify which classes it didn't work on before

Alrighty.

Why are you so bad at cleaning up your docstrings?

That's what you meant to say, anyway.

Is it important that they were removed

I know the GitHub highlighter makes it look that way, but the attributes were simply moved above the superconstructor, not removed. It was causing a getattr recursion error in my new Author attribute fix because they hadn't been set.

Should these assertions be temporary?

Well, if we don't check those assertions and just let it fly, the user might be very confused when the author of their multireddit is listed as "user" or something silly. I thought that having the assertions would make it immediately clear that something is broken so they can report it to us and get it patched up.
What's your philosophy on that?

Why'd you switch these around?

This only happens if its the ONLY object I refresh during that session. AKA I think the unique_counter doesn't work if it's zero. On second thought, maybe I should have gone into __init__ and set the starting value to 1? I haven't noticed this behavior anywhere else.

Is it important that they were removed

I actually asked if it was important if they were moved. But you answered my question anyway. :+1:

That's what you meant to say, anyway.

No I would never say that. You're doing some amazing work and it's completely normal to overlook some things.
Regarding assertions: I think they're great for testing something that you're not sure of. Maybe we want to leave them in for a period of time to see if anyone complains about the code failing. This is great if we're not certain we're doing something correctly. A good example of that is in the processing of MoreComments, where in the past I've made assertions that I don't expect to see certain things, and eventually someone found such instances. However, if you're sure it works as-is currently, then I don't think they're necessary. It would be difficult to protect against upstream changes everywhere, and when it happens the bugs will surely come in.

This only happens if its the ONLY object I refresh during that session.

Interesting. In that case, I would suggest initializing the value to 1 so that the order isn't important in refresh. Also, with issues like this, it's generally good to write a test that reliably fails with a zero initial value (maybe you can do that in a separate PR so this one doesn't continue to grow). That way someone doesn't get the bright idea in the future to initialize it again to 0.

I'm going to merge since the tests are all passing. Any updates can be made in a new commits. :+1:

I was just kidding with the docstring comment, don't worry about it.
I guess I'll remove the asserts. They're not hurting anything by being there, but you're right that the code doesn't need to be littered with asserts for every little thing.
I changed the unique_counter init to 1, and it works the way I intended it to. That should have been included in the PR instead of the old way. If I make another push to this branch, can you re-merge it, or would I have to include this in a future PR?

I'd suggest making a separate PR for the init change along with a test that should fail with an init value set to 0. If you want to remove the assertions you can do that there as well.

authors: bboe voussoir


text:
Disable zooming on Y-Axis

Is there a way to only scale and transform X axis, without any changes to Y?

Solved with customTransform={(x, _, scale) => translateX(${x}px) scaleX(${scale})}, be aware order matters


text:
Update outdated labels info in API reference

Via this comment:

the text in the reference is outdated -- it refers to adding labels as part of `setConfig`, but that feature was moved to be part of `requestBids()`

this was done

authors: bretg rmloveland


text:
madvertiseBidAdapter: support for response meta.advertiserDomains (v5.0) #7053

merge prebid-server and prebid-js doc + link to madvertiseBidAdapter: support for response meta.advertiserDomains (v5.0) #7053

If you changed this parameter from 's' to 'zoneId' in 5.0, you might want to consider leaving 's' in the table but flagging it as in-scope only for 4.x.
Recall that PBJS 4.x will be patched for at least a month and pubs may use it for longer.

Done. Even if code continue to work with both s and zoneId


text:
DeepIntent Bid Adapter: update docs with bid floor support

🏷 Type of documentation

[ ] new bid adapter
[ ] update bid adapter
[x] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[ ] https://github.com/prebid/Prebid.js/pull/12266

Hi @muuki88 @lpagnypubstack @patmmccann
Could you please review this PR?

Please have a little patience as well. Prebid.js is heavily driven by a community of volunteers, which dedicate work and free time.
If you want things to go faster, join Prebid and help 😊💪 Pinging a reviewer is okay, but a bunch of people is a little too much 😉

Hi @muuki88,
I apologise for tagging multiple maintainers at the same time. My PR for bid floor support in the main prebid repo was merged last Wednesday, so I thought that the docs PR also needs to be merged ASAP. Since this was my first contribution to prebid and open source in general, I was not aware of the correct process.
I have added the floors_supported metadata change as requested. Please review once again and let me know if any more changes are required.
Thanks!

thanks for the update. released with PBJS 9.15, so merging


text:
Add option to override published packages

By default, if a package is already published it get untouched. Add an option to allow to override them with newly built ones.

@piranna Could you please clarify? By "package", do you mean GitHub release?

Don't remember the details, but yes, I thing it was about override the published release in GitHub repo so npm version gets untouched but a newer prebuild is fetch, for example for development purposses.

authors: piranna vweevers

repo: prebuild/prebuild


text:
Predix Components not working after updating to new version Google Chrome 80

*After updated Google Chrome browser from 79 to 80, Most of predix components stop working in live project and creating a multiple problems on production server.
*Chrome dropped support for HTML imports which are used by PX components. See my reply in this thread about the webcomponents polyfill version workaround.
*I have seen information on this topic that the Predix UI dev team is fixing bugs; please let me know the completion time or any workaround the method.
Thank you for your support.

@benjaminliugang  @joshsylvester  @sheela-svmx  @evanjd  @arongraham

repo: predixdesignsystem/px-dropdown


text:
Failed to download package / connection closed before message completed

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
Environment/reproduction
os: Linux RHEL7
pixi version: 0.14

using an internally hosted mirror
machine is under heavy load
empty package cache, environment not installed yet
run pixi install

pixi.toml:
[project]
[...]
channels = ["https://artifactory.eu02.arm.com/artifactory/api/conda/conda-forge"]
platforms = ["linux-64", "linux-aarch64"]

[dependencies]
sysroot_linux-64 = "~=2.17.0"
python = "~=3.8.0"
mypy = "~=0.910.0"
flake8 = "~=4.0.0"
pylint = "~=2.14.0"
prettytable = "~=0.7.0"
ipython = "~=7.14.0"
pandas = "~=1.4.0"
requests = "~=2.26.0"
gcc = "~=11.3.0"
gxx = "~=11.3.0"
zlib = "~=1.2.0"
sqlite = "~=3.35.0"
scons = "~=4.6.0"

[system-requirements]
linux = "3.10.0"

Issue description
Hello,
Thanks for developping pixi, I think it is quite nice in my personal opinion, and I would like to use it at work on the project I'm working on.
That being said, I am encountering some error when downloading packages.
The error looks like this:
  × failed to download package https://artifactory.eu02.arm.com/artifactory/api/conda/conda-forge/noarch/typing_extensions-4.9.0-pyha770c72_0.conda
  ├─▶ Request error: error sending request for url (https://artifactory.eu02.arm.com/artifactory/api/conda/conda-forge/noarch/typing_extensions-4.9.0-pyha770c72_0.conda): connection closed
  │   before message completed
  ├─▶ error sending request for url (https://artifactory.eu02.arm.com/artifactory/api/conda/conda-forge/noarch/typing_extensions-4.9.0-pyha770c72_0.conda): connection closed before message
  │   completed
  ╰─▶ connection closed before message completed

I ran this a few times, it does not always fail on the same package.
As you can see, I am using a JFrog/artifactory mirror (set up as channel in pixi.toml).
I can't find if this is a client side issue or a server side issue. From my perspective, it seems like it could be either some abnormal connection termination and/or maybe an oversight in error handling.
The error occurs approximately a couple of minutes after downloading/installation starts, when it runs on a loaded machine. I have had more success when running on a less loaded machine.
Here are some logs I gathered by setting 'RUST_LOG=hyper::proto::h1::conn=debug,hyper::client=debug':
DEBUG hyper::client::pool: pooling idle connection for ("https", artifactory.eu02.arm.com)
DEBUG hyper::client::pool: reuse idle connection for ("https", artifactory.eu02.arm.com)
DEBUG hyper::client::pool: reuse idle connection for ("https", artifactory.eu02.arm.com)
DEBUG hyper::client::pool: reuse idle connection for ("https", artifactory.eu02.arm.com)
DEBUG hyper::client::pool: reuse idle connection for ("https", artifactory.eu02.arm.com)
DEBUG hyper::client::connect::dns: resolving host="artifactory.eu02.arm.com"
DEBUG hyper::client::connect::dns: resolving host="artifactory.eu02.arm.com"
DEBUG hyper::client::connect::dns: resolving host="artifactory.eu02.arm.com"
DEBUG hyper::proto::h1::conn: incoming body is content-length (50124 bytes)
DEBUG hyper::proto::h1::conn: incoming body is content-length (53242 bytes)
DEBUG hyper::proto::h1::conn: parse error (connection closed before message completed) with 0 bytes
DEBUG hyper::proto::h1::conn: error shutting down IO: Broken pipe (os error 32)
DEBUG hyper::client::client: client connection error: error shutting down connection: Broken pipe (os error 32)
DEBUG hyper::proto::h1::conn: parse error (connection closed before message completed) with 0 bytes
DEBUG hyper::proto::h1::conn: error shutting down IO: Broken pipe (os error 32)
DEBUG hyper::client::client: client connection error: error shutting down connection: Broken pipe (os error 32)
DEBUG hyper::client::connect::http: connecting to [...]:443
DEBUG hyper::client::connect::dns: resolving host="artifactory.eu02.arm.com"
DEBUG hyper::client::connect::http: connecting to [...]:443
  × failed to download package https://artifactory.eu02.arm.com/artifactory/api/conda/conda-forge/noarch/typing_extensions-4.9.0-pyha770c72_0.conda
  ├─▶ Request error: error sending request for url (https://artifactory.eu02.arm.com/artifactory/api/conda/conda-forge/noarch/typing_extensions-4.9.0-pyha770c72_0.conda): connection closed
  │   before message completed
  ├─▶ error sending request for url (https://artifactory.eu02.arm.com/artifactory/api/conda/conda-forge/noarch/typing_extensions-4.9.0-pyha770c72_0.conda): connection closed before message
  │   completed
  ╰─▶ connection closed before message completed

Expected behavior
Expected behavior is to handle the error more gracefully and continue the download/installation if possible.

I encountered the same issue, the first download attempt would fail, but the second would succeed.

I did a bit more testing. I tried to download packages from the same server with curl, and then extract them with tar/unzip: it is pretty fast, and nothing bad happens. So now I would lean towards an issue in pixi/rattler...

Thats weird. I have seen this as well but I haven't been able to figure out why you get:
DEBUG hyper::proto::h1::conn: parse error (connection closed before message completed) with 0 bytes
DEBUG hyper::proto::h1::conn: error shutting down IO: Broken pipe (os error 32)
DEBUG hyper::client::client: client connection error: error shutting down connection: Broken pipe (os error 32)

I tried to sample a call stack at random during download/install, with the pstack tool, on a recompiled debug build, and got this
Thread 9 (Thread 0x2adc0daf4700 (LWP 18931)):
#0  0x00002adc0bfe3d47 in flock () from /lib64/libc.so.6
#1  0x0000557b03a077d3 in fslock::unix::lock::h7a6e969c7a5dd50c (fd=13) at src/unix.rs:322
#2  0x0000557b03a07f80 in fslock::LockFile::lock::ha7b3f0a00b46253b (self=0x2adc0dae3ef0) at src/lib.rs:167
#3  0x0000557b03a0802a in fslock::LockFile::lock_with_pid::hc0667a16a00d9df6 (self=0x2adc0dae3ef0) at src/lib.rs:208
#4  0x0000557b0353af18 in rattler_networking::authentication_storage::backends::file::FileStorage::lock::heb4a62236029d1cf (self=0x557b07403700) at src/authentication_storage/backends/file.rs:55
#5  0x0000557b0353cfc2 in _$LT$rattler_networking..authentication_storage..backends..file..FileStorage$u20$as$u20$rattler_networking..authentication_storage..StorageBackend$GT$::get::hab54fcc510bbb6a5 (self=0x557b07403700, host=...) at src/authentication_storage/backends/file.rs:102
#6  0x0000557b03534865 in rattler_networking::authentication_storage::storage::AuthenticationStorage::get::h004c48059d2c2053 (self=0x557b075d5b20, host=...) at src/authentication_storage/storage.rs:88
#7  0x0000557b03535dd4 in rattler_networking::authentication_storage::storage::AuthenticationStorage::get_by_url::h2bd86cb3a1935aab (self=0x557b075d5b20, url=...) at src/authentication_storage/storage.rs:136
#8  0x0000557b03526e08 in _$LT$rattler_networking..authentication_middleware..AuthenticationMiddleware$u20$as$u20$reqwest_middleware..middleware..Middleware$GT$::handle::_$u7b$$u7b$closure$u7d$$u7d$::h1923ea75e8e75464 () at src/authentication_middleware.rs:29
#9  0x0000557b03a0bd2e in _$LT$core..pin..Pin$LT$P$GT$$u20$as$u20$core..future..future..Future$GT$::poll::h5865df82401df94a (self=..., cx=0x2adc0daf21a0) at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/future/future.rs:125
#10 0x0000557b03a0bd2e in _$LT$core..pin..Pin$LT$P$GT$$u20$as$u20$core..future..future..Future$GT$::poll::h5865df82401df94a (self=..., cx=0x2adc0daf21a0) at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/future/future.rs:125
#11 0x0000557b02923822 in reqwest_middleware::client::ClientWithMiddleware::execute_with_extensions::_$u7b$$u7b$closure$u7d$$u7d$::h95b8bea2d2aa0552 () at /home/wilalh01/.cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-middleware-0.2.4/src/client.rs:160
#12 0x0000557b02923360 in reqwest_middleware::client::RequestBuilder::send::_$u7b$$u7b$closure$u7d$$u7d$::hf89aaa89b10acd4f () at /home/wilalh01/.cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-middleware-0.2.4/src/client.rs:314
#13 0x0000557b01fb7018 in rattler_package_streaming::reqwest::tokio::get_reader::_$u7b$$u7b$closure$u7d$$u7d$::hb5c5c819077f717f () at /home/wilalh01/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rattler_package_streaming-0.18.0/src/reqwest/tokio.rs:35
#14 0x0000557b01fb769a in rattler_package_streaming::reqwest::tokio::extract_conda::_$u7b$$u7b$closure$u7d$$u7d$::ha861a16ffa2bc992 () at /home/wilalh01/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rattler_package_streaming-0.18.0/src/reqwest/tokio.rs:100
#15 0x0000557b01fb894c in rattler_package_streaming::reqwest::tokio::extract::_$u7b$$u7b$closure$u7d$$u7d$::h24e32e6b0fcf6afe () at /home/wilalh01/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rattler_package_streaming-0.18.0/src/reqwest/tokio.rs:132
#16 0x0000557b021a2e9f in rattler::package_cache::PackageCache::get_or_fetch_from_url_with_retry::_$u7b$$u7b$closure$u7d$$u7d$::_$u7b$$u7b$closure$u7d$$u7d$::_$u7b$$u7b$closure$u7d$$u7d$::hce10fa620d924b68 () at /home/wilalh01/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rattler-0.18.0/src/package_cache.rs:213
[...]

There might be some sort of locking issue

I checked with strace and it seems to confirm my suspicion:
44609 flock(12, LOCK_EX <unfinished ...>
44608 flock(13, LOCK_EX <unfinished ...>
44607 flock(15, LOCK_EX <unfinished ...>
44614 flock(16, LOCK_EX <unfinished ...>
44613 flock(17, LOCK_EX <unfinished ...>
44612 flock(14, LOCK_EX <unfinished ...>
44610 flock(18, LOCK_EX|LOCK_NB)        = -1 EAGAIN (Resource temporarily unavailable) <0.000422>
44610 flock(18, LOCK_EX <unfinished ...>
44611 <... flock resumed> )             = 0 <6.045419>
44611 flock(19, LOCK_UN)                = 0 <0.000261>
44609 <... flock resumed> )             = 0 <6.044859>
44609 flock(12, LOCK_UN <unfinished ...>
44611 flock(19, LOCK_EX|LOCK_NB <unfinished ...>
44609 <... flock resumed> )             = 0 <0.000421>
44611 <... flock resumed> )             = -1 EAGAIN (Resource temporarily unavailable) <0.000267>
44611 flock(19, LOCK_EX <unfinished ...>
44609 flock(12, LOCK_EX|LOCK_NB)        = -1 EAGAIN (Resource temporarily unavailable) <0.000278>
44609 flock(12, LOCK_EX <unfinished ...>
44618 +++ exited with 0 +++
44608 <... flock resumed> )             = 0 <12.140519>
44608 flock(13, LOCK_UN)                = 0 <0.000296>
44608 flock(13, LOCK_EX|LOCK_NB)        = -1 EAGAIN (Resource temporarily unavailable) <0.000275>
44608 flock(13, LOCK_EX <unfinished ...>
44607 <... flock resumed> )             = 0 <15.201206>
44607 flock(15, LOCK_UN)                = 0 <0.000319>
44607 flock(15, LOCK_EX|LOCK_NB)        = -1 EAGAIN (Resource temporarily unavailable) <0.000258>
44607 flock(15, LOCK_EX <unfinished ...>
44614 <... flock resumed> )             = 0 <18.213597>
44614 flock(16, LOCK_UN)                = 0 <0.000410>
44613 <... flock resumed> )             = 0 <18.215742>
44613 flock(17, LOCK_UN)                = 0 <0.000271>
44612 <... flock resumed> )             = 0 <18.217978>
44614 flock(16, LOCK_EX|LOCK_NB)        = -1 EAGAIN (Resource temporarily unavailable) <0.000044>
44614 flock(16, LOCK_EX <unfinished ...>
44612 flock(14, LOCK_UN <unfinished ...>
44613 flock(17, LOCK_EX|LOCK_NB <unfinished ...>
44612 <... flock resumed> )             = 0 <0.000388>
44613 <... flock resumed> )             = -1 EAGAIN (Resource temporarily unavailable) <0.000250>
44613 flock(17, LOCK_EX <unfinished ...>
44612 flock(14, LOCK_EX|LOCK_NB)        = -1 EAGAIN (Resource temporarily unavailable) <0.000196>
44612 flock(14, LOCK_EX <unfinished ...>
44610 <... flock resumed> )             = 0 <30.000863>

Some of the flock syscalls take seconds to finish.
Actually, it might be an issue with my environment. My home directory (where pixi/rattler stores/locks credentials.json) is mounted on NFS, and in my environment, NFS can often be under heavy load, and this would not be the first NFS related issue I have seen.
Is there a way to use another location for  credentials.json? I would like to see what happens when it is on regular local storage, maybe it would solve my issues...

to make the path configurable (unless it is already and I missed it)

I just saw #994 is already implementing that part :)

Hi @william-alhant, thanks for debugging this!
I think we should solve this by reading the entire authentication file once and then just keeping it in cache. Thanks for debugging this!

@william-alhant I've implemented a cache here: https://github.com/mamba-org/rattler/pull/573
I hope that that would help with the issues you were seeing. We should only try to read the file once in the future, and lock it also only once. File locks are very slow over NFS.

Since both suggestions have been implemented Im closing this for now.
Feel free to reopen if the issue persists.

authors: baszalmstra william-alhant wolfv zen-xu

repo: prefix-dev/pixi


text:
fix: align CI with rattler

Aligns the CI with the latest in rattler. See https://github.com/mamba-org/rattler/pull/274
#233 disabled the cache because of a build issue with aarch64. This PR reenables that again.

@ruben-arts Lets test the binaries tomorrow! :)


text:
CSS missing from cache even though present in build-time files

We render out styled-component styles are "build-time" and they get embedded into the html pages in style tags, not as external files.
We can see these styles in the built html that we are pushing up to S3+Cloudfront for hosting.
 .tIcQ {
        background: #000;
        position: absolute;
        z-index: 1615;
        left: 0px;
      } /*!sc*/
      data-styled.g256[id='QuickSearch__StyledButton-sc-1r5r0ix-6'] {
        content: 'tIcQ,';
      } /*!sc*/
      .famVaa {
        fill: #ffffff;
      } /*!sc*/

Then when we go and look at what prerender.io has cached it appears as all "those" styles have been removed. Its important to note that the only styles removed seem to be the "styled-component" ones. While other embedded styles are still there?
All I can think of is that maybe styled components JS is "re-hydrating" the page (removing the styles before trying to add them again) and maybe prerender is coming in and caching the page before styled-components js can re-hydrate.
This would seem super inefficient if indeed this is what SC is doing.... but I'm not sure what else it could be???

@iDVB I have covered this issue and solutions in my PR for a different related project linked below. Hope this helps you.
https://github.com/GoogleChrome/rendertron/pull/643

@iDVB there is a workaround to this issue. You need to disable speedy so styles will be stored in DOM. https://stackoverflow.com/questions/53486470/react-styled-components-stripped-out-from-production-build

authors: gravi2 iDVB marcinczeczko

repo: prerender/prerender


text:
🛑 ramp is down

In 2f7a8a6, ramp (https://ramp.network/buy/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ramp is back up in dc78b8a.

repo: preschian/kodadot-status


text:
Just updated. Every tab I close shrinks the file explorer to the default width

Self-Diagnosis

[x] I have searched the issues for an answer to my question.
[x] I have reviewed the NERDTree documentation. :h NERDTree
[x] I have reviewed the Wiki.
[x] I have searched the web for an answer to my question.

State Your Question
Probably a setting... I'm used to shift + A expanding the file explorer and not thinking about it again. Now, any opened tab causes the file explorer to shrink in width to the default.
I didn't go through them all, anything passed tag 5.0.0 seems to exhibit the issue.

@towens, you left a lot of context out of your question, so I have to guess how this can be reproduced. Since you mentioned tabs, I assume that you are opening NERDTree, using t to open the selected file in a new tab, and then opening NERDTree again in the new tab. If that assumption is incorrect, please add some more detail to the issue.
Here is what I know/discovered:

The NERDTree buffer's width is remembered each time it closes, so that it can be set to that width when it's opened again. So if you open a file in the same tab, with the o key, the next time NERDTree is opened, it will still be expanded.
Opening NERDTree with the :NERDTree command in a new tab will create a new NERDTree buffer. Since it's new, it will open in the narrow state.
You can use the :NERDTreeMirror command to open the same NERDTree you had in the first tab. This should work, and open it in the expanded state, but there is a bug that I discovered. NERDTree knows the window is supposed to be expanded, but it is being rendered as a narrow window. Pressing A once does nothing, because that is supposed to shrink the window (which is already shrunk). Pressing A the second time expands it.

I will address the bug in the third bullet. If you have another scenario, please describe it in detail in the issue.

@PhilRunninger, thanks for bringing up context. I will only have one instance of NERDTree open per tmux session, and you are correct, I open all files by pressing the t key. It's possible my .vimrc is no longer compatible with the latest release. The relevant settings.
" NERDTree
let NERDTreeShowHidden=1
let NERDTreeNaturalSort = 1
set switchbuf=useopen,usetab

" open NERDTree unless you specify a file name
autocmd StdinReadPre * let s:std_in=1
autocmd VimEnter * if argc() == 0 && !exists("s:std_in") | NERDTree | endif

Your settings are OK, although switchbuf has no effect on what NERDTree does. That setting controls how Quickfix commands work, and NERDTree doesn't use any of those commands.
You also need to add let NERDTreeQuitOnOpen = 1 in order to see the issue I referred to.  If set to 0 (the default), NERDTree will unzoom when opening a file so more room is given to the file that was just opened. But when set to 1, NERDTree closes after opening a file, and it remains zoomed the next time it's opened.
To make mirroring the NERDTree in a new tab easier, you can use a mapping like the one below. It will automatically mirror the NERDTree before opening it.
nnoremap <silent> <C-N> :NERDTreeMirror<CR>:NERDTreeFocus<CR>

Checkout branch i1176 and see if it solves your issue. That branch fixes the :NERDTreeMirror command so that it displays an already-zoomed NERDTree correctly.

authors: PhilRunninger towens

repo: preservim/nerdtree

license: WTFPL


text:
Flaky test TestRedisDistributed correlated queries

Error:  Failures:
Error:    TestRedisDistributed>AbstractTestQueries.testCorrelatedInPredicateSubqueries:1403->AbstractTestQueryFramework.assertQuery:159 Execution of 'actual' query failed: SELECT t1.a, t1.b,   t1.b in (SELECT t2.b     FROM (values (2, 3), (2, 4), (3, 0), (30,NULL)) t2(a, b)     WHERE t1.a - 5 <= t2.a and t2.a <= t1.a and 0 <= t2.a) from (values (1,1), (2,4), (3,5), (4,NULL), (30,2), (40,NULL) ) t1(a, b) order by t1.a
Error:    TestRedisDistributed>AbstractTestQueries.testCorrelatedJoin:1791->AbstractTestQueryFramework.assertQuery:159 Execution of 'actual' query failed: SELECT n FROM (SELECT 1 FROM (VALUES 1) WHERE rand() = 5) t(a) RIGHT JOIN LATERAL (SELECT name FROM region) r(n) ON true
Error:    TestRedisDistributedHash>AbstractTestQueries.testCorrelatedInPredicateSubqueries:1403->AbstractTestQueryFramework.assertQuery:159 Execution of 'actual' query failed: SELECT t1.a, t1.b,   t1.b in (SELECT t2.b     FROM (values (2, 3), (2, 4), (3, 0), (30,NULL)) t2(a, b)     WHERE t1.a - 5 <= t2.a and t2.a <= t1.a and 0 <= t2.a) from (values (1,1), (2,4), (3,5), (4,NULL), (30,2), (40,NULL) ) t1(a, b) order by t1.a
Error:    TestRedisDistributedHash>AbstractTestQueries.testCorrelatedJoin:1791->AbstractTestQueryFramework.assertQuery:159 Execution of 'actual' query failed: SELECT n FROM (SELECT 1 FROM (VALUES 1) WHERE rand() = 5) t(a) RIGHT JOIN LATERAL (SELECT name FROM region) r(n) ON true

https://github.com/prestosql/presto/runs/1466334338

Duplicate of https://github.com/prestosql/presto/issues/5758 ?

@findepi Probably. Let me close this one. I will reopen if needed.

authors: ebyhr findepi

repo: prestosql/presto


text:
Add test for SELECT Hive viewfs table

Related to https://github.com/prestosql/presto/issues/1305

@ebyhr
Travis:
2019-10-22 16:26:11 INFO: FAILURE     /    io.prestosql.tests.hive.TestViewfsHiveTable.testSelectViewfsTable (Groups: viewfs) took 1.3 seconds
2019-10-22 16:26:11 SEVERE: Failure cause:
io.prestosql.tempto.query.QueryExecutionException: java.sql.SQLException: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got exception: java.io.IOException ViewFs: Cannot initialize: Empty Mount table in config for viewfs://hadoop-viewfs/)
	at io.prestosql.tempto.query.JdbcQueryExecutor.execute(JdbcQueryExecutor.java:115)
	at io.prestosql.tempto.query.JdbcQueryExecutor.executeQuery(JdbcQueryExecutor.java:83)
	at io.prestosql.tests.hive.TestViewfsHiveTable.testSelectViewfsTable(TestViewfsHiveTable.java:58)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:645)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:851)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1177)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLException: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got exception: java.io.IOException ViewFs: Cannot initialize: Empty Mount table in config for viewfs://hadoop-viewfs/)
	at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:275)
	at io.prestosql.tempto.query.JdbcQueryExecutor.executeQueryNoParams(JdbcQueryExecutor.java:123)
	at io.prestosql.tempto.query.JdbcQueryExecutor.execute(JdbcQueryExecutor.java:108)
	... 15 more

@findepi Thanks for the confirmation. Excluded viewfs test from product-tests-suite-1.sh.

please rebase to rerun the CI

@findepi Thanks for your review. Rebased.


text:
feat(remove-legacy-icons): resolves #240

Remove legacy icon props and legacy icons

Codecov Report

Merging #256 into next will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff         @@
##           next   #256   +/-   ##
===================================
  Coverage   100%   100%
===================================
  Files        36     36
  Lines       423    417    -6
===================================
- Hits        423    417    -6

Impacted Files
Coverage Δ

src/Select.js
100% <ø> (ø)
:arrow_up:

src/Icon.js
100% <100%> (ø)
:arrow_up:

src/CloseButton.js
100% <100%> (ø)
:arrow_up:

src/Hug.js
100% <100%> (ø)
:arrow_up:

src/IconButton.js
100% <100%> (ø)
:arrow_up:

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 b4ea865...88906fa. Read the comment docs.

Fixes #240

@jxnblk @jes708 there are teams that are still relying on these icons. This PR shouldn't get merged until we kinda verify they've moved over to the new icons

@msafari I think more along the idea that teams shouldn't use version 2.0.0 until they have verified that they are not missing any icons, and replace them if they are missing.

authors: codecov-io jes708 jxnblk msafari

repo: pricelinelabs/design-system


text:
Post-MVP: Set-up embedded data so information is passed  between qualtrics/platform

Currently, we don't connect qualtrics survey to the student.
The easiest way to do so is to pass some identifier (user_id) to qualtrics in the iframe URL. Then, we can do a merge on user_id in post.

Addressed in #105

repo: prijatelilab/PrijateliTree


text:
Implement focus trap behavior and hook

This PR adds a "focus trap" behavior. For more details on its behavior and API, please see the rendered documentation.
Screenshots
Screenshot from storybook story:

Merge checklist

[x] Added/updated tests
[x] Added/updated documentation
[x] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

re: https://github.com/primer/components/pull/1114/files#r590876019
@T-Hugs does the focus trap behavior need something to be initially focused to work? If not, I think it would make sense to remove the initial focus setting from this behavior and let that be something that is implemented in it's own hook/behavior and called in useOverlay separately. That way if folks want to use useOpenAndCloseFocus on something that doesn't trap focus it they aren't tied together. In my Overlay PR I implemented  a JS only initialFocus behavior and auseOpenAndCloseFocus hook which calls initialFocus and returns focus to an element when it is removed from the DOM using the useEffect cleanup syntax, so it's ready to go.

@emplums Yes, when the focus trap is activated it is required to initially focus something (unless something inside the focus trap is already focused). The initialFocus argument lets you specify that element; otherwise it will default to the first tabbable element in the container.
I added this to support the case of confirmation dialogs (and similar UX), which may have a close button or other focusable UI above the OK/Cancel buttons.
I'm more than happy to take a second pass at some of these behaviors once they're all implemented in their base forms to make sure that we're sharing code where possible. As we work in parallel on many of these, there will be small bits of functionality that get duplicated.

Opened two bugs to follow-up on issues in this PR:

#1121
#1122

Yes, when the focus trap is activated it is required to initially focus something (unless something inside the focus trap is already focused). The initialFocus argument lets you specify that element; otherwise it will default to the first tabbable element in the container.

Sorry, didn't mean to ask if it's required a11y-wise, I mean is it required in order for this function to work correctly? Could we remove it and let another hook handle initial focus without breaking anything in this hook? If so, I think we should remove it. I see the focus trap behavior + the initial focus / return focus stuff being two separate concerns

authors: T-Hugs emplums

repo: primer/components


text:
All workflows

@colebemis commented: "I think we can remove all usages of this icon, so we don't need to design a v2 icon for it. @ashygee knows more about this"
Would we make the newer version of this icon or find a substitution?

This is not used in dotcom anymore

authors: colebemis edokoa


text:
Memory Leakage

Environment:
python:3.6.9
pylsd:ocrd-fork-pylsd == 0.0.3
OS: Linux16.04
from pylsd.lsd import lsd
img = cv2.imread("./a.jpg")
gray = cv2.cvtColor(img, cv2.COLOR_BGRA2GRAY)
lines = lsd(gray)
Memory leaks occur when as above code is used.

You can try this
https://github.com/primetang/pylsd/pull/16

you can try this
#16

repo: primetang/pylsd


text:
Reimplementing validation script as part of dataset creation

Reference Issues/PRs
Fixes #188
What does this implement/fix? Explain your changes.
This pull request recreates the flow that formerly existed in engine_validation.py. The primary functionality of this PR is to validate the tests gathered in previous steps to ensure they pass after applying the PR patch.
Key changes include:

Introduction of run_validation.py script, which validates the PR gold patch using the PR tests.
The script populates two lists in the JSON dataset: FAIL_TO_PASS and PASS_TO_PASS.
Enhancements to various scripts to improve logging, error handling, and progress tracking using tqdm.

@kwanUm did you wind up successfully using run_validation.py to save instances that passed the execution filter (that had also formerly passed the attribute filter in swebench/collect/get_tasks_pipeline.py) to a file with these changes? Or did you do something else? It seems like the authors wouldn't have taken away the ability to run the execution filter and maybe it got rolled into another part of the harness? Seems like them deleting these files would indicate that they were redundant to functionality that now exists elsewhere.

@kwanUm @chrisrytting closing this PR for now, please see my response in #188. Thanks again for the considerable effort.

authors: chrisrytting john-b-yang kwanUm

repo: princeton-nlp/SWE-bench


text:
batch logs

it seems the lib is outputting batch logs to stdout (i removed some values in the log):
2021/02/16 01:08:11 batch payload: {Batch:[{Query:mutation {result: executeRaw(query:"...",parameters:"[...]",) } Variables:map[]} {Query:mutation {result: updateOneParticipant(where:{id:"...",},data:{status:{set:"...",},},) {id createdAt updatedAt status comment location userId organizer eventId }} Variables:map[]} {Query:mutation {result: deleteManyParticipant(where:{id:{in:[],},eventId:{equals:"...",},},) {count }} Variables:map[]}] Transaction:true}

Looks like someone forgot to remove development logging 😄 https://github.com/prisma/prisma-client-go/blob/fad9280463bd9b1196c8029fac429f16bf6f2460/engine/request.go#L66-L67

Oops, thanks. Will fix asap :P

authors: hi019 steebchen tarrencev

repo: prisma/prisma-client-go


text:
Introspection engine --version argument

It is available in other engines, very useful for pin pointing binary version when debugging.
divyendusingh [test-introspection]$ ./migration-engine --version
b8d90fea39d266b128b4d748db5aca8505bb1026
divyendusingh [test-introspection]$ ./introspection-engine --version

@do4gr Did you already work on that?

This just got merged.

authors: divyenduz do4gr janpio

repo: prisma/prisma-engine


text:
Command that lets you create a seed script based on the current schema and data in your database

When you start using Prisma with an existing database, maybe just a production one, you have to bootstrap your development environment somehow. Probably you would usually do that by taking your current database, and just create a copy.
But our migrate dev development workflows depends on your being able to simply tear down and recreate your development environment (via reset and seed) - which requires you to have certain things: A Prisma schema of your database schema, a migration history that reflects that schema, and a seed script (that works with your schema) to recreate the data.
For the database schema that is already possible via db pull. You can then baseline your database (to create the base migration to get to the initial state), but for seeding we do not have build in support yet. You have to manually write a seed script and make it create useful data.
It could be great if there was a command or tool that create an initial seed script based on the current data in your database, that you then can sanitize and maintain.
(We investigated and partially implemented something like this internally before for PDP, when we created the templates you can choose when signing up and creating a new project without and existing schema and database. @sid405 did that back in the day, but it might still be around somewhere.)

I think it was called sql2pc, and it took in some SQL and "converted" it into a Prisma Client script. This SQL could come from a DB dump, and I guess that's how you'd be able to generate a seed script. (Doesn't even have to be a whole dump, just a few randomly selected rows even)
These days, you might also want to look into snaplet!

follow

authors: Abdel-Monaam-Aouini janpio sid405

repo: prisma/prisma


text:
prisma migrate dev

Prisma version (prisma -v or npx prisma -v):

Logs from Developer Tools Console or Command line, if any:

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error: Unable to require(`D:\nestjs\api-tutorial\node_modules\@prisma\engines\query_engine-windows.dll.node`)
 The specified module could not be found.
\\?\D:\nestjs\api-tutorial\node_modules\@prisma\engines\query_engine-windows.dll.node

Does the issue persist even after updating to the latest prisma CLI dev version? (npm i -D prisma@dev)

Prisma schema (if relevant):

This looks a bit like a duplicate of https://github.com/prisma/prisma/issues/12203 which has the same error message.

I'd advise against tagging this issue as a duplicate, as the error in this issue is The specified module could not be found., the error in #12203 is is not a valid Win32 application.

authors: SHRUTIKALOKHANDE janpio jkomyno


text:
findMany where condition - OR wrapped in a NOT changes to AND

Bug description
I'm very new user of Prisma, so unless I've missed something big, OR wrapped in a NOT changes to AND.
If this is a desired behavior I'm missing the logic.
I've tried NOT( ... AND ...) it doesn't change to OR
I am testing on sqlite database with prisma 4.2.1
    const edgeRootIds = [1, 2];

    const edges = await this.prismaLog.edge
      .findMany({
        select: {
          nodeId: true,
        },
        where: {
          NOT: {
            nodeId: {
              in: edgeRootIds,
            },
            OR: {
              revNodeId: {
                in: edgeRootIds,
              },
            },
          // this works:
          // AND: {
          //   NOT: {
          //     revNodeId: {
          //       in: edgeRootIds,
          //     },
          //   },
          // },
          },
        },
      });

the generated sql.
SELECT `main`.`Edge`.`nodeId` FROM `main`.`Edge`
WHERE
  (NOT
    (
      `main`.`Edge`.`nodeId` IN (?,?)
      AND `main`.`Edge`.`revNodeId` IN (?,?)
    )
  )
LIMIT ? OFFSET ?

How to reproduce

Expected behavior
That the sql generated would have a OR
SELECT `main`.`Edge`.`nodeId` FROM `main`.`Edge`
WHERE
  (NOT
    (
      `main`.`Edge`.`nodeId` IN (?,?)
      OR `main`.`Edge`.`revNodeId` IN (?,?)
    )
  )
LIMIT ? OFFSET ?

Prisma information

I was running this on a simple query on a single model.
Environment & setup

OS:
Database:
Node.js version:

Prisma Version
prisma                  : 4.2.1
@prisma/client          : 4.2.1
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine        : migration-engine-cli 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine    : introspection-core 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary           : prisma-fmt 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash    : 2920a97877e12e055c1333079b8d19cee7f33826
Studio                  : 0.469.0

seems I was not using the NOT write, if not passing it an array, it becomes an AND... but still I think it should not change a OR to AND.
        where: {
          NOT: [
            {
              nodeId: {
                in: edgeRootIds,
              },
            },
            {
              OR: {
                revNodeId: {
                  in: edgeRootIds,
                },
              },
            },
          ],
        }

And a much simpler way to write it...
where: {
  nodeId: {notIn: edgeRootIds},
  revNodeId: {notIn: edgeRootIds}
}

seems I was not using the NOT write, if not passing it an array, it becomes an AND... but still I think it should not change a OR to AND.
        where: {
          NOT: [
            {
              nodeId: {
                in: edgeRootIds,
              },
            },
            {
              OR: {
                revNodeId: {
                  in: edgeRootIds,
                },
              },
            },
          ],
        }

And a much simpler way to write it...
where: {
  nodeId: {notIn: edgeRootIds},
  revNodeId: {notIn: edgeRootIds}
}

Does this fix your issue, can we close this?

This fixes my issue.
Thanks.

authors: cantoute danstarns


text:
fieldReference of "prisma": "^4.6.0" not working with "prisma-nestjs-graphql": "^14.6.0" in nestjs project

i am using simple nestjs project. My schema.prisma file as follow:

generator client {
provider        = "prisma-client-js"
previewFeatures = ["filteredRelationCount","fieldReference"]
binaryTargets   = ["debian-openssl-1.1.x", "rhel-openssl-1.0.x", "rhel-openssl-1.1.x", "native"]
}
generator nestgraphql {
provider = "node node_modules/prisma-nestjs-graphql"
output   = "../src/@generated"
}
datasource db {
provider = "mongodb"
url      = env("DB_URL")
}
model User {
id          String   @id @default(auto()) @map("_id") @db.ObjectId
name        String  @default("")
email       String  @unique
device_id   String   @unique
enabled     Boolean  @default(true)
created_at  DateTime @default(now())
updated_at  DateTime @default(now())
@@map("users")
}

during run "npx prisma generate", I have got the following error:

Prisma schema loaded from prisma/schema.prisma
Error:
✔ Generated Prisma Client (4.6.1 | library) to ./node_modules/@prisma/client in 72ms
✔ Generated Prisma Joi Generator to ./src/@generated/joi-schemas in 567ms
TypeError: Cannot get matching input type from String, StringFieldRefInput
at getGraphqlInputType (/home/bozlur/quran-translation-web/node_modules/prisma-nestjs-graphql/index.js:551:9)
at AwaitEventEmitter.inputType (/home/bozlur/quran-translation-web/node_modules/prisma-nestjs-graphql/index.js:684:30)
at AwaitEventEmitter. (/home/bozlur/quran-translation-web/node_modules/await-event-emitter/lib/index.js:115:39)
at Generator.next ()
at /home/bozlur/quran-translation-web/node_modules/await-event-emitter/lib/index.js:12:71
at new Promise ()
at __awaiter (/home/bozlur/quran-translation-web/node_modules/await-event-emitter/lib/index.js:8:12)
at AwaitEventEmitter.emit (/home/bozlur/quran-translation-web/node_modules/await-event-emitter/lib/index.js:108:16)
at generate (/home/bozlur/quran-translation-web/node_modules/prisma-nestjs-graphql/index.js:2031:24)
at processTicksAndRejections (internal/process/task_queues.js:95:5)

Hi @bozlurrahman!
Thank you for the bug report. prisma-nestjs-graphql is a third party package and not maintained by Prisma. Stacktrace you provided points to the problem in that package. Please, report this issue to prisma-nestjs-graphql maintainers here.

Hi,
Thanks for your reply,
i have reported there and they resolved it.

authors: SevInf bozlurrahman


text:
Date object is actually string

Bug description
MongoDB: Typescript suggests dates are of JS Dates but they are actually strings.
How to reproduce
Schema: myDateField DateTime
Value in MongoDB: { "$date": "2024-03-01T00:00:27.000Z" }
In JS:
const obj = await prisma.coll.findFirst({})
typeof obj.myDateField // string, it should be Date, displayed as [object Object]

Expected behavior
Type should be JS Date
Prisma information
Actual schema is a bit more complex:
model Board {
  // ...
  columns Column[]
}

type Column {
  // ...
  cards Card[]
}

type Card {
  // ...
  createdAt DateTime
}

Environment & setup

OS: Windows
Database: MongoDB
Node.js version: v20.8.0

Prisma Version
Environment variables loaded from .env
prisma                  : 5.10.2
@prisma/client          : 5.10.2
Computed binaryTarget   : windows
Operating System        : win32
Architecture            : x64
Node.js                 : v20.8.0
Query Engine (Node-API) : libquery-engine 5a9203d0590c951969e85a7d07215503f4672eb9 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine           : schema-engine-cli 5a9203d0590c951969e85a7d07215503f4672eb9 (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm             : @prisma/prisma-schema-wasm 5.10.0-34.5a9203d0590c951969e85a7d07215503f4672eb9
Default Engines Hash    : 5a9203d0590c951969e85a7d07215503f4672eb9
Studio                  : 0.499.0

My bad. Another library was at fault for this one.


text:
FaunaDB support

Problem
FaunaDB is a serverless cloud database that offers fast global access to data via modern APIs. FaunaDB is becoming increasingly popular in the serverless ecosystem.
Suggested solution
Add support for FaunaDB in Prisma2 at the database level (more below).
Alternatives
Quoting @schickling in #350:

Fauna currently offers multiple different ways to access your data, most notably (1) Using FQL directly or via a language SDK (2) Using their GraphQL API.
In collaboration with Fauna, we've started working on a Rust driver [1] for Fauna which will eventually enable Prisma to add support for Fauna based on (1). Fauna's GraphQL API (2) is a very high-level abstraction and comes with a notable set of tradeoffs that doesn't make it a great fit as a Prisma connector since it hides a lot of Fauna's critical lower-level controls.

Additional context

[1] Rust driver developed in collaboration with Fauna
#350
https://github.com/prisma/faunadb-rust/issues/5

Hi I am using FaunaDB in my company's product and would love to know if there is something I can help with regarding this? Where should I start looking?

Anyway we can contribute?

Hey @ragnorc
Right now new connector requests are handled by Prisma employees as the connector architecture is very coupled with other pieces of the codebase and requires a good knowledge of our codebase.
I am glad that you showed interest in this but right now external contributions are really hard for us to process for that part of the codebase.

Is there a source for any further information regarding FaunaDB support? Specifically some kind of timeframe? I checked the public roadmap and I don't see FaunaDB support on the roadmap at this time.

Curious how this will work given Prisma currently abstracts a declarative language (SQL) whereas FQL is a declarative language. For example, would the Prisma API expand to accommodate things like which index to match against? And would the this be a type-safe operation such that you can't use the all_users index on your Products collection?

Also wanted to see if this was still something being considered - Fauna is growing in popularity more and more but in building applications for clients I would like to avoid FQL or any platform-specific implementations.

Would love to see this aswell!

Any update on this?

Fauna and Prisma sounds like a very powerful combo

Any news on this @albertoperdomo?

Prisma failed its mission statement (being language agnostic, only works with TS). People are jumping on to the drizzle bandwagon.

authors: ChrisJohnson-83 OultimoCoder albertoperdomo algoflows macaws nksaraf oliverjohnsticket pantharshit00 ragnorc smolattack timonmasberg


text:
the quickstart failed

Bug description
i am a newbie here, so i followed the official quickstart here https://www.prisma.io/docs/getting-started/quickstart
when running npm run dev , it hasnt output the expected result, instead, it gave a error report like this
jyf@x1:~/hack/starter$ npm run dev

> dev
> ts-node ./script.ts

/home/jyf/hack/starter/node_modules/ts-node/src/index.ts:513
    return new TSError(diagnosticText, diagnosticCodes)
           ^
TSError: ⨯ Unable to compile TypeScript:
script.ts:1:10 - error TS2305: Module '"@prisma/client"' has no exported member 'PrismaClient'.

1 import { PrismaClient } from '@prisma/client'
           ~~~~~~~~~~~~

    at createTSError (/home/jyf/hack/starter/node_modules/ts-node/src/index.ts:513:12)
    at reportTSError (/home/jyf/hack/starter/node_modules/ts-node/src/index.ts:517:19)
    at getOutput (/home/jyf/hack/starter/node_modules/ts-node/src/index.ts:752:36)
    at Object.compile (/home/jyf/hack/starter/node_modules/ts-node/src/index.ts:968:32)
    at Module.m._compile (/home/jyf/hack/starter/node_modules/ts-node/src/index.ts:1056:42)
    at Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Object.require.extensions.<computed> [as .ts] (/home/jyf/hack/starter/node_modules/ts-node/src/index.ts:1059:12)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
npm ERR! code 1
npm ERR! path /home/jyf/hack/starter
npm ERR! command failed
npm ERR! command sh -c ts-node ./script.ts

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jyf/.npm/_logs/2021-06-08T15_31_06_703Z-debug.log

i think it must be the document out of date which caused the problem, please fix it as soon as possble
How to reproduce
just follow the link https://www.prisma.io/docs/getting-started/quickstart
Expected behavior
No response
Prisma information
no
Environment & setup

OS: ubuntu 21.04
Database: SQLite
Node.js version: v12.21.0

Prisma Version
Environment variables loaded from prisma/.env
prisma               : 2.24.1
@prisma/client       : 2.24.1
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine 18095475d5ee64536e2f93995e48ad800737a9e4 (at node_modules/@prisma/engines/query-engine-debian-openssl-1.1.x)
Migration Engine     : migration-engine-cli 18095475d5ee64536e2f93995e48ad800737a9e4 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine : introspection-core 18095475d5ee64536e2f93995e48ad800737a9e4 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary        : prisma-fmt 18095475d5ee64536e2f93995e48ad800737a9e4 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash : 18095475d5ee64536e2f93995e48ad800737a9e4
Studio               : 0.397.0

yes and sorry for that


text:
This is a security test as part of a bug bouty, plese ignore.  pwtaxi

This is a security test as part of a bug bouty, plese ignore.  pwtaxi

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

Closing so no one accidentally clicks "Approve and run".
Checking if the jobs that did not need approval could be a problem here - let us know via security@prisma.io if you learn  anything interesting please.

authors: CLAassistant bazookaz1 janpio


text:
[bug] missing field on_delete in preview-6

After upgrading to preview-6, prisma2 lift save reports the following error:
  thread 'main' panicked at 'Deserializing the database migration failed.: Error("missing field `on_delete`", line: 0, column: 0)', src/libcore/result.rs:997:5

@beeplin Can you share some more information about this project, like the DB used and the datamodel? Maybe if possible, a minimal reproduction? Thanks :)

I ran into this issue too.
Chronology:
I hadn't made any edits to my data model for some time, just stopping and starting the server.
Things had been working fine.
I decided to add two fields to a model.
I add the fields (altList and altCard, in schema.prisma. )
model Deck {
    id         String  @id @default(cuid())
    title      String?
    list       String?
    altList    String?
    altCard    String?
    comments   Comment[]
    author     User?
}

I update the model with two new fields.
export const Deck = objectType({
  name: 'Deck',
  definition(t: any) {
    t.model.id()
    t.model.title()
    t.model.list()
    t.model.altList()
    t.model.altCard()
    t.model.author()
    t.model.comments({ pagination: false })
  },
})

I name my migration prisma2 lift save --name 'edit-deck'
this is when that error occurred.
I had to nuke my container and start fresh.
then it worked.
I run into this issue a lot where migrations get out of sync and editing the model has errors.
I have to start over every time I make an edit to a model.
I wish the steps were clearer on what order you must do things when you make an edit.
video tutorals would be great.

A Reproduction project:

prisma2: prisma2@2.0.0-preview-6, binary version: 4d17a0639165e5a8e54c7e5cf538ffdf114edb53
macOS: 10.14.6
Node: 12.7.0

Preview-6: prisma2 lift save --name 'addLogin' when run on unchanged (and changed) schema always throws the error, for me.
Reverting to Preview-5 eliminates the error and migrates the new schema as expected.
This issue appears on a project which is a modified version of the Photon TS example graphql-auth.
The problem does not appear on the 'official', unaltered example.
To produce the error:
With preview-6.1
$ git clone https://github.com/gihrig/hello-photon-graphql-auth.git
$ git checkout addLogin-err
$ yarn
$ prisma2 lift save --name 'addLogin'
revert to preview-5 and there is no error
$ sudo npm i -g --unsafe-perm prisma2@2.0.0-preview-5
$ prisma2 lift save --name 'addLogin'

Error: Error in lift engine for rpc listMigrations:
thread 'main' panicked at 'Deserializing the database migration failed.: Error("missing field on_delete", line: 0, column: 0)', src/libcore/result.rs:997:5

schema.prisma
datasource db {
  provider = "sqlite"
  url      = "file:dev.db"
  default  = true
}

generator photon {
  provider = "photonjs"
}

generator nexus_prisma {
  provider = "nexus-prisma"
}

model Post {
  id        String   @default(cuid()) @id @unique
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
  published Boolean
  title     String
  content   String?
  author    User?
}

model User {
  id       String  @default(cuid()) @id @unique
  email    String  @unique
  password String
  name     String?
  posts    Post[]
}

Failed listMigrations

# Failed listMigrations at 2019-08-10T05:30:59.341Z
## RPC Input One Line
```json
{"id":1,"jsonrpc":"2.0","method":"listMigrations","params":{"projectInfo":"","sourceConfig":"datasource db {\n  provider = \"sqlite\"\n  url      = \"file:dev.db\"\n  default  = true\n}\n\ngenerator photon {\n  provider = \"photonjs\"\n}\n\ngenerator nexus_prisma {\n  provider = \"nexus-prisma\"\n}\n\nmodel Post {\n  id        String   @default(cuid()) @id @unique\n  createdAt DateTime @default(now())\n  updatedAt DateTime @updatedAt\n  published Boolean\n  title     String\n  content   String?\n  author    User?\n}\n\nmodel User {\n  id       String  @default(cuid()) @id @unique\n  email    String  @unique\n  password String\n  name     String?\n  posts    Post[]\n}\n"}}

RPC Input Readable
{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "listMigrations",
  "params": {
    "projectInfo": "",
    "sourceConfig": "datasource db {\n  provider = \"sqlite\"\n  url      = \"file:dev.db\"\n  default  = true\n}\n\ngenerator photon {\n  provider = \"photonjs\"\n}\n\ngenerator nexus_prisma {\n  provider = \"nexus-prisma\"\n}\n\nmodel Post {\n  id        String   @default(cuid()) @id @unique\n  createdAt DateTime @default(now())\n  updatedAt DateTime @updatedAt\n  published Boolean\n  title     String\n  content   String?\n  author    User?\n}\n\nmodel User {\n  id       String  @default(cuid()) @id @unique\n  email    String  @unique\n  password String\n  name     String?\n  posts    Post[]\n}\n"
  }
}

RPC Response
null

Stack Trace
thread 'main' panicked at 'Deserializing the database migration failed.: Error("missing field `on_delete`", line: 0, column: 0)', src/libcore/result.rs:997:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::result::unwrap_failed
   9: <sql_migration_connector::SqlMigrationConnector as migration_connector::MigrationConnector>::deserialize_database_migration
  10: migration_core::commands::list_migrations::convert_migration_to_list_migration_steps_output
  11: <migration_core::commands::list_migrations::ListMigrationStepsCommand as migration_core::commands::command::MigrationCommand>::execute
  12: <F as jsonrpc_core::calls::RpcMethodSimple>::call
  13: <F as jsonrpc_core::calls::RpcMethod<T>>::call
  14: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
  15: <futures::future::then::Then<A,B,F> as futures::future::Future>::poll
  16: <futures::future::map::Map<A,F> as futures::future::Future>::poll
  17: <futures::future::either::Either<A,B> as futures::future::Future>::poll
  18: futures::task_impl::std::set
  19: std::thread::local::LocalKey<T>::with
  20: futures::future::Future::wait
  21: jsonrpc_core::io::IoHandler<M>::handle_request_sync
  22: migration_core::rpc_api::RpcApi::handle
  23: migration_engine::main
  24: std::rt::lang_start::{{closure}}
  25: std::panicking::try::do_call
  26: __rust_maybe_catch_panic
  27: std::rt::lang_start_internal
  28: main

I can confirm this

Happened once to me as well but only on a DB that is setup with preview 5 and below, a new DB setup with preview 6 does not exhibit this: https://gist.github.com/divyenduz/ca80533a8b4dfa0b2a2023de7e3c7cae

I agree, the problem is more a preview 5 to 6 migration issue than a bug, per se.
I tried editing or deleting records in the _migrations table, even dropping the the table, and removing different items in prisma/migrations. In the end I had to delete the database file to get preview-6 to work.
To get to preview-6 I did the following, working with SQLite:

Export db data, excluding the _migrations table
Delete the database file (dev.db)
Delete prisma/migrations/lift.lock
Remove any folders under prisma/migrations that correspond to earlier failed migrations.
prisma2 lift up
Import data

Now prisma2 lift up reports 'All migrations are already applied'

Update: Thanks for raising this issue, we missed this regression between preview-5 and preview-6 and this should have been mentioned in the release notes. We will take measures to make sure that we avoid that in future.
We expect breaking changes like these to occasionally pop up between preview releases and we will have release notes for all regressions. I will close this issue.
Please re-open a new issue if you feel that something is still unaddressed from this issue.

authors: beeplin divyenduz gihrig keepforever pantharshit00


text:
Implement "Rename" operation (e.g. for fields, models, ...) that automatically apply @map

WIP
Notes:

Might require a DB schema information file
F2

Duplicate of #245

authors: carmenberndt schickling

repo: prisma/vscode


text:
Recent merge breaks specs?

Am working on a potential PR (to add option for null api cache to aid ruby projects that use VCR) and after pull of recent merge (3285f6d633886c9f4baed40b456703e0c86ce131), specs break because of undefined local variable or method `token_cache' for Prismic::API:Class at line 128 of lib/prismic/api.rb

Yes indeed, the build was broken. It's fixed, sorry for the trouble!

authors: dhainlin erwan

repo: prismicio/ruby-kit


text:
Adding contributing guide

Adding contributing & linking to it
removing some dead code.

Here's my suggested edits @faresd, what do you think?

How to contribute to this kit
Did you find a bug?

Do not open up a GitHub issue if the bug is a security vulnerability
in the kit, and instead, email us at security@prismic.io.

Ensure the bug was not already reported by searching on GitHub under Issues.

If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behaviour that is not occurring.

Did you write a patch that fixes a bug?

Open a new GitHub pull request with the patch.

Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.

Link the PR to any open issues that it resolves.

Did you fix whitespace, format code, or make a purely cosmetic patch?

Open a new GitHub pull request with the change plus a small description and the team will verify/merge.

Do you want to add or request a new feature/update?

Please create PR in Github with the tag [RFC] to begin a conversation about a new feature. (GitHub issues are primarily intended for bug reports and fixes.)

Do not submit any code to GitHub until you have collected positive feedback about the change.

How do I make a PR?

If you want to learn how to make a PR then follow this freeCodeCamp guide to making your first PR.

Do you want to help review and merge PR's?

If you want to get involved in the maintenance of this kit, then you can request to become an admin on the project by messaging the Education Team on our community forum.

Thanks!

authors: faresd phillysnow


text:
tsx watch --ignore ... causes ERR_MODULE_NOT_FOUND errors

Precheck

[X] I searched existing issues before opening this one to avoid duplicates
[X] I'm able to reproduce this issue and prove it with a minimal reproduction
[X] I understand this is not a place to ask for free debugging support

Problem
Ignoring files with --ignore ./../pkg-a/.next/**/* causes ERR_MODULE_NOT_FOUND error:
$ cd pkg-b

$ pnpm i
Lockfile is up to date, resolution step is skipped
Packages: +2
++
Done in 492ms

~/projects/node-d5jut7/pkg-b
$ pnpm tsx watch --clear-screen=false --ignore ./../pkg-a/.next/**/* index.ts

(node:77) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/projects/node-d5jut7/pkg-a/.next/cache/webpack' imported from /home/projects/node-d5jut7/pkg-b/
    at __node_internal_ (https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:36:5406)
    at new <anonymous> (https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:36:4168)
    at https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:114:12002
    at https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:114:12159
    at defaultResolve (https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:114:12167)
    at nextResolve (https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:248:2120)
    at h (file:///home/projects/node-d5jut7/pkg-b/node_modules/.pnpm/@esbuild-kit+esm-loader@2.5.0/node_modules/@esbuild-kit/esm-loader/dist/index.js:19:2612)
    at U (file:///home/projects/node-d5jut7/pkg-b/node_modules/.pnpm/@esbuild-kit+esm-loader@2.5.0/node_modules/@esbuild-kit/esm-loader/dist/index.js:19:1536)
    at N (file:///home/projects/node-d5jut7/pkg-b/node_modules/.pnpm/@esbuild-kit+esm-loader@2.5.0/node_modules/@esbuild-kit/esm-loader/dist/index.js:19:1766)
    at h (file:///home/projects/node-d5jut7/pkg-b/node_modules/.pnpm/@esbuild-kit+esm-loader@2.5.0/node_modules/@esbuild-kit/esm-loader/dist/index.js:19:2711)
    at async nextResolve (https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:248:2114)
    at async ESMLoader.resolve (https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:248:7550)
    at async ESMLoader.getModuleJob (https://noded5jut7-fpux.w-credentialless.staticblitz.com/blitz.6843a59c.js:248:4376) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Removing the --ignore option causes the program to run through:
$ pnpm tsx watch index.ts
a 1

Expected behavior
Imported modules / packages / files can still be located if they are a part of the --ignore specifier
Minimal reproduction URL
https://stackblitz.com/edit/node-d5jut7?file=pkg-b%2Findex.ts&file=pkg-a%2F.next%2Fcache%2Fwebpack%2Ffile.ts
Version
v4.5.0
Node.js version
v18.18.0
Package manager
pnpm
Operating system
Linux
Contributions

[ ] I plan to open a pull request for this issue
[ ] I plan to make a financial contribution to this project

Bump - having the same issue

Digging deeper, this happens due to glob expansion.
What happens with the ignore flag above is that bash matches the files and expanded the arguments.
For example:
pnpm tsx watch --clear-screen=false --ignore ./../pkg-a/.next/**/* index.ts

Became
pnpm tsx watch --clear-screen=false --ignore ./../pkg-a/.next/path/path1 ./../pkg-a/.next/path/path2 ./../pkg-a/.next/path/path3 index.ts

To specify the ignore pattern without triggering that expansion, you only need to pass it as a string. So adding '' around it should fix the problem.
pnpm tsx watch --clear-screen=false --ignore './../pkg-a/.next/**/*' index.ts

This is what I'm using now. I reckon the docs should be updated to include the quotes

@Vija02 Appreciate it! I updated the docs: https://tsx.is/watch-mode

authors: Vija02 karlhorky lauhon privatenumber

repo: privatenumber/tsx


text:
Appointments are not shown in Calendar

Goodday,
Thank you for the clear instruction videos, it was interesting to learn the steps in making an appointment agent. However, after deploying your code I don't see the scheduled appointments in my Calendar. I went through the steps twice and I don't get any error.
Could you please help me out?

You need to make sure the service account is accurate. If your service account is not correct the calendar invite will not be created.

authors: Candlegreen priyankavergadia


text:
Misc Changes

Some small errors I noticed while working on the EECS 545 project last semester but never got pushed until now.
@jeff-regier , quick question - should the poetry.lock file be committed? I figured that as long as everyone has the correct pyproject.toml that should be sufficient (since if this file changes then the .lock file will be updated automatically after running poetry lock or poetry update). What do you think?

I'm not sure what the standard practice is.
If we commit poetry.lock to version control, then, say, six months from now, we'll be able to checkout a version of bliss from today and run it easily, even though many dependencies will have made breaking changes by then.
But there are probably some drawbacks too, e.g. large diffs, having to run poetry install every time some else changes poetry.lock.

After reading a bit about it, I think committing poetry.lock is better than not. But we should try not to update it all the time without reason. A good reason would be that we have a new dependency to add. Or we need a newer version. Or that it's been awhile and many dependencies are better now.

I see, in this case it seems two dependencies were updated to newer versions but both don't seem important (although not sure). In this case should we not commit then?

Either way seems fine

all tests pass and gpu and cpu now

authors: ismael-mendoza jeff-regier

repo: prob-ml/bliss


text:
ci: Add automatically a needs triage label to PRs coming from a team outsider

We need to highlight PRs coming from a team outsider, to differentiate it from our internal PR.

This exactly the kinda thing which is counterproductive to creating a community. There should be no difference between internal and external contributions.

As a company-driven open source project we need ways to support feedbacks, contributions, but also follow a product-oriented workflow.
We will get to a community-driven project when time is ripe.

authors: adrinjalali thomass-dev tuscland

repo: probabl-ai/skore


text:
Initial version of visualization code for unary relations over a single domain

Sample output image when run with
$ ./visualize_unary.py --observations=../cxx/assets/animals.unary.obs --clusters=../cxx/assets/animals.unary.hirm --output=/tmp/vis.html

Reassigned to @srvasude (who agreed to review while I focus on Model 7)

Thanks for the review!

authors: ThomasColthurst emilyfertig

repo: probcomp/hierarchical-irm


text:
dev

Feature Request
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I have an issue when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen. Add any considered drawbacks.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Teachability, Documentation, Adoption, Migration Strategy
If you can, explain how users will be able to use this and possibly write out a version the docs.
Maybe a screenshot or design?

like

repo: probot/probot

license: ISC


text:
[ Feat Enhancement ]  There should be smooth scroll in on page "https://p5js.org/reference/" on items present at top see video for better understanding

Increasing Access
It will give a User friendly appearance the main part after clicking can be highlighted for better searching of the element
Screencast from 05-09-23 01:23:16 PM IST.webm
Most appropriate sub-area of p5.js?

[ ] Accessibility
[ ] Color
[ ] Core/Environment/Rendering
[ ] Data
[ ] DOM
[ ] Events
[ ] Image
[ ] IO
[ ] Math
[ ] Typography
[ ] Utilities
[ ] WebGL
[ ] Build Process
[ ] Unit Testing
[ ] Internalization
[X] Friendly Errors
[X] Other (specify if possible)

Feature enhancement details
There can be smooth scroll just like when clicking on elements below environment and when the element get clicked the part they are taken to should be highlighted for better undestanding

hello , can you assing me this issue i want to work on it

can you please check my request

hi can anybody check and close this i have already added the feature requested

Hi @abhi267266 and @Rishul2003, we are currently in the process of rethinking the overall design of the website and so will not be implementing this as part of the current website. We will revisit this as part of the website redesign project (along with all other issues tagged "Web Design") during the design phase and will incorporate if required. Please feel free to have a look at open issues on p5.js if you'd like to contribute to another issue. Thanks!

can i help with that if you are using react for redesign can you give me a reference where can i look for more info

We are still at the planning phase of the project and cannot quite yet share much details just yet.


text:
Tests: add coverage report

Print a coverage report at the end of make check. Opens the door to check for a minimum coverage, or checking that the coverage doesn't decrease.
Why this? I started exploring it, seemed possible, then it was one rabbit hole after the other. Next time I'll think twice before thinking "I'll finish this just because I started it".

Leaving this one in the capable hands of @kprimerakis.

authors: SamirTalwar sergiogiro

repo: prodo-ai/plz


text:
Set X-Forwarded-Proto header if TLS is enabled when running checks

If I have an app which only responds to HTTPS requests (or redirects non-secure requests to HTTPS) any checks defined in the CHECKS file will fail. This isn’t a problem for “real requests” as nginx sets the X-Forwarded-Proto header accordingly.
I therefore suggest setting the X-Forwarded-Proto header to https when running checks against a TLS-enabled app.

Seems reasonable. Have you used this in a live environment?

I have (only) tested the change with this simple Express app:
app.enable('trust proxy')

app.get('/', function(request, response) {
  if(!request.secure) {
    return response.redirect(301, 'https://' + request.get('Host') + request.url)
  }

  response.send('Hello World!')
})

#1300 comes with some test fixes. can you rebase once I merge that?

No problem.

g2g

authors: SonicHedgehog michaelshobbs

repo: progrium/dokku


text:
Support for BDX session initiation

Problem
The only way for initiating/testing BDX protocol is in the context of file transfer with OTA.
But it only tests BDX in a specific configuration and remaining configs cannot be tested.
There is no way right now to execute tests TC-BDX-1.5, 1.6.
Proposed Solution
Add support for BDX session initiation to either OTA reference apps or chip-tool to perform these tests.

@carol-apple ?

We can't test this for v1.0

Moving out then, thanks!

authors: carol-apple ukatira woody-apple

repo: project-chip/connectedhomeip


text:
Need to sort out storage (PersistentStorageDelegate and KVS) behavior for 0-length nullptr data

Problem
Some of our storage backends allow storing a nullptr with 0 length; others do not.  We should be consistent and either always allow it (preferred) or always disallow it.  The current setup means that code can work against one backend but fail against another, reducing the value of testing we do.
Proposed Solution

Document in PersistentStorageDelegate what the expected behavior is.
Document in KeyValueStoreManager what the expected behavior is.
Align implenentations with the documentation.

It's possible that the storage audit addressed this....

Fixed by storage audit.


text:
[Pre-SVE] [TC-CNET-4.6] Chip-Tool Verification Steps doesn't match Expected Outcome

Problem
Step 1 to Step 3 expects FAILSAFE_REQUIRED status code, but CHIP Tool Verification Steps show UNSUPPORTED_ACCESS.

@AlvinHsiao Which SHA are you using?  Does this SHA include the fixes from #19964?

The specific commands are, to be executed without a fail-safe armed:
chip-tool networkcommissioning add-or-update-thread-network 1232034768527434274  51 0

chip-tool networkcommissioning remove-network 1232034768527434274 51 0

chip-tool networkcommissioning connect-network 1232034768527434274 51 0

These all assume the device is commissioned as node id 51.

It seems fixed in the newest https://docs.google.com/spreadsheets/d/1h4d4J90KAxFqUL_cXZHyM3pHjHCEXzFITkQhN2KMqDY/edit#gid=509371791

authors: AlvinHsiao bzbarsky-apple